approved
330
edits
Istanbul Airport: Difference between revisions
Added PDC/DCL section, updated ARR1A taxi-route, added more information to the arrival procedures section.
(Updated typo and few sentences for clarity) |
(Added PDC/DCL section, updated ARR1A taxi-route, added more information to the arrival procedures section.) |
||
| Line 67: | Line 67: | ||
Important things to keep in mind: | 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. | * 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. | ||
* For runway | * After the runway is vacated, '''do not report vacated''' to TWR* and '''DO NOT STOP''' on rapid-exit taxiways. | ||
* For runway | * For runway 34L/16R, after landing cross 34R/16L, then join taxiway A to the south direction and contact GND. | ||
* For runway | * 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 === | === 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, 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 2,049: | Line 2,052: | ||
|- | |- | ||
|1A | |1A | ||
|Arrival traffic vacating RWY 34L | |Arrival traffic vacating RWY 34L shall cross 34R and use taxiways A, A3, E1, D3, E, N1 and F and hold position at clearance limit given by ATC. | ||
|- | |- | ||
! colspan="2" |RWY 16R | ! colspan="2" |RWY 16R | ||
| Line 2,057: | Line 2,060: | ||
|- | |- | ||
|1A | |1A | ||
|Arrival traffic vacating RWY 16R | |Arrival traffic vacating RWY 16R, shall cross 16L and use taxiways A, A3, E1, D3, E, N1 and F and hold position at clearance limit given by ATC. | ||
|} | |} | ||
<gallery widths="480" heights="666" style="text-align:center"> | <gallery widths="480" heights="666" style="text-align:center"> | ||
| Line 2,316: | Line 2,319: | ||
=== ATIS === | === 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> | 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> | ||
=== 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 === | === Planning Taxi Times === | ||