Study Guide:OBS - Revision history

Christoph Seitlinger: /* Login as OBS */

2020-03-29T16:53:21Z

Christoph Seitlinger: /* How is an Aerodrome organized */

2020-03-29T16:49:59Z

How is an Aerodrome organized

Claus Faber at 14:46, 5 October 2017

2017-10-05T14:46:19Z

Claus Faber at 14:45, 5 October 2017

2017-10-05T14:45:39Z

Claus Faber at 14:45, 5 October 2017

2017-10-05T14:45:25Z

Claus Faber: /* 2) Readback */

2017-04-24T07:43:29Z

2) Readback

Claus Faber: /* 2) Readback */

2017-04-24T07:40:58Z

2) Readback

Claus Faber: /* 3) Contact - messages - handoff */

2017-04-24T07:38:35Z

3) Contact - messages - handoff

Claus Faber: /* 2) Readback */

2017-04-24T07:32:27Z

2) Readback

Claus Faber: /* 2) Readback */

2017-04-24T07:30:56Z

2) Readback

@@ Line 150: / Line 150: @@
 * You can log onto the VACC Austria Teamspeak server. Software and access instructions are [[http://www.vacc-austria.org/?page=content/static&id=SOFTWARE_PILOTS here]]. Teamspeak version 3 is current.
-* Teamspek is recommended - vital ATC coordination happens there. If you want to listen to controller coordination then switch channel to where those controllers are who you monitor. Say hello, say that you observe and learn, and then shup up. Don't even ask if intense coordination is going on - wait for a pause in traffic and conversation. Do not change into a channel where an exam is going on.
+* Teamspek is recommended - vital ATC coordination happens there. If you want to listen to controller coordination then switch channel to where those controllers are who you monitor. Say hello, say that you observe and learn, and then shut up. Don't even ask if intense coordination is going on - wait for a pause in traffic and conversation. Do not change into a channel where an exam is going on.
 * If you ask a question, then wait for a pause and ask first, if you can ask a question. You can do so by PM in Euroscope or via Teamspeak. Do not ask if traffic is intense, if a training or an exam is going on (in trainings, you might want to ask the trainer in a PM first). Controllers are happy to explain, but ATC is first.

@@ Line 123: / Line 123: @@
 As airports grew bigger over time also the workload for the Air Traffic Controller handling the traffic got bigger. Soon it was necessary to distribute this workload onto more than one controller in order to be able to cope with the traffic.
-So the Tower Position got divided into thre basic types with different areas of responsibility.
+So the Tower Position got divided into three basic types with different areas of responsibility.
 #Clearance delivery (DEL), responsible for checking flightplans and issuing IFR clearances to departing aircraft.
@@ Line 140: / Line 140: @@
 *Since they all use their radar to control air traffic, they are also called Radar positions.
 ----
 =Login as OBS=
 With this preparation, you are fit to login as Observer. You can listen and understand what happens and learn from others doing. Important info and the Euroscope software can be found [[http://www.vacc-austria.org/?page=content/static&id=SOFTWARE_ATC here]]. (You must be accepted as controller to access the page. If you are not yet, contact your mentor).

← Older revision		Revision as of 14:46, 5 October 2017
Line 1:		Line 1:
−	'' Back: [[Study Guide:Basic Lesson]] - Overview: [[Study Guide]] - Next: [[Study Guide:Delivery]]''	+	'' <-- Back: [[Study Guide:Basic Lesson]] - Overview: [[Study Guide]] - Next --> [[Study Guide:Delivery]]''

	== Introduction ==		== Introduction ==

← Older revision		Revision as of 14:45, 5 October 2017
Line 1:		Line 1:
−	'' Back: [[Study Guide:~~OBS~~]] - Overview: [[Study Guide]] - Next: [[Study Guide:Delivery]]''	+	'' Back: [[Study Guide:Basic Lesson]] - Overview: [[Study Guide]] - Next: [[Study Guide:Delivery]]''

	== Introduction ==		== Introduction ==

← Older revision		Revision as of 14:45, 5 October 2017
Line 1:		Line 1:
−	'' Overview: [[Study Guide]] - Next: [[Study Guide:Delivery]]''	+	'' Back: [[Study Guide:OBS]] - Overview: [[Study Guide]] - Next: [[Study Guide:Delivery]]''

	== Introduction ==		== Introduction ==

@@ Line 68: / Line 68: @@
   to Speedbird Airbus A320 crossing right to left on M.
   '''OE-DLT:''' Taxiing to H/P Rwy 29 via Exit 12, M and A1, giving way on M, QNH 1019, OE-DLT.
 ==== 3) Contact - messages - handoff ====

@@ Line 64: / Line 64: @@
   '''LOWW_TWR:''' AUA251, traffic information: Cessna on rwy 16 downwind, report in sight.
   '''AUA251:''' Traffic in sight, AUA251.
   '''LOWW_GND:''' OE-DLT, taxi to Holding Point Runway 29 via Exit 12, M and A1, QNH 1019, give way
@@ Line 71: / Line 69: @@
   '''OE-DLT:''' Taxiing to H/P Rwy 29 via Exit 12, M and A1, giving way on M, QNH 1019, OE-DLT.
-'''One important exception'''
+'''Important exception'''
 There is a difference between controllers and pilots. Why? Because on one frequency, there is one controller, but many pilots:
-* Controllers don't read back. That's logical, because you only read back orders, and pilots don't order.
+* Controllers don't read back. That's logical, because you only read back orders, and pilots don't order. Controllers sometimes acknowledge the receipt of a message, if it's important, like the choice of a runway. That is not read back, but acknowledged, like:
   LOWI_APP: Leipzig 123, runways 08 and 26 are available, report intentions.
@@ Line 81: / Line 78: @@
   LHA123: Expecting Localizer DME East Approach and 08, Leipzig 123.
-''That means: Innsbruck Radar has offered options and asked for the choice (that's an order). LHA123 has read back the order by choosing an option. Innsbruck radar then issues an order on the basis of this information, nd LHA123 reads it back.''
+''That means: Innsbruck Radar has offered options and asked for the choice (that's an order). LHA123 has read back the order by choosing an option. Innsbruck radar then issues an order on the basis of this information, and LHA123 reads it back.''
 ==== 3) Contact - messages - handoff ====

← Older revision		Revision as of 07:32, 24 April 2017
Line 46:		Line 46:

	When a controller (or aircraft) transmits a message to a station it is very important that the receiving station acknowledge the message. But saying "roger" is only in movies - what are you "roger"ing? The called station understood something, but what? Therefore, the '''message content has to be read back in relevant parts'''. If the receiving station does not acknowledge, the transmitted message is considered as a lost transmission and the sender should resend the message or check if the receiving station got the message. For a controller, this is extremely important to remember, since if a pilot's readback is incorrect, the controller has to ask for confirmation, i.e a new readback.		When a controller (or aircraft) transmits a message to a station it is very important that the receiving station acknowledge the message. But saying "roger" is only in movies - what are you "roger"ing? The called station understood something, but what? Therefore, the '''message content has to be read back in relevant parts'''. If the receiving station does not acknowledge, the transmitted message is considered as a lost transmission and the sender should resend the message or check if the receiving station got the message. For a controller, this is extremely important to remember, since if a pilot's readback is incorrect, the controller has to ask for confirmation, i.e a new readback.
		+
		+	The '''Syntax for the readback is reversed''': First the message, then the callsign.

	'''LHA123:''' Wien Radar, Leipzig Air 123, Flight level 230.		'''LHA123:''' Wien Radar, Leipzig Air 123, Flight level 230.

@@ Line 51: / Line 51: @@
   '''LHA123:''' Continuing, Leipzig Air 123.
-''That means: LHA123 calls in the first time and tells which altitude in order to be found and identified by the controller. The Controller acknowledges the contact, and then issues an order: to coninue (on the filed flight plan). This order is then read back by the pilot.''
+''That means: LHA123 calls in the first time and tells which altitude in order to be found and identified by the controller (see part 3) below). The Controller acknowledges the contact, and then issues an order: to coninue (on the filed flight plan). This order is then read back by the pilot.''
 *Items that '''must always be read back''' in full are all clearances (including altitudes, headings, speeds, radials etc), runway in use, altimeter setting (QNH or QFE) and transition level, and all frequencies.