Difference between revisions of "Study Guide: Approach"

From VACC Austria DokuWiki
Jump to navigation Jump to search
 
(51 intermediate revisions by 11 users not shown)
Line 1: Line 1:
 +
'' Prev: [[Study Guide:Tower]] - Overview: [[Study Guide]] - Next: [[Study Guide:Radar]]''
 +
 
= General  =
 
= General  =
  
TMA controller includes approach and departure control services associated with a particular airport have the following main tasks:
+
TMA controller includes approach and departure control services associated with a particular airport have the following main tasks:  
  
#maintain an orderly flow of traffic
+
#maintain an orderly flow of traffic  
#provide separation service between aircraft
+
#provide separation service between aircraft  
 
#provide assistance to pilots<br>
 
#provide assistance to pilots<br>
  
Line 26: Line 28:
  
 
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs.  
 
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs.  
 +
 +
Weitere Informationen: [[Radar_Identification|Radar Identification]]
  
 
----
 
----
  
=== Position informations<br>  ===
+
=== Position information<br>  ===
  
 
Positionsinformationen dienen zur Orientierung des Piloten und können nach Möglichkeit an Hand von Navaids oder markanten Punkten, ähnlich den Pflichtmeldepunkten an den Piloten übermittelt werden. Die Positionsinformation unter Angabe markanter Punkte soll nur reaktiv angeboten werden, nicht jeder Pilot unter IFR ist mit den Örtlichkeiten vertraut, es empfiehlt sich daher grundsätzlich veröffentlichte Navaids oder einfache Kursangaben und Entfernung für die Übermittlung solcher Informationen zu nutzen.<br>  
 
Positionsinformationen dienen zur Orientierung des Piloten und können nach Möglichkeit an Hand von Navaids oder markanten Punkten, ähnlich den Pflichtmeldepunkten an den Piloten übermittelt werden. Die Positionsinformation unter Angabe markanter Punkte soll nur reaktiv angeboten werden, nicht jeder Pilot unter IFR ist mit den Örtlichkeiten vertraut, es empfiehlt sich daher grundsätzlich veröffentlichte Navaids oder einfache Kursangaben und Entfernung für die Übermittlung solcher Informationen zu nutzen.<br>  
Line 43: Line 47:
 
=== Usage of directs  ===
 
=== Usage of directs  ===
  
Piloten unter RNAV und Non-RNAV sind neben dem befolgen von Kursanweisungen auch in der Lage, ihr Flugzeug direkt zu einem gewünschten Wegpunkt zu navigieren und anschließend auf der ursprünglich geplanten Route weiterzufliegen. Die Anweisung zum fliegen eines directs ist für den Piloten nicht verbindlich, er darf dies jederzeit ohne Angabe von Gründen ablehnen. In Absprache mit benachbarten Flugverkehrskontrollstellen ist es auch möglich, directs über große Entfernungen und durch mehrere Flugsicherungssektoren anzubieten. Bei der Freigabe für den Direktflug zu einem Wegpunkt ist zu prüfen, ob der Pilot davon überhaupt einen Nutzen hat, ein Shortcut welcher den Flugweg des Flugzeugs lediglich um 2 Meilen verkürzt ist kein direct und keine Hilfe für den Piloten. Bei der Vergabe von Shortcuts besteht die Gefahr, dass man sich selbst sehr schnell den Luftraum zusperrt, besonders auf Flughäfen wie Innsbruck ist es riskant allen Flugzeugen den Direktflug zum IAF (RTT bzw. KTI&nbsp;NDB) zu erteilen. Ein Direct zu einen Punkt auf einer Transition ist übrigens die gleichzeitige Freigabe für die gesamte darauffolgende Wegstrecke der Transition, allerdings nicht des vertikalen Profils, gleiches gilt für einen Direct zu einem Punkt der STAR, so ist der Pilot freigegeben für die gesamte STAR bis zum IAF, nicht mehr nur bis zum clearance limit.<br>
+
Piloten unter RNAV und Non-RNAV sind neben dem befolgen von Kursanweisungen auch in der Lage, ihr Flugzeug direkt zu einem gewünschten Wegpunkt zu navigieren und anschließend auf der ursprünglich geplanten Route weiterzufliegen. Die Anweisung zum fliegen eines directs ist für den Piloten nicht verbindlich, er darf dies jederzeit ohne Angabe von Gründen ablehnen. In Absprache mit benachbarten Flugverkehrskontrollstellen ist es auch möglich, directs über große Entfernungen und durch mehrere Flugsicherungssektoren anzubieten. Bei der Freigabe für den Direktflug zu einem Wegpunkt ist zu prüfen, ob der Pilot davon überhaupt einen Nutzen hat, ein Shortcut welcher den Flugweg des Flugzeugs lediglich um 2 Meilen verkürzt ist kein direct und keine Hilfe für den Piloten. Bei der Vergabe von Shortcuts besteht die Gefahr, dass man sich selbst sehr schnell den Luftraum zusperrt, besonders auf Flughäfen wie Innsbruck ist es riskant allen Flugzeugen den Direktflug zum IAF (RTT bzw. KTI&nbsp;NDB) zu erteilen. Ein Direct zu einen Punkt auf einer Transition ist übrigens die gleichzeitige Freigabe für die gesamte darauffolgende Wegstrecke der Transition, allerdings nicht des vertikalen Profils, gleiches gilt für einen Direct zu einem Punkt der STAR, so ist der Pilot freigegeben für die gesamte STAR bis zum IAF, nicht mehr nur bis zum clearance limit.<br>  
 +
 
 +
----
 +
 
 +
= Separation  =
 +
 
 +
=== Vertical separation  ===
 +
 
 +
Vertical separation is obtained by requiring aircraft using prescribed altimeter setting procedures to operate at different levels to avoid lost of separation. The vertical separation minimum shall be 1000 feet below FL 410 in RVSM&nbsp;airspace or 2000 feet above FL290 in non-RVSM&nbsp;airspaces. To fly within RVSM an aircraft must be equipped with:
 +
 
 +
