¶ Dublin Area Control Operations Manual
NOT FOR REAL WORLD USE
Last Updated - August 2023
¶ Sectors
There are two Dublin Area Control sectors, ACC North and ACC South. The vertical and lateral limits of the sectors are shown below.
| Sector | IVAO Callsign | RTF Callsign | Frequency | FRA |
|---|---|---|---|---|
| ACC ALL | EIDW_CTR | Dublin Control | 132.580 | APC+ |
| ACC North | EIDW N CTR | Dublin Control | 132.580 | APC+ |
| ACC South | EIDW S CTR | Dublin Control | 120.755 | APC+ |
¶ Dublin ACC North
Dublin ACC North is responsible for departing and arriving aircraft north of a line which extends through the Runway 28L/ 10R centrelines.
¶ Dublin ACC South
Dublin ACC South is responsible for departing and arriving aircraft south of a line which extends through the Runway 28L/ 10R centrelines.
¶ Policy
- ACC ALL must be the first sector to be opened.
- ACC North is the next sector to be opened. Once ACC North is open, ACC ALL MUST close.
- Only when the ACC North sector is open, can ACC South be opened.
¶ Bandboxing
| Sector Bandbox | Sector Split |
|---|---|
| EIDW_CTR “Dublin ACC ALL” | EIDW N CTR “Dublin ACC North” |
| EIDW S CTR “Dublin ACC South” |
- Should ACC ALL be online when any other position is online, they shall relinquish responsibility for that respective position.
- ACC ALL and ACC North can not be open at the same time as both sectors share the same frequency
¶ Top-Down Coverage
Controllers shall provide Approach and Aerodrome Control to the airfields listed below when the appropriate positions are not online.
Should two overlapping sectors be online at the same time, the lower of the two sectors shall be responsible for provision of Approach and Aerodrome control at the airfields listed below.
A service may be provided to aircraft at airfields not listed below within the lateral confines of a sector. Non-radar units must only be controlled at Approach level only (i.e. APP).
| Sector ID | Aerodromes Controlled |
|---|---|
| ACC ALL | All aerodromes within the lateral limits of the Dublin TMA |
| ACC North | None |
| ACC South | None |
¶ Suspension of Top-Down Coverage
When high levels of traffic are forecast in a sector (for example during an event). Dublin Area Control may suspend the top down control coverage at airfields under their responsibility. In such cases, the lowest flight level at which a service can be provided must be notified by ATIS. For more information, please see /a231_policy.
¶ Responsibilities
- Control of Arriving aircraft until control is transferred to Approach Control.
- Aircraft approaching from outside of controlled airspace, place themselves under the control of Dublin Area Control until control is transferred to Approach Control or Aerodrome Control.
- Departing aircraft are taken over from Aerodrome Control until:
(a) they are transferred to Area Control; or
(b) they are clear of controlled airspace.
4. overflying aircraft within the relevant controlled airspace.
5. Provison of Flight Information Services outside of controlled airspace.
¶ Aerodromes
¶ Baldonnel/ Casement (EIMC)
¶ Departures
- IFR Departures from Baldonnel will climb initially to:
a) Altitude 4000ft if on an A/B Category SID.
b) FL90 if on a C/D Category SID.
¶ Arrivals
(1) Baldonnel arrivals are to follow the Standard RNAV arrivals for Dublin
(2) Arrivals are to descend to FL80/ FL70 depending on the STAR in accordance with the base of controlled airspace (CAS).
(3) Baldonnel arrivals should be transferred to Dublin Approach for Radar Vectoring.
¶ Dublin (EIDW)
¶ Departures
(1) IFR Departures from Dublin will climb initially to:
a) Altitude 4000ft - Category A/B SID.
b) FL90 - Category C/D SID.
(2) Once clear of conflict, and clear of Dublin Arrivals, Dublin Area Control can issue climb up to FL230 Eastbound/ FL240 Westbound.
(3) Area Control will transfer control of departures to the appropriate Shannon Area Control sector when approaching FL230/ FL240.
¶ Arrivals
On first contact with Dublin Area Control, Arrivals are to be given:
- Cleared Standard Arrival (STAR). And hold (if holding is expected).
- Dublin Runway in use.
- ATIS Code (If omitted)
Arrivals are to descend to FL80/ FL70 depending on the STAR in accordance with the base of controlled airspace (CAS).
¶ Routes
The following Lower Airways are delegated from Shannon Area Control to Dublin Area Control with vertical limits up to FL245:
L18; L149; L975; M17; M145; N34; P600; P620; Q36; Q37.
¶ SSR Codes
- Eurocontrol ORCAM codes (Automatically generated in Aurora) are issued to IFR aircraft.
- Dublin FIS Listening Squawk - 0401
¶ Delegated areas of ATS
Irish Sea Delegated Airspace
Holyhead CTA’s 10, 11, 12, 13, 14, 19, 20 and 21, are delegated from Scottish Control (PC) MTMA to Dublin ACC from DB (Declared Base) to FL245.
Irish Sea CTA’s 4, 5 and 6 are delegated from London AC to Dublin ACC from DB (Declared Base) to FL245.
¶ General
¶ Altimeter Setting
- Departing aircraft from aerodromes within the Dublin CTR/ CTA and TMA’s are to be given the Dublin QNH.
- Arriving aircraft below the transition level are to be given the Dublin QNH.
- Aircraft under a Flight Information Service should be given the Dublin QNH.
¶ Transition Altitude
5000 ft
¶ Transition Level
By ATC
¶ Separation Standards
¶ Horizontal Separation
Within the Dublin TMA: 3 NM
Outside the Dublin TMA: 5 NM
¶ Ensuring Horizontal Separation
Aircraft on their own navigation where horizontal separation is expected to be less than 15nm and no vertical separation exists should be given radar headings to ensure separation.
¶ Vertical Separation
Vertical separation exists when the vertical distance between aircraft is never less than the prescribed minimum. The vertical separation minima are:
Within the Dublin TMA: Below FL290 - 1000 ft
¶ Transfer of Control & Communications
Aircraft under the control of one sector are not permitted to penetrate the airspace of another sector unless:
- The aircraft is following a standing agreement; or
- Assumed Coordination is in effect; or
- Prior coordination has taken place
¶ Standing Agreement
Aircraft may enter the airspace of another sector without the need for individual coordination provided that:
- It is following a standard route on its own navigation, or on a specified track on a heading; and
- It has been cleared to or is at the standing agreement level before transfer of communication
Unless specified within the standing agreement, transfer of control will occur at the same time as transfer of communications provided that:
- The receiving sector continues the flight in the same general direction and does not reverse the vertical profile (e.g. climb a descending aircraft) or stop at an intermediate level within the confines of the offering sector
- Any potential conflicts with aircraft in the offering sectors airspace are resolved prior to transfer of communications
Unless the standing agreement states otherwise:
- Aircraft may be released for climb or descent within the confines of the offering sector
- Aircraft may be released for turns on own navigation such that the flight path is altered by not more than 45° left or right within the confines of the offering sector
- Aircraft transferred on a heading must be coordinated prior to issuing a heading change within the confines of the offering sector.
¶ Assumed Coordination
A sector may transfer traffic that is not covered by a standing agreement without coordination provided that:
- The aircraft is in the cruise at the RFL
- The aircraft is following the planned route, or on a heading within the confines of that route
- The aircraft is not an Opposite Direction Level