ATC-pie: Difference between revisions

ATC-pie (view source)

Revision as of 22:22, 19 January 2015

102 bytes added , 19 January 2015

no edit summary

Mickybadia

265

edits

@@ Line 72: / Line 72: @@
 * most importantly, the aircraft's ''callsign'', to be used on the radio;
 * its type, airspeed and all sorts of other details that can be specified by the pilots themselves when filing ''flight plans''; and
-* parameter assignments: squawk code, altitude and heading when vectoring, etc.
+* parameter assignments: transponder code, altitude and heading when vectoring, etc.
 === Linking strips ===
-Double-clicking on a strip will open a strip detail sheet where those details can be manually edited, but strips can also be '''linked''' with a middle button click, each to a flight plan and/or a visible radar contact on the scope screen — a strip can only be linked to one flight plan and to one radar contact. Linking to a strip will automatically make the strip display the missing elements made available by the linked aircraft transponder or flight plan. Any detail mismatch between the strip and either a linked flight plan or radar contact will be reported for you to resolve.
+Double-clicking on a strip will open a strip detail sheet where those details can be manually edited, but strips can also be '''linked''' with a middle button click, each to a flight plan and/or a visible radar contact on the scope screen — a strip can only be linked to one flight plan and to one radar contact. Linking to a strip will automatically:
+* make the strip display the missing elements made available by the linked aircraft transponder or flight plan;
+* label the radar contact dot with the more informed linked details (e.g. assigned altitude).
+Any detail mismatch between the strip and either a linked flight plan or radar contact will be reported for you to resolve.
-To identify an aircraft and link the right radar contact to a strip, ATC can rely on different things. He can read an aircraft's callsign straight away if it is visible (or cheated), tell from reported positions and altitudes, or use a unique transponder code and wait for it to appear on the radar. For instance, say a VFR traffic makes an initial radio contact giving his callsign and approximate position, ATC will typically pull out a new blank strip and give the pilot a transponder code to squawk, writing this assignment detail on the strip alongside the announced callsign. This allows for what ATC-pie calls ''soft links'', in essence radar identification of an aircraft–strip pair such that:
+To identify an aircraft and link the right radar contact to a strip, ATC can rely on different things. He can read an aircraft's callsign straight away if it is visible (or cheated), tell from reported positions and altitudes, or use a transponder code. For instance, say a VFR traffic makes an initial radio contact giving his callsign and approximate position, ATC will typically pull out a new blank strip and give the pilot a unique transponder code to squawk, writing this assignment detail on the strip alongside the announced callsign, and wait for it to appear on the radar. This allows for what ATC-pie calls ''soft links'', in essence radar identification of an aircraft–strip pair such that:
+* the strip is assigned a transponder code;
-* a strip is assigned a squawk code;
+* no other strip is assigned the same code;
-* an aircraft is the only one using that transponder code in radar range; and
+* the aircraft is the only one squawking that code in radar range.
-* no other strip is assigned this code.
 Soft links are reported to you so you can properly link the two and consider the aircraft identified... and inform them and give them subsequent instructions.