Skip to main content

TWR/GND

Coordination Between ATC Units

Effective communication and coordination between ATC units areis essential for safe and efficient air traffic management. While many standard procedures are defined in SOPs,SOPs, certainsome situations require direct controller-to-controller coordination betweento controllers.handle non-standard operations effectively.

Coordination Between Tower (TWR) and Approach (APP)APP

Some scenarios where Tower and Approach controllers must coordinate include:in various scenarios, including:

  • Vectored Departures: If→ anWhen IFRa pilot cannot or does not want to fly a SID.SID.
  • Visual Departures: → If permitted accordingunder to SOPs.SOPs.
  • Departure Releases: If→ required.When required for IFR departures.
  • Non-Standard Approach Procedures: Such→ ase.g., visual approaches when a pilot cannot fly a standard approach.
  • Emergencies: → Including all relevant details.details.
  • Missed Approaches: Including→ Coordination on reasons and& further instructions (usually the standard missed approach)approach).
  • SVFR Operations: To→ allowAllowing the approach controllerAPP to increase arrival spacing between arrivals if necessary.
  • Low Visibility Operations. → Adjusting procedures to ensure safe traffic flow.
  • Runway Closures and Closures/Reopenings. → Ensuring both controllers manage traffic accordingly.
  • Change of Runway Direction Changes. → Synchronizing arrivals and departures to the new configuration.
  • Departures from Non-Standard Runways: → If a pilot requests a different departure runway than the one in use.

Coordination Between Tower (TWR) and Ground (GND)

GroundEfficient communication between TWR and TowerGND controllersis must coordinate efficientlynecessary in several situations,situations such as:

  • PilotIncorrect Taxiing Incorrectly:→ IfWhen an aircraft mis-taxis and needs to be rerouted.rerouting.
  • Aircraft Technical Issues at the Holding Point: → If an aircraft developshas a technical problem, requiring subsequent aircraftdepartures to be rerouted.rerouted.
  • Pilot Requests a Specific Intersection: → When a pilot has requestedrequests a specific taxiway intersection for departure.
  • Missing Aircraft on Frequency: → If a controller is missing an aircraft thathas shouldnot alreadyswitched befrequencies onas theirexpected, frequency.coordination is needed to locate them.

Coordination Guidelines

Unlike some Approach and Center communications,coordination, Tower and Ground coordination typically does not havefollow standardizedstrict phraseology.phraseology. Instead, controllers should use clear and concise plain language shouldto bekeep used.communication Sincebrief and efficient—especially when the receiving controller may beis busy with pilots,pilot it is important to keep coordination brief and to the point.interactions.

Example Coordination Exchanges

Tower and Approach Coordination

TWR:TWR → APP:

"Approach, Tower
APP:Tower."

APP → TWR:

"Go ahead
TWR:ahead."

TWR → APP:

"TUN988 cannot fly SIDs and needs direct MEDIL. What vectored departure should I issue?
APP:"

APP → TWR:

"Climb runway track to 4000 feet, expect radar vectors. TWR: Copied."

TWR → APP:

"Copied."

Tower and Ground Coordination

TWR:TWR → GND:

"Ground, Tower.
GND:"

GND → TWR:

"Go ahead
TWR:ahead."

TWR → GND:

"KMR112 mis-taxied, now coming via J5 instead of J2
GND:J2."

GND → TWR:

"Roger."

Class D Airspace Coordination

ACC/APP → Class D Tower (Heads-Up Coordination)

For arrivals or overflights, coordination should be completed at least 5 minutes before the boundary.

Format for Verbal Coordination

"Via (Route/Procedure), (Callsign), (Level - if different from standard), (Runway - if not duty runway)"

Class D Tower → Enroute/Approach (Next Call Coordination)

For all CTA/TMA departures, the next call must be made within 2 minutes of takeoff.

Radar Tower Coordination

Radar Tower → Approach (APP) Coordination

  • The Radar Tower must coordinate all departures with APP unless local Auto Release rules apply.
  • If Auto Release is overridden or suspended, the TWR must advise APP of any aircraft with a takeoff clearance.
Timing Requirement
  • Next call must be made within 2 minutes of takeoff unless Auto Release applies.
Phraseology Example: Cancelling Auto Release

APP → TWR:

"Cancel Auto Release."

TWR → APP:

"Cancel Auto Release, MAC477T released."

APP → TWR:

"MAC477T."

Approach (APP) → Radar Tower Coordination

  • Radar Towers must Next-coordinate all departures, unless Auto Release is active.
  • APP responds with any required lateral departure instructions (if needed for SID or departure procedures).
  • APP may also apply additional vertical restrictions or state "unrestricted."
Auto Release Suspension

If Auto Release must be cancelled due to weather, overflying aircraft, or runway configuration changes, APP must notify the ADC controller.

  • ADC will then respond with any aircraft that already have takeoff clearance.
Back to top