VATSIM Türkiye Wiki

Istanbul Airport: Difference between revisions

Page Discussion

Istanbul Airport (view source)

Revision as of 19:52, 7 October 2026

14,927 bytes added ,  Yesterday at 19:52
m
→‎Image position correcte
 
(42 intermediate revisions by 4 users not shown)
Line 1: Line 1:
[[File:Istanbul TWR.jpg|thumb|Istanbul Airport ATC Tower]]
[[File:Istanbul TWR.jpg|thumb|Istanbul Airport ATC Tower]]
Istanbul Airport (IATA: IST, ICAO: LTFM) is the biggest airport in Turkiye. Located in north west of Istanbul, the airport is the busiest and biggest airport in Europe as per 2022 statistics of EuroControl<ref>https://www.eurocontrol.int/publication/eurocontrol-comprehensive-aviation-assessment-archive-2022</ref>. The airport has 5 runways, fuel farm, dedicated cargo area consisting of 5 apron (29 heavy stands), several warehouses and facilities (biggest one being Turkish Cargo followed by DHL and UPS), and is home to world's biggest airport terminal (under one roof).  
Istanbul Airport (IATA: IST, ICAO: LTFM) is the biggest airport in Turkiye. Located in north west of Istanbul, the airport is the busiest and biggest airport in Europe as per 2022 statistics of EuroControl<ref>https://www.eurocontrol.int/publication/eurocontrol-comprehensive-aviation-assessment-archive-2022</ref>. The airport has 6 runways<ref>Runway 09 is operational (since 18.09.2026)</ref>, fuel farm, dedicated cargo area consisting of 5 apron (29 heavy stands), several warehouses and facilities (biggest one being Turkish Cargo followed by DHL and UPS), and is home to world's biggest airport terminal (under one roof).  


The airport has not been completed. As of January 2023, only Phase 1a and 1b is finished. The final phase of the airport includes 8 runways, 2 terminals with 1 satellite terminal with up to 200 million passenger/year capacity.   
The airport has not been completed. As of September 2026, Phase 1a, 1b and 2 is finished. The final phase of the airport includes 8 runways, 2 terminals with 1 satellite terminal with up to 200 million passenger/year capacity.   
[[File:Istanbul Airport Current and Planned Layout.png|thumb|Istanbul Airport Current and Planned Layout]]
[[File:LTFM COMPLETE.png|thumb|Istanbul Airport Complete Plan]]


== Sceneries ==
== Sceneries ==
Line 17: Line 17:
|P3D v4/v5
|P3D v4/v5
|SceneryTR
|SceneryTR
|SceneryTR
|SimMarket
|https://secure.simmarket.com/scenerytr-stanbul-airport-ltfm.phtml
|https://secure.simmarket.com/scenerytr-stanbul-airport-ltfm.phtml
|-
|-
|X-Plane
|X-Plane 11
|SceneryTR
|SceneryTR/SimPort Team
|Aerosoft
|Aerosoft
|https://secure.simmarket.com/aerosoft-airport-istanbul-x-plane-11.phtml
|https://secure.simmarket.com/aerosoft-airport-istanbul-x-plane-11.phtml
|-
|-
|MSFS 2020
|X-Plane 12
|SceneryTR
|Aerosoft
|Aerosoft
|https://store.x-plane.org/Airport-Istanbul-XP_p_1443.html
|-
|Microsoft Flight Simulator 2020
|SceneryTR
|SceneryTR
|SimMarket
|Can be bought from MarketPlace
|Can be bought from MarketPlace
OR
OR
https://secure.simmarket.com/scenerytr-istanbul-airport-ltfm_msfs.phtml
https://secure.simmarket.com/scenerytr-istanbul-airport-ltfm_msfs.phtml
|-
|Microsoft Flight Simulator 2024
|SceneryTR
|SimMarket
|https://secure.simmarket.com/scenerytr-istanbul-airport-ltfm_msfs-(de_16986).phtml
|}
|}


Line 43: Line 53:
|-
|-
|FSX/P3D
|FSX/P3D
|Hakan Daghan, Kamil Uzun, Erman Gokman Pilicoglu, Muhtesem Firtina Ozcinar
|Hakan Dağhan, Kamil Uzun, Erman Gökman Piliçoğlu, Muhteşem Fırtına Özçınar
|Turkish Virtual
|Turkish Virtual
|https://turkishvirtual.com/turkishvirtual_LTFM_scenerys.asp
|https://turkishvirtual.com/turkishvirtual_LTFM_scenerys.asp
|-
|-
|X-Plane
|X-Plane 11
|Mali Oguducu, Hayri Buberci, Kamil Uzun, Muhtesem Firtina Ozcinar
|Mali Öğüdücü, Hayri Büberci, Kamil Uzun, Muhteşem Fırtına Özçınar
|Turkish Virtual
|Turkish Virtual
|https://turkishvirtual.com/turkishvirtual_LTFM_scenerys.asp
|https://turkishvirtual.com/turkishvirtual_LTFM_scenerys.asp
|-
|-
|MSFS 2020
|Microsoft Flight Simulator 2020
|Hayri Buberci, Mali Oguducu, Kamil UZUN, M Firtina Ozcinar
|Hayri Büberci, Mali Öğüdücü, Kamil Uzun, Muhteşem Fırtına Özçınar
|Turkish Virtual
|Turkish Virtual
|https://turkishvirtual.com/turkishvirtual_LTFM_scenerys.asp
|https://turkishvirtual.com/turkishvirtual_LTFM_scenerys.asp
|}
|}
== Preferential Runway System (PRS) ==
The term “Preferential RWY System (PRS)” shall be used to indicate the runway that, at a particular time, is considered by the ATC unit to be the most suitable for use by the aircraft expected to land at or take-off from the aerodrome, by taking into consideration aircraft performance, surface wind speed and its components. PRS Operations contribute to the optimum use of airspace and aerodrome capacity.<blockquote><big>The Preferential Runways in Istanbul Airport (LTFM) are north configuration runways (34L/R & 35L/R & 36)</big></blockquote>
{| class="wikitable"
!RWYCC (Runway Condition Code)
!Tail Wind Component (max)
|-
|RWYCC 6/6/6
(dry, maximum braking)
|10 KT (included)
|-
|When RWYCC is reported at least 5 for any each runway third
(worse than dry, low braking)
|5 KT (included)
|}
# In the PRS operations, the above wind criteria depending on the runway surface condition shall be applied.
# During the PRS operations, ATC unit takes into account the ground wind, traffic situation, local meteorological conditions, environmental restrictions, technical infrastructure, noise abatement, etc.
# PRS operations will not be available under the following circumstances:
#* The instrument approach/departure procedures available for the preferred RWY(s) are not convenient for landing and/ or take-off operations under the existing meteorological conditions
#* When the preferred RWY(s) are '''dry''' (RWYCC<ref>Runway Condition Code</ref> 6/6/6), '''the tail wind component is greater than 10 Kt''',
#* When RWYCC is reported at least 5 for any each the preferred RWY(s) third, the tail wind component is greater than 5 Kt,
#* When RWYCC is reported at least 5 for any each the preferred RWY(s) third, there is a NOTAM/equivalent information (which may be included in the RCR) stating that the runway is slippery, ATIS announcement when PRS Operations are in progress shall be; “Preferential Runway Operations are in Progress”.
#* RWYCC is reported 4 or less any each the preferred RWY(s) third,
#* Meteorological conditions such as heavy rainfall, thunderstorm or wind-shear has been reported on the approach or climb path of the preferred RWY(s),
#* Low visibility operations are in progress.
# ATIS announcement when PRS Operations are in progress shall be; “Preferential Runway Operations are in Progress”.
# Pilots unable to comply with PRS Operations shall notify the relevant ATC unit at the time of requesting start-up clearance, at the first contact or 20 minutes in advance of the ETA (which is earlier).


