VATSIM Türkiye Wiki

Istanbul Airport: Difference between revisions

Page Discussion

Istanbul Airport (view source)

Revision as of 05:47, 14 February 2023

5,910 bytes added ,  14 February 2023
Final push
(Added TWR and GND Sector map/layout)
(Final push)
Line 59: Line 59:


== Arrival Procedures ==
== Arrival Procedures ==
=== Introduction ===
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 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.
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:
* After the runway is vacated, '''do not report vacated''' to TWR and '''DO NOT STOP''' on rapid-exit taxiways.
* For runway 35R/17L, vacate to the C taxiway then contact ground when taxiing.
* For runway 36/18, vacate to the G taxiway then contact ground when taxiing.
* For runway 34L/16R, '''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 then contact the GND.
=== Low Visibility Procedure ===
During the LVP, 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, 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.
Line 123: Line 134:
</gallery>[[File:Image.png|thumb|ILS-X 35R Approach (showing both IMREN and SADIK transition)|335x335px]]
</gallery>[[File:Image.png|thumb|ILS-X 35R Approach (showing both IMREN and SADIK transition)|335x335px]]
=== 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'', 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]]
== 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).
Line 2,301: Line 2,312:
|}
|}


== STANDARD PROCEDURE FOR ALL PILOTS TO COMPLY ==
== Departure Procedures ==
We request all pilots to comply these procedures in order to reduce the workload over the controllers
 
=== 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 4E SID, correct phraseology would be:<blockquote>xxx hello, Turkish 123, 4E.</blockquote>
 
=== 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.
 
=== 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.
 
Aircraft: Line up and wait runway 35L, intersection B2, number 2.</blockquote>


=== Departure Procedure ===
=== Minimum Runway Occupancy Time ===
Minimum runway occupancy time is applied to all landing and departing aircraft:
 
* To optimize the runway utilization, flight crews shall complete all check lists prior to line-up clearance and be ready for immediate take-off,
* 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,
* Pilots are expected to react take-off clearances within 10 seconds,
* 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.
 
=== 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)
|4C
|-
|South (24)
|4Q*
|-
| rowspan="2" |35L/R
|North (06)
|4D
|-
|South (24)
|4R*
|-
| rowspan="2" |36
|North (06)
|4E
|-
|South (24)
|4S*
|}
''Check Sabiha Gokcen config to use correct SID procedure.''


==== Normal Procedure ====
<nowiki>*</nowiki>Only applicable to ''ASMAP'' SID.
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>'''.  
|-
[[File:LTFM ATIS.png|thumb]]
!South Config
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.
|-
|During South Configuration, the following SIDs are used
{| class="wikitable"
!RWY
!Sabiha Gokcen (LTFJ) Config
!SID
|-
| rowspan="2" |16L/R
|South (24)
|4F
|-
|North (06)
|4T*
|-
| rowspan="2" |17L/R
|South (24)
|4G
|-
|North (06)
|4U*
|-
| rowspan="2" |18
|South (24)
|4H
|-
|North (06)
|4V**
|}
''Check Sabiha Gokcen config to use correct SID procedure.''


==== Low Visibility Procedure ====
<nowiki>*</nowiki>Only applicable to ''ASMAP, RATVU'' SIDs.
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.


=== Arrival Procedure ===
<nowiki>**</nowiki>Only applicable to ''BARPE, IVGUS,'' ''ASMAP, RATVU'' SIDs.
|}
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 for ASMAP and RATVU (only for south config, for north config it's only for ASMAP).


==== Normal Procedure ====
==== North Config ====
After you vacate the runway, do not report vacated to Tower and '''<u>DO NOT STOP</u>''' on rapid-exit taxiways.
<gallery widths="300" heights="200">
File:LTFM SID VADEN TUDBU IBLAL 4C 4D 4E.png|VADEN, TUDBU, IBLAL 4C/4D/4E
File:LTFM SID BARPE IVGUS RATVU 4C 4D 4E.png|BARPE, IVGUS, RATVU 4C/4D/4E
File:LTFM SID MAKOL OSMEV ASMAP 4C 4D 4E.png|MAKOL, OSMEV, ASMAP 4C/4D/4E
File:LTFM SID ASMAP 4Q 4R 4S.png|ASMAP 4Q/4R/4S
</gallery>


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.
==== South Config ====
<gallery widths="200" heights="280">
File:LTFM SID VADEN TUDBU IBLAL BARPE IVGUS 4F.png|VADEN, TUDBU, IBLAL, IVGUS 4F
File:LTFM SID VADEN TUDBU IBLAL BARPE IVGUS 4G.png|VADEN, TUDBU, IBLAL, BARPE 4G
File:LTFM SID VADEN TUDBU IBLAL BARPE IVGUS 4H.png|VADEN, TUDBU, IBLAL, BARPE 4H
File:LTFM SID MAKOL OSMEV ASMAP RATVU 4F.png|MAKOL, OSMEV, ASMAP, RATVU 4F
File:LTFM SID MAKOL OSMEV ASMAP RATVU 4G.png|MAKOL OSMEV ASMAP RATVU 4G
File:LTFM SID MAKOL OSMEV ASMAP RATVU 4H.png|MAKOL OSMEV ASMAP RATVU 4F
File:LTFM SID ASMAP RATVU 4T 4U 4V.png|ASMAP, RATVU 4T/4U/4V
File:LTFM SID BARPE IVGUS 4V.png|BARPE, IVGUS 4V
</gallery>


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!
==== After Departure ====
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 4E SID, correct phraseology would be:<blockquote>xxx hello, Turkish 123, 4E.</blockquote>We hope you had fun flying to/from Istanbul Airport and we hope to see you again!


==== Low Visibility Procedure ====
== References ==
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 />
<references />
[[Category:Airports]]
[[Category:Airports]]
{{DEFAULTSORT:LTFM}}
{{DEFAULTSORT:LTFM}}
__INDEX__
__INDEX__
Trvacc
approved
330

edits

Retrieved from "https://wiki.vatsim.tr/wiki/Special:MobileDiff/128"