NOT FOR REAL WORLD USE
Position | IVAN Callsign | RT Callsign | Frequency |
---|---|---|---|
AIR | EGNR_TWR | Hawarden Tower | 124.955 |
INT | EGNR_APP | Hawarden Radar | 120.055 |
Runway 22 is the preferred Runway when the tailwind component is 5 knots or less.
Departing aircraft are to be given the Hawarden QNH prior to take-off.
Arriving aircraft below the transition level are to be given the Hawarden QNH.
Aircraft entering the aerodrome traffic circuit are to operate on the Hawarden QFE.
Hawarden QFE = QNH - 2 hPa
5000 ft
By ATC.
CAT ll/lll Operations not available.
Low Visibility Procedures (LVPs) are in force when:
Hwarden has no established Standard Instrument Departures (SID’s). Instead, Hawarden departures should be cleared via the Standard Outbound Clearance (SOC). The Standard Outbound clearances can be found in the XU Quickview or UK AIP.
Departure clearance’s should be requested from Hawarden Radar (INT). AIR will then relay this clearance to the aircraft using the following phraseology:
”Aircraft Callsign, Controller Callsign, After Departure, “Cleared to join controlled airspace” (Standard Outbound Clearance), Squawk [SSR Code].
“BGA415F, Hawarden Tower, Cleared to Join controlled Airspace, REXAM 5 Departure, Squawk 2204”
Datalink clearances are not in use at Hawarden.
All departures from Hawarden except for departures remaining in the visual circuit require a release from Hawarden Radar (INT).
Due to the unique layout of Hawarden, Departures may require a full length backtrack of Runway 04 or 22.
“BGA415F, Via E1, Backtrack, Line up, Runway 22”
Wake turbulence separation minima on departure shall be applied by measuring airborne times between successive aircraft. Take-off clearance may be issued with an allowance for the anticipated take-off run on the runway; however, the airborne time interval shall reflect a difference of at least the required time separation. ATC does not have the discretion to reduce wake turbulence separation minima.
CAA Departure seperation minima must be applied between departing aircraft. Departure separation minima can also be found within the XU Quickview.
Leading | Following | Separation (Mins) |
---|---|---|
REXAM | REXAM | 2 |
REXAM | WAL | 1 |
WAL | WAL | 2 |
WAL | REXAM | 1 |
The release of the iniBuilds Airbus Beluga and Hawarden Scenery brings with it a fictional apron (The Victor Apron) that can accommodate 10 Airbus Belugas. IVAO will fully support iniBuilds with the implementation and use of this apron however it will not be noted on any charts produced by NATS, Navigraph and the like. However, the surface movement radar at Hawarden will include this apron.
The fictional apron is shown in dark red on the SMR, with the fictional holds displayed below.
It is expected that pilots using this scenery will be familiar with the victor apron, however, are under no obligation to use it. Controllers shall accommodate pilots to use whichever parking facility they wish to use, and the victor apron shall be used in the same way as any other.
Extreme care shall be taken when proceeding beyond V1 toward the Beluga Apron to ensure that aircraft are not proceeding on conflicting taxi routings as additional stopbars are scarce beyond this point.
The victor apron is not wide enough to facilitate the movement of two-way traffic, therefore if an aircraft will shortly require access to the apron in order to vacate the runway, then no aircraft shall push back until the arriving aircraft has made its approach, landing and has arrived on its stand.
Hawarden Radar (INT) is responsible for providing approach control services within 30nm of Hawarden airport.
Type | Code |
---|---|
Approach | 0431 - 0446 |
Frequency Monitoring Code | 4607 |
Conspicuity code* | 0430 |
*Conspicuity code used for non-radar/ procedural approaches.
Hold | Inbound course/ Direction | Minimum Level |
---|---|---|
KEGUN | 003/ Right | FL70/ MSL |
The wake turbulence separation minima in the XU Quickview shall be applied to aircraft on final approach when:
(1) an aircraft is operating directly behind another aircraft at the same altitude or less than 1,000 ft below; or
(2) an aircraft is crossing behind another aircraft, at the same altitude or less than 1,000 ft below;
Departing aircraft should state their Passing altitude on first contact to validate their Mode A/C transponder.
This altitude must be within +/- 200ft.
Beluga aircraft and IFR departures should be issued a Deconfliction service on first contact.
”BGA123, Hawarden Radar, Deconfliction Service, Climb now FL190”
When clear of conflict and local traffic Hawarden departures should be issued climb up to FL190 or Requested Cruise Level if lower. On entering controlled airspace, departures should be upgraded to a Radar Control Service. Before reaching FL190, level at FL190 or Requested cruise, departures should be transferred to Scottish Control.
Hawarden Airport is located within class G uncontrolled airspace. A Radio Mandatory Zone (RMZ) has been established to create a known traffic environment.
Circuits are flown to the north west of the aerodrome at different heights depending on the aircraft.
Arrivals: Route own navigation to the airfield and transferred to AIR when they have the airfield in sight. AIR will issue joining instructions to integrate into the visual circuit.
Departures: AIR will issue the following departure instructions:
“After departure, (Runway), Left/ Right turn out, VFR, Squawk 0431.”
Aircraft may be asked to route via the below VRP’s
Diagram - https://airspacesafety.com
For flight within the Radio Mandatory Zone (RMZ) aircraft commanders must comply with one of the following:
Establish satisfactory two-way RTF communication with and pass pertinent flight details to Hawarden Radar (120.055 MHz) prior to entering the RMZ. Maintain two-way communication with Hawarden Radar whilst operating inside the RMZ, unless otherwise instructed.
Display the Hawarden Frequency Monitoring Code (FMC) (*4607) with Mode C and monitor Hawarden Radar (120.055 MHz) prior to entering and whilst inside the RMZ. Pilots must maintain a listening watch and establish two-way RTF communication, if directed, whilst operating inside the RMZ.
Selection of the FMC does not imply receipt of an ATC service and pilots remain responsible for navigation, separation, terrain clearance, and are expected to remain outside of Controlled Airspace at all times.
When a pilot leaves the RMZ they should deselect the FMC.
Hawarden Radar provides UK Flight Information Services (UK FIS) up to a range of 30nm.
IFR Departures such as Airbus Beluga aircraft should be issued a Deconfliction service from Radar immediately on first contact.
VFR Departures should be issued a Basic service on first contact with Radar. If requested a Traffic Service may be provided.