ATLAS TEST27.20 - AXEMAN AND KRISTINE CAS
=======================================

ENABLE
Stop ATLAS and DCS. Update Test27 and apply its host DCS integration to the
selected profile. Airports > JTAC air support > Enable. Axeman defaults to
249.500 MHz UHF AM. Kristine remains on 249.000 AM with her female voice.
Run the single ATLAS Setup EXE. Existing ATLAS Radio is retained; new pilots install Radio separately.
Use different frequencies from mission services. Aircraft must support UHF AM.

ATLAS owns this controller; no aircraft native JTAC menu or SADL is required.
Native ground units are discovered regardless of spawn script. Virtual cargo
cannot observe until it exists in DCS. A script that leaves transported ground
units physically present cannot communicate private cargo status to ATLAS.

KRISTINE - 249.000 AM
Check in when you are willing to take CAS tasking:
  "Kristine, Colt one one, available for CAS."
Or include optional weapon details and time available:
  "Kristine, Colt one one, two GBU-twelves, twenty minutes available for CAS."
Exact weapon names/counts are not required. Say AVAILABLE FOR CAS or READY FOR
CAS at the end of the check-in. Callsign and "checking in" are optional.
Reported weapons are advisory text only; actual CURRENT inventory determines
eligibility. A declaration cannot qualify an empty or air-to-air-only aircraft.
Availability applies to your own aircraft, not unverified wingmen.

Kristine acknowledges your time available. Omitted playtime defaults to 30
simulation minutes; you can report 1-180 minutes. Repeat the check-in to renew
or update it. Landing, disconnect, changing slots/occupants, respawn, a new
mission, or disabling this feature clears availability. Time expiry removes
you from selection and cancels an outstanding offer; it does not interrupt an
Axeman attack already accepted. "Unable CAS" withdraws your availability and
offer until you explicitly check in as available again. After a handoff to
Axeman, check in with Kristine again when you want another CAS assignment.

When a friendly observer sees an eligible enemy ground target, Kristine selects
the nearest checked-in, available airborne player aircraft with suitable CAS
weapons by distance to the observer. Armed aircraft that have not volunteered
remain outside her tasking list. No eligible available aircraft means no vector.
Her announcement is addressed to that aircraft and audible to everyone on
249.000. It supplies a vector to the named IP and a handoff to Axeman.
These are pilot instructions; no aircraft AI task or autopilot is changed.

CURRENT Unit.getAmmo inventory must confirm explosive bombs, rockets or a
recognized air-to-ground missile. Air-to-air-only, anti-radiation/anti-ship-only,
gun-only, practice/marker, depleted/jettisoned and unknown loads are excluded.
Aircraft model/mission role is not a qualification. Recognized ASM families:
AGM-65, AGM-114, AGM-176, Brimstone, 9M127, 9M120, 9M114, Kh-25, Kh-29,
S-25L, BGM-71 and HOT3, with supporting native descriptors. Unknown mod missiles
are excluded. Qualification does not establish weapon/target effectiveness,
cockpit readiness, fuel suitability or priority over your existing mission.

Observer/target offers are reserved and rechecked. Active Axeman assignments
are excluded. Invalid inventories, identities, observers or targets withdraw
the offer. Discovery is polled every five seconds; offers expire after three
minutes. Announcements are at least 30 seconds apart, with a five-minute repeat
limit per task. "Kristine, request CAS vectors" repeats your current vector.
"Unable CAS" releases your offer and removes you from the availability list.

AXEMAN - RADIO FLOW (AIRCRAFT RADIO PTT, NOT JESTER INTERCOM)
  "Axeman, Colt one one, checking in."
  "Ready for game plan."
  Copy Type 2 / bomb-on-target, one pass, IP/egress coordinates, altitude and
  the explicitly briefed MAGNETIC heading reference. Kristine's IP is preserved.
  "Ready to copy."
  Copy nine lines, grouped three at a time without spoken line numbers.
  "Ready for remarks."
  Copy heading/tolerance, routing altitude, friendly restriction and laser code.
  Read back target elevation, full target location and every restriction.
  Natural example (substitute the actual briefed values):
  "Axeman, Colt one one. One hundred feet. Three eight Tango Kilo Mike,
   one two three four five, six seven eight niner zero. Final attack heading
   zero three zero, plus or minus thirty degrees. At or above five thousand
   feet until IP inbound. No attack within five hundred meters of friendlies."
  Labelled readbacks remain supported. A final heading cone may also be read
  as its equivalent boundaries, e.g. 000 through 060 equals 030 plus/minus 30.
  Axeman requests the readback once, then confirms or identifies the affected
  item. For a correction, repeat that item, e.g. "Correction, grid [full MGRS]".
  Correct earlier items are retained only for the current assignment. Every
  required value must be confirmed before the attack sequence can advance.
  Wait for "Readback correct". Fly to the actual IP at routing altitude or above.
  "IP inbound."
  "Request smoke."       Optional actual ATLAS white smoke.
  "Laser on."            Optional ATLAS-owned spot, with the briefed code.
  "Contact the mark."    Mark contact does not identify the target.
  "Tally target."        Only after identifying the assigned target.
  "Colt one one, IN heading [three digits]."
  Wait for "Axeman. Cleared hot, one pass." Fly the attack.
  "Colt one one, off [direction]." Follow the assigned egress to Bravo.
  "Established at egress." Axeman reports the previous target and remaining targets in sight.
  "Request further tasking." New game plan, then "Ready to copy" for the next nine-line.
  Complete remarks/readback/IP inbound/tally/IN for each attack.
  "Request battle damage assessment." "Checking out."