#2 independent altimeters
 +
#an autopilot witch must be able to hold an specific altitude
 +
#min. Mode C transponder
 +
 
 +
----
 +
 
 +
=== Lateral separation  ===
 +
 
 +
Lateral separation is also known as radar separation and shall be applied so that the distance between those portions of the intended routes for with the aircraft are to be laterally separated is never less than an established distance to account for navigational inaccuracies. Have a look into the wake turbulence separation to find the required distances for the lateral separation.
  
 
----
 
----
  
== the role of Approach Controllers ==
+
=== Wake turbulence separation ===
  
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.<br>
+
Wake turbulence is turbulence that forms behind an aircraft as it passes through the air. This turbulence includes various components, the most important of which are wingtip vortices and jetwash. Jetwash refers simply to the rapidly moving gases expelled from a jet engine; it is extremely turbulent, but of short duration. Wingtip vortices, on the other hand, are much more stable and can remain in the air for up to three minutes after the passage of an aircraft.  
  
*maintain an orderly flow of traffic<br>
+
===== Takeoff<br> =====
*provide a separation service between aircraft<br>
 
*provide assistance to pilots<br>
 
  
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. <br>There are some separation in your airspace:<br>
+
An aircraft of a lower wake vortex category must not be allowed to take off less than two minutes behind an aircraft of a higher wake vortex category. If the following aircraft does not start its take off roll from the same point as the preceding aircraft, this is increased to three minutes.  
  
*'''Vertical separation:''' should be at least RVSM 1000ft, Non-RVSM 2000ft. Austria uses RVSM (Reduced Vertical Seperation Minima). So you can use 1000ft up to FL410.<br>
+
===== Landing  =====
*'''Horizonal separation:''' The Minimum Horizontal Seperation depends on the radar equipment involved. APP Sectors work with a minimum of 3 nm, CTR Sectors use 5 nm.<br>
 
  
<br>  
+
{| style="width: 415px; height: 256px;" class="wikitable"
 +
|-
 +
! Preceding aircraft
 +
! Following aircraft
 +
! Minimum radar separation
 +
|-
 +
| rowspan="4" | Super
 +
| Super
 +
| 4 [[Nautical mile|NM]]
 +
|-
 +
| Heavy
 +
| 6 NM
 +
|-
 +
| Medium
 +
| 7 NM
 +
|-
 +
| Small
 +
| 8 NM
 +
|-
 +
| rowspan="3" | Heavy
 +
| Heavy
 +
| 4 NM
 +
|-
 +
| Medium
 +
| 5 NM
 +
|-
 +
| Small
 +
| 5 NM
 +
|-
 +
| Medium
 +
| Small
 +
|
 +
4 NM
 +
 
 +
|}
 +
 
 +
*Staying on or above leader's glide path<br>Incident data shows that the greatest potential for a wake vortex incident occurs when a light aircraft is turning from base to final behind a heavy aircraft flying a straight-in approach. Light aircraft pilots must use extreme caution and intercept their final approach path above or well behind the heavier aircraft's path. When a visual approach following a preceding aircraft is issued and accepted, the pilot is required to establish a safe landing interval behind the aircraft he was instructed to follow. The pilot is responsible for wake turbulence separation. Pilots must not decrease the separation that existed when the visual approach was issued unless they can remain on or above the flight path of the preceding aircraft.<br>
 +
 
 +
----
 +
 
 +
=== Separation with individual speeds<br>  ===
 +
 
 +
A controller may issue speed instructions within an aircraft operating limits. There are two possible ways to do this, either by using Indicated Airspeed (FL280 or below) or by specifying a Mach number (FL280 or above). Take notice of the minimum speed of the aircraft! Normally you are working with "minimum clean" (means the lowest speed an aircraft can maintain without using flaps or slats above FL100. The best way to gain separation between two aircraft is to advise an specific speed to the relevant aircraft.
 +
 
 +
For example:
 +
<pre>LOWW_APP: AUA14F, speed 220 knots indicated.
 +
AUA14F:      Speed 220 Knots, AUA14F.
 +
</pre>
 +
If the pilot reports "unable" ask the pilot witch speed would be suitable for his current situation. It is important to know that aircraft like a Boeing 747 with a lot of payload on a long distance leg is unable to stay below 250 knots during departure.
 +
 
 +
*'''The phrase "<strike>Reduce to minimum approach speed</strike>" shall not be used!'''
 +
*'''Instead use "Reduce to final approach speed"'''
 +
 
 +
The difference is that the minimum approach speed is the slowest speed an aircraft can possibly fly.
 +
On the other hand, the final approach speed is the planned speed from the pilot, factoring in the wind, and other margins like flap settings and such.
  
How to maintain visual separation?<br>You may use:
+
----
  
*'''Lateral vectoring'''&nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five).
 
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a "stop climbing/descending at FLxxx" to avoid a conflict.<br>
 
*'''Speed limit:''' A controller may issue speed instructions within an aircrafts operating limits. There are two possible ways to do this, either by using Indicated Airspeed (FL280 or below) or by specifying a Mach number (FL280 or above). Take notice of the minimum speed of the aircraft! Normally you are working with "minimum clean" (means the lowest speed an aircraft can maintain without using flaps or spoilers) above FL100. The second is “minimum approach speed” which is the lowest speed an aircraft can maintain using both flaps and spoilers.<br>
 
  
<br>
 
  
 
= Phraseology<br>  =
 
= Phraseology<br>  =
Line 165: Line 234:
 
== LOWW  ==
 
== LOWW  ==
  
Frequencies:  
+
Frequencies: (called Wien Radar)
  
LOWW_APP can be divided into up to six Sectors:
+
134.675 Wien Approach<br>
 +
118.770 Wien N Approach<br>
 +
129.050 Wien P Approach<br>
 +
125.170 Wien M Approach<br>
 +
119.800 Wien Arrival rwy16/34<br>
 +
