Study Guide:Radar - Revision history

Jakob Engelbrecht: /* Coordination with adjacent Sectors */

2020-10-03T12:55:30Z

Coordination with adjacent Sectors

Jakob Engelbrecht: /* Coordination with adjacent Sectors */

2020-10-03T12:51:20Z

Coordination with adjacent Sectors

Jakob Engelbrecht: /* The Handoff */

2020-10-03T12:50:47Z

The Handoff

Jakob Engelbrecht: /* Holding */

2020-10-03T12:46:39Z

Holding

Jakob Engelbrecht: /* The Release */

2020-10-03T12:46:07Z

The Release

Jakob Engelbrecht: /* Coordination with adjacent Sectors */

2020-10-03T12:43:33Z

Coordination with adjacent Sectors

Jakob Engelbrecht: /* Transfer of Control */

2020-10-03T12:39:36Z

Transfer of Control

Jakob Engelbrecht at 12:31, 3 October 2020

2020-10-03T12:31:21Z

Jakob Engelbrecht at 12:05, 3 October 2020

2020-10-03T12:05:24Z

Patrick Weineis: /* Structure of Flightplans and Routings */

2017-11-06T03:59:56Z

Structure of Flightplans and Routings

@@ Line 267: / Line 267: @@
 If the handoff is accepted, transfer of control is complete.
 ===The Release===
@@ Line 273: / Line 277: @@
 is used.
-Alternatively the downstream sector can use the Topsky release function while transferring the tag to release the aircraft to the downstream sector either climb (C), descent( D), turns (T) or full (F).
+Alternatively the upstream sector can use the Topsky release function while transferring the tag to release the aircraft to the downstream sector either climb (C), descent( D), turns (T) or full (F).
 ==VFR Traffic==

@@ Line 252: / Line 252: @@
 * Transfer of Control
-Before you transfer an aircraft however, you must ensure to send it to the appropriate sector and station. Aircraft climbing through different sectors are generally only allowed with prior coordination. Should you want to avoid this you msut instruct an aircraft to avoid a sector horizontally/vertically (eg cross SOVIL at FL170 or above (to avoid entering the Linz APP Sector))
+Before you transfer an aircraft however, you must ensure to send it to the appropriate sector and station. Aircraft climbing through different sectors are generally only allowed with prior coordination. Should you want to avoid this you must instruct an aircraft to avoid a sector horizontally/vertically (eg cross SOVIL at FL170 or above (to avoid entering the Linz APP Sector))
 ====Transfer of Communication====

@@ Line 251: / Line 251: @@
 * Transfer of Communication
 * Transfer of Control
 ====Transfer of Communication====

@@ Line 207: / Line 207: @@
   - The time to leave the fix in the event of a communications failure.
-* '''Standart Holding Pattern'''
+* '''Standard Holding Pattern'''
      * Standard Hold: A hold where all turns are made to the right
@@ Line 222: / Line 222: @@
      * Non Holding Side: The side of the course where you do not want the pilot to be holding
-* '''Non Standart Holding Pattern'''
+* '''Non Standard Holding Pattern'''
 A non-standard holding pattern is one in which

@@ Line 270: / Line 270: @@
   "Released for ..."
 is used.
 ==VFR Traffic==

@@ Line 256: / Line 256: @@
 ====Transfer of Control====
-This is done by sending the tag to the next controller as soon as the pilot reads back the corretc clearance. You may only do this if the plane is safe and will remain safe within your sector at all time. So initiate the handoff if you don't need him anymore, but not before that.
+This is done by sending the tag to the next controller as soon as the pilot reads back the correct clearance. You may only do this if the plane is safe and will remain safe within your sector at all time. So initiate the handoff if you don't need him anymore, but not before that.
-The other controller accepts the handoff. Again he only does this if he can really accept the traffic without creating a conflict. If that's not possible the two of you will have to work out a different solution.
+The other controller accepts the handoff upon the intial call of the pilot.
 If the next controller rejects the handoff, the aircraft is not allowed to enter his sector and it is your responsibility to ensure it doesn't.
 '''<span style="color:#ff0000;">You are responsible for everything that happens in your sector.</span>''' And you are not allowed to do anything in somebody else's if it is not stated in your sectors Letters of Agreement or without his permission.

@@ Line 91: / Line 91: @@
   ABC123 turn right heading 080°, radar vectors for ILS approach RWY 11
 After vectoring an aircraft you might have to send the aircraft back on its flight planned route:
-  ABC123, proceed direct to SITNI
+  ABC123, resume own navigation direct to SITNI
 It is important to know, that as soon as you take an aircraft of a publsihed route, either by vectoring or by using a direct, you are also responsible for the necessary terrain clearance. To do this always consider the MRVA on the aircrafts path.
 ====Vertical Vectoring====
@@ Line 112: / Line 112: @@
 To effectively use the sequencing techniques explained below we first have to assess the current situation.
 ====Determining current seperation====
-In VRC and ES there are tools available to determine the seperation between aircraft. One of them is the Seperation Predictor. It is a very comfortable way to determine the point where two aircraft, given a constant speed, will be closest to each other. Furthermore it gives you the minimum distance and the time to go to this point.
+In Topsky and ES there are tools available to determine the seperation between aircraft. One of them is the Seperation Tool (SEP in the Radar Menu). It is a very comfortable way to determine the point where two aircraft, given their calculated groundspeed and track, will be closest to each other. Furthermore, it gives you the minimum distance and time of this point.
-To constantly survey the distance between to aircraft (or between an aircraft and a point) you can use seperation links (or anchors).
+To constantly survey the distance between to aircraft (or between an aircraft and a point) you can use QDM tool.
 These tools give you an overview over the lateral situation. The vertical situations is a bit more complicated since you have to use a bit of math. If you have two converging aircraft who are not at a constant altitude you need their rate of climb/descend to determine the spacing at their closest point.

@@ Line 28: / Line 28: @@
 ==Structure of Flightplans and Routings==
 A route consist of one or more points connected by eithe airways or directs (DCT).
- SITNI DCT BAGSI DCT NANIT
+SOVIL DCT SITNI DCT BAGSI DCT NANIT
 In this case SITNI is the first point of the Route, thereafter it direct to BAGSI and so on.
 ===SIDs===
 SID (Standard Instrument Departure): It is a pre-defined route which aircrafts have to fly to get to their initial airway to follow their desired routing to their destination.
-e.g.: Flightplan from LOWW (Wien) to Salzburg (LOWS): SITNI DCT BAGSI DCT MATIG - SITNI is our first waypoint of our routing and let us say for instance that in Vienna Runway 29 is in use. We take a look at our charts and we see that we can plan for a socalled SITNI6C departure route.
+e.g.: Flightplan from LOWW (Wien) to Salzburg (LOWS): SOVIL DCT SITNI DCT BAGSI DCT MATIG - SITNI is our first waypoint of our routing and let us say for instance that in Vienna Runway 29 is in use. We take a look at our charts and we see that we can plan for a socalled SITNI6C departure route.
 SIDs are specified by the local Air Traffic Control. A SID can contain the following navigation aids: R-NAV Waypoints, VORs, NDBs, etc.