== Arrival Procedures ==
== Arrival Procedures ==
Istanbul Airport is located within Yesilkoy TMA (Terminal Manoeuvring Area). Yesilkoy TMA covers Istanbul Airport (LTFM), Sabiha Gokcen Airport (LTFJ), Ataturk Airport (LTBA), Samandira Airbase (LTBX), Corlu Ataturk Airport (LTBU), Hezarfen Municipal Airport (LTBW), Cengiz Topel Airport (LTBQ), Canakkale Airport (LTBH), Bursa Yunuseli Airport (LTBE) and Bursa Yenisehir Airport (LTBQ).


Istanbul Airport utilizes RNAV in all of its procedures. In addition, P-RNAV (''Precision-Area Navigation, RNP1'') capability is required. If unable, pilot '''must''' inform the controller so that aircraft can be given radar vectors to final. Arrival into Istanbul Airport might seem complicated to some pilots however it is actually very simple. LTFM STARs utilize PMS (Point Merge System) for efficient airspace control, separation, and to control traffic flow within Yesilkoy TMA. All STARs utilize idle descent philosophy until PMS entry. These point merge systems act as an arc of a circle and ease air traffic control.
=== Introduction ===
Istanbul Airport is located within Istanbul TMA (Terminal Manoeuvring Area). Istanbul TMA covers Istanbul Airport (LTFM), Sabiha Gokcen Airport (LTFJ), Ataturk Airport (LTBA), Samandira Airbase (LTBX), Corlu Ataturk Airport (LTBU), Hezarfen Municipal Airport (LTBW), Cengiz Topel Airport (LTBQ), Bursa Yunuseli Airport (LTBE) and Bursa Yenisehir Airport (LTBR). There are several more airports within the TMA however they are so small and not known that they are never used in VATSIM.
 
Istanbul Airport utilizes RNAV in all of its STAR procedures. In addition, P-RNAV (''Precision-Area Navigation, RNP1'') capability is required. If unable, pilot '''must''' inform the controller so that aircraft can be given radar vectors to final. Arrival into Istanbul Airport might seem complicated to some pilots however it is actually very simple. LTFM STARs utilize PMS (Point Merge System) for efficient airspace control, separation, and to control traffic flow within Yesilkoy TMA. All STARs utilize idle descent philosophy until PMS entry. These point merge systems act as an arc of a circle and ease air traffic control.
 
Important things to keep in mind:
 
* Vacating aircraft has priority at the intersection of the parallel taxiway. Which means, if you are vacating a RWY using rapid exit, the traffic on G, for example, should stop for you.
* After the runway is vacated, '''do not report vacated''' to TWR* and '''DO NOT STOP''' on rapid-exit taxiways.
* For runway 34L/16R, after landing cross 34R/16L, then join taxiway A to the south direction and contact GND.
* For runway 35R/17L, vacate to the C taxiway then contact GND without stopping.
* For runway 36/18, traffics should '''not''' vacate via G11 and G12 taxiways. Instead, pilots should use the rapid exit taxiways to G taxiway then contact GND.
<nowiki>*</nowiki>''unless LVP is in progress. Check next section for more details.''
 
=== Low Visibility Procedure ===
When LVP are in progress, every traffic '''must''' report "'''''Vacated'''''" to the TWR, as verbal confirmation from the traffic is mandatory and for the TWR to know the runway is available for the next traffic.


=== STARs ===
=== STARs ===
The STARs at Istanbul airport are designed to be ambiguous between the active runways. For instance, if northern config is active, RILEX2A STAR will end at '''IMREN''' waypoint, and '''IMREN''' is ''IAF'' (Initial Approach Fix) for all approach procedures for all northern runways. This means, whether you land at 34L, 35R or 36 (when north config is active), you still use the same STAR procedure for all runways. You can find the STAR designator table on the next page.
The STARs at Istanbul airport are designed to be ambiguous between the active runways. For instance, if northern config is active, RILEX1A STAR will end at '''IMREN''' waypoint, and '''IMREN''' is ''IAF'' (Initial Approach Fix) for all approach procedures for all northern runways. This means, whether you land at 34L, 35R or 36 (when north config is active), you still use the same STAR procedure for all runways. You can find the STAR designator table on the next page.
{| class="wikitable"
{| class="wikitable"
!Active Runway Configuration
!Active Runway Configuration
|-
|-
|''North'' Configuration uses the following STAR identifiers.
!North Config
|-
|
{| class="wikitable"
{| class="wikitable"
!Type
!Type
Line 74: Line 128:
|-
|-
|Standard
|Standard
(uses default PMS)
(uses default Arc)
|2A
|1A
|-
|Alternative*
(no Arc usage)
 
<nowiki>*</nowiki>''not applicable to RILEX, RIXEN, NUGBA and KANQO STARs''
|1C
|-
|Alternative*
(uses opposite Arc)
 
<nowiki>*</nowiki>''not applicable to INBET, SISPI, DRAMO and INBET STARs''
|1N
|-
|-
|Alternative*
|Alternative*
(uses opposite PMS)
(uses same Arc as 1A (if original Arc is West, still uses the West Arc) but from opposite entry)  


<nowiki>*</nowiki>''not applicable to DRAMO and INBET STARs''
<nowiki>*</nowiki>''only applicable to ERSEN and AYTEK STARs''
|2N
|1Q
|}
|}<nowiki>*</nowiki>Alternative: Only used by ATC.
<nowiki>*</nowiki>Alternative: Only used by ATC.
|-
!South Config
|-
|-
|''South'' Configuration uses the following STAR identifiers.
|
{| class="wikitable"
{| class="wikitable"
!Type
!Type
Line 91: Line 158:
|-
|-
|Standard
|Standard
(uses default PMS)
(uses default Arc)
|2B
|1B
|-
|-
|Alternative*
|Alternative*
(uses opposite PMS)  
(no Arc usage)  


<nowiki>*</nowiki>''not applicable to RILEX STARs''
<nowiki>*</nowiki>''not applicable to SISPI, INBET and DRAMO STARs''
|2P
|1M
|}
|-
<nowiki>*</nowiki>Alternative: Only used by ATC.
|Alternative*
(no Arc usage - opposite side of 1M arrival)
 
<nowiki>*</nowiki>''only applicable to RIXEN STAR''
|1W
|-
|Alternative*
(uses opposite Arc)
 
<nowiki>*</nowiki>''not applicable to AYTEK, RILEX, NUGBA and KANQO  STARs''
|1P
|-
|Alternative*
(uses same Arc as 1B (if original Arc is West, still uses the West Arc) but from opposite entry)
 
<nowiki>*</nowiki>''not applicable to RILEX, RIXEN, NUGBA, KANQO, SISPI, INBET and DRAMO STARs''
|1R
|}<nowiki>*</nowiki>Alternative: Only used by ATC.
|}
|}
As Istanbul Airport utilizes multiple configurations depending on traffic, weather, congestion, NOTAMs etc. You might be cleared to a different STAR compared to another traffic that is flying exactly the same route as you. Default designators for northern config (34/35/36) is 2A and default designator for southern configuration (16/17/18) is 2B. These STARs keep the traffic arriving west to use the west PMS and traffic arriving from east to use the east PMS. 2N and 2P STARs are designed to ease the workload of a PMS, by making the traffic to use the opposite PMS (traffic arriving from west to use the east PMS or to enter PMS from north instead of south at different altitude e.g).
As Istanbul Airport utilizes multiple configurations depending on traffic, weather, congestion, NOTAMs etc. You might be cleared to a different STAR compared to another traffic that is flying exactly the same route as you. Default designators for northern config (34/35/36) is 1A and default designator for southern configuration (16/17/18) is 1B. These STARs keep the traffic arriving west to use the west PMS and traffic arriving from east to use the east PMS. 1N and 1P STARs are designed to ease the workload of a PMS, by making the traffic to use the opposite PMS (traffic arriving from west to use the east PMS or to enter PMS from north instead of south at different altitude e.g).


