0% found this document useful (0 votes)
36 views

Heathrow RFE 2024 Controller Briefing

Uploaded by

tituan.mitard
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
36 views

Heathrow RFE 2024 Controller Briefing

Uploaded by

tituan.mitard
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

Version 1.

1 XU ATC Operations Department

Heathrow RFE
2024: Controller
Briefing
XU ATC Operations

JANUARY 2024
Introduction
This document has been created with the specific purpose and application
of temporary control measures in place by the United Kingdom and Ireland
MCD for the Heathrow RFE 2024 which shall take place between 1200-1800z,
Saturday 16th March 2024 and shall affect all arrivals and departures in
and out of London Heathrow Airport (EGLL/LHR) between the
aforementioned times.

The briefing is intended to improve the joint understanding of all key


stakeholders and therefore allow the most safe, efficient and expeditious
flow of traffic in and out of the XU Airspace during a time of anticipated
significant demand.

The briefing and temporary flow measures are designed to facilitate a


smooth and orderly flow of traffic without causing significant disruption.

2
Neighboring FIRs
Flow Temporary Restrictions
As always the XU FIR and TMA controllers will aim to keep a safe, efficient
and expeditious flow of traffic into the London, Scottish and Shannon
Airspaces.

The predicted schedule (if fully booked) will see 43 arrivals every hour
between 1200-1800z. We anticipate we could facilitate up to 50 arrivals per
hour if required. On this basis the following temporary procedures will apply

● - A release will be required by the first London Area controller on an


aircraft’s route for ANY non event traffic bound for London Heathrow
(EGLL)

● - Aircraft must NOT be given a Direct to any waypoint inside the XU


Airspace

● - Time separation of all aircraft arriving at the XU FIR entry points will
be at least 2 minutes. With “soft” speed control if necessary to
maintain this separation

● - For Clarity: please handoff pilots to report any constraints to the


next controller. E.g

”Speedbird 123, report your heading / cleared level / speed to London


Control 123.450”

3
● Due to the high amount of sectors online - If using Aurora we
recommend frequency is sent automatically in text on release for
“All” to avoid wrong frequency messages delaying RT.

● Coordination between London/Scottish/Shannon controllers will be


done in person in the Virtual ACC.

● For effective stability of the Aurora positioned stations in the VACC


please coordinate with our controllers using Text Only. Anticipate
small delays and avoid sending messages more than once. Do not
use Intercom a to communicate with our controllers as the
combination of lost RT time and inability to effectively monitor the
frequencies leads to delays.

We have also attached the FIR entry/exit map and superimposed the
agreed levels for entering the airspace from adjacent European sectors.
(Annex 1)

4
Within XU Airspace

VFR Aircraft
London Heathrow airport does not accept ANY VFR arriving, departing or
transiting traffic excluding Helicopter operations in the defined Heli lanes
system. Any users not familiar with the H Lanes will not be permitted to
transit Heathrow Class D airspace. Request for the use of the H lanes will be
to the FIN controller who will have ultimate discretion whether to accept the
traffic dependent on controller workload.

All aircraft, booked or not, that have filed to London Heathrow, MUST have a
route terminating at a current Standard Terminal Arrival [STAR](listed
below)

● ALESO
● BARMI
● LOGAN
● NUGRA
● FITBO
● HAZEL
● HON (Honiley VOR)
● OTMET
● ROXOG
● SIRIC

We will not accept traffic who file any “relief” STAR, these are for congestion
purposes to be assigned by ATC only.

5
● Traffic should plan to hold at the end of the STAR as published unless
otherwise directed by ATC.

● Due to the high amount of sectors online - If using Aurora we


recommend frequency is sent automatically in text on release for
“All” to avoid wrong frequency messages delaying RT.

● Coordination between London/Scottish/Shannon controllers will be


done in person in the Virtual ACC.

● For effective stability of the Aurora positioned stations in the VACC


please coordinate with our controllers using Text Only. Anticipate
small delays and avoid sending messages more than once. Do not
use Intercom to communicate between controllers as the
combination of lost RT time and inability to effectively monitor the
frequencies leads to delays.

TEAM Arrivals

Heathrow may, if available, use both runways for landing during high arrival
demand. These ‘TEAM’ arrivals usually can accept up to 6 aircraft on the
departure runway per hour.

Pilots can expect to hold so early descents at Pilots request are very much
discouraged.

6
Aircraft should be at or, if absolutely necessary, above the standard agreed
levels on entering XU Airspace. Deviation from the agreed levels will require
coordination.

XU controllers will ensure aircraft are climbed only to agreed levels on


departing our airspace unless coordinated with the next relevant sector.

Intention codes will be used for traffic to assist both our Area Controllers
and adjacent sectors so if “Direct to” is used within our airspace it will still
be abundantly clear to both our TMA/FIR positions and accompanying
positions where the aircraft will exit.

London Terminal Control


LTC will be split into defined sectors North (bandboxing NE & NW), South
(bandboxing SE & SW) and East. Tower Controllers for all LTMA airports
including non-event airports should be familiar with the handoff / prenote /
clearance request / release procedures and which controller is responsible
for their departing traffic. (Annex 4, 6)

Channel Islands TMA


EGTT_W_CTR (Annex 6) is responsible for the airspace in the Channel
Islands TMA underneath Brest Control up to FL195. There will be no
coordination with Brest Control as long as aircraft remain with the agreed
levels.

Coordination will be instigated to Brest FIR for aircraft leaving the Channel
Islands North into London Area Control for an earlier climb where necessary
and agreed.

7
Local Procedures
An up to date copy of all Area Sectors is attached for your reference.

It will be Statutory and Mandatory for all controllers controlling event traffic
from Home or at the vACC in Milton Keynes to have reviewed the Heathrow
Specific Moodle. There is no examination but the responsibility to remain
current and familiar resides with individuals.

Printed at the RFE location and Annexed within this document as required,
you can find a selection of resources to assist you for quick reference
including:

● Heathrow QuickView (Annex 2)


● Ground Movement Map (Annex 3)
● Live Stand Allocation board (vACC only)
● London Sectors Map (Annex 4)
● FIR Entry/Exit Points with agreed levels (Annex 1)
● All High and Low Sectors Callsigns (Annex 6)

Please ensure aircraft follow the semi-circular rule in their cleared level on
entering XU airspace. For aircraft flying north through French airspace even
levels are anticipated.

If you have any questions or would like to discuss further details please do
not hesitate to contact us prior to 8th March 2024.

With Respect

ATC Operations Department

United Kingdom and Ireland MCD

8
Briefing Ends

Annex 1

9
Annex 2

10
Annex 3

11
Annex 4

12
Annex 5

13
Annex 6

Position Callsign Notes Vertical Limit Frequency

EISN_CTR Shannon Shannon Area All DB-660


Control

EIDW_CTR Dublin Dublin Area DB-245 132.580


Control

EGPX_CTR Scottish Scottish Area All DB-660


Control

EGTT_S_CTR London London Area South DB-660 135.055


Control

EGTT_N_CTR London London Area North DB-660 128.130


Control

EGTT_W_CTR London London Area West DB-660 126.075


Control CTMA (DB-FL195)

EGTL_N_CTR London London Terminal North NW (DB-FL215) 121.280


Control NE (DB-FL245)

EGTL_S_CTR London London Terminal South SW (DB-FL175) 135.805


Control SE (DB-FL195)

EGTL_E_CTR London London Terminal East DB-FL245 129.605


Control

14
15

You might also like