Coordination Message Format

Coordination Message Format (Voice)

Note: IRL, most non-TWR positions have at least two controllers, and three for busy positions. One to talk to aircraft, one to plan procedurally in the event of a surveillance outage, and one to effect the coordination as described here. We don’t have that luxury on the VATNZ network, so voice coordination as described here is not normally done; transferring the tag is usually sufficient. However, controllers should first contact adjacent controllers for their agreement to forego formal coordination. Exception: if handing off to or from a procedural TWR, this must be coordinated, since tag transfers do not take place in this circumstance.

For the sake of clarity, this does not include “auto-releases” or where an aircraft is coming off a long STAR for an ILS or similar long straight-in approach. Coordination is not required in these two circumstances.

When using voice to coordinate, there are three message categories: ESTIMATE, DEPARTURE, and REVISION.

ESTIMATE is used for aircraft already in the air, and is the nominal coordination type between TMA/Procedural TWR to ENR, ENR to ENR, and ENR to TMA/Procedural TWR.

Similarly, DEPARTURE is used for aircraft just departing, and originates from a TWR.

REVISION is used if a change is requested after coordination has taken place, but before the aircraft has transferred to the accepting controller.

ESTIMATE message

Format:

ESTIMATE [aircraft callsign]
(if departing into NZZO) DEPARTURE [departure time]
[REP] [ETO]
[level] or CLIMBING TO [level] or [level] DESCENDING TO [level]
(if handing over to a procedural TWR) [type of approach] [route]
other information

Example 1.

ANZ101 is an NZAA-YSSY flight that departed NZAA at 1823z and is entering NZZO at MADEP REP, with MADEP estimated at 1908z, climbing to RFL F360. OCR is required to effect coordination with ARO 10 minutes before ETO MADEP. ANZ101 has advised OCR that it will not reach its RFL (F360) by MADEP per the SID transition requirement and has requested to cross MADEP at F330 or higher. OCR must obtain ARO approval for the lower crossing level, since ARO expects ANZ101 to cross MADEP at its RFL.

(OCR to ARO)

ESTIMATE ANZ101 DEPARTURE 1823 MADEP 1908 CLIMBING TO F360 REQUEST CROSS MADEP F330 OR ABOVE

(ARO to OCR)

ANZ101 ACCEPTED CLIMBING TO F360 CROSS MADEP F330 OR ABOVE

(OCR to ARO)

CROSS MADEP F300 OR ABOVE ANZ101

(ARO to OCR)

NEGATIVE ANZ101 CROSS MADEP F330 OR ABOVE

(OCR to ARO)

CROSS MADEP F330 OR ABOVE ANZ101

Example 2.

ANZ549 is an NZAA-NZCH flight estimating NP at 0441 at FL360. Coordination is required 10 minutes before NP.

(OCR to NAK)

ESTIMATE ANZ549 NP 0441 F360 CAUTION SIMILAR CALLSIGN ANZ449 12 MINUTES BEHIND

(NAK to OCR)

ANZ549 ACCEPTED F360 AND ANZ449 ROGER

Example 3.

ANZ699 is an NZAA-NZNV flight estimating OGAVO at 0528, descending to F150 requesting the VOR/DME RWY04 approach for training. Coordination should be effected 15 minutes before OGAVO, the transfer point. As this requires the NV2A arrival rather than the default RNP arrival, STH must obtain TNV approval beforehand.

(STH to TNV)

ESTIMATE ANZ699 OGAVO 0528 F210 DESCENDING TO F150 REQUEST VORDME RWY04 VIA NV2A ARRIVAL

(TNV to STH)

ANZ699 ACCEPTED DESCENDING TO F150 CLEARED NV2A ARRIVAL EXPECT VORDME RWY04 VIA DME ARC

(STH TO TNV)

CLEARED NV2A ARRIVAL ANZ699 AND ROGER

DEPARTURE message

Format (procedural TWR):

DEPARTURE [aircraft callsign] [departure time]

Example (procedural TWR):

ANZ029M is a flight from NZNR to NZAA, departing now at 0214z.

(TNR to OHA) DEPARTURE ANZ029M 0214

(OHA to TNR) ANZ029M

(later)

(TNR to OHA) ESTIMATE ANZ029M MOOSE 0259 CLIMBING TO F190

(OHA to TNR) ANZ029 ACCEPTED F190

Format (surveillance TWR):

DEPARTURE [aircraft callsign] ROLLING RUNWAY [number]

Example (surveillance TWR):

ANZ101 is departing from RWY23L at NZAA.

(TAA to ATMA) DEPARTURE ANZ101 ROLLING RWY23L

(ATMA to TAA) ANZ101

REVISION message

A REVISION message is required if a change to what has already been coordinated with the accepting controller is requested or has occurred. Changes to ETO/ETA, route, or level are examples.

Revision to ETO/ETA

If the ETO/ETA varies by 3 minutes or more from what has been coordinated:

REVISION [aircraft callsign] [REP] [new ETO/ETA]

Example:

REVISION ANZ029M MOOSE 0255

Revision to level

REVISION [aircraft callsign] CLIMBING TO AMENDED [amended level]

Example:

REVISION ANZ029M CLIMBING TO AMENDED F170