126.550 Wien Arrival rwy11/29
  
{| class="prettytable FCK__ShowTableBorders"
+
'''Limits'''
|-
+
 
|
+
- vertikal: GND - FL245
LOWW_APP
 
  
|
+
'''preferred RWY configurations'''
LOWW_N_APP
 
  
|
+
- ARR 34/DEP 29<br>
LOWW_S_APP
+
- ARR 11+16/DEP 16<br>
 +
- ARR 16/DEP 16+29<br>
 +
- ARR 34/DEP 34+29
  
|
 
LOWW_F_APP
 
  
|
 
LOWW_D_APP
 
  
|
+
<br>reference sheet you find [https://downloads.vacc-austria.org/Documents/QRS_LOWW.pdf QRS LOWW]
LOWW_DEP
 
  
|-
+
== LOWI  ==
|
 
128.200
 
  
|
+
Frequencies: 119.27
124.550
 
  
|
+
Transition Altitude: 10000ft
129.550
 
  
|
+
'''Limits'''
119.800
 
  
|
+
- vertikal: GND - FL165
132.470
 
  
|
+
'''Arrivals'''
118.770
 
  
|-
+
*LOC/DME West via KTI FL130 over KUDAV
|
 
GND-FL105
 
  
|
+
*LOC//DME East via RTT 9500ft over RTT
FL105-FL245
 
  
|
+
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure
FL105-FL245
 
  
|
+
*RNP - RNAV Approach Rundway 08:instrumental approach with lower minimas, final also a visual Approach.
1<sup>st</sup> Director
 
  
|
+
*All arrivals are going via AB, finals after RUM are always visual
2<sup>nd</sup> Director
 
  
|
+
The reference sheet you find: [https://downloads.vacc-austria.org/Documents/QRS_LOWI.pdf QRS_LOWI]
Departure
 
  
|}
+
== LOWG  ==
  
The decision which sectors are used shall be based on traffic Situation.
+
'''Frequencies:'''
  
Transition Altitude: 5000ft
+
Graz Approach 119.3
  
'''Limits'''
+
Graz Tower 118.2
  
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile
+
Klagenfurt Graz Approach (LOVV_S_APP) 119.3
  
'''Arrivals'''
+
Transition Altitude: 10000ft
  
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:
+
'''Limits'''
  
{| class="wikitable FCK__ShowTableBorders"
+
- vertikal: GND - FL165
|-
 
|
 
VIA
 
  
|
+
'''Arrivals'''
FL
 
  
|-
+
STARs end in XIBAR (arriving form the west) or PIBIP (arriving from the east).
|
 
MASUR
 
  
|
+
You can follow-up with the corresponding RNAV transitions:
at FL170
 
  
|-
+
'''16C''' - XIBAR'''2N'''/PIBIP'''2N''' terminating in RONOT and followed by RNP or VOR approach.
|
 
BARUG
 
  
|
+
'''34C''' - XIBAR'''2S'''/PIBIP'''2S''' terminating in VAGIL and followed by ILS, RNP or VOR approach.
at FL170
 
  
|-
+
Use caution due to high MRVAs.
|
 
NIGSI
 
  
|
 
at FL180
 
  
|}
+
*ILS 34C starts at 3300ft. Best way is to intercept at VAGIL at 3500ft.
  
*LHCC: approaching traffic is maintaining FL140 over GIGOR
+
*RNP 34C follows the transition and starts at VAGIL 3500ft.
  
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180
+
*RNP 16C follows the transition and starts at RONOT 7500ft.
  
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170
+
*VOR-DME 34C: Approach via GRZ-VOR to DME 7.0 GRZ (heading 144°), join final track via D6.0 GRZ (heading 344°). For descend a racetrack procedure (GRZ inbound 344°, right turns) is available.
  
'''Departures'''
+
*VOR-DME 16C: Approach via GRZ-VOR (heading 164°), starts at D21.9 (RONOT) in 7500ft, descend profile see chart.
  
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.
 
  
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix)
+
'''preferred RWY configurations'''
  
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.
+
Opposite RWY ops: ARR 34C/DEP 16C to avoid overflying the city.
  
*via SASAL, STEIN cleared FL230 to LHCC_CTR
 
  
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.
+
'''hand/over'''
  
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)
+
*LHCC_CTR via GOTAR, climbing FL150, above FL130
  
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)
+
*LJLA_CTR via RADLY, climbing FL160
  
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.
+
*LOVV_CTR, climbing FL160
  
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)'''
+
Find the reference sheet here: [https://downloads.vacc-austria.org/Documents/QRS_LOWG.pdf QRS_LOWG]
  
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.
+
== LOWK  ==
  
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.
+
'''Frequencies:'''
  
{| class="wikitable FCK__ShowTableBorders"
+
Approach 126.825
|-
 
|
 
inbound LZIB
 
  
|
+
Tower 118.120
FL070 (KUNET at level)
 
  
|-
+
Klagenfurt Graz Approach (LOVV_S_APP) 119.300
|
 
outbound LZIB
 
  
|
 
climbing FL120
 
  
|-
+
Transition Altitude: 10000ft
|
 
inbound LKTB
 
  
|
+
''CAUTION: high terrain and therefore high MRVAs surrounding the aerodrome''
FL110 (MIKOV at level)
 
  
|-
 
|
 
outbound LKTB
 
  
|
+
'''Limits'''
climbing FL100
 
  
|-
+
- vertikal: GND - FL165
|
 
LOWW to LZIB
 
  
|
+
'''Arrivals'''
FL070 (ABLOM at level)
 
  
|-
+
All STARS terminate basically above the airport at MOKEG, except for ABIRI'''3T''' which is used for 28R approaches.
|
 
LZIB to LOWW
 
  
|
+
Following MOKEG, transitions are available:
6000ft (TOVKA at level)
 
  
|}
+
'''10L''' via MOKEG'''2W'''
 +
 +
'''28R''' via MOKEG'''2E'''
  
'''Remarks'''
+
Due to an error in Jeppesen data, many pilots will be unable to select the MOKEG2E transition in combination with ILS28R.
  
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.
+
Either advise them to program manually (4 WK... waypoints) or use vectors. Caution, tight space requires close monitoring of flightpath!.
  
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.
 
  
*Hand-off for arrivals to LZIB short before MIRLU.
+
*ILS 28R via KFT (or WK827, same position!)
  
'''Appendix'''
+
*RNP 28R via WK824 at 6500ft(on ABIRI arrival) and WK827
  
[[Image:LOVV APP.jpg]]&nbsp;
+
*NDB-DME 28R, the famous "Seesaw-Approach", which requires good preplanning, as aircrafts will fly back and forth above the aerodrome!
  
<br>
+
*NDB-DME 10, starts at WK808 - 8000ft straight in or WK806 - 6300ft
  
reference sheet you find [http://downloads.vacc-austria.org/Documents/QRS_LOWW_v1.3.pdf downloads.vacc-austria.org/Documents/QRS_LOWW_v1.3.pdf]
+
*Circling 10: Approach via 28R (ILS, RNP), circling starts latest at KI with breakoff into a right downwind 10L.
  
== LOWI  ==
+
'''hand/over'''
  
Frequencies: 119.27
+
*LJLA_CTR via BERTA, KLAGY or DIPSA, climbing FL150 above FL130
  
Transition Altitude: 11000ft
+
*LOVV_CTR, climbing FL160
  
'''Limits'''
+
== LOWS  ==
  
- vertikal: GND - FL165
+
'''Frequencies'''
  
'''Arrivals'''
+
Approach 123.720
  
*LOC/DME West via KTI FL130 over KTI
+
Tower 118.1
  
*LOC//DME East via RTT 9500ft over RTT
+
Salzburg Linz Approach (LOVV_N_APP) 123.720
  
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure
 
  
*All arrivals are going via AB, finals after AB are always visual
+
Transition Altitude: 10000ft
  
The reference sheet you find: [http://downloads.vacc-austria.org/Documents/QRS_LOWI_v1.2.pdf downloads.vacc-austria.org/Documents/QRS_LOWI_v1.2.pdf]
+
'''Limits'''
  
== LOWG  ==
+
- vertikal: GND - FL125
  
Frequencies: 119.3
+
'''Arrivals'''
  
Transition Altitude: 4000ft
+
All STARs terminate overhead '''SBG VOR'''. No transitions are available, use directs, vectors or procedure turns (holding at SBG).
  
'''Limits'''
+
*ILS/NDB 15 - ILS is most commonly used, both approaches start at SBG VOR 4000ft with intercept via SBG NDB (caution, some pilots may be confused by VOR/NDB)
 +
*RNP E 15 - final track is identical to ILS/NDB 15, can be intercepted from west (WS813) or east (WS814) at 5000ft.
 +
*RNP X 15 - higher minima than RNP E, Missed Approach does not overfly the aerodrome.
  
- vertikal: GND - FL165
+
*Visual 33 - uses ILS 15 followed by a right downwind RWY 33
 +
*RNP V 33 - from north, starting at WS831 or WS832 at 5000ft, and basically a right downwind to RWY33, final turn is visual (high minima). Caution! Departures crossing! Coordination with TWR (initial climb) is required.
 +
*RNP Y 33 - same as V, but final turn is RNAV based, therefore lower minima
 +
*RNP Z 33 - from south, intercept via KONUG (11500ft) or ETROK (10000ft), scenic route through the valley. Caution to MRVA! Use vectors or ETROK also for arrivals from south-west to avoid steep descend angles.
  
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used.
 
  
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.
+
'''hand/over'''
  
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track
+
EDDM_S_APP via TRAUN, climbing FL120
  
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.
+
EDDM_S_APP via TITIG, climbing FL90 and released for FL120.
  
'''hand/over'''
+
EDMM_CTR via SIMBA, climbing FL120
  
*LHCC_CTR via GOTAR FL150
 
  
*LJLA_CTR via RADLY FL160
 
  
*LOVV_CTR FL160
+
rest to LOVV_CTR, climbing FL120
  
== LOWK  ==
 
  
Frequencies: 126.825
+
find the reference sheet at [http://downloads.vacc-austria.org/Documents/QRS_LOWS_v1.1.pdf downloads.vacc-austria.org/Documents/QRS_LOWS_v1.1.pdf]
  
Transition Altitude: 7000ft
+
== LOWL  ==
  
'''Limits'''  
+
'''Frequencies'''  
  
- vertikal: GND - FL165
+
Approach 129.620
  
'''Arrivals'''
+
Tower 118.8
  
*ILS 28
+
Salzburg Linz Approach (LOVV_N_APP) 123.720
  
*NDB-DME 28
 
  
*NDB-DME 10
+
Transition Altitude: 10000ft
  
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI
 
  
'''hand/over'''  
+
'''Limits'''
  
*LJLA_CTR via REKTI FL160
+
- vertikal: GND - FL165
  
*LOVV_CTR FL160
+
'''Arrivals'''
  
== <br>LOWS  ==
+
STARs from north will end in PETEN, while STARs from south terminate in ARASA.
  
Frequencies: 123.720<br>Transition Altitude: 4000ft
+
Transitions are available:
  
Limits
+
'''08''' via PETEN'''1C''' or ARASA'''1C''' followed by ILS, RNP or VOR approaches.
  
- vertikal: GND - FL125
+
'''26''' via PETEN'''1D''' or ARASA'''1D''' followed by ILS, RNP or NDB approaches.
  
Arrivals
 
  
ILS&nbsp;16 <br>NDB&nbsp;16&nbsp;<br>visual&nbsp;34 <br><br>hand/over
+
*ILS/VOR 08 (ILS 08 not in standard FSX), starting from LIDSI at 4000ft or a racetrack procedure from LNZ VOR
 +
*ILS/NDB 26, starting from PEROL at 4000ft or a racetrack procedure from LNZ NDB
 +
*RNP 08, via transition and LIDSI at 4000ft.
 +
*RNP 26, via transition and PEROL at 4000ft.
  
EDDM_S_APP via NAPSA and TRAUN<br>EDDM_CTR via TRAUN<br>rest to LOVV_CTR, all&nbsp;FL120 <br>
+
'''hand/over'''
  
reference sheet you find at [http://downloads.vacc-austria.org/Documents/QRS_LOWS_v1.1.pdf downloads.vacc-austria.org/Documents/QRS_LOWS_v1.1.pdf]
+
EDMM_CTR via RENKA or LAMSI, climbing FL160
  
<br>
+
EDMM_CTR via SUBEN, climbing FL140, released for FL160 (20nm to SUBEN)
  
== LOWL  ==
+
LKAA_CTR via UPEGU, at FL160
  
Frequencies: 129.620<br>Transition Altitude: 4000ft
+
rest to LOVV_CTR, all FL160
  
Limits
 
  
- vertikal: GND - FL165
+
find the reference sheet at [http://downloads.vacc-austria.org/Documents/QRS_LOWL_v1.0.pdf downloads.vacc-austria.org/Documents/QRS_LOWL_v1.0.pdf]
  
Arrivals
+
==References==
  
ILS/VOR&nbsp;08 (ILS 08 not in standard FSX)&nbsp;<br>ILS/NDB 26<br>(former RWYs known as 09 and 27)
+
* http://en.wikipedia.org/wiki/Wake_turbulence<br>  
  
hand/over
+
* The VACC-SAG.org study guide for APP is more detailed and well to read: see [[http://board.vacc-sag.org/14/23543/ this thread]] in the VACC-SAG board (you need a login, and it's free).
  
EDDM_CTR via PABSA and TRAUN<br>LKAA_CTR via ADLET<br>rest to LOVV_CTR, all FL160
+
* The Austrocontrol [[http://eaip.austrocontrol.at/lo/130110/PART_2/LO_ENR_1_4_en.pdf airspace definition]]
  
<br>reference sheet you find at [http://downloads.vacc-austria.org/Documents/QRS_LOWL_v1.0.pdf downloads.vacc-austria.org/Documents/QRS_LOWL_v1.0.pdf]  
+
* [[Radar_Identification|Radar Identification]]
  
 
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]
 
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]

Latest revision as of 15:37, 4 January 2023

Prev: Study Guide:Tower - Overview: Study Guide - Next: Study Guide:Radar

General

TMA controller includes approach and departure control services associated with a particular airport have the following main tasks:

  1. maintain an orderly flow of traffic
  2. provide separation service between aircraft
  3. provide assistance to pilots

General radar procedures

Identifikation mit Hilfe eines Transponders

Ein Transponder ist ein Bauteil von den gängigen Verkehrs- und Sportflugzeugen, es dient zur Übermittlung von Daten an die Flugverkehrskontrollstelle um die Flugsicherung zu vereinfachen. Mit Hilfe des Transponders ist es möglich, einem Kontakt auf dem Primärradar ein Callsign und einen Flugplan zu zuordnen. Aus diesem Grund erhält jeder Instrumentenflug und spezielle VFR Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen.

Mode A

Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode.

Mode C

Flugzeuge mit Transpondermode C sind in der Lage neben dem Transpondercode auch die aktuelle Flughöhe, gemessen vom barometrischen Höhenmesser. Die übermittelte Höhe ist unabhängig vom eingestellten QNH, die Übermittlung erfolgt in 100-Fuß-Schritten.

Mode S

Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs.

Weitere Informationen: Radar Identification


Position information

Positionsinformationen dienen zur Orientierung des Piloten und können nach Möglichkeit an Hand von Navaids oder markanten Punkten, ähnlich den Pflichtmeldepunkten an den Piloten übermittelt werden. Die Positionsinformation unter Angabe markanter Punkte soll nur reaktiv angeboten werden, nicht jeder Pilot unter IFR ist mit den Örtlichkeiten vertraut, es empfiehlt sich daher grundsätzlich veröffentlichte Navaids oder einfache Kursangaben und Entfernung für die Übermittlung solcher Informationen zu nutzen.


Vectoring of Aircrafts

Flugzeuge kann man mit Hilfe von Kursanweisungen in die gewünschte Flugrichtung führen. Es ist dabei zu beachten, dass eine Kursanweisungen zu einem gewünschten Punkt in Abhängigkeit von Wind, Geschwindigkeit und Bank-Angle nicht immer 100%ig zum gewünschten Ergebnis führen kann, darum ist es wichtig, ein gewisses Gefühl für die Piloten und Flugzeuge zu entwickeln. Übrigens, bei einem Bank Angle von 30° und identischer Geschwindigkeit, ist der Kurvenradius eines Airbus A380 genau so groß, wie der einer Cessna Citation, obwohl diese viel kleiner ist. Grundsätzlich empfiehlt sich, Kursanweisungen möglichst großzügig und rechtzeitig zu erteilen und ein Flugzeug lieber bei 12 dme until touchdown auf dem LOC aufzufädeln, als auf 8 dme.


Usage of directs

Piloten unter RNAV und Non-RNAV sind neben dem befolgen von Kursanweisungen auch in der Lage, ihr Flugzeug direkt zu einem gewünschten Wegpunkt zu navigieren und anschließend auf der ursprünglich geplanten Route weiterzufliegen. Die Anweisung zum fliegen eines directs ist für den Piloten nicht verbindlich, er darf dies jederzeit ohne Angabe von Gründen ablehnen. In Absprache mit benachbarten Flugverkehrskontrollstellen ist es auch möglich, directs über große Entfernungen und durch mehrere Flugsicherungssektoren anzubieten. Bei der Freigabe für den Direktflug zu einem Wegpunkt ist zu prüfen, ob der Pilot davon überhaupt einen Nutzen hat, ein Shortcut welcher den Flugweg des Flugzeugs lediglich um 2 Meilen verkürzt ist kein direct und keine Hilfe für den Piloten. Bei der Vergabe von Shortcuts besteht die Gefahr, dass man sich selbst sehr schnell den Luftraum zusperrt, besonders auf Flughäfen wie Innsbruck ist es riskant allen Flugzeugen den Direktflug zum IAF (RTT bzw. KTI NDB) zu erteilen. Ein Direct zu einen Punkt auf einer Transition ist übrigens die gleichzeitige Freigabe für die gesamte darauffolgende Wegstrecke der Transition, allerdings nicht des vertikalen Profils, gleiches gilt für einen Direct zu einem Punkt der STAR, so ist der Pilot freigegeben für die gesamte STAR bis zum IAF, nicht mehr nur bis zum clearance limit.


Separation

Vertical separation

Vertical separation is obtained by requiring aircraft using prescribed altimeter setting procedures to operate at different levels to avoid lost of separation. The vertical separation minimum shall be 1000 feet below FL 410 in RVSM airspace or 2000 feet above FL290 in non-RVSM airspaces. To fly within RVSM an aircraft must be equipped with:

  1. 2 independent altimeters
  2. an autopilot witch must be able to hold an specific altitude
  3. min. Mode C transponder

Lateral separation

Lateral separation is also known as radar separation and shall be applied so that the distance between those portions of the intended routes for with the aircraft are to be laterally separated is never less than an established distance to account for navigational inaccuracies. Have a look into the wake turbulence separation to find the required distances for the lateral separation.


Wake turbulence separation

Wake turbulence is turbulence that forms behind an aircraft as it passes through the air. This turbulence includes various components, the most important of which are wingtip vortices and jetwash. Jetwash refers simply to the rapidly moving gases expelled from a jet engine; it is extremely turbulent, but of short duration. Wingtip vortices, on the other hand, are much more stable and can remain in the air for up to three minutes after the passage of an aircraft.

Takeoff

An aircraft of a lower wake vortex category must not be allowed to take off less than two minutes behind an aircraft of a higher wake vortex category. If the following aircraft does not start its take off roll from the same point as the preceding aircraft, this is increased to three minutes.

Landing
Preceding aircraft Following aircraft Minimum radar separation
Super Super 4 NM
Heavy 6 NM
Medium 7 NM
Small 8 NM
Heavy Heavy 4 NM
Medium 5 NM
Small 5 NM
Medium Small

4 NM

  • Staying on or above leader's glide path
    Incident data shows that the greatest potential for a wake vortex incident occurs when a light aircraft is turning from base to final behind a heavy aircraft flying a straight-in approach. Light aircraft pilots must use extreme caution and intercept their final approach path above or well behind the heavier aircraft's path. When a visual approach following a preceding aircraft is issued and accepted, the pilot is required to establish a safe landing interval behind the aircraft he was instructed to follow. The pilot is responsible for wake turbulence separation. Pilots must not decrease the separation that existed when the visual approach was issued unless they can remain on or above the flight path of the preceding aircraft.

Separation with individual speeds

A controller may issue speed instructions within an aircraft operating limits. There are two possible ways to do this, either by using Indicated Airspeed (FL280 or below) or by specifying a Mach number (FL280 or above). Take notice of the minimum speed of the aircraft! Normally you are working with "minimum clean" (means the lowest speed an aircraft can maintain without using flaps or slats above FL100. The best way to gain separation between two aircraft is to advise an specific speed to the relevant aircraft.

For example:

LOWW_APP: AUA14F, speed 220 knots indicated.
AUA14F:       Speed 220 Knots, AUA14F.

If the pilot reports "unable" ask the pilot witch speed would be suitable for his current situation. It is important to know that aircraft like a Boeing 747 with a lot of payload on a long distance leg is unable to stay below 250 knots during departure.

  • The phrase "Reduce to minimum approach speed" shall not be used!
  • Instead use "Reduce to final approach speed"

The difference is that the minimum approach speed is the slowest speed an aircraft can possibly fly. On the other hand, the final approach speed is the planned speed from the pilot, factoring in the wind, and other margins like flap settings and such.



Phraseology

A ...Pilot
G...ATC

Approach

Standard clearances for arriving aircraft shall contain the following items, if applicable:

1. Aircraft identification
2. Designator of assigned STAR
3. Runway-in-use, except when part of the STAR description
4. Initial level, except when this element is included in the START description and
5. Any other necessary instructions or information not contained in the START description, e.g. change of communication

Type of approach procedure

G: CLEARED / PROCEED VIA (designator) ARRIVAL
G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL
G: CLEARED (type of approach) APPROACH RUNWAY (number)
G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]
G: CLEARED APPROACH RUNWAY (number)
A: REQUEST (type of approach) APPROACH [RUNWAY (number)]
G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]
A: REQUEST (RNAV plain language designator)
G: CLEARED (RNAV plain language designator)
G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]?

Straight-in approach

A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]
G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]

Approach instructions with radar

G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)
G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT
G: VECTORING FOR (positioning in the circuit)
G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)
G: VECTORING FOR PRECISION APPROACH RUNWAY (number)
G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)
G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)
G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN
A: REQUEST (distance) FINAL
G: CLEARED FOR (type) APPROCH RUNWAY (number)
G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]
G: REPORT ESTABLISHED ON FINAL APPROACH TRACK
G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]
G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]
G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)
G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]
G: TAKING YOU THROUGH (localizer or radio aid) [reason]
G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION
G: REPORT ESTABLISHED ON GLIDE PATH
G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]
G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]
G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT
G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER
G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)
G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)
G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)


Go around

G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)
G: IF GOING AROUND (appropriate instructions)
G: ARE YOU GOING AROUND?
A: GOING AROUND

Level changes, reports and rates

G: CLIMB / DESCEND
- TO (level)
- TO AND MAINTAIN BLOCK (level) TO (level)
- TO REACH (level) AT / BY (time or significant point)
- REPORT LEAVING / REACHING / PASSING (level)
- AT (number) FEET PER MINUTE [OR GREATER / LESS]
G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]
G: STOP CLIMB / DESCENT AT (level)
G: CONTINUE CLIMB / DESCENT TO (level)
G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]
G: RESUME NORMAL RATE OF CLIMB / DESCENT
G: REPORT LEAVING / REACHING / PASSING (level)
G: WHEN READY CLIMB / DESCENT TO (level)
G: EXPEDITE CLIMB / DESCENT AT (time of significant point)
G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)
A: REQUEST DESCENT AT (time)
A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]
A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)
G: EXPECT LEVEL CHANGE / CLIMB / DESCENT
- FROM (name of unit)
- AT (time or position)
- AFTER PASSING (position)
- IN (number) MINUTES
G: IMMEDIATELY
G: AFTER PASSING (significant point)
G: AT (time or significant point)
G: WHEN READY (instructions)

Vectoring

G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]
G: CONTINUE HEADING (three digits)
G: CONTINUE PRESENT HEADING
G: FLY HEADING (three digits)
G: TURN LEFT / RIGHT HEADING (three digits) [reason]
G: TURN LEFT / RIGHT (number) DEGREES [reason]
G: STOP TURN HEADING (three digits)
G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)
G: HEADING IS GOOD
G: WHEN ABLE PROCEED DIRECT (position)
G: SUGGEST (suggestion)
G: IF UNABLE [(alternative instructions)] ADVISE
A: UNABLE TO COMPLY (reason)
G: VECTORING FOR SPACING / SEPERATION / DELAY
G: VECTORING DUE TO TRAFFIC
G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)
G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]
G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]
G: ORBIT LEFT / RIGHT [reason]
G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”
G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT
G: TURN LEFT / RIGHT NOW
G: STOP TURN NOW

Speed instructions:

G: REPORT SPEED
G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER
A: SPEED (number) KNOTS / MACH (number)
G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]
G: DO NOT EXCEED (number) KNOTS / MACH (number)
G: MAINTAIN PRESENT SPEED
G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]
G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]
A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)
G: RESUME NORMAL SPEED
G: REDUCE TO MINIMUM APPROACH SPEED
G: REDUCE TO MINIMUM CLEAN SPEED
G: REDUCE TO MINUMUM SPEED
A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS
G: NO [ATC] SPEED RESTRICTIONS

Flight rules

A: CANCELLING IFR
G: IFR CANCELLED AT (time)

A: REQUEST IFR CLEARANCE
G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)]

G: CLEARED NIGHT VFR
G: CLEARED SPECIAL VFR

FAQs

How do I work with STARs and Transitions?
STAR means Standard Terminal Arrival Route is like a route to the airport.This road has a name that has three parts. The first part is the navigational point where the route starts, the second is the version number, and the third is usually but again not always coupled to a certain runway(s). Transitions are connecting between the end of STAR to the final but not at any airport.
Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing "transition and profile" the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.

How to use a Holding?
The primary use of a holding is delaying aircraft that have arrived over their destination but cannot land yet because of traffic congestion, poor weather, or unavailability of the runway. Several aircraft may fly the same holding pattern at the same time, separated vertically by 1,000 feet or more.
A holding is situated around a holding fix. In a standard holding pattern the aircraft flies inbound to the holding fix on a certain course (Inbound leg). After passing the fix it turns right (standard turn: 2° per second) and flies one minute (1,5 min above FL 140) into the other direction (outbound leg). After one minute the pilot turns right again (standard turn) and establishes again on the inbound leg.
If you count all this together you end up with four minutes required to finish one holding pattern. However some holding patterns use left turns, others don't use one minute to measure the outbound leg, but fly to a certain distance.
Also every holding has a minimum altitude.


What does MRVA mean?
Minimum Radar Vectoring Altitude: lowest altitude above MSL that can be used for IFR vectoring


When is the best moment for my handoff?
Out of conflict and as early as possible.


Which classes of airspace are provided in Austria?

  • C (Charlie) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR will be separated to other IFR and VFR traffic, VFR traffic receive traffic information about other VFR traffic. C starts AT FL195 and inside Special Rules Area (e.g. SRA Wien)
  • D (Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR; VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA.
  • E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs (Terminal Control Areas).
  • G (Golf) uncontrolled airspace. Traffic information as far as possible.

What are Y and Z-flights?
Basically these are flights with a change between IFR/VFR

  • Y starts with IFR, changing to VFR (IFR cancellation)
  • Z starts with VFR, changing to IFR (IFR pickup)



References

Information about airspaces and airways can be found here: [1]

Details about air pressure and altitudes you will find here: [2]

Links for the reference (working) sheets you find at the airport details.



Local Procedures

LOWW

Frequencies: (called Wien Radar)

134.675 Wien Approach
118.770 Wien N Approach
129.050 Wien P Approach
125.170 Wien M Approach
119.800 Wien Arrival rwy16/34
126.550 Wien Arrival rwy11/29

Limits

- vertikal: GND - FL245

preferred RWY configurations

- ARR 34/DEP 29
- ARR 11+16/DEP 16
- ARR 16/DEP 16+29
- ARR 34/DEP 34+29



reference sheet you find QRS LOWW

LOWI

Frequencies: 119.27

Transition Altitude: 10000ft

Limits

- vertikal: GND - FL165

Arrivals

  • LOC/DME West via KTI FL130 over KUDAV
  • LOC//DME East via RTT 9500ft over RTT
  • RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure
  • RNP - RNAV Approach Rundway 08:instrumental approach with lower minimas, final also a visual Approach.
  • All arrivals are going via AB, finals after RUM are always visual

The reference sheet you find: QRS_LOWI

LOWG

Frequencies:

Graz Approach 119.3

Graz Tower 118.2

Klagenfurt Graz Approach (LOVV_S_APP) 119.3

Transition Altitude: 10000ft

Limits

- vertikal: GND - FL165

Arrivals

STARs end in XIBAR (arriving form the west) or PIBIP (arriving from the east).

You can follow-up with the corresponding RNAV transitions:

16C - XIBAR2N/PIBIP2N terminating in RONOT and followed by RNP or VOR approach.

34C - XIBAR2S/PIBIP2S terminating in VAGIL and followed by ILS, RNP or VOR approach.

Use caution due to high MRVAs.


  • ILS 34C starts at 3300ft. Best way is to intercept at VAGIL at 3500ft.
  • RNP 34C follows the transition and starts at VAGIL 3500ft.
  • RNP 16C follows the transition and starts at RONOT 7500ft.
  • VOR-DME 34C: Approach via GRZ-VOR to DME 7.0 GRZ (heading 144°), join final track via D6.0 GRZ (heading 344°). For descend a racetrack procedure (GRZ inbound 344°, right turns) is available.
  • VOR-DME 16C: Approach via GRZ-VOR (heading 164°), starts at D21.9 (RONOT) in 7500ft, descend profile see chart.


preferred RWY configurations

Opposite RWY ops: ARR 34C/DEP 16C to avoid overflying the city.


hand/over

  • LHCC_CTR via GOTAR, climbing FL150, above FL130
  • LJLA_CTR via RADLY, climbing FL160
  • LOVV_CTR, climbing FL160

Find the reference sheet here: QRS_LOWG

LOWK

Frequencies:

Approach 126.825

Tower 118.120

Klagenfurt Graz Approach (LOVV_S_APP) 119.300


Transition Altitude: 10000ft

CAUTION: high terrain and therefore high MRVAs surrounding the aerodrome


Limits

- vertikal: GND - FL165

Arrivals

All STARS terminate basically above the airport at MOKEG, except for ABIRI3T which is used for 28R approaches.

Following MOKEG, transitions are available:

10L via MOKEG2W

28R via MOKEG2E

Due to an error in Jeppesen data, many pilots will be unable to select the MOKEG2E transition in combination with ILS28R.

Either advise them to program manually (4 WK... waypoints) or use vectors. Caution, tight space requires close monitoring of flightpath!.


  • ILS 28R via KFT (or WK827, same position!)
  • RNP 28R via WK824 at 6500ft(on ABIRI arrival) and WK827
  • NDB-DME 28R, the famous "Seesaw-Approach", which requires good preplanning, as aircrafts will fly back and forth above the aerodrome!
  • NDB-DME 10, starts at WK808 - 8000ft straight in or WK806 - 6300ft
  • Circling 10: Approach via 28R (ILS, RNP), circling starts latest at KI with breakoff into a right downwind 10L.

hand/over

  • LJLA_CTR via BERTA, KLAGY or DIPSA, climbing FL150 above FL130
  • LOVV_CTR, climbing FL160

LOWS

Frequencies

Approach 123.720

Tower 118.1

Salzburg Linz Approach (LOVV_N_APP) 123.720


Transition Altitude: 10000ft

Limits

- vertikal: GND - FL125

Arrivals

All STARs terminate overhead SBG VOR. No transitions are available, use directs, vectors or procedure turns (holding at SBG).

  • ILS/NDB 15 - ILS is most commonly used, both approaches start at SBG VOR 4000ft with intercept via SBG NDB (caution, some pilots may be confused by VOR/NDB)
  • RNP E 15 - final track is identical to ILS/NDB 15, can be intercepted from west (WS813) or east (WS814) at 5000ft.
  • RNP X 15 - higher minima than RNP E, Missed Approach does not overfly the aerodrome.
  • Visual 33 - uses ILS 15 followed by a right downwind RWY 33
  • RNP V 33 - from north, starting at WS831 or WS832 at 5000ft, and basically a right downwind to RWY33, final turn is visual (high minima). Caution! Departures crossing! Coordination with TWR (initial climb) is required.
  • RNP Y 33 - same as V, but final turn is RNAV based, therefore lower minima
  • RNP Z 33 - from south, intercept via KONUG (11500ft) or ETROK (10000ft), scenic route through the valley. Caution to MRVA! Use vectors or ETROK also for arrivals from south-west to avoid steep descend angles.


hand/over

EDDM_S_APP via TRAUN, climbing FL120

EDDM_S_APP via TITIG, climbing FL90 and released for FL120.

EDMM_CTR via SIMBA, climbing FL120


rest to LOVV_CTR, climbing FL120


find the reference sheet at downloads.vacc-austria.org/Documents/QRS_LOWS_v1.1.pdf

LOWL

Frequencies

Approach 129.620

Tower 118.8

Salzburg Linz Approach (LOVV_N_APP) 123.720


Transition Altitude: 10000ft


Limits

- vertikal: GND - FL165

Arrivals

STARs from north will end in PETEN, while STARs from south terminate in ARASA.

Transitions are available:

08 via PETEN1C or ARASA1C followed by ILS, RNP or VOR approaches.

26 via PETEN1D or ARASA1D followed by ILS, RNP or NDB approaches.


  • ILS/VOR 08 (ILS 08 not in standard FSX), starting from LIDSI at 4000ft or a racetrack procedure from LNZ VOR
  • ILS/NDB 26, starting from PEROL at 4000ft or a racetrack procedure from LNZ NDB
  • RNP 08, via transition and LIDSI at 4000ft.
  • RNP 26, via transition and PEROL at 4000ft.

hand/over

EDMM_CTR via RENKA or LAMSI, climbing FL160

EDMM_CTR via SUBEN, climbing FL140, released for FL160 (20nm to SUBEN)

LKAA_CTR via UPEGU, at FL160

rest to LOVV_CTR, all FL160


find the reference sheet at downloads.vacc-austria.org/Documents/QRS_LOWL_v1.0.pdf

References

  • The VACC-SAG.org study guide for APP is more detailed and well to read: see [this thread] in the VACC-SAG board (you need a login, and it's free).