==== North Config ====
==== North Config ====
<gallery>
<gallery>
File:ATPIX2A ERSEN-RIXEN2N.png|ATPIX 2A, ERSEN 2N and RIXEN 2N
File:LT AD 2 LTFM STAR 07 en.png|'''RIXEN 1N''', '''NUGBA 1D''', '''ERSEN 1Q''' and '''KANQO 1A''' arrivals
File:ATPIX2N.png| ATPIX 2N
File:LT AD 2 LTFM STAR 08 en.png|'''ERSEN 1C''', '''SISPI 1C''', '''ERSEN 1A''' and '''SISPI 1A''' arrivals
File:DRAMO2A INBET2A.png|DRAMO 2A and INBET 2A
File:LT AD 2 LTFM STAR 09 en.png|'''AYTEK 1Q''', '''DRAMO 1A''', '''INBET 1A''', '''AYTEK 1C''', '''DRAMO 1C''' and '''INBET 1C''' arrivals
File:ERSEN2A SISPI2A.png|ERSEN 2A and SISPI 2A
File:LT AD 2 LTFM STAR 10 en.png|'''AYTEK 1A''', '''RILEX 1A''' and '''RIXEN 1A''' arrivals
File:RILEX2A RIXEN2A.png|RILEX 2A and RIXEN 2A
File:LT AD 2 LTFM STAR 11 en.png|'''NUGBA 1N''' and '''KANQO 1N''' arrivals
File:RILEX2N.png|RILEX 2N
File:LT AD 2 LTFM STAR 12 en.png|'''AYTEK 1N''' and '''RILEX 1N''' arrivals
</gallery>
</gallery>


==== South Config ====
==== South Config ====
<gallery>
<gallery>
File:DRAMO-INBET2B 2P.png|DRAMO 2B, 2P and INBET 2B, 2P
File:LT AD 2 LTFM STAR 01 en.png|'''RIXEN 1P''', '''NUGBA 1E''', '''KANQO 1B''' and '''ERSEN 1R''' arrivals
File:ERSEN SISPI2B.png|ERSEN 2B and SISPI 2B
File:LT AD 2 LTFM STAR 02 en.png|'''ERSEN 1B''' and '''SISPI 1B''' arrivals
File:ERSEN SISPI2P.png|ERSEN 2P and SISPI 2P
File:LT AD 2 LTFM STAR 03 en.png|'''DRAMO 1P''' and '''INBET 1P''' arrivals
File:RILEX RIXEN2B.png|RILEX 2B and RIXEN 2B
File:LT AD 2 LTFM STAR 04 en.png|'''AYTEK 1R''', '''DRAMO 1B''' and '''INBET 1B''' arrivals
File:RIXEN2P ATPIX2B.png|RIXEN 2P and ATPIX 2B
File:LT AD 2 LTFM STAR 05 en.png|'''AYTEK 1B''', '''RILEX 1B''' and '''RIXEN 1B''' arrivals
</gallery>[[File:Image.png|thumb|ILS-X 35R Approach (showing both IMREN and SADIK transition)|335x335px]]
File:LT AD 2 LTFM STAR 06 en.png|'''ERSEN 1P''' and '''SISPI 1P''' arrivals
File:LT AD 2 LTFM STAR 13 en.png|'''AYTEK 1M''', '''RILEX 1M''' and '''RIXEN 1M''' arrivals
File:LT AD 2 LTFM STAR 14 en.png|'''RIXEN 1W''', '''NUGBA 1M''', '''KANQO 1M''' and '''ERSEN 1M''' arrivals
</gallery>
[[File:NORTH TRS1.png|thumb|335x335px|ILS-Z North Config Approach (showing IMREN, SADIK and NEWPE transitions)]]
 
=== Transitions and Approach Phase ===
=== Transitions and Approach Phase ===
As mentioned previously, Istanbul Airport utilizes Point-Merge System. Each PMS leads to last point of the STAR and '''the entry point of the approach transition''' . For northern config, IAF for west PMS is ''IMREN'', for east config it is ''SADIK''. For south config, IAF for west PMS is ''INSTA'' and for east PMS it is ''DIVDI''. '''Flying the correct transition is crucial and must'''. Each pilot is responsible for selecting the correct transition. This transition is '''NOT a STAR''' transition but transition for the approach procedure. There are different approach procedures and each has different transition phase (both laterally and vertically), go around procedure and used differently to streamline the independent parallel approach procedure . As a pilot, you must make sure you have programmed your FMS using the correct approach procedure and transition. '''If ATC clears the traffic for ILS-X 35R via IMREN transition, it is pilot's responsibility to fly ILS-X approach via IMREN transition'''. Since transitions are a must as they play a crucial role in the independent parallel approach procedure, pilot's must fly the transition both laterally and vertically at all times. If the transition is not selected correctly in the aircraft's FMS, the plane will fly directly to FAF, skipping the transition completely. This is not allowed for approach procedure into Istanbul as each approach procedure and transition is very different than one another, both laterally and vertically. You can see an example of how ILS-X and ILS-Z transition differs from the pictures below (you can see they are both laterally and vertically different).[[File:ILS-Z 35R TRANSITION2.png|thumb|ILS-Z Approach (showing both IMREN and SADIK transition)|335x335px]]
As mentioned previously, Istanbul Airport utilizes Point-Merge System. Each PMS leads to last point of the STAR and '''the entry point of the approach transition'''. For northern config, IAF for west PMS is ''IMREN'' and ''NEWPE'', for east config it is ''SADIK''. For south config, IAF for west PMS is ''INSTA'' and for east PMS it is ''ULQAL'' and ''GAZGE''. '''Flying the correct transition is crucial and must'''. Each pilot is responsible for selecting the correct transition. This transition is '''NOT a STAR''' transition but transition for the approach procedure. There are different approach procedures and each has different transition phase (both laterally and vertically), go  
[[File:SOUTH TRS1.png|thumb|335x335px|ILS-Z South Config Approach (showing INSTA, ULQAL and GAZGE transitions)]]around procedure and used differently to streamline the independent parallel approach procedure . As a pilot, you must make sure you have programmed your FMS using the correct approach procedure and transition. '''Each pilot is responsible for selecting and flying the correct transition whether ATC is online or not.''' Since transitions are a must as they play a crucial role in the independent parallel approach procedure, pilot's must fly the transition both laterally and vertically at all times. If the transition is not selected correctly in the aircraft's FMS, the plane will fly directly to FAF, skipping the transition completely. This is not allowed for approach procedure into Istanbul as each approach procedure and transition is very different than one another, both laterally and vertically.
== Ground Layout ==
== Ground Layout ==
Istanbul airport is on the list of biggest airports as per surface area, with staggering 76.5 million m<sup>2</sup> of land area. The airport has 5 runways, 34L/16R, 34R/16L, 35L/17R, 35R/17L and 36/18. Between RWYs 34 and 35, the main MRO and cargo area can be found. Between RWY 35 and 36, main passenger terminal and the stands can be found. Most gates and stands utilize MARS (Multiple Aircraft Ramp System). This increases the efficiency and gate usage significantly. With the MARS system, one gate can be shared by either 2 small to medium aircraft or 1 heavy (widebody) aircraft. In Istanbul Airport, MARS system uses L (as left) and R (as right) abbreviations for medium/split gates. For instance B4 gate is used by either 1 heavy aircraft or 2 medium aircrafts use B4L (Gate B 4 Left) and B4R (Gate B 4 Right).
Istanbul airport is on the list of biggest airports as per surface area, with staggering 76.5 million m<sup>2</sup> of land area. The airport has 5 runways, 34L/16R, 34R/16L, 35L/17R, 35R/17L and 36/18. Between RWYs 34 and 35, the main MRO and cargo area can be found. Between RWY 35 and 36, main passenger terminal and the stands can be found. Most gates and stands utilize MARS (Multiple Aircraft Ramp System). This increases the efficiency and gate usage significantly. With the MARS system, one gate can be shared by either 2 small to medium aircraft or 1 heavy (widebody) aircraft. In Istanbul Airport, MARS system uses L (as left) and R (as right) abbreviations for medium/split gates. For instance B4 gate is used by either 1 heavy aircraft or 2 medium aircrafts use B4L (Gate B 4 Left) and B4R (Gate B 4 Right).
[[File:LT AD 2 LTFM ADC en 2022-08-11.png|center|thumb|900x900px|LTFM Aerodrome Chart]]
[[File:LT AD 2 LTFM ADC en-1.png|center|thumb|900x900px|LTFM Aerodrome Chart<ref>September 2026</ref>]]


