Rules this trainer uses, and where they come from
- Coordinate with an adjacent radar sector before the aircraft is within 5 NM of the boundary (RDR 15, 15.2.1).
- Domestic to Oceanic: coordinate before the aircraft comes within 10 NM of the Oceanic boundary (RDR 15, 15.2.1).
- Forcing a strip is not coordination; it only gives information on which to base coordination (RDR 15, 15.2.1).
- Under continuous radar control the CPL time criterion is reduced to 10 minutes; an LOA or LUO may reduce it further (RDR 15, Coordination Time Criteria).
- Revise a passed estimate when it changes by 3 minutes or more for a radar sector, 2 minutes for an approach sector, and 5 minutes for an aerodrome control unit (RDR 15, 15.5.2).
- Approval request when the time to the boundary will not allow coordination within the time criteria: “APPROVAL REQUEST (callsign, level) VIA (significant point) (other details)” (RDR 15, 15.6.1).
- Before terminating radar service into a non-radar environment, establish non-radar separation and ensure the aircraft can continue on its own navigation, considering terrain (RDR 15, 15.2.2).
Game settings to confirm with the training team, not taken from the course: a new level is a Revision with 10 minutes or more to the boundary point, and an Approval request inside 10 minutes; a non-standard level and an off-track deviation are a Will you accept, with no estimate for the deviation; Forest Tower arrivals use a 10 NM coordination distance at FZ; estimates are accepted within ±1 minute; even levels 090° to 269° magnetic, odd levels 270° to 089°; the North Control name and the datablock layout are placeholders. The Forest airspace is the fictional training chart. Figures come from the 054 question bank built from 054 Surveillance Control (Domestic); check them against current MATS and AIPNZ before use.