-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
54152a1
commit 39b76d6
Showing
3 changed files
with
120 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,5 +4,6 @@ nav: | |
- info.md | ||
- general_information.md | ||
- general_procedures.md | ||
- aor.md | ||
- arrivals.md | ||
- departures.md |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,98 @@ | ||
# 3. Designated areas of responsibility (AoR) | ||
## 3.1 General | ||
→ reduce workload during peak periods, the Doha TMA may be divided in→ a maximum of seven sec→rs. Each sec→r is assigned specific departures and arrivals and must adhere → standard level clearance and handoff procedures → maintain separation. | ||
|
||
## 3.2 Coordination between controllers | ||
Clearances for direct routing → waypoints, radar vec→rs before the downwind leg, or deviations from standard level clearances within designated controller Areas of Responsibility (AoRs) must not be issued without prior coordination between the relevant controllers. | ||
|
||
Handoffs between controllers must be conducted early enough → allow the next sec→r → facilitate continuous climb or descent, provided no conflicts exist with other traffic and separation is maintained. | ||
|
||
## 3.3 Sec→rs - Doha TMA | ||
| Logon | Sec→r | Radio Callsign | Area of Responsibility | | ||
|:----------:|:------------------:|:---------------:|:---------------------------------------------------------:| | ||
| DOH_R1_APP | Radar (North) | "DOHA RADAR" | Departure services for: ALSEM, ALVEN, LUBET, TULUB, VAXIN | | ||
| | | | Arrival services for: ALKAN, HAYYA, TOSNA, VEDED | | ||
| DOH_R2_APP | Radar (South) | "DOHA RADAR" | Departure Services for: BUNDU, DATRI, KUPRO, ULIKA | | ||
| | | | Arrival services provided for: LAEEB, ORLEK, TOSNA, TOVOX | | ||
| DOH_A1_APP | Approach (East) | "DOHA APPROACH" | Departures/Arrivals for runway 16L/34R | | ||
| DOH_A2_APP | Approach (West) | "DOHA APPROACH" | Departures/Arrivals for runways 16R/34L & 15/33 | | ||
| DOH_F1_APP | Director (East) | "DOHA DIRECTOR" | Final approach sequencing for runway 16L/34R | | ||
| DOH_F2_APP | Director (Central) | "DOHA DIRECTOR" | Final approach sequencing for runway 16R/34L | | ||
| DOH_F3_APP | Director (West) | "DOHA DIRECTOR" | Final approach sequencing for runway 15/33 | | ||
<figure markdown> | ||
<figcaption>Table 3-1: Doha TMA areas of responsibility</figcaption> | ||
</figure> | ||
|
||
## 3.4 Handoff procedure | ||
### 3.4.1 Doha TMA - Departures - Doha 15 / Hamad 16s | ||
| Departure Aerodrome | Runway | SID | Handoff procedure | | ||
|:-------------------:|:------:|:-------:|:--------------------------------------------:| | ||
| OTHH | 16L | ALSEM2M | Approach East → Radar North → U.A.E Radar | | ||
| OTHH | 16L | ALVEN2M | Approach East → Radar North → Doha Control | | ||
| OTHH | 16L | KUPRO1M | Approach East → Radar South → U.A.E Radar | | ||
| OTHH | 16L | LUBET1M | Approach East → Radar North → Bahrain Radar | | ||
| OTHH | 16L | LUBET1Y | Approach East → Radar North → Bahrain Radar | | ||
| OTHH | 16L | TULUB1M | Approach East → Radar North → Bahrain Radar | | ||
| OTHH | 16L | VAXIN2M | Approach East → Radar North → Doha Control | | ||
| OTHH | 16R | BUNDU2C | Approach West → Radar South → U.A.E Radar | | ||
| OTHH | 16R | DATRI1C | Approach West → Radar South → Jeddah Control | | ||
| OTHH | 16R | LUBET1C | Approach West → Radar North → Bahrain Radar | | ||
| OTHH | 16R | TULUB1C | Approach West → Radar North → Bahrain Radar | | ||
| OTHH | 16R | ULIKA1C | Approach West → Radar South → Jeddah Control | | ||
| OTBD | 15 | ALSEM3S | Approach West → Radar North → U.A.E Radar | | ||
| OTBD | 15 | ALVEN3S | Approach West → Radar North → Doha Control | | ||
| OTBD | 15 | BUNDU3S | Approach West → Radar South → U.A.E Radar | | ||
| OTBD | 15 | DATRI1S | Approach West → Radar South → Jeddah Control | | ||
| OTBD | 15 | KUPRO1S | Approach West → Radar South → U.A.E Radar | | ||
| OTBD | 15 | LUBET2S | Approach West → Radar North → Bahrain Radar | | ||
| OTBD | 15 | PATOM3S | Approach West → Radar North → Bahrain Radar | | ||
| OTBD | 15 | TULUB2S | Approach West → Radar North → Bahrain Radar | | ||
| OTBD | 15 | ULIKA1S | Approach West → Radar South → Jeddah Control | | ||
| OTBD | 15 | VAXIN3S | Approach West → Radar South → Doha Control | | ||
<figure markdown> | ||
<figcaption>Table 3-2: Doha TMA departure handoffs (OTBD 15/OTHH 16s)</figcaption> | ||
</figure> | ||
|
||
### 3.4.2 Doha TMA - Departures - Doha 33 / Hamad 34s | ||
| Departure Aerodrome | Runway | SID | Handoff procedure | | ||
|:-------------------:|:------:|:-------:|:--------------------------------------------:| | ||
| OTHH | 34L | DATRI1W | Approach West → Radar South → Jeddah Control | | ||
| OTHH | 34L | LUBET1A | Approach West → Radar North → Bahrain Radar | | ||
| OTHH | 34L | LUBET1W | Approach West → Radar North → Bahrain Radar | | ||
| OTHH | 34L | TULUB1A | Approach West → Radar North → Bahrain Radar | | ||
| OTHH | 34L | TULUB1W | Approach West → Radar North → Bahrain Radar | | ||
| OTHH | 34L | ULIKA1A | Approach West → Radar South → Jeddah Control | | ||
| OTHH | 34L | ULIKA1W | Approach West → Radar South → Jeddah Control | | ||
| OTHH | 34R | ALSEM2E | Approach East → Radar North → U.A.E Radar | | ||
| OTHH | 34R | ALVEN3E | Approach East → Radar North → Doha Control | | ||
| OTHH | 34R | BUNDU2E | Approach East → Radar South → U.A.E Radar | | ||
| OTHH | 34R | KUPRO1E | Approach East → Radar South → U.A.E Radar | | ||
| OTHH | 34R | LUBET2E | Approach East → Radar North → Bahrain Radar | | ||
| OTHH | 34R | LUBET2Z | Approach East → Radar North → Bahrain Radar | | ||
| OTHH | 34R | TULUB2E | Approach East → Radar North → Bahrain Radar | | ||
| OTHH | 34R | VAXIN2E | Approach East → Radar North → Doha Control | | ||
| OTBD | 33 | ALSEM3N | Approach West → Radar North → U.A.E Radar | | ||
| OTBD | 33 | ALVEN3N | Approach West → Radar North → Doha Control | | ||
| OTBD | 33 | BUNDU3N | Approach West → Radar South → U.A.E Radar | | ||
| OTBD | 33 | DATRI1N | Approach West → Radar South → Jeddah Control | | ||
| OTBD | 33 | KUPRO1N | Approach West → Radar South → U.A.E Radar | | ||
| OTBD | 33 | LUBET2N | Approach West → Radar North → Bahrain Radar | | ||
| OTBD | 33 | PATOM3N | Approach West → Radar North → Bahrain Radar | | ||
| OTBD | 33 | TULUB2N | Approach West → Radar North → Bahrain Radar | | ||
| OTBD | 33 | ULIKA1N | Approach West → Radar South → Bahrain Radar | | ||
| OTBD | 33 | VAXIN3N | Approach West → Radar North → Doha Control | | ||
<figure markdown> | ||
<figcaption>Table 3-3: Doha TMA departure handoffs (OTBD 33/OTHH 34s)</figcaption> | ||
</figure> | ||
|
||
### 3.4.3 Doha TMA - Arrivals - Doha 15 / Hamad 16s | ||
|
||
<figure markdown> | ||
<figcaption>Table 3-4: Doha TMA arrivals handoffs (OTBD 15/OTHH 16s)</figcaption> | ||
</figure> | ||
|
||
### 3.4.4 Doha TMA - Arrivals - Doha 33 / Hamad 34s | ||
|
||
<figure markdown> | ||
<figcaption>Table 3-5: Doha TMA arrivals handoffs (OTBD 33/OTHH 34s)</figcaption> | ||
</figure> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# 2. General Procedures | ||
## 2.1 General provisions | ||
The Approach Control Radar ensures surveillance-based separation services for arriving aircraft, as well as between arriving and departing aircraft, within the Doha Terminal Maneuvering Area (TMA). This encompasses Doha International Airport (DIA/OTBD), Hamad International Airport (DOH/OTHH), and Al-Udaid Airbase (OTBH). | ||
|
||
Additionally, radar control services are extended to aircraft operating within the boundaries of the Doha TMA, including those departing to or arriving from adjacent airspaces, as necessary. | ||
|
||
## 2.2 Separation minima | ||
### 2.2.1 Surveillance-based separation | ||
Unless specified otherwise in sections 2.2.2 and 4.1.1, aircraft operating within the Doha TMA must maintain a minimum horizontal separation of **3 NM**. If this cannot be achieved, a minimum vertical separation of **1,000 ft** must be applied. | ||
|
||
Controllers are required to employ suitable speed and altitude instructions, along with lateral profile adjustments, to ensure adherence to the prescribed separation minima. | ||
|
||
### 2.2.2 Wake turbulence separation | ||
The applicable Recategorisation Wake Turbulence Separation Minima (**RECAT**) must always be enforced for aircraft operating below **6,000 ft** under the following conditions: | ||
|
||
- When an aircraft is directly behind another at the same altitude or within **1,000 ft** below. | ||
- When both aircraft are utilizing the same runway or parallel runways separated by less than **760 meters**. | ||
- When an aircraft is crossing behind another at the same altitude or within **1,000 ft** below. | ||
|
||
## 2.3 Doha TMA runway configuration | ||
Due to the interactions between departure and arrival procedures, the runway direction in the Doha TMA is determined by the active runway configuration at Hamad (OTHH). Consequently, Doha (OTBD) and Al-Udaid (OTBH) must always operate in the same runway configuration as Hamad. |