VATSIM Türkiye Wiki

Van Ferit Melen Airport: Difference between revisions

Page Discussion

Van Ferit Melen Airport (view source)

Revision as of 11:06, 16 October 2026

1,029 bytes removed ,  16 October
Correct frequencies to the TRvACC sector file instead of DHMİ AIP values.
(Correct frequencies to the TRvACC sector file instead of DHMİ AIP values.)
Line 66: Line 66:
* '''RNAV (GNSS) STARs for RWY 03''' (STAR-3 "1T" and STAR-4 "1A"). STAR-4 ('''BEYAZ 1A, ESENK 1A, ZELSU 1A''') ends at the FAF '''INKEL''' for the '''LOC only RWY 03''' approach (IAC-6), and '''Basic RNP 1''' is required between BEYAZ/ESENK/ZELSU and INKEL. STAR-3 ('''ZELSU 1T''', RNP 1 required) ends at '''MAPOD''', the IAF of the RNP RWY 03 approach (IAC-5).
* '''RNAV (GNSS) STARs for RWY 03''' (STAR-3 "1T" and STAR-4 "1A"). STAR-4 ('''BEYAZ 1A, ESENK 1A, ZELSU 1A''') ends at the FAF '''INKEL''' for the '''LOC only RWY 03''' approach (IAC-6), and '''Basic RNP 1''' is required between BEYAZ/ESENK/ZELSU and INKEL. STAR-3 ('''ZELSU 1T''', RNP 1 required) ends at '''MAPOD''', the IAF of the RNP RWY 03 approach (IAC-5).


Approach service is provided by '''Van Approach''' (122.700), or by '''Van Tower''' when required or when Van Approach transfers it (AD 2.17).
Approach service is provided by '''Van Tower''' on '''118.750'''. There is no separate approach position.


* '''Aircraft requesting the LOC only approach for RWY 03 must say so on first contact with Van Approach''', using the phrase ''"Request Loc-Only Approach RWY 03"'' (STAR-4 caution).
* '''Aircraft requesting the LOC only approach for RWY 03 must say so on first contact with Van Tower''', using the phrase ''"Request Loc-Only Approach RWY 03"'' (STAR-4 caution).
* The LOC only procedure is '''only flown by aircraft able to comply with the RNAV arrival on STAR-4''' (IAC-6 caution). Aircraft unable to comply with the RNP approach must tell Van Approach on first contact (IAC-5).
* The LOC only procedure is '''only flown by aircraft able to comply with the RNAV arrival on STAR-4''' (IAC-6 caution). Aircraft unable to comply with the RNP approach must tell Van Tower on first contact (IAC-5).
* '''Missed approaches due to bad weather:''' to avoid disturbing the traffic flow in the Van TMA, aircraft that abort the landing and pass over the runway because of bad weather must give '''priority to ATC instructions over the standard missed approach procedure''' (AD 2.22).
* '''Missed approaches due to bad weather:''' to avoid disturbing the traffic flow in the Van TMA, aircraft that abort the landing and pass over the runway because of bad weather must give '''priority to ATC instructions over the standard missed approach procedure''' (AD 2.22).
* '''Charter flights''' must obtain prior permission '''3 hours in advance''' from the aerodrome office on duty. All civil, charter and military IFR/VFR traffic planning to use the aerodrome must contact the Van Ferit Melen aerodrome authority or the ATC unit (AD 2.20).
* '''Charter flights''' must obtain prior permission '''3 hours in advance''' from the aerodrome office on duty. All civil, charter and military IFR/VFR traffic planning to use the aerodrome must contact the Van Ferit Melen aerodrome authority or the ATC unit (AD 2.20).
Line 642: Line 642:


=== Airborne ===
=== Airborne ===
Unless instructed otherwise, '''contact Van Approach on 122.700''' after take-off. Comply with all speed, altitude and climb gradient requirements on the SID, and tell ATC if you cannot fly the assigned SID. For the RNAV SIDs, aircraft unable to comply must say so to Van Tower on first contact.
There is no separate Van Approach position. Stay with '''Van Tower on 118.750''' until you are transferred to Ankara Control. Comply with all speed, altitude and climb gradient requirements on the SID, and tell ATC if you cannot fly the assigned SID. For the RNAV SIDs, aircraft unable to comply must say so to Van Tower on first contact.
<!-- EDITOR: the AIP does not say when to change to Approach or what to report on first contact. Add the TRvACC standard (e.g. callsign + SID designator). -->
<blockquote>
'''TWR:''' THY7AC, contact Van Approach 122.700, goodbye.
 
'''Pilot:''' Van Approach 122.700, THY7AC, goodbye.
 
'''Pilot:''' Van Approach, THY7AC, ESENK 1H.
 
'''APP:''' THY7AC, Van Approach, radar contact, climb FL190.
</blockquote>
<!-- EDITOR: "radar contact" and the climb level in this example are illustrative; AD 2 LTCI does not state the surveillance service available. -->


== After Departure ==
== After Departure ==
Line 678: Line 667:
|Van Tower
|Van Tower
|118.750
|118.750
|-
|Approach
|Van Approach
|122.700
|}
|}
AD 2.18 lists Tower and Approach together as '''VAN TWR/APP''' on 118.75 MHz, 122.7 MHz and 337.575 MHz (plus 121.5 / 243.0 MHz emergency); the charts assign '''118.750 to Tower''' and '''122.700 to Approach'''. Approach service is provided by Van Approach, or by Van Tower when required or when transferred by Van Approach (AD 2.17). Van Rescue Sub-center (SAR): 123.1 MHz, 282.8 MHz, 5680 kHz, 3023 kHz.
There is no separate Approach position. Approach service is provided by Van Tower on 118.750.
<!-- EDITOR: these are AIP (real-world) frequencies. Align with the TRvACC sector file / VATSIM positions before publishing. -->
 


== References ==
== References ==
Retrieved from "https://wiki.vatsim.tr/wiki/Special:MobileDiff/768"