Cairns TCU
Positions
| Name | ID | Callsign | Frequency | Login ID |
|---|---|---|---|---|
| Cairns Approach 1 | CS1 | Cairns Approach | 118.400 | CS_APP |
| Cairns Approach 2 | CS2 | Cairns Approach | 126.100 | CS-W_APP |
| Cairns Flow | CSF | CS_FMP |
Non-Standard Positions
Non-standard positions may only be used in accordance with VATPAC Air Traffic Services Policy.
Approval must be sought from the bolded parent position prior to opening a Non-Standard Position, unless NOTAMs indicate otherwise (eg, for events).
Airspace
The vertical limits of the CS TCU are SFC to F180.
Note
Due to terrain shielding, radar coverage may be limited below A025 southwest of the aerodrome.
CS ADC
CS ADC is responsible for the airspace within the CS CTR from SFC to A010.
Airspace Division
The divisions of the airspace between CS1 and CS2 change based on the runway mode. In either case, CS2 is responsible for the Class G airspace within the Cairns TMA.
Note
When both TCU positions are active, coordination requirements exist between CS1 and CS2 for aircraft transiting the boundary of CTA vertically or horizontally.
Departure/Arrival Procedures
Radar Departure Headings
There are no Standard Assignable Departure Headings at CS, and CS ADC will make a 'Next' call for each aircraft departing via the radar SID.
Due the high terrain to the west of the airport, aircraft departing via the CS (RADAR) SID should be issued an assigned heading within the ranges below.
| Runway | VMC below A030 | Otherwise |
|---|---|---|
| 15 | 350° to 030° | 030° |
| 33 | 330° to 070° | 330° |
Minimum IMC Levels
The lowest assignable levels in IMC for the following assigned headings are:
| Runway | Jet | Non-Jet |
|---|---|---|
| 15 | A030 |
A020, between 350° to 030° |
| 33 | A040, between 330° to 009°. A030, all other headings |
A040, between 330° to 009°. A020, between 010° to 060°. A024, between 061° to 070° |
Phraseology
UTY7242 is departing Runway 15 on the CS (RADAR) SID in VMC
CS ADC -> CS1: "Next, UTY7242, runway 15"
CS1 -> CS ADC: "UTY7424, runway 15, heading 350, unrestricted"
CS ADC -> CS1: "Heading 350, UTY7242"
Visual Approaches
When VMC exists below A030, aircraft of light & medium weight categories (B737/A320 and below) may be processed via a visual approach to either runway 15 or 33.
Creek Corridor
Aircraft for runway 15 will be cleared via the Victor STAR by enroute, which terminates on the Creek Corridor visual procedure (see YBCS DAP Noise Abatement Procedures chart). These aircraft should be cleared for a visual approach "via the Creek Corridor" and transferred to ADC prior to reaching the coastline.
Phraseology
RXA5474 is tracking via the NONUM Victor STAR for runway 15.
RXA5474: "RXA5474, visual"
CS TCU: "RXA5474, cleared visual approach tracking via the Creek Corridor"
RXA5474: "Cleared visual approach via the Creek Corridor, RXA5474"
Visual Base Runway 33
Aircraft for runway 33 may be cleared for a visual approach tracking via the STAR or localiser, or navigating visually through the valley to the south of the aerodrome.
Aircraft cleared via the KEEWI Victor STAR or otherwise approaching from the north shall be instructed to track for a visual right base and, once clear of departing traffic, assigned A020 visual. These aircraft will pass over the top of the CS CTR (owned by ADC), so further descent is not available. CS TCU must coordinate with ADC, then transfer them to ADC, who will issue visual approach clearance.
Phraseology
JCI is tracking inbound from the north at A050 and has reported visual.
CS1 -> CS ADC: "Via right base, JCI, will be assigned A020 visual"
CS ADC -> CS1: "A020 visual, JCI"
CS1: "JCI, track for a right base runway 33, descend to A020 visual"
JCI: "Track for right base runway 33, descend A020 visual, JCI"
CS1: "JCI, contact Cairns Tower on 124.9"
JCI: "124.9, JCI"
Flow
Local Knowledge
- Aircraft can be assigned the Xray or Victor STAR to reduce track miles
- Aircraft from the west/southwest can be assigned the TOTTY W STAR to reduce track miles
- With RWY 33 in use, aircraft via NONUM may be recleared DCT TOTTY for the TOTTY W STAR or DCT VEKBI for the HENDO A STAR
Flow Tables
The tables below give an estimated time in minutes from the Feeder Fix to the Threshold.
| STAR | Jets & DH8D | Non-Jets |
|---|---|---|
| CODIE A ANDOP transition AVDAN transition LOCKA transition OVLET transition PUNIT transition ZANEY transition |
14 12 13 13 14 14 |
15 14 14 14 16 15 |
| KASPI B/V ANDOP transition AVDAN transition LOCKA transition OVLET transition PUNIT transition ZANEY transition |
15 13 12 14 15 12 |
17 15 14 15 17 14 |
| NONUM A Feeder Fix: NONUM Feeder Fix: MUSEY Feeder Fix: NORMA |
9^ 15 18 |
11^ 17 20 |
| NONUM V Feeder Fix: NONUM Feeder Fix: MUSEY Feeder Fix: NORMA |
12^ 17 20 |
13^ 19 23 |
| NONUM W Feeder Fix: NONUM Feeder Fix: MUSEY Feeder Fix: NORMA |
9^ 14 17 |
10^ 16 19 |
| UPOLO A Feeder Fix: BARIA |
16 |
18 |
| UPOLO V Feeder Fix: BARIA |
15 |
17 |
| UPOLO W Feeder Fix: BARIA |
15 |
17 |
| STAR | Jets & DH8D | Non-Jets |
|---|---|---|
| HENDO A ANDOP transition BARIA transition ISNER transition NORMA transition OVLET transition PUNIT transition VEKBI transition |
21 12^ 12 14 22 20 24 |
24 14^ 14 15 25 23 27 |
| KEEWI A AVDAN transition LOCKA transition ZANEY transition |
23 22 22 |
26 26 25 |
| KEEWI V AVDAN transition LOCKA transition OVLET transition ZANEY transition |
16 15 16 14 |
18 17 18 16 |
| KEEWI X AVDAN transition LOCKA transition OVLET transition ZANEY transition |
18 17 19 17 |
21 20 21 19 |
| KEEWI Y AVDAN transition LOCKA transition OVLET transition |
22 22 21 |
25 25 24 |
| TOTTY W ANDOP transition ISNER transition NORMA transition PUNIT transition VEKBI transition |
19 13 13 19 22 |
22 15 15 21 25 |
Corrections
| Situation | Correction |
|---|---|
| Assigned a reduced speed | +1 min, except ^ |
| Over 40kt of head/tailwind component | +1 min for headwind -1 min for tailwind |
Assumptions
- Nil wind
- The feeder fix for all STARs is the assigned STAR transition waypoint (if applicable), otherwise:
- The feeder fixes for the NONUM STAR are MUSEY and NORMA (depending on inbound airway)
- The feeder fix for the UPOLO STAR is BARIA
Calculator
The following calculator will generate a landing time from a feeder fix ETA, or the reverse.
Coordination
Enroute
Departures
Voiceless for all aircraft:
- Tracking via a Procedural SID terminus; and
- Assigned the lower of
F180or theRFL
Note
Aircraft are not required to be tracking via the SID procedure, simply tracking via any of the terminus waypoints (regardless of departure airport or assigned SID) is sufficient to meet the criteria for voiceless coordination.
All other aircraft going to KEN(All) CTA must be Heads-up coordinated by CS TCU prior to the boundary.
Phraseology
CS2 -> KEN: "JST789, with your concurrence, will be assigned F160, for my separation with ANZ12"
KEN -> CS2: "JST789, concur F160"
Arrivals
Voiceless for all aircraft:
- With ADES YBCS; and
- Assigned a STAR; and
- Assigned the Standard Assignable level of:
- Radials 055° clockwise through to 355°:
A070 - Radials 355° clockwise to 055°:
A090
All other aircraft coming from KEN(All) CTA will be Heads-up coordinated to CS TCU.
CS ADC
Airspace
CS ADC is responsible for the airspace within the CS CTR from SFC to A010.
Departures
Next coordination is not required for aircraft that are:
- Departing from a runway nominated on the ATIS; and
- Assigned the standard assignable level; and
- Assigned a Procedural SID
All other aircraft require a 'Next' call to CS TCU.
The Standard Assignable level from CS ADC to CS TCU is:
| Aircraft | Level |
|---|---|
| All | The lower of A060 and RFL |
ACD to TCU
The controller assuming responsibility of CS ACD shall give heads-up coordination to the relevant CS TCU controller prior to the issue of the following clearances:
- VFR departures entering CS TCU CTA
- Aircraft using a runway not on the ATIS
Arrivals
Aircraft tracking via a visual right base to runway 33 must be coordinated with ADC (see Visual Base Runway 33). All other arriving aircraft do not require coordination.
CS TCU Internal
All aircraft transiting between internal CS TCU boundaries must be heads-up coordinated.
Phraseology
CS1 -> CS2: "via CS, ESQ"
CS2 -> CS1: "ESQ, A025"
Boundary coordination is not required between CS1 and CS2 for aircraft arriving or departing tracking via the 15/33 extended centreline.
Class G to CTA
Standard Radar to TCU coordination for each aircraft transiting between Class G and CTA (or vice versa).