=== Main Passenger Terminal and Terminal Contact Apron ===
=== Main Passenger Terminal and Terminal Contact Apron ===
[[File:LT AD 2 LTFM PRKG 01 en 2022-08-11.png|thumb|Main Passenger Terminal and Terminal Contact Apron]]Passenger terminal at Istanbul Airport both house international and domestic traffic. The gates are split into piers and identifiers.  
[[File:LT AD 2 LTFM PRKG 01 en-1.png|thumb|Main Passenger Terminal and Terminal Contact Apron<ref>September 2026</ref>]]
Passenger terminal at Istanbul Airport both house international and domestic traffic. The gates are split into piers and identifiers.  
[[File:IST airport terminal layout departures.png|thumb|Terminal split showing international and domestic areas]]  
[[File:IST airport terminal layout departures.png|thumb|Terminal split showing international and domestic areas]]  
{| class="wikitable"
{| class="wikitable"
Line 157: Line 248:
|-
|-
|<big>F</big> Gates
|<big>F</big> Gates
|X*
|X
|F1
|
|-
|-
|<big>G</big> Gates
|<big>G</big> Gates
Line 182: Line 273:


==== F Pier ====
==== F Pier ====
F pier has mix of gates and flights. Gate F2 is medium only whereas gates F3, F4, F5, F6, F7, F8, F9, F12, F13 use MARS. Gates F14, F15, F16, F17, F18, F19 are heavy only gates. F1 gate uses MARS however is domestic only.[[File:LT AD 2 LTFM PRKG 02 en 2022-08-11.png|thumb|Apron 1 stands]]
F pier has mix of gates and flights. Gate F2 is medium only whereas gates F3, F4, F5, F6, F7, F8, F9, F12, F13 use MARS. Gates F14, F15, F16, F17, F18, F19 are heavy only gates. F1 gate uses MARS however is domestic only.[[File:LT AD 2 LTFM PRKG 02 en 2022-08-11.png|thumb|Apron 1 stands]]


Line 212: Line 302:
Each gate/stand in Istanbul Airport has published standard and alternative pushback procedure. These procedures increase efficiency of the aprons, gates, ground movements and streamline the traffic flow through out the airport. You might see abbreviations such as '''PSN'''. There are "Pushback Positions" which act as point where aircraft should pushback to.
Each gate/stand in Istanbul Airport has published standard and alternative pushback procedure. These procedures increase efficiency of the aprons, gates, ground movements and streamline the traffic flow through out the airport. You might see abbreviations such as '''PSN'''. There are "Pushback Positions" which act as point where aircraft should pushback to.
[[File:Pushback Procedures of A Pier - Standard.png|thumb|Pushback Procedures of A Pier - Standard]]
[[File:Pushback Procedures of A Pier - Standard.png|thumb|Pushback Procedures of A Pier - Standard]]
[[File:Pushback Procedures of Southwest Area - Alternative.png|thumb|Pushback Procedures of Southwest Area - Alternative]]
[[File:Pushback Procedures of Southwest Area - Alternative.png|thumb|Pushback Procedures of Southwest Area - Alternative|388x388px]]
[[File:Pushback Procedures for A9-A10-A11 Gates - Standard.png|thumb|Pushback Procedures for A9-A10-A11 Gates - Standard]]
[[File:Pushback Procedures for A9-A10-A11 Gates - Standard.png|thumb|Pushback Procedures for A9-A10-A11 Gates - Standard]]


Line 1,995: Line 2,085:


=== Terminal Area ===
=== Terminal Area ===
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.
[[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.]]


Line 2,025: Line 2,115:
| -3*
| -3*
|36/18
|36/18
|-
| -4*
|09
|}
|}
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. The different colors on the charts represent the taxi speed for that taxiway. Next section shows the taxi speeds for the airport.
As it can be seen, '''-1'''* routes are for runways 34L/16R, '''-2'''* routes are for 35/17 runways (L/R), '''-3'''* routes are for 36/18 runways, and '''-4'''* routes are for runway 09. The different colors on the charts represent the taxi speed for that taxiway. The next section shows the taxi speeds for the airport.


==== Arrival Taxi Routes ====
==== Arrival Taxi Routes ====
Line 2,038: Line 2,131:
|-
|-
|1A
|1A
|Arrival traffic vacating RWY 34L (Crossing the RWY 16L/34R is subject to Red Stop-Bars and ATC permission), shall use taxiways A, A3, E1, D3, E, N1 and F and hold position at clearance limit given by ATC.
|Arrival traffic vacating RWY 34L shall cross 34R and use taxiways A, A3, E1, D3, E and hold short of NW taxiway.
|-
|-
! colspan="2" |RWY 16R
! colspan="2" |RWY 16R
Line 2,046: Line 2,139:
|-
|-
|1A
|1A
|Arrival traffic vacating RWY 16R (Crossing the RWY 16L/34R is subject to Red Stop-Bars and ATC permission), shall use taxiways A, A3, E1, D3, E, N1 and F and hold position at clearance limit given by ATC.
|Arrival traffic vacating RWY 16R, shall cross 16L and use taxiways A, A3, E1, D3, E and hold short of NW taxiway.
|}
|}
<gallery widths="480" heights="666" style="text-align:center">
<gallery widths="480" heights="666" style="text-align:center">
File:LT AD 2 LTFM GMC 01 en 2022-03-24.png|RWY 34L
File:LT AD 2 LTFM GMC 01.png|<big>RWY 34L</big>
File:LT AD 2 LTFM GMC 02 en 2022-03-24.png|RWY 16R
File:LT AD 2 LTFM GMC 02.png|<big>RWY 16R</big>
</gallery>
</gallery>


