<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.vacc-austria.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Chris+Wirowski</id>
	<title>VACC Austria DokuWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.vacc-austria.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Chris+Wirowski"/>
	<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php/Special:Contributions/Chris_Wirowski"/>
	<updated>2026-04-07T14:58:18Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.9</generator>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=How_to_become_a_visiting_controller_in_the_VACC_Austria&amp;diff=2261</id>
		<title>How to become a visiting controller in the VACC Austria</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=How_to_become_a_visiting_controller_in_the_VACC_Austria&amp;diff=2261"/>
		<updated>2012-06-30T13:57:42Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: /* Apply for visting controller status */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Requirements to become a visiting controller  ===&lt;br /&gt;
&lt;br /&gt;
#The applicant is required to obey the [http://www.vacc-austria.org/page/RULES Rules of VACC Austria]. &lt;br /&gt;
#The applicant must be fluent in german language, both, written and spoken.&lt;br /&gt;
#The applicant is required to hold a permanent Senior Student (S3) or above rating. &lt;br /&gt;
#The applicant must be at least 16 years old. &lt;br /&gt;
#The applicant should have a justified interest in controlling the requested airspace. &lt;br /&gt;
#The applicant is required for at least 10 Hours services in the period of 6 month.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Please note: The right to claim being a visiting controller does not exist. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Register at VACC-Austria  ===&lt;br /&gt;
&lt;br /&gt;
If your are not already registered in the VACC-Austria, go to our [http://www.vacc-austria.org Homepage] and create your account. Keep in mind, that the credentials for the VACC-Austria infrastructure differs from your VATSIM account! &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Gather some practice and experience  ===&lt;br /&gt;
&lt;br /&gt;
At this point we strongly recommend that you connect to the network and fly around our Airports for several hours to get a feeling on the pilot side and spend some hours at observing active controllers in Austria, as well. Feel free to chat with other pilots and controllers in our [[Teamspeak|Teamspeak]] Voice Chat and share your experience with us in our [http://forum.vacc-austria.org/ Forums]. Remember, the best controllers are also pilots, however, having (virtual) pilot experience is not a requirement but a recommendation from our side. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Apply for visting controller status  ===&lt;br /&gt;
&lt;br /&gt;
Log into the [http://vacc-austria.org/ VACC-Austria homepage] and select from the menu &amp;quot;member&amp;quot; and select &amp;quot;My Training&amp;quot; . In the information form fill out the application. Please give us some details about yourself, your skills, previous experience with flight simulation, phraseology etc. It would be nice to read some words about your motivation to apply for an controller status and how much hours you would spend into manning an VACC&amp;amp;nbsp;Austria position per month.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Procedure for accepted visiting controllers  ===&lt;br /&gt;
&lt;br /&gt;
After your acceptence as a visiting controller, anticipate the contact of your dedicated [[Mentor/trainer|mentor]], for further information. &lt;br /&gt;
&lt;br /&gt;
----&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=2192</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=2192"/>
		<updated>2012-06-02T16:43:27Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: /* LOWW */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport have the following main tasks: &lt;br /&gt;
&lt;br /&gt;
#maintain an orderly flow of traffic &lt;br /&gt;
#provide separation service between aircraft &lt;br /&gt;
#provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Separation  =&lt;br /&gt;
&lt;br /&gt;
=== Vertical separation  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;airspace or 2000 feet above FL290 in non-RVSM&amp;amp;nbsp;airspaces. To fly within RVSM an aircraft must be equipped with: &lt;br /&gt;
&lt;br /&gt;
#2 independent altimeters &lt;br /&gt;
#an autopilot witch must be able to hold an specific altitude &lt;br /&gt;
#min. Mode C transponder&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lateral separation  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Wake turbulence separation  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Takeoff&amp;lt;br&amp;gt;  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Landing  =====&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;width: 415px; height: 256px;&amp;quot; class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Preceding aircraft &lt;br /&gt;
! Following aircraft &lt;br /&gt;
! Minimum radar separation&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; | Super &lt;br /&gt;
| Super &lt;br /&gt;
| 4 [[Nautical mile|NM]]&lt;br /&gt;
|-&lt;br /&gt;
| Heavy &lt;br /&gt;
| 6 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 7 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 8 NM&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;3&amp;quot; | Heavy &lt;br /&gt;
| Heavy &lt;br /&gt;
| 4 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| Small &lt;br /&gt;
| &lt;br /&gt;
4 NM &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*Staying on or above leader's glide path&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Separation with individual speeds&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;minimum clean&amp;quot; (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.&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: AUA14F, speed 220 knots indicated.&lt;br /&gt;
AUA14F:       Speed 220 Knots, AUA14F.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
If the pilot reports &amp;quot;unable&amp;quot; ask the pilot witch speed would be suitable for his current situation. Its important to know that aircraft like a Boeing 747 with a lot of payload on an long distance leg are unable to stay below 250 knots during departure.&lt;br /&gt;
&lt;br /&gt;
*'''The phrase &amp;quot;&amp;lt;strike&amp;gt;Reduce to minimum approach speed&amp;lt;/strike&amp;gt;&amp;quot; shall not be used!'''&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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]&lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; ==References==&amp;lt;!-- AnimalBiology56:535. --&amp;gt;&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
http://en.wikipedia.org/wiki/Wake_turbulence&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=How_to_become_a_visiting_controller_in_the_VACC_Austria&amp;diff=2149</id>
		<title>How to become a visiting controller in the VACC Austria</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=How_to_become_a_visiting_controller_in_the_VACC_Austria&amp;diff=2149"/>
		<updated>2012-05-08T12:57:22Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: /* Requirements to become a visiting controller */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Requirements to become a visiting controller  ===&lt;br /&gt;
&lt;br /&gt;
#The applicant is required to obey the [http://www.vacc-austria.org/page/RULES Rules of VACC Austria]. &lt;br /&gt;
#The applicant must be fluent in german language, both, written and spoken.&lt;br /&gt;
#The applicant is required to hold a permanent Senior Student (S3) or above rating. &lt;br /&gt;
#The applicant must be at least 16 years old. &lt;br /&gt;
#The applicant should have a justified interest in controlling the requested airspace. &lt;br /&gt;
#The applicant is required for at least 10 Hours services in the period of 6 month.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Please note: The right to claim being a visiting controller does not exist. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Register at VACC-Austria  ===&lt;br /&gt;
&lt;br /&gt;
If your are not already registered in the VACC-Austria, go to our [http://www.vacc-austria.org Homepage] and create your account. Keep in mind, that the credentials for the VACC-Austria infrastructure differs from your VATSIM account! &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Gather some practice and experience  ===&lt;br /&gt;
&lt;br /&gt;
At this point we strongly recommend that you connect to the network and fly around our Airports for several hours to get a feeling on the pilot side and spend some hours at observing active controllers in Austria, as well. Feel free to chat with other pilots and controllers in our [[Teamspeak|Teamspeak]] Voice Chat and share your experience with us in our [http://forum.vacc-austria.org/ Forums]. Remember, the best controllers are also pilots, however, having (virtual) pilot experience is not a requirement but a recommendation from our side. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Apply for visting controller status  ===&lt;br /&gt;
&lt;br /&gt;
Log into the [http://vacc-austria.org/ VACC-Austria homepage] and select from the menu &amp;quot;member&amp;quot; and select &amp;quot;My Training&amp;quot; . In the information form fill out the application. Please give us some details about yourself, your skills, previous experience with flight simulation, phraseology etc. It would be nice to read some words about your motivation to apply for an visiting controller status and how much hours you would spend into manning an VACC&amp;amp;nbsp;Austria position per month.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Procedure for accepted visiting controllers  ===&lt;br /&gt;
&lt;br /&gt;
After your acceptence as a visiting controller, anticipate the contact of your dedicated [[Mentor/trainer|mentor]], for further information. &lt;br /&gt;
&lt;br /&gt;
----&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=How_to_become_a_VACC_Austria_Controller&amp;diff=2148</id>
		<title>How to become a VACC Austria Controller</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=How_to_become_a_VACC_Austria_Controller&amp;diff=2148"/>
		<updated>2012-05-08T12:56:30Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Requirements to become a VACC&amp;amp;nbsp;Austria controller  ===&lt;br /&gt;
&lt;br /&gt;
*The applicant is required to obey the [http://www.vacc-austria.org/page/RULES Rules of VACC Austria] and must be fluent in german speaking/writing.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Register your VATSIM account  ===&lt;br /&gt;
&lt;br /&gt;
If you are not already a VATSIM member, go to the [http://www.vatsim.net VATSIM&amp;amp;nbsp;Homepage] and create your account. Make sure your account is assigned to [http://www.vateur.org/ VATEUR (Europe) divison] and[http://www.vateud.org VATEUD (Europe without UK and Russia) subdivision]. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Check your VATSIM region assignment  ===&lt;br /&gt;
&lt;br /&gt;
Go to the [https://cert.vatsim.net/vatsimnet/statcheck.html VATSIM&amp;amp;nbsp;Certificate Website], type in your VATSIM&amp;amp;nbsp;ID, press &amp;quot;Lookup&amp;quot; and check if the region shows &amp;quot;Austria&amp;quot;. In case the region is not selected or not correct, send a mail to the [mailto:vateud4@vateud.net VATEUD Membership Director ]and ask to correct the region assignment. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Register at VACC-Austria  ===&lt;br /&gt;
&lt;br /&gt;
If your are not already registered in the VACC-Austria, go to our [http://www.vacc-austria.org Homepage] and create your account.&amp;amp;nbsp;Keep in mind, that the credentials for the VACC-Austria infrastructure differs from your VATSIM account! &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Gather some practice and experience  ===&lt;br /&gt;
&lt;br /&gt;
At this point we strongly recommend that you connect to the network and fly around for several hours to get a feeling on the pilot side and spend some hours at observing active controllers in Austria, as well. Feel free to chat with other pilots and controllers in our [[Teamspeak|Teamspeak]] Voice Chat and share your experience with us in our [http://forum.vacc-austria.org/ Forums]. Remember, the best controllers are also pilots, however, having (virtual) pilot experience is not a requirement but a recommendation from our side. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Apply for controller status  ===&lt;br /&gt;
&lt;br /&gt;
Log into the [http://vacc-austria.org/ VACC-Austria homepage] and select from the menu &amp;quot;member&amp;quot; and select &amp;quot;My Training&amp;quot; (deutschsprachige Mitglieder finden die Bewerbung unter &amp;quot;Mitglied&amp;quot; - &amp;quot;Meine Ausbildung&amp;quot;). In the information form, fill out the application. Please give us some details about yourself, your skills, previous experience with flight simulation, phraseology etc. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Procedure for accepted controllers  ===&lt;br /&gt;
&lt;br /&gt;
After your acceptence as a VACC Austria controller, anticipate the contact of your dedicated [[Mentor/trainer|mentor]], for further information. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Holding_Management&amp;diff=2134</id>
		<title>Holding Management</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Holding_Management&amp;diff=2134"/>
		<updated>2012-04-21T17:22:49Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Holding management''' is an essential part of providing professional ATC - not only but especially in high traffic situations. This tutorial shows what to keep in mind regarding holdings and includes basics of holdings and advanced holding management. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Definition  ==&lt;br /&gt;
&lt;br /&gt;
A holding (or holding pattern or hold) is a maneuver designated to delay airplanes in flight by keeping them within a specified airspace. Standard holding patterns use right turns, non-standard ones use left turns. Holding patterns may be published on charts (enroute, STARs, approach) or may be given by ATC. Holdings may be anchored on a VOR, VOR/DME, NDB or compass locator, intersection or DME distances. &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Standard Holding Pattern  ==&lt;br /&gt;
&lt;br /&gt;
A standard holding pattern consists of: &lt;br /&gt;
&lt;br /&gt;
*The holding fix &lt;br /&gt;
*A right 180° turn at standard rate (3 degrees/sec) away from the holding fix &lt;br /&gt;
*An outbound leg (standard length: 1 minute below 14000 ft, see below for speed/altitudes) &lt;br /&gt;
*A right 180° turn at standard rate towards the holding fix &lt;br /&gt;
*An inbound leg (standard length: 1 minute)&lt;br /&gt;
&lt;br /&gt;
However, pilots have to correct wind shifts, and therefore there is hardly any &amp;quot;ideal&amp;quot; standard pattern. &lt;br /&gt;
&lt;br /&gt;
[http://upload.wikimedia.org/wikipedia/commons/5/5e/HoldDirectEntry.svg A standard holding pattern] &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== ATC Holding Clearances  ==&lt;br /&gt;
&lt;br /&gt;
A typical ATC holding clearance for a published holding could be: ''&amp;quot;AUA123, enter holding at NERDU as published, maintain FL90, (220 knots), 1 minute leg, expect further clearance at 1015Z.&amp;quot;'' &lt;br /&gt;
&lt;br /&gt;
Of course, there are times when an ATC - for any reason - can't clear a published holding. Possible holding fixes can be any waypoints, VORs or NDBs, also DME distances or the current position. Anyway, as it is a non-published holding, ATC has to give more information so that pilots know how to fly the holding - for example: ''&amp;quot;AUA123, proceed direct and hold at NIGSI, FL110, 2 minutes leg, left orbit, expect further clearance at 1310Z.&amp;quot;'' &lt;br /&gt;
&lt;br /&gt;
For longer holdings keep in mind that the pilot has to crosscheck the EFC-time ('''e'''xpect '''f'''urther '''c'''learance-time) with available fuel (reserves). Note: the EFC-time is always assigned in the USA (FAA procedures), however in most parts of Europe and also in South America ATC never gives EFC-time, especially for shorter holdings (10-20 minutes). However, advising an EFC-time - if possible - is always a service for the pilot and should be done. &lt;br /&gt;
&lt;br /&gt;
ATC has to issue further instructions while the airplane is in the hold if: &lt;br /&gt;
&lt;br /&gt;
*The delay exceeds one hour &lt;br /&gt;
*A revised EFC is necessary &lt;br /&gt;
*Weather is becoming less than the required for the intended approach &lt;br /&gt;
*Other operational information is necessary (eg: airport closed)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Altitudes And Speed Restrictions == &lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;600&amp;quot; border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; cellspacing=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ ICAO holding restrictions &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Altitude segment for holding &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Speed (IAS/Mach) in the holding &lt;br /&gt;
! scope=&amp;quot;col&amp;quot; | Time length of legs&lt;br /&gt;
|-&lt;br /&gt;
| surface to 14,000 ft &lt;br /&gt;
| max. 230 kts &lt;br /&gt;
| 1 minute&lt;br /&gt;
|-&lt;br /&gt;
| 14,001 to 20,000 ft &lt;br /&gt;
| max. 240 kts &lt;br /&gt;
| 1 &amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;/&amp;lt;sub&amp;gt;2&amp;lt;/sub&amp;gt; minutes&lt;br /&gt;
|-&lt;br /&gt;
| 20,001 to 34,000 ft &lt;br /&gt;
| max. 265 kts &lt;br /&gt;
| 1 &amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;/&amp;lt;sub&amp;gt;2&amp;lt;/sub&amp;gt; minutes&lt;br /&gt;
|-&lt;br /&gt;
| above 34,001 ft &lt;br /&gt;
| max. 0,83 Mach&amp;lt;span class=&amp;quot;Apple-tab-span&amp;quot; style=&amp;quot;white-space:pre&amp;quot;&amp;gt;	&amp;lt;/span&amp;gt; &lt;br /&gt;
| 1 &amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;/&amp;lt;sub&amp;gt;2&amp;lt;/sub&amp;gt; minutes&amp;lt;sup&amp;gt;&amp;lt;/sup&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;line-height: normal;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Every published holding has got a minimum holding altitude (MHA) which is noted on the charts. For example, NERDU has an MHA of 5,000 ft (see STAR chart for LOWW here: [http://charts.vacc-austria.org/LOWW/LOWW_Arrival_STAR_08042012.pdf]).&lt;br /&gt;
&lt;br /&gt;
Note that, for operational requirements (e.g. if an extended period of holding is foreseen, to avoid too many “rounds” for passenger comfort or to stay in clean configuration), the pilot may request and ATC grant (if possible), either longer legs (usually 2 minutes) or higher speeds in the holding pattern.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Holding Stack And Separation ==&lt;br /&gt;
&lt;br /&gt;
In periods of very high traffic it may be required that two or more aircraft hold above the same fix.&lt;br /&gt;
In this case ATC must consider:&lt;br /&gt;
*Approach sequence shall be kept unchanged. The aircraft that enters the holding at first, should leave it at first too.&lt;br /&gt;
*Aircraft must be separated 1000 feet vertically.&lt;br /&gt;
*Aircrafts may be advised to descend in the holding if necessary for succeeding approach.&lt;br /&gt;
&lt;br /&gt;
An aircraft may be cleared to a level previously occupied by another aircraft only after the latter has reported vacating it, except when:&lt;br /&gt;
*severe turbulence is known to exist;&lt;br /&gt;
*the higher aircraft is effecting a cruise climb; or&lt;br /&gt;
*the difference in aircraft performance is such that less than the applicable separation minimum may result; in which case such clearance shall be withheld until the aircraft vacating the level has reported at or passing another level separated by the required minimum.&lt;br /&gt;
&lt;br /&gt;
When the aircraft concerned are established in the same holding pattern, consideration shall be given to aircraft descending at markedly different rates and, if necessary, additional measures such as specifying a maximum descent rate for the higher aircraft and a minimum descent rate for the lower aircraft, should be applied to ensure that the required separation is maintained.&lt;br /&gt;
&lt;br /&gt;
Radar separation shall not be applied between aircraft holding over the same holding point!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References  ==&lt;br /&gt;
&lt;br /&gt;
United Virtual Airlines Trainings Departement: Pilot's Guide. Holdings (http://www.united-virtual.com/files/documents/UVA_Guides_HOLDING.pdf)&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Teamspeak&amp;diff=2049</id>
		<title>Teamspeak</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Teamspeak&amp;diff=2049"/>
		<updated>2012-04-03T19:10:17Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: /* Teamspeak 2 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Teamspeak is a voice chat client for the use of communication with friends, pilots and controllers, as well as a trainings tool. Teamspeak is further used for the coordination with other active ATC stations. Active ATC controllers are required to use Teamspeak while on station. &lt;br /&gt;
&lt;br /&gt;
== Teamspeak 2  ==&lt;br /&gt;
&lt;br /&gt;
Download the [http://www.teamspeak.com/?page=downloads&amp;amp;archive=1 Teamspeak 2 Client] and follow the installation routine. &lt;br /&gt;
&lt;br /&gt;
#Open Teamspeak 2&amp;lt;br&amp;gt; &lt;br /&gt;
#Select Connection in the menu bar&amp;lt;br&amp;gt; &lt;br /&gt;
#Local Addressbook Tab&amp;lt;br&amp;gt; &lt;br /&gt;
#Right mouse click&amp;lt;br&amp;gt; &lt;br /&gt;
#Add&amp;amp;nbsp; Server&amp;lt;br&amp;gt; &lt;br /&gt;
#Name it into vacc-austria&amp;lt;br&amp;gt; &lt;br /&gt;
#Now continue on the right side and fill in the following data:&lt;br /&gt;
&amp;lt;pre&amp;gt;Server: ts.vacc-austria.org&lt;br /&gt;
Nickname: &amp;amp;lt;full name&amp;amp;gt;&lt;br /&gt;
Registered: checked&lt;br /&gt;
Loginname: &amp;amp;lt;VACC-Austria Username (full name)&amp;amp;gt;&lt;br /&gt;
Password: &amp;amp;lt;VACC-Austria password&amp;amp;gt; &amp;lt;/pre&amp;gt; &lt;br /&gt;
*Once connected, configure your audio devices. You will find it under Settings-&amp;amp;gt;Options and make sure that you have configured Push to Talk, you will find this option under Settings-&amp;amp;gt;Sound Input/Output Settings.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Teamspeak 3  ==&lt;br /&gt;
&lt;br /&gt;
Currently not used by the vacc Austria.&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1985</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1985"/>
		<updated>2012-03-27T21:26:07Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergencies and abnormal procedures arise from two directions: from the pilots or the ATC- depending where actually they occur. If a pilot gets into trouble then he decleares an emergency. If for example the runway is blocked (damaged aircraft, animals etc.) then the ATC reports abnormal procedures to the surrounding stations.&lt;br /&gt;
&lt;br /&gt;
It is quite common that the emergency call does not come right away. The crew might discover something (an indicator in the cockpit) and follows the letters: DODAR (Diagnose, Options available, Decide, Allocate task, Review). In this case, a short message to ATC is common, that something is wrong:&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Tower, Laipzich Air 123, we have a problem, standby.&lt;br /&gt;
TWR: LHA123, roger.&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''If you are controller and hear this, prepare yourself:''' Oversee the situation, you might wait with the next takeoff clearance, think of scenarios like: where could the aircraft turn back? Which diversion can it reach? The pilot will call you back in a few seconds with precise information.&lt;br /&gt;
&lt;br /&gt;
== Abnormal procedures  ==&lt;br /&gt;
&lt;br /&gt;
=== Pan-pan  ===&lt;br /&gt;
&lt;br /&gt;
Pan-Pan is an urgency announcement of the crew, which is used if an aircraft or its occupence are endangered but not acute at risk (so no need for immediate action), and the crew calls for a preferential treatment. The crew can mostly continue flying under normal or restricted conditions and usually also land regularly.&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;pre&amp;gt;SWR111:&amp;amp;nbsp;  Swissair one-eleven heavy is declaring pan-pan-pan. We have smoke in the cockpit. Request immediate return to a convenient place, I guess Boston.&lt;br /&gt;
CZQM_CTR: Swissair one-eleven heavy, pan-pan received, turn left direct Boston VOR, climb and maintain flight level 310.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Pan-pan is only a message that the crew has to fly under abnormal circumstances and eventually needs a higher priority as non-pan flights.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Radio communication&amp;amp;nbsp;Failure (RCF) ===&lt;br /&gt;
&lt;br /&gt;
You notice RCF at the SQ 7600, which lights up the letters &amp;quot;RDOF&amp;quot; in the aircraft tag of Euroscope. But maybe it is you who discovers RCF first - crew might not know it yet. In this case, assume the aircraft continues as filed, and you have to clear the way.&lt;br /&gt;
&lt;br /&gt;
*First, determine what RDOF it is: does the pilot hear or is his aircraft completely deaf? For this purpose, you ask the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;Controller: Leipzig 123, received radio communication failure. If you read, squawk Ident.&amp;lt;/pre&amp;gt;&lt;br /&gt;
If an ident signal is received, then things are easier: The pilot can receive calls normally, but might need to land priority. If the pilot sends no ident signal, then you (and even more important: the pilot...) needs to know the RCF failure procedures. The airplane will follow this procedure and land. Controller's job is...&lt;br /&gt;
* to get other pilots out of the way&lt;br /&gt;
* to inform other ATC &amp;quot;upstream&amp;quot; about the situation&lt;br /&gt;
* to monitor the aircraft: A RDF failure could turn into an emergency (you don't know, what's all wrong in the plane), and the pilot might not strictly follow the RDF procedure. Remember that the pilot needs the radio for local QNH, which might have changed since departure (local QNH at destination is part of the briefing).&lt;br /&gt;
* to bear in mind that the runway config might have changed and the pilot still approaches the &amp;quot;old&amp;quot; config.&lt;br /&gt;
&lt;br /&gt;
A RDF procedure typically follows the pattern:&lt;br /&gt;
#If the pilot has received the airport info (ATIS or other), then it will follow it (QNH, runway in use). Caution: The only way to determine this is if there has been contact, for example with APP, where the pilot has reported &amp;quot;ATIS on board&amp;quot;.&lt;br /&gt;
#If the pilot has not received it, then it will follow standard runway configuration according to the charts.&lt;br /&gt;
#Typically, procedures include flying standard STAR and transition and flying the minimum altitudes described in the charts. Some airports include holdings for a predetermined time.&lt;br /&gt;
See the RCF procedures for [[http://charts.vacc-austria.org/LOWW/LOWW_Arrival_COM%20Fail%20Procedure_06062011.pdf LOWW]]. Hey guys, where are the RCF procedures for the other LOVV airports?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Go Around and missed approach  ===&lt;br /&gt;
A Go-Around can be seen as abnormal procedure. Two different procedures can be followed:&lt;br /&gt;
#Missed Approach published in the Charts. APP should be informed about it (via teamspeak or PM).&lt;br /&gt;
#Individual handling like heading and altitude. This has to be coordinated with APP.&lt;br /&gt;
Remember: If necessary for safety, TWR can (and must) tell the aircraft virtually anything the aircraft is able to. If the reason for go-around is in the direction of the go-around procedure, then &amp;quot;proceed as published&amp;quot; does not really make sense. TWR might tell the aircraft to turn off left or right immediately.&lt;br /&gt;
&lt;br /&gt;
Phraseology differs according who announces it:&lt;br /&gt;
*If ATC issues go-around, then the phraseology expresses urgency. Listen to the readback - it is vital that the pilot received it. In this example, the go-around is individual:&lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Leipzig 123, go-around, say again go-around, turn left immediately direct SNU, climb 5000ft.&lt;br /&gt;
LHA123:LHA123 is going around, turning left SNU, climbing 5000ft.&amp;lt;/pre&amp;gt;&lt;br /&gt;
*If the pilot goes around, then he/she announces it. In this example, standard go-around pattern is used:&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Lepzig 123 goes around.&lt;br /&gt;
TWR: Roger, Leipzig 123, go around as published&amp;lt;/pre&amp;gt;&lt;br /&gt;
As a courtesy, you could tell the pilot the go-around procedure anyway - many of them don't know it.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Rejected take-off  ===&lt;br /&gt;
&lt;br /&gt;
Rejected take-off procedures can quickly turn into a nasty situation, if ATC does not react immediately and correctly. &lt;br /&gt;
&lt;br /&gt;
====== If the pilot rejects take-off ======&lt;br /&gt;
&lt;br /&gt;
Then the approaching traffic should immediately receive go-around instructions and the APP should be informed about it. Do not expect the aircraft to leave the runway immediately - something serious might be wrong, so be prepared to change the runway (if you have, like in LOWW).&lt;br /&gt;
&lt;br /&gt;
====== If TWR withdraws take-off clearance ======&lt;br /&gt;
&lt;br /&gt;
The situation is even worse, as the aircraft might be rolling already and be beyond v1 where it can't stop (and you as TWR don't know the specific V1 speed). In this case, TWR has to do the following:&lt;br /&gt;
&lt;br /&gt;
If the aircraft has commenced take-off:&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;quot;(Callsign) Stop immediately. I say again (Callsign) stop immediately - acknowledge&amp;quot;.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
If the aircraft has not commenced take-off:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;quot;(Callsign) hold position. Cancel take-off - I say again, cancel take-off - acknowledge&amp;quot;.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*If you have arriving traffic you must assume go-around instructions until the runway is free for the next approaching aircraft.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Malfunctions of airport navigation equipment  ===&lt;br /&gt;
Malfunctions of airport equipment (broken ILS, VOR or NDB) cannot be simulated at VATSIM (navaids are part of pilot software). If an aircraft has broken equipment, then this is actually a &amp;quot;pan-pan&amp;quot; case and should be treated as such. &lt;br /&gt;
&lt;br /&gt;
It could happen that a pilot reports a malfunction (in case his software simulates such a failure - but this failure only affects him. And Still, you could simulate airport malfunctions for all pilots and see, what they will do. In this case, you should know the other approaches available, offer alternatives (and communicate them between TWR and APP). If weather permits, you can offer visual approaches.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Priority Landing  ===&lt;br /&gt;
&lt;br /&gt;
This is an easy case: A fully functional and communicating aircraft has only one grievance: Get down as soon as possible. Most reasons are medical issuse, live organs, low fuel (at too low fuel the pilot will report an emergency), or VIPs on board. Also government flights can request priority handling.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Handling is easy: Issue instructions (vectors, descent, and on ground: a gate close to arrival) that best meet his/her request. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Runway closure  ===&lt;br /&gt;
&lt;br /&gt;
This procedure is triggered by the TWR controller. There are two different cases:&lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''If the runway has to be closed immediately (broken down aircraft, debris, deer, ...), then the runway closure is imminent:&lt;br /&gt;
#approaching traffic receives go-around&lt;br /&gt;
#APP receives request, not to hand off any more aircraft&lt;br /&gt;
#GND receives information to halt taxi clearances to this runway&lt;br /&gt;
#New runway is opened, GND and APP informed (or airport closed)&lt;br /&gt;
#ATIS adapted.&lt;br /&gt;
&lt;br /&gt;
*'''Step-by-step closure:''' If the reason for closure can be forseen (wind changes slowly, noise abatement rules, then the runway closure is more orderly:&lt;br /&gt;
&lt;br /&gt;
#APP receives request not to hand off any more aircraft and/or divert to new runway&lt;br /&gt;
#GND receives request not to issue taxi clearances tot his runway, and the new one&lt;br /&gt;
#Remaining aircraft receive landing clearance&lt;br /&gt;
#New runway will be opened&lt;br /&gt;
#ATIS adapted&lt;br /&gt;
#APP and GND are informed.&lt;br /&gt;
&lt;br /&gt;
== Emergencies -  4 phases ==&lt;br /&gt;
If a pilot discovers a condition of being threatened by serious and/or&lt;br /&gt;
imminent danger '''and''' of requiring immediate assistance, then he/she will issue an emergency call.&lt;br /&gt;
&lt;br /&gt;
A basic principle is important: The pilot is in command, ATC is here to assist. Don't tell the pilot how to fly the aircraft - it's not your job, and you are not there. The pilot says his intentions, and ATC reacts. This does not mean that you don't order the pilot to do things, but they should be according to his/her intentions, not yours.&lt;br /&gt;
&lt;br /&gt;
Mayday procedure has the following phases:&lt;br /&gt;
&lt;br /&gt;
==== 1) Mayday call by the pilot:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123:   Mayday, mayday, mayday. AUA123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: AUA123, emergency received, engine failure. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Pilot calls &amp;quot;mayday&amp;quot; three times, the nature of his/her emergency, what his/her intentions are and what he/she needs now. ATC reads back the emergency. &lt;br /&gt;
&lt;br /&gt;
*Please, do not advise the pilot to set squawk 7700, the current problem on bord is bigger than a wrong squawk code.&lt;br /&gt;
&lt;br /&gt;
==== 2) standard response by ATC  ====&lt;br /&gt;
The pilot has a few seconds to do (avigate, navigate), and ATC too: He/she needs to inform other pilots and fellow ATC stations.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&amp;lt;/pre&amp;gt;&lt;br /&gt;
With this call pilots know: They should continue as told (their SID, transitions, STAR). They only call ATC, if safety is at stake. If they receive ATC orders, they don't read back - they just do it.&lt;br /&gt;
&lt;br /&gt;
Then ATC informs other controllers via intercom, Text or teamspeak, and collects the necessary information.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Generally, the controller makes sure that he/she does not get any traffic any more: no takeoffs from below, no handoffs from above.&lt;br /&gt;
&lt;br /&gt;
Beyond this point, there is no fixed phraseology. ATC speaks with pilots to make sure that he is served best. With the information gathered, ATC will turn back to the pilot and figure out next steps.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, for runway 11 maintain present heading, wind 320°4kt. When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
ATC's information is important to pilots: Where can I land and how far it is? Pilots say, that accurate distance is vital, so use the distance tool on your scope.&lt;br /&gt;
&lt;br /&gt;
The pilot's first information is important for controllers: What is wrong? That says a lot about the ability of the pilot to control the aircraft. The last info is important for real life: Emergency services on the ground need to prepare for rescue.&lt;br /&gt;
&lt;br /&gt;
==== 3) All following measures  ====&lt;br /&gt;
There is no strict rules beyond the standard response. Pilot and ATC communicate the way that suits best their situation. The following guidelines are vital:&lt;br /&gt;
*'''Pilot tells, ATC delivers.''' On the flight plan, you read &amp;quot;PIC - pilot in command&amp;quot; - let him stay in command, and let him decide, which command he wants you to take over.&lt;br /&gt;
*'''Communication: least possible, as precise as possible.''' During an emergency, the cockpit is a beehouse. The more time pilots have for themselves, the better. If a pilot does not answer: stay calm - the pilot might follow the rule 1-avigate 2-navigate 3-communicate and might not have reached step 3. He/she may say &amp;quot;ATC standby&amp;quot; or just nothing. To quote a real-life example: [[http://www.youtube.com/watch?v=lICb8p9SvvM don't do this.]]&lt;br /&gt;
*'''Clear needed airspace:''' Noone needs to turn away, if he/she is not in the way. Some traffic might continue as normal. You might consider premature handoffs to other controllers or holdings. As a rule of thumb: don't produce more emergencies than you have already.&lt;br /&gt;
*'''Pilot has the choice of frequency:''' An aircraft can stay on the frequency (eg. TWR) through all stages of his/her emergency or change, if he/she wishes. ATC will adjust. Assume that you have an engine failure at FL100 approaching LOWW. The pilot is on the APP frequency and does not want to change. Either APP coordinates with TWR landing clearance and issues it, or TWR enters the APP frequency and issues landing clearance him/herself.&lt;br /&gt;
&lt;br /&gt;
==== 4)&amp;amp;nbsp;End emergency procedure  ====&lt;br /&gt;
At some stage, the emergency is over, and the aircraft is happily on the runway or unhappy in the wood. At this stage, all other pilots and ATC need to know that it is over:&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Then, cleanup starts: There might be a dozen aircraft in holdings to bring in, runways to clean and aircraft on ground to get out.&lt;br /&gt;
&lt;br /&gt;
== Emergencies - the cases ==&lt;br /&gt;
This list is open - be prepared to react to the unusual. If you discover an emergency which is not covered here, feel free to add it.&lt;br /&gt;
=== Loss of Cabin pressure  ===&lt;br /&gt;
&lt;br /&gt;
This could be a problem in high traffic situations. The pilot will immediately begin an &amp;quot;emergency descent&amp;quot; to FL100 or below (he won't wait for approval). As controller, you can expect that the pilot wants to land as soon as possible. Be prepared that the emergency situation escalates, as there is a reason for the loss of cabin pressure which could cause other systems to fail too.&lt;br /&gt;
&lt;br /&gt;
=== Loss of Hydraulicpressure  ===&lt;br /&gt;
&lt;br /&gt;
This is a major problem, depending on the degree of failure: On large aircraft, all systems for manoever depend on hydraulic pressure. First thing after the usual introduction is to ask the pilot about his/her status - which systems are affected and what this means. It could mean that the pilot cannot deploy speedbrakes (that's trivial) or flaps (that means a long runout on the runway), or cannot perform certain manoevers (like left or right turn etc, or that the plane reacts very slow. As ATC, you should offer the nearest suitable airport and increase separation. Also a loss of hydraulic pressure can escalate quickly into a worse emergency.&lt;br /&gt;
&lt;br /&gt;
===Electrics failure===&lt;br /&gt;
... means that the aircraft has very short time in the air. If all systems rely on battery, it will be drained quickly. &lt;br /&gt;
*Pilots will most likely want the closest suitable airfield.&lt;br /&gt;
*A major power consumer is radio communication. Consider offering solutions which need very short answers.&lt;br /&gt;
*Navigational aids may fail without power. Consider vectors for routing, and monitor headings, as instruments in the cockpit might fail.&lt;br /&gt;
*Expect abnormal approach procedures - shortened, steeper, but maybe with smaller bank angles - the pilot will tell what he is able to.&lt;br /&gt;
&lt;br /&gt;
=== Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Smoke in cockpit is a very challenging situation. The best way is not to lose overview in the situation. Time is critical - the aircraft has to come down really quickly. Contrary to other emergencies, smoke in cockpit means a &amp;quot;talk-down&amp;quot; approach. Supply the pilot with vectors and distance to the nearest airfield. You might consider to supply the pilot with vital information (it could be that he/she cannot see his/her instruments)in regular intervals (minutes or less), like:&lt;br /&gt;
&amp;lt;pre&amp;gt;Mayday Leipzig 123, speed 220 ok, altitude 6000ft ok, heading ok, runway 11 miles&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Such an emergency should definitely land at the next suitable aerodrome, and maybe on a separate runway in case anything goes wrong. Increase separation considerably.&lt;br /&gt;
&lt;br /&gt;
=== Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Engine failures are the most dangerous incidents that can happen: Altitude over ground is low, the aircraft is at full thrust and full of fuel, speed is low. This is the cocktail for a nasty situation. Most frequent reason is bird strike.&lt;br /&gt;
&lt;br /&gt;
Most likely, the bird strike happened already on ground above v1, and the aircraft has to get into the air with reduced engine power. Therefore, TWR is most likely to receive the mayday call. High insecurity adds to this, as it may take time to assess the degree of damage. How much thrust is still left? Is climbing an option? Does the aircraft need to make an emergency U-turn or does it have enough time for a controlled approach?&lt;br /&gt;
&lt;br /&gt;
Workload in the cockpit is very high. Quick, short response and coordination is the key to this situation. More important than in any other situation is to offer solutions, but let the pilot decide. The pilot will tell you, what he is able to and what his intentions are. &lt;br /&gt;
&lt;br /&gt;
Be prepared that the aircraft may not follow the filed SID. It will most likely climb slower, step-climb and need a larger turn radius. In turns, the rate of descent might double.&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=9KhZwsYtNDE Here is a perfect example], how it should work: &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;as precise as possible:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Answer ATC:&amp;amp;nbsp;As precise as possible (listen: Thomson 253H has not requested anything, so TWR is offering the prime information which the pilot needs now):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warns all other stations ans waits. the pilot is &amp;quot;in command&amp;quot;, he will call. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Pilot has called, now TWR offers solutions. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Now the pilot says his intentions: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower reads back and done. If the pilot does not want anything else, then TWR keeps quiet. He knows that the pilot will fly a controlled approach via a VOR (Afterwards we will see that his right engine is dead while the left one runs normally - far enough for a modern aircraft to take off and climb). Shortly later he makes the offer to land in Liverpool - which is turned down - the pilot is happy with returning to Manchester. Then TWR reports runway 06R closed because of debris - the aircraft has lost parts of its engine. This is an order to the pilot - he should not land on a closed runway. A short time afterwards, the aircraft lands orderly on 06L.&lt;br /&gt;
&lt;br /&gt;
=== Engine Failure at approach - Triebwerksversagen beim Landeanflug  ===&lt;br /&gt;
&lt;br /&gt;
===Total engine failure===&lt;br /&gt;
For ATC, this is easy, as it means: This aircraft will come down very quickly. In this situation, workload in the cockpit is enormous, as they try to re-light the engines. ATC's job is to analyse every option to reach ground safely and offer them in sequence of relevance.&lt;br /&gt;
&lt;br /&gt;
===(Very) low fuel===&lt;br /&gt;
If fuel is gone, then this is the same situation as a complete engine failure. If such a situation is possible or even likely (=if it could happen within the distance between aircraft and airport), then the aircraft has to be routed to the nearest runway threshold. Again - the pilot decides, bearing in mind that steep turns cost altitude. If no runway can be reached, then anything like it is better than nothing - a taxiway maybe. As ATC, do not allow the aircraft to endanger other aircraft or people.&lt;br /&gt;
&lt;br /&gt;
===Directional Gyro Failure===&lt;br /&gt;
The directional gyro is the &amp;quot;compass&amp;quot; of the aircraft. If the directional gyro fails, then the pilot does not know any more, where north is. Most likely, you as ATC will notice first that the aircraft goes into strange circles.&lt;br /&gt;
*Normally, aircraft have a standard mechanic magnetic compass in sight - a simple ball. This is not enough to fly a vector, but good enough to fly a visual approach.&lt;br /&gt;
*(it happened to me once) If the pilot has no compass (or iPhone) to look at, then the ground is the only possible visual reference. ATC can approve descent to minimum altitude until ground contact. Then, incremental turns can be issued: &amp;quot;turn 20° left from present heading&amp;quot; - until runway is in sight.&lt;br /&gt;
&lt;br /&gt;
===Landing gear failure===&lt;br /&gt;
*If landing gear fails to retract after takeoff, then this is a pan-pan situation. Crew can continue normally, but with reduced speed and more fuel consumption - crew will recalculate if they need a diversion. For ATC this means to accomodate crew's wishes.&lt;br /&gt;
*A broken tyre could prevent the aircraft from retracting the gear. Landing with a flat tyre is already an emergency, as the aircraft could become unstable after touchdown. For ATC this means: Clear the runway, increase spacing behind and alert fire services.&lt;br /&gt;
*If the aircraft fails to expand gear, then the situation is more critical. The only thing pilot see is their warning lights (they can't get out and see). This will occur in the last 10miles final. First reaction is a go-around to gain time to analyse the problem. In real life, the aircraft performs a low approach and technicians look at the aircraft from below. If gear fails to expand properly, then an attempted landing is imminent (at some point, the aircraf ''must'' land). This is an emergency. For ATC: Clear the runway, increace spacing behind and alert fire services.&lt;br /&gt;
&lt;br /&gt;
=== THIS PART AWAITS MORE. DO YOU KNOW MORE? ===&lt;br /&gt;
&lt;br /&gt;
=== Multiple emergencies ===&lt;br /&gt;
There is nothing more challenging than multiple emergencies, as you as controller have to rank its severity and propose measures that all of them can accomodated. If emergencies collide, you have to set priorities:&lt;br /&gt;
*Aircraft which risk to go down soon have priority to those which can still fly for a few minutes (all-engine failure is first compared to hydraulics failure).&lt;br /&gt;
*Aircraft which need to be on the ground first are first (passenger with heart attack is first compared to low - but not empty - fuel).&lt;br /&gt;
*More people saved is better than less (full engine failure has priority compared with a passenger with heart attack).&lt;br /&gt;
Nothing is heavier than taking these decisions. Let's be happy to fly online.&lt;br /&gt;
&lt;br /&gt;
=Further reading=&lt;br /&gt;
A [[http://www.skybrary.aero/bookshelf/books/200.pdf brochure by the British Air Traffic Authorities]] is an excellent reference for controllers.&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1984</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1984"/>
		<updated>2012-03-27T21:19:24Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergencies and abnormal procedures arise from two directions: from the pilots or the ATC- depending where actually they occur. If a pilot gets into trouble then he decleares an emergency. If for example the runway is blocked (damaged aircraft, animals etc.) then the ATC reports abnormal procedures to the surrounding stations.&lt;br /&gt;
&lt;br /&gt;
It is quite common that the emergency call does not come right away. The crew might discover something (an indicator in the cockpit) and follows the letters: DODAR (Diagnose, Options available, Decide, Allocate task, Review). In this case, a short message to ATC is common, that something is wrong:&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Tower, Laipzich Air 123, we have a problem, standby.&lt;br /&gt;
TWR: LHA123, roger.&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''If you are controller and hear this, prepare yourself:''' Oversee the situation, you might wait with the next takeoff clearance, think of scenarios like: where could the aircraft turn back? Which diversion can it reach? The pilot will call you back in a few seconds with precise information.&lt;br /&gt;
&lt;br /&gt;
== Abnormal procedures  ==&lt;br /&gt;
&lt;br /&gt;
=== Pan-pan  ===&lt;br /&gt;
&lt;br /&gt;
Pan-Pan is an urgency announcement of the crew, which is used if an aircraft or its occupence are endangered but not acute at risk (so no need for immediate action), and the crew calls for a preferential treatment. The crew can mostly continue flying under normal or restricted conditions and usually also land regularly.&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;pre&amp;gt;SWR111:&amp;amp;nbsp;  Swissair one-eleven heavy is declaring pan-pan-pan. We have smoke in the cockpit. Request immediate return to a convenient place, I guess Boston.&lt;br /&gt;
CZQM_CTR: Swissair one-eleven heavy, pan-pan received, turn left direct Boston VOR, climb and maintain flight level 310.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Pan-pan is only a message that the crew has to fly under abnormal circumstances and eventually needs a higher priority as non-pan flights.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Radio communication&amp;amp;nbsp;Failure (RCF) ===&lt;br /&gt;
&lt;br /&gt;
You notice RCF at the SQ 7600, which lights up the letters &amp;quot;RDOF&amp;quot; in the aircraft tag of Euroscope. But maybe it is you who discovers RCF first - crew might not know it yet. In this case, assume the aircraft continues as filed, and you have to clear the way.&lt;br /&gt;
&lt;br /&gt;
*First, determine what RDOF it is: does the pilot hear or is his aircraft completely deaf? For this purpose, you ask the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;Controller: Leipzig 123, received radio communication failure. If you read, squawk Ident.&amp;lt;/pre&amp;gt;&lt;br /&gt;
If an ident signal is received, then things are easier: The pilot can receive calls normally, but might need to land priority. If the pilot sends no ident signal, then you (and even more important: the pilot...) needs to know the RCF failure procedures. The airplane will follow this procedure and land. Controller's job is...&lt;br /&gt;
* to get other pilots out of the way&lt;br /&gt;
* to inform other ATC &amp;quot;upstream&amp;quot; about the situation&lt;br /&gt;
* to monitor the aircraft: A RDF failure could turn into an emergency (you don't know, what's all wrong in the plane), and the pilot might not strictly follow the RDF procedure. Remember that the pilot needs the radio for local QNH, which might have changed since departure (local QNH at destination is part of the briefing).&lt;br /&gt;
* to bear in mind that the runway config might have changed and the pilot still approaches the &amp;quot;old&amp;quot; config.&lt;br /&gt;
&lt;br /&gt;
A RDF procedure typically follows the pattern:&lt;br /&gt;
#If the pilot has received the airport info (ATIS or other), then it will follow it (QNH, runway in use). Caution: The only way to determine this is if there has been contact, for example with APP, where the pilot has reported &amp;quot;ATIS on board&amp;quot;.&lt;br /&gt;
#If the pilot has not received it, then it will follow standard runway configuration according to the charts.&lt;br /&gt;
#Typically, procedures include flying standard STAR and transition and flying the minimum altitudes described in the charts. Some airports include holdings for a predetermined time.&lt;br /&gt;
See the RCF procedures for [[http://charts.vacc-austria.org/LOWW/LOWW_Arrival_COM%20Fail%20Procedure_06062011.pdf LOWW]]. Hey guys, where are the RCF procedures for the other LOVV airports?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Go Around and missed approach  ===&lt;br /&gt;
A Go-Around can be seen as abnormal procedure. Two different procedures can be followed:&lt;br /&gt;
#Missed Approach published in the Charts. APP should be informed about it (via teamspeak or PM).&lt;br /&gt;
#Individual handling like heading and altitude. This has to be coordinated with APP.&lt;br /&gt;
Remember: If necessary for safety, TWR can (and must) tell the aircraft virtually anything the aircraft is able to. If the reason for go-around is in the direction of the go-around procedure, then &amp;quot;proceed as published&amp;quot; does not really make sense. TWR might tell the aircraft to turn off left or right immediately.&lt;br /&gt;
&lt;br /&gt;
Phraseology differs according who announces it:&lt;br /&gt;
*If ATC issues go-around, then the phraseology expresses urgency. Listen to the readback - it is vital that the pilot received it. In this example, the go-around is individual:&lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Leipzig 123, go-around, say again go-around, turn left immediately direct SNU, climb 5000ft.&lt;br /&gt;
LHA123:LHA123 is going around, turning left SNU, climbing 5000ft.&amp;lt;/pre&amp;gt;&lt;br /&gt;
*If the pilot goes around, then he/she announces it. In this example, standard go-around pattern is used:&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Lepzig 123 goes around.&lt;br /&gt;
TWR: Roger, Leipzig 123, go around as published&amp;lt;/pre&amp;gt;&lt;br /&gt;
As a courtesy, you could tell the pilot the go-around procedure anyway - many of them don't know it.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Rejected take-off  ===&lt;br /&gt;
&lt;br /&gt;
Rejected take-off procedures can quickly turn into a nasty situation, if ATC does not react immediately and correctly. &lt;br /&gt;
&lt;br /&gt;
====== If the pilot rejects take-off ======&lt;br /&gt;
&lt;br /&gt;
Then the approaching traffic should immediately receive go-around instructions and the APP should be informed about it. Do not expect the aircraft to leave the runway immediately - something serious might be wrong, so be prepared to change the runway (if you have, like in LOWW).&lt;br /&gt;
&lt;br /&gt;
====== If TWR withdraws take-off clearance ======&lt;br /&gt;
&lt;br /&gt;
The situation is even worse, as the aircraft might be rolling already and be beyond v1 where it can't stop (and you as TWR don't know the specific V1 speed). In this case, TWR has to do the following:&lt;br /&gt;
&lt;br /&gt;
If the aircraft has commenced take-off:&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;quot;(Callsign) Stop immediately. I say again (Callsign) stop immediately - acknowledge&amp;quot;.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
If the aircraft has not commenced take-off:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;quot;(Callsign) hold position. Cancel take-off - I say again, cancel take-off - acknowledge&amp;quot;.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*If you have arriving traffic you must assume go-around instructions until the runway is free for the next approaching aircraft.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Malfunctions of airport navigation equipment  ===&lt;br /&gt;
Malfunctions of airport equipment (broken ILS, VOR or NDB) cannot be simulated at VATSIM (navaids are part of pilot software). If an aircraft has broken equipment, then this is actually a &amp;quot;pan-pan&amp;quot; case and should be treated as such. &lt;br /&gt;
&lt;br /&gt;
It could happen that a pilot reports a malfunction (in case his software simulates such a failure - but this failure only affects him. And Still, you could simulate airport malfunctions for all pilots and see, what they will do. In this case, you should know the other approaches available, offer alternatives (and communicate them between TWR and APP). If weather permits, you can offer visual approaches.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Priority Landing  ===&lt;br /&gt;
&lt;br /&gt;
This is an easy case: A fully functional and communicating aircraft has only one grievance: Get down as soon as possible. Most reasons are medical issuse, live organs, low fuel (at too low fuel the pilot will report an emergency), or VIPs on board. Also government flights can request priority handling.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Handling is easy: Issue instructions (vectors, descent, and on ground: a gate close to arrival) that best meet his/her request. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Runway closure  ===&lt;br /&gt;
&lt;br /&gt;
This procedure is triggered by the TWR controller. There are two different cases:&lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''If the runway has to be closed immediately (broken down aircraft, debris, deer, ...), then the runway closure is imminent:&lt;br /&gt;
#approaching traffic receives go-around&lt;br /&gt;
#APP receives request, not to hand off any more aircraft&lt;br /&gt;
#GND receives information to halt taxi clearances to this runway&lt;br /&gt;
#New runway is opened, GND and APP informed (or airport closed)&lt;br /&gt;
#ATIS adapted.&lt;br /&gt;
&lt;br /&gt;
*'''Step-by-step closure:''' If the reason for closure can be forseen (wind changes slowly, noise abatement rules, then the runway closure is more orderly:&lt;br /&gt;
&lt;br /&gt;
#APP receives request not to hand off any more aircraft and/or divert to new runway&lt;br /&gt;
#GND receives request not to issue taxi clearances tot his runway, and the new one&lt;br /&gt;
#Remaining aircraft receive landing clearance&lt;br /&gt;
#New runway will be opened&lt;br /&gt;
#ATIS adapted&lt;br /&gt;
#APP and GND are informed.&lt;br /&gt;
&lt;br /&gt;
== Emergencies -  4 phases ==&lt;br /&gt;
If a pilot discovers a condition of being threatened by serious and/or&lt;br /&gt;
imminent danger '''and''' of requiring immediate assistance, then he/she will issue an emergency call.&lt;br /&gt;
&lt;br /&gt;
A basic principle is important: The pilot is in command, ATC is here to assist. Don't tell the pilot how to fly the aircraft - it's not your job, and you are not there. The pilot says his intentions, and ATC reacts. This does not mean that you don't order the pilot to do things, but they should be according to his/her intentions, not yours.&lt;br /&gt;
&lt;br /&gt;
Mayday procedure has the following phases:&lt;br /&gt;
&lt;br /&gt;
==== 1) Mayday call by the pilot:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Pilot calls &amp;quot;mayday&amp;quot; three times, the nature of his/her emergency, what his/her intentions are and what he/she needs now. ATC reads back, tells him to set transponder to 7700 (then all ATC see his mayday call on the Euroscope screen: The tag turns red and is preceded with &amp;quot;EMG&amp;quot;). Then the aircraft gets the needed information.&lt;br /&gt;
&lt;br /&gt;
==== 2) standard response by ATC  ====&lt;br /&gt;
The pilot has a few seconds to do (avigate, navigate), and ATC too: He/she needs to inform other pilots and fellow ATC stations.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&amp;lt;/pre&amp;gt;&lt;br /&gt;
With this call pilots know: They should continue as told (their SID, transitions, STAR). They only call ATC, if safety is at stake. If they receive ATC orders, they don't read back - they just do it.&lt;br /&gt;
&lt;br /&gt;
Then ATC informs other controllers via intercom, Text or teamspeak, and collects the necessary information.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Generally, the controller makes sure that he/she does not get any traffic any more: no takeoffs from below, no handoffs from above.&lt;br /&gt;
&lt;br /&gt;
Beyond this point, there is no fixed phraseology. ATC speaks with pilots to make sure that he is served best. With the information gathered, ATC will turn back to the pilot and figure out next steps.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, for runway 11 maintain present heading, wind 320°4kt. When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
ATC's information is important to pilots: Where can I land and how far it is? Pilots say, that accurate distance is vital, so use the distance tool on your scope.&lt;br /&gt;
&lt;br /&gt;
The pilot's first information is important for controllers: What is wrong? That says a lot about the ability of the pilot to control the aircraft. The last info is important for real life: Emergency services on the ground need to prepare for rescue.&lt;br /&gt;
&lt;br /&gt;
==== 3) All following measures  ====&lt;br /&gt;
There is no strict rules beyond the standard response. Pilot and ATC communicate the way that suits best their situation. The following guidelines are vital:&lt;br /&gt;
*'''Pilot tells, ATC delivers.''' On the flight plan, you read &amp;quot;PIC - pilot in command&amp;quot; - let him stay in command, and let him decide, which command he wants you to take over.&lt;br /&gt;
*'''Communication: least possible, as precise as possible.''' During an emergency, the cockpit is a beehouse. The more time pilots have for themselves, the better. If a pilot does not answer: stay calm - the pilot might follow the rule 1-avigate 2-navigate 3-communicate and might not have reached step 3. He/she may say &amp;quot;ATC standby&amp;quot; or just nothing. To quote a real-life example: [[http://www.youtube.com/watch?v=lICb8p9SvvM don't do this.]]&lt;br /&gt;
*'''Clear needed airspace:''' Noone needs to turn away, if he/she is not in the way. Some traffic might continue as normal. You might consider premature handoffs to other controllers or holdings. As a rule of thumb: don't produce more emergencies than you have already.&lt;br /&gt;
*'''Pilot has the choice of frequency:''' An aircraft can stay on the frequency (eg. TWR) through all stages of his/her emergency or change, if he/she wishes. ATC will adjust. Assume that you have an engine failure at FL100 approaching LOWW. The pilot is on the APP frequency and does not want to change. Either APP coordinates with TWR landing clearance and issues it, or TWR enters the APP frequency and issues landing clearance him/herself.&lt;br /&gt;
&lt;br /&gt;
==== 4)&amp;amp;nbsp;End emergency procedure  ====&lt;br /&gt;
At some stage, the emergency is over, and the aircraft is happily on the runway or unhappy in the wood. At this stage, all other pilots and ATC need to know that it is over:&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Then, cleanup starts: There might be a dozen aircraft in holdings to bring in, runways to clean and aircraft on ground to get out.&lt;br /&gt;
&lt;br /&gt;
== Emergencies - the cases ==&lt;br /&gt;
This list is open - be prepared to react to the unusual. If you discover an emergency which is not covered here, feel free to add it.&lt;br /&gt;
=== Loss of Cabin pressure  ===&lt;br /&gt;
&lt;br /&gt;
This could be a problem in high traffic situations. The pilot will immediately begin an &amp;quot;emergency descent&amp;quot; to FL100 or below (he won't wait for approval). As controller, you can expect that the pilot wants to land as soon as possible. Be prepared that the emergency situation escalates, as there is a reason for the loss of cabin pressure which could cause other systems to fail too.&lt;br /&gt;
&lt;br /&gt;
=== Loss of Hydraulicpressure  ===&lt;br /&gt;
&lt;br /&gt;
This is a major problem, depending on the degree of failure: On large aircraft, all systems for manoever depend on hydraulic pressure. First thing after the usual introduction is to ask the pilot about his/her status - which systems are affected and what this means. It could mean that the pilot cannot deploy speedbrakes (that's trivial) or flaps (that means a long runout on the runway), or cannot perform certain manoevers (like left or right turn etc, or that the plane reacts very slow. As ATC, you should offer the nearest suitable airport and increase separation. Also a loss of hydraulic pressure can escalate quickly into a worse emergency.&lt;br /&gt;
&lt;br /&gt;
===Electrics failure===&lt;br /&gt;
... means that the aircraft has very short time in the air. If all systems rely on battery, it will be drained quickly. &lt;br /&gt;
*Pilots will most likely want the closest suitable airfield.&lt;br /&gt;
*A major power consumer is radio communication. Consider offering solutions which need very short answers.&lt;br /&gt;
*Navigational aids may fail without power. Consider vectors for routing, and monitor headings, as instruments in the cockpit might fail.&lt;br /&gt;
*Expect abnormal approach procedures - shortened, steeper, but maybe with smaller bank angles - the pilot will tell what he is able to.&lt;br /&gt;
&lt;br /&gt;
=== Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Smoke in cockpit is a very challenging situation. The best way is not to lose overview in the situation. Time is critical - the aircraft has to come down really quickly. Contrary to other emergencies, smoke in cockpit means a &amp;quot;talk-down&amp;quot; approach. Supply the pilot with vectors and distance to the nearest airfield. You might consider to supply the pilot with vital information (it could be that he/she cannot see his/her instruments)in regular intervals (minutes or less), like:&lt;br /&gt;
&amp;lt;pre&amp;gt;Mayday Leipzig 123, speed 220 ok, altitude 6000ft ok, heading ok, runway 11 miles&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Such an emergency should definitely land at the next suitable aerodrome, and maybe on a separate runway in case anything goes wrong. Increase separation considerably.&lt;br /&gt;
&lt;br /&gt;
=== Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Engine failures are the most dangerous incidents that can happen: Altitude over ground is low, the aircraft is at full thrust and full of fuel, speed is low. This is the cocktail for a nasty situation. Most frequent reason is bird strike.&lt;br /&gt;
&lt;br /&gt;
Most likely, the bird strike happened already on ground above v1, and the aircraft has to get into the air with reduced engine power. Therefore, TWR is most likely to receive the mayday call. High insecurity adds to this, as it may take time to assess the degree of damage. How much thrust is still left? Is climbing an option? Does the aircraft need to make an emergency U-turn or does it have enough time for a controlled approach?&lt;br /&gt;
&lt;br /&gt;
Workload in the cockpit is very high. Quick, short response and coordination is the key to this situation. More important than in any other situation is to offer solutions, but let the pilot decide. The pilot will tell you, what he is able to and what his intentions are. &lt;br /&gt;
&lt;br /&gt;
Be prepared that the aircraft may not follow the filed SID. It will most likely climb slower, step-climb and need a larger turn radius. In turns, the rate of descent might double.&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=9KhZwsYtNDE Here is a perfect example], how it should work: &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;as precise as possible:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Answer ATC:&amp;amp;nbsp;As precise as possible (listen: Thomson 253H has not requested anything, so TWR is offering the prime information which the pilot needs now):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warns all other stations ans waits. the pilot is &amp;quot;in command&amp;quot;, he will call. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Pilot has called, now TWR offers solutions. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Now the pilot says his intentions: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower reads back and done. If the pilot does not want anything else, then TWR keeps quiet. He knows that the pilot will fly a controlled approach via a VOR (Afterwards we will see that his right engine is dead while the left one runs normally - far enough for a modern aircraft to take off and climb). Shortly later he makes the offer to land in Liverpool - which is turned down - the pilot is happy with returning to Manchester. Then TWR reports runway 06R closed because of debris - the aircraft has lost parts of its engine. This is an order to the pilot - he should not land on a closed runway. A short time afterwards, the aircraft lands orderly on 06L.&lt;br /&gt;
&lt;br /&gt;
=== Engine Failure at approach - Triebwerksversagen beim Landeanflug  ===&lt;br /&gt;
&lt;br /&gt;
===Total engine failure===&lt;br /&gt;
For ATC, this is easy, as it means: This aircraft will come down very quickly. In this situation, workload in the cockpit is enormous, as they try to re-light the engines. ATC's job is to analyse every option to reach ground safely and offer them in sequence of relevance.&lt;br /&gt;
&lt;br /&gt;
===(Very) low fuel===&lt;br /&gt;
If fuel is gone, then this is the same situation as a complete engine failure. If such a situation is possible or even likely (=if it could happen within the distance between aircraft and airport), then the aircraft has to be routed to the nearest runway threshold. Again - the pilot decides, bearing in mind that steep turns cost altitude. If no runway can be reached, then anything like it is better than nothing - a taxiway maybe. As ATC, do not allow the aircraft to endanger other aircraft or people.&lt;br /&gt;
&lt;br /&gt;
===Directional Gyro Failure===&lt;br /&gt;
The directional gyro is the &amp;quot;compass&amp;quot; of the aircraft. If the directional gyro fails, then the pilot does not know any more, where north is. Most likely, you as ATC will notice first that the aircraft goes into strange circles.&lt;br /&gt;
*Normally, aircraft have a standard mechanic magnetic compass in sight - a simple ball. This is not enough to fly a vector, but good enough to fly a visual approach.&lt;br /&gt;
*(it happened to me once) If the pilot has no compass (or iPhone) to look at, then the ground is the only possible visual reference. ATC can approve descent to minimum altitude until ground contact. Then, incremental turns can be issued: &amp;quot;turn 20° left from present heading&amp;quot; - until runway is in sight.&lt;br /&gt;
&lt;br /&gt;
===Landing gear failure===&lt;br /&gt;
*If landing gear fails to retract after takeoff, then this is a pan-pan situation. Crew can continue normally, but with reduced speed and more fuel consumption - crew will recalculate if they need a diversion. For ATC this means to accomodate crew's wishes.&lt;br /&gt;
*A broken tyre could prevent the aircraft from retracting the gear. Landing with a flat tyre is already an emergency, as the aircraft could become unstable after touchdown. For ATC this means: Clear the runway, increase spacing behind and alert fire services.&lt;br /&gt;
*If the aircraft fails to expand gear, then the situation is more critical. The only thing pilot see is their warning lights (they can't get out and see). This will occur in the last 10miles final. First reaction is a go-around to gain time to analyse the problem. In real life, the aircraft performs a low approach and technicians look at the aircraft from below. If gear fails to expand properly, then an attempted landing is imminent (at some point, the aircraf ''must'' land). This is an emergency. For ATC: Clear the runway, increace spacing behind and alert fire services.&lt;br /&gt;
&lt;br /&gt;
=== THIS PART AWAITS MORE. DO YOU KNOW MORE? ===&lt;br /&gt;
&lt;br /&gt;
=== Multiple emergencies ===&lt;br /&gt;
There is nothing more challenging than multiple emergencies, as you as controller have to rank its severity and propose measures that all of them can accomodated. If emergencies collide, you have to set priorities:&lt;br /&gt;
*Aircraft which risk to go down soon have priority to those which can still fly for a few minutes (all-engine failure is first compared to hydraulics failure).&lt;br /&gt;
*Aircraft which need to be on the ground first are first (passenger with heart attack is first compared to low - but not empty - fuel).&lt;br /&gt;
*More people saved is better than less (full engine failure has priority compared with a passenger with heart attack).&lt;br /&gt;
Nothing is heavier than taking these decisions. Let's be happy to fly online.&lt;br /&gt;
&lt;br /&gt;
=Further reading=&lt;br /&gt;
A [[http://www.skybrary.aero/bookshelf/books/200.pdf brochure by the British Air Traffic Authorities]] is an excellent reference for controllers.&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1983</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1983"/>
		<updated>2012-03-27T21:14:25Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: /* Rejected Take-off */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergencies and abnormal procedures arise from two directions: from the pilots or the ATC- depending where actually they occur. If a pilot gets into trouble then he decleares an emergency. If for example the runway is blocked (damaged aircraft, animals etc.) then the ATC reports abnormal procedures to the surrounding stations.&lt;br /&gt;
&lt;br /&gt;
It is quite common that the emergency call does not come right away. The crew might discover something (an indicator in the cockpit) and follows the letters: DODAR (Diagnose, Options available, Decide, Allocate task, Review). In this case, a short message to ATC is common, that something is wrong:&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Tower, Laipzich Air 123, we have a problem, standby.&lt;br /&gt;
TWR: LHA123, roger.&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''If you are controller and hear this, prepare yourself:''' Oversee the situation, you might wait with the next takeoff clearance, think of scenarios like: where could the aircraft turn back? Which diversion can it reach? The pilot will call you back in a few seconds with precise information.&lt;br /&gt;
&lt;br /&gt;
== Abnormal procedures  ==&lt;br /&gt;
&lt;br /&gt;
=== Pan-pan  ===&lt;br /&gt;
&lt;br /&gt;
Pan-Pan is an urgency announcement of the crew, which is used if an aircraft or its occupence are endangered but not acute at risk (so no need for immediate action), and the crew calls for a preferential treatment. The crew can mostly continue flying under normal or restricted conditions and usually also land regularly.&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;pre&amp;gt;SWR111:&amp;amp;nbsp;  Swissair one-eleven heavy is declaring pan-pan-pan. We have smoke in the cockpit. Request immediate return to a convenient place, I guess Boston.&lt;br /&gt;
CZQM_CTR: Swissair one-eleven heavy, pan-pan received, turn left direct Boston VOR, climb and maintain flight level 310.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Pan-pan is only a message that the crew has to fly under abnormal circumstances and eventually needs a higher priority as non-pan flights.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Radio communication&amp;amp;nbsp;Failure (RCF) ===&lt;br /&gt;
&lt;br /&gt;
You notice RCF at the SQ 7600, which lights up the letters &amp;quot;RDOF&amp;quot; in the aircraft tag of Euroscope. But maybe it is you who discovers RCF first - crew might not know it yet. In this case, assume the aircraft continues as filed, and you have to clear the way.&lt;br /&gt;
&lt;br /&gt;
*First, determine what RDOF it is: does the pilot hear or is his aircraft completely deaf? For this purpose, you ask the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;Controller: Leipzig 123, received radio communication failure. If you read, squawk Ident.&amp;lt;/pre&amp;gt;&lt;br /&gt;
If an ident signal is received, then things are easier: The pilot can receive calls normally, but might need to land priority. If the pilot sends no ident signal, then you (and even more important: the pilot...) needs to know the RCF failure procedures. The airplane will follow this procedure and land. Controller's job is...&lt;br /&gt;
* to get other pilots out of the way&lt;br /&gt;
* to inform other ATC &amp;quot;upstream&amp;quot; about the situation&lt;br /&gt;
* to monitor the aircraft: A RDF failure could turn into an emergency (you don't know, what's all wrong in the plane), and the pilot might not strictly follow the RDF procedure. Remember that the pilot needs the radio for local QNH, which might have changed since departure (local QNH at destination is part of the briefing).&lt;br /&gt;
* to bear in mind that the runway config might have changed and the pilot still approaches the &amp;quot;old&amp;quot; config.&lt;br /&gt;
&lt;br /&gt;
A RDF procedure typically follows the pattern:&lt;br /&gt;
#If the pilot has received the airport info (ATIS or other), then it will follow it (QNH, runway in use). Caution: The only way to determine this is if there has been contact, for example with APP, where the pilot has reported &amp;quot;ATIS on board&amp;quot;.&lt;br /&gt;
#If the pilot has not received it, then it will follow standard runway configuration according to the charts.&lt;br /&gt;
#Typically, procedures include flying standard STAR and transition and flying the minimum altitudes described in the charts. Some airports include holdings for a predetermined time.&lt;br /&gt;
See the RCF procedures for [[http://charts.vacc-austria.org/LOWW/LOWW_Arrival_COM%20Fail%20Procedure_06062011.pdf LOWW]]. Hey guys, where are the RCF procedures for the other LOVV airports?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Go Around and missed approach  ===&lt;br /&gt;
A Go-Around can be seen as abnormal procedure. Two different procedures can be followed:&lt;br /&gt;
#Missed Approach published in the Charts. APP should be informed about it (via teamspeak or PM).&lt;br /&gt;
#Individual handling like heading and altitude. This has to be coordinated with APP.&lt;br /&gt;
Remember: If necessary for safety, TWR can (and must) tell the aircraft virtually anything the aircraft is able to. If the reason for go-around is in the direction of the go-around procedure, then &amp;quot;proceed as published&amp;quot; does not really make sense. TWR might tell the aircraft to turn off left or right immediately.&lt;br /&gt;
&lt;br /&gt;
Phraseology differs according who announces it:&lt;br /&gt;
*If ATC issues go-around, then the phraseology expresses urgency. Listen to the readback - it is vital that the pilot received it. In this example, the go-around is individual:&lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Leipzig 123, go-around, say again go-around, turn left immediately direct SNU, climb 5000ft.&lt;br /&gt;
LHA123:LHA123 is going around, turning left SNU, climbing 5000ft.&amp;lt;/pre&amp;gt;&lt;br /&gt;
*If the pilot goes around, then he/she announces it. In this example, standard go-around pattern is used:&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Lepzig 123 goes around.&lt;br /&gt;
TWR: Roger, Leipzig 123, go around as published&amp;lt;/pre&amp;gt;&lt;br /&gt;
As a courtesy, you could tell the pilot the go-around procedure anyway - many of them don't know it.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Rejected take-off  ===&lt;br /&gt;
&lt;br /&gt;
Rejected take-off procedures can quickly turn into a nasty situation, if ATC does not react immediately and correctly. &lt;br /&gt;
&lt;br /&gt;
====== If the pilot rejects take-off ======&lt;br /&gt;
&lt;br /&gt;
Then the approaching traffic should immediately receive go-around instructions and the APP should be informed about it. Do not expect the aircraft to leave the runway immediately - something serious might be wrong, so be prepared to change the runway (if you have, like in LOWW).&lt;br /&gt;
&lt;br /&gt;
====== If TWR withdraws take-off clearance ======&lt;br /&gt;
&lt;br /&gt;
The situation is even worse, as the aircraft might be rolling already and be beyond v1 where it can't stop (and you as TWR don't know the specific V1 speed). In this case, TWR has to do the following:&lt;br /&gt;
&lt;br /&gt;
If the aircraft has commenced take-off:&lt;br /&gt;
&amp;lt;pre&amp;gt;&amp;quot;(Callsign) Stop immediately. I say again (Callsign) stop immediately - acknowledge&amp;quot;.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
If the aircraft has not commenced take-off:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;quot;(Callsign) hold position. Cancel take-off - I say again, cancel take-off - acknowledge&amp;quot;.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*If you have arriving traffic you must assume go-around instructions until the runway is free for the next approaching aircraft.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Malfunctions of airport navigation equipment  ===&lt;br /&gt;
Malfunctions of airport equipment (broken ILS, VOR or NDB) cannot be simulated at VATSIM (navaids are part of pilot software). If an aircraft has broken equipment, then this is actually a &amp;quot;pan-pan&amp;quot; case and should be treated as such. &lt;br /&gt;
&lt;br /&gt;
It could happen that a pilot reports a malfunction (in case his software simulates such a failure - but this failure only affects him. And Still, you could simulate airport malfunctions for all pilots and see, what they will do. In this case, you should know the other approaches available, offer alternatives (and communicate them between TWR and APP). If weather permits, you can offer visual approaches.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Priority Landing  ===&lt;br /&gt;
This is an easy case: A fully functional and communicating aircraft has only one grievance: Get down as soon as possible. Most reasons are medical emergencies, live organs, low fuel (at too low fuel this is an emergency), or VIPs on board (feel free to send him into 2 hours holding and divert to GATB if it is Karl-Heinz Grasser).&lt;br /&gt;
&lt;br /&gt;
Handling is easy: Issue instructions (vectors, descent, and on ground: a gate close to arrival) that best meet his/her request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Runway closure  ===&lt;br /&gt;
&lt;br /&gt;
This procedure is triggered by the TWR controller. There are two different cases:&lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''If the runway has to be closed immediately (broken down aircraft, debris, deer, ...), then the runway closure is imminent:&lt;br /&gt;
#approaching traffic receives go-around&lt;br /&gt;
#APP receives request, not to hand off any more aircraft&lt;br /&gt;
#GND receives information to halt taxi clearances to this runway&lt;br /&gt;
#New runway is opened, GND and APP informed (or airport closed)&lt;br /&gt;
#ATIS adapted.&lt;br /&gt;
&lt;br /&gt;
*'''Step-by-step closure:''' If the reason for closure can be forseen (wind changes slowly, noise abatement rules, then the runway closure is more orderly:&lt;br /&gt;
&lt;br /&gt;
#APP receives request not to hand off any more aircraft and/or divert to new runway&lt;br /&gt;
#GND receives request not to issue taxi clearances tot his runway, and the new one&lt;br /&gt;
#Remaining aircraft receive landing clearance&lt;br /&gt;
#New runway will be opened&lt;br /&gt;
#ATIS adapted&lt;br /&gt;
#APP and GND are informed.&lt;br /&gt;
&lt;br /&gt;
== Emergencies -  4 phases ==&lt;br /&gt;
If a pilot discovers a condition of being threatened by serious and/or&lt;br /&gt;
imminent danger '''and''' of requiring immediate assistance, then he/she will issue an emergency call.&lt;br /&gt;
&lt;br /&gt;
A basic principle is important: The pilot is in command, ATC is here to assist. Don't tell the pilot how to fly the aircraft - it's not your job, and you are not there. The pilot says his intentions, and ATC reacts. This does not mean that you don't order the pilot to do things, but they should be according to his/her intentions, not yours.&lt;br /&gt;
&lt;br /&gt;
Mayday procedure has the following phases:&lt;br /&gt;
&lt;br /&gt;
==== 1) Mayday call by the pilot:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Pilot calls &amp;quot;mayday&amp;quot; three times, the nature of his/her emergency, what his/her intentions are and what he/she needs now. ATC reads back, tells him to set transponder to 7700 (then all ATC see his mayday call on the Euroscope screen: The tag turns red and is preceded with &amp;quot;EMG&amp;quot;). Then the aircraft gets the needed information.&lt;br /&gt;
&lt;br /&gt;
==== 2) standard response by ATC  ====&lt;br /&gt;
The pilot has a few seconds to do (avigate, navigate), and ATC too: He/she needs to inform other pilots and fellow ATC stations.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&amp;lt;/pre&amp;gt;&lt;br /&gt;
With this call pilots know: They should continue as told (their SID, transitions, STAR). They only call ATC, if safety is at stake. If they receive ATC orders, they don't read back - they just do it.&lt;br /&gt;
&lt;br /&gt;
Then ATC informs other controllers via intercom, Text or teamspeak, and collects the necessary information.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Generally, the controller makes sure that he/she does not get any traffic any more: no takeoffs from below, no handoffs from above.&lt;br /&gt;
&lt;br /&gt;
Beyond this point, there is no fixed phraseology. ATC speaks with pilots to make sure that he is served best. With the information gathered, ATC will turn back to the pilot and figure out next steps.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, for runway 11 maintain present heading, wind 320°4kt. When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
ATC's information is important to pilots: Where can I land and how far it is? Pilots say, that accurate distance is vital, so use the distance tool on your scope.&lt;br /&gt;
&lt;br /&gt;
The pilot's first information is important for controllers: What is wrong? That says a lot about the ability of the pilot to control the aircraft. The last info is important for real life: Emergency services on the ground need to prepare for rescue.&lt;br /&gt;
&lt;br /&gt;
==== 3) All following measures  ====&lt;br /&gt;
There is no strict rules beyond the standard response. Pilot and ATC communicate the way that suits best their situation. The following guidelines are vital:&lt;br /&gt;
*'''Pilot tells, ATC delivers.''' On the flight plan, you read &amp;quot;PIC - pilot in command&amp;quot; - let him stay in command, and let him decide, which command he wants you to take over.&lt;br /&gt;
*'''Communication: least possible, as precise as possible.''' During an emergency, the cockpit is a beehouse. The more time pilots have for themselves, the better. If a pilot does not answer: stay calm - the pilot might follow the rule 1-avigate 2-navigate 3-communicate and might not have reached step 3. He/she may say &amp;quot;ATC standby&amp;quot; or just nothing. To quote a real-life example: [[http://www.youtube.com/watch?v=lICb8p9SvvM don't do this.]]&lt;br /&gt;
*'''Clear needed airspace:''' Noone needs to turn away, if he/she is not in the way. Some traffic might continue as normal. You might consider premature handoffs to other controllers or holdings. As a rule of thumb: don't produce more emergencies than you have already.&lt;br /&gt;
*'''Pilot has the choice of frequency:''' An aircraft can stay on the frequency (eg. TWR) through all stages of his/her emergency or change, if he/she wishes. ATC will adjust. Assume that you have an engine failure at FL100 approaching LOWW. The pilot is on the APP frequency and does not want to change. Either APP coordinates with TWR landing clearance and issues it, or TWR enters the APP frequency and issues landing clearance him/herself.&lt;br /&gt;
&lt;br /&gt;
==== 4)&amp;amp;nbsp;End emergency procedure  ====&lt;br /&gt;
At some stage, the emergency is over, and the aircraft is happily on the runway or unhappy in the wood. At this stage, all other pilots and ATC need to know that it is over:&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Then, cleanup starts: There might be a dozen aircraft in holdings to bring in, runways to clean and aircraft on ground to get out.&lt;br /&gt;
&lt;br /&gt;
== Emergencies - the cases ==&lt;br /&gt;
This list is open - be prepared to react to the unusual. If you discover an emergency which is not covered here, feel free to add it.&lt;br /&gt;
=== Loss of Cabin pressure  ===&lt;br /&gt;
&lt;br /&gt;
This could be a problem in high traffic situations. The pilot will immediately begin an &amp;quot;emergency descent&amp;quot; to FL100 or below (he won't wait for approval). As controller, you can expect that the pilot wants to land as soon as possible. Be prepared that the emergency situation escalates, as there is a reason for the loss of cabin pressure which could cause other systems to fail too.&lt;br /&gt;
&lt;br /&gt;
=== Loss of Hydraulicpressure  ===&lt;br /&gt;
&lt;br /&gt;
This is a major problem, depending on the degree of failure: On large aircraft, all systems for manoever depend on hydraulic pressure. First thing after the usual introduction is to ask the pilot about his/her status - which systems are affected and what this means. It could mean that the pilot cannot deploy speedbrakes (that's trivial) or flaps (that means a long runout on the runway), or cannot perform certain manoevers (like left or right turn etc, or that the plane reacts very slow. As ATC, you should offer the nearest suitable airport and increase separation. Also a loss of hydraulic pressure can escalate quickly into a worse emergency.&lt;br /&gt;
&lt;br /&gt;
===Electrics failure===&lt;br /&gt;
... means that the aircraft has very short time in the air. If all systems rely on battery, it will be drained quickly. &lt;br /&gt;
*Pilots will most likely want the closest suitable airfield.&lt;br /&gt;
*A major power consumer is radio communication. Consider offering solutions which need very short answers.&lt;br /&gt;
*Navigational aids may fail without power. Consider vectors for routing, and monitor headings, as instruments in the cockpit might fail.&lt;br /&gt;
*Expect abnormal approach procedures - shortened, steeper, but maybe with smaller bank angles - the pilot will tell what he is able to.&lt;br /&gt;
&lt;br /&gt;
=== Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Smoke in cockpit is a very challenging situation. The best way is not to lose overview in the situation. Time is critical - the aircraft has to come down really quickly. Contrary to other emergencies, smoke in cockpit means a &amp;quot;talk-down&amp;quot; approach. Supply the pilot with vectors and distance to the nearest airfield. You might consider to supply the pilot with vital information (it could be that he/she cannot see his/her instruments)in regular intervals (minutes or less), like:&lt;br /&gt;
&amp;lt;pre&amp;gt;Mayday Leipzig 123, speed 220 ok, altitude 6000ft ok, heading ok, runway 11 miles&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Such an emergency should definitely land at the next suitable aerodrome, and maybe on a separate runway in case anything goes wrong. Increase separation considerably.&lt;br /&gt;
&lt;br /&gt;
=== Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Engine failures are the most dangerous incidents that can happen: Altitude over ground is low, the aircraft is at full thrust and full of fuel, speed is low. This is the cocktail for a nasty situation. Most frequent reason is bird strike.&lt;br /&gt;
&lt;br /&gt;
Most likely, the bird strike happened already on ground above v1, and the aircraft has to get into the air with reduced engine power. Therefore, TWR is most likely to receive the mayday call. High insecurity adds to this, as it may take time to assess the degree of damage. How much thrust is still left? Is climbing an option? Does the aircraft need to make an emergency U-turn or does it have enough time for a controlled approach?&lt;br /&gt;
&lt;br /&gt;
Workload in the cockpit is very high. Quick, short response and coordination is the key to this situation. More important than in any other situation is to offer solutions, but let the pilot decide. The pilot will tell you, what he is able to and what his intentions are. &lt;br /&gt;
&lt;br /&gt;
Be prepared that the aircraft may not follow the filed SID. It will most likely climb slower, step-climb and need a larger turn radius. In turns, the rate of descent might double.&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=9KhZwsYtNDE Here is a perfect example], how it should work: &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;as precise as possible:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Answer ATC:&amp;amp;nbsp;As precise as possible (listen: Thomson 253H has not requested anything, so TWR is offering the prime information which the pilot needs now):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warns all other stations ans waits. the pilot is &amp;quot;in command&amp;quot;, he will call. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Pilot has called, now TWR offers solutions. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Now the pilot says his intentions: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower reads back and done. If the pilot does not want anything else, then TWR keeps quiet. He knows that the pilot will fly a controlled approach via a VOR (Afterwards we will see that his right engine is dead while the left one runs normally - far enough for a modern aircraft to take off and climb). Shortly later he makes the offer to land in Liverpool - which is turned down - the pilot is happy with returning to Manchester. Then TWR reports runway 06R closed because of debris - the aircraft has lost parts of its engine. This is an order to the pilot - he should not land on a closed runway. A short time afterwards, the aircraft lands orderly on 06L.&lt;br /&gt;
&lt;br /&gt;
=== Engine Failure at approach - Triebwerksversagen beim Landeanflug  ===&lt;br /&gt;
&lt;br /&gt;
===Total engine failure===&lt;br /&gt;
For ATC, this is easy, as it means: This aircraft will come down very quickly. In this situation, workload in the cockpit is enormous, as they try to re-light the engines. ATC's job is to analyse every option to reach ground safely and offer them in sequence of relevance.&lt;br /&gt;
&lt;br /&gt;
===(Very) low fuel===&lt;br /&gt;
If fuel is gone, then this is the same situation as a complete engine failure. If such a situation is possible or even likely (=if it could happen within the distance between aircraft and airport), then the aircraft has to be routed to the nearest runway threshold. Again - the pilot decides, bearing in mind that steep turns cost altitude. If no runway can be reached, then anything like it is better than nothing - a taxiway maybe. As ATC, do not allow the aircraft to endanger other aircraft or people.&lt;br /&gt;
&lt;br /&gt;
===Directional Gyro Failure===&lt;br /&gt;
The directional gyro is the &amp;quot;compass&amp;quot; of the aircraft. If the directional gyro fails, then the pilot does not know any more, where north is. Most likely, you as ATC will notice first that the aircraft goes into strange circles.&lt;br /&gt;
*Normally, aircraft have a standard mechanic magnetic compass in sight - a simple ball. This is not enough to fly a vector, but good enough to fly a visual approach.&lt;br /&gt;
*(it happened to me once) If the pilot has no compass (or iPhone) to look at, then the ground is the only possible visual reference. ATC can approve descent to minimum altitude until ground contact. Then, incremental turns can be issued: &amp;quot;turn 20° left from present heading&amp;quot; - until runway is in sight.&lt;br /&gt;
&lt;br /&gt;
===Landing gear failure===&lt;br /&gt;
*If landing gear fails to retract after takeoff, then this is a pan-pan situation. Crew can continue normally, but with reduced speed and more fuel consumption - crew will recalculate if they need a diversion. For ATC this means to accomodate crew's wishes.&lt;br /&gt;
*A broken tyre could prevent the aircraft from retracting the gear. Landing with a flat tyre is already an emergency, as the aircraft could become unstable after touchdown. For ATC this means: Clear the runway, increase spacing behind and alert fire services.&lt;br /&gt;
*If the aircraft fails to expand gear, then the situation is more critical. The only thing pilot see is their warning lights (they can't get out and see). This will occur in the last 10miles final. First reaction is a go-around to gain time to analyse the problem. In real life, the aircraft performs a low approach and technicians look at the aircraft from below. If gear fails to expand properly, then an attempted landing is imminent (at some point, the aircraf ''must'' land). This is an emergency. For ATC: Clear the runway, increace spacing behind and alert fire services.&lt;br /&gt;
&lt;br /&gt;
=== THIS PART AWAITS MORE. DO YOU KNOW MORE? ===&lt;br /&gt;
&lt;br /&gt;
=== Multiple emergencies ===&lt;br /&gt;
There is nothing more challenging than multiple emergencies, as you as controller have to rank its severity and propose measures that all of them can accomodated. If emergencies collide, you have to set priorities:&lt;br /&gt;
*Aircraft which risk to go down soon have priority to those which can still fly for a few minutes (all-engine failure is first compared to hydraulics failure).&lt;br /&gt;
*Aircraft which need to be on the ground first are first (passenger with heart attack is first compared to low - but not empty - fuel).&lt;br /&gt;
*More people saved is better than less (full engine failure has priority compared with a passenger with heart attack).&lt;br /&gt;
Nothing is heavier than taking these decisions. Let's be happy to fly online.&lt;br /&gt;
&lt;br /&gt;
=Further reading=&lt;br /&gt;
A [[http://www.skybrary.aero/bookshelf/books/200.pdf brochure by the British Air Traffic Authorities]] is an excellent reference for controllers.&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1982</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1982"/>
		<updated>2012-03-27T20:56:09Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: /* Pan-pan */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergencies and abnormal procedures arise from two directions: from the pilots or the ATC- depending where actually they occur. If a pilot gets into trouble then he decleares an emergency. If for example the runway is blocked (damaged aircraft, animals etc.) then the ATC reports abnormal procedures to the surrounding stations.&lt;br /&gt;
&lt;br /&gt;
It is quite common that the emergency call does not come right away. The crew might discover something (an indicator in the cockpit) and follows the letters: DODAR (Diagnose, Options available, Decide, Allocate task, Review). In this case, a short message to ATC is common, that something is wrong:&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Tower, Laipzich Air 123, we have a problem, standby.&lt;br /&gt;
TWR: LHA123, roger.&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''If you are controller and hear this, prepare yourself:''' Oversee the situation, you might wait with the next takeoff clearance, think of scenarios like: where could the aircraft turn back? Which diversion can it reach? The pilot will call you back in a few seconds with precise information.&lt;br /&gt;
&lt;br /&gt;
== Abnormal procedures  ==&lt;br /&gt;
&lt;br /&gt;
=== Pan-pan  ===&lt;br /&gt;
&lt;br /&gt;
Pan-Pan is an urgency announcement of the crew, which is used if an aircraft or its occupence are endangered but not acute at risk (so no need for immediate action), and the crew calls for a preferential treatment. The crew can mostly continue flying under normal or restricted conditions and usually also land regularly.&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;pre&amp;gt;SWR111:&amp;amp;nbsp;  Swissair one-eleven heavy is declaring pan-pan-pan. We have smoke in the cockpit. Request immediate return to a convenient place, I guess Boston.&lt;br /&gt;
CZQM_CTR: Swissair one-eleven heavy, pan-pan received, turn left direct Boston VOR, climb and maintain flight level 310.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Pan-pan is only a message that the crew has to fly under abnormal circumstances and eventually needs a higher priority as non-pan flights.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Radio communication&amp;amp;nbsp;Failure (RCF) ===&lt;br /&gt;
&lt;br /&gt;
You notice RCF at the SQ 7600, which lights up the letters &amp;quot;RDOF&amp;quot; in the aircraft tag of Euroscope. But maybe it is you who discovers RCF first - crew might not know it yet. In this case, assume the aircraft continues as filed, and you have to clear the way.&lt;br /&gt;
&lt;br /&gt;
*First, determine what RDOF it is: does the pilot hear or is his aircraft completely deaf? For this purpose, you ask the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;Controller: Leipzig 123, received radio communication failure. If you read, squawk Ident.&amp;lt;/pre&amp;gt;&lt;br /&gt;
If an ident signal is received, then things are easier: The pilot can receive calls normally, but might need to land priority. If the pilot sends no ident signal, then you (and even more important: the pilot...) needs to know the RCF failure procedures. The airplane will follow this procedure and land. Controller's job is...&lt;br /&gt;
* to get other pilots out of the way&lt;br /&gt;
* to inform other ATC &amp;quot;upstream&amp;quot; about the situation&lt;br /&gt;
* to monitor the aircraft: A RDF failure could turn into an emergency (you don't know, what's all wrong in the plane), and the pilot might not strictly follow the RDF procedure. Remember that the pilot needs the radio for local QNH, which might have changed since departure (local QNH at destination is part of the briefing).&lt;br /&gt;
* to bear in mind that the runway config might have changed and the pilot still approaches the &amp;quot;old&amp;quot; config.&lt;br /&gt;
&lt;br /&gt;
A RDF procedure typically follows the pattern:&lt;br /&gt;
#If the pilot has received the airport info (ATIS or other), then it will follow it (QNH, runway in use). Caution: The only way to determine this is if there has been contact, for example with APP, where the pilot has reported &amp;quot;ATIS on board&amp;quot;.&lt;br /&gt;
#If the pilot has not received it, then it will follow standard runway configuration according to the charts.&lt;br /&gt;
#Typically, procedures include flying standard STAR and transition and flying the minimum altitudes described in the charts. Some airports include holdings for a predetermined time.&lt;br /&gt;
See the RCF procedures for [[http://charts.vacc-austria.org/LOWW/LOWW_Arrival_COM%20Fail%20Procedure_06062011.pdf LOWW]]. Hey guys, where are the RCF procedures for the other LOVV airports?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Go Around and missed approach  ===&lt;br /&gt;
A Go-Around can be seen as abnormal procedure. Two different procedures can be followed:&lt;br /&gt;
#Missed Approach published in the Charts. APP should be informed about it (via teamspeak or PM).&lt;br /&gt;
#Individual handling like heading and altitude. This has to be coordinated with APP.&lt;br /&gt;
Remember: If necessary for safety, TWR can (and must) tell the aircraft virtually anything the aircraft is able to. If the reason for go-around is in the direction of the go-around procedure, then &amp;quot;proceed as published&amp;quot; does not really make sense. TWR might tell the aircraft to turn off left or right immediately.&lt;br /&gt;
&lt;br /&gt;
Phraseology differs according who announces it:&lt;br /&gt;
*If ATC issues go-around, then the phraseology expresses urgency. Listen to the readback - it is vital that the pilot received it. In this example, the go-around is individual:&lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Leipzig 123, go-around, say again go-around, turn left immediately direct SNU, climb 5000ft.&lt;br /&gt;
LHA123:LHA123 is going around, turning left SNU, climbing 5000ft.&amp;lt;/pre&amp;gt;&lt;br /&gt;
*If the pilot goes around, then he/she announces it. In this example, standard go-around pattern is used:&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Lepzig 123 goes around.&lt;br /&gt;
TWR: Roger, Leipzig 123, go around as published&amp;lt;/pre&amp;gt;&lt;br /&gt;
As a courtesy, you could tell the pilot the go-around procedure anyway - many of them don't know it.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Rejected Take-off  ===&lt;br /&gt;
Rejected takeoff can quickly turn into a nasty situation, if ATC does not react immediately and correctly.&lt;br /&gt;
*If the pilot rejects takeoff, then the approaching traffic should immediately receive go-around. APP should be informed about it. Do not expect the aircraft to leave the runway immediately - something serious might be wrong, so be prepared to change the runway (if you have, like in LOWW).&lt;br /&gt;
*If TWR withdraws takeoff clearance, the situation is even worse, as the aircraft might be rolling already and be beyond v1 where it can't stop (and you as TWR don't know this). In this case, TWR has to do the following:&lt;br /&gt;
#Issue takeoff cancellation: &amp;quot;Leipzig 123, cancel takeoff, say again, cancel takeoff.&amp;quot; The pilot will do, if able (=below V1).&lt;br /&gt;
#Arriving aircraft behind have to be issued a go-around which leads them away from the departure route of the departing aircraft - departing aircraft could be above v1 and fly out.&lt;br /&gt;
#Inform all surrounding ATC stations about the situation.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Malfunctions of airport navigation equipment  ===&lt;br /&gt;
Malfunctions of airport equipment (broken ILS, VOR or NDB) cannot be simulated at VATSIM (navaids are part of pilot software). If an aircraft has broken equipment, then this is actually a &amp;quot;pan-pan&amp;quot; case and should be treated as such. &lt;br /&gt;
&lt;br /&gt;
It could happen that a pilot reports a malfunction (in case his software simulates such a failure - but this failure only affects him. And Still, you could simulate airport malfunctions for all pilots and see, what they will do. In this case, you should know the other approaches available, offer alternatives (and communicate them between TWR and APP). If weather permits, you can offer visual approaches.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Priority Landing  ===&lt;br /&gt;
This is an easy case: A fully functional and communicating aircraft has only one grievance: Get down as soon as possible. Most reasons are medical emergencies, live organs, low fuel (at too low fuel this is an emergency), or VIPs on board (feel free to send him into 2 hours holding and divert to GATB if it is Karl-Heinz Grasser).&lt;br /&gt;
&lt;br /&gt;
Handling is easy: Issue instructions (vectors, descent, and on ground: a gate close to arrival) that best meet his/her request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Runway closure  ===&lt;br /&gt;
&lt;br /&gt;
This procedure is triggered by the TWR controller. There are two different cases:&lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''If the runway has to be closed immediately (broken down aircraft, debris, deer, ...), then the runway closure is imminent:&lt;br /&gt;
#approaching traffic receives go-around&lt;br /&gt;
#APP receives request, not to hand off any more aircraft&lt;br /&gt;
#GND receives information to halt taxi clearances to this runway&lt;br /&gt;
#New runway is opened, GND and APP informed (or airport closed)&lt;br /&gt;
#ATIS adapted.&lt;br /&gt;
&lt;br /&gt;
*'''Step-by-step closure:''' If the reason for closure can be forseen (wind changes slowly, noise abatement rules, then the runway closure is more orderly:&lt;br /&gt;
&lt;br /&gt;
#APP receives request not to hand off any more aircraft and/or divert to new runway&lt;br /&gt;
#GND receives request not to issue taxi clearances tot his runway, and the new one&lt;br /&gt;
#Remaining aircraft receive landing clearance&lt;br /&gt;
#New runway will be opened&lt;br /&gt;
#ATIS adapted&lt;br /&gt;
#APP and GND are informed.&lt;br /&gt;
&lt;br /&gt;
== Emergencies -  4 phases ==&lt;br /&gt;
If a pilot discovers a condition of being threatened by serious and/or&lt;br /&gt;
imminent danger '''and''' of requiring immediate assistance, then he/she will issue an emergency call.&lt;br /&gt;
&lt;br /&gt;
A basic principle is important: The pilot is in command, ATC is here to assist. Don't tell the pilot how to fly the aircraft - it's not your job, and you are not there. The pilot says his intentions, and ATC reacts. This does not mean that you don't order the pilot to do things, but they should be according to his/her intentions, not yours.&lt;br /&gt;
&lt;br /&gt;
Mayday procedure has the following phases:&lt;br /&gt;
&lt;br /&gt;
==== 1) Mayday call by the pilot:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Pilot calls &amp;quot;mayday&amp;quot; three times, the nature of his/her emergency, what his/her intentions are and what he/she needs now. ATC reads back, tells him to set transponder to 7700 (then all ATC see his mayday call on the Euroscope screen: The tag turns red and is preceded with &amp;quot;EMG&amp;quot;). Then the aircraft gets the needed information.&lt;br /&gt;
&lt;br /&gt;
==== 2) standard response by ATC  ====&lt;br /&gt;
The pilot has a few seconds to do (avigate, navigate), and ATC too: He/she needs to inform other pilots and fellow ATC stations.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&amp;lt;/pre&amp;gt;&lt;br /&gt;
With this call pilots know: They should continue as told (their SID, transitions, STAR). They only call ATC, if safety is at stake. If they receive ATC orders, they don't read back - they just do it.&lt;br /&gt;
&lt;br /&gt;
Then ATC informs other controllers via intercom, Text or teamspeak, and collects the necessary information.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Generally, the controller makes sure that he/she does not get any traffic any more: no takeoffs from below, no handoffs from above.&lt;br /&gt;
&lt;br /&gt;
Beyond this point, there is no fixed phraseology. ATC speaks with pilots to make sure that he is served best. With the information gathered, ATC will turn back to the pilot and figure out next steps.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, for runway 11 maintain present heading, wind 320°4kt. When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
ATC's information is important to pilots: Where can I land and how far it is? Pilots say, that accurate distance is vital, so use the distance tool on your scope.&lt;br /&gt;
&lt;br /&gt;
The pilot's first information is important for controllers: What is wrong? That says a lot about the ability of the pilot to control the aircraft. The last info is important for real life: Emergency services on the ground need to prepare for rescue.&lt;br /&gt;
&lt;br /&gt;
==== 3) All following measures  ====&lt;br /&gt;
There is no strict rules beyond the standard response. Pilot and ATC communicate the way that suits best their situation. The following guidelines are vital:&lt;br /&gt;
*'''Pilot tells, ATC delivers.''' On the flight plan, you read &amp;quot;PIC - pilot in command&amp;quot; - let him stay in command, and let him decide, which command he wants you to take over.&lt;br /&gt;
*'''Communication: least possible, as precise as possible.''' During an emergency, the cockpit is a beehouse. The more time pilots have for themselves, the better. If a pilot does not answer: stay calm - the pilot might follow the rule 1-avigate 2-navigate 3-communicate and might not have reached step 3. He/she may say &amp;quot;ATC standby&amp;quot; or just nothing. To quote a real-life example: [[http://www.youtube.com/watch?v=lICb8p9SvvM don't do this.]]&lt;br /&gt;
*'''Clear needed airspace:''' Noone needs to turn away, if he/she is not in the way. Some traffic might continue as normal. You might consider premature handoffs to other controllers or holdings. As a rule of thumb: don't produce more emergencies than you have already.&lt;br /&gt;
*'''Pilot has the choice of frequency:''' An aircraft can stay on the frequency (eg. TWR) through all stages of his/her emergency or change, if he/she wishes. ATC will adjust. Assume that you have an engine failure at FL100 approaching LOWW. The pilot is on the APP frequency and does not want to change. Either APP coordinates with TWR landing clearance and issues it, or TWR enters the APP frequency and issues landing clearance him/herself.&lt;br /&gt;
&lt;br /&gt;
==== 4)&amp;amp;nbsp;End emergency procedure  ====&lt;br /&gt;
At some stage, the emergency is over, and the aircraft is happily on the runway or unhappy in the wood. At this stage, all other pilots and ATC need to know that it is over:&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Then, cleanup starts: There might be a dozen aircraft in holdings to bring in, runways to clean and aircraft on ground to get out.&lt;br /&gt;
&lt;br /&gt;
== Emergencies - the cases ==&lt;br /&gt;
This list is open - be prepared to react to the unusual. If you discover an emergency which is not covered here, feel free to add it.&lt;br /&gt;
=== Loss of Cabin pressure  ===&lt;br /&gt;
&lt;br /&gt;
This could be a problem in high traffic situations. The pilot will immediately begin an &amp;quot;emergency descent&amp;quot; to FL100 or below (he won't wait for approval). As controller, you can expect that the pilot wants to land as soon as possible. Be prepared that the emergency situation escalates, as there is a reason for the loss of cabin pressure which could cause other systems to fail too.&lt;br /&gt;
&lt;br /&gt;
=== Loss of Hydraulicpressure  ===&lt;br /&gt;
&lt;br /&gt;
This is a major problem, depending on the degree of failure: On large aircraft, all systems for manoever depend on hydraulic pressure. First thing after the usual introduction is to ask the pilot about his/her status - which systems are affected and what this means. It could mean that the pilot cannot deploy speedbrakes (that's trivial) or flaps (that means a long runout on the runway), or cannot perform certain manoevers (like left or right turn etc, or that the plane reacts very slow. As ATC, you should offer the nearest suitable airport and increase separation. Also a loss of hydraulic pressure can escalate quickly into a worse emergency.&lt;br /&gt;
&lt;br /&gt;
===Electrics failure===&lt;br /&gt;
... means that the aircraft has very short time in the air. If all systems rely on battery, it will be drained quickly. &lt;br /&gt;
*Pilots will most likely want the closest suitable airfield.&lt;br /&gt;
*A major power consumer is radio communication. Consider offering solutions which need very short answers.&lt;br /&gt;
*Navigational aids may fail without power. Consider vectors for routing, and monitor headings, as instruments in the cockpit might fail.&lt;br /&gt;
*Expect abnormal approach procedures - shortened, steeper, but maybe with smaller bank angles - the pilot will tell what he is able to.&lt;br /&gt;
&lt;br /&gt;
=== Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Smoke in cockpit is a very challenging situation. The best way is not to lose overview in the situation. Time is critical - the aircraft has to come down really quickly. Contrary to other emergencies, smoke in cockpit means a &amp;quot;talk-down&amp;quot; approach. Supply the pilot with vectors and distance to the nearest airfield. You might consider to supply the pilot with vital information (it could be that he/she cannot see his/her instruments)in regular intervals (minutes or less), like:&lt;br /&gt;
&amp;lt;pre&amp;gt;Mayday Leipzig 123, speed 220 ok, altitude 6000ft ok, heading ok, runway 11 miles&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Such an emergency should definitely land at the next suitable aerodrome, and maybe on a separate runway in case anything goes wrong. Increase separation considerably.&lt;br /&gt;
&lt;br /&gt;
=== Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Engine failures are the most dangerous incidents that can happen: Altitude over ground is low, the aircraft is at full thrust and full of fuel, speed is low. This is the cocktail for a nasty situation. Most frequent reason is bird strike.&lt;br /&gt;
&lt;br /&gt;
Most likely, the bird strike happened already on ground above v1, and the aircraft has to get into the air with reduced engine power. Therefore, TWR is most likely to receive the mayday call. High insecurity adds to this, as it may take time to assess the degree of damage. How much thrust is still left? Is climbing an option? Does the aircraft need to make an emergency U-turn or does it have enough time for a controlled approach?&lt;br /&gt;
&lt;br /&gt;
Workload in the cockpit is very high. Quick, short response and coordination is the key to this situation. More important than in any other situation is to offer solutions, but let the pilot decide. The pilot will tell you, what he is able to and what his intentions are. &lt;br /&gt;
&lt;br /&gt;
Be prepared that the aircraft may not follow the filed SID. It will most likely climb slower, step-climb and need a larger turn radius. In turns, the rate of descent might double.&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=9KhZwsYtNDE Here is a perfect example], how it should work: &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;as precise as possible:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Answer ATC:&amp;amp;nbsp;As precise as possible (listen: Thomson 253H has not requested anything, so TWR is offering the prime information which the pilot needs now):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warns all other stations ans waits. the pilot is &amp;quot;in command&amp;quot;, he will call. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Pilot has called, now TWR offers solutions. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Now the pilot says his intentions: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower reads back and done. If the pilot does not want anything else, then TWR keeps quiet. He knows that the pilot will fly a controlled approach via a VOR (Afterwards we will see that his right engine is dead while the left one runs normally - far enough for a modern aircraft to take off and climb). Shortly later he makes the offer to land in Liverpool - which is turned down - the pilot is happy with returning to Manchester. Then TWR reports runway 06R closed because of debris - the aircraft has lost parts of its engine. This is an order to the pilot - he should not land on a closed runway. A short time afterwards, the aircraft lands orderly on 06L.&lt;br /&gt;
&lt;br /&gt;
=== Engine Failure at approach - Triebwerksversagen beim Landeanflug  ===&lt;br /&gt;
&lt;br /&gt;
===Total engine failure===&lt;br /&gt;
For ATC, this is easy, as it means: This aircraft will come down very quickly. In this situation, workload in the cockpit is enormous, as they try to re-light the engines. ATC's job is to analyse every option to reach ground safely and offer them in sequence of relevance.&lt;br /&gt;
&lt;br /&gt;
===(Very) low fuel===&lt;br /&gt;
If fuel is gone, then this is the same situation as a complete engine failure. If such a situation is possible or even likely (=if it could happen within the distance between aircraft and airport), then the aircraft has to be routed to the nearest runway threshold. Again - the pilot decides, bearing in mind that steep turns cost altitude. If no runway can be reached, then anything like it is better than nothing - a taxiway maybe. As ATC, do not allow the aircraft to endanger other aircraft or people.&lt;br /&gt;
&lt;br /&gt;
===Directional Gyro Failure===&lt;br /&gt;
The directional gyro is the &amp;quot;compass&amp;quot; of the aircraft. If the directional gyro fails, then the pilot does not know any more, where north is. Most likely, you as ATC will notice first that the aircraft goes into strange circles.&lt;br /&gt;
*Normally, aircraft have a standard mechanic magnetic compass in sight - a simple ball. This is not enough to fly a vector, but good enough to fly a visual approach.&lt;br /&gt;
*(it happened to me once) If the pilot has no compass (or iPhone) to look at, then the ground is the only possible visual reference. ATC can approve descent to minimum altitude until ground contact. Then, incremental turns can be issued: &amp;quot;turn 20° left from present heading&amp;quot; - until runway is in sight.&lt;br /&gt;
&lt;br /&gt;
===Landing gear failure===&lt;br /&gt;
*If landing gear fails to retract after takeoff, then this is a pan-pan situation. Crew can continue normally, but with reduced speed and more fuel consumption - crew will recalculate if they need a diversion. For ATC this means to accomodate crew's wishes.&lt;br /&gt;
*A broken tyre could prevent the aircraft from retracting the gear. Landing with a flat tyre is already an emergency, as the aircraft could become unstable after touchdown. For ATC this means: Clear the runway, increase spacing behind and alert fire services.&lt;br /&gt;
*If the aircraft fails to expand gear, then the situation is more critical. The only thing pilot see is their warning lights (they can't get out and see). This will occur in the last 10miles final. First reaction is a go-around to gain time to analyse the problem. In real life, the aircraft performs a low approach and technicians look at the aircraft from below. If gear fails to expand properly, then an attempted landing is imminent (at some point, the aircraf ''must'' land). This is an emergency. For ATC: Clear the runway, increace spacing behind and alert fire services.&lt;br /&gt;
&lt;br /&gt;
=== THIS PART AWAITS MORE. DO YOU KNOW MORE? ===&lt;br /&gt;
&lt;br /&gt;
=== Multiple emergencies ===&lt;br /&gt;
There is nothing more challenging than multiple emergencies, as you as controller have to rank its severity and propose measures that all of them can accomodated. If emergencies collide, you have to set priorities:&lt;br /&gt;
*Aircraft which risk to go down soon have priority to those which can still fly for a few minutes (all-engine failure is first compared to hydraulics failure).&lt;br /&gt;
*Aircraft which need to be on the ground first are first (passenger with heart attack is first compared to low - but not empty - fuel).&lt;br /&gt;
*More people saved is better than less (full engine failure has priority compared with a passenger with heart attack).&lt;br /&gt;
Nothing is heavier than taking these decisions. Let's be happy to fly online.&lt;br /&gt;
&lt;br /&gt;
=Further reading=&lt;br /&gt;
A [[http://www.skybrary.aero/bookshelf/books/200.pdf brochure by the British Air Traffic Authorities]] is an excellent reference for controllers.&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1981</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1981"/>
		<updated>2012-03-27T20:53:56Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: /* General */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergencies and abnormal procedures arise from two directions: from the pilots or the ATC- depending where actually they occur. If a pilot gets into trouble then he decleares an emergency. If for example the runway is blocked (damaged aircraft, animals etc.) then the ATC reports abnormal procedures to the surrounding stations.&lt;br /&gt;
&lt;br /&gt;
It is quite common that the emergency call does not come right away. The crew might discover something (an indicator in the cockpit) and follows the letters: DODAR (Diagnose, Options available, Decide, Allocate task, Review). In this case, a short message to ATC is common, that something is wrong:&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Tower, Laipzich Air 123, we have a problem, standby.&lt;br /&gt;
TWR: LHA123, roger.&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''If you are controller and hear this, prepare yourself:''' Oversee the situation, you might wait with the next takeoff clearance, think of scenarios like: where could the aircraft turn back? Which diversion can it reach? The pilot will call you back in a few seconds with precise information.&lt;br /&gt;
&lt;br /&gt;
== Abnormal procedures  ==&lt;br /&gt;
&lt;br /&gt;
=== Pan-pan  ===&lt;br /&gt;
&lt;br /&gt;
Pan-Pan is an urgency announcement of the crew, which is used if an aircraft or its occupence are endangered but not acute at risk (so no need for immediate action), and the crew calls for a preferential treatment. The crew can mostly continue flying under normal or restricted conditions and usually also land regularly.&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;pre&amp;gt;SWR111:&amp;amp;nbsp;  Swissair one-eleven heavy is declaring pan-pan pan-pan pan-pan. We have smoke in the cockpit. Request immediate return to a convenient place, I guess Boston.&lt;br /&gt;
CZQM_CTR: Swissair one-eleven heavy, pan-pan received, turn left direct Boston VOR, climb and maintain flight level 310.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Pan-pan is only a message that the crew has to fly under abnormal circumstances and eventually needs a higher priority as non-pan flights.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Radio communication&amp;amp;nbsp;Failure (RCF) ===&lt;br /&gt;
&lt;br /&gt;
You notice RCF at the SQ 7600, which lights up the letters &amp;quot;RDOF&amp;quot; in the aircraft tag of Euroscope. But maybe it is you who discovers RCF first - crew might not know it yet. In this case, assume the aircraft continues as filed, and you have to clear the way.&lt;br /&gt;
&lt;br /&gt;
*First, determine what RDOF it is: does the pilot hear or is his aircraft completely deaf? For this purpose, you ask the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;Controller: Leipzig 123, received radio communication failure. If you read, squawk Ident.&amp;lt;/pre&amp;gt;&lt;br /&gt;
If an ident signal is received, then things are easier: The pilot can receive calls normally, but might need to land priority. If the pilot sends no ident signal, then you (and even more important: the pilot...) needs to know the RCF failure procedures. The airplane will follow this procedure and land. Controller's job is...&lt;br /&gt;
* to get other pilots out of the way&lt;br /&gt;
* to inform other ATC &amp;quot;upstream&amp;quot; about the situation&lt;br /&gt;
* to monitor the aircraft: A RDF failure could turn into an emergency (you don't know, what's all wrong in the plane), and the pilot might not strictly follow the RDF procedure. Remember that the pilot needs the radio for local QNH, which might have changed since departure (local QNH at destination is part of the briefing).&lt;br /&gt;
* to bear in mind that the runway config might have changed and the pilot still approaches the &amp;quot;old&amp;quot; config.&lt;br /&gt;
&lt;br /&gt;
A RDF procedure typically follows the pattern:&lt;br /&gt;
#If the pilot has received the airport info (ATIS or other), then it will follow it (QNH, runway in use). Caution: The only way to determine this is if there has been contact, for example with APP, where the pilot has reported &amp;quot;ATIS on board&amp;quot;.&lt;br /&gt;
#If the pilot has not received it, then it will follow standard runway configuration according to the charts.&lt;br /&gt;
#Typically, procedures include flying standard STAR and transition and flying the minimum altitudes described in the charts. Some airports include holdings for a predetermined time.&lt;br /&gt;
See the RCF procedures for [[http://charts.vacc-austria.org/LOWW/LOWW_Arrival_COM%20Fail%20Procedure_06062011.pdf LOWW]]. Hey guys, where are the RCF procedures for the other LOVV airports?&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Go Around and missed approach  ===&lt;br /&gt;
A Go-Around can be seen as abnormal procedure. Two different procedures can be followed:&lt;br /&gt;
#Missed Approach published in the Charts. APP should be informed about it (via teamspeak or PM).&lt;br /&gt;
#Individual handling like heading and altitude. This has to be coordinated with APP.&lt;br /&gt;
Remember: If necessary for safety, TWR can (and must) tell the aircraft virtually anything the aircraft is able to. If the reason for go-around is in the direction of the go-around procedure, then &amp;quot;proceed as published&amp;quot; does not really make sense. TWR might tell the aircraft to turn off left or right immediately.&lt;br /&gt;
&lt;br /&gt;
Phraseology differs according who announces it:&lt;br /&gt;
*If ATC issues go-around, then the phraseology expresses urgency. Listen to the readback - it is vital that the pilot received it. In this example, the go-around is individual:&lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Leipzig 123, go-around, say again go-around, turn left immediately direct SNU, climb 5000ft.&lt;br /&gt;
LHA123:LHA123 is going around, turning left SNU, climbing 5000ft.&amp;lt;/pre&amp;gt;&lt;br /&gt;
*If the pilot goes around, then he/she announces it. In this example, standard go-around pattern is used:&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Lepzig 123 goes around.&lt;br /&gt;
TWR: Roger, Leipzig 123, go around as published&amp;lt;/pre&amp;gt;&lt;br /&gt;
As a courtesy, you could tell the pilot the go-around procedure anyway - many of them don't know it.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Rejected Take-off  ===&lt;br /&gt;
Rejected takeoff can quickly turn into a nasty situation, if ATC does not react immediately and correctly.&lt;br /&gt;
*If the pilot rejects takeoff, then the approaching traffic should immediately receive go-around. APP should be informed about it. Do not expect the aircraft to leave the runway immediately - something serious might be wrong, so be prepared to change the runway (if you have, like in LOWW).&lt;br /&gt;
*If TWR withdraws takeoff clearance, the situation is even worse, as the aircraft might be rolling already and be beyond v1 where it can't stop (and you as TWR don't know this). In this case, TWR has to do the following:&lt;br /&gt;
#Issue takeoff cancellation: &amp;quot;Leipzig 123, cancel takeoff, say again, cancel takeoff.&amp;quot; The pilot will do, if able (=below V1).&lt;br /&gt;
#Arriving aircraft behind have to be issued a go-around which leads them away from the departure route of the departing aircraft - departing aircraft could be above v1 and fly out.&lt;br /&gt;
#Inform all surrounding ATC stations about the situation.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Malfunctions of airport navigation equipment  ===&lt;br /&gt;
Malfunctions of airport equipment (broken ILS, VOR or NDB) cannot be simulated at VATSIM (navaids are part of pilot software). If an aircraft has broken equipment, then this is actually a &amp;quot;pan-pan&amp;quot; case and should be treated as such. &lt;br /&gt;
&lt;br /&gt;
It could happen that a pilot reports a malfunction (in case his software simulates such a failure - but this failure only affects him. And Still, you could simulate airport malfunctions for all pilots and see, what they will do. In this case, you should know the other approaches available, offer alternatives (and communicate them between TWR and APP). If weather permits, you can offer visual approaches.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Priority Landing  ===&lt;br /&gt;
This is an easy case: A fully functional and communicating aircraft has only one grievance: Get down as soon as possible. Most reasons are medical emergencies, live organs, low fuel (at too low fuel this is an emergency), or VIPs on board (feel free to send him into 2 hours holding and divert to GATB if it is Karl-Heinz Grasser).&lt;br /&gt;
&lt;br /&gt;
Handling is easy: Issue instructions (vectors, descent, and on ground: a gate close to arrival) that best meet his/her request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Runway closure  ===&lt;br /&gt;
&lt;br /&gt;
This procedure is triggered by the TWR controller. There are two different cases:&lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''If the runway has to be closed immediately (broken down aircraft, debris, deer, ...), then the runway closure is imminent:&lt;br /&gt;
#approaching traffic receives go-around&lt;br /&gt;
#APP receives request, not to hand off any more aircraft&lt;br /&gt;
#GND receives information to halt taxi clearances to this runway&lt;br /&gt;
#New runway is opened, GND and APP informed (or airport closed)&lt;br /&gt;
#ATIS adapted.&lt;br /&gt;
&lt;br /&gt;
*'''Step-by-step closure:''' If the reason for closure can be forseen (wind changes slowly, noise abatement rules, then the runway closure is more orderly:&lt;br /&gt;
&lt;br /&gt;
#APP receives request not to hand off any more aircraft and/or divert to new runway&lt;br /&gt;
#GND receives request not to issue taxi clearances tot his runway, and the new one&lt;br /&gt;
#Remaining aircraft receive landing clearance&lt;br /&gt;
#New runway will be opened&lt;br /&gt;
#ATIS adapted&lt;br /&gt;
#APP and GND are informed.&lt;br /&gt;
&lt;br /&gt;
== Emergencies -  4 phases ==&lt;br /&gt;
If a pilot discovers a condition of being threatened by serious and/or&lt;br /&gt;
imminent danger '''and''' of requiring immediate assistance, then he/she will issue an emergency call.&lt;br /&gt;
&lt;br /&gt;
A basic principle is important: The pilot is in command, ATC is here to assist. Don't tell the pilot how to fly the aircraft - it's not your job, and you are not there. The pilot says his intentions, and ATC reacts. This does not mean that you don't order the pilot to do things, but they should be according to his/her intentions, not yours.&lt;br /&gt;
&lt;br /&gt;
Mayday procedure has the following phases:&lt;br /&gt;
&lt;br /&gt;
==== 1) Mayday call by the pilot:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Pilot calls &amp;quot;mayday&amp;quot; three times, the nature of his/her emergency, what his/her intentions are and what he/she needs now. ATC reads back, tells him to set transponder to 7700 (then all ATC see his mayday call on the Euroscope screen: The tag turns red and is preceded with &amp;quot;EMG&amp;quot;). Then the aircraft gets the needed information.&lt;br /&gt;
&lt;br /&gt;
==== 2) standard response by ATC  ====&lt;br /&gt;
The pilot has a few seconds to do (avigate, navigate), and ATC too: He/she needs to inform other pilots and fellow ATC stations.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&amp;lt;/pre&amp;gt;&lt;br /&gt;
With this call pilots know: They should continue as told (their SID, transitions, STAR). They only call ATC, if safety is at stake. If they receive ATC orders, they don't read back - they just do it.&lt;br /&gt;
&lt;br /&gt;
Then ATC informs other controllers via intercom, Text or teamspeak, and collects the necessary information.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Generally, the controller makes sure that he/she does not get any traffic any more: no takeoffs from below, no handoffs from above.&lt;br /&gt;
&lt;br /&gt;
Beyond this point, there is no fixed phraseology. ATC speaks with pilots to make sure that he is served best. With the information gathered, ATC will turn back to the pilot and figure out next steps.&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, for runway 11 maintain present heading, wind 320°4kt. When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
ATC's information is important to pilots: Where can I land and how far it is? Pilots say, that accurate distance is vital, so use the distance tool on your scope.&lt;br /&gt;
&lt;br /&gt;
The pilot's first information is important for controllers: What is wrong? That says a lot about the ability of the pilot to control the aircraft. The last info is important for real life: Emergency services on the ground need to prepare for rescue.&lt;br /&gt;
&lt;br /&gt;
==== 3) All following measures  ====&lt;br /&gt;
There is no strict rules beyond the standard response. Pilot and ATC communicate the way that suits best their situation. The following guidelines are vital:&lt;br /&gt;
*'''Pilot tells, ATC delivers.''' On the flight plan, you read &amp;quot;PIC - pilot in command&amp;quot; - let him stay in command, and let him decide, which command he wants you to take over.&lt;br /&gt;
*'''Communication: least possible, as precise as possible.''' During an emergency, the cockpit is a beehouse. The more time pilots have for themselves, the better. If a pilot does not answer: stay calm - the pilot might follow the rule 1-avigate 2-navigate 3-communicate and might not have reached step 3. He/she may say &amp;quot;ATC standby&amp;quot; or just nothing. To quote a real-life example: [[http://www.youtube.com/watch?v=lICb8p9SvvM don't do this.]]&lt;br /&gt;
*'''Clear needed airspace:''' Noone needs to turn away, if he/she is not in the way. Some traffic might continue as normal. You might consider premature handoffs to other controllers or holdings. As a rule of thumb: don't produce more emergencies than you have already.&lt;br /&gt;
*'''Pilot has the choice of frequency:''' An aircraft can stay on the frequency (eg. TWR) through all stages of his/her emergency or change, if he/she wishes. ATC will adjust. Assume that you have an engine failure at FL100 approaching LOWW. The pilot is on the APP frequency and does not want to change. Either APP coordinates with TWR landing clearance and issues it, or TWR enters the APP frequency and issues landing clearance him/herself.&lt;br /&gt;
&lt;br /&gt;
==== 4)&amp;amp;nbsp;End emergency procedure  ====&lt;br /&gt;
At some stage, the emergency is over, and the aircraft is happily on the runway or unhappy in the wood. At this stage, all other pilots and ATC need to know that it is over:&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Then, cleanup starts: There might be a dozen aircraft in holdings to bring in, runways to clean and aircraft on ground to get out.&lt;br /&gt;
&lt;br /&gt;
== Emergencies - the cases ==&lt;br /&gt;
This list is open - be prepared to react to the unusual. If you discover an emergency which is not covered here, feel free to add it.&lt;br /&gt;
=== Loss of Cabin pressure  ===&lt;br /&gt;
&lt;br /&gt;
This could be a problem in high traffic situations. The pilot will immediately begin an &amp;quot;emergency descent&amp;quot; to FL100 or below (he won't wait for approval). As controller, you can expect that the pilot wants to land as soon as possible. Be prepared that the emergency situation escalates, as there is a reason for the loss of cabin pressure which could cause other systems to fail too.&lt;br /&gt;
&lt;br /&gt;
=== Loss of Hydraulicpressure  ===&lt;br /&gt;
&lt;br /&gt;
This is a major problem, depending on the degree of failure: On large aircraft, all systems for manoever depend on hydraulic pressure. First thing after the usual introduction is to ask the pilot about his/her status - which systems are affected and what this means. It could mean that the pilot cannot deploy speedbrakes (that's trivial) or flaps (that means a long runout on the runway), or cannot perform certain manoevers (like left or right turn etc, or that the plane reacts very slow. As ATC, you should offer the nearest suitable airport and increase separation. Also a loss of hydraulic pressure can escalate quickly into a worse emergency.&lt;br /&gt;
&lt;br /&gt;
===Electrics failure===&lt;br /&gt;
... means that the aircraft has very short time in the air. If all systems rely on battery, it will be drained quickly. &lt;br /&gt;
*Pilots will most likely want the closest suitable airfield.&lt;br /&gt;
*A major power consumer is radio communication. Consider offering solutions which need very short answers.&lt;br /&gt;
*Navigational aids may fail without power. Consider vectors for routing, and monitor headings, as instruments in the cockpit might fail.&lt;br /&gt;
*Expect abnormal approach procedures - shortened, steeper, but maybe with smaller bank angles - the pilot will tell what he is able to.&lt;br /&gt;
&lt;br /&gt;
=== Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Smoke in cockpit is a very challenging situation. The best way is not to lose overview in the situation. Time is critical - the aircraft has to come down really quickly. Contrary to other emergencies, smoke in cockpit means a &amp;quot;talk-down&amp;quot; approach. Supply the pilot with vectors and distance to the nearest airfield. You might consider to supply the pilot with vital information (it could be that he/she cannot see his/her instruments)in regular intervals (minutes or less), like:&lt;br /&gt;
&amp;lt;pre&amp;gt;Mayday Leipzig 123, speed 220 ok, altitude 6000ft ok, heading ok, runway 11 miles&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Such an emergency should definitely land at the next suitable aerodrome, and maybe on a separate runway in case anything goes wrong. Increase separation considerably.&lt;br /&gt;
&lt;br /&gt;
=== Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Engine failures are the most dangerous incidents that can happen: Altitude over ground is low, the aircraft is at full thrust and full of fuel, speed is low. This is the cocktail for a nasty situation. Most frequent reason is bird strike.&lt;br /&gt;
&lt;br /&gt;
Most likely, the bird strike happened already on ground above v1, and the aircraft has to get into the air with reduced engine power. Therefore, TWR is most likely to receive the mayday call. High insecurity adds to this, as it may take time to assess the degree of damage. How much thrust is still left? Is climbing an option? Does the aircraft need to make an emergency U-turn or does it have enough time for a controlled approach?&lt;br /&gt;
&lt;br /&gt;
Workload in the cockpit is very high. Quick, short response and coordination is the key to this situation. More important than in any other situation is to offer solutions, but let the pilot decide. The pilot will tell you, what he is able to and what his intentions are. &lt;br /&gt;
&lt;br /&gt;
Be prepared that the aircraft may not follow the filed SID. It will most likely climb slower, step-climb and need a larger turn radius. In turns, the rate of descent might double.&lt;br /&gt;
&lt;br /&gt;
[http://www.youtube.com/watch?v=9KhZwsYtNDE Here is a perfect example], how it should work: &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;as precise as possible:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Answer ATC:&amp;amp;nbsp;As precise as possible (listen: Thomson 253H has not requested anything, so TWR is offering the prime information which the pilot needs now):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warns all other stations ans waits. the pilot is &amp;quot;in command&amp;quot;, he will call. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Pilot has called, now TWR offers solutions. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Now the pilot says his intentions: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower reads back and done. If the pilot does not want anything else, then TWR keeps quiet. He knows that the pilot will fly a controlled approach via a VOR (Afterwards we will see that his right engine is dead while the left one runs normally - far enough for a modern aircraft to take off and climb). Shortly later he makes the offer to land in Liverpool - which is turned down - the pilot is happy with returning to Manchester. Then TWR reports runway 06R closed because of debris - the aircraft has lost parts of its engine. This is an order to the pilot - he should not land on a closed runway. A short time afterwards, the aircraft lands orderly on 06L.&lt;br /&gt;
&lt;br /&gt;
=== Engine Failure at approach - Triebwerksversagen beim Landeanflug  ===&lt;br /&gt;
&lt;br /&gt;
===Total engine failure===&lt;br /&gt;
For ATC, this is easy, as it means: This aircraft will come down very quickly. In this situation, workload in the cockpit is enormous, as they try to re-light the engines. ATC's job is to analyse every option to reach ground safely and offer them in sequence of relevance.&lt;br /&gt;
&lt;br /&gt;
===(Very) low fuel===&lt;br /&gt;
If fuel is gone, then this is the same situation as a complete engine failure. If such a situation is possible or even likely (=if it could happen within the distance between aircraft and airport), then the aircraft has to be routed to the nearest runway threshold. Again - the pilot decides, bearing in mind that steep turns cost altitude. If no runway can be reached, then anything like it is better than nothing - a taxiway maybe. As ATC, do not allow the aircraft to endanger other aircraft or people.&lt;br /&gt;
&lt;br /&gt;
===Directional Gyro Failure===&lt;br /&gt;
The directional gyro is the &amp;quot;compass&amp;quot; of the aircraft. If the directional gyro fails, then the pilot does not know any more, where north is. Most likely, you as ATC will notice first that the aircraft goes into strange circles.&lt;br /&gt;
*Normally, aircraft have a standard mechanic magnetic compass in sight - a simple ball. This is not enough to fly a vector, but good enough to fly a visual approach.&lt;br /&gt;
*(it happened to me once) If the pilot has no compass (or iPhone) to look at, then the ground is the only possible visual reference. ATC can approve descent to minimum altitude until ground contact. Then, incremental turns can be issued: &amp;quot;turn 20° left from present heading&amp;quot; - until runway is in sight.&lt;br /&gt;
&lt;br /&gt;
===Landing gear failure===&lt;br /&gt;
*If landing gear fails to retract after takeoff, then this is a pan-pan situation. Crew can continue normally, but with reduced speed and more fuel consumption - crew will recalculate if they need a diversion. For ATC this means to accomodate crew's wishes.&lt;br /&gt;
*A broken tyre could prevent the aircraft from retracting the gear. Landing with a flat tyre is already an emergency, as the aircraft could become unstable after touchdown. For ATC this means: Clear the runway, increase spacing behind and alert fire services.&lt;br /&gt;
*If the aircraft fails to expand gear, then the situation is more critical. The only thing pilot see is their warning lights (they can't get out and see). This will occur in the last 10miles final. First reaction is a go-around to gain time to analyse the problem. In real life, the aircraft performs a low approach and technicians look at the aircraft from below. If gear fails to expand properly, then an attempted landing is imminent (at some point, the aircraf ''must'' land). This is an emergency. For ATC: Clear the runway, increace spacing behind and alert fire services.&lt;br /&gt;
&lt;br /&gt;
=== THIS PART AWAITS MORE. DO YOU KNOW MORE? ===&lt;br /&gt;
&lt;br /&gt;
=== Multiple emergencies ===&lt;br /&gt;
There is nothing more challenging than multiple emergencies, as you as controller have to rank its severity and propose measures that all of them can accomodated. If emergencies collide, you have to set priorities:&lt;br /&gt;
*Aircraft which risk to go down soon have priority to those which can still fly for a few minutes (all-engine failure is first compared to hydraulics failure).&lt;br /&gt;
*Aircraft which need to be on the ground first are first (passenger with heart attack is first compared to low - but not empty - fuel).&lt;br /&gt;
*More people saved is better than less (full engine failure has priority compared with a passenger with heart attack).&lt;br /&gt;
Nothing is heavier than taking these decisions. Let's be happy to fly online.&lt;br /&gt;
&lt;br /&gt;
=Further reading=&lt;br /&gt;
A [[http://www.skybrary.aero/bookshelf/books/200.pdf brochure by the British Air Traffic Authorities]] is an excellent reference for controllers.&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1758</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1758"/>
		<updated>2012-03-15T22:05:50Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport have the following main tasks: &lt;br /&gt;
&lt;br /&gt;
#maintain an orderly flow of traffic &lt;br /&gt;
#provide separation service between aircraft &lt;br /&gt;
#provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Separation  =&lt;br /&gt;
&lt;br /&gt;
=== Vertical separation  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;airspace or 2000 feet above FL290 in non-RVSM&amp;amp;nbsp;airspaces. To fly within RVSM an aircraft must be equipped with: &lt;br /&gt;
&lt;br /&gt;
#2 independent altimeters &lt;br /&gt;
#an autopilot witch must be able to hold an specific altitude &lt;br /&gt;
#min. Mode C transponder&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lateral separation  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Wake turbulence separation  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Takeoff&amp;lt;br&amp;gt;  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Landing  =====&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;width: 415px; height: 256px;&amp;quot; class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Preceding aircraft &lt;br /&gt;
! Following aircraft &lt;br /&gt;
! Minimum radar separation&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; | Super &lt;br /&gt;
| Super &lt;br /&gt;
| 4 [[Nautical mile|NM]]&lt;br /&gt;
|-&lt;br /&gt;
| Heavy &lt;br /&gt;
| 6 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 7 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 8 NM&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;3&amp;quot; | Heavy &lt;br /&gt;
| Heavy &lt;br /&gt;
| 4 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| Small &lt;br /&gt;
| &lt;br /&gt;
4 NM &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*Staying on or above leader's glide path&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Separation with individual speeds&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;minimum clean&amp;quot; (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.&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: AUA14F, speed 220 knots indicated.&lt;br /&gt;
AUA14F:       Speed 220 Knots, AUA14F.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
If the pilot reports &amp;quot;unable&amp;quot; ask the pilot witch speed would be suitable for his current situation. Its important to know that aircraft like a Boeing 747 with a lot of payload on an long distance leg are unable to stay below 250 knots during departure.&lt;br /&gt;
&lt;br /&gt;
*'''The phrase &amp;quot;&amp;lt;strike&amp;gt;Reduce to minimum approach speed&amp;lt;/strike&amp;gt;&amp;quot; shall not be used!'''&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; ==References==&amp;lt;!-- AnimalBiology56:535. --&amp;gt;&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
http://en.wikipedia.org/wiki/Wake_turbulence&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:Tower&amp;diff=1757</id>
		<title>Study Guide:Tower</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:Tower&amp;diff=1757"/>
		<updated>2012-03-15T14:40:24Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: /* Departing Traffic */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''&amp;lt;span style=&amp;quot;color:#ff0000;&amp;quot;&amp;gt;This study guide is still work in progress. Stay tuned for further chapters.&amp;lt;/span&amp;gt;''' &lt;br /&gt;
&lt;br /&gt;
== Introduction  ==&lt;br /&gt;
&lt;br /&gt;
This Study Guide is designed to give you all the information you need to become a Tower Controller within VACC Austria. We assume that you have already read the Delivery and Ground Study Guides and that you have some experience controlling on VATSIM. &lt;br /&gt;
Since you will handle aircraft in the air for the first time, we want to discuss some basic principles of flying before actually talking about procedures. Also we'll have to talk about some organisational issues. The fourth chapter of this article will then familiarize you with the procedures you need for controlling tower positions.&lt;br /&gt;
&lt;br /&gt;
== Aircraft and basic Flying Principles  ==&lt;br /&gt;
&lt;br /&gt;
=== Producing Lift  ===&lt;br /&gt;
&lt;br /&gt;
For an aircraft to fly the lift force produced by (mostly) the wings has to outweigh the gravitational force that affects the aircraft. &lt;br /&gt;
&lt;br /&gt;
Basically a wing produces lift by deflecting the air it moves through into one direction. According to Newton's third law of motion the lift is produced into the opposite direction. This lift grows with the speed the aircraft has in relation to the air and with the angle the wing draws with the direction of movement. This angle is called Angle of Attack (AoA). &lt;br /&gt;
&lt;br /&gt;
The principle only works as long as a steady airflow around the wing exists. As soon as the airflow seperates from the wings surface the lift starts to decerease. The AoA at which this occurs is called critical Angle of Attack. It depends on the profile of the wing and it's dimensions but for subsonic aircrafts it typically lies between 8 and 21 degrees. &lt;br /&gt;
&lt;br /&gt;
Think of an level flying aircraft that reduces it speed. In order to compensate the reducing lift the pilot has to raise the nose. However at some point the Angle of Attack will cross the critical angle of Attack and the pilot will find himself in a stall. So the speed of an aircraft is limited on the lower side by the so called stall speed. Because the stall speed depends on the profile most aircraft are equipped with devices that alter the profile during flight such as flaps or slats. &lt;br /&gt;
&lt;br /&gt;
On approach pilots have to fly in a certain speed range in order to conduct a safe landing. The lower boundary is called landing reference speed and is often a fixed multiple of the stall speed. As a result of this the approach speed also depends on weight an aircraft configuration (Flap/Slat setting). For safety the Approach Vapp is higher than Vref and the difference depends mostly on the weather conditions. &lt;br /&gt;
&lt;br /&gt;
Generally you can say that bigger aircraft also have a bigger approach speed however at some point this rule does not work anymore because the Vref depends largely on the aircrafts weight in relation to it's maximum takeoff weight (MTOW). The speed ranges from 50 knots in a C150 up to 170 knots with a fully loaded 747. However for example it is possible that a light 747 is slower than a fully loaded 737. &lt;br /&gt;
&lt;br /&gt;
=== Aircraft Categories  ===&lt;br /&gt;
&lt;br /&gt;
The most important ways of categorizing aircraft in aviation are by weight or by approach speed. &lt;br /&gt;
&lt;br /&gt;
==== Weight Categories  ====&lt;br /&gt;
&lt;br /&gt;
Aircraft are categorized into three weight categories: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| '''Category''' &lt;br /&gt;
| '''MTOW'''&lt;br /&gt;
|-&lt;br /&gt;
| Light Aircraft (L) &lt;br /&gt;
| &amp;amp;lt; 7 000 kg&lt;br /&gt;
|-&lt;br /&gt;
| Medium Aircraft (M) &lt;br /&gt;
| 7 000 – 136 000 kg&lt;br /&gt;
|-&lt;br /&gt;
| Heavy Aircraft (H) &lt;br /&gt;
| &amp;amp;gt;136 000 kg&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
You can find a list of aircrafts in this link [http://www.skybrary.aero/index.php?title=Category:Aircraft&amp;amp;until=D228] &amp;lt;br&amp;gt;Weight depicted is MTOW. &lt;br /&gt;
&lt;br /&gt;
==== Approach Speed  ====&lt;br /&gt;
&lt;br /&gt;
Aircraft are categorized by their reference approach speed (Vref) at maximum landing weight: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| '''Category''' &lt;br /&gt;
| '''Vref'''&lt;br /&gt;
|-&lt;br /&gt;
| A &lt;br /&gt;
| &amp;amp;lt;= 90 knots&lt;br /&gt;
|-&lt;br /&gt;
| B &lt;br /&gt;
| 91 - 120 knots&lt;br /&gt;
|-&lt;br /&gt;
| C &lt;br /&gt;
| 121 - 140 knots&lt;br /&gt;
|-&lt;br /&gt;
| D &lt;br /&gt;
| 141 - 165 knots&lt;br /&gt;
|-&lt;br /&gt;
| E &lt;br /&gt;
| &amp;amp;gt;= 165 knots&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Before you start controlling==&lt;br /&gt;
&lt;br /&gt;
Tower is responsible for all movements on the runways as well as for all movements within the control zone. He decides which runways are in use and maintains the ATIS. Tower is also responsible for ground and delivery if they are not online. &lt;br /&gt;
&lt;br /&gt;
=== Airspace Structure around Major Airports  ===&lt;br /&gt;
Major airports in Austria are surrounded by a so called control zone which is a class D airspace. This means that all aircraft need a clearance to enter this piece of airspace. So either they are cleared to an approach or you need to clear them specifically into the control zone. Details will be discussed in the VFR part later on.&lt;br /&gt;
&lt;br /&gt;
===Choosing the active runways===&lt;br /&gt;
The guiding principle in choosing the active runways is that aircraft prefer to depart into direction the wind is coming from.&lt;br /&gt;
 An airport has one runway named 16/34. The wind is reported as 320 degrees at 14 knots. In &lt;br /&gt;
 this case runway 34 is chosen as the active runway.&lt;br /&gt;
However due to noise abatement and terrain considerations most airports have some kind of preferential runway system. Tailwind components of up to five knots are normally accepted in these cases. &lt;br /&gt;
Bear in mind that it is the pilots decision whether he can accept a certain runway because only he knows the performance of his aircraft.&lt;br /&gt;
&lt;br /&gt;
For details on the preferred runway configurations for a specific airport ask your mentor.&lt;br /&gt;
&lt;br /&gt;
=== ATIS  ===&lt;br /&gt;
&lt;br /&gt;
ATIS stands for Automatic Terminal Information Service and is a usually automatically generated broadcast that contains essential informations for pilots. It is continuously broadcasted on a dedicated frequency. On initial contact with the controller, pilots should already have listened to the ATIS and state the identifying letter. &lt;br /&gt;
&lt;br /&gt;
A ATIS broadcast has to consist of: &lt;br /&gt;
&lt;br /&gt;
*Name of the Airport &lt;br /&gt;
*Identification Letter &lt;br /&gt;
*Time of Observation &lt;br /&gt;
*Active Runways &lt;br /&gt;
*Transition Level &lt;br /&gt;
*Wind direction and velocity &lt;br /&gt;
*Visibilities &lt;br /&gt;
*Special weather conditions (such as rain) &lt;br /&gt;
*Cloud ceiling &lt;br /&gt;
*Temperature and Dewpoint &lt;br /&gt;
*QNH &lt;br /&gt;
*Trends&lt;br /&gt;
&lt;br /&gt;
It is updated every 30 minutes or as soon as significant changes occur. In practice the ATIS function of Euroscope should be used. You can find the necessary files [http://www.vacc-austria.org/index.php?page=content/static&amp;amp;id=SOFTWARE_ATC here]. Please consult enclosed readme for information how to use this package.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Transition Altitude/Transition Level  ===&lt;br /&gt;
&lt;br /&gt;
Knowing the altitude you are flying is one of the most important informations you need in order to safely operate an airplane. Aircraft Altimeters use the air pressure around them to determine their actual altitude. In order to get correct readings you have to use the actual local pressure in your area. As a memory hook you can use this: The altimeter needle moves in the same direction you turn the rotary knob to adjust the pressure. If you turn it counterclockwise, the needle also turns counterclockwise and therefor indicates a lower altitude. &lt;br /&gt;
&lt;br /&gt;
On the other hand it would not be very practical to use the local pressure while flying at higher altitudes, since terrain is not an issue here and you would have to set a new pressure setting in your altimeter every few minutes. &lt;br /&gt;
&lt;br /&gt;
To avoid this pilots use the local pressure when departing from an airport until they pass the so called Transition Altitude (TA), where they set the so called standard pressure (QNH 1013 hpa or Altimeter 29.92 inHg). They continue to use this setting until they descend through the Transition Level (TRL) at their destination airport (or an airport on their route), where they set the local pressure again. &lt;br /&gt;
&lt;br /&gt;
In airport charts only TA is given, whereas TRL has to be determined by ATC. Use the following table to calculated your TRL: &lt;br /&gt;
&lt;br /&gt;
 QNH      &amp;amp;lt; 0977: TA + 3000 ft.&lt;br /&gt;
 QNH 0978 - 1012: TA + 2000 ft.&lt;br /&gt;
 QNH 1013 - 1050: TA + 1000 ft.&lt;br /&gt;
 QNH 1051 &amp;amp;gt;    &amp;amp;nbsp;: TA = TL&lt;br /&gt;
&lt;br /&gt;
The room between TA and TRL is called Transition layer. It ensures that the minimum spacing of 1000 ft between aircraft flying in lower part (with local pressure) and the upper part (using Standard pressure).&lt;br /&gt;
&lt;br /&gt;
== Working as a Tower Controller  ==&lt;br /&gt;
&lt;br /&gt;
===Setting the right priorities===&lt;br /&gt;
The moment you are responsible for more than one aircraft you will have to set priorities in your handling. As a general guideline aircraft in the air take precedence to aircraft on the ground. This also means that you will have to tell pilots to stand by while you attend to other matters. Make sure you keep a list of aircraft you told to stand by so you don't forget to call them back.&lt;br /&gt;
&lt;br /&gt;
=== Runway Separation  ===&lt;br /&gt;
&lt;br /&gt;
The runways are one of the most dangerous spots on an airport because aircraft are travelling at high speed with little room to maneuver and most of the time no ability to stop at a reasonable distance. Because of this the general rule is that '''&amp;lt;span style=&amp;quot;color:#ff0000;&amp;quot;&amp;gt;only one aircaft may be cleared to use a runway at the same time.&amp;lt;/span&amp;gt;''' What this means practically and exceptions from this rule are explained in the following chapters. &lt;br /&gt;
&lt;br /&gt;
=== Departing Traffic  ===&lt;br /&gt;
&lt;br /&gt;
So now we are at the point where the pilot reaches the Holding Point of his departure runway and reports ready for departure. What are the things you should check before issuing the takeoff clearance? &lt;br /&gt;
&lt;br /&gt;
*Have a look at the flightplan. Take note of the type of aircraft and the Departure Route. &lt;br /&gt;
*Check the traffic approaching the runway.&lt;br /&gt;
&lt;br /&gt;
To give him the takeoff clearance the following phrase should be used: &lt;br /&gt;
&lt;br /&gt;
  e.g.: TWR: AUA2CM, wind 320 degerees, 7 knots, Runway 29, cleared for takeoff.&lt;br /&gt;
 AUA2CM: Cleared for takeoff Runway 29, AUA2CM&lt;br /&gt;
&lt;br /&gt;
The pilot lines up on the runway, advances the throttle and takes off. When he is well established in climb check he is squawking Mode C and the right Code. Afterwards he is handed off to the next Controller, in this case a radar position:&lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_TWR: AUA2CM, contact Wien Radar frequency 128.20, bye bye!&lt;br /&gt;
AUA2CM: Contacting Wien Radar on frequency 128.20, AUA2CM. &amp;lt;/pre&amp;gt; &lt;br /&gt;
The next aircraft reports ready for departure. Again check the points above, but this time we cannot give the takeoff clearance straight away because the preceeding aircraft is still occupying the runway. Now you get to know the first exception to the Runway Seperation rule above. To speed things up you can instruct the next aircraft to line up behind the first one while this one is still in the takeoff roll occupying the runway: &lt;br /&gt;
&lt;br /&gt;
  TWR: AZA639, behind departing Austrian Airbus A319, line-up rwy 29 and wait behind.&lt;br /&gt;
 AZA639: behind departing Airbus lining up runway 29 and waiting behind, AZA639.&lt;br /&gt;
 ''Note: The two times behind in this instruction is not a typing error but was implemented''&lt;br /&gt;
 to emphasize that part of the clearance.&lt;br /&gt;
&lt;br /&gt;
This type of clearance is called a conditional clearance. &amp;lt;br&amp;gt; The earliest possible point where you can issue the next takeoff clearance is, when the preceeding aircraft has overflown the opposite runway end or has clearly turned onto either side of it.&amp;lt;br&amp;gt; However in some cases this could be very close which leads us to the next chapter but before lets have a look on helicopters. &lt;br /&gt;
&lt;br /&gt;
Helicopters are sometimes able to start from there current position like a Helipad or a normal stand, if he want to depart from a Runway you can use the normal Phrases for VFR Traffic. &lt;br /&gt;
&lt;br /&gt;
 e.g.: OEATD: Wien Tower, OEATD at General Aviation Parking ready for departure.&lt;br /&gt;
 TWR: OEATD, Wien Tower, after departure leave control zone via Freudenau and Donauturm, 2500 feet or below, Wind 290° 6 Knots, present position cleared for take-off.&lt;br /&gt;
 OEATD: After departure leaving the control zone via Freudenau and Donauturm not above 2500 feet, present position cleared for take-off.&lt;br /&gt;
&lt;br /&gt;
=== Departure Seperation  ===&lt;br /&gt;
&lt;br /&gt;
==== Based on Type of Aircraft and departure route  ====&lt;br /&gt;
&lt;br /&gt;
One of the main tasks of air traffic control is to keep aircraft at a safe distance to each other. So imagine the following situation: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
*Two aircraft are departing right after each other. &lt;br /&gt;
*The first aircraft is a relatively slow Cessna 208 (~around 70 knots in climb), the second one a fast Boeing 767 (140-180 knots on the initial climb). &lt;br /&gt;
*Both follow the same departure route.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Obviously it would not take long until the B767 catches up with the Cessna, a potentially very dangerous situation! You can see, that it is very important to check the flightplan of the aircraft you are about to clear for takeoff. &amp;lt;br&amp;gt; The minimum radar seperation in the area around an airport is 3 nm or 1000 feet. These are the limits radar stations have to obey. Tower Controllers should aim to achieve the following seperation for departing aircraft following departure routes which share a common part: &lt;br /&gt;
&amp;lt;div align=&amp;quot;left&amp;quot;&amp;gt;&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| Fast followed by slow &lt;br /&gt;
| 3 nm&lt;br /&gt;
|-&lt;br /&gt;
| Matching Types &lt;br /&gt;
| 5 nm&lt;br /&gt;
|-&lt;br /&gt;
| Slow followed by fast &lt;br /&gt;
| 10 nm&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
In extreme examples like the one above it is often more advisable to coordinate with APP to find another solution. Often this involves clearing the aircraft to a non standard altitude or departure route: &lt;br /&gt;
&lt;br /&gt;
  TWR: DLH2441, after departure maintain runway heading, climb initially to 3000 ft&lt;br /&gt;
 DLH2441: After departure maintaining runway heading, climbing to 3000 ft, DLH2441 &lt;br /&gt;
 TWR: DLH2441, wind 320 degrees at 9 knots, runway 29, cleared for takeoff&lt;br /&gt;
 DLH2441: Cleared for takeoff runway 29, DLH2441&lt;br /&gt;
&lt;br /&gt;
The other main task of ATC is to expedite the flow of traffic. Situation: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
*You have numerous aircraft departing from the same runway, following different departure routes. Some of them involve immediate right turns other SIDs immediate left turns. &lt;br /&gt;
*There are two holdingpoints available.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
It would benificial to use the gaps that arise between the aircraft using similar Departure Routes, so in close coordination with ground you should try to distribute aircraft over the holding points in a way to be able to fill those gaps. &lt;br /&gt;
&lt;br /&gt;
==== Based on Wake Turbulence Category  ====&lt;br /&gt;
&lt;br /&gt;
There are two ways aircraft influence the air around them when passing through it: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
*Jetwash produced by the engines &lt;br /&gt;
*Turbulence created at the wings and especially at the wingtips&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This turbulence can cause severe problems or even loss of control for following aircraft. The wake turbulence categories are based on the Maximum Takeoff weight (MTOW) of the aircraft: &lt;br /&gt;
&amp;lt;div align=&amp;quot;left&amp;quot;&amp;gt;&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| Light Aircraft (L) &lt;br /&gt;
| &amp;amp;lt; 7 000 kg&lt;br /&gt;
|-&lt;br /&gt;
| Medium Aircraft (M) &lt;br /&gt;
| 7 000 – 136 000 kg&lt;br /&gt;
|-&lt;br /&gt;
| Heavy Aircraft (H) &lt;br /&gt;
| &amp;amp;gt;136 000 kg&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/div&amp;gt; &lt;br /&gt;
For departing aircraft, 2 minutes separation (3 minutes if the succeeding aircraft departs from an intersection) is applied when an aircraft in wake turbulence category LIGHT or MEDIUM departs behind an aircraft in wake turbulence category HEAVY, or when a LIGHT category aircraft departs behind a MEDIUM category aircraft.&amp;lt;br&amp;gt; You may issue a take-off clearance to an aircraft that has waived wake turbulence separation, except, if it's a light or medium aircraft departing as follows: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
*Behind a heavy a/c and takeoff is started from an interception or along the runway in the direction of take-off. &lt;br /&gt;
*Behind a heavy a/c that is taking off or making a low or missed approach in the opposite direction on the same runway. &lt;br /&gt;
*Behind a heavy a/c that is making a low or missed approach in the same direction of the runway.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
To point out this hazard to a pilot the following phrase should be used: &lt;br /&gt;
&lt;br /&gt;
  TWR:ESK32C, behind departing heavy B777 line up runway 16 behind and wait,&lt;br /&gt;
 &amp;lt;u&amp;gt;caution wake turbulence.&amp;lt;/u&amp;gt;&lt;br /&gt;
 ESK32C: behind departing B777 lining up rwy 29 and waiting, ESK32C.&lt;br /&gt;
&lt;br /&gt;
=== Arriving Traffic  ===&lt;br /&gt;
&lt;br /&gt;
Arriving Aircraft call you when they are established on an approach to a runway. Most of the time this is an ILS Approach but also other kinds are possible. &lt;br /&gt;
&lt;br /&gt;
  MAH224:Linz Tower, MAH224 established ILS Approach rwy 27.&lt;br /&gt;
&lt;br /&gt;
Again you are not allowed to clear more than one aircraft onto the same runway at the same time.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| In order to issue a landing clearance &lt;br /&gt;
#preceeding departing traffic must have overflown the opposite runway threshold or clearly turned onto either side of the runway. &lt;br /&gt;
#preceeding landing traffic must have left the runway safety strip with all parts. &lt;br /&gt;
#traffic crossing the runway must have left the runway safety strip with all parts.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
If these conditions are met use the following phrase to clear the aircraft: &lt;br /&gt;
&lt;br /&gt;
  TWR:MAH224, Linz Tower, wind 300 degerees at 16 knots, runway 27, cleared to land.&lt;br /&gt;
 MAH224:cleared to land runway 27, MAH224.&lt;br /&gt;
&lt;br /&gt;
During periods of high traffic it is likely that you have more than one aircraft approaching the same runway at the same time. Approach has to ensure the minimum radar seperation of 3 nm and additionally increased seperation due to wake turbulence. &lt;br /&gt;
&lt;br /&gt;
  AUA26T:Linz Tower, AUA26T established ILS 27.&lt;br /&gt;
 TWR:AUA26T, Linz Tower, continue approach, wind 300 degrees at 16 knots.&lt;br /&gt;
 AUA26T:continuing approach, AUA26T.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| Meanwhile MAH224 has left the runway.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
  TWR:AUA26T wind 310 degrees at 14 knots, runway 27 cleared to land.&lt;br /&gt;
 AUA26T:Runway 27, cleared to land, MAH224.&lt;br /&gt;
&lt;br /&gt;
Often it is useful to give pilots additional information, such as traffic information or wind: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| CSA276 is following NLY7751 (A320):&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
  CSA276: Wien Tower, CSA276 established ILS 34.&lt;br /&gt;
 TWR:CSA276, Wien Tower, preceeding traffic is a NLY Airbus A320 3,5 nm ahead of you, continue&lt;br /&gt;
 approach runway 34, wind 010 degrees at 4 knots.&lt;br /&gt;
 CSA276:We have the airbus in sight continuing approach, CSA276.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| AUA81 is approaching runway 16, OE-AGA is on left base runway 16 and there is a rescue helicopter operating in the area around Freudenau.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
  AUA81:Wien Tower, AUA81 established ILS 16&lt;br /&gt;
 TWR:AUA81, Wien Tower, VFR traffic is on left base rwy 16, continue approach, wind 140&lt;br /&gt;
 degrees at 7 knots.&lt;br /&gt;
 AUA81:continuing approach, AUA81.&lt;br /&gt;
 TWR:AUA81, There is an helicopter operating west of the extended centerline, presently at&lt;br /&gt;
 your one o'clock position, 5 nm, 1400 ft.&lt;br /&gt;
 AUA81: Thank you, looking out, AUA81.&lt;br /&gt;
 AUA81: traffic in sight, AUA81.&lt;br /&gt;
&lt;br /&gt;
Helicopters don't need a Runway for the approach, sometimes they are able to land at their parking position, lets have a look on the Phrases. &lt;br /&gt;
&lt;br /&gt;
 eg. the rescue helicopter from the example above needs to land on your airport:&lt;br /&gt;
 OEATD: Wien Tower, request landing at the General Aviation Terminal.&lt;br /&gt;
 TWR: OEATD, wind 010 degreees 4 knots direct General Aviation Terminal, cleared to land.&lt;br /&gt;
&lt;br /&gt;
To give you an idea how dense traffic can get in real life consider that during peak times and good weather the seperation is reduced to 2,5 nm. This equals to one landing every 75 seconds. However on VATSIM the minimum seperation is 3 nm which already requires good cooperation from all the pilots involved. &lt;br /&gt;
&lt;br /&gt;
=== Merging Departing and Arriving Traffic  ===&lt;br /&gt;
&lt;br /&gt;
And now to the most fun part of being a Tower Controller. Sometimes you get into the situation that you use the same runway for departures and arrivals. Either your airport has only one runway or weather demand this configuration. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; Still the above rule of only one aircraft at the same time applies, however we also use conditional clearances which look very similar to those above in the departing traffic section. &lt;br /&gt;
&lt;br /&gt;
 LOWW_TWR: AUA123, Traffic short final RWY 29, C750, report in sight&lt;br /&gt;
 AUA123: Traffic in sight, AUA123&lt;br /&gt;
 LOWW_TWR: AUA123, behind landing C750 line up RWY 29 behind and wait&lt;br /&gt;
 AUA123: Behind landing C750 lining up RWY 29 behdind and waiting, AUA123&lt;br /&gt;
&lt;br /&gt;
To avoid misunderstandings, this time we make sure that the Pilot has the the landing aircraft in sight. You don't have to worry about wake turbulence seperation between landing and departing aircraft since they never cross through each others wake. &lt;br /&gt;
&lt;br /&gt;
To depart an aircraft in front of an approaching aircraft at the time of the departure clearance given the arriving aircraft should not be closer than 4 nm to touchdown. To squeeze a departing aircraft between two arrivals you normally need a minimum of 6 nm between them. It is important for you to check carefully if you have the necessary gap, so have a close look at the distance between the arrivals and their speed. If the second one comes in faster than normal consider this in your calculation. Also you should make sure, that the pilot will be ready for departure when you need him to depart. To check this use the following phrase: &lt;br /&gt;
&lt;br /&gt;
 Callsign, are you ready for immediate departure?&lt;br /&gt;
&lt;br /&gt;
Again it is a good idea to give the pilot an idea of the traffic situation around him. &lt;br /&gt;
&lt;br /&gt;
Example: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| You are the Tower Controller at Vienna airport. Runway 29 is active for departures and arrivals. One aircraft is on a 5 nm final, one at 12 nm out. Additionally you have two departures waiting at the holding point of ruwnay 29.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 TWR:CAL275, are you ready for immediate departure?&lt;br /&gt;
 CAL275:Affirmitive, ready for immediate departure, CAL275&lt;br /&gt;
 TWR:Traffic is now at a 4 nm final, wind 300 degrees at 7 knots, runway 29 cleared for&lt;br /&gt;
 immediate takeoff.&lt;br /&gt;
 CAL275:cleared for immediate takeoff runway 29, CAL275&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| After the CAL B747 has taken off.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 TWR:AUA289, wind 300 degrees at 7 knots, runway 29, cleared to land.&lt;br /&gt;
 AUA289:Runway 29, cleared to land, AUA289.&lt;br /&gt;
 TWR:AUA2LT, traffic is an AUA Airbus A320 on a 2 nm final rwy 29, do you have traffic in sight?&lt;br /&gt;
 AUA2LT:Traffic in sight, AUA2LT.&lt;br /&gt;
 TWR:AUA2LT, behind landing traffic line up runway 29 behind and wait.&lt;br /&gt;
 AUA2LT:Behind the landing Airbus, lining up runway 29 behind and waiting, AUA2LT.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| AUA289 has vacated the runway.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 TWR:AUA2LT, wind 300 degrees at 8 knots, runway 29 cleared for takeoff, landing traffic is&lt;br /&gt;
 now on a 3,5 nm final.&lt;br /&gt;
 AUA2LT:cleread for takeoff runway 29, AUA2LT.&lt;br /&gt;
&lt;br /&gt;
=== VFR Traffic  ===&lt;br /&gt;
&lt;br /&gt;
==== Differences to handling of IFR Traffic  ====&lt;br /&gt;
&lt;br /&gt;
The essential collision safety principle guiding the VFR pilot is &amp;quot;see and avoid.&amp;quot; Pilots flying under VFR assume responsibility for their separation from all other aircraft and are generally not assigned routes or altitudes by air traffic control. Governing agencies establish specific requirements for VFR flight, consisting of minimum visibility, distance from clouds, and altitude to ensure that aircraft operating under VFR can be seen from a far enough distance to ensure safety. &lt;br /&gt;
&lt;br /&gt;
To guide VFR TRaffic through your airspace you make use of VFR Routes, Sectors and reporting Points. '''Used phrases''': &lt;br /&gt;
&lt;br /&gt;
 TWR:OE-AGA, enter control zone via VFR route Klosterneuburg – Freudenau, 1500ft or below,&lt;br /&gt;
 QNH 1020, Squawk 4604, report XXXX (i.e. Freudenau), expect runway 29.&lt;br /&gt;
 TWR:OE-AGA hold (orbit) overhead XXXX (i.e. Freudenau) in XXXX (i.e. 2500ft)&lt;br /&gt;
&lt;br /&gt;
VFR flights should be guided into downwind, base and final leg for landing.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 TWR:OE-AGA, enter downwind for runway 29, report on downwind&lt;br /&gt;
 TWR:OE-AGA, enter base for runway 29, report on base&lt;br /&gt;
&lt;br /&gt;
VFR Flights get their Clearance from &amp;lt;u&amp;gt;Tower&amp;lt;/u&amp;gt;. After startup, they will contact Ground for taxi, thereafter the Tower will issue the clearance. A possible VFR clearance could be:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 TWR:OE-AGA, verlassen Sie die Kontrollzone über Sichtflugstrecke Klosterneuburg, 1500 Fuß&lt;br /&gt;
 oder darunter, QNH 1014, Squawk 4607, Rechtskurve nach dem Abheben so bald als möglich.&lt;br /&gt;
 TWR:OE-AGA, leave controlzone via VFR-route Klosterneuburg, 1500 feet or below,&lt;br /&gt;
 QNH 1014, Squawk 4607,  right turn after departure as soon as possible.&lt;br /&gt;
&lt;br /&gt;
 TWR:OE-AGA, steigen sie auf 3500 Fuß, melden Sie Donauturm.&lt;br /&gt;
 TWR:OE-AGA, climb 3500 feet, report Donauturm.&lt;br /&gt;
&lt;br /&gt;
In the air ATC provides traffic information. &lt;br /&gt;
&lt;br /&gt;
 TWR:OE-AGA, Traffic at your 12 o'clock position, 2100 feet, a PA28 on VFR inbound&lt;br /&gt;
 route Klosterneuburg-Freudenau.&lt;br /&gt;
&lt;br /&gt;
When the aircraft leaves the controlzone. &lt;br /&gt;
&lt;br /&gt;
 TWR:OE-AGA, set Sqauwk 7000, leaving frequency is approved.&lt;br /&gt;
&lt;br /&gt;
Wien Tower/Turm can also be contacted in German. &lt;br /&gt;
&lt;br /&gt;
==== Merging in VFR Traffic  ====&lt;br /&gt;
&lt;br /&gt;
To manage VFR Traffic efficiently you have to use traffic information and visual seperation. &lt;br /&gt;
&lt;br /&gt;
 TWR: OE-ANX, traffic at your 3 o´clock position, moving right to left, B767, distance 2.5&lt;br /&gt;
 miles, report mentioned traffic in sight&lt;br /&gt;
 OE-ANX: Traffic in sight, OE-ANX&lt;br /&gt;
&lt;br /&gt;
Because of other traffic it might be necessary for the aircraft to remain in the downwind leg until the traffic has passed: &lt;br /&gt;
&lt;br /&gt;
 TWR:OE-AGA, fly extended right downwind, standby for base.&lt;br /&gt;
 OE-AGA: Extending right downwind, OE-AGA&lt;br /&gt;
&lt;br /&gt;
To instruct the aircraft to continue it's approach use the following procedure: &lt;br /&gt;
&lt;br /&gt;
 TWR: OE-ANX, traffic at your 3 o´clock position, moving right to left, B767, distance 2.5&lt;br /&gt;
 miles, report mentioned traffic in sight&lt;br /&gt;
 OE-ANX: Traffic in sight, OE-ANX&lt;br /&gt;
 TWR:OE-AGA, behind B767 traffic, enter final RWY 29, caution wake turbulence&lt;br /&gt;
 OE-AGA: Behind B767, enter final RWY 29 behind, caution wake turbulence, OE-ANX&lt;br /&gt;
&lt;br /&gt;
When using an extended downwind you should always consider that the aircrafts speed might be considerably lower than the speed of other aircrafts involved. So if an aircraft has to fly a long way out it might take some time for it to come all the way back, generating a big gap in the arrival sequence. Instead you should aim to keep the plane within the vicinity of the airfield: &lt;br /&gt;
&lt;br /&gt;
 TWR: OE-AGA, Make a right three-sixty.&lt;br /&gt;
 OE-AGA: Making three-sixty to the right.&lt;br /&gt;
 TWR: OE-AGA, Orbit left&lt;br /&gt;
 OE-AGA: Orbiting left, OE-AGA&lt;br /&gt;
&lt;br /&gt;
The second instructions means, that the pilot should make orbits until further advice. &lt;br /&gt;
&lt;br /&gt;
==== Information Positions  ====&lt;br /&gt;
&lt;br /&gt;
=== Coordination with other ATC Stations ===&lt;br /&gt;
''Communication from one controller to another is as important as the communication from controller to pilot.'' This is especially true during high traffic situations where you might be tempted to concentrate solely on what is happening on your frequency. In these situations don't hesitate to take a call from a fellow controller even if it means that a pilot has to wait before you call him back. Secondly if you know a controller is busy, try to keep your conversation with him concise and avoid chatting in a teamspeak channel next to him.&lt;br /&gt;
&lt;br /&gt;
Within VACC Austria we usually use teamspeak to coordinate with each other. The coordination with other ATC units is mostly done per private chat.&lt;br /&gt;
Other means of communication are the Intercom functions of Euroscope which would be a very nice feature, however often they only work with certain controllers. The ATC Channel within Euroscope should not be used for individual coordination.&lt;br /&gt;
&lt;br /&gt;
When you come online or go offline you should inform neighboring ATC stations.&lt;br /&gt;
&lt;br /&gt;
=== Special Situations (High Traffic, Slots, ...)  ===&lt;br /&gt;
&lt;br /&gt;
==== High traffic situations  ====&lt;br /&gt;
&lt;br /&gt;
During high traffic situations communication with adjacent approach sectors is very important. Especially during single runway operations you might have to ask for increased inbound spacing to be able to fit in departing aircraft. &lt;br /&gt;
&lt;br /&gt;
==== Additional phrases during periods of high traffic  ====&lt;br /&gt;
&lt;br /&gt;
In order to expedite the flow of traffic use the following phrases: &lt;br /&gt;
&lt;br /&gt;
 Austrian 125, wind is xxx/xx runway 29 cleared for takeoff, expedite&lt;br /&gt;
 Austrian 125, wind is xxx/xx runway 34 cleared to land, expedite vacating&lt;br /&gt;
 OE-ABC, wind xxx/xx, runway 29 cleared for takeoff, after departure right turn&lt;br /&gt;
 as soon as practicable&lt;br /&gt;
&lt;br /&gt;
==== Opposite runway operations  ====&lt;br /&gt;
&lt;br /&gt;
This is one of the more difficult situtions for a Tower controller. You have to consider the departure route of each aircraft to estimate the required spacing to arriving traffic. Again close coordination with approach is very important.&lt;br /&gt;
&lt;br /&gt;
== Ressourcen  ==&lt;br /&gt;
&lt;br /&gt;
*[http://vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=77&amp;amp;Itemid=122 VATEUD Training Department] &lt;br /&gt;
*[http://de.wikipedia.org/wiki/ICAO-Alphabet Wikipedia: Buchstabentafel]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]][[Category:Study Guides]][[Category:Training]][[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1752</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1752"/>
		<updated>2012-03-10T21:23:06Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergencies and abnormal procedures arrise from two directions: from the pilots or the ATC- depending where actually they occur. If a pilot gets into trouble then he decleares an emergency. If for example the runway is blocked (damaged aircraft, animals etc.) then the ATC reports abnormal procedures to the surrounding stations. &lt;br /&gt;
&lt;br /&gt;
== Abnormal procedures  ==&lt;br /&gt;
&lt;br /&gt;
===== Pan-pan  =====&lt;br /&gt;
&lt;br /&gt;
Pan-Pan is an urgency announcement of the crew, which is used if an aircraft or its occupence are endangered but not acute at risk, and the crew calls for a preferential treatment. The crew can mostly continue flying under normal or restricted conditions and usually also regularly land.&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;pre&amp;gt;SWR111:&amp;amp;nbsp;  Swissair one-eleven heavy is declaring pan-pan-pan. We have smoke in the cockpit. Request immediate return to a convenient place, I guess Boston.&lt;br /&gt;
CZQM_CTR: Swissair one-eleven heavy, pan-pan received, turn left direct Boston VOR, climb and maintain flight level 310.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Pan-pan is only a message that the crew has to fly under abnormal circumstances and eventually needs a higher priority as non-pan flights.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Radio communication&amp;amp;nbsp;Failure  =====&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Go Around and missed approach  =====&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
#Missed Approach laut Chart &lt;br /&gt;
#Individuelles Handling z.B bestimmte Kursanweisung und Höhe &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Rejected Take-off  =====&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Ausfall von Anflughilfen  =====&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Prioritylanding  =====&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[http://wiki.vacc-austria.org/index.php?title=Emergency_Handling#3..29_Radio_Communication_Failure_-_Funkausfall] &lt;br /&gt;
&lt;br /&gt;
== Emergencies  ==&lt;br /&gt;
&lt;br /&gt;
Wenn ein Pilot einen Zustand bemerkt, die ihm das Weiterfliegen verunmöglichen und das Flugzeug oder Insassen in Gefahr bringen, dann kommt das drastischere Mittel: Der Notruf. Er hat folgende Phasen: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== 1) Ausrufen des Notfalls durch den Piloten:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Der Pilot meldet sich mit dreimal &amp;quot;mayday&amp;quot;, seinem&amp;amp;nbsp;Callsign, seiner Notlage, was er jetzt tut, und was er jetzt braucht. &lt;br /&gt;
&lt;br /&gt;
Der ATC bestätigt den Ruf (readback), fordert ihn auf, den&amp;amp;nbsp;Transponder auf 7700 zu stellen&amp;amp;nbsp;(das erscheint gleich auf allen ATC-Radarschirmen) und gibt ihm eine schnelle Antwort. &lt;br /&gt;
&lt;br /&gt;
==== 2) &amp;quot;Einrichten&amp;quot; im Notfall:  ====&lt;br /&gt;
&lt;br /&gt;
Der Pilot hat nun einige Sekunden zu tun (seinen bedepschten Vogel auf 20° zu drehen und zu stabilisieren), und der ATC auch:&amp;amp;nbsp;Er muss die anderen Piloten auf der Frequenz informieren, und seine angrenzenden&amp;amp;nbsp;Sektoren, und den Flughafen, zu dem es runter geht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Mit dieser Meldung wissen die Piloten:&amp;amp;nbsp;Sie fliegen ihre Verfahren ungerührt weiter:&amp;amp;nbsp;ihre&amp;amp;nbsp;Routen, ihre SID und STAR, ihre Transitions. Sie melden sich bei ATC nur, wenn es ihre Sicherheit erfordert. Wenn sie Anweisungen vom&amp;amp;nbsp;ATC bekommen, dann lesen sie diese nicht zurück. &lt;br /&gt;
&lt;br /&gt;
Dann wird ATC sich über intercom, Text oder Teamspeak mit den anderen ATC in Verbindung setzen und sie über den&amp;amp;nbsp;Notfall informieren, und was für sie daraus folgt: &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
In der Regel sorgt der Controller als erstes dafür, dass er keinen zusätzlichen&amp;amp;nbsp;Traffic mehr übergeben bekommt, und dass sein&amp;amp;nbsp;Flieger heil weiter kommt. &lt;br /&gt;
&lt;br /&gt;
Ab diesem Punkt gibt es keine festgesetzte Phraseologie mehr. Der ATC spricht so mit dem Piloten, dass er am besten serviciert wird. &lt;br /&gt;
&lt;br /&gt;
Mit dieser Information sich der ATC z.B. wieder an den Piloten wenden und die nächsten Schritte klären:&amp;amp;nbsp;Die konkrete Betroffenheit, und wo er landen kann. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, maintain present heading.&lt;br /&gt;
          When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Die ersten Informationen sind auch für VATSIM-Controller wichtig:&amp;amp;nbsp;Was konkret ist kaputt, und was tut der Pilot gerade? Die letzte Info ist auf VATSIM untergeordnet - sie dient in der Realität dazu, den Umfang der Rettungsmaßnahmen abzuschätzen. &lt;br /&gt;
&lt;br /&gt;
==== 3) Alle weiteren Maßnahmen richten sich an folgenden Gesichtspunkten:  ====&lt;br /&gt;
&lt;br /&gt;
*'''Der Pilot sagt, was er braucht, der ATC liefert's. '''Nicht zu&amp;amp;nbsp;Unrecht steht in den Flugplänen&amp;amp;nbsp;&amp;quot;PIC&amp;quot; - pilot in command. Der Pilot kommandiert seine Maschine auch dann, wenn sie ihm auseinanderfällt. ATC ist der Partner, der ihn dabei unterstützt. ATC schafft niemals dem Piloten an, was er tun soll. &lt;br /&gt;
*'''Kommunikation mit dem Piloten:&amp;amp;nbsp;So wenig wie möglich, so viel wie nötig, so präzise wie möglich'''. Bei Notfällen geht's zu im Cockpit. Warntöne piepsen, Warnmeldungen verlauten, Checklisten werden durchgegangen, Lage wird besprochen. Je mehr Zeit die PilotInnen für sich haben, umso besser. Wenn ein/e PilotIn nicht antwortet:&amp;amp;nbsp;nur die Ruhe. Er/sie befolgt (hoffentlich) die Regel:&amp;amp;nbsp;1-avigate, 2-navigate, 3-communicate, und ist noch nicht bei Stufe 3 angekommen. &lt;br /&gt;
*'''&amp;quot;Ausräumen&amp;quot; des restlichen Flugraums:'''&amp;amp;nbsp;Niemand muss abdrehen oder in eine Holding, der nicht im&amp;amp;nbsp;Weg ist. Anderer traffic kann also weitergehen, sofern er die Notfall-Operation nicht stört. Wenn er stört, dann ist möglich: ILS-Freigabe und weg von der Frequenz, direct holding, oder frühzeitige Übergabe (z.B. an CTR) nach&amp;amp;nbsp;Absprache. &lt;br /&gt;
*'''Der Pilot hat die Wahl der Frequenz:''' ob er an anderen ATC übergeben wird (z.B.&amp;amp;nbsp;TWR), oder auf der Frequenz bleibt und bis auf den&amp;amp;nbsp;Boden gebracht wird.TWR kann sich für die Landefreigabe zB auf die Frequenz von APP dazuhängen, damit der Pilot nicht Frequenz wechseln muss.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''&amp;quot;Mayday&amp;quot; ist ein Notfall, der absolute Priorität hat. Nur der Beginn des Verfahrens ist normiert:&amp;amp;nbsp;Ausrufen durch den Piloten, Bestätigung durch&amp;amp;nbsp;ATC, Information der anderen Piloten und anderen ATC. Dann kommunizieren Pilot und ATC, wie es am günstigsten ist. Aufgabe des ATC ist, den Luftraum und die Funkfrequenz möglichst frei zu halten.''&amp;lt;br&amp;gt; &amp;lt;/blockquote&amp;gt; &lt;br /&gt;
==== 4)&amp;amp;nbsp;Notfallprozedur beenden  ====&lt;br /&gt;
&lt;br /&gt;
Irgendwann ist die Notfallprozedur auch beendet und der Flieger glücklich auf der Runway oder unglücklich im Wald. Dann müssen alle anderen wissen, dass die Notfallprozedur beendet ist und alles normal weitergeht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Hinzu kommt, dass die anderen ATC davon wissen müssen (über Intercom, Text oder Teamspeak). CTR hat vielleicht ein Dutzend Flieger im Holding, die abgebaut werden müssen, und GND ein Dutzend Flieger die raus müssen.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
== Liste möglicher Notfallarten und ihr Handling:&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
=== 1.) Go Around - Durchstarteverfahren  ===&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
*Missed Approach laut Chart&amp;lt;br&amp;gt; &lt;br /&gt;
*Individuelles Handling z.B bestimmte Kursanweisung und Höhe&lt;br /&gt;
&lt;br /&gt;
=== 2.) Rejected Takoff - Startabbruch  ===&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &lt;br /&gt;
&lt;br /&gt;
=== 3.) Radio Communication Failure - Funkausfall  ===&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist. &lt;br /&gt;
&lt;br /&gt;
=== 4.) Loss of ILS, NDB, VOR - Ausfall von Anflughilfen  ===&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &lt;br /&gt;
&lt;br /&gt;
=== 5.) Loss of Cabinpressure - Druckabfall  ===&lt;br /&gt;
&lt;br /&gt;
Dies ist ein Fall, der unangenehm werden könnte für den ATCO bei Hightraffic. Der Pilot wird einen sogenannten &amp;quot;Emergencydescent&amp;quot; einleiten (FL100 or below). Als ATCO ihn so schnell wie nur möglich auf dem eigenen Flughafen landen lassen oder ihn auf einen Ausweichflughafen landen lassen. Wichtig dabei ist, dass der ATCO dem Emergencyflieger nicht zutextet und niederquaselt, sondern der Pilot wird sagen, was er tun wird und ATC wird das bestmögliche tun um ihn das zu gewährleisten. Es kann auch vorkommen, dass der Pilot sagt &amp;quot;ATC standby&amp;quot;, d.h. der ATCO soll diesen Flieger bis auf weiteres nicht ansprechen, außer die Situation wird noch gefährlicher durch z.B. crossing Traffic below. Koordination ist in diesem Fall das A &amp;amp;amp; O! &lt;br /&gt;
&lt;br /&gt;
=== 6.) Loss of Hydraulicpressure - Verlust der Hydraulik  ===&lt;br /&gt;
&lt;br /&gt;
Wenn diese Art von Verlust kommt, dann ist meistens die Aircraftperformance (stark) beeinträchtigt. Wichtig hierbei ist zu Erfahren, inwieweit der Pilot die Kontrolle über seinen Flieger noch hat, d.h. Descentrate/Turnrate erfragen oder ob es andere Probleme gibt. Auch kann es dazukommen, dass der Pilot nur mehr Links oder Rechtskurvene fliegen kann. Auch hier sollte man im Hinterkopf haben, dass sich so eine Situation zu einem noch größeren Notfall entwickeln kann. Den betroffenen Flieger so schnell wie nur möglich auf den Boden bringen - Seperation zu den umliegenden Fliegern erhöhen. &lt;br /&gt;
&lt;br /&gt;
=== 7.) Prioritylanding - Dringlichkeitslandung  ===&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
=== 8.) Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Diese Art von Notfall setzt großes Wissen von Notfällen vorraus, da dies eine sehr anspruchsvolle Prozedur ist. Die beste Art diese Situation zu handeln ist, die Übersicht nicht zu verlieren und den Piloten mit wertvollen Informationen zu &amp;quot;versorgen&amp;quot;, d.h. DME Angabe zum Airport, Speed, Altitude, Heading, zu hoch/tief, Trafficinformation,... Alles in allem ist dies ein &amp;quot;Talk-Down-Approach&amp;quot; indem der ATCO wirklich stark gefordert wird in Sachen Konzentration &amp;amp;amp; Koordination. Diese Informationen sollten nicht nur einmal gegeben werden, sonder wirklich beinahe im Minutentakt. Wichig dabei ist wieder, dass der Flieger so schnell als wie nur möglich am Zielflughafen landen sollte, wenn möglich sogar auf einer eigenen Piste, sodass er den anderen anfliegenden Verkehr nicht behindert. Seperation sollte wieder stark erhöht werden zu umliegenden Fluzeugen, falls nötig sogar Warteverfahren aufbauen. &lt;br /&gt;
&lt;br /&gt;
=== 9.) Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Triebwerksversagen beim&amp;amp;nbsp;Start gehört zu den gefährlichsten Zwischenfällen, die es gibt. Die Höhe über Grund ist niedrig, das Flugzeug läuft auch&amp;amp;nbsp;Hochtouren, die Fluggeschwindigkeit ist niedrig (und damit auch die Stabilität). Knappe Koordination ist hier das A und O. Meist passiert der Vogelschlag noch in Bodennähe nach der v1:&amp;amp;nbsp;Der Flieger kann nicht mehr stoppen und muss in die Luft. Der Mayday-call erreicht also meistens noch den&amp;amp;nbsp;TWR controller. Noch dazu variiert die Schwere der Situation nach dem Grad der Schäden, und das ist nicht immer gleich ersichtlich. Professionalität bei&amp;amp;nbsp;Pilot und TWR&amp;amp;nbsp;controller sind sehr wichtig, damit eine heile Landung gelingt.[http://www.youtube.com/watch?v=9KhZwsYtNDE Folgende Aufnahme ]ist ein&amp;amp;nbsp;Schulbeispiel, wie es gut funktioniert:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;So präzise wie möglich:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Antwort ATC:&amp;amp;nbsp;So präzise wie möglich (merke:&amp;amp;nbsp;Tomson hat keinen request geäussert, also braucht er auch gerade nichts):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warnt andere Stationen, und wartet. Der Pilot ist &amp;quot;in command&amp;quot;, er wird sich schon melden. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Der Pilot hat sich gemeldet. Jetzt macht ATC Angebote. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Jetzt sagt der Pilot, was er vorhat: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial &lt;br /&gt;
towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower liest nur zurück und fertig. Wenn der Pilot nichts will, lässt du ihn in Ruhe. Etwas später macht Manchester noch das Angebot, in Liverpool zu landen - das wird abgelehnt. Noch etwas später meldet Manchester Tower, dass die Landebahn 06R wegen Verschmutzung gesperrt ist - die havarierte Maschine hat Teile verloren (das muss er tun - braucht es doch die Maschine für den&amp;amp;nbsp;Landeanflug). Die Maschine landet kurze Zeit später geordnet und sicher. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*dieser Abschnitt wartet noch auf Vervollständigung&lt;br /&gt;
&lt;br /&gt;
=== 10.) Engine Failure at approach - Triebwerksversagen beim Landeanflug&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
dieser Abschnitt wartet noch auf Vervollständigung &lt;br /&gt;
&lt;br /&gt;
=== 11.) Runway closure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Diese Prozedur wird vom Fluglotsen im TWR ausgelöst. Es gibt zwei Unterschiede: &lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''Wenn die Landebahn nicht mehr benützbar ist (Havarierter Flieger, Flugzeugteile, Tiere, ...), dann ist eine Sperre der Landebahn sofort wirksam:&lt;br /&gt;
&lt;br /&gt;
#Anfliegende Flieger bekommen go-around &lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi clearances zu dieser rwy zu geben &lt;br /&gt;
#Neue Landebahn wird geöffnet (oder Flughafen wird geschlossen) &lt;br /&gt;
#ATIS wird angepasst.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Step-by-step &amp;lt;/span&amp;gt;'''closure:''' Wenn der Grund des Schließens abzusehen ist (Wind dreht langsam, noise abatement rules, ...), dann geht die Schließung der Landebahn mit mehr Ordnung vor sich:&lt;br /&gt;
&lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi Clearances zu dieser rwy zu geben &lt;br /&gt;
#verbleibende anfliegende Flugzeuge bekommen Landefreigabe &lt;br /&gt;
#neue Landebahn wird geöffnet &lt;br /&gt;
#ATIS wird angepasst &lt;br /&gt;
#APP und GND werden informiert.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1751</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1751"/>
		<updated>2012-03-10T21:12:44Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergencies and abnormal procedures arrise from two directions: from the pilots or the ATC- depending where actually they occur. If a pilot gets into trouble then he decleares an emergency. If for example the runway is blocked (damaged aircraft, animals etc.) then the ATC reports abnormal procedures to the surrounding stations. &lt;br /&gt;
&lt;br /&gt;
== Abnormal procedures ==&lt;br /&gt;
&lt;br /&gt;
===== Pan-pan  =====&lt;br /&gt;
&lt;br /&gt;
Pan-Pan is an urgency announcement of the crew, witch is used if an aircraft or its occupence are endangered but not acute at risk and the crew calls for a prefferencual treatment. The crew can mostly continue flying under normal conditions or ristricted and usualy also regularly land.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;SWR111:&amp;amp;nbsp;  Swissair one-eleven heavy is declaring pan-pan-pan. We have smoke in the cockpit. Request immediate return to a convenient place, I guess Boston.&lt;br /&gt;
CZQM_CTR: Swissair one-eleven heavy, pan-pan received, turn left direct Boston VOR, climb and maintain flight level 310.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
''PAN ist nur eine Meldung:&amp;amp;nbsp;Der Flieger fliegt &amp;quot;normal&amp;quot; weiter.&amp;amp;nbsp;ATC berücksichtigt nur, dass er zu bestimmten Manövern evtl. nicht in der Lage ist.'' &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Radio communication&amp;amp;nbsp;Failure  =====&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Go Around and missed approach  =====&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
#Missed Approach laut Chart &lt;br /&gt;
#Individuelles Handling z.B bestimmte Kursanweisung und Höhe &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Rejected Take-off  =====&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Ausfall von Anflughilfen  =====&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Prioritylanding  =====&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[http://wiki.vacc-austria.org/index.php?title=Emergency_Handling#3..29_Radio_Communication_Failure_-_Funkausfall] &lt;br /&gt;
&lt;br /&gt;
== Emergencies  ==&lt;br /&gt;
&lt;br /&gt;
Wenn ein Pilot einen Zustand bemerkt, die ihm das Weiterfliegen verunmöglichen und das Flugzeug oder Insassen in Gefahr bringen, dann kommt das drastischere Mittel: Der Notruf. Er hat folgende Phasen: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== 1) Ausrufen des Notfalls durch den Piloten:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Der Pilot meldet sich mit dreimal &amp;quot;mayday&amp;quot;, seinem&amp;amp;nbsp;Callsign, seiner Notlage, was er jetzt tut, und was er jetzt braucht. &lt;br /&gt;
&lt;br /&gt;
Der ATC bestätigt den Ruf (readback), fordert ihn auf, den&amp;amp;nbsp;Transponder auf 7700 zu stellen&amp;amp;nbsp;(das erscheint gleich auf allen ATC-Radarschirmen) und gibt ihm eine schnelle Antwort. &lt;br /&gt;
&lt;br /&gt;
==== 2) &amp;quot;Einrichten&amp;quot; im Notfall:  ====&lt;br /&gt;
&lt;br /&gt;
Der Pilot hat nun einige Sekunden zu tun (seinen bedepschten Vogel auf 20° zu drehen und zu stabilisieren), und der ATC auch:&amp;amp;nbsp;Er muss die anderen Piloten auf der Frequenz informieren, und seine angrenzenden&amp;amp;nbsp;Sektoren, und den Flughafen, zu dem es runter geht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Mit dieser Meldung wissen die Piloten:&amp;amp;nbsp;Sie fliegen ihre Verfahren ungerührt weiter:&amp;amp;nbsp;ihre&amp;amp;nbsp;Routen, ihre SID und STAR, ihre Transitions. Sie melden sich bei ATC nur, wenn es ihre Sicherheit erfordert. Wenn sie Anweisungen vom&amp;amp;nbsp;ATC bekommen, dann lesen sie diese nicht zurück. &lt;br /&gt;
&lt;br /&gt;
Dann wird ATC sich über intercom, Text oder Teamspeak mit den anderen ATC in Verbindung setzen und sie über den&amp;amp;nbsp;Notfall informieren, und was für sie daraus folgt: &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
In der Regel sorgt der Controller als erstes dafür, dass er keinen zusätzlichen&amp;amp;nbsp;Traffic mehr übergeben bekommt, und dass sein&amp;amp;nbsp;Flieger heil weiter kommt. &lt;br /&gt;
&lt;br /&gt;
Ab diesem Punkt gibt es keine festgesetzte Phraseologie mehr. Der ATC spricht so mit dem Piloten, dass er am besten serviciert wird. &lt;br /&gt;
&lt;br /&gt;
Mit dieser Information sich der ATC z.B. wieder an den Piloten wenden und die nächsten Schritte klären:&amp;amp;nbsp;Die konkrete Betroffenheit, und wo er landen kann. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, maintain present heading.&lt;br /&gt;
          When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Die ersten Informationen sind auch für VATSIM-Controller wichtig:&amp;amp;nbsp;Was konkret ist kaputt, und was tut der Pilot gerade? Die letzte Info ist auf VATSIM untergeordnet - sie dient in der Realität dazu, den Umfang der Rettungsmaßnahmen abzuschätzen. &lt;br /&gt;
&lt;br /&gt;
==== 3) Alle weiteren Maßnahmen richten sich an folgenden Gesichtspunkten:  ====&lt;br /&gt;
&lt;br /&gt;
*'''Der Pilot sagt, was er braucht, der ATC liefert's. '''Nicht zu&amp;amp;nbsp;Unrecht steht in den Flugplänen&amp;amp;nbsp;&amp;quot;PIC&amp;quot; - pilot in command. Der Pilot kommandiert seine Maschine auch dann, wenn sie ihm auseinanderfällt. ATC ist der Partner, der ihn dabei unterstützt. ATC schafft niemals dem Piloten an, was er tun soll. &lt;br /&gt;
*'''Kommunikation mit dem Piloten:&amp;amp;nbsp;So wenig wie möglich, so viel wie nötig, so präzise wie möglich'''. Bei Notfällen geht's zu im Cockpit. Warntöne piepsen, Warnmeldungen verlauten, Checklisten werden durchgegangen, Lage wird besprochen. Je mehr Zeit die PilotInnen für sich haben, umso besser. Wenn ein/e PilotIn nicht antwortet:&amp;amp;nbsp;nur die Ruhe. Er/sie befolgt (hoffentlich) die Regel:&amp;amp;nbsp;1-avigate, 2-navigate, 3-communicate, und ist noch nicht bei Stufe 3 angekommen. &lt;br /&gt;
*'''&amp;quot;Ausräumen&amp;quot; des restlichen Flugraums:'''&amp;amp;nbsp;Niemand muss abdrehen oder in eine Holding, der nicht im&amp;amp;nbsp;Weg ist. Anderer traffic kann also weitergehen, sofern er die Notfall-Operation nicht stört. Wenn er stört, dann ist möglich: ILS-Freigabe und weg von der Frequenz, direct holding, oder frühzeitige Übergabe (z.B. an CTR) nach&amp;amp;nbsp;Absprache. &lt;br /&gt;
*'''Der Pilot hat die Wahl der Frequenz:''' ob er an anderen ATC übergeben wird (z.B.&amp;amp;nbsp;TWR), oder auf der Frequenz bleibt und bis auf den&amp;amp;nbsp;Boden gebracht wird.TWR kann sich für die Landefreigabe zB auf die Frequenz von APP dazuhängen, damit der Pilot nicht Frequenz wechseln muss.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''&amp;quot;Mayday&amp;quot; ist ein Notfall, der absolute Priorität hat. Nur der Beginn des Verfahrens ist normiert:&amp;amp;nbsp;Ausrufen durch den Piloten, Bestätigung durch&amp;amp;nbsp;ATC, Information der anderen Piloten und anderen ATC. Dann kommunizieren Pilot und ATC, wie es am günstigsten ist. Aufgabe des ATC ist, den Luftraum und die Funkfrequenz möglichst frei zu halten.''&amp;lt;br&amp;gt; &amp;lt;/blockquote&amp;gt; &lt;br /&gt;
==== 4)&amp;amp;nbsp;Notfallprozedur beenden  ====&lt;br /&gt;
&lt;br /&gt;
Irgendwann ist die Notfallprozedur auch beendet und der Flieger glücklich auf der Runway oder unglücklich im Wald. Dann müssen alle anderen wissen, dass die Notfallprozedur beendet ist und alles normal weitergeht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Hinzu kommt, dass die anderen ATC davon wissen müssen (über Intercom, Text oder Teamspeak). CTR hat vielleicht ein Dutzend Flieger im Holding, die abgebaut werden müssen, und GND ein Dutzend Flieger die raus müssen.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
== Liste möglicher Notfallarten und ihr Handling:&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
=== 1.) Go Around - Durchstarteverfahren  ===&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
*Missed Approach laut Chart&amp;lt;br&amp;gt; &lt;br /&gt;
*Individuelles Handling z.B bestimmte Kursanweisung und Höhe&lt;br /&gt;
&lt;br /&gt;
=== 2.) Rejected Takoff - Startabbruch  ===&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &lt;br /&gt;
&lt;br /&gt;
=== 3.) Radio Communication Failure - Funkausfall  ===&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist. &lt;br /&gt;
&lt;br /&gt;
=== 4.) Loss of ILS, NDB, VOR - Ausfall von Anflughilfen  ===&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &lt;br /&gt;
&lt;br /&gt;
=== 5.) Loss of Cabinpressure - Druckabfall  ===&lt;br /&gt;
&lt;br /&gt;
Dies ist ein Fall, der unangenehm werden könnte für den ATCO bei Hightraffic. Der Pilot wird einen sogenannten &amp;quot;Emergencydescent&amp;quot; einleiten (FL100 or below). Als ATCO ihn so schnell wie nur möglich auf dem eigenen Flughafen landen lassen oder ihn auf einen Ausweichflughafen landen lassen. Wichtig dabei ist, dass der ATCO dem Emergencyflieger nicht zutextet und niederquaselt, sondern der Pilot wird sagen, was er tun wird und ATC wird das bestmögliche tun um ihn das zu gewährleisten. Es kann auch vorkommen, dass der Pilot sagt &amp;quot;ATC standby&amp;quot;, d.h. der ATCO soll diesen Flieger bis auf weiteres nicht ansprechen, außer die Situation wird noch gefährlicher durch z.B. crossing Traffic below. Koordination ist in diesem Fall das A &amp;amp;amp; O! &lt;br /&gt;
&lt;br /&gt;
=== 6.) Loss of Hydraulicpressure - Verlust der Hydraulik  ===&lt;br /&gt;
&lt;br /&gt;
Wenn diese Art von Verlust kommt, dann ist meistens die Aircraftperformance (stark) beeinträchtigt. Wichtig hierbei ist zu Erfahren, inwieweit der Pilot die Kontrolle über seinen Flieger noch hat, d.h. Descentrate/Turnrate erfragen oder ob es andere Probleme gibt. Auch kann es dazukommen, dass der Pilot nur mehr Links oder Rechtskurvene fliegen kann. Auch hier sollte man im Hinterkopf haben, dass sich so eine Situation zu einem noch größeren Notfall entwickeln kann. Den betroffenen Flieger so schnell wie nur möglich auf den Boden bringen - Seperation zu den umliegenden Fliegern erhöhen. &lt;br /&gt;
&lt;br /&gt;
=== 7.) Prioritylanding - Dringlichkeitslandung  ===&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
=== 8.) Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Diese Art von Notfall setzt großes Wissen von Notfällen vorraus, da dies eine sehr anspruchsvolle Prozedur ist. Die beste Art diese Situation zu handeln ist, die Übersicht nicht zu verlieren und den Piloten mit wertvollen Informationen zu &amp;quot;versorgen&amp;quot;, d.h. DME Angabe zum Airport, Speed, Altitude, Heading, zu hoch/tief, Trafficinformation,... Alles in allem ist dies ein &amp;quot;Talk-Down-Approach&amp;quot; indem der ATCO wirklich stark gefordert wird in Sachen Konzentration &amp;amp;amp; Koordination. Diese Informationen sollten nicht nur einmal gegeben werden, sonder wirklich beinahe im Minutentakt. Wichig dabei ist wieder, dass der Flieger so schnell als wie nur möglich am Zielflughafen landen sollte, wenn möglich sogar auf einer eigenen Piste, sodass er den anderen anfliegenden Verkehr nicht behindert. Seperation sollte wieder stark erhöht werden zu umliegenden Fluzeugen, falls nötig sogar Warteverfahren aufbauen. &lt;br /&gt;
&lt;br /&gt;
=== 9.) Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Triebwerksversagen beim&amp;amp;nbsp;Start gehört zu den gefährlichsten Zwischenfällen, die es gibt. Die Höhe über Grund ist niedrig, das Flugzeug läuft auch&amp;amp;nbsp;Hochtouren, die Fluggeschwindigkeit ist niedrig (und damit auch die Stabilität). Knappe Koordination ist hier das A und O. Meist passiert der Vogelschlag noch in Bodennähe nach der v1:&amp;amp;nbsp;Der Flieger kann nicht mehr stoppen und muss in die Luft. Der Mayday-call erreicht also meistens noch den&amp;amp;nbsp;TWR controller. Noch dazu variiert die Schwere der Situation nach dem Grad der Schäden, und das ist nicht immer gleich ersichtlich. Professionalität bei&amp;amp;nbsp;Pilot und TWR&amp;amp;nbsp;controller sind sehr wichtig, damit eine heile Landung gelingt.[http://www.youtube.com/watch?v=9KhZwsYtNDE Folgende Aufnahme ]ist ein&amp;amp;nbsp;Schulbeispiel, wie es gut funktioniert:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;So präzise wie möglich:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Antwort ATC:&amp;amp;nbsp;So präzise wie möglich (merke:&amp;amp;nbsp;Tomson hat keinen request geäussert, also braucht er auch gerade nichts):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warnt andere Stationen, und wartet. Der Pilot ist &amp;quot;in command&amp;quot;, er wird sich schon melden. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Der Pilot hat sich gemeldet. Jetzt macht ATC Angebote. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Jetzt sagt der Pilot, was er vorhat: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial &lt;br /&gt;
towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower liest nur zurück und fertig. Wenn der Pilot nichts will, lässt du ihn in Ruhe. Etwas später macht Manchester noch das Angebot, in Liverpool zu landen - das wird abgelehnt. Noch etwas später meldet Manchester Tower, dass die Landebahn 06R wegen Verschmutzung gesperrt ist - die havarierte Maschine hat Teile verloren (das muss er tun - braucht es doch die Maschine für den&amp;amp;nbsp;Landeanflug). Die Maschine landet kurze Zeit später geordnet und sicher. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*dieser Abschnitt wartet noch auf Vervollständigung&lt;br /&gt;
&lt;br /&gt;
=== 10.) Engine Failure at approach - Triebwerksversagen beim Landeanflug&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
dieser Abschnitt wartet noch auf Vervollständigung &lt;br /&gt;
&lt;br /&gt;
=== 11.) Runway closure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Diese Prozedur wird vom Fluglotsen im TWR ausgelöst. Es gibt zwei Unterschiede: &lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''Wenn die Landebahn nicht mehr benützbar ist (Havarierter Flieger, Flugzeugteile, Tiere, ...), dann ist eine Sperre der Landebahn sofort wirksam:&lt;br /&gt;
&lt;br /&gt;
#Anfliegende Flieger bekommen go-around &lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi clearances zu dieser rwy zu geben &lt;br /&gt;
#Neue Landebahn wird geöffnet (oder Flughafen wird geschlossen) &lt;br /&gt;
#ATIS wird angepasst.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Step-by-step &amp;lt;/span&amp;gt;'''closure:''' Wenn der Grund des Schließens abzusehen ist (Wind dreht langsam, noise abatement rules, ...), dann geht die Schließung der Landebahn mit mehr Ordnung vor sich:&lt;br /&gt;
&lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi Clearances zu dieser rwy zu geben &lt;br /&gt;
#verbleibende anfliegende Flugzeuge bekommen Landefreigabe &lt;br /&gt;
#neue Landebahn wird geöffnet &lt;br /&gt;
#ATIS wird angepasst &lt;br /&gt;
#APP und GND werden informiert.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1750</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1750"/>
		<updated>2012-03-10T20:55:26Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergencies and abnormal procedures arrise from two directions: from the pilots or the ATC- depending where actually they occur. If a pilot gets into trouble then he decleares an emergency. If for example the runway is blocked (damaged aircraft, animals etc.) then the ATC reports abnormal procedures to the surrounding stations. &lt;br /&gt;
&lt;br /&gt;
== Abnormal procedures&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
===== Pan-pan  =====&lt;br /&gt;
&lt;br /&gt;
Pan-Pan ist eine Dringlichkeitsmeldung im Sprechfunkverkehr Flugzeugen, die abgesetzt wird, wenn das Flugzeug oder seine Insassen konkret, aber nicht akut gefährdet sind, und mit der die Besatzung eine bevorzugte Behandlung einfordert. Der Flieger kann meist normal oder eingeschränkt weiterfliegen und üblicherweise auch regulär landen.&lt;br /&gt;
&lt;br /&gt;
Für den Piloten heisst das:&amp;amp;nbsp;Anmelden der Panne, und was für ihn daraus folgt. &lt;br /&gt;
&amp;lt;pre&amp;gt;SWR111:&amp;amp;nbsp;  Swissair one-eleven heavy is declaring pan-pan-pan. We have smoke in the cockpit. Request immediate return to a convenient place, I guess Boston.&lt;br /&gt;
CZQM_CTR: Swissair one-eleven heavy, pan-pan received, turn left direct Boston VOR, climb and maintain flight level 310.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*''PAN ist nur eine Meldung:&amp;amp;nbsp;Der Flieger fliegt &amp;quot;normal&amp;quot; weiter.&amp;amp;nbsp;ATC berücksichtigt nur, dass er zu bestimmten Manövern evtl. nicht in der Lage ist.''&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Radio communication&amp;amp;nbsp;Failure  =====&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Go Around and missed approach  =====&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
#Missed Approach laut Chart &lt;br /&gt;
#Individuelles Handling z.B bestimmte Kursanweisung und Höhe &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Rejected Take-off  =====&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Ausfall von Anflughilfen  =====&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Prioritylanding  =====&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[http://wiki.vacc-austria.org/index.php?title=Emergency_Handling#3..29_Radio_Communication_Failure_-_Funkausfall] &lt;br /&gt;
&lt;br /&gt;
== Emergencies  ==&lt;br /&gt;
&lt;br /&gt;
Wenn ein Pilot einen Zustand bemerkt, die ihm das Weiterfliegen verunmöglichen und das Flugzeug oder Insassen in Gefahr bringen, dann kommt das drastischere Mittel: Der Notruf. Er hat folgende Phasen: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== 1) Ausrufen des Notfalls durch den Piloten:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Der Pilot meldet sich mit dreimal &amp;quot;mayday&amp;quot;, seinem&amp;amp;nbsp;Callsign, seiner Notlage, was er jetzt tut, und was er jetzt braucht. &lt;br /&gt;
&lt;br /&gt;
Der ATC bestätigt den Ruf (readback), fordert ihn auf, den&amp;amp;nbsp;Transponder auf 7700 zu stellen&amp;amp;nbsp;(das erscheint gleich auf allen ATC-Radarschirmen) und gibt ihm eine schnelle Antwort. &lt;br /&gt;
&lt;br /&gt;
==== 2) &amp;quot;Einrichten&amp;quot; im Notfall:  ====&lt;br /&gt;
&lt;br /&gt;
Der Pilot hat nun einige Sekunden zu tun (seinen bedepschten Vogel auf 20° zu drehen und zu stabilisieren), und der ATC auch:&amp;amp;nbsp;Er muss die anderen Piloten auf der Frequenz informieren, und seine angrenzenden&amp;amp;nbsp;Sektoren, und den Flughafen, zu dem es runter geht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Mit dieser Meldung wissen die Piloten:&amp;amp;nbsp;Sie fliegen ihre Verfahren ungerührt weiter:&amp;amp;nbsp;ihre&amp;amp;nbsp;Routen, ihre SID und STAR, ihre Transitions. Sie melden sich bei ATC nur, wenn es ihre Sicherheit erfordert. Wenn sie Anweisungen vom&amp;amp;nbsp;ATC bekommen, dann lesen sie diese nicht zurück. &lt;br /&gt;
&lt;br /&gt;
Dann wird ATC sich über intercom, Text oder Teamspeak mit den anderen ATC in Verbindung setzen und sie über den&amp;amp;nbsp;Notfall informieren, und was für sie daraus folgt: &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
In der Regel sorgt der Controller als erstes dafür, dass er keinen zusätzlichen&amp;amp;nbsp;Traffic mehr übergeben bekommt, und dass sein&amp;amp;nbsp;Flieger heil weiter kommt. &lt;br /&gt;
&lt;br /&gt;
Ab diesem Punkt gibt es keine festgesetzte Phraseologie mehr. Der ATC spricht so mit dem Piloten, dass er am besten serviciert wird. &lt;br /&gt;
&lt;br /&gt;
Mit dieser Information sich der ATC z.B. wieder an den Piloten wenden und die nächsten Schritte klären:&amp;amp;nbsp;Die konkrete Betroffenheit, und wo er landen kann. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, maintain present heading.&lt;br /&gt;
          When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Die ersten Informationen sind auch für VATSIM-Controller wichtig:&amp;amp;nbsp;Was konkret ist kaputt, und was tut der Pilot gerade? Die letzte Info ist auf VATSIM untergeordnet - sie dient in der Realität dazu, den Umfang der Rettungsmaßnahmen abzuschätzen. &lt;br /&gt;
&lt;br /&gt;
==== 3) Alle weiteren Maßnahmen richten sich an folgenden Gesichtspunkten:  ====&lt;br /&gt;
&lt;br /&gt;
*'''Der Pilot sagt, was er braucht, der ATC liefert's. '''Nicht zu&amp;amp;nbsp;Unrecht steht in den Flugplänen&amp;amp;nbsp;&amp;quot;PIC&amp;quot; - pilot in command. Der Pilot kommandiert seine Maschine auch dann, wenn sie ihm auseinanderfällt. ATC ist der Partner, der ihn dabei unterstützt. ATC schafft niemals dem Piloten an, was er tun soll. &lt;br /&gt;
*'''Kommunikation mit dem Piloten:&amp;amp;nbsp;So wenig wie möglich, so viel wie nötig, so präzise wie möglich'''. Bei Notfällen geht's zu im Cockpit. Warntöne piepsen, Warnmeldungen verlauten, Checklisten werden durchgegangen, Lage wird besprochen. Je mehr Zeit die PilotInnen für sich haben, umso besser. Wenn ein/e PilotIn nicht antwortet:&amp;amp;nbsp;nur die Ruhe. Er/sie befolgt (hoffentlich) die Regel:&amp;amp;nbsp;1-avigate, 2-navigate, 3-communicate, und ist noch nicht bei Stufe 3 angekommen. &lt;br /&gt;
*'''&amp;quot;Ausräumen&amp;quot; des restlichen Flugraums:'''&amp;amp;nbsp;Niemand muss abdrehen oder in eine Holding, der nicht im&amp;amp;nbsp;Weg ist. Anderer traffic kann also weitergehen, sofern er die Notfall-Operation nicht stört. Wenn er stört, dann ist möglich: ILS-Freigabe und weg von der Frequenz, direct holding, oder frühzeitige Übergabe (z.B. an CTR) nach&amp;amp;nbsp;Absprache. &lt;br /&gt;
*'''Der Pilot hat die Wahl der Frequenz:''' ob er an anderen ATC übergeben wird (z.B.&amp;amp;nbsp;TWR), oder auf der Frequenz bleibt und bis auf den&amp;amp;nbsp;Boden gebracht wird.TWR kann sich für die Landefreigabe zB auf die Frequenz von APP dazuhängen, damit der Pilot nicht Frequenz wechseln muss.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''&amp;quot;Mayday&amp;quot; ist ein Notfall, der absolute Priorität hat. Nur der Beginn des Verfahrens ist normiert:&amp;amp;nbsp;Ausrufen durch den Piloten, Bestätigung durch&amp;amp;nbsp;ATC, Information der anderen Piloten und anderen ATC. Dann kommunizieren Pilot und ATC, wie es am günstigsten ist. Aufgabe des ATC ist, den Luftraum und die Funkfrequenz möglichst frei zu halten.''&amp;lt;br&amp;gt; &amp;lt;/blockquote&amp;gt; &lt;br /&gt;
==== 4)&amp;amp;nbsp;Notfallprozedur beenden  ====&lt;br /&gt;
&lt;br /&gt;
Irgendwann ist die Notfallprozedur auch beendet und der Flieger glücklich auf der Runway oder unglücklich im Wald. Dann müssen alle anderen wissen, dass die Notfallprozedur beendet ist und alles normal weitergeht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Hinzu kommt, dass die anderen ATC davon wissen müssen (über Intercom, Text oder Teamspeak). CTR hat vielleicht ein Dutzend Flieger im Holding, die abgebaut werden müssen, und GND ein Dutzend Flieger die raus müssen.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
== Liste möglicher Notfallarten und ihr Handling:&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
=== 1.) Go Around - Durchstarteverfahren  ===&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
*Missed Approach laut Chart&amp;lt;br&amp;gt; &lt;br /&gt;
*Individuelles Handling z.B bestimmte Kursanweisung und Höhe&lt;br /&gt;
&lt;br /&gt;
=== 2.) Rejected Takoff - Startabbruch  ===&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &lt;br /&gt;
&lt;br /&gt;
=== 3.) Radio Communication Failure - Funkausfall  ===&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist. &lt;br /&gt;
&lt;br /&gt;
=== 4.) Loss of ILS, NDB, VOR - Ausfall von Anflughilfen  ===&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &lt;br /&gt;
&lt;br /&gt;
=== 5.) Loss of Cabinpressure - Druckabfall  ===&lt;br /&gt;
&lt;br /&gt;
Dies ist ein Fall, der unangenehm werden könnte für den ATCO bei Hightraffic. Der Pilot wird einen sogenannten &amp;quot;Emergencydescent&amp;quot; einleiten (FL100 or below). Als ATCO ihn so schnell wie nur möglich auf dem eigenen Flughafen landen lassen oder ihn auf einen Ausweichflughafen landen lassen. Wichtig dabei ist, dass der ATCO dem Emergencyflieger nicht zutextet und niederquaselt, sondern der Pilot wird sagen, was er tun wird und ATC wird das bestmögliche tun um ihn das zu gewährleisten. Es kann auch vorkommen, dass der Pilot sagt &amp;quot;ATC standby&amp;quot;, d.h. der ATCO soll diesen Flieger bis auf weiteres nicht ansprechen, außer die Situation wird noch gefährlicher durch z.B. crossing Traffic below. Koordination ist in diesem Fall das A &amp;amp;amp; O! &lt;br /&gt;
&lt;br /&gt;
=== 6.) Loss of Hydraulicpressure - Verlust der Hydraulik  ===&lt;br /&gt;
&lt;br /&gt;
Wenn diese Art von Verlust kommt, dann ist meistens die Aircraftperformance (stark) beeinträchtigt. Wichtig hierbei ist zu Erfahren, inwieweit der Pilot die Kontrolle über seinen Flieger noch hat, d.h. Descentrate/Turnrate erfragen oder ob es andere Probleme gibt. Auch kann es dazukommen, dass der Pilot nur mehr Links oder Rechtskurvene fliegen kann. Auch hier sollte man im Hinterkopf haben, dass sich so eine Situation zu einem noch größeren Notfall entwickeln kann. Den betroffenen Flieger so schnell wie nur möglich auf den Boden bringen - Seperation zu den umliegenden Fliegern erhöhen. &lt;br /&gt;
&lt;br /&gt;
=== 7.) Prioritylanding - Dringlichkeitslandung  ===&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
=== 8.) Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Diese Art von Notfall setzt großes Wissen von Notfällen vorraus, da dies eine sehr anspruchsvolle Prozedur ist. Die beste Art diese Situation zu handeln ist, die Übersicht nicht zu verlieren und den Piloten mit wertvollen Informationen zu &amp;quot;versorgen&amp;quot;, d.h. DME Angabe zum Airport, Speed, Altitude, Heading, zu hoch/tief, Trafficinformation,... Alles in allem ist dies ein &amp;quot;Talk-Down-Approach&amp;quot; indem der ATCO wirklich stark gefordert wird in Sachen Konzentration &amp;amp;amp; Koordination. Diese Informationen sollten nicht nur einmal gegeben werden, sonder wirklich beinahe im Minutentakt. Wichig dabei ist wieder, dass der Flieger so schnell als wie nur möglich am Zielflughafen landen sollte, wenn möglich sogar auf einer eigenen Piste, sodass er den anderen anfliegenden Verkehr nicht behindert. Seperation sollte wieder stark erhöht werden zu umliegenden Fluzeugen, falls nötig sogar Warteverfahren aufbauen. &lt;br /&gt;
&lt;br /&gt;
=== 9.) Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Triebwerksversagen beim&amp;amp;nbsp;Start gehört zu den gefährlichsten Zwischenfällen, die es gibt. Die Höhe über Grund ist niedrig, das Flugzeug läuft auch&amp;amp;nbsp;Hochtouren, die Fluggeschwindigkeit ist niedrig (und damit auch die Stabilität). Knappe Koordination ist hier das A und O. Meist passiert der Vogelschlag noch in Bodennähe nach der v1:&amp;amp;nbsp;Der Flieger kann nicht mehr stoppen und muss in die Luft. Der Mayday-call erreicht also meistens noch den&amp;amp;nbsp;TWR controller. Noch dazu variiert die Schwere der Situation nach dem Grad der Schäden, und das ist nicht immer gleich ersichtlich. Professionalität bei&amp;amp;nbsp;Pilot und TWR&amp;amp;nbsp;controller sind sehr wichtig, damit eine heile Landung gelingt.[http://www.youtube.com/watch?v=9KhZwsYtNDE Folgende Aufnahme ]ist ein&amp;amp;nbsp;Schulbeispiel, wie es gut funktioniert:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;So präzise wie möglich:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Antwort ATC:&amp;amp;nbsp;So präzise wie möglich (merke:&amp;amp;nbsp;Tomson hat keinen request geäussert, also braucht er auch gerade nichts):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warnt andere Stationen, und wartet. Der Pilot ist &amp;quot;in command&amp;quot;, er wird sich schon melden. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Der Pilot hat sich gemeldet. Jetzt macht ATC Angebote. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Jetzt sagt der Pilot, was er vorhat: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial &lt;br /&gt;
towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower liest nur zurück und fertig. Wenn der Pilot nichts will, lässt du ihn in Ruhe. Etwas später macht Manchester noch das Angebot, in Liverpool zu landen - das wird abgelehnt. Noch etwas später meldet Manchester Tower, dass die Landebahn 06R wegen Verschmutzung gesperrt ist - die havarierte Maschine hat Teile verloren (das muss er tun - braucht es doch die Maschine für den&amp;amp;nbsp;Landeanflug). Die Maschine landet kurze Zeit später geordnet und sicher. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*dieser Abschnitt wartet noch auf Vervollständigung&lt;br /&gt;
&lt;br /&gt;
=== 10.) Engine Failure at approach - Triebwerksversagen beim Landeanflug&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
dieser Abschnitt wartet noch auf Vervollständigung &lt;br /&gt;
&lt;br /&gt;
=== 11.) Runway closure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Diese Prozedur wird vom Fluglotsen im TWR ausgelöst. Es gibt zwei Unterschiede: &lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''Wenn die Landebahn nicht mehr benützbar ist (Havarierter Flieger, Flugzeugteile, Tiere, ...), dann ist eine Sperre der Landebahn sofort wirksam:&lt;br /&gt;
&lt;br /&gt;
#Anfliegende Flieger bekommen go-around &lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi clearances zu dieser rwy zu geben &lt;br /&gt;
#Neue Landebahn wird geöffnet (oder Flughafen wird geschlossen) &lt;br /&gt;
#ATIS wird angepasst.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Step-by-step &amp;lt;/span&amp;gt;'''closure:''' Wenn der Grund des Schließens abzusehen ist (Wind dreht langsam, noise abatement rules, ...), dann geht die Schließung der Landebahn mit mehr Ordnung vor sich:&lt;br /&gt;
&lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi Clearances zu dieser rwy zu geben &lt;br /&gt;
#verbleibende anfliegende Flugzeuge bekommen Landefreigabe &lt;br /&gt;
#neue Landebahn wird geöffnet &lt;br /&gt;
#ATIS wird angepasst &lt;br /&gt;
#APP und GND werden informiert.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1749</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1749"/>
		<updated>2012-03-10T20:44:46Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergencies and abnormal procedures arrise from two directions: from the pilots or the ATC- depending where actually they occur. If a pilot gets into trouble then he decleares an emergency. If for example the runway is blocked (damaged aircraft, animals etc.) then the ATC reports abnormal procedures to the surrounding stations. &lt;br /&gt;
&lt;br /&gt;
== Abnormal procedures&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
===== PAN&amp;amp;nbsp;(Panne)  =====&lt;br /&gt;
&lt;br /&gt;
Wenn einem Flugzeug einzelne Systeme ausfallen, die ihn nicht in ernste Gefahr bringen, aber dazu bringen könnten, dass er seinen Flug nicht &amp;quot;normal&amp;quot; fortsetzen kann, dann ist dies eine Pannenmeldung.&amp;amp;nbsp;Dazu zählt der Klassiker &amp;quot;low fuel&amp;quot;, aber auch Ausfälle von nicht-vitalen&amp;amp;nbsp;Systemen wie z.B. FMC, VOR receiver oder speedbrakes. Der Flieger kann normal weiter fliegen und üblicherweise auch regulär landen, aber er kann bestimmte Flugmanöver nicht durchführen (ohne VOR receiver geht z.B. kein ILS-Anflug, ohne FMC ist &amp;quot;direct WW380&amp;quot; nicht möglich. &lt;br /&gt;
&lt;br /&gt;
Für den Piloten heisst das:&amp;amp;nbsp;Anmelden der Panne, und was für ihn daraus folgt. &lt;br /&gt;
&amp;lt;pre&amp;gt;G-WIRO:&amp;amp;nbsp;  Pan-pan-pan, G-WIRO, low fuel, requesting CDA to&amp;amp;nbsp;Vienna.&lt;br /&gt;
LOWW_APP: G-WIRO, pan message received, direct WW380, descent 4000ft at own discretion, QNH 1033.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*''PAN ist nur eine Meldung:&amp;amp;nbsp;Der Flieger fliegt &amp;quot;normal&amp;quot; weiter.&amp;amp;nbsp;ATC berücksichtigt nur, dass er zu bestimmten Manövern evtl. nicht in der Lage ist.''&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Radio communication&amp;amp;nbsp;Failure  =====&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Go Around and missed approach =====&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden:&lt;br /&gt;
&lt;br /&gt;
#Missed Approach laut Chart&lt;br /&gt;
#Individuelles Handling z.B bestimmte Kursanweisung und Höhe &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Rejected Take-off =====&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Ausfall von Anflughilfen =====&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Prioritylanding =====&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[http://wiki.vacc-austria.org/index.php?title=Emergency_Handling#3..29_Radio_Communication_Failure_-_Funkausfall ] &lt;br /&gt;
&lt;br /&gt;
== Emergencies  ==&lt;br /&gt;
&lt;br /&gt;
Wenn ein Pilot einen Zustand bemerkt, die ihm das Weiterfliegen verunmöglichen und das Flugzeug oder Insassen in Gefahr bringen, dann kommt das drastischere Mittel: Der Notruf. Er hat folgende Phasen: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== 1) Ausrufen des Notfalls durch den Piloten:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Der Pilot meldet sich mit dreimal &amp;quot;mayday&amp;quot;, seinem&amp;amp;nbsp;Callsign, seiner Notlage, was er jetzt tut, und was er jetzt braucht. &lt;br /&gt;
&lt;br /&gt;
Der ATC bestätigt den Ruf (readback), fordert ihn auf, den&amp;amp;nbsp;Transponder auf 7700 zu stellen&amp;amp;nbsp;(das erscheint gleich auf allen ATC-Radarschirmen) und gibt ihm eine schnelle Antwort. &lt;br /&gt;
&lt;br /&gt;
==== 2) &amp;quot;Einrichten&amp;quot; im Notfall:  ====&lt;br /&gt;
&lt;br /&gt;
Der Pilot hat nun einige Sekunden zu tun (seinen bedepschten Vogel auf 20° zu drehen und zu stabilisieren), und der ATC auch:&amp;amp;nbsp;Er muss die anderen Piloten auf der Frequenz informieren, und seine angrenzenden&amp;amp;nbsp;Sektoren, und den Flughafen, zu dem es runter geht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Mit dieser Meldung wissen die Piloten:&amp;amp;nbsp;Sie fliegen ihre Verfahren ungerührt weiter:&amp;amp;nbsp;ihre&amp;amp;nbsp;Routen, ihre SID und STAR, ihre Transitions. Sie melden sich bei ATC nur, wenn es ihre Sicherheit erfordert. Wenn sie Anweisungen vom&amp;amp;nbsp;ATC bekommen, dann lesen sie diese nicht zurück. &lt;br /&gt;
&lt;br /&gt;
Dann wird ATC sich über intercom, Text oder Teamspeak mit den anderen ATC in Verbindung setzen und sie über den&amp;amp;nbsp;Notfall informieren, und was für sie daraus folgt: &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
In der Regel sorgt der Controller als erstes dafür, dass er keinen zusätzlichen&amp;amp;nbsp;Traffic mehr übergeben bekommt, und dass sein&amp;amp;nbsp;Flieger heil weiter kommt. &lt;br /&gt;
&lt;br /&gt;
Ab diesem Punkt gibt es keine festgesetzte Phraseologie mehr. Der ATC spricht so mit dem Piloten, dass er am besten serviciert wird. &lt;br /&gt;
&lt;br /&gt;
Mit dieser Information sich der ATC z.B. wieder an den Piloten wenden und die nächsten Schritte klären:&amp;amp;nbsp;Die konkrete Betroffenheit, und wo er landen kann. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, maintain present heading.&lt;br /&gt;
          When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Die ersten Informationen sind auch für VATSIM-Controller wichtig:&amp;amp;nbsp;Was konkret ist kaputt, und was tut der Pilot gerade? Die letzte Info ist auf VATSIM untergeordnet - sie dient in der Realität dazu, den Umfang der Rettungsmaßnahmen abzuschätzen. &lt;br /&gt;
&lt;br /&gt;
==== 3) Alle weiteren Maßnahmen richten sich an folgenden Gesichtspunkten:  ====&lt;br /&gt;
&lt;br /&gt;
*'''Der Pilot sagt, was er braucht, der ATC liefert's. '''Nicht zu&amp;amp;nbsp;Unrecht steht in den Flugplänen&amp;amp;nbsp;&amp;quot;PIC&amp;quot; - pilot in command. Der Pilot kommandiert seine Maschine auch dann, wenn sie ihm auseinanderfällt. ATC ist der Partner, der ihn dabei unterstützt. ATC schafft niemals dem Piloten an, was er tun soll. &lt;br /&gt;
*'''Kommunikation mit dem Piloten:&amp;amp;nbsp;So wenig wie möglich, so viel wie nötig, so präzise wie möglich'''. Bei Notfällen geht's zu im Cockpit. Warntöne piepsen, Warnmeldungen verlauten, Checklisten werden durchgegangen, Lage wird besprochen. Je mehr Zeit die PilotInnen für sich haben, umso besser. Wenn ein/e PilotIn nicht antwortet:&amp;amp;nbsp;nur die Ruhe. Er/sie befolgt (hoffentlich) die Regel:&amp;amp;nbsp;1-avigate, 2-navigate, 3-communicate, und ist noch nicht bei Stufe 3 angekommen. &lt;br /&gt;
*'''&amp;quot;Ausräumen&amp;quot; des restlichen Flugraums:'''&amp;amp;nbsp;Niemand muss abdrehen oder in eine Holding, der nicht im&amp;amp;nbsp;Weg ist. Anderer traffic kann also weitergehen, sofern er die Notfall-Operation nicht stört. Wenn er stört, dann ist möglich: ILS-Freigabe und weg von der Frequenz, direct holding, oder frühzeitige Übergabe (z.B. an CTR) nach&amp;amp;nbsp;Absprache. &lt;br /&gt;
*'''Der Pilot hat die Wahl der Frequenz:''' ob er an anderen ATC übergeben wird (z.B.&amp;amp;nbsp;TWR), oder auf der Frequenz bleibt und bis auf den&amp;amp;nbsp;Boden gebracht wird.TWR kann sich für die Landefreigabe zB auf die Frequenz von APP dazuhängen, damit der Pilot nicht Frequenz wechseln muss.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''&amp;quot;Mayday&amp;quot; ist ein Notfall, der absolute Priorität hat. Nur der Beginn des Verfahrens ist normiert:&amp;amp;nbsp;Ausrufen durch den Piloten, Bestätigung durch&amp;amp;nbsp;ATC, Information der anderen Piloten und anderen ATC. Dann kommunizieren Pilot und ATC, wie es am günstigsten ist. Aufgabe des ATC ist, den Luftraum und die Funkfrequenz möglichst frei zu halten.''&amp;lt;br&amp;gt; &amp;lt;/blockquote&amp;gt; &lt;br /&gt;
==== 4)&amp;amp;nbsp;Notfallprozedur beenden  ====&lt;br /&gt;
&lt;br /&gt;
Irgendwann ist die Notfallprozedur auch beendet und der Flieger glücklich auf der Runway oder unglücklich im Wald. Dann müssen alle anderen wissen, dass die Notfallprozedur beendet ist und alles normal weitergeht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Hinzu kommt, dass die anderen ATC davon wissen müssen (über Intercom, Text oder Teamspeak). CTR hat vielleicht ein Dutzend Flieger im Holding, die abgebaut werden müssen, und GND ein Dutzend Flieger die raus müssen.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
== Liste möglicher Notfallarten und ihr Handling:&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
=== 1.) Go Around - Durchstarteverfahren  ===&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
*Missed Approach laut Chart&amp;lt;br&amp;gt; &lt;br /&gt;
*Individuelles Handling z.B bestimmte Kursanweisung und Höhe&lt;br /&gt;
&lt;br /&gt;
=== 2.) Rejected Takoff - Startabbruch  ===&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &lt;br /&gt;
&lt;br /&gt;
=== 3.) Radio Communication Failure - Funkausfall  ===&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist. &lt;br /&gt;
&lt;br /&gt;
=== 4.) Loss of ILS, NDB, VOR - Ausfall von Anflughilfen  ===&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &lt;br /&gt;
&lt;br /&gt;
=== 5.) Loss of Cabinpressure - Druckabfall  ===&lt;br /&gt;
&lt;br /&gt;
Dies ist ein Fall, der unangenehm werden könnte für den ATCO bei Hightraffic. Der Pilot wird einen sogenannten &amp;quot;Emergencydescent&amp;quot; einleiten (FL100 or below). Als ATCO ihn so schnell wie nur möglich auf dem eigenen Flughafen landen lassen oder ihn auf einen Ausweichflughafen landen lassen. Wichtig dabei ist, dass der ATCO dem Emergencyflieger nicht zutextet und niederquaselt, sondern der Pilot wird sagen, was er tun wird und ATC wird das bestmögliche tun um ihn das zu gewährleisten. Es kann auch vorkommen, dass der Pilot sagt &amp;quot;ATC standby&amp;quot;, d.h. der ATCO soll diesen Flieger bis auf weiteres nicht ansprechen, außer die Situation wird noch gefährlicher durch z.B. crossing Traffic below. Koordination ist in diesem Fall das A &amp;amp;amp; O! &lt;br /&gt;
&lt;br /&gt;
=== 6.) Loss of Hydraulicpressure - Verlust der Hydraulik  ===&lt;br /&gt;
&lt;br /&gt;
Wenn diese Art von Verlust kommt, dann ist meistens die Aircraftperformance (stark) beeinträchtigt. Wichtig hierbei ist zu Erfahren, inwieweit der Pilot die Kontrolle über seinen Flieger noch hat, d.h. Descentrate/Turnrate erfragen oder ob es andere Probleme gibt. Auch kann es dazukommen, dass der Pilot nur mehr Links oder Rechtskurvene fliegen kann. Auch hier sollte man im Hinterkopf haben, dass sich so eine Situation zu einem noch größeren Notfall entwickeln kann. Den betroffenen Flieger so schnell wie nur möglich auf den Boden bringen - Seperation zu den umliegenden Fliegern erhöhen. &lt;br /&gt;
&lt;br /&gt;
=== 7.) Prioritylanding - Dringlichkeitslandung  ===&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
=== 8.) Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Diese Art von Notfall setzt großes Wissen von Notfällen vorraus, da dies eine sehr anspruchsvolle Prozedur ist. Die beste Art diese Situation zu handeln ist, die Übersicht nicht zu verlieren und den Piloten mit wertvollen Informationen zu &amp;quot;versorgen&amp;quot;, d.h. DME Angabe zum Airport, Speed, Altitude, Heading, zu hoch/tief, Trafficinformation,... Alles in allem ist dies ein &amp;quot;Talk-Down-Approach&amp;quot; indem der ATCO wirklich stark gefordert wird in Sachen Konzentration &amp;amp;amp; Koordination. Diese Informationen sollten nicht nur einmal gegeben werden, sonder wirklich beinahe im Minutentakt. Wichig dabei ist wieder, dass der Flieger so schnell als wie nur möglich am Zielflughafen landen sollte, wenn möglich sogar auf einer eigenen Piste, sodass er den anderen anfliegenden Verkehr nicht behindert. Seperation sollte wieder stark erhöht werden zu umliegenden Fluzeugen, falls nötig sogar Warteverfahren aufbauen. &lt;br /&gt;
&lt;br /&gt;
=== 9.) Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Triebwerksversagen beim&amp;amp;nbsp;Start gehört zu den gefährlichsten Zwischenfällen, die es gibt. Die Höhe über Grund ist niedrig, das Flugzeug läuft auch&amp;amp;nbsp;Hochtouren, die Fluggeschwindigkeit ist niedrig (und damit auch die Stabilität). Knappe Koordination ist hier das A und O. Meist passiert der Vogelschlag noch in Bodennähe nach der v1:&amp;amp;nbsp;Der Flieger kann nicht mehr stoppen und muss in die Luft. Der Mayday-call erreicht also meistens noch den&amp;amp;nbsp;TWR controller. Noch dazu variiert die Schwere der Situation nach dem Grad der Schäden, und das ist nicht immer gleich ersichtlich. Professionalität bei&amp;amp;nbsp;Pilot und TWR&amp;amp;nbsp;controller sind sehr wichtig, damit eine heile Landung gelingt.[http://www.youtube.com/watch?v=9KhZwsYtNDE Folgende Aufnahme ]ist ein&amp;amp;nbsp;Schulbeispiel, wie es gut funktioniert:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;So präzise wie möglich:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Antwort ATC:&amp;amp;nbsp;So präzise wie möglich (merke:&amp;amp;nbsp;Tomson hat keinen request geäussert, also braucht er auch gerade nichts):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warnt andere Stationen, und wartet. Der Pilot ist &amp;quot;in command&amp;quot;, er wird sich schon melden. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Der Pilot hat sich gemeldet. Jetzt macht ATC Angebote. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Jetzt sagt der Pilot, was er vorhat: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial &lt;br /&gt;
towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower liest nur zurück und fertig. Wenn der Pilot nichts will, lässt du ihn in Ruhe. Etwas später macht Manchester noch das Angebot, in Liverpool zu landen - das wird abgelehnt. Noch etwas später meldet Manchester Tower, dass die Landebahn 06R wegen Verschmutzung gesperrt ist - die havarierte Maschine hat Teile verloren (das muss er tun - braucht es doch die Maschine für den&amp;amp;nbsp;Landeanflug). Die Maschine landet kurze Zeit später geordnet und sicher. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*dieser Abschnitt wartet noch auf Vervollständigung&lt;br /&gt;
&lt;br /&gt;
=== 10.) Engine Failure at approach - Triebwerksversagen beim Landeanflug&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
dieser Abschnitt wartet noch auf Vervollständigung &lt;br /&gt;
&lt;br /&gt;
=== 11.) Runway closure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Diese Prozedur wird vom Fluglotsen im TWR ausgelöst. Es gibt zwei Unterschiede: &lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''Wenn die Landebahn nicht mehr benützbar ist (Havarierter Flieger, Flugzeugteile, Tiere, ...), dann ist eine Sperre der Landebahn sofort wirksam:&lt;br /&gt;
&lt;br /&gt;
#Anfliegende Flieger bekommen go-around &lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi clearances zu dieser rwy zu geben &lt;br /&gt;
#Neue Landebahn wird geöffnet (oder Flughafen wird geschlossen) &lt;br /&gt;
#ATIS wird angepasst.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Step-by-step &amp;lt;/span&amp;gt;'''closure:''' Wenn der Grund des Schließens abzusehen ist (Wind dreht langsam, noise abatement rules, ...), dann geht die Schließung der Landebahn mit mehr Ordnung vor sich:&lt;br /&gt;
&lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi Clearances zu dieser rwy zu geben &lt;br /&gt;
#verbleibende anfliegende Flugzeuge bekommen Landefreigabe &lt;br /&gt;
#neue Landebahn wird geöffnet &lt;br /&gt;
#ATIS wird angepasst &lt;br /&gt;
#APP und GND werden informiert.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1748</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1748"/>
		<updated>2012-03-10T20:38:23Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergencies and abnormal procedures arrise from two directions: from the pilots or the ATC- depending where actually they occur. If a pilot gets into trouble then he decleares an emergency. If for example the runway is blocked (damaged aircraft, animals etc.) then the ATC reports abnormal procedures to the surrounding stations. &lt;br /&gt;
&lt;br /&gt;
== Types of abnormal procedures&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
=== PAN&amp;amp;nbsp;(Panne)  ===&lt;br /&gt;
&lt;br /&gt;
Wenn einem Flugzeug einzelne Systeme ausfallen, die ihn nicht in ernste Gefahr bringen, aber dazu bringen könnten, dass er seinen Flug nicht &amp;quot;normal&amp;quot; fortsetzen kann, dann ist dies eine Pannenmeldung.&amp;amp;nbsp;Dazu zählt der Klassiker &amp;quot;low fuel&amp;quot;, aber auch Ausfälle von nicht-vitalen&amp;amp;nbsp;Systemen wie z.B. FMC, VOR receiver oder speedbrakes. Der Flieger kann normal weiter fliegen und üblicherweise auch regulär landen, aber er kann bestimmte Flugmanöver nicht durchführen (ohne VOR receiver geht z.B. kein ILS-Anflug, ohne FMC ist &amp;quot;direct WW380&amp;quot; nicht möglich. &lt;br /&gt;
&lt;br /&gt;
Für den Piloten heisst das:&amp;amp;nbsp;Anmelden der Panne, und was für ihn daraus folgt. &lt;br /&gt;
&amp;lt;pre&amp;gt;G-WIRO:&amp;amp;nbsp;  Pan-pan-pan, G-WIRO, low fuel, requesting CDA to&amp;amp;nbsp;Vienna.&lt;br /&gt;
LOWW_APP: G-WIRO, pan message received, direct WW380, descent 4000ft at own discretion, QNH 1033.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
*''PAN ist nur eine Meldung:&amp;amp;nbsp;Der Flieger fliegt &amp;quot;normal&amp;quot; weiter.&amp;amp;nbsp;ATC berücksichtigt nur, dass er zu bestimmten Manövern evtl. nicht in der Lage ist.''&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Radio communication&amp;amp;nbsp;Failure  ===&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist. [http://wiki.vacc-austria.org/index.php?title=Emergency_Handling#3..29_Radio_Communication_Failure_-_Funkausfall ] &lt;br /&gt;
&lt;br /&gt;
=== Emergency  ===&lt;br /&gt;
&lt;br /&gt;
Wenn ein Pilot einen Zustand bemerkt, die ihm das Weiterfliegen verunmöglichen und das Flugzeug oder Insassen in Gefahr bringen, dann kommt das drastischere Mittel: Der Notruf. Er hat folgende Phasen: &lt;br /&gt;
&lt;br /&gt;
==== 1) Ausrufen des Notfalls durch den Piloten:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Der Pilot meldet sich mit dreimal &amp;quot;mayday&amp;quot;, seinem&amp;amp;nbsp;Callsign, seiner Notlage, was er jetzt tut, und was er jetzt braucht. &lt;br /&gt;
&lt;br /&gt;
Der ATC bestätigt den Ruf (readback), fordert ihn auf, den&amp;amp;nbsp;Transponder auf 7700 zu stellen&amp;amp;nbsp;(das erscheint gleich auf allen ATC-Radarschirmen) und gibt ihm eine schnelle Antwort. &lt;br /&gt;
&lt;br /&gt;
==== 2) &amp;quot;Einrichten&amp;quot; im Notfall:  ====&lt;br /&gt;
&lt;br /&gt;
Der Pilot hat nun einige Sekunden zu tun (seinen bedepschten Vogel auf 20° zu drehen und zu stabilisieren), und der ATC auch:&amp;amp;nbsp;Er muss die anderen Piloten auf der Frequenz informieren, und seine angrenzenden&amp;amp;nbsp;Sektoren, und den Flughafen, zu dem es runter geht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Mit dieser Meldung wissen die Piloten:&amp;amp;nbsp;Sie fliegen ihre Verfahren ungerührt weiter:&amp;amp;nbsp;ihre&amp;amp;nbsp;Routen, ihre SID und STAR, ihre Transitions. Sie melden sich bei ATC nur, wenn es ihre Sicherheit erfordert. Wenn sie Anweisungen vom&amp;amp;nbsp;ATC bekommen, dann lesen sie diese nicht zurück. &lt;br /&gt;
&lt;br /&gt;
Dann wird ATC sich über intercom, Text oder Teamspeak mit den anderen ATC in Verbindung setzen und sie über den&amp;amp;nbsp;Notfall informieren, und was für sie daraus folgt: &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
In der Regel sorgt der Controller als erstes dafür, dass er keinen zusätzlichen&amp;amp;nbsp;Traffic mehr übergeben bekommt, und dass sein&amp;amp;nbsp;Flieger heil weiter kommt. &lt;br /&gt;
&lt;br /&gt;
Ab diesem Punkt gibt es keine festgesetzte Phraseologie mehr. Der ATC spricht so mit dem Piloten, dass er am besten serviciert wird. &lt;br /&gt;
&lt;br /&gt;
Mit dieser Information sich der ATC z.B. wieder an den Piloten wenden und die nächsten Schritte klären:&amp;amp;nbsp;Die konkrete Betroffenheit, und wo er landen kann. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, maintain present heading.&lt;br /&gt;
          When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Die ersten Informationen sind auch für VATSIM-Controller wichtig:&amp;amp;nbsp;Was konkret ist kaputt, und was tut der Pilot gerade? Die letzte Info ist auf VATSIM untergeordnet - sie dient in der Realität dazu, den Umfang der Rettungsmaßnahmen abzuschätzen. &lt;br /&gt;
&lt;br /&gt;
==== 3) Alle weiteren Maßnahmen richten sich an folgenden Gesichtspunkten:  ====&lt;br /&gt;
&lt;br /&gt;
*'''Der Pilot sagt, was er braucht, der ATC liefert's. '''Nicht zu&amp;amp;nbsp;Unrecht steht in den Flugplänen&amp;amp;nbsp;&amp;quot;PIC&amp;quot; - pilot in command. Der Pilot kommandiert seine Maschine auch dann, wenn sie ihm auseinanderfällt. ATC ist der Partner, der ihn dabei unterstützt. ATC schafft niemals dem Piloten an, was er tun soll. &lt;br /&gt;
*'''Kommunikation mit dem Piloten:&amp;amp;nbsp;So wenig wie möglich, so viel wie nötig, so präzise wie möglich'''. Bei Notfällen geht's zu im Cockpit. Warntöne piepsen, Warnmeldungen verlauten, Checklisten werden durchgegangen, Lage wird besprochen. Je mehr Zeit die PilotInnen für sich haben, umso besser. Wenn ein/e PilotIn nicht antwortet:&amp;amp;nbsp;nur die Ruhe. Er/sie befolgt (hoffentlich) die Regel:&amp;amp;nbsp;1-avigate, 2-navigate, 3-communicate, und ist noch nicht bei Stufe 3 angekommen. &lt;br /&gt;
*'''&amp;quot;Ausräumen&amp;quot; des restlichen Flugraums:'''&amp;amp;nbsp;Niemand muss abdrehen oder in eine Holding, der nicht im&amp;amp;nbsp;Weg ist. Anderer traffic kann also weitergehen, sofern er die Notfall-Operation nicht stört. Wenn er stört, dann ist möglich: ILS-Freigabe und weg von der Frequenz, direct holding, oder frühzeitige Übergabe (z.B. an CTR) nach&amp;amp;nbsp;Absprache. &lt;br /&gt;
*'''Der Pilot hat die Wahl der Frequenz:''' ob er an anderen ATC übergeben wird (z.B.&amp;amp;nbsp;TWR), oder auf der Frequenz bleibt und bis auf den&amp;amp;nbsp;Boden gebracht wird.TWR kann sich für die Landefreigabe zB auf die Frequenz von APP dazuhängen, damit der Pilot nicht Frequenz wechseln muss.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''&amp;quot;Mayday&amp;quot; ist ein Notfall, der absolute Priorität hat. Nur der Beginn des Verfahrens ist normiert:&amp;amp;nbsp;Ausrufen durch den Piloten, Bestätigung durch&amp;amp;nbsp;ATC, Information der anderen Piloten und anderen ATC. Dann kommunizieren Pilot und ATC, wie es am günstigsten ist. Aufgabe des ATC ist, den Luftraum und die Funkfrequenz möglichst frei zu halten.''&amp;lt;br&amp;gt; &amp;lt;/blockquote&amp;gt; &lt;br /&gt;
==== 4)&amp;amp;nbsp;Notfallprozedur beenden  ====&lt;br /&gt;
&lt;br /&gt;
Irgendwann ist die Notfallprozedur auch beendet und der Flieger glücklich auf der Runway oder unglücklich im Wald. Dann müssen alle anderen wissen, dass die Notfallprozedur beendet ist und alles normal weitergeht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Hinzu kommt, dass die anderen ATC davon wissen müssen (über Intercom, Text oder Teamspeak). CTR hat vielleicht ein Dutzend Flieger im Holding, die abgebaut werden müssen, und GND ein Dutzend Flieger die raus müssen.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
== Liste möglicher Notfallarten und ihr Handling:&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
=== 1.) Go Around - Durchstarteverfahren  ===&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
*Missed Approach laut Chart&amp;lt;br&amp;gt; &lt;br /&gt;
*Individuelles Handling z.B bestimmte Kursanweisung und Höhe&lt;br /&gt;
&lt;br /&gt;
=== 2.) Rejected Takoff - Startabbruch  ===&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &lt;br /&gt;
&lt;br /&gt;
=== 3.) Radio Communication Failure - Funkausfall  ===&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist. &lt;br /&gt;
&lt;br /&gt;
=== 4.) Loss of ILS, NDB, VOR - Ausfall von Anflughilfen  ===&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &lt;br /&gt;
&lt;br /&gt;
=== 5.) Loss of Cabinpressure - Druckabfall  ===&lt;br /&gt;
&lt;br /&gt;
Dies ist ein Fall, der unangenehm werden könnte für den ATCO bei Hightraffic. Der Pilot wird einen sogenannten &amp;quot;Emergencydescent&amp;quot; einleiten (FL100 or below). Als ATCO ihn so schnell wie nur möglich auf dem eigenen Flughafen landen lassen oder ihn auf einen Ausweichflughafen landen lassen. Wichtig dabei ist, dass der ATCO dem Emergencyflieger nicht zutextet und niederquaselt, sondern der Pilot wird sagen, was er tun wird und ATC wird das bestmögliche tun um ihn das zu gewährleisten. Es kann auch vorkommen, dass der Pilot sagt &amp;quot;ATC standby&amp;quot;, d.h. der ATCO soll diesen Flieger bis auf weiteres nicht ansprechen, außer die Situation wird noch gefährlicher durch z.B. crossing Traffic below. Koordination ist in diesem Fall das A &amp;amp;amp; O! &lt;br /&gt;
&lt;br /&gt;
=== 6.) Loss of Hydraulicpressure - Verlust der Hydraulik  ===&lt;br /&gt;
&lt;br /&gt;
Wenn diese Art von Verlust kommt, dann ist meistens die Aircraftperformance (stark) beeinträchtigt. Wichtig hierbei ist zu Erfahren, inwieweit der Pilot die Kontrolle über seinen Flieger noch hat, d.h. Descentrate/Turnrate erfragen oder ob es andere Probleme gibt. Auch kann es dazukommen, dass der Pilot nur mehr Links oder Rechtskurvene fliegen kann. Auch hier sollte man im Hinterkopf haben, dass sich so eine Situation zu einem noch größeren Notfall entwickeln kann. Den betroffenen Flieger so schnell wie nur möglich auf den Boden bringen - Seperation zu den umliegenden Fliegern erhöhen. &lt;br /&gt;
&lt;br /&gt;
=== 7.) Prioritylanding - Dringlichkeitslandung  ===&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
=== 8.) Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Diese Art von Notfall setzt großes Wissen von Notfällen vorraus, da dies eine sehr anspruchsvolle Prozedur ist. Die beste Art diese Situation zu handeln ist, die Übersicht nicht zu verlieren und den Piloten mit wertvollen Informationen zu &amp;quot;versorgen&amp;quot;, d.h. DME Angabe zum Airport, Speed, Altitude, Heading, zu hoch/tief, Trafficinformation,... Alles in allem ist dies ein &amp;quot;Talk-Down-Approach&amp;quot; indem der ATCO wirklich stark gefordert wird in Sachen Konzentration &amp;amp;amp; Koordination. Diese Informationen sollten nicht nur einmal gegeben werden, sonder wirklich beinahe im Minutentakt. Wichig dabei ist wieder, dass der Flieger so schnell als wie nur möglich am Zielflughafen landen sollte, wenn möglich sogar auf einer eigenen Piste, sodass er den anderen anfliegenden Verkehr nicht behindert. Seperation sollte wieder stark erhöht werden zu umliegenden Fluzeugen, falls nötig sogar Warteverfahren aufbauen. &lt;br /&gt;
&lt;br /&gt;
=== 9.) Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Triebwerksversagen beim&amp;amp;nbsp;Start gehört zu den gefährlichsten Zwischenfällen, die es gibt. Die Höhe über Grund ist niedrig, das Flugzeug läuft auch&amp;amp;nbsp;Hochtouren, die Fluggeschwindigkeit ist niedrig (und damit auch die Stabilität). Knappe Koordination ist hier das A und O. Meist passiert der Vogelschlag noch in Bodennähe nach der v1:&amp;amp;nbsp;Der Flieger kann nicht mehr stoppen und muss in die Luft. Der Mayday-call erreicht also meistens noch den&amp;amp;nbsp;TWR controller. Noch dazu variiert die Schwere der Situation nach dem Grad der Schäden, und das ist nicht immer gleich ersichtlich. Professionalität bei&amp;amp;nbsp;Pilot und TWR&amp;amp;nbsp;controller sind sehr wichtig, damit eine heile Landung gelingt.[http://www.youtube.com/watch?v=9KhZwsYtNDE Folgende Aufnahme ]ist ein&amp;amp;nbsp;Schulbeispiel, wie es gut funktioniert:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;So präzise wie möglich:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Antwort ATC:&amp;amp;nbsp;So präzise wie möglich (merke:&amp;amp;nbsp;Tomson hat keinen request geäussert, also braucht er auch gerade nichts):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warnt andere Stationen, und wartet. Der Pilot ist &amp;quot;in command&amp;quot;, er wird sich schon melden. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Der Pilot hat sich gemeldet. Jetzt macht ATC Angebote. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Jetzt sagt der Pilot, was er vorhat: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial &lt;br /&gt;
towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower liest nur zurück und fertig. Wenn der Pilot nichts will, lässt du ihn in Ruhe. Etwas später macht Manchester noch das Angebot, in Liverpool zu landen - das wird abgelehnt. Noch etwas später meldet Manchester Tower, dass die Landebahn 06R wegen Verschmutzung gesperrt ist - die havarierte Maschine hat Teile verloren (das muss er tun - braucht es doch die Maschine für den&amp;amp;nbsp;Landeanflug). Die Maschine landet kurze Zeit später geordnet und sicher. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*dieser Abschnitt wartet noch auf Vervollständigung&lt;br /&gt;
&lt;br /&gt;
=== 10.) Engine Failure at approach - Triebwerksversagen beim Landeanflug&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
dieser Abschnitt wartet noch auf Vervollständigung &lt;br /&gt;
&lt;br /&gt;
=== 11.) Runway closure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Diese Prozedur wird vom Fluglotsen im TWR ausgelöst. Es gibt zwei Unterschiede: &lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''Wenn die Landebahn nicht mehr benützbar ist (Havarierter Flieger, Flugzeugteile, Tiere, ...), dann ist eine Sperre der Landebahn sofort wirksam:&lt;br /&gt;
&lt;br /&gt;
#Anfliegende Flieger bekommen go-around &lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi clearances zu dieser rwy zu geben &lt;br /&gt;
#Neue Landebahn wird geöffnet (oder Flughafen wird geschlossen) &lt;br /&gt;
#ATIS wird angepasst.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Step-by-step &amp;lt;/span&amp;gt;'''closure:''' Wenn der Grund des Schließens abzusehen ist (Wind dreht langsam, noise abatement rules, ...), dann geht die Schließung der Landebahn mit mehr Ordnung vor sich:&lt;br /&gt;
&lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi Clearances zu dieser rwy zu geben &lt;br /&gt;
#verbleibende anfliegende Flugzeuge bekommen Landefreigabe &lt;br /&gt;
#neue Landebahn wird geöffnet &lt;br /&gt;
#ATIS wird angepasst &lt;br /&gt;
#APP und GND werden informiert.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1747</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1747"/>
		<updated>2012-03-10T20:28:53Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergencies and abnormal procedures arrise from two directions: from the pilots or the ATC- depending where actually they occur. If a pilot gets into trouble then he decleares emergency. If for example the runway is blocked (damaged aircraft, animals etc.) then the ATC reports abnormal procedures to the surrounding stations. &lt;br /&gt;
&lt;br /&gt;
== Drei Typen von Notfällen, die der/die PilotIn anmeldet:  ==&lt;br /&gt;
&lt;br /&gt;
=== PAN&amp;amp;nbsp;(Panne)  ===&lt;br /&gt;
&lt;br /&gt;
Wenn einem Flugzeug einzelne Systeme ausfallen, die ihn nicht in ernste Gefahr bringen, aber dazu bringen könnten, dass er seinen Flug nicht &amp;quot;normal&amp;quot; fortsetzen kann, dann ist dies eine Pannenmeldung.&amp;amp;nbsp;Dazu zählt der Klassiker &amp;quot;low fuel&amp;quot;, aber auch Ausfälle von nicht-vitalen&amp;amp;nbsp;Systemen wie z.B. FMC, VOR receiver oder speedbrakes. Der Flieger kann normal weiter fliegen und üblicherweise auch regulär landen, aber er kann bestimmte Flugmanöver nicht durchführen (ohne VOR receiver geht z.B. kein ILS-Anflug, ohne FMC ist &amp;quot;direct WW380&amp;quot; nicht möglich. &lt;br /&gt;
&lt;br /&gt;
Für den Piloten heisst das:&amp;amp;nbsp;Anmelden der Panne, und was für ihn daraus folgt. &lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123:&amp;amp;nbsp;Pan-pan-pan, Laipzich Air 123, low fuel, requesting CDA to&amp;amp;nbsp;Vienna.&lt;br /&gt;
LOWW_APP:&amp;amp;nbsp;Leipzig Air 123, pan message received, direct WW380, descent 4000ft at own discretion, QNH 1033.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
APP wird danach in diesem Beispiel zweierlei tun: &lt;br /&gt;
&lt;br /&gt;
*Er wird ins Textfeld eine Notiz schreiben, damit die anderen Controller bescheid wissen (z.B. &amp;quot;low fuel&amp;quot;). Damit weiss TWR, dass &amp;quot;go-around&amp;quot; gefährlich sein kann. &lt;br /&gt;
*Er wird den&amp;amp;nbsp;Flieger im&amp;amp;nbsp;Auge behalten, andere Flieger auf Kollisionskurs ablenken, erhöhte Separation sicherstellen und darauf achten, dass das Flugzeug kontinuierlich sinken kann.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;''PAN ist nur eine Meldung:&amp;amp;nbsp;Der Flieger fliegt &amp;quot;normal&amp;quot; weiter.&amp;amp;nbsp;ATC berücksichtigt nur, dass er zu bestimmten Manövern evtl. nicht in der Lage ist.''&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
=== Radio communication&amp;amp;nbsp;Failure  ===&lt;br /&gt;
&lt;br /&gt;
Dazu gibt es weiter unten einen [http://wiki.vacc-austria.org/index.php?title=Emergency_Handling#3..29_Radio_Communication_Failure_-_Funkausfall eigenen&amp;amp;nbsp;Abschnitt.] &lt;br /&gt;
&lt;br /&gt;
=== Mayday - ein wirklicher Notfall.  ===&lt;br /&gt;
&lt;br /&gt;
Wenn ein Pilot einen Zustand bemerkt, die ihm das Weiterfliegen verunmöglichen und das Flugzeug oder Insassen in Gefahr bringen, dann kommt das drastischere Mittel: Der Notruf. Er hat folgende Phasen: &lt;br /&gt;
&lt;br /&gt;
==== 1) Ausrufen des Notfalls durch den Piloten:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Der Pilot meldet sich mit dreimal &amp;quot;mayday&amp;quot;, seinem&amp;amp;nbsp;Callsign, seiner Notlage, was er jetzt tut, und was er jetzt braucht. &lt;br /&gt;
&lt;br /&gt;
Der ATC bestätigt den Ruf (readback), fordert ihn auf, den&amp;amp;nbsp;Transponder auf 7700 zu stellen&amp;amp;nbsp;(das erscheint gleich auf allen ATC-Radarschirmen) und gibt ihm eine schnelle Antwort. &lt;br /&gt;
&lt;br /&gt;
==== 2) &amp;quot;Einrichten&amp;quot; im Notfall:  ====&lt;br /&gt;
&lt;br /&gt;
Der Pilot hat nun einige Sekunden zu tun (seinen bedepschten Vogel auf 20° zu drehen und zu stabilisieren), und der ATC auch:&amp;amp;nbsp;Er muss die anderen Piloten auf der Frequenz informieren, und seine angrenzenden&amp;amp;nbsp;Sektoren, und den Flughafen, zu dem es runter geht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Mit dieser Meldung wissen die Piloten:&amp;amp;nbsp;Sie fliegen ihre Verfahren ungerührt weiter:&amp;amp;nbsp;ihre&amp;amp;nbsp;Routen, ihre SID und STAR, ihre Transitions. Sie melden sich bei ATC nur, wenn es ihre Sicherheit erfordert. Wenn sie Anweisungen vom&amp;amp;nbsp;ATC bekommen, dann lesen sie diese nicht zurück. &lt;br /&gt;
&lt;br /&gt;
Dann wird ATC sich über intercom, Text oder Teamspeak mit den anderen ATC in Verbindung setzen und sie über den&amp;amp;nbsp;Notfall informieren, und was für sie daraus folgt: &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
In der Regel sorgt der Controller als erstes dafür, dass er keinen zusätzlichen&amp;amp;nbsp;Traffic mehr übergeben bekommt, und dass sein&amp;amp;nbsp;Flieger heil weiter kommt. &lt;br /&gt;
&lt;br /&gt;
Ab diesem Punkt gibt es keine festgesetzte Phraseologie mehr. Der ATC spricht so mit dem Piloten, dass er am besten serviciert wird. &lt;br /&gt;
&lt;br /&gt;
Mit dieser Information sich der ATC z.B. wieder an den Piloten wenden und die nächsten Schritte klären:&amp;amp;nbsp;Die konkrete Betroffenheit, und wo er landen kann. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, maintain present heading.&lt;br /&gt;
          When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Die ersten Informationen sind auch für VATSIM-Controller wichtig:&amp;amp;nbsp;Was konkret ist kaputt, und was tut der Pilot gerade? Die letzte Info ist auf VATSIM untergeordnet - sie dient in der Realität dazu, den Umfang der Rettungsmaßnahmen abzuschätzen. &lt;br /&gt;
&lt;br /&gt;
==== 3) Alle weiteren Maßnahmen richten sich an folgenden Gesichtspunkten:  ====&lt;br /&gt;
&lt;br /&gt;
*'''Der Pilot sagt, was er braucht, der ATC liefert's. '''Nicht zu&amp;amp;nbsp;Unrecht steht in den Flugplänen&amp;amp;nbsp;&amp;quot;PIC&amp;quot; - pilot in command. Der Pilot kommandiert seine Maschine auch dann, wenn sie ihm auseinanderfällt. ATC ist der Partner, der ihn dabei unterstützt. ATC schafft niemals dem Piloten an, was er tun soll. &lt;br /&gt;
*'''Kommunikation mit dem Piloten:&amp;amp;nbsp;So wenig wie möglich, so viel wie nötig, so präzise wie möglich'''. Bei Notfällen geht's zu im Cockpit. Warntöne piepsen, Warnmeldungen verlauten, Checklisten werden durchgegangen, Lage wird besprochen. Je mehr Zeit die PilotInnen für sich haben, umso besser. Wenn ein/e PilotIn nicht antwortet:&amp;amp;nbsp;nur die Ruhe. Er/sie befolgt (hoffentlich) die Regel:&amp;amp;nbsp;1-avigate, 2-navigate, 3-communicate, und ist noch nicht bei Stufe 3 angekommen. &lt;br /&gt;
*'''&amp;quot;Ausräumen&amp;quot; des restlichen Flugraums:'''&amp;amp;nbsp;Niemand muss abdrehen oder in eine Holding, der nicht im&amp;amp;nbsp;Weg ist. Anderer traffic kann also weitergehen, sofern er die Notfall-Operation nicht stört. Wenn er stört, dann ist möglich: ILS-Freigabe und weg von der Frequenz, direct holding, oder frühzeitige Übergabe (z.B. an CTR) nach&amp;amp;nbsp;Absprache. &lt;br /&gt;
*'''Der Pilot hat die Wahl der Frequenz:''' ob er an anderen ATC übergeben wird (z.B.&amp;amp;nbsp;TWR), oder auf der Frequenz bleibt und bis auf den&amp;amp;nbsp;Boden gebracht wird.TWR kann sich für die Landefreigabe zB auf die Frequenz von APP dazuhängen, damit der Pilot nicht Frequenz wechseln muss.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''&amp;quot;Mayday&amp;quot; ist ein Notfall, der absolute Priorität hat. Nur der Beginn des Verfahrens ist normiert:&amp;amp;nbsp;Ausrufen durch den Piloten, Bestätigung durch&amp;amp;nbsp;ATC, Information der anderen Piloten und anderen ATC. Dann kommunizieren Pilot und ATC, wie es am günstigsten ist. Aufgabe des ATC ist, den Luftraum und die Funkfrequenz möglichst frei zu halten.''&amp;lt;br&amp;gt; &amp;lt;/blockquote&amp;gt; &lt;br /&gt;
==== 4)&amp;amp;nbsp;Notfallprozedur beenden  ====&lt;br /&gt;
&lt;br /&gt;
Irgendwann ist die Notfallprozedur auch beendet und der Flieger glücklich auf der Runway oder unglücklich im Wald. Dann müssen alle anderen wissen, dass die Notfallprozedur beendet ist und alles normal weitergeht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Hinzu kommt, dass die anderen ATC davon wissen müssen (über Intercom, Text oder Teamspeak). CTR hat vielleicht ein Dutzend Flieger im Holding, die abgebaut werden müssen, und GND ein Dutzend Flieger die raus müssen.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
== Liste möglicher Notfallarten und ihr Handling:&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
=== 1.) Go Around - Durchstarteverfahren  ===&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
*Missed Approach laut Chart&amp;lt;br&amp;gt; &lt;br /&gt;
*Individuelles Handling z.B bestimmte Kursanweisung und Höhe&lt;br /&gt;
&lt;br /&gt;
=== 2.) Rejected Takoff - Startabbruch  ===&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &lt;br /&gt;
&lt;br /&gt;
=== 3.) Radio Communication Failure - Funkausfall  ===&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist. &lt;br /&gt;
&lt;br /&gt;
=== 4.) Loss of ILS, NDB, VOR - Ausfall von Anflughilfen  ===&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &lt;br /&gt;
&lt;br /&gt;
=== 5.) Loss of Cabinpressure - Druckabfall  ===&lt;br /&gt;
&lt;br /&gt;
Dies ist ein Fall, der unangenehm werden könnte für den ATCO bei Hightraffic. Der Pilot wird einen sogenannten &amp;quot;Emergencydescent&amp;quot; einleiten (FL100 or below). Als ATCO ihn so schnell wie nur möglich auf dem eigenen Flughafen landen lassen oder ihn auf einen Ausweichflughafen landen lassen. Wichtig dabei ist, dass der ATCO dem Emergencyflieger nicht zutextet und niederquaselt, sondern der Pilot wird sagen, was er tun wird und ATC wird das bestmögliche tun um ihn das zu gewährleisten. Es kann auch vorkommen, dass der Pilot sagt &amp;quot;ATC standby&amp;quot;, d.h. der ATCO soll diesen Flieger bis auf weiteres nicht ansprechen, außer die Situation wird noch gefährlicher durch z.B. crossing Traffic below. Koordination ist in diesem Fall das A &amp;amp;amp; O! &lt;br /&gt;
&lt;br /&gt;
=== 6.) Loss of Hydraulicpressure - Verlust der Hydraulik  ===&lt;br /&gt;
&lt;br /&gt;
Wenn diese Art von Verlust kommt, dann ist meistens die Aircraftperformance (stark) beeinträchtigt. Wichtig hierbei ist zu Erfahren, inwieweit der Pilot die Kontrolle über seinen Flieger noch hat, d.h. Descentrate/Turnrate erfragen oder ob es andere Probleme gibt. Auch kann es dazukommen, dass der Pilot nur mehr Links oder Rechtskurvene fliegen kann. Auch hier sollte man im Hinterkopf haben, dass sich so eine Situation zu einem noch größeren Notfall entwickeln kann. Den betroffenen Flieger so schnell wie nur möglich auf den Boden bringen - Seperation zu den umliegenden Fliegern erhöhen. &lt;br /&gt;
&lt;br /&gt;
=== 7.) Prioritylanding - Dringlichkeitslandung  ===&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
=== 8.) Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Diese Art von Notfall setzt großes Wissen von Notfällen vorraus, da dies eine sehr anspruchsvolle Prozedur ist. Die beste Art diese Situation zu handeln ist, die Übersicht nicht zu verlieren und den Piloten mit wertvollen Informationen zu &amp;quot;versorgen&amp;quot;, d.h. DME Angabe zum Airport, Speed, Altitude, Heading, zu hoch/tief, Trafficinformation,... Alles in allem ist dies ein &amp;quot;Talk-Down-Approach&amp;quot; indem der ATCO wirklich stark gefordert wird in Sachen Konzentration &amp;amp;amp; Koordination. Diese Informationen sollten nicht nur einmal gegeben werden, sonder wirklich beinahe im Minutentakt. Wichig dabei ist wieder, dass der Flieger so schnell als wie nur möglich am Zielflughafen landen sollte, wenn möglich sogar auf einer eigenen Piste, sodass er den anderen anfliegenden Verkehr nicht behindert. Seperation sollte wieder stark erhöht werden zu umliegenden Fluzeugen, falls nötig sogar Warteverfahren aufbauen. &lt;br /&gt;
&lt;br /&gt;
=== 9.) Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Triebwerksversagen beim&amp;amp;nbsp;Start gehört zu den gefährlichsten Zwischenfällen, die es gibt. Die Höhe über Grund ist niedrig, das Flugzeug läuft auch&amp;amp;nbsp;Hochtouren, die Fluggeschwindigkeit ist niedrig (und damit auch die Stabilität). Knappe Koordination ist hier das A und O. Meist passiert der Vogelschlag noch in Bodennähe nach der v1:&amp;amp;nbsp;Der Flieger kann nicht mehr stoppen und muss in die Luft. Der Mayday-call erreicht also meistens noch den&amp;amp;nbsp;TWR controller. Noch dazu variiert die Schwere der Situation nach dem Grad der Schäden, und das ist nicht immer gleich ersichtlich. Professionalität bei&amp;amp;nbsp;Pilot und TWR&amp;amp;nbsp;controller sind sehr wichtig, damit eine heile Landung gelingt.[http://www.youtube.com/watch?v=9KhZwsYtNDE Folgende Aufnahme ]ist ein&amp;amp;nbsp;Schulbeispiel, wie es gut funktioniert:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;So präzise wie möglich:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Antwort ATC:&amp;amp;nbsp;So präzise wie möglich (merke:&amp;amp;nbsp;Tomson hat keinen request geäussert, also braucht er auch gerade nichts):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warnt andere Stationen, und wartet. Der Pilot ist &amp;quot;in command&amp;quot;, er wird sich schon melden. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Der Pilot hat sich gemeldet. Jetzt macht ATC Angebote. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Jetzt sagt der Pilot, was er vorhat: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial &lt;br /&gt;
towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower liest nur zurück und fertig. Wenn der Pilot nichts will, lässt du ihn in Ruhe. Etwas später macht Manchester noch das Angebot, in Liverpool zu landen - das wird abgelehnt. Noch etwas später meldet Manchester Tower, dass die Landebahn 06R wegen Verschmutzung gesperrt ist - die havarierte Maschine hat Teile verloren (das muss er tun - braucht es doch die Maschine für den&amp;amp;nbsp;Landeanflug). Die Maschine landet kurze Zeit später geordnet und sicher. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*dieser Abschnitt wartet noch auf Vervollständigung&lt;br /&gt;
&lt;br /&gt;
=== 10.) Engine Failure at approach - Triebwerksversagen beim Landeanflug&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
dieser Abschnitt wartet noch auf Vervollständigung &lt;br /&gt;
&lt;br /&gt;
=== 11.) Runway closure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Diese Prozedur wird vom Fluglotsen im TWR ausgelöst. Es gibt zwei Unterschiede: &lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''Wenn die Landebahn nicht mehr benützbar ist (Havarierter Flieger, Flugzeugteile, Tiere, ...), dann ist eine Sperre der Landebahn sofort wirksam:&lt;br /&gt;
&lt;br /&gt;
#Anfliegende Flieger bekommen go-around &lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi clearances zu dieser rwy zu geben &lt;br /&gt;
#Neue Landebahn wird geöffnet (oder Flughafen wird geschlossen) &lt;br /&gt;
#ATIS wird angepasst.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Step-by-step &amp;lt;/span&amp;gt;'''closure:''' Wenn der Grund des Schließens abzusehen ist (Wind dreht langsam, noise abatement rules, ...), dann geht die Schließung der Landebahn mit mehr Ordnung vor sich:&lt;br /&gt;
&lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi Clearances zu dieser rwy zu geben &lt;br /&gt;
#verbleibende anfliegende Flugzeuge bekommen Landefreigabe &lt;br /&gt;
#neue Landebahn wird geöffnet &lt;br /&gt;
#ATIS wird angepasst &lt;br /&gt;
#APP und GND werden informiert.&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1746</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1746"/>
		<updated>2012-03-10T20:27:04Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergancys and abnormal procedures arrise from two directions: from the pilots or the ATC- depending where actually they occur. If a pilot gets into trouble then he decleares emergency. If for example the runway is blocked (damaged aircraft, animals etc.) then the ATC reports abnormal procedures to the surrounding stations. &lt;br /&gt;
&lt;br /&gt;
== Drei Typen von Notfällen, die der/die PilotIn anmeldet:  ==&lt;br /&gt;
&lt;br /&gt;
=== PAN&amp;amp;nbsp;(Panne)  ===&lt;br /&gt;
&lt;br /&gt;
Wenn einem Flugzeug einzelne Systeme ausfallen, die ihn nicht in ernste Gefahr bringen, aber dazu bringen könnten, dass er seinen Flug nicht &amp;quot;normal&amp;quot; fortsetzen kann, dann ist dies eine Pannenmeldung.&amp;amp;nbsp;Dazu zählt der Klassiker &amp;quot;low fuel&amp;quot;, aber auch Ausfälle von nicht-vitalen&amp;amp;nbsp;Systemen wie z.B. FMC, VOR receiver oder speedbrakes. Der Flieger kann normal weiter fliegen und üblicherweise auch regulär landen, aber er kann bestimmte Flugmanöver nicht durchführen (ohne VOR receiver geht z.B. kein ILS-Anflug, ohne FMC ist &amp;quot;direct WW380&amp;quot; nicht möglich. &lt;br /&gt;
&lt;br /&gt;
Für den Piloten heisst das:&amp;amp;nbsp;Anmelden der Panne, und was für ihn daraus folgt. &lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123:&amp;amp;nbsp;Pan-pan-pan, Laipzich Air 123, low fuel, requesting CDA to&amp;amp;nbsp;Vienna.&lt;br /&gt;
LOWW_APP:&amp;amp;nbsp;Leipzig Air 123, pan message received, direct WW380, descent 4000ft at own discretion, QNH 1033.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
APP wird danach in diesem Beispiel zweierlei tun: &lt;br /&gt;
&lt;br /&gt;
*Er wird ins Textfeld eine Notiz schreiben, damit die anderen Controller bescheid wissen (z.B. &amp;quot;low fuel&amp;quot;). Damit weiss TWR, dass &amp;quot;go-around&amp;quot; gefährlich sein kann. &lt;br /&gt;
*Er wird den&amp;amp;nbsp;Flieger im&amp;amp;nbsp;Auge behalten, andere Flieger auf Kollisionskurs ablenken, erhöhte Separation sicherstellen und darauf achten, dass das Flugzeug kontinuierlich sinken kann.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;''PAN ist nur eine Meldung:&amp;amp;nbsp;Der Flieger fliegt &amp;quot;normal&amp;quot; weiter.&amp;amp;nbsp;ATC berücksichtigt nur, dass er zu bestimmten Manövern evtl. nicht in der Lage ist.''&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
=== Radio communication&amp;amp;nbsp;Failure  ===&lt;br /&gt;
&lt;br /&gt;
Dazu gibt es weiter unten einen [http://wiki.vacc-austria.org/index.php?title=Emergency_Handling#3..29_Radio_Communication_Failure_-_Funkausfall eigenen&amp;amp;nbsp;Abschnitt.] &lt;br /&gt;
&lt;br /&gt;
=== Mayday - ein wirklicher Notfall.  ===&lt;br /&gt;
&lt;br /&gt;
Wenn ein Pilot einen Zustand bemerkt, die ihm das Weiterfliegen verunmöglichen und das Flugzeug oder Insassen in Gefahr bringen, dann kommt das drastischere Mittel: Der Notruf. Er hat folgende Phasen: &lt;br /&gt;
&lt;br /&gt;
==== 1) Ausrufen des Notfalls durch den Piloten:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Der Pilot meldet sich mit dreimal &amp;quot;mayday&amp;quot;, seinem&amp;amp;nbsp;Callsign, seiner Notlage, was er jetzt tut, und was er jetzt braucht. &lt;br /&gt;
&lt;br /&gt;
Der ATC bestätigt den Ruf (readback), fordert ihn auf, den&amp;amp;nbsp;Transponder auf 7700 zu stellen&amp;amp;nbsp;(das erscheint gleich auf allen ATC-Radarschirmen) und gibt ihm eine schnelle Antwort. &lt;br /&gt;
&lt;br /&gt;
==== 2) &amp;quot;Einrichten&amp;quot; im Notfall:  ====&lt;br /&gt;
&lt;br /&gt;
Der Pilot hat nun einige Sekunden zu tun (seinen bedepschten Vogel auf 20° zu drehen und zu stabilisieren), und der ATC auch:&amp;amp;nbsp;Er muss die anderen Piloten auf der Frequenz informieren, und seine angrenzenden&amp;amp;nbsp;Sektoren, und den Flughafen, zu dem es runter geht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Mit dieser Meldung wissen die Piloten:&amp;amp;nbsp;Sie fliegen ihre Verfahren ungerührt weiter:&amp;amp;nbsp;ihre&amp;amp;nbsp;Routen, ihre SID und STAR, ihre Transitions. Sie melden sich bei ATC nur, wenn es ihre Sicherheit erfordert. Wenn sie Anweisungen vom&amp;amp;nbsp;ATC bekommen, dann lesen sie diese nicht zurück. &lt;br /&gt;
&lt;br /&gt;
Dann wird ATC sich über intercom, Text oder Teamspeak mit den anderen ATC in Verbindung setzen und sie über den&amp;amp;nbsp;Notfall informieren, und was für sie daraus folgt: &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
In der Regel sorgt der Controller als erstes dafür, dass er keinen zusätzlichen&amp;amp;nbsp;Traffic mehr übergeben bekommt, und dass sein&amp;amp;nbsp;Flieger heil weiter kommt. &lt;br /&gt;
&lt;br /&gt;
Ab diesem Punkt gibt es keine festgesetzte Phraseologie mehr. Der ATC spricht so mit dem Piloten, dass er am besten serviciert wird. &lt;br /&gt;
&lt;br /&gt;
Mit dieser Information sich der ATC z.B. wieder an den Piloten wenden und die nächsten Schritte klären:&amp;amp;nbsp;Die konkrete Betroffenheit, und wo er landen kann. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, maintain present heading.&lt;br /&gt;
          When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Die ersten Informationen sind auch für VATSIM-Controller wichtig:&amp;amp;nbsp;Was konkret ist kaputt, und was tut der Pilot gerade? Die letzte Info ist auf VATSIM untergeordnet - sie dient in der Realität dazu, den Umfang der Rettungsmaßnahmen abzuschätzen. &lt;br /&gt;
&lt;br /&gt;
==== 3) Alle weiteren Maßnahmen richten sich an folgenden Gesichtspunkten:  ====&lt;br /&gt;
&lt;br /&gt;
*'''Der Pilot sagt, was er braucht, der ATC liefert's. '''Nicht zu&amp;amp;nbsp;Unrecht steht in den Flugplänen&amp;amp;nbsp;&amp;quot;PIC&amp;quot; - pilot in command. Der Pilot kommandiert seine Maschine auch dann, wenn sie ihm auseinanderfällt. ATC ist der Partner, der ihn dabei unterstützt. ATC schafft niemals dem Piloten an, was er tun soll. &lt;br /&gt;
*'''Kommunikation mit dem Piloten:&amp;amp;nbsp;So wenig wie möglich, so viel wie nötig, so präzise wie möglich'''. Bei Notfällen geht's zu im Cockpit. Warntöne piepsen, Warnmeldungen verlauten, Checklisten werden durchgegangen, Lage wird besprochen. Je mehr Zeit die PilotInnen für sich haben, umso besser. Wenn ein/e PilotIn nicht antwortet:&amp;amp;nbsp;nur die Ruhe. Er/sie befolgt (hoffentlich) die Regel:&amp;amp;nbsp;1-avigate, 2-navigate, 3-communicate, und ist noch nicht bei Stufe 3 angekommen. &lt;br /&gt;
*'''&amp;quot;Ausräumen&amp;quot; des restlichen Flugraums:'''&amp;amp;nbsp;Niemand muss abdrehen oder in eine Holding, der nicht im&amp;amp;nbsp;Weg ist. Anderer traffic kann also weitergehen, sofern er die Notfall-Operation nicht stört. Wenn er stört, dann ist möglich: ILS-Freigabe und weg von der Frequenz, direct holding, oder frühzeitige Übergabe (z.B. an CTR) nach&amp;amp;nbsp;Absprache. &lt;br /&gt;
*'''Der Pilot hat die Wahl der Frequenz:''' ob er an anderen ATC übergeben wird (z.B.&amp;amp;nbsp;TWR), oder auf der Frequenz bleibt und bis auf den&amp;amp;nbsp;Boden gebracht wird.TWR kann sich für die Landefreigabe zB auf die Frequenz von APP dazuhängen, damit der Pilot nicht Frequenz wechseln muss.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''&amp;quot;Mayday&amp;quot; ist ein Notfall, der absolute Priorität hat. Nur der Beginn des Verfahrens ist normiert:&amp;amp;nbsp;Ausrufen durch den Piloten, Bestätigung durch&amp;amp;nbsp;ATC, Information der anderen Piloten und anderen ATC. Dann kommunizieren Pilot und ATC, wie es am günstigsten ist. Aufgabe des ATC ist, den Luftraum und die Funkfrequenz möglichst frei zu halten.''&amp;lt;br&amp;gt; &amp;lt;/blockquote&amp;gt; &lt;br /&gt;
==== 4)&amp;amp;nbsp;Notfallprozedur beenden  ====&lt;br /&gt;
&lt;br /&gt;
Irgendwann ist die Notfallprozedur auch beendet und der Flieger glücklich auf der Runway oder unglücklich im Wald. Dann müssen alle anderen wissen, dass die Notfallprozedur beendet ist und alles normal weitergeht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Hinzu kommt, dass die anderen ATC davon wissen müssen (über Intercom, Text oder Teamspeak). CTR hat vielleicht ein Dutzend Flieger im Holding, die abgebaut werden müssen, und GND ein Dutzend Flieger die raus müssen.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
== Liste möglicher Notfallarten und ihr Handling:&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
=== 1.) Go Around - Durchstarteverfahren  ===&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
*Missed Approach laut Chart&amp;lt;br&amp;gt; &lt;br /&gt;
*Individuelles Handling z.B bestimmte Kursanweisung und Höhe&lt;br /&gt;
&lt;br /&gt;
=== 2.) Rejected Takoff - Startabbruch  ===&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &lt;br /&gt;
&lt;br /&gt;
=== 3.) Radio Communication Failure - Funkausfall  ===&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist. &lt;br /&gt;
&lt;br /&gt;
=== 4.) Loss of ILS, NDB, VOR - Ausfall von Anflughilfen  ===&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &lt;br /&gt;
&lt;br /&gt;
=== 5.) Loss of Cabinpressure - Druckabfall  ===&lt;br /&gt;
&lt;br /&gt;
Dies ist ein Fall, der unangenehm werden könnte für den ATCO bei Hightraffic. Der Pilot wird einen sogenannten &amp;quot;Emergencydescent&amp;quot; einleiten (FL100 or below). Als ATCO ihn so schnell wie nur möglich auf dem eigenen Flughafen landen lassen oder ihn auf einen Ausweichflughafen landen lassen. Wichtig dabei ist, dass der ATCO dem Emergencyflieger nicht zutextet und niederquaselt, sondern der Pilot wird sagen, was er tun wird und ATC wird das bestmögliche tun um ihn das zu gewährleisten. Es kann auch vorkommen, dass der Pilot sagt &amp;quot;ATC standby&amp;quot;, d.h. der ATCO soll diesen Flieger bis auf weiteres nicht ansprechen, außer die Situation wird noch gefährlicher durch z.B. crossing Traffic below. Koordination ist in diesem Fall das A &amp;amp;amp; O! &lt;br /&gt;
&lt;br /&gt;
=== 6.) Loss of Hydraulicpressure - Verlust der Hydraulik  ===&lt;br /&gt;
&lt;br /&gt;
Wenn diese Art von Verlust kommt, dann ist meistens die Aircraftperformance (stark) beeinträchtigt. Wichtig hierbei ist zu Erfahren, inwieweit der Pilot die Kontrolle über seinen Flieger noch hat, d.h. Descentrate/Turnrate erfragen oder ob es andere Probleme gibt. Auch kann es dazukommen, dass der Pilot nur mehr Links oder Rechtskurvene fliegen kann. Auch hier sollte man im Hinterkopf haben, dass sich so eine Situation zu einem noch größeren Notfall entwickeln kann. Den betroffenen Flieger so schnell wie nur möglich auf den Boden bringen - Seperation zu den umliegenden Fliegern erhöhen. &lt;br /&gt;
&lt;br /&gt;
=== 7.) Prioritylanding - Dringlichkeitslandung  ===&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
=== 8.) Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Diese Art von Notfall setzt großes Wissen von Notfällen vorraus, da dies eine sehr anspruchsvolle Prozedur ist. Die beste Art diese Situation zu handeln ist, die Übersicht nicht zu verlieren und den Piloten mit wertvollen Informationen zu &amp;quot;versorgen&amp;quot;, d.h. DME Angabe zum Airport, Speed, Altitude, Heading, zu hoch/tief, Trafficinformation,... Alles in allem ist dies ein &amp;quot;Talk-Down-Approach&amp;quot; indem der ATCO wirklich stark gefordert wird in Sachen Konzentration &amp;amp;amp; Koordination. Diese Informationen sollten nicht nur einmal gegeben werden, sonder wirklich beinahe im Minutentakt. Wichig dabei ist wieder, dass der Flieger so schnell als wie nur möglich am Zielflughafen landen sollte, wenn möglich sogar auf einer eigenen Piste, sodass er den anderen anfliegenden Verkehr nicht behindert. Seperation sollte wieder stark erhöht werden zu umliegenden Fluzeugen, falls nötig sogar Warteverfahren aufbauen. &lt;br /&gt;
&lt;br /&gt;
=== 9.) Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Triebwerksversagen beim&amp;amp;nbsp;Start gehört zu den gefährlichsten Zwischenfällen, die es gibt. Die Höhe über Grund ist niedrig, das Flugzeug läuft auch&amp;amp;nbsp;Hochtouren, die Fluggeschwindigkeit ist niedrig (und damit auch die Stabilität). Knappe Koordination ist hier das A und O. Meist passiert der Vogelschlag noch in Bodennähe nach der v1:&amp;amp;nbsp;Der Flieger kann nicht mehr stoppen und muss in die Luft. Der Mayday-call erreicht also meistens noch den&amp;amp;nbsp;TWR controller. Noch dazu variiert die Schwere der Situation nach dem Grad der Schäden, und das ist nicht immer gleich ersichtlich. Professionalität bei&amp;amp;nbsp;Pilot und TWR&amp;amp;nbsp;controller sind sehr wichtig, damit eine heile Landung gelingt.[http://www.youtube.com/watch?v=9KhZwsYtNDE Folgende Aufnahme ]ist ein&amp;amp;nbsp;Schulbeispiel, wie es gut funktioniert:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;So präzise wie möglich:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Antwort ATC:&amp;amp;nbsp;So präzise wie möglich (merke:&amp;amp;nbsp;Tomson hat keinen request geäussert, also braucht er auch gerade nichts):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warnt andere Stationen, und wartet. Der Pilot ist &amp;quot;in command&amp;quot;, er wird sich schon melden. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Der Pilot hat sich gemeldet. Jetzt macht ATC Angebote. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Jetzt sagt der Pilot, was er vorhat: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial &lt;br /&gt;
towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower liest nur zurück und fertig. Wenn der Pilot nichts will, lässt du ihn in Ruhe. Etwas später macht Manchester noch das Angebot, in Liverpool zu landen - das wird abgelehnt. Noch etwas später meldet Manchester Tower, dass die Landebahn 06R wegen Verschmutzung gesperrt ist - die havarierte Maschine hat Teile verloren (das muss er tun - braucht es doch die Maschine für den&amp;amp;nbsp;Landeanflug). Die Maschine landet kurze Zeit später geordnet und sicher. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*dieser Abschnitt wartet noch auf Vervollständigung&lt;br /&gt;
&lt;br /&gt;
=== 10.) Engine Failure at approach - Triebwerksversagen beim Landeanflug&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
dieser Abschnitt wartet noch auf Vervollständigung &lt;br /&gt;
&lt;br /&gt;
=== 11.) Runway closure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Diese Prozedur wird vom Fluglotsen im TWR ausgelöst. Es gibt zwei Unterschiede: &lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''Wenn die Landebahn nicht mehr benützbar ist (Havarierter Flieger, Flugzeugteile, Tiere, ...), dann ist eine Sperre der Landebahn sofort wirksam:&lt;br /&gt;
&lt;br /&gt;
#Anfliegende Flieger bekommen go-around &lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi clearances zu dieser rwy zu geben &lt;br /&gt;
#Neue Landebahn wird geöffnet (oder Flughafen wird geschlossen) &lt;br /&gt;
#ATIS wird angepasst.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Step-by-step &amp;lt;/span&amp;gt;'''closure:''' Wenn der Grund des Schließens abzusehen ist (Wind dreht langsam, noise abatement rules, ...), dann geht die Schließung der Landebahn mit mehr Ordnung vor sich:&lt;br /&gt;
&lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi Clearances zu dieser rwy zu geben &lt;br /&gt;
#verbleibende anfliegende Flugzeuge bekommen Landefreigabe &lt;br /&gt;
#neue Landebahn wird geöffnet &lt;br /&gt;
#ATIS wird angepasst &lt;br /&gt;
#APP und GND werden informiert.&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1745</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1745"/>
		<updated>2012-03-10T20:24:30Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergancys and abnormal procedures arrise from two directions: from the pilots or the ATC- depending where acactly they occur. If a pilot gets into troubble than he decleares emergency. If for example the runway is blocked (damaged aircraft, animals etc.) than the ATC reports abnormal procedures to the surrounding stations. &lt;br /&gt;
&lt;br /&gt;
== Drei Typen von Notfällen, die der/die PilotIn anmeldet:  ==&lt;br /&gt;
&lt;br /&gt;
=== PAN&amp;amp;nbsp;(Panne)  ===&lt;br /&gt;
&lt;br /&gt;
Wenn einem Flugzeug einzelne Systeme ausfallen, die ihn nicht in ernste Gefahr bringen, aber dazu bringen könnten, dass er seinen Flug nicht &amp;quot;normal&amp;quot; fortsetzen kann, dann ist dies eine Pannenmeldung.&amp;amp;nbsp;Dazu zählt der Klassiker &amp;quot;low fuel&amp;quot;, aber auch Ausfälle von nicht-vitalen&amp;amp;nbsp;Systemen wie z.B. FMC, VOR receiver oder speedbrakes. Der Flieger kann normal weiter fliegen und üblicherweise auch regulär landen, aber er kann bestimmte Flugmanöver nicht durchführen (ohne VOR receiver geht z.B. kein ILS-Anflug, ohne FMC ist &amp;quot;direct WW380&amp;quot; nicht möglich. &lt;br /&gt;
&lt;br /&gt;
Für den Piloten heisst das:&amp;amp;nbsp;Anmelden der Panne, und was für ihn daraus folgt. &lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123:&amp;amp;nbsp;Pan-pan-pan, Laipzich Air 123, low fuel, requesting CDA to&amp;amp;nbsp;Vienna.&lt;br /&gt;
LOWW_APP:&amp;amp;nbsp;Leipzig Air 123, pan message received, direct WW380, descent 4000ft at own discretion, QNH 1033.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
APP wird danach in diesem Beispiel zweierlei tun: &lt;br /&gt;
&lt;br /&gt;
*Er wird ins Textfeld eine Notiz schreiben, damit die anderen Controller bescheid wissen (z.B. &amp;quot;low fuel&amp;quot;). Damit weiss TWR, dass &amp;quot;go-around&amp;quot; gefährlich sein kann. &lt;br /&gt;
*Er wird den&amp;amp;nbsp;Flieger im&amp;amp;nbsp;Auge behalten, andere Flieger auf Kollisionskurs ablenken, erhöhte Separation sicherstellen und darauf achten, dass das Flugzeug kontinuierlich sinken kann.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;''PAN ist nur eine Meldung:&amp;amp;nbsp;Der Flieger fliegt &amp;quot;normal&amp;quot; weiter.&amp;amp;nbsp;ATC berücksichtigt nur, dass er zu bestimmten Manövern evtl. nicht in der Lage ist.''&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
=== Radio communication&amp;amp;nbsp;Failure  ===&lt;br /&gt;
&lt;br /&gt;
Dazu gibt es weiter unten einen [http://wiki.vacc-austria.org/index.php?title=Emergency_Handling#3..29_Radio_Communication_Failure_-_Funkausfall eigenen&amp;amp;nbsp;Abschnitt.] &lt;br /&gt;
&lt;br /&gt;
=== Mayday - ein wirklicher Notfall.  ===&lt;br /&gt;
&lt;br /&gt;
Wenn ein Pilot einen Zustand bemerkt, die ihm das Weiterfliegen verunmöglichen und das Flugzeug oder Insassen in Gefahr bringen, dann kommt das drastischere Mittel: Der Notruf. Er hat folgende Phasen: &lt;br /&gt;
&lt;br /&gt;
==== 1) Ausrufen des Notfalls durch den Piloten:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Der Pilot meldet sich mit dreimal &amp;quot;mayday&amp;quot;, seinem&amp;amp;nbsp;Callsign, seiner Notlage, was er jetzt tut, und was er jetzt braucht. &lt;br /&gt;
&lt;br /&gt;
Der ATC bestätigt den Ruf (readback), fordert ihn auf, den&amp;amp;nbsp;Transponder auf 7700 zu stellen&amp;amp;nbsp;(das erscheint gleich auf allen ATC-Radarschirmen) und gibt ihm eine schnelle Antwort. &lt;br /&gt;
&lt;br /&gt;
==== 2) &amp;quot;Einrichten&amp;quot; im Notfall:  ====&lt;br /&gt;
&lt;br /&gt;
Der Pilot hat nun einige Sekunden zu tun (seinen bedepschten Vogel auf 20° zu drehen und zu stabilisieren), und der ATC auch:&amp;amp;nbsp;Er muss die anderen Piloten auf der Frequenz informieren, und seine angrenzenden&amp;amp;nbsp;Sektoren, und den Flughafen, zu dem es runter geht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Mit dieser Meldung wissen die Piloten:&amp;amp;nbsp;Sie fliegen ihre Verfahren ungerührt weiter:&amp;amp;nbsp;ihre&amp;amp;nbsp;Routen, ihre SID und STAR, ihre Transitions. Sie melden sich bei ATC nur, wenn es ihre Sicherheit erfordert. Wenn sie Anweisungen vom&amp;amp;nbsp;ATC bekommen, dann lesen sie diese nicht zurück. &lt;br /&gt;
&lt;br /&gt;
Dann wird ATC sich über intercom, Text oder Teamspeak mit den anderen ATC in Verbindung setzen und sie über den&amp;amp;nbsp;Notfall informieren, und was für sie daraus folgt: &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
In der Regel sorgt der Controller als erstes dafür, dass er keinen zusätzlichen&amp;amp;nbsp;Traffic mehr übergeben bekommt, und dass sein&amp;amp;nbsp;Flieger heil weiter kommt. &lt;br /&gt;
&lt;br /&gt;
Ab diesem Punkt gibt es keine festgesetzte Phraseologie mehr. Der ATC spricht so mit dem Piloten, dass er am besten serviciert wird. &lt;br /&gt;
&lt;br /&gt;
Mit dieser Information sich der ATC z.B. wieder an den Piloten wenden und die nächsten Schritte klären:&amp;amp;nbsp;Die konkrete Betroffenheit, und wo er landen kann. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, maintain present heading.&lt;br /&gt;
          When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Die ersten Informationen sind auch für VATSIM-Controller wichtig:&amp;amp;nbsp;Was konkret ist kaputt, und was tut der Pilot gerade? Die letzte Info ist auf VATSIM untergeordnet - sie dient in der Realität dazu, den Umfang der Rettungsmaßnahmen abzuschätzen. &lt;br /&gt;
&lt;br /&gt;
==== 3) Alle weiteren Maßnahmen richten sich an folgenden Gesichtspunkten:  ====&lt;br /&gt;
&lt;br /&gt;
*'''Der Pilot sagt, was er braucht, der ATC liefert's. '''Nicht zu&amp;amp;nbsp;Unrecht steht in den Flugplänen&amp;amp;nbsp;&amp;quot;PIC&amp;quot; - pilot in command. Der Pilot kommandiert seine Maschine auch dann, wenn sie ihm auseinanderfällt. ATC ist der Partner, der ihn dabei unterstützt. ATC schafft niemals dem Piloten an, was er tun soll. &lt;br /&gt;
*'''Kommunikation mit dem Piloten:&amp;amp;nbsp;So wenig wie möglich, so viel wie nötig, so präzise wie möglich'''. Bei Notfällen geht's zu im Cockpit. Warntöne piepsen, Warnmeldungen verlauten, Checklisten werden durchgegangen, Lage wird besprochen. Je mehr Zeit die PilotInnen für sich haben, umso besser. Wenn ein/e PilotIn nicht antwortet:&amp;amp;nbsp;nur die Ruhe. Er/sie befolgt (hoffentlich) die Regel:&amp;amp;nbsp;1-avigate, 2-navigate, 3-communicate, und ist noch nicht bei Stufe 3 angekommen. &lt;br /&gt;
*'''&amp;quot;Ausräumen&amp;quot; des restlichen Flugraums:'''&amp;amp;nbsp;Niemand muss abdrehen oder in eine Holding, der nicht im&amp;amp;nbsp;Weg ist. Anderer traffic kann also weitergehen, sofern er die Notfall-Operation nicht stört. Wenn er stört, dann ist möglich: ILS-Freigabe und weg von der Frequenz, direct holding, oder frühzeitige Übergabe (z.B. an CTR) nach&amp;amp;nbsp;Absprache. &lt;br /&gt;
*'''Der Pilot hat die Wahl der Frequenz:''' ob er an anderen ATC übergeben wird (z.B.&amp;amp;nbsp;TWR), oder auf der Frequenz bleibt und bis auf den&amp;amp;nbsp;Boden gebracht wird.TWR kann sich für die Landefreigabe zB auf die Frequenz von APP dazuhängen, damit der Pilot nicht Frequenz wechseln muss.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''&amp;quot;Mayday&amp;quot; ist ein Notfall, der absolute Priorität hat. Nur der Beginn des Verfahrens ist normiert:&amp;amp;nbsp;Ausrufen durch den Piloten, Bestätigung durch&amp;amp;nbsp;ATC, Information der anderen Piloten und anderen ATC. Dann kommunizieren Pilot und ATC, wie es am günstigsten ist. Aufgabe des ATC ist, den Luftraum und die Funkfrequenz möglichst frei zu halten.''&amp;lt;br&amp;gt; &amp;lt;/blockquote&amp;gt; &lt;br /&gt;
==== 4)&amp;amp;nbsp;Notfallprozedur beenden  ====&lt;br /&gt;
&lt;br /&gt;
Irgendwann ist die Notfallprozedur auch beendet und der Flieger glücklich auf der Runway oder unglücklich im Wald. Dann müssen alle anderen wissen, dass die Notfallprozedur beendet ist und alles normal weitergeht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Hinzu kommt, dass die anderen ATC davon wissen müssen (über Intercom, Text oder Teamspeak). CTR hat vielleicht ein Dutzend Flieger im Holding, die abgebaut werden müssen, und GND ein Dutzend Flieger die raus müssen.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
== Liste möglicher Notfallarten und ihr Handling:&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
=== 1.) Go Around - Durchstarteverfahren  ===&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
*Missed Approach laut Chart&amp;lt;br&amp;gt; &lt;br /&gt;
*Individuelles Handling z.B bestimmte Kursanweisung und Höhe&lt;br /&gt;
&lt;br /&gt;
=== 2.) Rejected Takoff - Startabbruch  ===&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &lt;br /&gt;
&lt;br /&gt;
=== 3.) Radio Communication Failure - Funkausfall  ===&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist. &lt;br /&gt;
&lt;br /&gt;
=== 4.) Loss of ILS, NDB, VOR - Ausfall von Anflughilfen  ===&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &lt;br /&gt;
&lt;br /&gt;
=== 5.) Loss of Cabinpressure - Druckabfall  ===&lt;br /&gt;
&lt;br /&gt;
Dies ist ein Fall, der unangenehm werden könnte für den ATCO bei Hightraffic. Der Pilot wird einen sogenannten &amp;quot;Emergencydescent&amp;quot; einleiten (FL100 or below). Als ATCO ihn so schnell wie nur möglich auf dem eigenen Flughafen landen lassen oder ihn auf einen Ausweichflughafen landen lassen. Wichtig dabei ist, dass der ATCO dem Emergencyflieger nicht zutextet und niederquaselt, sondern der Pilot wird sagen, was er tun wird und ATC wird das bestmögliche tun um ihn das zu gewährleisten. Es kann auch vorkommen, dass der Pilot sagt &amp;quot;ATC standby&amp;quot;, d.h. der ATCO soll diesen Flieger bis auf weiteres nicht ansprechen, außer die Situation wird noch gefährlicher durch z.B. crossing Traffic below. Koordination ist in diesem Fall das A &amp;amp;amp; O! &lt;br /&gt;
&lt;br /&gt;
=== 6.) Loss of Hydraulicpressure - Verlust der Hydraulik  ===&lt;br /&gt;
&lt;br /&gt;
Wenn diese Art von Verlust kommt, dann ist meistens die Aircraftperformance (stark) beeinträchtigt. Wichtig hierbei ist zu Erfahren, inwieweit der Pilot die Kontrolle über seinen Flieger noch hat, d.h. Descentrate/Turnrate erfragen oder ob es andere Probleme gibt. Auch kann es dazukommen, dass der Pilot nur mehr Links oder Rechtskurvene fliegen kann. Auch hier sollte man im Hinterkopf haben, dass sich so eine Situation zu einem noch größeren Notfall entwickeln kann. Den betroffenen Flieger so schnell wie nur möglich auf den Boden bringen - Seperation zu den umliegenden Fliegern erhöhen. &lt;br /&gt;
&lt;br /&gt;
=== 7.) Prioritylanding - Dringlichkeitslandung  ===&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
=== 8.) Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Diese Art von Notfall setzt großes Wissen von Notfällen vorraus, da dies eine sehr anspruchsvolle Prozedur ist. Die beste Art diese Situation zu handeln ist, die Übersicht nicht zu verlieren und den Piloten mit wertvollen Informationen zu &amp;quot;versorgen&amp;quot;, d.h. DME Angabe zum Airport, Speed, Altitude, Heading, zu hoch/tief, Trafficinformation,... Alles in allem ist dies ein &amp;quot;Talk-Down-Approach&amp;quot; indem der ATCO wirklich stark gefordert wird in Sachen Konzentration &amp;amp;amp; Koordination. Diese Informationen sollten nicht nur einmal gegeben werden, sonder wirklich beinahe im Minutentakt. Wichig dabei ist wieder, dass der Flieger so schnell als wie nur möglich am Zielflughafen landen sollte, wenn möglich sogar auf einer eigenen Piste, sodass er den anderen anfliegenden Verkehr nicht behindert. Seperation sollte wieder stark erhöht werden zu umliegenden Fluzeugen, falls nötig sogar Warteverfahren aufbauen. &lt;br /&gt;
&lt;br /&gt;
=== 9.) Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Triebwerksversagen beim&amp;amp;nbsp;Start gehört zu den gefährlichsten Zwischenfällen, die es gibt. Die Höhe über Grund ist niedrig, das Flugzeug läuft auch&amp;amp;nbsp;Hochtouren, die Fluggeschwindigkeit ist niedrig (und damit auch die Stabilität). Knappe Koordination ist hier das A und O. Meist passiert der Vogelschlag noch in Bodennähe nach der v1:&amp;amp;nbsp;Der Flieger kann nicht mehr stoppen und muss in die Luft. Der Mayday-call erreicht also meistens noch den&amp;amp;nbsp;TWR controller. Noch dazu variiert die Schwere der Situation nach dem Grad der Schäden, und das ist nicht immer gleich ersichtlich. Professionalität bei&amp;amp;nbsp;Pilot und TWR&amp;amp;nbsp;controller sind sehr wichtig, damit eine heile Landung gelingt.[http://www.youtube.com/watch?v=9KhZwsYtNDE Folgende Aufnahme ]ist ein&amp;amp;nbsp;Schulbeispiel, wie es gut funktioniert:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;So präzise wie möglich:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Antwort ATC:&amp;amp;nbsp;So präzise wie möglich (merke:&amp;amp;nbsp;Tomson hat keinen request geäussert, also braucht er auch gerade nichts):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warnt andere Stationen, und wartet. Der Pilot ist &amp;quot;in command&amp;quot;, er wird sich schon melden. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Der Pilot hat sich gemeldet. Jetzt macht ATC Angebote. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Jetzt sagt der Pilot, was er vorhat: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial &lt;br /&gt;
towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower liest nur zurück und fertig. Wenn der Pilot nichts will, lässt du ihn in Ruhe. Etwas später macht Manchester noch das Angebot, in Liverpool zu landen - das wird abgelehnt. Noch etwas später meldet Manchester Tower, dass die Landebahn 06R wegen Verschmutzung gesperrt ist - die havarierte Maschine hat Teile verloren (das muss er tun - braucht es doch die Maschine für den&amp;amp;nbsp;Landeanflug). Die Maschine landet kurze Zeit später geordnet und sicher. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*dieser Abschnitt wartet noch auf Vervollständigung&lt;br /&gt;
&lt;br /&gt;
=== 10.) Engine Failure at approach - Triebwerksversagen beim Landeanflug&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
dieser Abschnitt wartet noch auf Vervollständigung &lt;br /&gt;
&lt;br /&gt;
=== 11.) Runway closure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Diese Prozedur wird vom Fluglotsen im TWR ausgelöst. Es gibt zwei Unterschiede: &lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''Wenn die Landebahn nicht mehr benützbar ist (Havarierter Flieger, Flugzeugteile, Tiere, ...), dann ist eine Sperre der Landebahn sofort wirksam:&lt;br /&gt;
&lt;br /&gt;
#Anfliegende Flieger bekommen go-around &lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi clearances zu dieser rwy zu geben &lt;br /&gt;
#Neue Landebahn wird geöffnet (oder Flughafen wird geschlossen) &lt;br /&gt;
#ATIS wird angepasst.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Step-by-step &amp;lt;/span&amp;gt;'''closure:''' Wenn der Grund des Schließens abzusehen ist (Wind dreht langsam, noise abatement rules, ...), dann geht die Schließung der Landebahn mit mehr Ordnung vor sich:&lt;br /&gt;
&lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi Clearances zu dieser rwy zu geben &lt;br /&gt;
#verbleibende anfliegende Flugzeuge bekommen Landefreigabe &lt;br /&gt;
#neue Landebahn wird geöffnet &lt;br /&gt;
#ATIS wird angepasst &lt;br /&gt;
#APP und GND werden informiert.&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1744</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1744"/>
		<updated>2012-03-10T20:23:23Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergancys and abnormal procedures come from two directions: from the pilots or the ATC- depending where acactly they occur. If a pilot gets into troubble than he decleares emergency. If for example the runway is blocked (damaged aircraft, animals etc.) than the ATC reports abnormal procedures to the surrounding stations. &lt;br /&gt;
&lt;br /&gt;
== Drei Typen von Notfällen, die der/die PilotIn anmeldet:  ==&lt;br /&gt;
&lt;br /&gt;
=== PAN&amp;amp;nbsp;(Panne)  ===&lt;br /&gt;
&lt;br /&gt;
Wenn einem Flugzeug einzelne Systeme ausfallen, die ihn nicht in ernste Gefahr bringen, aber dazu bringen könnten, dass er seinen Flug nicht &amp;quot;normal&amp;quot; fortsetzen kann, dann ist dies eine Pannenmeldung.&amp;amp;nbsp;Dazu zählt der Klassiker &amp;quot;low fuel&amp;quot;, aber auch Ausfälle von nicht-vitalen&amp;amp;nbsp;Systemen wie z.B. FMC, VOR receiver oder speedbrakes. Der Flieger kann normal weiter fliegen und üblicherweise auch regulär landen, aber er kann bestimmte Flugmanöver nicht durchführen (ohne VOR receiver geht z.B. kein ILS-Anflug, ohne FMC ist &amp;quot;direct WW380&amp;quot; nicht möglich. &lt;br /&gt;
&lt;br /&gt;
Für den Piloten heisst das:&amp;amp;nbsp;Anmelden der Panne, und was für ihn daraus folgt. &lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123:&amp;amp;nbsp;Pan-pan-pan, Laipzich Air 123, low fuel, requesting CDA to&amp;amp;nbsp;Vienna.&lt;br /&gt;
LOWW_APP:&amp;amp;nbsp;Leipzig Air 123, pan message received, direct WW380, descent 4000ft at own discretion, QNH 1033.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
APP wird danach in diesem Beispiel zweierlei tun: &lt;br /&gt;
&lt;br /&gt;
*Er wird ins Textfeld eine Notiz schreiben, damit die anderen Controller bescheid wissen (z.B. &amp;quot;low fuel&amp;quot;). Damit weiss TWR, dass &amp;quot;go-around&amp;quot; gefährlich sein kann. &lt;br /&gt;
*Er wird den&amp;amp;nbsp;Flieger im&amp;amp;nbsp;Auge behalten, andere Flieger auf Kollisionskurs ablenken, erhöhte Separation sicherstellen und darauf achten, dass das Flugzeug kontinuierlich sinken kann.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;''PAN ist nur eine Meldung:&amp;amp;nbsp;Der Flieger fliegt &amp;quot;normal&amp;quot; weiter.&amp;amp;nbsp;ATC berücksichtigt nur, dass er zu bestimmten Manövern evtl. nicht in der Lage ist.''&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
=== Radio communication&amp;amp;nbsp;Failure  ===&lt;br /&gt;
&lt;br /&gt;
Dazu gibt es weiter unten einen [http://wiki.vacc-austria.org/index.php?title=Emergency_Handling#3..29_Radio_Communication_Failure_-_Funkausfall eigenen&amp;amp;nbsp;Abschnitt.] &lt;br /&gt;
&lt;br /&gt;
=== Mayday - ein wirklicher Notfall.  ===&lt;br /&gt;
&lt;br /&gt;
Wenn ein Pilot einen Zustand bemerkt, die ihm das Weiterfliegen verunmöglichen und das Flugzeug oder Insassen in Gefahr bringen, dann kommt das drastischere Mittel: Der Notruf. Er hat folgende Phasen: &lt;br /&gt;
&lt;br /&gt;
==== 1) Ausrufen des Notfalls durch den Piloten:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Der Pilot meldet sich mit dreimal &amp;quot;mayday&amp;quot;, seinem&amp;amp;nbsp;Callsign, seiner Notlage, was er jetzt tut, und was er jetzt braucht. &lt;br /&gt;
&lt;br /&gt;
Der ATC bestätigt den Ruf (readback), fordert ihn auf, den&amp;amp;nbsp;Transponder auf 7700 zu stellen&amp;amp;nbsp;(das erscheint gleich auf allen ATC-Radarschirmen) und gibt ihm eine schnelle Antwort. &lt;br /&gt;
&lt;br /&gt;
==== 2) &amp;quot;Einrichten&amp;quot; im Notfall:  ====&lt;br /&gt;
&lt;br /&gt;
Der Pilot hat nun einige Sekunden zu tun (seinen bedepschten Vogel auf 20° zu drehen und zu stabilisieren), und der ATC auch:&amp;amp;nbsp;Er muss die anderen Piloten auf der Frequenz informieren, und seine angrenzenden&amp;amp;nbsp;Sektoren, und den Flughafen, zu dem es runter geht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Mit dieser Meldung wissen die Piloten:&amp;amp;nbsp;Sie fliegen ihre Verfahren ungerührt weiter:&amp;amp;nbsp;ihre&amp;amp;nbsp;Routen, ihre SID und STAR, ihre Transitions. Sie melden sich bei ATC nur, wenn es ihre Sicherheit erfordert. Wenn sie Anweisungen vom&amp;amp;nbsp;ATC bekommen, dann lesen sie diese nicht zurück. &lt;br /&gt;
&lt;br /&gt;
Dann wird ATC sich über intercom, Text oder Teamspeak mit den anderen ATC in Verbindung setzen und sie über den&amp;amp;nbsp;Notfall informieren, und was für sie daraus folgt: &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
In der Regel sorgt der Controller als erstes dafür, dass er keinen zusätzlichen&amp;amp;nbsp;Traffic mehr übergeben bekommt, und dass sein&amp;amp;nbsp;Flieger heil weiter kommt. &lt;br /&gt;
&lt;br /&gt;
Ab diesem Punkt gibt es keine festgesetzte Phraseologie mehr. Der ATC spricht so mit dem Piloten, dass er am besten serviciert wird. &lt;br /&gt;
&lt;br /&gt;
Mit dieser Information sich der ATC z.B. wieder an den Piloten wenden und die nächsten Schritte klären:&amp;amp;nbsp;Die konkrete Betroffenheit, und wo er landen kann. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, maintain present heading.&lt;br /&gt;
          When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Die ersten Informationen sind auch für VATSIM-Controller wichtig:&amp;amp;nbsp;Was konkret ist kaputt, und was tut der Pilot gerade? Die letzte Info ist auf VATSIM untergeordnet - sie dient in der Realität dazu, den Umfang der Rettungsmaßnahmen abzuschätzen. &lt;br /&gt;
&lt;br /&gt;
==== 3) Alle weiteren Maßnahmen richten sich an folgenden Gesichtspunkten:  ====&lt;br /&gt;
&lt;br /&gt;
*'''Der Pilot sagt, was er braucht, der ATC liefert's. '''Nicht zu&amp;amp;nbsp;Unrecht steht in den Flugplänen&amp;amp;nbsp;&amp;quot;PIC&amp;quot; - pilot in command. Der Pilot kommandiert seine Maschine auch dann, wenn sie ihm auseinanderfällt. ATC ist der Partner, der ihn dabei unterstützt. ATC schafft niemals dem Piloten an, was er tun soll. &lt;br /&gt;
*'''Kommunikation mit dem Piloten:&amp;amp;nbsp;So wenig wie möglich, so viel wie nötig, so präzise wie möglich'''. Bei Notfällen geht's zu im Cockpit. Warntöne piepsen, Warnmeldungen verlauten, Checklisten werden durchgegangen, Lage wird besprochen. Je mehr Zeit die PilotInnen für sich haben, umso besser. Wenn ein/e PilotIn nicht antwortet:&amp;amp;nbsp;nur die Ruhe. Er/sie befolgt (hoffentlich) die Regel:&amp;amp;nbsp;1-avigate, 2-navigate, 3-communicate, und ist noch nicht bei Stufe 3 angekommen. &lt;br /&gt;
*'''&amp;quot;Ausräumen&amp;quot; des restlichen Flugraums:'''&amp;amp;nbsp;Niemand muss abdrehen oder in eine Holding, der nicht im&amp;amp;nbsp;Weg ist. Anderer traffic kann also weitergehen, sofern er die Notfall-Operation nicht stört. Wenn er stört, dann ist möglich: ILS-Freigabe und weg von der Frequenz, direct holding, oder frühzeitige Übergabe (z.B. an CTR) nach&amp;amp;nbsp;Absprache. &lt;br /&gt;
*'''Der Pilot hat die Wahl der Frequenz:''' ob er an anderen ATC übergeben wird (z.B.&amp;amp;nbsp;TWR), oder auf der Frequenz bleibt und bis auf den&amp;amp;nbsp;Boden gebracht wird.TWR kann sich für die Landefreigabe zB auf die Frequenz von APP dazuhängen, damit der Pilot nicht Frequenz wechseln muss.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''&amp;quot;Mayday&amp;quot; ist ein Notfall, der absolute Priorität hat. Nur der Beginn des Verfahrens ist normiert:&amp;amp;nbsp;Ausrufen durch den Piloten, Bestätigung durch&amp;amp;nbsp;ATC, Information der anderen Piloten und anderen ATC. Dann kommunizieren Pilot und ATC, wie es am günstigsten ist. Aufgabe des ATC ist, den Luftraum und die Funkfrequenz möglichst frei zu halten.''&amp;lt;br&amp;gt; &amp;lt;/blockquote&amp;gt; &lt;br /&gt;
==== 4)&amp;amp;nbsp;Notfallprozedur beenden  ====&lt;br /&gt;
&lt;br /&gt;
Irgendwann ist die Notfallprozedur auch beendet und der Flieger glücklich auf der Runway oder unglücklich im Wald. Dann müssen alle anderen wissen, dass die Notfallprozedur beendet ist und alles normal weitergeht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Hinzu kommt, dass die anderen ATC davon wissen müssen (über Intercom, Text oder Teamspeak). CTR hat vielleicht ein Dutzend Flieger im Holding, die abgebaut werden müssen, und GND ein Dutzend Flieger die raus müssen.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
== Liste möglicher Notfallarten und ihr Handling:&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
=== 1.) Go Around - Durchstarteverfahren  ===&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
*Missed Approach laut Chart&amp;lt;br&amp;gt; &lt;br /&gt;
*Individuelles Handling z.B bestimmte Kursanweisung und Höhe&lt;br /&gt;
&lt;br /&gt;
=== 2.) Rejected Takoff - Startabbruch  ===&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &lt;br /&gt;
&lt;br /&gt;
=== 3.) Radio Communication Failure - Funkausfall  ===&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist. &lt;br /&gt;
&lt;br /&gt;
=== 4.) Loss of ILS, NDB, VOR - Ausfall von Anflughilfen  ===&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &lt;br /&gt;
&lt;br /&gt;
=== 5.) Loss of Cabinpressure - Druckabfall  ===&lt;br /&gt;
&lt;br /&gt;
Dies ist ein Fall, der unangenehm werden könnte für den ATCO bei Hightraffic. Der Pilot wird einen sogenannten &amp;quot;Emergencydescent&amp;quot; einleiten (FL100 or below). Als ATCO ihn so schnell wie nur möglich auf dem eigenen Flughafen landen lassen oder ihn auf einen Ausweichflughafen landen lassen. Wichtig dabei ist, dass der ATCO dem Emergencyflieger nicht zutextet und niederquaselt, sondern der Pilot wird sagen, was er tun wird und ATC wird das bestmögliche tun um ihn das zu gewährleisten. Es kann auch vorkommen, dass der Pilot sagt &amp;quot;ATC standby&amp;quot;, d.h. der ATCO soll diesen Flieger bis auf weiteres nicht ansprechen, außer die Situation wird noch gefährlicher durch z.B. crossing Traffic below. Koordination ist in diesem Fall das A &amp;amp;amp; O! &lt;br /&gt;
&lt;br /&gt;
=== 6.) Loss of Hydraulicpressure - Verlust der Hydraulik  ===&lt;br /&gt;
&lt;br /&gt;
Wenn diese Art von Verlust kommt, dann ist meistens die Aircraftperformance (stark) beeinträchtigt. Wichtig hierbei ist zu Erfahren, inwieweit der Pilot die Kontrolle über seinen Flieger noch hat, d.h. Descentrate/Turnrate erfragen oder ob es andere Probleme gibt. Auch kann es dazukommen, dass der Pilot nur mehr Links oder Rechtskurvene fliegen kann. Auch hier sollte man im Hinterkopf haben, dass sich so eine Situation zu einem noch größeren Notfall entwickeln kann. Den betroffenen Flieger so schnell wie nur möglich auf den Boden bringen - Seperation zu den umliegenden Fliegern erhöhen. &lt;br /&gt;
&lt;br /&gt;
=== 7.) Prioritylanding - Dringlichkeitslandung  ===&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
=== 8.) Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Diese Art von Notfall setzt großes Wissen von Notfällen vorraus, da dies eine sehr anspruchsvolle Prozedur ist. Die beste Art diese Situation zu handeln ist, die Übersicht nicht zu verlieren und den Piloten mit wertvollen Informationen zu &amp;quot;versorgen&amp;quot;, d.h. DME Angabe zum Airport, Speed, Altitude, Heading, zu hoch/tief, Trafficinformation,... Alles in allem ist dies ein &amp;quot;Talk-Down-Approach&amp;quot; indem der ATCO wirklich stark gefordert wird in Sachen Konzentration &amp;amp;amp; Koordination. Diese Informationen sollten nicht nur einmal gegeben werden, sonder wirklich beinahe im Minutentakt. Wichig dabei ist wieder, dass der Flieger so schnell als wie nur möglich am Zielflughafen landen sollte, wenn möglich sogar auf einer eigenen Piste, sodass er den anderen anfliegenden Verkehr nicht behindert. Seperation sollte wieder stark erhöht werden zu umliegenden Fluzeugen, falls nötig sogar Warteverfahren aufbauen. &lt;br /&gt;
&lt;br /&gt;
=== 9.) Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Triebwerksversagen beim&amp;amp;nbsp;Start gehört zu den gefährlichsten Zwischenfällen, die es gibt. Die Höhe über Grund ist niedrig, das Flugzeug läuft auch&amp;amp;nbsp;Hochtouren, die Fluggeschwindigkeit ist niedrig (und damit auch die Stabilität). Knappe Koordination ist hier das A und O. Meist passiert der Vogelschlag noch in Bodennähe nach der v1:&amp;amp;nbsp;Der Flieger kann nicht mehr stoppen und muss in die Luft. Der Mayday-call erreicht also meistens noch den&amp;amp;nbsp;TWR controller. Noch dazu variiert die Schwere der Situation nach dem Grad der Schäden, und das ist nicht immer gleich ersichtlich. Professionalität bei&amp;amp;nbsp;Pilot und TWR&amp;amp;nbsp;controller sind sehr wichtig, damit eine heile Landung gelingt.[http://www.youtube.com/watch?v=9KhZwsYtNDE Folgende Aufnahme ]ist ein&amp;amp;nbsp;Schulbeispiel, wie es gut funktioniert:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;So präzise wie möglich:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Antwort ATC:&amp;amp;nbsp;So präzise wie möglich (merke:&amp;amp;nbsp;Tomson hat keinen request geäussert, also braucht er auch gerade nichts):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warnt andere Stationen, und wartet. Der Pilot ist &amp;quot;in command&amp;quot;, er wird sich schon melden. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Der Pilot hat sich gemeldet. Jetzt macht ATC Angebote. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Jetzt sagt der Pilot, was er vorhat: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial &lt;br /&gt;
towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower liest nur zurück und fertig. Wenn der Pilot nichts will, lässt du ihn in Ruhe. Etwas später macht Manchester noch das Angebot, in Liverpool zu landen - das wird abgelehnt. Noch etwas später meldet Manchester Tower, dass die Landebahn 06R wegen Verschmutzung gesperrt ist - die havarierte Maschine hat Teile verloren (das muss er tun - braucht es doch die Maschine für den&amp;amp;nbsp;Landeanflug). Die Maschine landet kurze Zeit später geordnet und sicher. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*dieser Abschnitt wartet noch auf Vervollständigung&lt;br /&gt;
&lt;br /&gt;
=== 10.) Engine Failure at approach - Triebwerksversagen beim Landeanflug&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
dieser Abschnitt wartet noch auf Vervollständigung &lt;br /&gt;
&lt;br /&gt;
=== 11.) Runway closure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Diese Prozedur wird vom Fluglotsen im TWR ausgelöst. Es gibt zwei Unterschiede: &lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''Wenn die Landebahn nicht mehr benützbar ist (Havarierter Flieger, Flugzeugteile, Tiere, ...), dann ist eine Sperre der Landebahn sofort wirksam:&lt;br /&gt;
&lt;br /&gt;
#Anfliegende Flieger bekommen go-around &lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi clearances zu dieser rwy zu geben &lt;br /&gt;
#Neue Landebahn wird geöffnet (oder Flughafen wird geschlossen) &lt;br /&gt;
#ATIS wird angepasst.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Step-by-step &amp;lt;/span&amp;gt;'''closure:''' Wenn der Grund des Schließens abzusehen ist (Wind dreht langsam, noise abatement rules, ...), dann geht die Schließung der Landebahn mit mehr Ordnung vor sich:&lt;br /&gt;
&lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi Clearances zu dieser rwy zu geben &lt;br /&gt;
#verbleibende anfliegende Flugzeuge bekommen Landefreigabe &lt;br /&gt;
#neue Landebahn wird geöffnet &lt;br /&gt;
#ATIS wird angepasst &lt;br /&gt;
#APP und GND werden informiert.&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1743</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1743"/>
		<updated>2012-03-10T20:13:22Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergancys and abnormal procedures Notfälle und abnormale Prozeduren kommen von zwei&amp;amp;nbsp;Seiten Vom Piloten oder vom&amp;amp;nbsp;ATC - je nachdem, bei wem sie auftreten. Wenn ein Flieger in Schwierigkeiten gerät, dann meldet der Pilot den&amp;amp;nbsp;Notfall an. Wenn z.B. die Runway blockiert ist (havariertes Flugzeug/Fahrzeug), dann ist es der ATC. Dann gibt es noch&amp;amp;nbsp;Fälle, die bei beiden auftreten können. &lt;br /&gt;
&lt;br /&gt;
== Drei Typen von Notfällen, die der/die PilotIn anmeldet:  ==&lt;br /&gt;
&lt;br /&gt;
=== PAN&amp;amp;nbsp;(Panne)  ===&lt;br /&gt;
&lt;br /&gt;
Wenn einem Flugzeug einzelne Systeme ausfallen, die ihn nicht in ernste Gefahr bringen, aber dazu bringen könnten, dass er seinen Flug nicht &amp;quot;normal&amp;quot; fortsetzen kann, dann ist dies eine Pannenmeldung.&amp;amp;nbsp;Dazu zählt der Klassiker &amp;quot;low fuel&amp;quot;, aber auch Ausfälle von nicht-vitalen&amp;amp;nbsp;Systemen wie z.B. FMC, VOR receiver oder speedbrakes. Der Flieger kann normal weiter fliegen und üblicherweise auch regulär landen, aber er kann bestimmte Flugmanöver nicht durchführen (ohne VOR receiver geht z.B. kein ILS-Anflug, ohne FMC ist &amp;quot;direct WW380&amp;quot; nicht möglich. &lt;br /&gt;
&lt;br /&gt;
Für den Piloten heisst das:&amp;amp;nbsp;Anmelden der Panne, und was für ihn daraus folgt. &lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123:&amp;amp;nbsp;Pan-pan-pan, Laipzich Air 123, low fuel, requesting CDA to&amp;amp;nbsp;Vienna.&lt;br /&gt;
LOWW_APP:&amp;amp;nbsp;Leipzig Air 123, pan message received, direct WW380, descent 4000ft at own discretion, QNH 1033.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
APP wird danach in diesem Beispiel zweierlei tun: &lt;br /&gt;
&lt;br /&gt;
*Er wird ins Textfeld eine Notiz schreiben, damit die anderen Controller bescheid wissen (z.B. &amp;quot;low fuel&amp;quot;). Damit weiss TWR, dass &amp;quot;go-around&amp;quot; gefährlich sein kann. &lt;br /&gt;
*Er wird den&amp;amp;nbsp;Flieger im&amp;amp;nbsp;Auge behalten, andere Flieger auf Kollisionskurs ablenken, erhöhte Separation sicherstellen und darauf achten, dass das Flugzeug kontinuierlich sinken kann.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;''PAN ist nur eine Meldung:&amp;amp;nbsp;Der Flieger fliegt &amp;quot;normal&amp;quot; weiter.&amp;amp;nbsp;ATC berücksichtigt nur, dass er zu bestimmten Manövern evtl. nicht in der Lage ist.''&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
=== Radio communication&amp;amp;nbsp;Failure  ===&lt;br /&gt;
&lt;br /&gt;
Dazu gibt es weiter unten einen [http://wiki.vacc-austria.org/index.php?title=Emergency_Handling#3..29_Radio_Communication_Failure_-_Funkausfall eigenen&amp;amp;nbsp;Abschnitt.] &lt;br /&gt;
&lt;br /&gt;
=== Mayday - ein wirklicher Notfall.  ===&lt;br /&gt;
&lt;br /&gt;
Wenn ein Pilot einen Zustand bemerkt, die ihm das Weiterfliegen verunmöglichen und das Flugzeug oder Insassen in Gefahr bringen, dann kommt das drastischere Mittel: Der Notruf. Er hat folgende Phasen: &lt;br /&gt;
&lt;br /&gt;
==== 1) Ausrufen des Notfalls durch den Piloten:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Der Pilot meldet sich mit dreimal &amp;quot;mayday&amp;quot;, seinem&amp;amp;nbsp;Callsign, seiner Notlage, was er jetzt tut, und was er jetzt braucht. &lt;br /&gt;
&lt;br /&gt;
Der ATC bestätigt den Ruf (readback), fordert ihn auf, den&amp;amp;nbsp;Transponder auf 7700 zu stellen&amp;amp;nbsp;(das erscheint gleich auf allen ATC-Radarschirmen) und gibt ihm eine schnelle Antwort. &lt;br /&gt;
&lt;br /&gt;
==== 2) &amp;quot;Einrichten&amp;quot; im Notfall:  ====&lt;br /&gt;
&lt;br /&gt;
Der Pilot hat nun einige Sekunden zu tun (seinen bedepschten Vogel auf 20° zu drehen und zu stabilisieren), und der ATC auch:&amp;amp;nbsp;Er muss die anderen Piloten auf der Frequenz informieren, und seine angrenzenden&amp;amp;nbsp;Sektoren, und den Flughafen, zu dem es runter geht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, all stations, emergency in progress. [no calls, no readbacks].&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Mit dieser Meldung wissen die Piloten:&amp;amp;nbsp;Sie fliegen ihre Verfahren ungerührt weiter:&amp;amp;nbsp;ihre&amp;amp;nbsp;Routen, ihre SID und STAR, ihre Transitions. Sie melden sich bei ATC nur, wenn es ihre Sicherheit erfordert. Wenn sie Anweisungen vom&amp;amp;nbsp;ATC bekommen, dann lesen sie diese nicht zurück. &lt;br /&gt;
&lt;br /&gt;
Dann wird ATC sich über intercom, Text oder Teamspeak mit den anderen ATC in Verbindung setzen und sie über den&amp;amp;nbsp;Notfall informieren, und was für sie daraus folgt: &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
In der Regel sorgt der Controller als erstes dafür, dass er keinen zusätzlichen&amp;amp;nbsp;Traffic mehr übergeben bekommt, und dass sein&amp;amp;nbsp;Flieger heil weiter kommt. &lt;br /&gt;
&lt;br /&gt;
Ab diesem Punkt gibt es keine festgesetzte Phraseologie mehr. Der ATC spricht so mit dem Piloten, dass er am besten serviciert wird. &lt;br /&gt;
&lt;br /&gt;
Mit dieser Information sich der ATC z.B. wieder an den Piloten wenden und die nächsten Schritte klären:&amp;amp;nbsp;Die konkrete Betroffenheit, und wo er landen kann. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, maintain present heading.&lt;br /&gt;
          When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Die ersten Informationen sind auch für VATSIM-Controller wichtig:&amp;amp;nbsp;Was konkret ist kaputt, und was tut der Pilot gerade? Die letzte Info ist auf VATSIM untergeordnet - sie dient in der Realität dazu, den Umfang der Rettungsmaßnahmen abzuschätzen. &lt;br /&gt;
&lt;br /&gt;
==== 3) Alle weiteren Maßnahmen richten sich an folgenden Gesichtspunkten:  ====&lt;br /&gt;
&lt;br /&gt;
*'''Der Pilot sagt, was er braucht, der ATC liefert's. '''Nicht zu&amp;amp;nbsp;Unrecht steht in den Flugplänen&amp;amp;nbsp;&amp;quot;PIC&amp;quot; - pilot in command. Der Pilot kommandiert seine Maschine auch dann, wenn sie ihm auseinanderfällt. ATC ist der Partner, der ihn dabei unterstützt. ATC schafft niemals dem Piloten an, was er tun soll. &lt;br /&gt;
*'''Kommunikation mit dem Piloten:&amp;amp;nbsp;So wenig wie möglich, so viel wie nötig, so präzise wie möglich'''. Bei Notfällen geht's zu im Cockpit. Warntöne piepsen, Warnmeldungen verlauten, Checklisten werden durchgegangen, Lage wird besprochen. Je mehr Zeit die PilotInnen für sich haben, umso besser. Wenn ein/e PilotIn nicht antwortet:&amp;amp;nbsp;nur die Ruhe. Er/sie befolgt (hoffentlich) die Regel:&amp;amp;nbsp;1-avigate, 2-navigate, 3-communicate, und ist noch nicht bei Stufe 3 angekommen. &lt;br /&gt;
*'''&amp;quot;Ausräumen&amp;quot; des restlichen Flugraums:'''&amp;amp;nbsp;Niemand muss abdrehen oder in eine Holding, der nicht im&amp;amp;nbsp;Weg ist. Anderer traffic kann also weitergehen, sofern er die Notfall-Operation nicht stört. Wenn er stört, dann ist möglich: ILS-Freigabe und weg von der Frequenz, direct holding, oder frühzeitige Übergabe (z.B. an CTR) nach&amp;amp;nbsp;Absprache. &lt;br /&gt;
*'''Der Pilot hat die Wahl der Frequenz:''' ob er an anderen ATC übergeben wird (z.B.&amp;amp;nbsp;TWR), oder auf der Frequenz bleibt und bis auf den&amp;amp;nbsp;Boden gebracht wird.TWR kann sich für die Landefreigabe zB auf die Frequenz von APP dazuhängen, damit der Pilot nicht Frequenz wechseln muss.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''&amp;quot;Mayday&amp;quot; ist ein Notfall, der absolute Priorität hat. Nur der Beginn des Verfahrens ist normiert:&amp;amp;nbsp;Ausrufen durch den Piloten, Bestätigung durch&amp;amp;nbsp;ATC, Information der anderen Piloten und anderen ATC. Dann kommunizieren Pilot und ATC, wie es am günstigsten ist. Aufgabe des ATC ist, den Luftraum und die Funkfrequenz möglichst frei zu halten.''&amp;lt;br&amp;gt; &amp;lt;/blockquote&amp;gt; &lt;br /&gt;
==== 4)&amp;amp;nbsp;Notfallprozedur beenden  ====&lt;br /&gt;
&lt;br /&gt;
Irgendwann ist die Notfallprozedur auch beendet und der Flieger glücklich auf der Runway oder unglücklich im Wald. Dann müssen alle anderen wissen, dass die Notfallprozedur beendet ist und alles normal weitergeht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Hinzu kommt, dass die anderen ATC davon wissen müssen (über Intercom, Text oder Teamspeak). CTR hat vielleicht ein Dutzend Flieger im Holding, die abgebaut werden müssen, und GND ein Dutzend Flieger die raus müssen.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
== Liste möglicher Notfallarten und ihr Handling:&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
=== 1.) Go Around - Durchstarteverfahren  ===&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
*Missed Approach laut Chart&amp;lt;br&amp;gt; &lt;br /&gt;
*Individuelles Handling z.B bestimmte Kursanweisung und Höhe&lt;br /&gt;
&lt;br /&gt;
=== 2.) Rejected Takoff - Startabbruch  ===&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &lt;br /&gt;
&lt;br /&gt;
=== 3.) Radio Communication Failure - Funkausfall  ===&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist. &lt;br /&gt;
&lt;br /&gt;
=== 4.) Loss of ILS, NDB, VOR - Ausfall von Anflughilfen  ===&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &lt;br /&gt;
&lt;br /&gt;
=== 5.) Loss of Cabinpressure - Druckabfall  ===&lt;br /&gt;
&lt;br /&gt;
Dies ist ein Fall, der unangenehm werden könnte für den ATCO bei Hightraffic. Der Pilot wird einen sogenannten &amp;quot;Emergencydescent&amp;quot; einleiten (FL100 or below). Als ATCO ihn so schnell wie nur möglich auf dem eigenen Flughafen landen lassen oder ihn auf einen Ausweichflughafen landen lassen. Wichtig dabei ist, dass der ATCO dem Emergencyflieger nicht zutextet und niederquaselt, sondern der Pilot wird sagen, was er tun wird und ATC wird das bestmögliche tun um ihn das zu gewährleisten. Es kann auch vorkommen, dass der Pilot sagt &amp;quot;ATC standby&amp;quot;, d.h. der ATCO soll diesen Flieger bis auf weiteres nicht ansprechen, außer die Situation wird noch gefährlicher durch z.B. crossing Traffic below. Koordination ist in diesem Fall das A &amp;amp;amp; O! &lt;br /&gt;
&lt;br /&gt;
=== 6.) Loss of Hydraulicpressure - Verlust der Hydraulik  ===&lt;br /&gt;
&lt;br /&gt;
Wenn diese Art von Verlust kommt, dann ist meistens die Aircraftperformance (stark) beeinträchtigt. Wichtig hierbei ist zu Erfahren, inwieweit der Pilot die Kontrolle über seinen Flieger noch hat, d.h. Descentrate/Turnrate erfragen oder ob es andere Probleme gibt. Auch kann es dazukommen, dass der Pilot nur mehr Links oder Rechtskurvene fliegen kann. Auch hier sollte man im Hinterkopf haben, dass sich so eine Situation zu einem noch größeren Notfall entwickeln kann. Den betroffenen Flieger so schnell wie nur möglich auf den Boden bringen - Seperation zu den umliegenden Fliegern erhöhen. &lt;br /&gt;
&lt;br /&gt;
=== 7.) Prioritylanding - Dringlichkeitslandung  ===&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
=== 8.) Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Diese Art von Notfall setzt großes Wissen von Notfällen vorraus, da dies eine sehr anspruchsvolle Prozedur ist. Die beste Art diese Situation zu handeln ist, die Übersicht nicht zu verlieren und den Piloten mit wertvollen Informationen zu &amp;quot;versorgen&amp;quot;, d.h. DME Angabe zum Airport, Speed, Altitude, Heading, zu hoch/tief, Trafficinformation,... Alles in allem ist dies ein &amp;quot;Talk-Down-Approach&amp;quot; indem der ATCO wirklich stark gefordert wird in Sachen Konzentration &amp;amp;amp; Koordination. Diese Informationen sollten nicht nur einmal gegeben werden, sonder wirklich beinahe im Minutentakt. Wichig dabei ist wieder, dass der Flieger so schnell als wie nur möglich am Zielflughafen landen sollte, wenn möglich sogar auf einer eigenen Piste, sodass er den anderen anfliegenden Verkehr nicht behindert. Seperation sollte wieder stark erhöht werden zu umliegenden Fluzeugen, falls nötig sogar Warteverfahren aufbauen. &lt;br /&gt;
&lt;br /&gt;
=== 9.) Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Triebwerksversagen beim&amp;amp;nbsp;Start gehört zu den gefährlichsten Zwischenfällen, die es gibt. Die Höhe über Grund ist niedrig, das Flugzeug läuft auch&amp;amp;nbsp;Hochtouren, die Fluggeschwindigkeit ist niedrig (und damit auch die Stabilität). Knappe Koordination ist hier das A und O. Meist passiert der Vogelschlag noch in Bodennähe nach der v1:&amp;amp;nbsp;Der Flieger kann nicht mehr stoppen und muss in die Luft. Der Mayday-call erreicht also meistens noch den&amp;amp;nbsp;TWR controller. Noch dazu variiert die Schwere der Situation nach dem Grad der Schäden, und das ist nicht immer gleich ersichtlich. Professionalität bei&amp;amp;nbsp;Pilot und TWR&amp;amp;nbsp;controller sind sehr wichtig, damit eine heile Landung gelingt.[http://www.youtube.com/watch?v=9KhZwsYtNDE Folgende Aufnahme ]ist ein&amp;amp;nbsp;Schulbeispiel, wie es gut funktioniert:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;So präzise wie möglich:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Thomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Antwort ATC:&amp;amp;nbsp;So präzise wie möglich (merke:&amp;amp;nbsp;Tomson hat keinen request geäussert, also braucht er auch gerade nichts):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Thomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warnt andere Stationen, und wartet. Der Pilot ist &amp;quot;in command&amp;quot;, er wird sich schon melden. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Der Pilot hat sich gemeldet. Jetzt macht ATC Angebote. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Jetzt sagt der Pilot, was er vorhat: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radial &lt;br /&gt;
towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower liest nur zurück und fertig. Wenn der Pilot nichts will, lässt du ihn in Ruhe. Etwas später macht Manchester noch das Angebot, in Liverpool zu landen - das wird abgelehnt. Noch etwas später meldet Manchester Tower, dass die Landebahn 06R wegen Verschmutzung gesperrt ist - die havarierte Maschine hat Teile verloren (das muss er tun - braucht es doch die Maschine für den&amp;amp;nbsp;Landeanflug). Die Maschine landet kurze Zeit später geordnet und sicher. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*dieser Abschnitt wartet noch auf Vervollständigung&lt;br /&gt;
&lt;br /&gt;
=== 10.) Engine Failure at approach - Triebwerksversagen beim Landeanflug&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
dieser Abschnitt wartet noch auf Vervollständigung &lt;br /&gt;
&lt;br /&gt;
=== 11.) Runway closure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Diese Prozedur wird vom Fluglotsen im TWR ausgelöst. Es gibt zwei Unterschiede: &lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''Wenn die Landebahn nicht mehr benützbar ist (Havarierter Flieger, Flugzeugteile, Tiere, ...), dann ist eine Sperre der Landebahn sofort wirksam:&lt;br /&gt;
&lt;br /&gt;
#Anfliegende Flieger bekommen go-around &lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi clearances zu dieser rwy zu geben &lt;br /&gt;
#Neue Landebahn wird geöffnet (oder Flughafen wird geschlossen) &lt;br /&gt;
#ATIS wird angepasst.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Step-by-step &amp;lt;/span&amp;gt;'''closure:''' Wenn der Grund des Schließens abzusehen ist (Wind dreht langsam, noise abatement rules, ...), dann geht die Schließung der Landebahn mit mehr Ordnung vor sich:&lt;br /&gt;
&lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi Clearances zu dieser rwy zu geben &lt;br /&gt;
#verbleibende anfliegende Flugzeuge bekommen Landefreigabe &lt;br /&gt;
#neue Landebahn wird geöffnet &lt;br /&gt;
#ATIS wird angepasst &lt;br /&gt;
#APP und GND werden informiert.&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1742</id>
		<title>Emergency procedures</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Emergency_procedures&amp;diff=1742"/>
		<updated>2012-03-10T20:02:44Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: Created page with &amp;quot;= General  =  Emergancys and abnormal procedures Notfälle und abnormale Prozeduren kommen von zwei&amp;amp;nbsp;Seiten Vom Piloten oder vom&amp;amp;nbsp;ATC - je nachdem, bei wem sie auftreten....&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Emergancys and abnormal procedures Notfälle und abnormale Prozeduren kommen von zwei&amp;amp;nbsp;Seiten Vom Piloten oder vom&amp;amp;nbsp;ATC - je nachdem, bei wem sie auftreten. Wenn ein Flieger in Schwierigkeiten gerät, dann meldet der Pilot den&amp;amp;nbsp;Notfall an. Wenn z.B. die Runway blockiert ist (havariertes Flugzeug/Fahrzeug), dann ist es der ATC. Dann gibt es noch&amp;amp;nbsp;Fälle, die bei beiden auftreten können. &lt;br /&gt;
&lt;br /&gt;
== Drei Typen von Notfällen, die der/die PilotIn anmeldet:  ==&lt;br /&gt;
&lt;br /&gt;
=== PAN&amp;amp;nbsp;(Panne)  ===&lt;br /&gt;
&lt;br /&gt;
Wenn einem Flugzeug einzelne Systeme ausfallen, die ihn nicht in ernste Gefahr bringen, aber dazu bringen könnten, dass er seinen Flug nicht &amp;quot;normal&amp;quot; fortsetzen kann, dann ist dies eine Pannenmeldung.&amp;amp;nbsp;Dazu zählt der Klassiker &amp;quot;low fuel&amp;quot;, aber auch Ausfälle von nicht-vitalen&amp;amp;nbsp;Systemen wie z.B. FMC, VOR receiver oder speedbrakes. Der Flieger kann normal weiter fliegen und üblicherweise auch regulär landen, aber er kann bestimmte Flugmanöver nicht durchführen (ohne VOR receiver geht z.B. kein ILS-Anflug, ohne FMC ist &amp;quot;direct WW380&amp;quot; nicht möglich. &lt;br /&gt;
&lt;br /&gt;
Für den Piloten heisst das:&amp;amp;nbsp;Anmelden der Panne, und was für ihn daraus folgt. &lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123:&amp;amp;nbsp;Pan-pan-pan, Laipzich Air 123, low fuel, requesting CDA to&amp;amp;nbsp;Vienna.&lt;br /&gt;
LOWW_APP:&amp;amp;nbsp;Leipzig Air 123, pan message received, direct WW380, descent 4000ft at own discretion, QNH 1033.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
APP wird danach in diesem Beispiel zweierlei tun: &lt;br /&gt;
&lt;br /&gt;
*Er wird ins Textfeld eine Notiz schreiben, damit die anderen Controller bescheid wissen (z.B. &amp;quot;low fuel&amp;quot;). Damit weiss TWR, dass &amp;quot;go-around&amp;quot; gefährlich sein kann. &lt;br /&gt;
*Er wird den&amp;amp;nbsp;Flieger im&amp;amp;nbsp;Auge behalten, andere Flieger auf Kollisionskurs ablenken, erhöhte Separation sicherstellen und darauf achten, dass das Flugzeug kontinuierlich sinken kann.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;''PAN ist nur eine Meldung:&amp;amp;nbsp;Der Flieger fliegt &amp;quot;normal&amp;quot; weiter.&amp;amp;nbsp;ATC berücksichtigt nur, dass er zu bestimmten Manövern evtl. nicht in der Lage ist.''&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
=== Radio communication&amp;amp;nbsp;Failure  ===&lt;br /&gt;
&lt;br /&gt;
Dazu gibt es weiter unten einen [http://wiki.vacc-austria.org/index.php?title=Emergency_Handling#3..29_Radio_Communication_Failure_-_Funkausfall eigenen&amp;amp;nbsp;Abschnitt.] &lt;br /&gt;
&lt;br /&gt;
=== Mayday - ein wirklicher Notfall.  ===&lt;br /&gt;
&lt;br /&gt;
Wenn ein Pilot einen Zustand bemerkt, die ihm das Weiterfliegen verunmöglichen und das Flugzeug oder Insassen in Gefahr bringen, dann kommt das drastischere Mittel: Der Notruf. Er hat folgende Phasen: &lt;br /&gt;
&lt;br /&gt;
==== 1) Ausrufen des Notfalls durch den Piloten:  ====&lt;br /&gt;
&amp;lt;pre&amp;gt;LHA123: Mayday, mayday, mayday. Laipzich Air 123 engine failure. Descending below FL240, Request vectors to nearest suitable airfield.&lt;br /&gt;
LOWW_APP: Leipzig Air 123, mayday call received, engine failure. Squawk 7700. Next airfield is Vienna Airport, turn left 020°, 60 miles.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Der Pilot meldet sich mit dreimal &amp;quot;mayday&amp;quot;, seinem&amp;amp;nbsp;Callsign, seiner Notlage, was er jetzt tut, und was er jetzt braucht. &lt;br /&gt;
&lt;br /&gt;
Der ATC bestätigt den Ruf (readback), fordert ihn auf, den&amp;amp;nbsp;Transponder auf 7700 zu stellen&amp;amp;nbsp;(das erscheint gleich auf allen ATC-Radarschirmen) und gibt ihm eine schnelle Antwort. &lt;br /&gt;
&lt;br /&gt;
==== 2) &amp;quot;Einrichten&amp;quot; im Notfall:  ====&lt;br /&gt;
&lt;br /&gt;
Der Pilot hat nun einige Sekunden zu tun (seinen bedepschten Vogel auf 20° zu drehen und zu stabilisieren), und der ATC auch:&amp;amp;nbsp;Er muss die anderen Piloten auf der Frequenz informieren, und seine angrenzenden&amp;amp;nbsp;Sektoren, und den Flughafen, zu dem es runter geht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency in operation. [no calls, no readbacks].&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Mit dieser Meldung wissen die Piloten:&amp;amp;nbsp;Sie fliegen ihre Verfahren ungerührt weiter:&amp;amp;nbsp;ihre&amp;amp;nbsp;Routen, ihre SID und STAR, ihre Transitions. Sie melden sich bei ATC nur, wenn es ihre Sicherheit erfordert. Wenn sie Anweisungen vom&amp;amp;nbsp;ATC bekommen, dann lesen sie diese nicht zurück. &lt;br /&gt;
&lt;br /&gt;
Dann wird ATC sich über intercom, Text oder Teamspeak mit den anderen ATC in Verbindung setzen und sie über den&amp;amp;nbsp;Notfall informieren, und was für sie daraus folgt: &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP-&amp;amp;gt;LOWW_CTR:&amp;amp;nbsp;mayday LHA123, engine failure, no handoffs&lt;br /&gt;
LOWW_APP-&amp;amp;gt;LOWW_TWR:&amp;amp;nbsp;mayday LHA123 engine failure, request rwys available&lt;br /&gt;
LOWW_TWR-&amp;amp;gt;LOWW_APP: all rwys available, wind 320°6kt&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
In der Regel sorgt der Controller als erstes dafür, dass er keinen zusätzlichen&amp;amp;nbsp;Traffic mehr übergeben bekommt, und dass sein&amp;amp;nbsp;Flieger heil weiter kommt. &lt;br /&gt;
&lt;br /&gt;
Ab diesem Punkt gibt es keine festgesetzte Phraseologie mehr. Der ATC spricht so mit dem Piloten, dass er am besten serviciert wird. &lt;br /&gt;
&lt;br /&gt;
Mit dieser Information sich der ATC z.B. wieder an den Piloten wenden und die nächsten Schritte klären:&amp;amp;nbsp;Die konkrete Betroffenheit, und wo er landen kann. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP: Mayday-Leipzig 123, Vienna reports all runways available, 52 miles to final, maintain present heading.&lt;br /&gt;
          When able, report situation.&lt;br /&gt;
LHA123: Leipzig 123, left engine out, right engine 40%, descending 1800, 48 passengers and 5 crew on board, fuel for 1 hour.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
Die ersten Informationen sind auch für VATSIM-Controller wichtig:&amp;amp;nbsp;Was konkret ist kaputt, und was tut der Pilot gerade? Die letzte Info ist auf VATSIM untergeordnet - sie dient in der Realität dazu, den Umfang der Rettungsmaßnahmen abzuschätzen. &lt;br /&gt;
&lt;br /&gt;
==== 3) Alle weiteren Maßnahmen richten sich an folgenden Gesichtspunkten:  ====&lt;br /&gt;
&lt;br /&gt;
*'''Der Pilot sagt, was er braucht, der ATC liefert's. '''Nicht zu&amp;amp;nbsp;Unrecht steht in den Flugplänen&amp;amp;nbsp;&amp;quot;PIC&amp;quot; - pilot in command. Der Pilot kommandiert seine Maschine auch dann, wenn sie ihm auseinanderfällt. ATC ist der Partner, der ihn dabei unterstützt. ATC schafft niemals dem Piloten an, was er tun soll. &lt;br /&gt;
*'''Kommunikation mit dem Piloten:&amp;amp;nbsp;So wenig wie möglich, so viel wie nötig, so präzise wie möglich'''. Bei Notfällen geht's zu im Cockpit. Warntöne piepsen, Warnmeldungen verlauten, Checklisten werden durchgegangen, Lage wird besprochen. Je mehr Zeit die PilotInnen für sich haben, umso besser. Wenn ein/e PilotIn nicht antwortet:&amp;amp;nbsp;nur die Ruhe. Er/sie befolgt (hoffentlich) die Regel:&amp;amp;nbsp;1-avigate, 2-navigate, 3-communicate, und ist noch nicht bei Stufe 3 angekommen. &lt;br /&gt;
*'''&amp;quot;Ausräumen&amp;quot; des restlichen Flugraums:'''&amp;amp;nbsp;Niemand muss abdrehen oder in eine Holding, der nicht im&amp;amp;nbsp;Weg ist. Anderer traffic kann also weitergehen, sofern er die Notfall-Operation nicht stört. Wenn er stört, dann ist möglich: ILS-Freigabe und weg von der Frequenz, direct holding, oder frühzeitige Übergabe (z.B. an CTR) nach&amp;amp;nbsp;Absprache. &lt;br /&gt;
*'''Der Pilot hat die Wahl der Frequenz:''' ob er an anderen ATC übergeben wird (z.B.&amp;amp;nbsp;TWR), oder auf der Frequenz bleibt und bis auf den&amp;amp;nbsp;Boden gebracht wird.TWR kann sich für die Landefreigabe zB auf die Frequenz von APP dazuhängen, damit der Pilot nicht Frequenz wechseln muss.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;blockquote&amp;gt;''&amp;quot;Mayday&amp;quot; ist ein Notfall, der absolute Priorität hat. Nur der Beginn des Verfahrens ist normiert:&amp;amp;nbsp;Ausrufen durch den Piloten, Bestätigung durch&amp;amp;nbsp;ATC, Information der anderen Piloten und anderen ATC. Dann kommunizieren Pilot und ATC, wie es am günstigsten ist. Aufgabe des ATC ist, den Luftraum und die Funkfrequenz möglichst frei zu halten.''&amp;lt;br&amp;gt; &amp;lt;/blockquote&amp;gt; &lt;br /&gt;
==== 4)&amp;amp;nbsp;Notfallprozedur beenden  ====&lt;br /&gt;
&lt;br /&gt;
Irgendwann ist die Notfallprozedur auch beendet und der Flieger glücklich auf der Runway oder unglücklich im Wald. Dann müssen alle anderen wissen, dass die Notfallprozedur beendet ist und alles normal weitergeht. &lt;br /&gt;
&amp;lt;pre&amp;gt;LOWW_APP:&amp;amp;nbsp;All stations, emergency procedures terminated. All operations return to normal.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
*Hinzu kommt, dass die anderen ATC davon wissen müssen (über Intercom, Text oder Teamspeak). CTR hat vielleicht ein Dutzend Flieger in der Holding, die abgebaut werden müssen, und GND ein Dutzend Flieger die raus müssen.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&amp;lt;blockquote&amp;gt;&amp;lt;/blockquote&amp;gt; &lt;br /&gt;
== Liste möglicher Notfallarten und ihr Handling:&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
=== 1.) Go Around - Durchstarteverfahren  ===&lt;br /&gt;
&lt;br /&gt;
Auch ein Durchstartverfahren kann als eine abnormale Prozedur angesehen werden. Je nach Runwaykonfiguration/ SoP/Absprache mit den umliegenden ATC-Stationen können 2 Prozeduren angewandt werden: &lt;br /&gt;
&lt;br /&gt;
*Missed Approach laut Chart&amp;lt;br&amp;gt; &lt;br /&gt;
*Individuelles Handling z.B bestimmte Kursanweisung und Höhe&lt;br /&gt;
&lt;br /&gt;
=== 2.) Rejected Takoff - Startabbruch  ===&lt;br /&gt;
&lt;br /&gt;
Der Startabbruch kann sehr schnell zu einer unangenehmen Situation führen, wenn nicht schnell und vorallem richtig vom ATCO gehandelt/reagiert wird. Sollte ein Startabbruch passieren, dann ist sicherzustellen, dass der anfliegende Verkehr auf die selbe Piste, ein Durchstarteverfahren durchführt. Es sollte nicht darauf vertraut werden, dass der Flieger die Piste sofort verlassen kann. Ist diese erste Maßnahme durchgeführt sollte so schnell wie nur möglich die umliegenden ATCStationen infomiert werden (kurz und prägnant!) und die weitere Vorgangsweise besprechen (anfliegenden Verkehr umleiten, neue Piste,...) bzw. vom Tower festlegen lassen. &lt;br /&gt;
&lt;br /&gt;
=== 3.) Radio Communication Failure - Funkausfall  ===&lt;br /&gt;
&lt;br /&gt;
Einen RCF zu handeln ist prinzipiell nicht schwer, solang man ein paar Punkte im Hinterkopf aufbewahrt. Erkennen kann man diesen Failure an den Buchstaben &amp;quot;RDOF&amp;quot; und an dem SQ 7600. Wichtig ist nun festzustellen, um welche Failure es sich handelt, d.h. kann mich der Pilot noch hören (&amp;quot;if you read SQ ident&amp;quot;) oder ist sein ganzes Funkequipment ausgefallen. Sollte der Pilot den Controller noch hören, dann können die Anweisungen ganz normal kommen wie immer, jedoch sollte dieser Flieger beschleunigt auf dem gewünschten Flughafen landen. Sollte die ganze Funalge ausgefallen sein, dann sollte man als ATCO wissen, wie das sogennante &amp;quot;Radio Communication Failure Procedure&amp;quot; laut Charts aussieht, damit es zu keinen Komplikationen kommt. Auch zu berücksichtigen ist, dass, wenn sich die Pistenkonfiguration geändert hat, der Pilot diese Änderungen nicht mehr mitbekommen kann und deshalb auf der im alten ATIS zugewiesene Piste anfliegt. Wieder die umliegenen ATC-Stationen darüber informieren und dementsprechend handeln. Im Hinterkopf haben, dass sich ein RDOF in einen Emergency (7700) ausarten kann und deshalb die Seperation großzügig berechnen, eventuell Holdings aufbauen bis die Situation bereinigt ist. &lt;br /&gt;
&lt;br /&gt;
=== 4.) Loss of ILS, NDB, VOR - Ausfall von Anflughilfen  ===&lt;br /&gt;
&lt;br /&gt;
Grundsätzlich ist auch ein Ausfall von Anflughilfen nicht problematisch. Wichtig ist hierbei, dass der Trainee die Arten der Anflüge weiss, die der Airport zur Verfügung stellt. Sollte nun das ILS wegen Wartungsarbeiten nicht Verfügbar sein, dann kann gerne auf andere Anflugarten zurückgegriffen werden. Sollten die Wetterbedingungen es erlauben, dürfen auch gerne visuelle Anflüge (in Absprache mit TWR) angeboten werden. &lt;br /&gt;
&lt;br /&gt;
=== 5.) Loss of Cabinpressure - Druckabfall  ===&lt;br /&gt;
&lt;br /&gt;
Dies ist ein Fall, der unangenehm werden könnte für den ATCO bei Hightraffic. Der Pilot wird einen sogenannten &amp;quot;Emergencydescent&amp;quot; einleiten (FL100 or below). Als ATCO ihn so schnell wie nur möglich auf dem eigenen Flughafen landen lassen oder ihn auf einen Ausweichflughafen landen lassen. Wichtig dabei ist, dass der ATCO dem Emergencyflieger nicht zutextet und niederquaselt, sondern der Pilot wird sagen, was er tun wird und ATC wird das bestmögliche tun um ihn das zu gewährleisten. Es kann auch vorkommen, dass der Pilot sagt &amp;quot;ATC standby&amp;quot;, d.h. der ATCO soll diesen Flieger bis auf weiteres nicht ansprechen, außer die Situation wird noch gefährlicher durch z.B. crossing Traffic below. Koordination ist in diesem Fall das A &amp;amp;amp; O! &lt;br /&gt;
&lt;br /&gt;
=== 6.) Loss of Hydraulicpressure - Verlust der Hydraulik  ===&lt;br /&gt;
&lt;br /&gt;
Wenn diese Art von Verlust kommt, dann ist meistens die Aircraftperformance (stark) beeinträchtigt. Wichtig hierbei ist zu Erfahren, inwieweit der Pilot die Kontrolle über seinen Flieger noch hat, d.h. Descentrate/Turnrate erfragen oder ob es andere Probleme gibt. Auch kann es dazukommen, dass der Pilot nur mehr Links oder Rechtskurvene fliegen kann. Auch hier sollte man im Hinterkopf haben, dass sich so eine Situation zu einem noch größeren Notfall entwickeln kann. Den betroffenen Flieger so schnell wie nur möglich auf den Boden bringen - Seperation zu den umliegenden Fliegern erhöhen. &lt;br /&gt;
&lt;br /&gt;
=== 7.) Prioritylanding - Dringlichkeitslandung  ===&lt;br /&gt;
&lt;br /&gt;
Wie der Name schon ahnen lässt, handelt es sich hierbei um einen Flieger, der auf dem schnellsten und direktesten Weg von A nach B will. Beispiele wären gesundheitliche Notfälle, Low Fuel (solang kein Emergency ausgesprochen wurde), VIPs on board, Krankentransporte,... &lt;br /&gt;
&lt;br /&gt;
=== 8.) Smoke in Cockpit - Rauch in der Flugkanzel  ===&lt;br /&gt;
&lt;br /&gt;
Diese Art von Notfall setzt großes Wissen von Notfällen vorraus, da dies eine sehr anspruchsvolle Prozedur ist. Die beste Art diese Situation zu handeln ist, die Übersicht nicht zu verlieren und den Piloten mit wertvollen Informationen zu &amp;quot;versorgen&amp;quot;, d.h. DME Angabe zum Airport, Speed, Altitude, Heading, zu hoch/tief, Trafficinformation,... Alles in allem ist dies ein &amp;quot;Talk-Down-Approach&amp;quot; indem der ATCO wirklich stark gefordert wird in Sachen Konzentration &amp;amp;amp; Koordination. Diese Informationen sollten nicht nur einmal gegeben werden, sonder wirklich beinahe im Minutentakt. Wichig dabei ist wieder, dass der Flieger so schnell als wie nur möglich am Zielflughafen landen sollte, wenn möglich sogar auf einer eigenen Piste, sodass er den anderen anfliegenden Verkehr nicht behindert. Seperation sollte wieder stark erhöht werden zu umliegenden Fluzeugen, falls nötig sogar Warteverfahren aufbauen. &lt;br /&gt;
&lt;br /&gt;
=== 9.) Engine Failure at takeoff - Triebwerksversagen beim&amp;amp;nbsp;Start&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Triebwerksversagen beim&amp;amp;nbsp;Start gehört zu den gefährlichsten Zwischenfällen, die es gibt. Die Höhe über Grund ist niedrig, das Flugzeug läuft auch&amp;amp;nbsp;Hochtouren, die Fluggeschwindigkeit ist niedrig (und damit auch die Stabilität). Knappe Koordination ist hier das A und O. Meist passiert der Vogelschlag noch in Bodennähe nach der v1:&amp;amp;nbsp;Der Flieger kann nicht mehr stoppen und muss in die Luft. Der Mayday-call erreicht also meistens noch den&amp;amp;nbsp;TWR controller. Noch dazu variiert die Schwere der Situation nach dem Grad der Schäden, und das ist nicht immer gleich ersichtlich. Professionalität bei&amp;amp;nbsp;Pilot und TWR&amp;amp;nbsp;controller sind sehr wichtig, damit eine heile Landung gelingt.[http://www.youtube.com/watch?v=9KhZwsYtNDE Folgende Aufnahme ]ist ein&amp;amp;nbsp;Schulbeispiel, wie es gut funktioniert:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Mayday call:&amp;amp;nbsp;So präzise wie möglich:&amp;amp;nbsp;Mayday, callsign, problem, intentions, request &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft: Mayday mayday mayday Tomson 253H, engine failure, continuing northwesterly, inbound towards Wallasey.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
2. Antwort ATC:&amp;amp;nbsp;So präzise wie möglich (merke:&amp;amp;nbsp;Tomson hat keinen request geäussert, also braucht er auch gerade nichts):&amp;amp;nbsp; &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR: Tomson 253H, roger, all runways are available for landing, surface wind 070° at 5 knots.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
3. ATC warnt andere Stationen, und wartet. Der Pilot ist &amp;quot;in command&amp;quot;, er wird sich schon melden. &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, Mayday 253H&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
4. Der Pilot hat sich gemeldet. Jetzt macht ATC Angebote. &lt;br /&gt;
&amp;lt;pre&amp;gt;TWR:&amp;amp;nbsp;Mayday 253H, all runways are available. If you wish, vectors, or continue visually for 06 left or right.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
5. Jetzt sagt der Pilot, was er vorhat: &lt;br /&gt;
&amp;lt;pre&amp;gt;Acft:&amp;amp;nbsp;Manchester, we are heading in a northwesterly direction and trying to establish on the 85° inbound radio &lt;br /&gt;
towards Wallacy, climb to 3500 ft and then advise you about our further intentions.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
6. Manchester Tower liest nur zurück und fertig. Wenn der Pilot nichts will, lässt du ihn in Ruhe. Etwas später macht Manchester noch das Angebot, in Liverpool zu landen - das wird abgelehnt. Noch etwas später meldet Manchester Tower, dass die Landebahn 06R wegen Verschmutzung gesperrt ist - die havarierte Maschine hat Teile verloren (das muss er tun - braucht es doch die Maschine für den&amp;amp;nbsp;Landeanflug). Die Maschine landet kurze Zeit später geordnet und sicher. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*dieser Abschnitt wartet noch auf Vervollständigung&lt;br /&gt;
&lt;br /&gt;
=== 10.) Engine Failure at approach - Triebwerksversagen beim Landeanflug&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
dieser Abschnitt wartet noch auf Vervollständigung &lt;br /&gt;
&lt;br /&gt;
=== 11.) Runway closure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
Diese Prozedur wird vom Fluglotsen im TWR ausgelöst. Es gibt zwei Unterschiede: &lt;br /&gt;
&lt;br /&gt;
*'''Immediate closure:&amp;amp;nbsp;'''Wenn die Landebahn nicht mehr benützbar ist (Havarierter Flieger, Flugzeugteile, Tiere, ...), dann ist eine Sperre der Landebahn sofort wirksam:&lt;br /&gt;
&lt;br /&gt;
#Anfliegende Flieger bekommen go-around &lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi clearances zu dieser rwy zu geben &lt;br /&gt;
#Neue Landebahn wird geöffnet (oder Flughafen wird geschlossen) &lt;br /&gt;
#ATIS wird angepasst.&lt;br /&gt;
&lt;br /&gt;
*&amp;lt;span style=&amp;quot;font-weight: bold;&amp;quot;&amp;gt;Step-by-step &amp;lt;/span&amp;gt;'''closure:''' Wenn der Grund des Schließens abzusehen ist (Wind dreht langsam, noise abatement rules, ...), dann geht die Schließung der Landebahn mit mehr Ordnung vor sich:&lt;br /&gt;
&lt;br /&gt;
#APP bekommt Information, keine Flugzeuge zuzuführen &lt;br /&gt;
#GND bekommt Information, keine Taxi Clearances zu dieser rwy zu geben &lt;br /&gt;
#verbleibende anfliegende Flugzeuge bekommen Landefreigabe &lt;br /&gt;
#neue Landebahn wird geöffnet &lt;br /&gt;
#ATIS wird angepasst &lt;br /&gt;
#APP und GND werden informiert.&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Over_the_shoulder&amp;diff=1727</id>
		<title>Over the shoulder</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Over_the_shoulder&amp;diff=1727"/>
		<updated>2012-03-03T23:47:47Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: /* Formal requirements */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
In order to pass your OTS, you need to prove your familiarity with the procedures at Vienna airport, and that you can handle high traffic operations safely. Your mentor and two checkers will monitor your activities and judge upon your skills. If too heavy traffic persists, the examiner may open lower stations. Exams will be taken at our weekly wednesday or special events. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Formal requirements&amp;lt;br&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
#You requested an OTS and your mentor has accepted.&lt;br /&gt;
#Your knowlege of all antecedents is required.&lt;br /&gt;
#Physical and mental fitness at the test.&lt;br /&gt;
#Date arrangement with mentor and TD&lt;br /&gt;
#Passed OTS training&lt;br /&gt;
#Trainee has to arrange &amp;quot;standby positions&amp;quot;&lt;br /&gt;
#Empirically between 70 and 200 hours on the tested station&lt;br /&gt;
#Station booked&amp;amp;nbsp;by trainee on our [http://vacc-austria.org homepage]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Formal procedure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
#Pre-briefing with checkers on teamspeak 30 minutes prior to test &lt;br /&gt;
#Man the testing station &lt;br /&gt;
#Announcement of test start &lt;br /&gt;
#Accomplishing the test within 90 minutes or less &lt;br /&gt;
#Announcment of test end &lt;br /&gt;
#Checker's decision finding &lt;br /&gt;
#Feedback to trainee&lt;br /&gt;
&lt;br /&gt;
*Please note, in case of unforseen events or major faults, checkers may abort the OTS session.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Examination contents&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
===== Student 2&amp;lt;br&amp;gt;  =====&lt;br /&gt;
&lt;br /&gt;
#Runway configuration&amp;lt;br&amp;gt; &lt;br /&gt;
#Runway separation&amp;lt;br&amp;gt; &lt;br /&gt;
#Separation on ground&amp;lt;br&amp;gt; &lt;br /&gt;
#LVP&amp;lt;br&amp;gt; &lt;br /&gt;
#VFR and IFR&amp;amp;nbsp;phraseology&amp;lt;br&amp;gt; &lt;br /&gt;
#Emergency and lost comm procedures&amp;lt;br&amp;gt; &lt;br /&gt;
#Situation awareness and priority sequence&amp;lt;br&amp;gt; &lt;br /&gt;
#METAR /&amp;amp;nbsp;TAF&amp;lt;br&amp;gt; &lt;br /&gt;
#ATIS&amp;lt;br&amp;gt; &lt;br /&gt;
#Influance of the QNH for the transition altitude and transition level&amp;lt;br&amp;gt; &lt;br /&gt;
#Traffic and weather information&amp;lt;br&amp;gt; &lt;br /&gt;
#Missed approach and go arround procedures&amp;lt;br&amp;gt; &lt;br /&gt;
#Coordination with other ATC stations &lt;br /&gt;
#Inhibit of runway(s) and or taxiways&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Student 3&amp;lt;br&amp;gt;  =====&lt;br /&gt;
&lt;br /&gt;
#Flight rule changes&amp;lt;br&amp;gt; &lt;br /&gt;
#SID /&amp;amp;nbsp;STAR&amp;amp;nbsp;cancellation&amp;lt;br&amp;gt; &lt;br /&gt;
#Situation awareness and priority sequence&amp;lt;br&amp;gt; &lt;br /&gt;
#Seperation&amp;lt;br&amp;gt; &lt;br /&gt;
#Sequencing&amp;lt;br&amp;gt; &lt;br /&gt;
#LVP&amp;lt;br&amp;gt; &lt;br /&gt;
#Emergency and lost comm procedures&amp;lt;br&amp;gt; &lt;br /&gt;
#Holding management&amp;lt;br&amp;gt; &lt;br /&gt;
#Speedlimits&amp;lt;br&amp;gt; &lt;br /&gt;
#Traffic and weather information&amp;lt;br&amp;gt; &lt;br /&gt;
#LoA&amp;lt;br&amp;gt; &lt;br /&gt;
#Type of approaches&amp;lt;br&amp;gt; &lt;br /&gt;
#Coordination with other ATC stations&amp;lt;br&amp;gt; &lt;br /&gt;
#Missed approach and go arround procedures&amp;lt;br&amp;gt; &lt;br /&gt;
#Inhibit of airports or runways &lt;br /&gt;
#Diversions&lt;br /&gt;
&lt;br /&gt;
*And examination contents for Student 2.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Controller 1&amp;lt;br&amp;gt;  =====&lt;br /&gt;
&lt;br /&gt;
#Situation awareness and priority sequence&amp;lt;br&amp;gt; &lt;br /&gt;
#Coordination with other ATC stations&amp;lt;br&amp;gt; &lt;br /&gt;
#Seperation&amp;lt;br&amp;gt; &lt;br /&gt;
#Traffic and weather information&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*And examination contents for Student 2 and Student 3&lt;br /&gt;
&lt;br /&gt;
----&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Tutorial:%C3%9Cbersicht&amp;diff=1726</id>
		<title>Tutorial:Übersicht</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Tutorial:%C3%9Cbersicht&amp;diff=1726"/>
		<updated>2012-03-03T16:09:20Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: Protected &amp;quot;Tutorial:Übersicht&amp;quot; ([edit=sysop] (indefinite) [move=sysop] (indefinite))&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tutorial: Übersicht | [[Tutorial:Intro]]--&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
= Work in Progress! =&lt;br /&gt;
&lt;br /&gt;
Diese Seiten sind noch in Bau. Sie sind nicht verlinkt - bitte noch nicht für training etc. verwenden! Aktive ControllerInnen sind gerne eingeladen, auszubessern und zu ergänzen. Noch lernende sind auf den derzeit gültigen [[Study Guide]] verwiesen.&lt;br /&gt;
&lt;br /&gt;
= Willkommen im Kreis der Fluglotsen bei der VACC Austria!  =&lt;br /&gt;
&lt;br /&gt;
Dieses Tutorial soll Dir eine Unterstützung für Dein Training sein. Er ist ein Tutorial - eine Lernhilfe, mit der Du Schritt für Schritt in Deine Aufgabe &amp;quot;hineinwächst&amp;quot;. Jede Seite ist ein Lernschritt, und er hat folgenden Aufbau: &lt;br /&gt;
&lt;br /&gt;
#Inhaltsangabe &lt;br /&gt;
#Was kannst Du danach? &lt;br /&gt;
#Lerninhalte inkl. Beispiele &lt;br /&gt;
#Praxisfragen &amp;amp;amp; Antworten &lt;br /&gt;
#weiterführende Links &lt;br /&gt;
#Hinweis auf den nächsten Schritt.&lt;br /&gt;
&lt;br /&gt;
= Übersicht&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Folgende Schritte sind vorgesehen (und in Bau): &lt;br /&gt;
&lt;br /&gt;
#[[Tutorial:Intro]]: Was ist ein Controller? Was tut er/sie? Wie sind Controller organisiert? &lt;br /&gt;
#[[Tutorial:Software]]: Was brauchst Du, um zum ersten mal Online zu gehen und zuzusehen? Software und Konfigurationen &lt;br /&gt;
#[[Tutorial:Theorie 1]]: Was musst Du wissen, bevor Du beginnst: Funksprache, METAR, Lufträume, Flugpläne, Karten undsoweiter. &lt;br /&gt;
#[[Tutorial:DEL]] Dein erster Job: Delivery &lt;br /&gt;
#[[Tutorial:GND]] Bleib am Boden Ground - Bodenkontrolle &lt;br /&gt;
#[[Tutorial:Theorie 2]]: Was du brauchst für den ersten Schritt in die Luft&lt;br /&gt;
#[[Tutorial:TWR]]: Frei zum Abheben: TWR (Tower) &lt;br /&gt;
#[[Tutorial:APP]]: APP und weg: Approach &lt;br /&gt;
#[[Tutorial:CTR]]: im&amp;amp;nbsp;Zentrum: Center&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Hinweise? Grössere Änderungen empfohlen? Bitte einfach in die Diskussionsseite schreiben! Wir schauen es immer mal durch und passen die Inhalte an.&lt;br /&gt;
&lt;br /&gt;
= Intern =&lt;br /&gt;
&lt;br /&gt;
Plan für die Struktur:&lt;br /&gt;
&lt;br /&gt;
# Intro: Was tut ein Controller, welche Grundprinzipien gibts, IFR/VFR, ATC layers, Airspaces Einführung. Ergebnis: Grundlegende Prinzipien.&lt;br /&gt;
# Euroscope: Install &amp;amp; config. Ergebnis: Trainee kann als OBS online gehen.&lt;br /&gt;
# Theory 1: Funksprache, Flugpläne, METAR verstehen, ATIS verstehen. Ergebnis: kann als OBS online verstehen, was los ist.&lt;br /&gt;
# DEL. Ergebnis: Fit für DEL.&lt;br /&gt;
# GND. Ergebnis: Fit für GND.&lt;br /&gt;
# Theory 2: ATIS machen, Airspaces, ... was TWR braucht.&lt;br /&gt;
# TWR. Ergebnis: Fit für TWR.&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
Tutorial: Übersicht | [[Tutorial:Intro]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=How_to_become_a_VACC_Austria_Controller&amp;diff=1618</id>
		<title>How to become a VACC Austria Controller</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=How_to_become_a_VACC_Austria_Controller&amp;diff=1618"/>
		<updated>2012-02-17T16:57:22Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: /* Procedure for accepted controllers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Requirements to become a VACC&amp;amp;nbsp;Austria controller  ===&lt;br /&gt;
&lt;br /&gt;
*The applicant is required to obey the [http://www.vacc-austria.org/page/RULES Rules of VACC Austria].&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Register your VATSIM account  ===&lt;br /&gt;
&lt;br /&gt;
If you are not already a VATSIM member, go to the [http://www.vatsim.net VATSIM&amp;amp;nbsp;Homepage] and create your account. Make sure your account is assigned to [http://www.vateur.org/ VATEUR (Europe) divison] and[http://www.vateud.org VATEUD (Europe without UK and Russia) subdivision]. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Check your VATSIM region assignment  ===&lt;br /&gt;
&lt;br /&gt;
Go to the [https://cert.vatsim.net/vatsimnet/statcheck.html VATSIM&amp;amp;nbsp;Certificate Website], type in your VATSIM&amp;amp;nbsp;ID, press &amp;quot;Lookup&amp;quot; and check if the region shows &amp;quot;Austria&amp;quot;. In case the region is not selected or not correct, send a mail to the [mailto:vateud4@vateud.net VATEUD Membership Director ]and ask to correct the region assignment. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Register at VACC-Austria  ===&lt;br /&gt;
&lt;br /&gt;
If your are not already registered in the VACC-Austria, go to our [http://www.vacc-austria.org Homepage] and create your account.&amp;amp;nbsp;Keep in mind, that the credentials for the VACC-Austria infrastructure differs from your VATSIM account! &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Gather some practice and experience  ===&lt;br /&gt;
&lt;br /&gt;
At this point we strongly recommend that you connect to the network and fly around for several hours to get a feeling on the pilot side and spend some hours at observing active controllers in Austria, as well. Feel free to chat with other pilots and controllers in our [[Teamspeak|Teamspeak]] Voice Chat and share your experience with us in our [http://forum.vacc-austria.org/ Forums]. Remember, the best controllers are also pilots, however, having (virtual) pilot experience is not a requirement but a recommendation from our side. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Apply for controller status  ===&lt;br /&gt;
&lt;br /&gt;
Log into the [http://vacc-austria.org/ VACC-Austria homepage] and select from the menu &amp;quot;member&amp;quot; and select &amp;quot;My Training&amp;quot; (deutschsprachige Mitglieder finden die Bewerbung unter &amp;quot;Mitglied&amp;quot; - &amp;quot;Meine Ausbildung&amp;quot;). In the information form fill out the application. Please give us some details about yourself, your skills, previous experience with flight simulation, phraseology etc. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Procedure for accepted controllers  ===&lt;br /&gt;
&lt;br /&gt;
After your acceptence as a VACC Austria controller, anticipate the contact of your dedicated [[Mentor/trainer|mentor]], for further information. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Over_the_shoulder&amp;diff=1595</id>
		<title>Over the shoulder</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Over_the_shoulder&amp;diff=1595"/>
		<updated>2012-02-11T23:02:27Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: /* Formal procedure */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
In order to pass your OTS, you need to prove your familiarity with the procedures at Vienna airport, and that you can handle high traffic operations safely. Your mentor and two checkers will monitor your activities and judge upon your skills. If too heavy traffic persists, the examiner may open lower stations. Exams will be taken at our weekly wednesday or special events. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Formal requirements&amp;lt;br&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
#You requested an OTS and your mentor has accepted.&lt;br /&gt;
#Your knowlege of all antecedents is required.&lt;br /&gt;
#Physical and mental fitness at the test.&lt;br /&gt;
#Date arrangement with mentor and TD&lt;br /&gt;
#Passed OTS training&lt;br /&gt;
#Trainee to arrange &amp;quot;standby positions&amp;quot;&lt;br /&gt;
#Empirically between 70 and 200 hours on the tested station&lt;br /&gt;
#Station booked&amp;amp;nbsp;by trainee on our [http://vacc-austria.org homepage]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Formal procedure&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
#Pre-briefing with checkers on teamspeak 30 minutes prior to test &lt;br /&gt;
#Man the testing station &lt;br /&gt;
#Announcement of test start &lt;br /&gt;
#Accomplishing the test within 90 minutes or less &lt;br /&gt;
#Announcment of test end &lt;br /&gt;
#Checker's decision finding &lt;br /&gt;
#Feedback to trainee&lt;br /&gt;
&lt;br /&gt;
*Please note, in case of unforseen events or major faults, checkers may abort the OTS session.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Examination contents&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
===== Student 2&amp;lt;br&amp;gt;  =====&lt;br /&gt;
&lt;br /&gt;
#Runway configuration&amp;lt;br&amp;gt; &lt;br /&gt;
#Runway separation&amp;lt;br&amp;gt; &lt;br /&gt;
#Separation on ground&amp;lt;br&amp;gt; &lt;br /&gt;
#LVP&amp;lt;br&amp;gt; &lt;br /&gt;
#VFR and IFR&amp;amp;nbsp;phraseology&amp;lt;br&amp;gt; &lt;br /&gt;
#Emergency and lost comm procedures&amp;lt;br&amp;gt; &lt;br /&gt;
#Situation awareness and priority sequence&amp;lt;br&amp;gt; &lt;br /&gt;
#METAR /&amp;amp;nbsp;TAF&amp;lt;br&amp;gt; &lt;br /&gt;
#ATIS&amp;lt;br&amp;gt; &lt;br /&gt;
#Influance of the QNH for the transition altitude and transition level&amp;lt;br&amp;gt; &lt;br /&gt;
#Traffic and weather information&amp;lt;br&amp;gt; &lt;br /&gt;
#Missed approach and go arround procedures&amp;lt;br&amp;gt; &lt;br /&gt;
#Coordination with other ATC stations &lt;br /&gt;
#Inhibit of runway(s) and or taxiways&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Student 3&amp;lt;br&amp;gt;  =====&lt;br /&gt;
&lt;br /&gt;
#Flight rule changes&amp;lt;br&amp;gt; &lt;br /&gt;
#SID /&amp;amp;nbsp;STAR&amp;amp;nbsp;cancellation&amp;lt;br&amp;gt; &lt;br /&gt;
#Situation awareness and priority sequence&amp;lt;br&amp;gt; &lt;br /&gt;
#Seperation&amp;lt;br&amp;gt; &lt;br /&gt;
#Sequencing&amp;lt;br&amp;gt; &lt;br /&gt;
#LVP&amp;lt;br&amp;gt; &lt;br /&gt;
#Emergency and lost comm procedures&amp;lt;br&amp;gt; &lt;br /&gt;
#Holding management&amp;lt;br&amp;gt; &lt;br /&gt;
#Speedlimits&amp;lt;br&amp;gt; &lt;br /&gt;
#Traffic and weather information&amp;lt;br&amp;gt; &lt;br /&gt;
#LoA&amp;lt;br&amp;gt; &lt;br /&gt;
#Type of approaches&amp;lt;br&amp;gt; &lt;br /&gt;
#Coordination with other ATC stations&amp;lt;br&amp;gt; &lt;br /&gt;
#Missed approach and go arround procedures&amp;lt;br&amp;gt; &lt;br /&gt;
#Inhibit of airports or runways &lt;br /&gt;
#Diversions&lt;br /&gt;
&lt;br /&gt;
*And examination contents for Student 2.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
===== Controller 1&amp;lt;br&amp;gt;  =====&lt;br /&gt;
&lt;br /&gt;
#Situation awareness and priority sequence&amp;lt;br&amp;gt; &lt;br /&gt;
#Coordination with other ATC stations&amp;lt;br&amp;gt; &lt;br /&gt;
#Seperation&amp;lt;br&amp;gt; &lt;br /&gt;
#Traffic and weather information&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*And examination contents for Student 2 and Student 3&lt;br /&gt;
&lt;br /&gt;
----&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=How_to_become_a_visiting_controller_in_the_VACC_Austria&amp;diff=1566</id>
		<title>How to become a visiting controller in the VACC Austria</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=How_to_become_a_visiting_controller_in_the_VACC_Austria&amp;diff=1566"/>
		<updated>2012-01-27T22:03:15Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Requirements to become a visiting controller  ===&lt;br /&gt;
&lt;br /&gt;
#The applicant is required to obey the [http://www.vacc-austria.org/page/RULES Rules of VACC Austria]. &lt;br /&gt;
#The applicant is required to hold a permanent Senior Student (S3) or above rating. &lt;br /&gt;
#The applicant must be at least 16 years old. &lt;br /&gt;
#The applicant should have a justified interest in controlling the requested airspace. &lt;br /&gt;
#The applicant is required for at least 10 Hours services in the period of 6 month.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Please note: The right to claim being a visiting controller does not exist. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Register at VACC-Austria  ===&lt;br /&gt;
&lt;br /&gt;
If your are not already registered in the VACC-Austria, go to our [http://www.vacc-austria.org Homepage] and create your account. Keep in mind, that the credentials for the VACC-Austria infrastructure differs from your VATSIM account! &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Gather some practice and experience  ===&lt;br /&gt;
&lt;br /&gt;
At this point we strongly recommend that you connect to the network and fly around our Airports for several hours to get a feeling on the pilot side and spend some hours at observing active controllers in Austria, as well. Feel free to chat with other pilots and controllers in our [[Teamspeak|Teamspeak]] Voice Chat and share your experience with us in our [http://forum.vacc-austria.org/ Forums]. Remember, the best controllers are also pilots, however, having (virtual) pilot experience is not a requirement but a recommendation from our side. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Apply for visting controller status  ===&lt;br /&gt;
&lt;br /&gt;
Log into the [http://vacc-austria.org/ VACC-Austria homepage] and select from the menu &amp;quot;member&amp;quot; and select &amp;quot;My Training&amp;quot; . In the information form fill out the application. Please give us some details about yourself, your skills, previous experience with flight simulation, phraseology etc. It would be nice to read some words about your motivation to apply for an visiting controller status and how much hours you would spend into manning an VACC&amp;amp;nbsp;Austria position per month.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Procedure for accepted visiting controllers  ===&lt;br /&gt;
&lt;br /&gt;
After your acceptence as a visiting controller, anticipate the contact of your dedicated [[Mentor/trainer|mentor]], for further information. &lt;br /&gt;
&lt;br /&gt;
----&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1561</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1561"/>
		<updated>2012-01-27T20:33:33Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport have the following main tasks: &lt;br /&gt;
&lt;br /&gt;
#maintain an orderly flow of traffic &lt;br /&gt;
#provide separation service between aircraft &lt;br /&gt;
#provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Separation  =&lt;br /&gt;
&lt;br /&gt;
=== Vertical separation  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;airspace or 2000 feet above FL290 in non-RVSM&amp;amp;nbsp;airspaces. To fly within RVSM an aircraft must be equipped with: &lt;br /&gt;
&lt;br /&gt;
#2 independent altimeters &lt;br /&gt;
#an autopilot witch must be able to hold an specific altitude &lt;br /&gt;
#min. Mode C transponder&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lateral separation  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Wake turbulence separation  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Takeoff&amp;lt;br&amp;gt; =====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Landing =====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width: 415px; height: 256px;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Preceding aircraft &lt;br /&gt;
! Following aircraft &lt;br /&gt;
! Minimum radar separation&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; | Super &lt;br /&gt;
| Super &lt;br /&gt;
| 4 [[Nautical mile|NM]]&lt;br /&gt;
|-&lt;br /&gt;
| Heavy &lt;br /&gt;
| 6 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 7 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 8 NM&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;3&amp;quot; | Heavy &lt;br /&gt;
| Heavy &lt;br /&gt;
| 4 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| Small &lt;br /&gt;
| &lt;br /&gt;
4 NM &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*Staying on or above leader's glide path&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
the role of Approach Controllers &lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==References==&amp;lt;!-- AnimalBiology56:535. --&amp;gt;&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
http://en.wikipedia.org/wiki/Wake_turbulence&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1560</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1560"/>
		<updated>2012-01-27T20:27:35Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport have the following main tasks: &lt;br /&gt;
&lt;br /&gt;
#maintain an orderly flow of traffic &lt;br /&gt;
#provide separation service between aircraft &lt;br /&gt;
#provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Separation  =&lt;br /&gt;
&lt;br /&gt;
=== Vertical separation  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;airspace or 2000 feet above FL290 in non-RVSM&amp;amp;nbsp;airspaces. To fly within RVSM an aircraft must be equipped with: &lt;br /&gt;
&lt;br /&gt;
#2 independent altimeters &lt;br /&gt;
#an autopilot witch must be able to hold an specific altitude &lt;br /&gt;
#min. Mode C transponder&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lateral separation  ===&lt;br /&gt;
&lt;br /&gt;
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 turbulance separation to find the required distances for the lateral separation. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Wake turbulence separation  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Takeoff&amp;lt;br&amp;gt; =====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Landing =====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width: 415px; height: 256px;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Preceding aircraft &lt;br /&gt;
! Following aircraft &lt;br /&gt;
! Minimum radar separation&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; | Super &lt;br /&gt;
| Super &lt;br /&gt;
| 4 [[Nautical mile|NM]]&lt;br /&gt;
|-&lt;br /&gt;
| Heavy &lt;br /&gt;
| 6 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 7 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 8 NM&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;3&amp;quot; | Heavy &lt;br /&gt;
| Heavy &lt;br /&gt;
| 4 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| Small &lt;br /&gt;
| &lt;br /&gt;
4 NM &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*Staying on or above leader's glide path&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
the role of Approach Controllers &lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==References==&amp;lt;!-- AnimalBiology56:535. --&amp;gt;&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
http://en.wikipedia.org/wiki/Wake_turbulence&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1559</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1559"/>
		<updated>2012-01-27T20:26:01Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport have the following main tasks: &lt;br /&gt;
&lt;br /&gt;
#maintain an orderly flow of traffic &lt;br /&gt;
#provide separation service between aircraft &lt;br /&gt;
#provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Separation  =&lt;br /&gt;
&lt;br /&gt;
=== Vertical separation  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;airspace or 2000 feet above FL290 in non-RVSM&amp;amp;nbsp;airspaces. To fly within RVSM an aircraft must be equipped with: &lt;br /&gt;
&lt;br /&gt;
#2 independent altimeters &lt;br /&gt;
#an autopilot witch must be able to hold an specific altitude &lt;br /&gt;
#min. Mode C transponder&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lateral separation  ===&lt;br /&gt;
&lt;br /&gt;
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 turbulance separation to find the required distances for the lateral separation. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Wake turbulence separation  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Takeoff&amp;lt;br&amp;gt; =====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Landing =====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width: 415px; height: 256px;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Preceding aircraft &lt;br /&gt;
! Following aircraft &lt;br /&gt;
! Minimum radar separation&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; | Super &lt;br /&gt;
| Super &lt;br /&gt;
| 4 [[Nautical mile|NM]]&lt;br /&gt;
|-&lt;br /&gt;
| Heavy &lt;br /&gt;
| 6 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 7 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 8 NM&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;3&amp;quot; | Heavy &lt;br /&gt;
| Heavy &lt;br /&gt;
| 4 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| Small &lt;br /&gt;
| &lt;br /&gt;
4 NM &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===== Staying on or above leader's glide path =====&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
the role of Approach Controllers &lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==References==&amp;lt;!-- AnimalBiology56:535. --&amp;gt;&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
http://en.wikipedia.org/wiki/Wake_turbulence&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1558</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1558"/>
		<updated>2012-01-27T20:24:35Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport have the following main tasks: &lt;br /&gt;
&lt;br /&gt;
#maintain an orderly flow of traffic &lt;br /&gt;
#provide separation service between aircraft &lt;br /&gt;
#provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Separation  =&lt;br /&gt;
&lt;br /&gt;
=== Vertical separation  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;airspace or 2000 feet above FL290 in non-RVSM&amp;amp;nbsp;airspaces. To fly within RVSM an aircraft must be equipped with: &lt;br /&gt;
&lt;br /&gt;
#2 independent altimeters &lt;br /&gt;
#an autopilot witch must be able to hold an specific altitude &lt;br /&gt;
#min. Mode C transponder&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lateral separation  ===&lt;br /&gt;
&lt;br /&gt;
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 turbulance separation to find the required distances for the lateral separation. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Wake turbulence separation  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Takeoff&amp;lt;br&amp;gt; =====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Landing =====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width: 415px; height: 256px;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Preceding aircraft &lt;br /&gt;
! Following aircraft &lt;br /&gt;
! Minimum radar separation&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; | Super &lt;br /&gt;
| Super &lt;br /&gt;
| 4 [[Nautical mile|NM]]&lt;br /&gt;
|-&lt;br /&gt;
| Heavy &lt;br /&gt;
| 6 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 7 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 8 NM&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;3&amp;quot; | Heavy &lt;br /&gt;
| Heavy &lt;br /&gt;
| 4 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| Small &lt;br /&gt;
| &lt;br /&gt;
4 NM &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
===== Staying on or above leader's glide path =====&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
the role of Approach Controllers &lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==References==&amp;lt;!-- AnimalBiology56:535. --&amp;gt;&lt;br /&gt;
{{Reflist}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1557</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1557"/>
		<updated>2012-01-27T20:21:02Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport have the following main tasks: &lt;br /&gt;
&lt;br /&gt;
#maintain an orderly flow of traffic &lt;br /&gt;
#provide separation service between aircraft &lt;br /&gt;
#provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Separation =&lt;br /&gt;
&lt;br /&gt;
=== Vertical separation  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;airspace or 2000 feet above FL290 in non-RVSM&amp;amp;nbsp;airspaces. To fly within RVSM an aircraft must be equipped with:&lt;br /&gt;
&lt;br /&gt;
#2 independent altimeters&lt;br /&gt;
#an autopilot witch must be able to hold an specific altitude&lt;br /&gt;
#min. Mode C transponder&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lateral separation ===&lt;br /&gt;
&lt;br /&gt;
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 turbulance separation to find the required distances for the lateral separation.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Wake turbulence separation  ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
;Takeoff&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
;Landing&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;width: 415px; height: 256px;&amp;quot; class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Preceding aircraft &lt;br /&gt;
! Following aircraft &lt;br /&gt;
! Minimum radar separation&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; | Super &lt;br /&gt;
| Super &lt;br /&gt;
| 4 [[Nautical mile|NM]]&lt;br /&gt;
|-&lt;br /&gt;
| Heavy &lt;br /&gt;
| 6 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 7 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 8 NM&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;3&amp;quot; | Heavy &lt;br /&gt;
| Heavy &lt;br /&gt;
| 4 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| Small &lt;br /&gt;
| &lt;br /&gt;
4 NM &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==  ==&lt;br /&gt;
&lt;br /&gt;
==  ==&lt;br /&gt;
&lt;br /&gt;
==  ==&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1556</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1556"/>
		<updated>2012-01-27T20:19:44Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport have the following main tasks: &lt;br /&gt;
&lt;br /&gt;
#maintain an orderly flow of traffic &lt;br /&gt;
#provide separation service between aircraft &lt;br /&gt;
#provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Separation =&lt;br /&gt;
&lt;br /&gt;
=== Vertical separation  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;airspace or 2000 feet above FL290 in non-RVSM&amp;amp;nbsp;airspaces. To fly within RVSM an aircraft must be equipped with:&lt;br /&gt;
&lt;br /&gt;
#2 independent altimeters&lt;br /&gt;
#an autopilot witch must be able to hold an specific altitude&lt;br /&gt;
#min. Mode C transponder&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lateral separation ===&lt;br /&gt;
&lt;br /&gt;
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 turbulance separation to find the required distances for the lateral separation.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Wake turbulence separation  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
;Takeoff&amp;lt;br&amp;gt;&lt;br /&gt;
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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
;Landing &lt;br /&gt;
;;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width: 415px; height: 256px;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Preceding aircraft &lt;br /&gt;
! Following aircraft &lt;br /&gt;
! Minimum radar separation&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;4&amp;quot; | Super &lt;br /&gt;
| Super &lt;br /&gt;
| 4 [[Nautical mile|NM]]&lt;br /&gt;
|-&lt;br /&gt;
| Heavy &lt;br /&gt;
| 6 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 7 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 8 NM&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=&amp;quot;3&amp;quot; | Heavy &lt;br /&gt;
| Heavy &lt;br /&gt;
| 4 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small &lt;br /&gt;
| 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large &lt;br /&gt;
| Small &lt;br /&gt;
| &lt;br /&gt;
4 NM&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==  ==&lt;br /&gt;
&lt;br /&gt;
==  ==&lt;br /&gt;
&lt;br /&gt;
==  ==&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1555</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1555"/>
		<updated>2012-01-27T20:14:42Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: /* Wake turbulance separation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport have the following main tasks: &lt;br /&gt;
&lt;br /&gt;
#maintain an orderly flow of traffic &lt;br /&gt;
#provide separation service between aircraft &lt;br /&gt;
#provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Separation =&lt;br /&gt;
&lt;br /&gt;
=== Vertical separation  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;airspace or 2000 feet above FL290 in non-RVSM&amp;amp;nbsp;airspaces. To fly within RVSM an aircraft must be equipped with:&lt;br /&gt;
&lt;br /&gt;
#2 independent altimeters&lt;br /&gt;
#an autopilot witch must be able to hold an specific altitude&lt;br /&gt;
#min. Mode C transponder&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lateral separation ===&lt;br /&gt;
&lt;br /&gt;
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 turbulance separation to find the required distances for the lateral separation.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Wake turbulence separation  ===&lt;br /&gt;
&lt;br /&gt;
;Landing&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Preceding aircraft || Following aircraft || Minimum radar separation&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=4 | Super || Super || 4 [[nautical mile|NM]]&lt;br /&gt;
|-&lt;br /&gt;
| Heavy || 6 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large || 7 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small || 8 NM&lt;br /&gt;
|-&lt;br /&gt;
| rowspan=3 | Heavy || Heavy || 4 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large || 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Small || 5 NM&lt;br /&gt;
|-&lt;br /&gt;
| Large || Small || 4 NM&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==  ==&lt;br /&gt;
&lt;br /&gt;
==  ==&lt;br /&gt;
&lt;br /&gt;
==  ==&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1554</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1554"/>
		<updated>2012-01-27T20:11:27Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport have the following main tasks: &lt;br /&gt;
&lt;br /&gt;
#maintain an orderly flow of traffic &lt;br /&gt;
#provide separation service between aircraft &lt;br /&gt;
#provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Separation =&lt;br /&gt;
&lt;br /&gt;
=== Vertical separation  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;airspace or 2000 feet above FL290 in non-RVSM&amp;amp;nbsp;airspaces. To fly within RVSM an aircraft must be equipped with:&lt;br /&gt;
&lt;br /&gt;
#2 independent altimeters&lt;br /&gt;
#an autopilot witch must be able to hold an specific altitude&lt;br /&gt;
#min. Mode C transponder&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lateral separation ===&lt;br /&gt;
&lt;br /&gt;
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 turbulance separation to find the required distances for the lateral separation.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Wake turbulance separation ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==  ==&lt;br /&gt;
&lt;br /&gt;
==  ==&lt;br /&gt;
&lt;br /&gt;
==  ==&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1546</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1546"/>
		<updated>2012-01-27T19:34:57Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport have the following main tasks:&lt;br /&gt;
&lt;br /&gt;
#maintain an orderly flow of traffic&lt;br /&gt;
#provide separation service between aircraft&lt;br /&gt;
#provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1545</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1545"/>
		<updated>2012-01-27T19:18:59Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs  ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1544</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1544"/>
		<updated>2012-01-27T19:16:11Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Usage of directs ===&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;NDB) zu erteilen. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1543</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1543"/>
		<updated>2012-01-27T19:08:16Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts  ===&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1542</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1542"/>
		<updated>2012-01-27T19:07:20Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Vectoring of Aircrafts ===&lt;br /&gt;
&lt;br /&gt;
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 können, 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.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1541</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1541"/>
		<updated>2012-01-27T18:51:33Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft as published.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1540</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1540"/>
		<updated>2012-01-27T18:48:24Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= General radar procedures  =&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;STAR means ''Standard Instrument Arrival'' 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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1539</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1539"/>
		<updated>2012-01-27T18:48:04Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== General radar procedures  ==&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;STAR means ''Standard Instrument Arrival'' 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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1538</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1538"/>
		<updated>2012-01-27T18:46:32Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== General radar procedures  ==&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders  ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen. &lt;br /&gt;
&lt;br /&gt;
===== Mode A  =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode. &lt;br /&gt;
&lt;br /&gt;
===== Mode C  =====&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===== Mode S  =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs. &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Position informations&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Beispiel&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;STAR means ''Standard Instrument Arrival'' 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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1537</id>
		<title>Study Guide: Approach</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:_Approach&amp;diff=1537"/>
		<updated>2012-01-27T18:37:19Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General =&lt;br /&gt;
&lt;br /&gt;
TMA&amp;amp;nbsp;controller includes approach and departure control services associated with a particular airport.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== General radar procedures ==&lt;br /&gt;
&lt;br /&gt;
==== Identifikation mit Hilfe eines Transponders ====&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;nbsp;Verfahren von der Flugverkehrskontrollstelle einen Transpondercode zugewiesen.&lt;br /&gt;
&lt;br /&gt;
===== Mode A =====&lt;br /&gt;
&lt;br /&gt;
Flugzeuge mit Transpondermode A senden nur den zugewiesenen Transpondercode.&lt;br /&gt;
&lt;br /&gt;
===== Mode C =====&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
===== Mode S =====&lt;br /&gt;
&lt;br /&gt;
Transpondermode S übermittelt neben dem Squawk und der Flughöhe zusätzlich das Callsign des Flugzeugs.&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== the role of Approach Controllers  ==&lt;br /&gt;
&lt;br /&gt;
TMA Controllers (S3) includes approach and departure control services associated with a particular airport.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*maintain an orderly flow of traffic&amp;lt;br&amp;gt; &lt;br /&gt;
*provide a separation service between aircraft&amp;lt;br&amp;gt; &lt;br /&gt;
*provide assistance to pilots&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The greatest difference when you are starting you TMA-carreer will be the separation between approaching and departing traffic. &amp;lt;br&amp;gt;There are some separation in your airspace:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*'''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.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
How to maintain visual separation?&amp;lt;br&amp;gt;You may use: &lt;br /&gt;
&lt;br /&gt;
*'''Lateral vectoring'''&amp;amp;nbsp;When issuing a heading to an aircraft, make sure that you are using a direction ending on 0 (zero) or on 5 (five). &lt;br /&gt;
*'''Vertical vectoring:''' climbing or descending. For departing or arriving traffic you also can use a &amp;quot;stop climbing/descending at FLxxx&amp;quot; to avoid a conflict.&amp;lt;br&amp;gt; &lt;br /&gt;
*'''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 &amp;quot;minimum clean&amp;quot; (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.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Phraseology&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
A ...Pilot&amp;lt;br&amp;gt;G...ATC&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Standard clearances for arriving aircraft shall contain the following items, if applicable:&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
1. Aircraft identification&amp;lt;br&amp;gt;2. Designator of assigned STAR&amp;lt;br&amp;gt;3. Runway-in-use, except when part of the STAR description&amp;lt;br&amp;gt;4. Initial level, except when this element is included in the START description and&amp;lt;br&amp;gt;5. Any other necessary instructions or information not contained in the START description, e.g. change of communication&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Type of approach procedure  ====&lt;br /&gt;
&lt;br /&gt;
G: CLEARED / PROCEED VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit) VIA (designator) ARRIVAL&amp;lt;br&amp;gt;G: CLEARED (type of approach) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: CLEARED LOCALIZER APPROACH [RUNWAY (number)] [GLIDE PATH INOPERATIVE]&amp;lt;br&amp;gt;G: CLEARED APPROACH RUNWAY (number)&amp;lt;br&amp;gt;A: REQUEST (type of approach) APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: (type of approach) NOT AVAILABLE DUE (reason) [alternative instructions]&amp;lt;br&amp;gt;A: REQUEST (RNAV plain language designator)&amp;lt;br&amp;gt;G: CLEARED (RNAV plain language designator)&amp;lt;br&amp;gt;G: ARE YOU FAMILIAR WITH (name) APPROACH PROCEDURE [RUNWAY (number)]? &lt;br /&gt;
&lt;br /&gt;
==== Straight-in approach  ====&lt;br /&gt;
&lt;br /&gt;
A: REQUEST STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;G: CLEARED STRAIGHT-IN / DIRECT [type of approach] APPROACH [RUNWAY (number)]&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Approach instructions with radar  ====&lt;br /&gt;
&lt;br /&gt;
G: VECTORING FOR (tpye of pilot interpreted aid) APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VETORING FOR VISUAL APPROACH RUNWAY (number), REPORT FIELD / RUNWAY IN SIGHT&amp;lt;br&amp;gt;G: VECTORING FOR (positioning in the circuit)&amp;lt;br&amp;gt;G: VECTORING FOR SURVEILLANCE RADAR APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: VECTORING FOR PRECISION APPROACH RUNWAY (number)&amp;lt;br&amp;gt;G: (type) APPROACH NOT AVAILABLE DUE (reason) (alternative instructions)&amp;lt;br&amp;gt;G: POSITION (number) MILES FROM (position) / TOUCH DOWN. TURN LEFT / RIGHT HEADING (three digits)&amp;lt;br&amp;gt;G: YOU WILL INTERCEPT (radio aid or track) (distance) FROM (significant point) / TOUCH DOWN&amp;lt;br&amp;gt;A: REQUEST (distance) FINAL&amp;lt;br&amp;gt;G: CLEARED FOR (type) APPROCH RUNWAY (number)&amp;lt;br&amp;gt;G: REPORT ESABLISHED [ON ILS / LOCALIZER / GLIDE PATH]&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON FINAL APPROACH TRACK&amp;lt;br&amp;gt;G: CLOSING FROM LEFT / RIGHT [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [TO INTERCEPT [RIGHT TO LEFT / LEFT TO RIGHT / REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: EXPECT VECTORS ACROSS (localizer or radio aid) (reason)&amp;lt;br&amp;gt;G: THIS TURN WILL TAKE YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: TAKING YOU THROUGH (localizer or radio aid) [reason]&amp;lt;br&amp;gt;G: MAINTAIN (altitude) UNTIL GLIDE PATH INTERCEPTION&amp;lt;br&amp;gt;G: REPORT ESTABLISHED ON GLIDE PATH&amp;lt;br&amp;gt;G: INTERCEPT (localizer or radio aid) [REPORT ESTABLISHED]&amp;lt;br&amp;gt;G: INTERCEPT (radio aid) [LEFT TO RIGHT / RIGHT TO LEFT]&amp;lt;br&amp;gt;G: CLEARED FOR ILS APPROACH RUNWAY (number) LEFT / RIGHT&amp;lt;br&amp;gt;G: YOU HAVE CROSSED THE LOCALIZER. TURN LEFT / RIGHT IMMEDIATELY AND RETURN TO THE LOCALIZER&amp;lt;br&amp;gt;G: ILS RUNWAY (number) LEFT / RIGHT LOCALIZER FREQUENCY IS (number)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES / HEADING (three digits) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPROACH], CLIMB TO (level)&amp;lt;br&amp;gt;G: CLIMB TO (level) IMMEDIATELY TO AVOID TRAFFIC [DEVIATING FROM ADJACENT APPORACH] (further instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Go around  ====&lt;br /&gt;
&lt;br /&gt;
G: GO AROUND IMMEDIATELY (missed approach instruction) (reason)&amp;lt;br&amp;gt;G: IF GOING AROUND (appropriate instructions)&amp;lt;br&amp;gt;G: ARE YOU GOING AROUND?&amp;lt;br&amp;gt;A: GOING AROUND&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Level changes, reports and rates  ====&lt;br /&gt;
&lt;br /&gt;
G: CLIMB / DESCEND&amp;lt;br&amp;gt;- TO (level)&amp;lt;br&amp;gt;- TO AND MAINTAIN BLOCK (level) TO (level)&amp;lt;br&amp;gt;- TO REACH (level) AT / BY (time or significant point)&amp;lt;br&amp;gt;- REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;- AT (number) FEET PER MINUTE [OR GREATER / LESS]&amp;lt;br&amp;gt;G: REQUEST LEVEL / FLIGHT LEVEL / ALTITUDE CHANGE FROM (name of level) [AT (time or significant point)]&amp;lt;br&amp;gt;G: STOP CLIMB / DESCENT AT (level)&amp;lt;br&amp;gt;G: CONTINUE CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCEND [UNTIL PASSING (level)]&amp;lt;br&amp;gt;G: RESUME NORMAL RATE OF CLIMB / DESCENT&amp;lt;br&amp;gt;G: REPORT LEAVING / REACHING / PASSING (level)&amp;lt;br&amp;gt;G: WHEN READY CLIMB / DESCENT TO (level)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT AT (time of significant point)&amp;lt;br&amp;gt;G: EXPEDITE CLIMB / DESCENT UNTIL PASSING (level)&amp;lt;br&amp;gt;A: REQUEST DESCENT AT (time)&amp;lt;br&amp;gt;A: REQUEST ALTITUDE (number FEET) / FLIGHT LEVEL (number) VIA (route) [DUE TO (reason)]&amp;lt;br&amp;gt;A: REQUEST LEVEL CHANGE / CLIMB / DESCENT AT (time / position)&amp;lt;br&amp;gt;G: EXPECT LEVEL CHANGE / CLIMB / DESCENT&amp;lt;br&amp;gt;- FROM (name of unit)&amp;lt;br&amp;gt;- AT (time or position)&amp;lt;br&amp;gt;- AFTER PASSING (position)&amp;lt;br&amp;gt;- IN (number) MINUTES&amp;lt;br&amp;gt;G: IMMEDIATELY&amp;lt;br&amp;gt;G: AFTER PASSING (significant point)&amp;lt;br&amp;gt;G: AT (time or significant point)&amp;lt;br&amp;gt;G: WHEN READY (instructions)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Vectoring  ====&lt;br /&gt;
&lt;br /&gt;
G. LEAVE (significant point) HEADING (three digits) [INBOUND [AT (time)]&amp;lt;br&amp;gt;G: CONTINUE HEADING (three digits)&amp;lt;br&amp;gt;G: CONTINUE PRESENT HEADING&amp;lt;br&amp;gt;G: FLY HEADING (three digits)&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT HEADING (three digits) [reason]&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT (number) DEGREES [reason]&amp;lt;br&amp;gt;G: STOP TURN HEADING (three digits)&amp;lt;br&amp;gt;G: FLY HEADING (three digits), WHEN ABLE PROCEED DIRECT (name) (significant point)&amp;lt;br&amp;gt;G: HEADING IS GOOD&amp;lt;br&amp;gt;G: WHEN ABLE PROCEED DIRECT (position)&amp;lt;br&amp;gt;G: SUGGEST (suggestion)&amp;lt;br&amp;gt;G: IF UNABLE [(alternative instructions)] ADVISE&amp;lt;br&amp;gt;A: UNABLE TO COMPLY (reason)&amp;lt;br&amp;gt;G: VECTORING FOR SPACING / SEPERATION / DELAY&amp;lt;br&amp;gt;G: VECTORING DUE TO TRAFFIC&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION (position of a/c) (specific instructions)&amp;lt;br&amp;gt;G: RESUME OWN NAVIGATION [DIRECT] (significant point) [MAGNETIC TRACK (three digits) DISTANCE (number) MILES]&amp;lt;br&amp;gt;G: MAKE A THREE SIXTY TURN LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: ORBIT LEFT / RIGHT [reason]&amp;lt;br&amp;gt;G: MAKE ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND START AND STOP ALL TURNS ON THE COMMAND “NOW”&amp;lt;br&amp;gt;G: ALL TURNS RATE ONE / RATE HALF (number) DEGREES PER SECOND, EXECUTE ISNTRUCTIONS IMMEDIATELY UPON RECEIPT&amp;lt;br&amp;gt;G: TURN LEFT / RIGHT NOW&amp;lt;br&amp;gt;G: STOP TURN NOW&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Speed instructions:  ====&lt;br /&gt;
&lt;br /&gt;
G: REPORT SPEED&amp;lt;br&amp;gt;G: REPORT INDICATED AIRSPEED / TRUE AIRSPEED / MACH NUMBER&amp;lt;br&amp;gt;A: SPEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN (number) KNOTS / MACH (number) [OR GREATER / LESS] [UNTIL (significant point)]&amp;lt;br&amp;gt;G: DO NOT EXCEED (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: MAINTAIN PRESENT SPEED&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;G: INCREASE / REDUCE SPEED BY (number) KNOTS / MACH (number) [OR GREATER / LESS]&amp;lt;br&amp;gt;A: UNABLE TO COMPLY, INDICATED AIRSPEED WILL BE (number) KNOTS / MACH (number)&amp;lt;br&amp;gt;G: RESUME NORMAL SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM APPROACH SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINIMUM CLEAN SPEED&amp;lt;br&amp;gt;G: REDUCE TO MINUMUM SPEED&amp;lt;br&amp;gt;A: MINUMUM SPEED / MINIMUM CLEAN SPEED / MINIMUM APPROACH SPEED IS (number) KNOTS&amp;lt;br&amp;gt;G: NO [ATC] SPEED RESTRICTIONS&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Flight rules  ====&lt;br /&gt;
&lt;br /&gt;
A: CANCELLING IFR&amp;lt;br&amp;gt;G: IFR CANCELLED AT (time) &lt;br /&gt;
&lt;br /&gt;
A: REQUEST IFR CLEARANCE&amp;lt;br&amp;gt;G: CLEARED TO (clearance limit), VIA (route) (level) (other instructions), IFR [FLIGHT] STARTS AT (position or time) / WHEN REACHING (level) / PASSING (level) / NOW [(instructions)] &lt;br /&gt;
&lt;br /&gt;
G: CLEARED NIGHT VFR&amp;lt;br&amp;gt;G: CLEARED SPECIAL VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= FAQs&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
'''How do I work with STARs and Transitions?'''&amp;lt;br&amp;gt;STAR means ''Standard Instrument Arrival'' 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.&amp;lt;br&amp;gt;Using STARs and Transition simplifies the arrival considerably for both pilots and controllers. By clearing &amp;quot;transition and profile&amp;quot; the pilot has also the clearance for descending as published. So you can expect the track, descend and speed of an aircraft.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''How to use a Holding?'''&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;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.&amp;lt;br&amp;gt;Also every holding has a minimum altitude. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''What does MRVA mean?'''&amp;lt;br&amp;gt;'''M'''inimum '''R'''adar '''V'''ectoring '''A'''ltitude: lowest altitude above MSL that can be used for IFR vectoring&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''When is the best moment for my handoff?'''&amp;lt;br&amp;gt;Out of conflict and as early as possible.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''Which classes of airspace are provided in Austria?''' &lt;br /&gt;
&lt;br /&gt;
*C&amp;amp;nbsp;(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&amp;amp;nbsp;FL195 and inside Special Rules Area (e.g. SRA&amp;amp;nbsp;Wien)&amp;lt;br&amp;gt; &lt;br /&gt;
*D&amp;amp;nbsp;(Delta) controlled airspace, IFR and VFR possible, aircontroll is mandatory. IFR is separated to other IFR and receives traffic information about other VFR;&amp;amp;nbsp;VFR traffic reveives information about other traffic. D in Austria covers space between FL125 and FL195 (CTA) and inside contolled zones and certain SRA. &lt;br /&gt;
*E (Echo) controlled airspace only for IFR; VFR receives information as far as possible. In Austria up to FL125 in inside of certain TCAs ('''T'''erminal '''C'''ontrol '''A'''reas). &lt;br /&gt;
*G&amp;amp;nbsp;(Golf) uncontrolled airspace. Traffic information as far as possible.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''What are Y and Z-flights?'''&amp;lt;br&amp;gt;Basically these are flights with a change between IFR/VFR&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Y starts with IFR, changing to VFR (IFR cancellation)&lt;br /&gt;
&lt;br /&gt;
*Z starts with VFR, changing to IFR (IFR pickup)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= References&amp;lt;br&amp;gt;  =&lt;br /&gt;
&lt;br /&gt;
Information about airspaces and airways can be found here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=127&amp;amp;Itemid=205] &lt;br /&gt;
&lt;br /&gt;
Details about air pressure and altitudes you will find here: [http://www.vateud.net/index.php?option=com_content&amp;amp;view=article&amp;amp;id=126&amp;amp;Itemid=201] &lt;br /&gt;
&lt;br /&gt;
Links for the reference (working) sheets you find at the airport details.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Local Procedures  =&lt;br /&gt;
&lt;br /&gt;
== LOWW  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: &lt;br /&gt;
&lt;br /&gt;
LOWW_APP can be divided into up to six Sectors: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_N_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_S_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_F_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_D_APP &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
LOWW_DEP &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
128.200 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
124.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
129.550 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
119.800 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
132.470 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
118.770 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
GND-FL105 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL105-FL245 &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
1&amp;lt;sup&amp;gt;st&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
2&amp;lt;sup&amp;gt;nd&amp;lt;/sup&amp;gt; Director &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
Departure &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The decision which sectors are used shall be based on traffic Situation. &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 5000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL245 - lateral: see appendix and shown by sectorfile &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR should clear traffic for LOWW STAR. Hand-off 2 minutes before listed waypoints below:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
VIA &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
MASUR &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
BARUG &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL170 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
NIGSI &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
at FL180 &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
*LHCC: approaching traffic is maintaining FL140 over GIGOR&lt;br /&gt;
&lt;br /&gt;
*LZBB: arriving traffic via TOKVA has to maintain FL160 and via REKLU FL180&lt;br /&gt;
&lt;br /&gt;
*LKAA: FL 130 via MIKOV/LEDVA and FL170 via LANUX FL170&lt;br /&gt;
&lt;br /&gt;
'''Departures''' &lt;br /&gt;
&lt;br /&gt;
*via UMBIL, OSPEN, SITNI, LUGIM and MOTIX cleared to FL200.&lt;br /&gt;
&lt;br /&gt;
Those flights are released to LOVV_CTR for further climb within the Release Area South and Release Area West (see Appendix) &lt;br /&gt;
&lt;br /&gt;
*via LANUX, KOVEL, MIKOV, LEDVA cleared FL240 to LKAA_CTR.&lt;br /&gt;
&lt;br /&gt;
*via SASAL, STEIN cleared FL230 to LHCC_CTR&lt;br /&gt;
&lt;br /&gt;
*via ABLOM cleared FL150 (ABLOM FL130 or above) to LZBB_CTR.&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWL: maximum FL160 (hand-off to LOWL_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWG: maximum FL160 (hand-off to LOWG_APP)&lt;br /&gt;
&lt;br /&gt;
*LOWW to LOWS / LOWK / LOWI: if requested FL is above FL160, traffic shall be transferred to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
'''Inbound / Outbound LZIB (Bratislava) and LKTB (Brno)''' &lt;br /&gt;
&lt;br /&gt;
*Inbounds LKTB and LZIB shall be cleared from LOVV_CTR to FL210 and hand-off short before Approach Area Wien.&lt;br /&gt;
&lt;br /&gt;
*Outbounds LKTB and LZIB shall be cleared to FL240 and hand-off to LOVV_CTR.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable FCK__ShowTableBorders&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (KUNET at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL120 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
inbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL110 (MIKOV at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
outbound LKTB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
climbing FL100 &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LOWW to LZIB &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
FL070 (ABLOM at level) &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| &lt;br /&gt;
LZIB to LOWW &lt;br /&gt;
&lt;br /&gt;
| &lt;br /&gt;
6000ft (TOVKA at level) &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Remarks''' &lt;br /&gt;
&lt;br /&gt;
*Coordination regarding procedures not listed in this document shall be done in due time with the respective and responsible ATC unit.&lt;br /&gt;
&lt;br /&gt;
*LOWW_APP may send departing traffic to the last waypoint of the SID without coordination.&lt;br /&gt;
&lt;br /&gt;
*Hand-off for arrivals to LZIB short before MIRLU.&lt;br /&gt;
&lt;br /&gt;
'''Appendix''' &lt;br /&gt;
&lt;br /&gt;
[[Image:LOVV APP.jpg]]&amp;amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWI  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.27 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 11000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*LOC/DME West via KTI FL130 over KTI&lt;br /&gt;
&lt;br /&gt;
*LOC//DME East via RTT 9500ft over RTT&lt;br /&gt;
&lt;br /&gt;
*RNP – RNAV Approach Runway 26: instrumental approach with lower minimas, final also a visual approach. Only on pilot request; different miss-appproach-procedure&lt;br /&gt;
&lt;br /&gt;
*All arrivals are going via AB, finals after AB are always visual&lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
== LOWG  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 119.3 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' There are no STARs in LOWG. Most of the arrival routes ends at GRZ-VOR. After GRAZ normally vectors are used. &lt;br /&gt;
&lt;br /&gt;
*ILS 35C starts at 3300ft. Best way is to intercept at LENIZ at 3500ft.&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 35C: Approach über GRZ-VOR nach DME 7.0 GRZ (heading 147°), danach vector auf final track&lt;br /&gt;
&lt;br /&gt;
*VOR-DME 17C: Approach über GRZ-VOR, starts at D15. GRZ 7000ft, descend profile see chart.&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LHCC_CTR via GOTAR FL150&lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via RADLY FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== LOWK  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 126.825 &lt;br /&gt;
&lt;br /&gt;
Transition Altitude: 7000ft &lt;br /&gt;
&lt;br /&gt;
'''Limits''' &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
'''Arrivals''' &lt;br /&gt;
&lt;br /&gt;
*ILS 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 28&lt;br /&gt;
&lt;br /&gt;
*NDB-DME 10&lt;br /&gt;
&lt;br /&gt;
*Circling 10: Anflug über ILS28, desc. 3000ft, circeling starts at KI&lt;br /&gt;
&lt;br /&gt;
'''hand/over''' &lt;br /&gt;
&lt;br /&gt;
*LJLA_CTR via REKTI FL160&lt;br /&gt;
&lt;br /&gt;
*LOVV_CTR FL160&lt;br /&gt;
&lt;br /&gt;
== &amp;lt;br&amp;gt;LOWS  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 123.720&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL125 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS&amp;amp;nbsp;16 &amp;lt;br&amp;gt;NDB&amp;amp;nbsp;16&amp;amp;nbsp;&amp;lt;br&amp;gt;visual&amp;amp;nbsp;34 &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_S_APP via NAPSA and TRAUN&amp;lt;br&amp;gt;EDDM_CTR via TRAUN&amp;lt;br&amp;gt;rest to LOVV_CTR, all&amp;amp;nbsp;FL120 &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== LOWL  ==&lt;br /&gt;
&lt;br /&gt;
Frequencies: 129.620&amp;lt;br&amp;gt;Transition Altitude: 4000ft &lt;br /&gt;
&lt;br /&gt;
Limits &lt;br /&gt;
&lt;br /&gt;
- vertikal: GND - FL165 &lt;br /&gt;
&lt;br /&gt;
Arrivals &lt;br /&gt;
&lt;br /&gt;
ILS/VOR&amp;amp;nbsp;08 (ILS 08 not in standard FSX)&amp;amp;nbsp;&amp;lt;br&amp;gt;ILS/NDB 26&amp;lt;br&amp;gt;(former RWYs known as 09 and 27) &lt;br /&gt;
&lt;br /&gt;
hand/over &lt;br /&gt;
&lt;br /&gt;
EDDM_CTR via PABSA and TRAUN&amp;lt;br&amp;gt;LKAA_CTR via ADLET&amp;lt;br&amp;gt;rest to LOVV_CTR, all FL160 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;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] &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:Ground&amp;diff=1533</id>
		<title>Study Guide:Ground</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:Ground&amp;diff=1533"/>
		<updated>2012-01-27T18:07:37Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Ground is responsible for all movements of aircraft on ground, except the movements on the runway. Ground takes over responsibility for Delivery if he is not online.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Phraseology&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
==== Start-up clearance&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Start-up clearance can be given if no other aircraft is taxiing behind the starting-up aircraft and if the take-off is expected in 20 minutes or less.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 Austrian 125, start-up approved, (Temperature Minus 3)&lt;br /&gt;
&lt;br /&gt;
==== Push-back clearance&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Push-back clearance can be given if no other aircraft is passing behind and the parking position requires push-back.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 Austrian 125, push-back approved”&lt;br /&gt;
&lt;br /&gt;
==== '''Combination of both phrases'''&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
During low traffic you can use these two phrases together&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 Austrian 125, start(-up) and push(-back) approved&lt;br /&gt;
&lt;br /&gt;
==== Taxi Instructions  ====&lt;br /&gt;
&lt;br /&gt;
The pilot pushes back and starts the aircrafts engines. As soon as he is ready for taxi he will call you: &lt;br /&gt;
&lt;br /&gt;
 AUA125:AUA125, ready for taxi.&lt;br /&gt;
&lt;br /&gt;
Depending on traffic you can give him the taxi instruction to his departure runway: &lt;br /&gt;
&lt;br /&gt;
 GND:AUA125, taxi to holding point Rwy 16 via taxiways Exit 4, L and F, QNH 1019.&lt;br /&gt;
 AUA125:Taxiing to holding point runway 29 via L and F, AUA125.&lt;br /&gt;
&lt;br /&gt;
Sometimes it is necessary to hold an aircraft in front of another taxiway: &lt;br /&gt;
&lt;br /&gt;
 GND:AUA125, hold short of taxiway L.&lt;br /&gt;
 AUA125:Holding short of L, AUA125.&lt;br /&gt;
&lt;br /&gt;
When an aircraft is approaching its assigned holding-point (and clear of possible traffic-conflict) a hand-off to next higher position (i.e. TWR) shall be initiated as soon as possible. &lt;br /&gt;
&lt;br /&gt;
 GND:AUA125, contact now Salzburg Tower on frequency 118.10, bye bye!&lt;br /&gt;
 AUA125:contacting Tower on frequency 118,10 bye!&lt;br /&gt;
&lt;br /&gt;
Air-taxiing is the Movement of a helicopter / VTOL above the surface of an aerodrome, normally in ground effect and at a ground speed of normally less than 20 KT (37 km/h). Please Note: The actual height may vary, and some helicopters may require air-taxiing above 25 FT (8 m) AGL to reduce ground effect turbulence or provide clearance for cargo sling loads. &lt;br /&gt;
&amp;lt;pre&amp;gt;OEATD: request air taxi to Runway 29.&lt;br /&gt;
GND: OEATD, air taxi to Runway 29 via Exit 13 and M.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Ground Traffic Management  ===&lt;br /&gt;
&lt;br /&gt;
To organise the traffic on ground different techniques are available, some of them relying on the pilots seeing each other. Generally you should avoid clearing two aircraft onto crossing pathways, unless you are sure they will never meet each other. To achieve this you should instruct aircraft to hold short of taxiways in the way stated above. Consider the following situation: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| You are the Ground Controller at Vienna Airport. Runways active are 34 for landing and 29 for departure. DLH6KM has vacated rwy 34 and requests taxi to its parking position. LZB421 is ready for taxi at stand 7Q.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 GND:DLH6KM taxi to stand C40 via taxiway D and L.&lt;br /&gt;
 DLH6KM:Taxiing to stand C40 via D and L, DLH6KM.&lt;br /&gt;
 LZB421:Wien ground LZB421 stand 7Q, ready for taxi.&lt;br /&gt;
 GND:LZB421, taxi taxiway W, hold short of taxiway L.&lt;br /&gt;
 LZB421:taxiing via W holding short of L.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| The aircraft are now both approaching the intersection L/W.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 GND:LZB421, give way to the DLH B737 crossing left to right on L, thereafter continue&lt;br /&gt;
 taxi to holding point runway 29 via taxiways Exit 2, M and A1.&lt;br /&gt;
 LZB421:Giving way to the 737 from left to right, then continuing taxi to holding point&lt;br /&gt;
 runway 29 via Exit 2, M and A1.&lt;br /&gt;
&lt;br /&gt;
Of course you have to make sure that this instruction is unambiguous, so there shouldn't be two DLH B737s in the area. Also in low visibility operations this procedure might not work very well, in this case you might have to give the aircraft the instruction to continue taxi when the other aircraft has passed. In some cases it is also useful to let one aircraft follow the other: &lt;br /&gt;
&amp;lt;pre&amp;gt;GND:LZB421, follow the Austrian DASH 8 crossing you right to left on M to holding point runway 29.&lt;br /&gt;
LZB421:following the DASH 8 crossing us right to left on M to holding point runway 29.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intersection departure  ===&lt;br /&gt;
&lt;br /&gt;
Some flights do not need the whole length of their given departure runway so they might request takeoff from an intersection somewhere down the runway. This procedure is called a intersection takeoff. You should only grant this in coordination with Tower and if traffic situation permits. Also at some airports intersections are used to be more flexible in the departure sequence (see section [[Study Guide:Tower#Departure_Seperation_-_Based_on_Type_of_Aircraft_and_departure_route|Departure Seperation]]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Special Situations (High Traffic, Slots, ...)  ===&lt;br /&gt;
&lt;br /&gt;
==== Slots  ====&lt;br /&gt;
&lt;br /&gt;
In case the above mentioned slot regulations are in force ground has the responsibility to set up a departure sequence in a way that the aircraft do not miss their slot. &lt;br /&gt;
&lt;br /&gt;
==== Opposite runway operations  ====&lt;br /&gt;
&lt;br /&gt;
At some austrian airports it is very common to use opposite runway configurations (departure and arrival runway are opposite to each other). In these situations it can happen very fast that you have two aircraft facing each other nose to nose. Special attention should be paid to avoid this situation. &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:Ground&amp;diff=1532</id>
		<title>Study Guide:Ground</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:Ground&amp;diff=1532"/>
		<updated>2012-01-27T18:05:31Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= General  =&lt;br /&gt;
&lt;br /&gt;
Ground is responsible for all movements of aircraft on ground, except the movements on the runway. Ground takes over responsibility for Delivery if he is not online.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Phraseology&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
==== Start-up clearance&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Start-up clearance can be given if no other aircraft is taxiing behind the starting-up aircraft and if the take-off is expected in 20 minutes or less.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 Austrian 125, start-up approved, (Temperature Minus 3)&lt;br /&gt;
&lt;br /&gt;
==== Push-back clearance&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Push-back clearance can be given if no other aircraft is passing behind and the parking position requires push-back.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 Austrian 125, push-back approved”&lt;br /&gt;
&lt;br /&gt;
==== '''Combination of both phrases'''&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
During low traffic you can use these two phrases together&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
 Austrian 125, start(-up) and push(-back) approved&lt;br /&gt;
&lt;br /&gt;
==== Taxi Instructions  ====&lt;br /&gt;
&lt;br /&gt;
The pilot pushes back and starts the aircrafts engines. As soon as he is ready for taxi he will call you: &lt;br /&gt;
&lt;br /&gt;
 AUA125:AUA125, ready for taxi.&lt;br /&gt;
&lt;br /&gt;
Depending on traffic you can give him the taxi instruction to his departure runway: &lt;br /&gt;
&lt;br /&gt;
 GND:AUA125, taxi to holding point Rwy 16 via taxiways Exit 4, L and F, QNH 1019.&lt;br /&gt;
 AUA125:Taxiing to holding point runway 29 via L and F, AUA125.&lt;br /&gt;
&lt;br /&gt;
Sometimes it is necessary to hold an aircraft in front of another taxiway: &lt;br /&gt;
&lt;br /&gt;
 GND:AUA125, hold short of taxiway L.&lt;br /&gt;
 AUA125:Holding short of L, AUA125.&lt;br /&gt;
&lt;br /&gt;
When an aircraft is approaching its assigned holding-point (and clear of possible traffic-conflict) a hand-off to next higher position (i.e. TWR) shall be initiated as soon as possible. &lt;br /&gt;
&lt;br /&gt;
 GND:AUA125, contact now Salzburg Tower on frequency 118.10, bye bye!&lt;br /&gt;
 AUA125:contacting Tower on frequency 118,10 bye!&lt;br /&gt;
&lt;br /&gt;
Air-taxiing is the Movement of a helicopter / VTOL above the surface of an aerodrome, normally in ground effect and at a ground speed of normally less than 20 KT (37 km/h). Please Note: The actual height may vary, and some helicopters may require air-taxiing above 25 FT (8 m) AGL to reduce ground effect turbulence or provide clearance for cargo sling loads. &lt;br /&gt;
&amp;lt;pre&amp;gt;OEATD: request air taxi to Runway 29.&lt;br /&gt;
GND: OEATD, air taxi to Runway 29 via Exit 13 and M.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Ground Traffic Management  ===&lt;br /&gt;
&lt;br /&gt;
To organise the traffic on ground different techniques are available, some of them relying on the pilots seeing each other. Generally you should avoid clearing two aircraft onto crossing pathways, unless you are sure they will never meet each other. To achieve this you should instruct aircraft to hold short of taxiways in the way stated above. Consider the following situation: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| You are the Ground Controller at Vienna Airport. Runways active are 34 for landing and 29 for departure. DLH6KM has vacated rwy 34 and requests taxi to its parking position. LZB421 is ready for taxi at stand 7Q.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 GND:DLH6KM taxi to stand 40 via taxiways D and L, QNH 1019.&lt;br /&gt;
 DLH6KM:Taxiing to stand 40 via D and L, DLH6KM.&lt;br /&gt;
 LZB421:Wien ground LZB421 stand 7Q, ready for taxi.&lt;br /&gt;
 GND:LZB421, taxi taxiway W, hold short of taxiway L.&lt;br /&gt;
 LZB421:taxiing via W holding short of L.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| The aircraft are now both approaching the intersection L/W.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 GND:LZB421, give way to the DLH B737 crossing left to right on L, thereafter continue&lt;br /&gt;
 taxi to holding point runway 29 via taxiways Exit 2, M and A1.&lt;br /&gt;
 LZB421:Giving way to the 737 from left to right, then continuing taxi to holding point&lt;br /&gt;
 runway 29 via Exit 2, M and A1.&lt;br /&gt;
&lt;br /&gt;
Of course you have to make sure that this instruction is unambiguous, so there shouldn't be two DLH B737s in the area. Also in low visibility operations this procedure might not work very well, in this case you might have to give the aircraft the instruction to continue taxi when the other aircraft has passed. In some cases it is also useful to let one aircraft follow the other: &lt;br /&gt;
&amp;lt;pre&amp;gt;GND:LZB421, follow the Austrian DASH 8 crossing you right to left on M to holding point runway 29.&lt;br /&gt;
LZB421:following the DASH 8 crossing us right to left on M to holding point runway 29.&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intersection departure  ===&lt;br /&gt;
&lt;br /&gt;
Some flights do not need the whole length of their given departure runway so they might request takeoff from an intersection somewhere down the runway. This procedure is called a intersection takeoff. You should only grant this in coordination with Tower and if traffic situation permits. Also at some airports intersections are used to be more flexible in the departure sequence (see section [[Study Guide:Tower#Departure_Seperation_-_Based_on_Type_of_Aircraft_and_departure_route|Departure Seperation]]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Special Situations (High Traffic, Slots, ...)  ===&lt;br /&gt;
&lt;br /&gt;
==== Slots  ====&lt;br /&gt;
&lt;br /&gt;
In case the above mentioned slot regulations are in force ground has the responsibility to set up a departure sequence in a way that the aircraft do not miss their slot. &lt;br /&gt;
&lt;br /&gt;
==== Opposite runway operations  ====&lt;br /&gt;
&lt;br /&gt;
At some austrian airports it is very common to use opposite runway configurations (departure and arrival runway are opposite to each other). In these situations it can happen very fast that you have two aircraft facing each other nose to nose. Special attention should be paid to avoid this situation. &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
	<entry>
		<id>https://wiki.vacc-austria.org/index.php?title=Study_Guide:Ground&amp;diff=1531</id>
		<title>Study Guide:Ground</title>
		<link rel="alternate" type="text/html" href="https://wiki.vacc-austria.org/index.php?title=Study_Guide:Ground&amp;diff=1531"/>
		<updated>2012-01-27T18:05:13Z</updated>

		<summary type="html">&lt;p&gt;Chris Wirowski: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= '''&amp;lt;span style=&amp;quot;color:#ff0000;&amp;quot; /&amp;gt;'''General =&lt;br /&gt;
&lt;br /&gt;
Ground is responsible for all movements of aircraft on ground, except the movements on the runway. Ground takes over responsibility for Delivery if he is not online.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Phraseology&amp;lt;br&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
==== Start-up clearance&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
Start-up clearance can be given if no other aircraft is taxiing behind the starting-up aircraft and if the take-off is expected in 20 minutes or less.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Austrian 125, start-up approved, (Temperature Minus 3)&lt;br /&gt;
&lt;br /&gt;
==== Push-back clearance&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Push-back clearance can be given if no other aircraft is passing behind and the parking position requires push-back.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Austrian 125, push-back approved”&lt;br /&gt;
&lt;br /&gt;
==== '''Combination of both phrases'''&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
During low traffic you can use these two phrases together&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Austrian 125, start(-up) and push(-back) approved&lt;br /&gt;
&lt;br /&gt;
==== Taxi Instructions  ====&lt;br /&gt;
&lt;br /&gt;
The pilot pushes back and starts the aircrafts engines. As soon as he is ready for taxi he will call you: &lt;br /&gt;
&lt;br /&gt;
 AUA125:AUA125, ready for taxi.&lt;br /&gt;
&lt;br /&gt;
Depending on traffic you can give him the taxi instruction to his departure runway: &lt;br /&gt;
&lt;br /&gt;
 GND:AUA125, taxi to holding point Rwy 16 via taxiways Exit 4, L and F, QNH 1019.&lt;br /&gt;
 AUA125:Taxiing to holding point runway 29 via L and F, AUA125.&lt;br /&gt;
&lt;br /&gt;
Sometimes it is necessary to hold an aircraft in front of another taxiway: &lt;br /&gt;
&lt;br /&gt;
 GND:AUA125, hold short of taxiway L.&lt;br /&gt;
 AUA125:Holding short of L, AUA125.&lt;br /&gt;
&lt;br /&gt;
When an aircraft is approaching its assigned holding-point (and clear of possible traffic-conflict) a hand-off to next higher position (i.e. TWR) shall be initiated as soon as possible. &lt;br /&gt;
&lt;br /&gt;
 GND:AUA125, contact now Salzburg Tower on frequency 118.10, bye bye!&lt;br /&gt;
 AUA125:contacting Tower on frequency 118,10 bye!&lt;br /&gt;
&lt;br /&gt;
Air-taxiing is the Movement of a helicopter / VTOL above the surface of an aerodrome, normally in ground effect and at a ground speed of normally less than 20 KT (37 km/h). Please Note: The actual height may vary, and some helicopters may require air-taxiing above 25 FT (8 m) AGL to reduce ground effect turbulence or provide clearance for cargo sling loads. &lt;br /&gt;
&amp;lt;pre&amp;gt;OEATD: request air taxi to Runway 29.&lt;br /&gt;
GND: OEATD, air taxi to Runway 29 via Exit 13 and M.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Ground Traffic Management ===&lt;br /&gt;
&lt;br /&gt;
To organise the traffic on ground different techniques are available, some of them relying on the pilots seeing each other. Generally you should avoid clearing two aircraft onto crossing pathways, unless you are sure they will never meet each other. To achieve this you should instruct aircraft to hold short of taxiways in the way stated above. Consider the following situation: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| You are the Ground Controller at Vienna Airport. Runways active are 34 for landing and 29 for departure. DLH6KM has vacated rwy 34 and requests taxi to its parking position. LZB421 is ready for taxi at stand 7Q.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 GND:DLH6KM taxi to stand 40 via taxiways D and L, QNH 1019.&lt;br /&gt;
 DLH6KM:Taxiing to stand 40 via D and L, DLH6KM.&lt;br /&gt;
 LZB421:Wien ground LZB421 stand 7Q, ready for taxi.&lt;br /&gt;
 GND:LZB421, taxi taxiway W, hold short of taxiway L.&lt;br /&gt;
 LZB421:taxiing via W holding short of L.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;prettytable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| The aircraft are now both approaching the intersection L/W.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
 GND:LZB421, give way to the DLH B737 crossing left to right on L, thereafter continue&lt;br /&gt;
 taxi to holding point runway 29 via taxiways Exit 2, M and A1.&lt;br /&gt;
 LZB421:Giving way to the 737 from left to right, then continuing taxi to holding point&lt;br /&gt;
 runway 29 via Exit 2, M and A1.&lt;br /&gt;
&lt;br /&gt;
Of course you have to make sure that this instruction is unambiguous, so there shouldn't be two DLH B737s in the area. Also in low visibility operations this procedure might not work very well, in this case you might have to give the aircraft the instruction to continue taxi when the other aircraft has passed. In some cases it is also useful to let one aircraft follow the other: &lt;br /&gt;
&amp;lt;pre&amp;gt;GND:LZB421, follow the Austrian DASH 8 crossing you right to left on M to holding point runway 29.&lt;br /&gt;
LZB421:following the DASH 8 crossing us right to left on M to holding point runway 29.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Intersection departure  ===&lt;br /&gt;
&lt;br /&gt;
Some flights do not need the whole length of their given departure runway so they might request takeoff from an intersection somewhere down the runway. This procedure is called a intersection takeoff. You should only grant this in coordination with Tower and if traffic situation permits. Also at some airports intersections are used to be more flexible in the departure sequence (see section [[Study Guide:Tower#Departure_Seperation_-_Based_on_Type_of_Aircraft_and_departure_route|Departure Seperation]]). &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Special Situations (High Traffic, Slots, ...) ===&lt;br /&gt;
&lt;br /&gt;
==== Slots ====&lt;br /&gt;
&lt;br /&gt;
In case the above mentioned slot regulations are in force ground has the responsibility to set up a departure sequence in a way that the aircraft do not miss their slot. &lt;br /&gt;
&lt;br /&gt;
==== Opposite runway operations ====&lt;br /&gt;
&lt;br /&gt;
At some austrian airports it is very common to use opposite runway configurations (departure and arrival runway are opposite to each other). In these situations it can happen very fast that you have two aircraft facing each other nose to nose. Special attention should be paid to avoid this situation. &lt;br /&gt;
&lt;br /&gt;
[[Category:Documents]] [[Category:Study_Guides]] [[Category:Training]] [[Category:Controller]]&lt;/div&gt;</summary>
		<author><name>Chris Wirowski</name></author>
	</entry>
</feed>