Say the actual values, not brackets/example numbers. Exact elevation, full grid,
route altitude, final heading, tolerance and 500-meter restriction are required.
Missing/incorrect values cannot advance. Continue, mark contact and readback
confirmation are not attack clearances. BDA confirms native observed destruction;
despawn/UNIT_LOST alone is not a kill. New passes require a fresh brief/readback/clearance, without checking in again.

CONTINUOUS TASKING
After OFF, fly to the assigned egress point at routing altitude and report established.
Axeman reports only currently visible detected hostile ground units, including a
surviving assigned target. Counts are not the total enemies in the mission and may
change with observation. Despawn is never counted as confirmed destruction.
Say "Request further tasking", "Request next target", or "Request reattack".
The same observer selects the nearest visible eligible unassigned target; a surviving
target may be assigned again. Axeman passes a fresh game plan, followed by the
nine-line on "Ready to copy" and remarks on "Ready for remarks". All readback,
contact, routing and per-pass clearance gates reset. Old laser handles are stopped.
He does not silently switch observers or give blanket clearance for remaining targets.
No visible target means standing by; a later request can pick up newly detected units.
Current native CAS stores and actual egress position/altitude are required.
The observer stays reserved while attached, including between passes. Check out or
abort to release it. Observer pickup/replacement, native FAC takeover, player identity
changes, mission disable or ten minutes without accepted task activity ends continuity.
Other missions' JTACs, spots, tasks, radios and menus remain untouched.

ROUTING
IP Alpha [task number] and egress Bravo [task number] are computed geographic
points six NM from the target, not your check-in position or cockpit waypoints.
Copy coordinates from the game plan/current brief and enter them manually.
"Request routing" repeats the points. Multiple sectors are considered; routes
avoid ground friendlies within 750 meters and avoid passing through the immediate
target area on the way to the IP. Terrain is sampled every 200 meters along
centerline and 500 meters either side of transit/ingress/egress legs. Routing
altitude is the sampled maximum plus 1,500 feet, rounded up to 1,000 feet, with
a 5,000-foot MSL minimum and 25,000-foot ceiling. Missing/unusable data means
standby. This is sampled terrain screening, not continuous obstacle clearance,
SAM avoidance, weather/airspace deconfliction or an autopilot path. Climb first.

All numerical headings and CAS vectors are MAGNETIC. ATLAS uses the installed
DCS magnetic model at the reference position and mission month/year. The user
hook performs native model queries outside the mission sandbox. No map-wide
constant, external framework, cloud lookup or MissionScripting.lua edit is needed.
Axeman uses the IP variation for the briefed attack axis, with true geometric
position checks kept separate. Kristine uses the aircraft position for CAS vectors.
All future tasking obtains a fresh magnetic brief and readback. Missing magnetic
data withholds numerical guidance; it never falls back to a true heading.
Other ATLAS numerical position bearings and dynamic IFR heading assignments are
also converted. Published magnetic courses/radials are retained as published.
Physical runway, ship, aircraft and terrain geometry remains in true coordinates.
IP inbound requires within 1.5 NM of the IP and routing altitude (200-foot
tolerance). IN requires readback, inbound, tally, a reported heading within
30 degrees of the brief and an aircraft position in the corresponding approach
sector 500 meters to 8 NM from the target. Reported heading is not measured
aircraft orientation. One clearance lasts 45 simulation seconds. Routing altitude
applies through IP inbound; the pilot selects the attack profile. Egress-
established checks actual destination proximity and routing altitude.

EXISTING MISSION JTACS
ATLAS never sets AI tasks, routes, ROE, radios or native menus. Native FACs and
their group members are excluded as Axeman observers. An observer becoming
a native FAC aborts its ATLAS assignment. Only ATLAS-created laser handles are
updated/destroyed; other scripts' spots/event handlers are not replaced.
Known FAC laser codes in mission task data are excluded. Private dynamically
chosen script codes are not universally discoverable: coordinate ATLAS and
mission frequencies/codes. No claim of universal hidden-code conflict detection.

Pickup/death/replacement, lost native detection, target movement over 25 meters,
friendlies entering the route, pilot identity changes and stale telemetry
invalidate affected instructions. Targets must be within 8 km of the observer,
with visible/type/range-known native detection and terrain line of sight.
The 500-meter attack restriction is an ATLAS simulator rule, not a universal
weapon-specific real-world danger-close distance.

"Say again line six." "Repeat remarks." "Request routing." "Status."
"Terminate." "Abort." "Checking out." One intent per transmission.
Open current JTAC briefs in settings for coordinates and numbered written lines.
Pocket/optional Gemini speech remain selectable; recognition stays local.
Automated fixtures and offline speech are not live multiplayer flights.

REFERENCE
Radio design follows the CAS briefing/readback and individual attack-control model
in JP 3-09.3; ATLAS terrain routing and fixed separation remain simulator limits.
https://edocs.nps.edu/dodpubs/topic/jointpubs/JP3/JP_3_09.3_090708.pdf