Line 2,065: Line 2,158:
|-
|-
|2B
|2B
|Arrival traffic vacating RWY 35R, shall use taxiways C, N5, T9 and hold short of N2 taxiway.
|Arrival traffic vacating RWY 35R, shall use taxiways C, N5 and hold short of T9 taxiway.
|-
|-
|2C
|2C
|Arrival traffic vacating RWY 35R, shall use taxiways C, N1 and F and hold position at clearance limit given by ATC.
|Arrival traffic vacating RWY 35R, shall use taxiways C, N1 and hold short of T7 taxiway.
|-
|-
|2D
|2D
|Arrival traffic vacating RWY 35R, shall use taxiways C, N1, D and B and hold short of A3 taxiway.
|Arrival traffic vacating RWY 35R, shall use taxiways C, N1, D, B and hold short of A3 taxiway.
|-
|-
|2E
|2E
|Arrival traffic vacating RWY 35R, shall use taxiways C, N5, T9, N3 and F and hold position at clearance limit given by ATC.
|Arrival traffic vacating RWY 35R, shall use taxiways C, N5, T9, N3, F and hold position at clearance limit given by ATC.
|-
|-
! colspan="2" |RWY 17L
! colspan="2" |RWY 17L
Line 2,082: Line 2,175:
|-
|-
|2A
|2A
|Arrival traffic vacating RWY 17L, shall use taxiways C, N5 and T3 and hold short of N2 taxiway.
|Arrival traffic vacating RWY 17L, shall use taxiways C, N5, T3 and hold short of N2 taxiway.
|-
|-
|2B
|2B
|Arrival traffic vacating RWY 17L, shall use taxiways C, N5 and T9 and hold short of N2 taxiway.
|Arrival traffic vacating RWY 17L, shall use taxiways C, N5 and hold short of T9 taxiway.
|-
|-
|2C
|2C
|Arrival traffic vacating RWY 17L, shall use taxiways C, N1 and F and hold position at clearance limit given by ATC.
|Arrival traffic vacating RWY 17L, shall use taxiways C, N1 and hold short of T7 taxiway.
|-
|-
|2D
|2D
|Arrival traffic vacating RWY 17L, shall use taxiways C, N1, D and B and hold short of A3 taxiway.
|Arrival traffic vacating RWY 17L, shall use taxiways C, N1, D, B and hold short of A3 taxiway.
|-
|-
|2E
|2E
|Arrival traffic vacating RWY 17L, shall use taxiways C, N5, T9, N3 and F and hold position at clearance limit given by ATC.
|Arrival traffic vacating RWY 17L, shall use taxiways C, N5, T9, N3, F and hold position at clearance limit given by ATC.
|}
|}
<gallery widths="460" heights="688" style="text-align:center">
<gallery widths="460" heights="688" style="text-align:center">
Line 2,100: Line 2,193:
File:LT AD 2 LTFM GMC 04 en 2022-04-21.png|RWY 17L
File:LT AD 2 LTFM GMC 04 en 2022-04-21.png|RWY 17L
</gallery>
</gallery>
===== ARR 3A, ARR 3B, ARR 3C, ARR 3D =====
===== ARR 3A, ARR 3B, ARR 3C, ARR 3D, ARR 3E =====
{| class="wikitable"
{| class="wikitable"
! colspan="2" |RWY 36
! colspan="2" |RWY 36
Line 2,108: Line 2,201:
|-
|-
|3A
|3A
|Arrival traffic vacating RWY 36, shall use taxiways G, N4 and T3 and hold short of N2 taxiway
|Arrival traffic vacating RWY 36, shall use taxiways G, N4 and hold short of T3 taxiway.
|-
|-
|3B
|3B
|Arrival traffic vacating RWY 36, shall use taxiways G, N4 and T9 and hold short of N2 taxiway
|Arrival traffic vacating RWY 36, shall use taxiways G, N4, T9 and hold short of N2 taxiway.
|-
|-
|3C
|3C
|Arrival traffic vacating RWY 36, shall use taxiways G, N3 and F and hold position at clearance limit given by ATC
|Arrival traffic vacating RWY 36, shall use taxiways G, N2, F and hold position at clearance limit given by ATC.
|-
|-
|3D
|3D
|Arrival traffic vacating RWY 36, shall use taxiways G, N4, D and B and hold short of A3 taxiway
|Arrival traffic vacating RWY 36, shall use taxiways G, N4, D, B and hold short of A3 taxiway.
|-
|3E
|Arrival traffic vacating RWY 36, shall use taxiways G, N2 and hold short of T5 taxiway.
|}[[File:LT AD 2 LTFM GMC 05 en 2022-03-24.png|thumb|567x567px|Arrival taxi routes for RWY 36|center]]
|}[[File:LT AD 2 LTFM GMC 05 en 2022-03-24.png|thumb|567x567px|Arrival taxi routes for RWY 36|center]]


Line 2,128: Line 2,224:
|-
|-
|3F
|3F
|Arrival traffic vacating RWY 18, shall use taxiways G, N2, D and B and hold short of A3 taxiway
|Arrival traffic vacating RWY 18, shall use taxiways G, N2, D, B and hold short of A3 taxiway.
|-
|-
|3G
|3G
|Arrival traffic vacating RWY 18, shall use taxiways G and N4 and hold position at clearance limit given by ATC
|Arrival traffic vacating RWY 18, shall use taxiways G, N4 and hold position at clearance limit given by ATC.
|-
|-
|3H
|3H
|Arrival traffic vacating RWY 18, shall use taxiway F and hold position at clearance limit given by ATC
|Arrival traffic vacating RWY 18, shall use taxiway F and hold position at clearance limit given by ATC.
|}
|}
[[File:LT AD 2 LTFM GMC 06 en 2022-03-24.png|center|thumb|652x652px|Arrival taxi routes ARR 3F, ARR 3G, ARR 3H for RWY 18]]
[[File:LT AD 2 LTFM GMC 06 en 2022-03-24.png|center|thumb|652x652px|Arrival taxi routes ARR 3F, ARR 3G, ARR 3H for RWY 18]]
Line 2,140: Line 2,236:
==== Departure Taxi Routes ====
==== Departure Taxi Routes ====


===== DEP 1A =====
===== DEP 1A, DEP 1B =====
{| class="wikitable"
{| class="wikitable"
! colspan="2" |RWY 34L
! colspan="2" |RWY 34L & 34R
|-
|-
!Procedure
!Procedure
Line 2,148: Line 2,244:
|-
|-
|1A
|1A
|Departure traffic shall use G, N2, D, B, E1D, A1 and A1B taxiways and hold short of RWY 34R
|Departure traffic shall use G, N2, D, B, E1D, A1, A1B taxiways and hold short of RWY 34R.
|-
|1B
|Departure aircraft shall use G, N2, D, B, E1A, E1, A1, A1B taxiways and hold short of RWY 34R.
|}
|}
[[File:LT AD 2 LTFM GMC 07 en 2022-03-24.png|center|thumb|626x626px|DEP 1A taxi route for RWY 34L]]
[[File:LT AD 2 LTFM GMC 07 en 2022-03-24.png|center|thumb|626x626px|DEP 1A & DEP 1B taxi route for RWY 34L and 34R]]


