652
edits
OpenRadarGuide: Difference between revisions
Jump to navigation
Jump to search
m
raw input of the FlightPlan feature description - in work
(→Startup: add 3rd welcome-tab "tweaks") |
m (raw input of the FlightPlan feature description - in work) |
||
| Line 351: | Line 351: | ||
<br /> <br /> | <br /> <br /> | ||
---- | ---- | ||
=='''''Flight-Plan & Flight-Management'''''== | |||
There is a now Flight-Plan feature inside OpenRadar, that gets distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time. In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan. | |||
Define/Edit a Flight-Plan: | |||
You open the Flight-Plan for a target by clicking with the “center mouse-button” onto the Flight-Strip or the target on the radar-screen. | |||
Controlling the ownership: | |||
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field | |||
“Controlled/Uncontrolled” must state “controlled by me”! | |||
If it is “Uncontrolled” click onto “control” and that field will indicate your “ownership” and avoid others to change | |||
If it is “Controlled by …..” you must wait till the ATC controlling it now will | |||
either remove his “ownership” by | |||
clicking onto “Handover to” and selecting | |||
another ATC for takeover | |||
or the “blank” for just removing that control. | |||
or clicking onto the button “UnControl” | |||
or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically | |||
or you send the controlling ATC a mail asking him to release the target | |||
If it shows “Controlled by me” you can release the target | |||
by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover | |||
or you grab the Flight-Strip with the mouse and move it left into the radar-scope and select an ATC (or “blank”) | |||
or you move the Flight-Strip all the way to the right – that will just remove your ownership | |||
Mandatory fields of the OR-Flight-Plan: | |||
Contact is the flight UID of the target (will be set automatically) | |||
Aircraft is the model-code of the target (will be set automatically) | |||
Departure is the departure Airport (will be set automatically to your airport if on GND - or manual) | |||
Destination needs the IATA-code of the destination (e.g. EDDF for Frankfurt) | |||
ETA is the “Estimated Time of Arrival” - it is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (will be calculated automatically) | |||
Optional fields of the OR-Flight-Plan: | |||
native language is per default “en” for English. If you choose another language your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language” | |||
FgCom indicates that target uses FgCom | |||
Squawk shows the Squake-Code you assigned to the target | |||
Assgnd RWY shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or be DoubleClick onto the runway number in the “Runway Settings” | |||
Route defines the SID, STAR, etc. assigned | |||
Altitude as assigned by ATC from time to time (not the constant Crsg.Alt!) | |||
Code will be used in future when given by a more professional Flight-Planning system | |||
IFR/VFR may be defined by the PullDown | |||
Route can be used to document a preplanned route | |||
Crsg.Alt.: Define the planned cruising altitude en route (usually in FL) | |||
Crsg.TAS.: Define the planned TAS en route (usually as GND-speed) | |||
Alt.Airports can be defined as needed deviations in case of bad weather etc. | |||
Comments these are comments that will be kept together with the Flight-Plan | |||
Private notes are comments that remain with the ATC making these (in file OpenRadar/settings/atcComments.xml) and will always be inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not. | |||
Flight-management: | |||
You always can open all Flight-Plans for all targets in your range by center-mouse-click onto the radar-target or the FlightStrip. Then do as described in the following scenarios: | |||
1. A target appears on your airport | |||
(1) | |||
There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus | |||
the tag-color is “green” | |||
the flight-strip background color is light green, in order to indicate that you did not yet do anything with it. | |||
a simple mouse-click or any other action will remove the green background. | |||
2. → you define a new Flight Plan | |||
Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). (If there is still another ATC the owner in charge you cannot take over prior that the other ATC released or transferred that target!) | |||
Generate the Flight-Plan | |||
See the Informations given in the target-label and the stripe. e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)” it could look like: | |||
(2) | |||
jomo the pilot FGFS-UID | |||
160* the current heading (now on ramp!) | |||
HaedSet-sign that pilot uses radio (FGCom or Mumble) | |||
CONC the FGFS-model is the Concorde | |||
KJFK is the planned destination | |||
260° is the straight heading EDDF (departure) to KJFK (destination) | |||
BIBTI is the SID planned for departure (on arrival here would be the STAR) | |||
RW25C is the runway assigned for departure (or for arrival) | |||
0400* is the current altitude (on GND in EDDF!) | |||
00 is the speed (still parking!) | |||
Also see the two fields for comments: | |||
in the upper line at the bottom are same data as in the target-label center-line | |||
in the lower line are private comments from yourself to that FGFS-UID | |||
Departing | |||
GND will use the data as shown to bring the plane to the HoldingPoint | |||
TWR will take over | |||
The runway-assignment will be removed automatically | |||
Transfer Control to next ATC (or blank) | |||
(3) | |||
grab-move the FlightStrip left into the Scope and select the next ATC (or open the Flight-plan and select at “Handover to:”). | |||
if there is no “next ATC” available select the blank entry – the target is then free to be picked by ans ATC en-route. | |||
the FlightStrip will indicate the pending transfer by showing | |||
“current ATC” => “next ATC” | |||
The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention! | |||
as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicate the “next ATC” and prevent any more changes from you! | |||
3. A target appears in your airspace: | |||
take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control | |||
if the target has no owner yet and is just crossing your airspace and indicates his destination you may open the FlightPlan and insert that destination so that all the other ATCs know about it. | |||
If the target lands on your airport: | |||
assign a STAR and/or RW | |||
the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. (But you can always add your remarks for your own usage). | |||
1. If an ATC forgets to “reassign” or “free” a target the ownership will automaticalle removed as soon as the tagets gets out of the rang of that ATC (~100mi). Any other ATC may then take over. | |||
== '''''Useful Features''''' == | == '''''Useful Features''''' == | ||