approved
330
edits
Istanbul Airport: Difference between revisions
added remaining pushback procedures, added taxi routes information, added ARR 1A
m (→STARs: *Alternative note updated.) |
(added remaining pushback procedures, added taxi routes information, added ARR 1A) |
||
| Line 1,065: | Line 1,065: | ||
'''Face East''' | '''Face East''' | ||
|} | |} | ||
[[File:Terminal Contact Apron F Pier STD.png|thumb|Pushback procedures for F pier - standard]] | |||
[[File:Terminal Contact Apron F Pier ALT.png|thumb|Pushback procedures for F Pier - alternative]] | |||
=== Terminal Contact Apron | Northeast area === | === Terminal Contact Apron | Northeast area === | ||
| Line 1,331: | Line 1,333: | ||
'''Face East''' | '''Face East''' | ||
|} | |} | ||
[[File:Terminal Contact Apron G Pier STD.png|thumb|Pushback procedures for G pier - standard]] | |||
[[File:Terminal Contact Apron G Pier ALT.png|thumb|Pushback procedures for G pier - alternative]] | |||
[[File:Terminal Contact Apron G Pier2 STD.png|thumb|Pushback procedures for G9, G10, G11 gates - STD]] | |||
[[File:Terminal Contact Apron G Pier2 ALT.png|thumb|Pushback procedures for gates G9, G10, G11 - alternative]] | |||
=== Terminal Contact Apron | Southeast Area === | === Terminal Contact Apron | Southeast Area === | ||
| Line 1,995: | Line 2,001: | ||
Main terminal has predefined exits and routes. These predefined routes and directions help ease the traffic flow and ground movement in the airport. As it can be seen below from the picture, the | Main terminal has predefined exits and routes. These predefined routes and directions help ease the traffic flow and ground movement in the airport. As it can be seen below from the picture, the | ||
[[File:LTFM Terminal Exits.png|center|thumb|700x700px|Diagram showing Terminal apron exits and directions, taxiways to be used.]] | [[File:LTFM Terminal Exits.png|center|thumb|700x700px|Diagram showing Terminal apron exits and directions, taxiways to be used.]] | ||
=== Taxi Routes === | |||
Istanbul airport is a big airport. There are 12 ground sectors and with around 1,300 flights every day, ground frequencies get very congested. In addition, giving taxi instructions one by one to each aircraft increases the workload for air traffic controllers and creates more congestion in the frequency. To fix this problem, Istanbul Airport utilizes "Taxi Routes". These taxi routes are pre-defined, published (available in ALL charts) procedures to lower the workload of controllers and reduce clutter in the frequency. Example: | |||
A traffic (''THY123'') is pushing back from F12L would pushback facing south as per standard pushback procedure. Let's say the departure runway is 35L. The conversation on for the frequency would be in below fashion if old system was used:<blockquote>''THY123'': Istanbul ground, Turkish 123 requesting taxi. | |||
''ATC'': Turkish 123, taxi to holding point B4A, via TD, T7, N2, D, B. | |||
''THY123'': Taxi to holding point B4A via TD, T7, N2, D, B.</blockquote>The issue with this phraseology is that, first of all, it's very long. In an airport with 1,300/day traffic movement, this kind of phraseology would block the traffic. Moreover, if traffic or ATC make a mistake such as mispronouncing one letter or if traffic doesn't understand the taxi instructions, readback the instructions wrong, both ATC and pilot will further continue this conversation. This will create even more congestion and the frequency will be blocked. Let's look at the following example:<blockquote>''THY123'': Istanbul ground, Turkish 123 requesting taxi. | |||
''ATC'': Turkish 123, taxi via TD, T7, DEPARTURE 2A. | |||
''THY123:'' Taxi via TD, T7, DEPARTURE 2A.</blockquote>As it can be seen from the example, it's very easy and straightforward for everyone involved in this conversation. The instructions are precise and since these procedures are published in the charts, can be updated anytime by DHMI. | |||
Taxi route system uses the following designators which makes it easier to understand. | |||
{| class="wikitable" | |||
|+ | |||
!Designator | |||
!Runway | |||
|- | |||
| -1* | |||
|34L/16R | |||
|- | |||
| -2* | |||
|35L/17R, 35R/17L | |||
|- | |||
| -3* | |||
|36/18 | |||
|} | |||
As it can be seen, -1* routes are for runways 34L/16R, -2* routes are for 35/17 runways (L/R) and -3* routes are for 36/18 runway. | |||
==== Arrival Taxi Routes ==== | |||
===== ARR 1A ===== | |||
<gallery widths="480" heights="666"> | |||
File:LT AD 2 LTFM GMC 01 en 2022-03-24.png|RWY 34L | |||
File:LT AD 2 LTFM GMC 02 en 2022-03-24.png|RWY 16R | |||
</gallery> | |||
[[File:LT AD 2 LTFM GMC 02 en 2022-03-24.png|none|thumb|460x460px|Diagram showing ARR 1A taxi route for RWY 16R]] | |||
[[File:LT AD 2 LTFM GMC 01 en 2022-03-24.png|center|thumb|Diagram showing ARR 1A Taxi route for RWY 34L]] | |||
<references /> | <references /> | ||
[[Category:Airports]] | [[Category:Airports]] | ||