===== DEP 1F =====
===== DEP 1F, DEP 1G =====
{| class="wikitable"
{| class="wikitable"
! colspan="2" |RWY 16R
! colspan="2" |RWY 16R & 16L
|-
|-
!Procedure
!Procedure
Line 2,160: Line 2,259:
|-
|-
|1F
|1F
|Departure traffic shall use G, N2, D, B, A7, A and A10B taxiways and hold short of RWY 16L
|Departure traffic shall use G, N2, D, B, A7, A, A10B taxiways and hold short of RWY 16L.
|-
|1G
|Departure aircraft shall use G, N2, D, B, E1D, A1, A, A10B taxiways and hold short of RWY 16L.
|}
|}
[[File:LT AD 2 LTFM GMC 08 en 2022-03-24.png|center|thumb|625x625px|DEP 1F taxi route for RWY 16R]]
[[File:LT AD 2 LTFM GMC 08 en 2022-03-24.png|center|thumb|625x625px|DEP 1F & DEP 1G taxi route for RWY 16R & 16L]]


===== DEP 2A, DEP 2B, DEP 2C =====
===== DEP 2A, DEP 2B, DEP 2D =====
{| class="wikitable"
{| class="wikitable"
! colspan="2" |RWY 35L
! colspan="2" |RWY 35L
Line 2,172: Line 2,274:
|-
|-
|2A
|2A
|Departure traffic shall use G, N2, D, B and B4A taxiways and hold short of RWY 35L
|Departure traffic shall use G, N2, D, B, B4A taxiways and hold short of RWY 35L.
|-
|-
|2B
|2B
|Departure traffic shall use G, N2, C and C5A taxiways and hold short of RWY 35R
|Departure aircraft shall use G, N2, C, C5A taxiways and hold short of RWY 35R.
|-
|-
|2C
|2C
|Departure traffic shall use E, D8, C1B and C1A taxiways and hold short of RWY 35R
|Departure aircraft shall use E, D11, C4B, C4A taxiways and hold short of RWY 35R.
|}
|}
<gallery widths="480" heights="665" style="text-align:center">
[[File:LT AD 2 LTFM GMC 09 en 2022-03-24.png|center|thumb|625x625px|DEP 2A, DEP 2B & DEP 2D taxi route for RWY 35L]]
File:LT AD 2 LTFM GMC 09 en 2022-03-24.png|DEP 2A and DEP 2B
File:LT AD 2 LTFM GMC 11 en 2022-03-24.png|DEP 2B and DEP 2C
</gallery>


===== DEP 2F, DEP 2G, DEP 2H =====
===== DEP 2B, DEP 2C, DEP 2D =====
{| class="wikitable"
{| class="wikitable"
! colspan="2" |RWY 17R
! colspan="2" |RWY 35R
|-
|-
!Procedure
!Procedure
!Description
!Description
|-
|-
|2F
|2B
|Departure traffic shall use G, N2, D, B and B9A taxiways and hold short of RWY 17R
|Departure aircraft shall use G, N2, C, C5A taxiways and hold short of RWY 35R.
|-
|-
|2G
|2C
|Departure traffic shall use G, N2, D, C7B, C and C11 taxiways and hold short of RWY 17L
|Departure aircrafts shall use E, D8, C1B, C1A taxiways and hold short of RWY 35R.
|-
|-
|2H
|2D
|Departure traffic shall use E, NW, D, C7B, C and C11 taxiways and hold short of RWY 17L
|Departure aircrafts shall use E, D11, C4B, C4A taxiways and hold short of RWY 35R.
|}
|}
<gallery widths="480" heights="665" style="text-align:center">
[[File:LT AD 2 LTFM GMC 11 en 2022-03-24.png|center|thumb|626x626px|DEP 2B, DEP 2C & DEP 2D taxi route for RWY 35R]]
File:LT AD 2 LTFM GMC 10 en 2022-03-24.png|DEP 2F and DEP 2G
File:LT AD 2 LTFM GMC 12 en 2022-03-24.png|DEP 2G and DEP 2H
</gallery>


===== DEP 3A, DEP 3B =====
===== DEP 2G, DEP 2H =====
{| class="wikitable"
{| class="wikitable"
! colspan="2" |RWY 36
! colspan="2" |RWY 17L
|-
!Procedure
!Description
|-
|2G
|Departure aircraft shall use G, N2, D, C, C11 taxiways and hold short of RWY 17L.
|-
|2H
|Departure aircraft shall use E, NW, D, C, C11 taxiways and hold short of RWY 17L.
|}
[[File:LT AD 2 LTFM GMC 12 en 2022-03-24.png|center|thumb|629x629px|DEP 2G & DEP 2H taxi route for RWY 17L]]
 
===== DEP 2F, DEP 2G =====
{| class="wikitable"
! colspan="2" |RWY 17R
|-
!Procedure
!Description
|-
|2F
|Departure aircraft shall use G, N2, D, B, B9A taxiways and hold short of RWY 17R.
|-
|2G
|Departure aircraft shall use G, N2, D, C, C11 taxiways and hold short of RWY 17L.
|}
[[File:LT AD 2 LTFM GMC 10 en 2022-03-24.png|center|thumb|626x626px|DEP 2F & DEP 2G taxi route for RWY 17R]]
 
===== DEP 3A, DEP 3B, DEP 3C =====
{| class="wikitable"
! colspan="2" |RWY 36
|-
|-
!Procedure
!Procedure
Line 2,214: Line 2,340:
|-
|-
|3A
|3A
|Departure traffic shall use E1, D3, E, N1, G and G7A taxiways and hold short of RWY 36
|Departure aircraft shall use E1, D3, E, N1, G, G7A taxiways and hold short of RWY 36.
|-
|-
|3B
|3B
|Departure traffic shall use G and G6A taxiways and hold short of RWY 36
|Departure aircraft shall use G, G6A taxiways and hold short of RWY 36.
|-
|3C
|Departure aircraft shall use F6, G6, G6A taxiways and hold short of RWY 36.
|}
|}
[[File:LT AD 2 LTFM GMC 13 en 2022-03-24.png|center|thumb|624x624px|DEP 3A and DEP 3B]]
[[File:LT AD 2 LTFM GMC 13 en 2022-03-24.png|center|thumb|624x624px|DEP 3A, DEP 3B & DEP 3C taxi route for RWY 36]]


===== DEP 3F, DEP 3G =====
===== DEP 3F, DEP 3G =====
Line 2,229: Line 2,358:
|-
|-
|3F
|3F
|Departure traffic shall use E1, D3, E, N1, G and G7A taxiways and hold short of RWY 36
|Departure traffic shall use E1, D3, E, N1, T2, N3, G, G17 taxiways and hold short of RWY 18.
|-
|-
|3G
|3G
|Departure traffic shall use G and G6A taxiways and hold short of RWY 36
|Departure aircraft shall use G, G17 taxiways and hold short of RWY 18.
|}
|}
[[File:LT AD 2 LTFM GMC 14 en 2022-03-24.png|center|thumb|625x625px|DEP 3F and DEP 3G]]
[[File:LT AD 2 LTFM GMC 14 en 2022-03-24.png|center|thumb|625x625px|DEP 3F and DEP 3G]]
[[File:Taxi Speeds.png|thumb|562x562px]]
 
===== DEP 4A =====
{| class="wikitable"
! colspan="2" |RWY 09
|-
!Procedure
!Description
|-
|4A
|Departure traffic shall use E1, D3, E, G1, G2B taxiways and hold short of RWY 09.
|}
[[File:LT AD 2 LTFM GMC 15 en-1.png|center|thumb|381x381px|DEP 4A]]


