Darwin (YPDN)
Positions
| Name | Callsign | Frequency | Login ID |
|---|---|---|---|
| Darwin ADC | Darwin Tower | 133.100 | DN_TWR |
| Darwin SMC | Darwin Ground | 121.800 | DN_GND |
| Darwin ACD | Darwin Delivery | 126.800 | DN_DEL |
| Darwin ATIS | 128.250 | YPDN_ATIS |
Note
YPDN is a joint military/civil aerodrome and procedures can differ significantly to those at a civil aerodrome. Ensure you are familiar with the military controller skills necessary to provide a quality service.
Airspace
ADC owns the airspace within the DN CTR (SFC–A010). This airspace is designed to facilitate the processing of helicopter scenic flights and low-level helicopter circuits.
The CTR extends 7NM from the thresholds of runways 11 and 29 but does not including the Robertson Barracks transit zone.
ADC may request DN TCU (SFC–A020) from DN TCU to facilitate fixed-wing circuit operations:
a) Fixed-wing circuit operations are typically conducted at Delissaville (YDLV) due to high traffic density at Darwin
b) ADC may deny requests for circuits if IFR traffic may be unduly delayed
Manoeuvring Area
Standard Taxi Routes
Aircraft transiting to or from the Southern and Northern GA should follow the following standardised taxi routes:
a) Outbound via V1
b) Inbound via Y1
Traffic permitting, aircraft above 136,000kg MTOW shall be entered/exited for RWY 11/29 from taxiways B2, C3, D or E2 and backtracked as required.
Taxiway V has a passing bay, located adjacent to the ARFF section. The passing bay is the preferred location for engine run-ups, no longer than 3 minutes
Local Procedures
Marrara Coded Clearance
VFR aircraft arriving via LPT may be cleared for a visual approach via a 'Marrara Downwind' clearance. Aircraft that area cleared for a Marrara Downwind will track from LPT towards Marrara Stadium before turning to joing a left (Runway 11) or right (Runway 29) downwind.
Phraseology
DN ADC: "ZYX, cleared visual approach via Marrara Downwind, Runway 11"
VFR Departures
VFR aircraft are required to track via one of the published VFR Routes (as shown on the Darwin VTC). VFR routes shall be assigned based on the destination radial from Darwin, as per below:
| Outbound Radial | Route | Outbound | Inbound |
|---|---|---|---|
| 270-044 | VFR Route 1 | LPT JAC CGR |
CGR JAC LPT |
| 045-104 | VFR Route 2 | LPT JAC ADRM |
ADRM JAC LPT |
| 105-133 | VFR Route 3 | CHI LAD ADB |
ADB LAD CHI |
| 134-179 | VFR Route 4 | CHI LAD MTD |
MTD LAD CHI |
| 180-269 | VFR Route 5 | CHI BYNO |
BYNO CHI |
Tip
If a VFR aircraft has not planned via a VFR route as above, use the phraseology: “ABC, cleared amended route VFR route 1, climb to A020, squawk 4512”
Helicopter Operations
VFR helicopters are generally processed via the TALC HEAD Helicopter route. There is both an inbound and outbound route. This route is delivered as a coded clearance designed to separate helicopters from fixed-wing aircraft.
Departures
DN ACD will issue airways clearance for all helicopters, including those on a helicopter route. The helicopter route title should be recorded in the global ops field and the route waypoints should be added to the FDR route, as below.
| Route | Waypoints |
|---|---|
| TALC HEAD OUTBOUND | WOW TCH |
Phraseology
QRS: "Darwin Delivery, helicopter QRS, for the Talc Head outbound, request clearance"
DN ACD: "QRS, Darwin Delivery, cleared Talc Head outbound, squawk 0215, departure frequency 134.1"
QRS: "Cleared Talc Head outbound, squawk 0215, departure frequency 134.1, QRS"
Arrivals
VFR helicopters are generally processed via by the TALC HEAD Inbound route. IFR helicopters should conform to fixed wing ops and be processed via an appropriate runway.
Phraseology
QRS: "Darwin Tower, helicopter QRS, WSM, A005, received Tango, request Talc Head Inbound"
DN ADC: "QRS, Darwin Tower, cleared Talc Head Inbound, report at WOW."
QRS: "Cleared Talc Head Inbound, QRS"
Hospital Helipads
The Darwin CTR contains the helipad at the Royal Darwin Hospital (YXDH). This pad sits outside the manoeuvring area, so no takeoff or landing clearances should be issued. Instead, helicopters should be instructed to report airborne or report on the ground.
Runway Modes
Preferred Runway Modes
If winds are too great, single runway operations may be necessary (eg, Runway 11 for Arrivals and Departures). However, pending wind limitations (Crosswind <20kts, Tailwind <5kts), the following runway modes are to be used:
| Mode | Arrivals | Departures |
|---|---|---|
| 29AD36A | 29 & 36 | 29 |
| 29AD18A | 29 & 18 | 29 |
| 11AD36A | 11 & 36 | 11 |
| 11AD18A | 11 & 18 | 11 |
Special Runway Operations
LAHSO
Important
Due to its operational complexity, LAHSO must be authorised by a senior VATPAC staff member or a nominated event coordinator.
Very little benefit is achieved by running LAHSO without a flow controller and it is almost exclusively reserved for our busiest events.
Detailed procedures exist to ensure that controllers are aware of their responsibilities when performing LAHSO. See Controller Skills for more information.
Weather Conditions
LAHSO may only be used where the weather conditions meet the following minimum requirements:
| Element | Criteria |
|---|---|
| Cloud Ceiling | A030 or higher |
| Visibility | 8km or greater |
| Surface Condition | Dry |
| Windshear | None Reported |
Two simultaneous landings may be conducted by both day and night. A simultaneous takeoff and landing may only be conducted by day.
Runway Mode
The only approved LAHSO mode at YPDN is 29AD36A. Runway 36 is considered the active runway, while runway 29 is considered the passive runway.
Circuits
VFR aircraft that will operate only in ADCs airspace shall be assigned SSR code 0100
Circuit altitude will depend on the type of aircraft. Assign circuit altitudes for the following aircraft types:
| Aircraft | Altitude |
|---|---|
| Military Jet | A020 |
| Other Jet | A015 |
| Non-Jet | A010 |
| Helicopter | A010 |
SID Selection
Jet Aircraft planned via HELLI, JULIE, OCTOB or RUPEG shall be assigned the Procedural SID that terminates at the appropriate waypoint. Jet Aircraft not planned via any of these waypoints shall receive amended routing via the most appropriate SID terminus, unless the pilot indicates they are unable to accept a Procedural SID.
Non-Jet Aircraft planned via LAKUP, OLTAS, RUSKA or VANDI shall be assigned the Procedural SID that terminates at the appropriate waypoint.
a) Aircraft using Runway 18/36; or
b) Aircraft that cannot accept a Procedural SID
Shall be assigned the Radar SID.
Non-RNAV Departures
For non-RNAV approved IFR aircraft with a wake turbulence category of medium or greater, issue a Radar SID
For non-RNAV approved IFR aircraft with a wake turbulence category of light, issue a visual departure or Radar SID
ATIS
Operational Info
LAHSO
When LAHSO is in use, the ATIS OPR INFO shall include:
LAND AND HOLD SHORT OPERATIONS IN PROGRESS
Coordination
Auto Release
Next coordination is required from DN ADC to DN TCU for all aircraft.
The Standard Assignable Level from DN ADC to DN TCU is:
| Aircraft | Level |
|---|---|
| IFR aircraft assigned a Procedural SID | The lower of F180 and RFL |
| IFR aircraft not assigned a Procedural SID | The lower of A030 and RFL |
| VFR aircraft | The lower of A020 and RFL |
Departures Controller
When a TCU controller is online, aircraft shall be issued with a departure frequency during their airways clearance in accordance with the table below. If no TCU controllers are online, the most appropriate Enroute controller or Advisory frequency shall be issued.
| Runway | Via | Departure Frequency |
|---|---|---|
| 11 | All | 125.2 (DAE) |
| Runway | Via | Departure Frequency |
|---|---|---|
| 18 | East | 125.2 (DAE) |
| 18 | West | 134.1 (DAW) |
| Runway | Via | Departure Frequency |
|---|---|---|
| 29 | All | 134.1 (DAW) |
| Runway | Via | Departure Frequency |
|---|---|---|
| 36 | East | 125.2 (DAE) |
| 36 | West | 134.1 (DAW) |
Charts
Reference
Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of RAAF AIP page