=== Taxi Speeds ===
=== Taxi Speeds ===
1) The speed of the aircraft on TWY turns is under the pilot in command.
Taxi speeds in Istanbul are determined based on the taxiway length, width, PCN and it's purpose. Pilots should always obey speed rules and follow the instructions. The ATC might warn the pilot if they are going faster than the allowed speed for that taxiway. In addition, under LVP (Low Visibility Procedures) conditions, it is up to the pilot in command to manage the speed and spacing between other ground traffic.
[[File:Taxi Speeds2026.png|center|thumb|639x639px|Chart showing taxi speed limits in LTFM]]
[[File:LTFM GND SECTOR LAYOUT.png|thumb|622x622px|Chart showing the layout and coverage of the sectors and their subsectors]]


2) The speed and the spacing with other aircraft while LVO conditions are under the responsibility of responsibility of t pilot in command.
=== Ground and Tower Sector Layout ===
 
=== TWR&GND FREQUENCY ALLOCATION ===
[[File:Fm freq 2.jpg|thumb|LTFM TWR&GND Frequency Allocation]]
{| class="wikitable"
{| class="wikitable"
|+
|+
!SECTOR
!Sector
!COVERS
!Coverage Area
!FREQUENCY
!Frequency
|-
! colspan="3" |Delivery
|-
|-
|LTFM_DEL
|LTFM_DEL
|N/A
|Entire airport
|121.700
|121.700
|-
|-
|LTFM_GND
! colspan="3" |Ground
|ALL GROUND SECTORS IF THEY ARE OFFLINE
|-
|124.725
|LTFM_W_GND
|West half of the airport (if the airport was split in half)
|126.300
|-
|LTFM_E_GND
|East half of the airport (if the airport was split in half)
|124.425
|-
|LTFM_TW_GND
|West half of Terminal Contact Apron
|121.625
|-
|LTFM_TE_GND
|East half of Terminal Contact Apron
|121.825
|-
! colspan="3" |Tower
|-
|LTFM_C_TWR
|RWYs 34L/16R and 34R/16L
|118.075
|-
|LTFM_W_TWR
|RWYs 35L/17R and 35R/17L
|131.100
|-
|LTFM_E_TWR
|RWY 36/18
|119.025
|}
 
== Departure Procedures ==
 
=== ATIS ===
Istanbul airport utilizes the double ATIS system, which is LTFM_A_ATIS and LTFM_D_ATIS. A ATIS is for arrival, and D is for departures. Depending on your flight, please make sure you listen and obtain the correct ATIS information. In addition, pilots '''must''' get the current ATIS information before calling for clearance. Moreover, in departure ATIS, the airborne frequency is published and every traffic '''''must''''' contact departure frequency immediately using the "''callsign'', ''sid & designator''" phraseology. For instance THY123 is a traffic departing from runway 36 and is on VADEN 1E SID, correct phraseology would be:<blockquote>xxx hello, Turkish 123, VADEN 1E.</blockquote>
 
=== PDC/DCL ===
As Istanbul airport is extremely busy, it is '''''MANDATORY''''' to use Departure Clearance Service (''DCL''). This is done by requesting your IFR clearance through CPDLC. If your aircraft does not natively support PDC/DCL (such as PMDG 737 NG3 on MSFS), you can use software such as '''''EasyCPDLC''''' to obtain your clearance. It is very easy to use and eliminates the congestion on the delivery frequency. Just grab your LOGON code from https://www.hoppie.nl/acars/system/register.html and request your clearance through ''Pre-Departure Clearance'' menu.
 
=== Planning Taxi Times ===
Taxi times in Istanbul Airport differ according to each apron and configuration. In addition, if you fly during an event or you were given a CTOT (Calculated Takeoff Time, slot), then it is, as the pilot, your responsibility to make sure you do not miss your slot. From ''terminal contact apron'', the average taxi time can be between 10-15 minutes and from ''cargo area'' 5-10 minutes depending on the configuration.
 
=== Low Visibility Procedure ===
When LVP is in progress pilots must:
 
# Taxi to CAT II/III holding point of the runways. This is a '''must''' as going pass these holding points interfere with ILS (specifically G/S) radio waves.
# (you can verify by asking the controller or checking ATIS), departure traffic '''must''' report ''"AIRBORNE"'' to tower. As visibility is very limited, TWR must know verbally that runway is cleared and available for the next traffic.
 
=== RECAT - LTFM ===
With the introduction of "Wake Turbulence Re-categorisation" in Turkish Airspace, the conventional wake turbulence categories has been re-defined. You can find more information from [https://www.skybrary.aero/articles/recat-wake-turbulence-re-categorisation Skybrary using this link].
{| class="wikitable"
!RECAT LTFM
!Follower
! Super Heavy
!Upper Heavy
!Lower Heavy
!Upper Medium
!Lower Medium
!Light
|-
!Leader
|
!A
!B
!C
!D
!E
!F
|-
! Super Heavy
!A
|*
|100s
|120s
|140s
|160s
|180s
|-
!Upper Heavy
!B
|*
|*
|*
|100s
|120s
|140s
|-
!Lower Heavy
!C
|*
|*
|*
|*
|100s
|120s
|-
!Upper Medium
!D
| *
|*
|*
|*
|*
|120s
|-
!Lower Medium
!E
|*
|*
|*
|*
|*
|100s
|-
|-
|LTFM_TWR
!Light
|ALL TOWER AND GROUND SECTORS IF THEY ARE OFFLINE
!F
|130.625
|*
|*
|*
|*
|*
|*
|}
|}
<nowiki>*</nowiki> = End of Runway Threshold or 45 seconds, whichever is '''later'''.
=== Multiple Line Up Procedures ===
To optimize runway utilization, line-up instructions may be issued by TWR to more than one aircraft at different points on the same runway, provided all that:
* Intersection take-off criteria is applied,
* Minimum visibility shall be more than 3000 meters,
* TWR shall continuously observe the multiple line-up positions and the relevant aircraft by visual reference,
* Pilot of the succeeding aircraft shall observe the preceding aircraft on the same RWY by visual reference,
* Pilots shall be advised of the position of any essential traffic information on the same runway,
* Aircraft involved in multiple line-ups on the same runway shall be on the same radio frequency,
* Pilots instructed to line-up shall read-back, the runway designator, the name of the intersection (if applicable) and the number in the departure sequence,
* Wake turbulence separation is applied.
Example phraseology:<blockquote>ATC: Line up and wait runway 35L, intersection B2, number 2 for departure, number one is B737 departing from B4B.


== STANDARD PROCEDURE FOR ALL PILOTS TO COMPLY ==
We request all pilots to comply these procedures in order to reduce the workload over the controllers


=== Departure Procedure ===
Aircraft: Line up and wait runway 35L, intersection B2, number 2.</blockquote>


==== Normal Procedure ====
=== Minimum Runway Occupancy Time ===
Before you request clearence you have to check ATIS. In ATIS script we publish '''<u>DEPARTURE FREQUENCY</u>'''. You need to write it down because when airborne pilots must immeadietly switch to <u>'''DEPARTURE'''</u> and report departure only '''<u>Callsign</u>''' and '''<u>SID</u>'''.
Minimum runway occupancy time is applied to all landing and departing aircraft:
[[File:LTFM ATIS.png|thumb]]
This procedure is not only for LTFM, if there is '''<u>DEPARTURE FREQUENCY</u>''' in '''<u>ATIS</u>''' any airport in Turkey, you need to do the same procedure.


==== Low Visibility Procedure ====
* To optimize the runway utilization, flight crews shall complete all check lists prior to line-up clearance and be ready for immediate take-off,
During the Low Visibility Procedure, before switch frequency to Departure, pilots '''<u>MUST</u>''' report '''AIRBORNE''' to tower, so Tower will know the runway is available for the next traffic.
* When aircraft is at the RWY holding point, pilots should commence line-up and take off roll immediately after take-off clearance is issued by ATC,
* When aircraft is already lined-up on RWY, pilots should commence take off roll immediately after take-off clearance is issued by ATC,
* <u>Pilots are expected to react take-off clearances within 10 seconds</u>,
* Pilots unable to comply with these requirements shall notify ATC before entering the RWY, otherwise ATC may instruct the aircraft to vacate the RWY and re-sequence to prevent excessive RWY occupation.


=== Arrival Procedure ===
=== SIDs ===
Istanbul Airport utilizes RNAV in all of its SID procedures. In addition, P-RNAV (''Precision-Area Navigation, RNP1'') capability is required. If unable, pilot '''must''' inform the controller as soon as possible so that aircraft can be given radar vectors after departure. In addition, if an aircraft was cleared and told to "maintain runway heading after departure" '''''the traffic must maintain the runway heading until further instructions.'''''
{| class="wikitable"
!Active Runway Configuration
|-
!North Config
|-
|During North Configuration, the following SIDs are used
{| class="wikitable"
!RWY
!Sabiha Gokcen (LTFJ) Config
!SID
|-
| rowspan="2" |34L/R
|North (06)
|1C
|-
|South (24)
|1Q*
|-
| rowspan="2" |35L/R
|North (06)
|1D
|-
|South (24)
|1R*
|-
| rowspan="2" |36
|North (06)
|1E
|-
|South (24)
|1S*
|}
''Check Sabiha Gokcen config to use correct SID procedure.''
 
<nowiki>*</nowiki>Only applicable to ''VICEN'' SID.
|-
!South Config
|-
|During South Configuration, the following SIDs are used
{| class="wikitable"
!RWY
!Sabiha Gokcen (LTFJ) Config
!SID
|-
| rowspan="2" |16L/R
|South (24)
|1F
|-
|North (06)
|1T*
|-
| rowspan="2" |17L/R
|South (24)
|1G
|-
|North (06)
|1U*
|-
| rowspan="2" |18
|South (24)
|1H
|-
|North (06)
|1V**
|}
''Check Sabiha Gokcen config to use correct SID procedure.''
 
<nowiki>*</nowiki>Only applicable to ''VICEN, RATVU'' SIDs.
 
<nowiki>**</nowiki>Only applicable to ''BARPE, IVGUS,'' ''VICEN, RATVU'' SIDs.
|-
!09 Departures
|-
|During 09 Departures Configuration, the following SIDs are used
{| class="wikitable"
!LTFM Arrival Config
!LTFJ Arrival Config
!SID
!
|-
|34L/35R/36 (North)
|North (06)
|1L
|STD
|-
|16R/17L/18 (South)
|South (24)
|1M
|STD
|-
|16R/17L/18 (South)
|North (06)
|1Y
|Opposite
|-
|34L/35R/36 (North)
|South (24)
|1Z
|Opposite
|}
''Please check Istanbul and Sabiha Gokcen arrival config to use''
 
''correct SID procedure.''
|}
As it can be seen from the table above, if the runway configuration used in Sabiha Gokcen Airport (LTFJ) is in reverse direction, special SID's are used.
 
==== North Config ====
<gallery widths="300" heights="200">
File:LT AD 2 LTFM SID 03 en-1.png|VADEN, TUDBU, REZOV, IBLAL 1C/1D/1E
File:LT AD 2 LTFM SID 04 en-1.png|MAKOL, EKAWE, VICEN 1C/1D/1E
File:LT AD 2 LTFM SID 05 en-1.png|BARPE, IVGUS, RATVU 1C/1D/1E
File:LT AD 2 LTFM SID 08 en-1.png|VICEN 1Q/1R/1S (Opposite Config w/ LTFJ)
</gallery>
 
==== South Config ====
<gallery widths="200" heights="280">
File:LT AD 2 LTFM SID 01 en-1.png|VADEN, TUDBU, IBLAL, BARPE, IVGUS, REZOV 1F/1G/1H
File:LT AD 2 LTFM SID 02 en-1.png|MAKOL, EKAWE, VICEN, RATVU 1F/1G/1H
File:LT AD 2 LTFM SID 06 en-1.png|VICEN & RATVU 1T/1U/1V
File:LT AD 2 LTFM SID 07 en-1.png|BARPE & IVGUS 1V
</gallery>
 
==== 09 Departures Config ====
<gallery widths="200" heights="280">
File:LT AD 2 LTFM SID 16 en-1.png|VADEN, TUDBU, IBLAL, BARPE, IVGUS, REZOV 1M
File:LT AD 2 LTFM SID 17 en-1.png|MAKOL, EKAWE, VICEN, RATVU 1M
File:LT AD 2 LTFM SID 18 en-1.png|VICEN, RATVU, BARPE, IVGUS 1Y (Opposite /w LTFJ)
File:LT AD 2 LTFM SID 19 en-1.png|VADEN, TUDBU, IBLAL, BARPE, IVGUS, REZOV 1L
File:LT AD 2 LTFM SID 20 en-1.png|MAKOL, EKAWE, VICEN, RATVU 1L
File:LT AD 2 LTFM SID 21 en-1.png|VICEN 1Z (Opposite /w LTFJ)
</gallery>


==== Normal Procedure ====
=== After Departure ===
After you vacate the runway, do not report vacated to Tower and '''<u>DO NOT STOP</u>''' on rapid-exit taxiways.


For runway 17L/35R & 18/36 after vacate continue on C (for 17L/35R) or G (for 18/36), continue taxi and contact ground when taxiing.
Every departure traffic '''''must''''' contact departure frequency immediately (if LVP is ''not'' in progress) using the "''callsign'' + ''sid & designator''" phraseology. For instance THY123 is a traffic departing from runway 36 and is on VADEN 1E SID, correct phraseology would be:<blockquote>xxx hello, Turkish 123, VADEN 1E.</blockquote>We hope you had fun flying to/from Istanbul Airport and we hope to see you again!


For runway 16R/34L, after vacate '''Stop''' before holding point of runway 16L/34R unless instructed to cross by ATC. If you are already cleared to cross runway 16L/34R, cross the runway and join taxiway A to the South!
== VFR in Istanbul TMA ==
You can find the VFR chart for Istanbul TMA showing the VFR routings, VFR waypoints, training areas below. If you have any questions regarding this, you can reach out to our Air Traffic, Operation and Navigation department by opening a ticket.
[[File:LT AD 2 LTFM VFR en-1.png|center|thumb|803x803px|Istanbul TMA VFR Chart]]


==== Low Visibility Procedure ====
== Feedback and Updates ==
During the Low Visibility Procedure, before switch to ground report '''VACATED''' to the Tower, so Tower will know the runway is available for the next traffic.<references />
If you have any feedback, comments, suggestions or improvements regarding this page, please [https://support.vatsim.tr/ open a ticket].
== References ==
<references />
[[Category:Airports]]
[[Category:Airports]]
{{DEFAULTSORT:LTFM}}
{{DEFAULTSORT:LTFM}}
__INDEX__
__INDEX__
Retrieved from "https://wiki.vatsim.tr/wiki/Special:MobileDiff/108...413"