You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20Lines changed: 20 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,7 @@ At the moment, `DelHel` supports the following validations and processing:
54
54
- CFL (**c**leared **f**light **l**evel) validation: verifies correct CFL is set for selected SID. Processing a FPL automatically sets the correct CFL for the calculated SID.
55
55
- RWY (**r**un**w**a**y**) validation: displays a warning if a runway assignment has been found in the flightplan as this might influence SID selection.
56
56
- Flightplan cleanup: when processing a flightplan, some cleanup will be performed, removing any additional information the pilot might have included before the SID fix (e.g. a SID filed by the pilot), only leaving a valid speed/level group or a runway designation included. This prevents SID assignments filed by pilots from selecting an incorrect runway or procedure by accident.
57
+
- INV (**Inv**alid routing): verifies that the filed flightplan contains a valid routing according to the maintained routing.json file. Those routes can e.g. be the SAXFRA compulsory routings or special Vatsim Event routings. Each route contains at least an entry point (= last waypoint of the SID) and optional waypoints. If waypoints are maintained, the flightplan has to contain those waypoints in identical sequence in order to pass the routing validation. "DCT"/"DIRECT"/Speed-Altitude-Blocks in the FP are omitted.
57
58
58
59
Flightplans can be processed manually using the [`Process FPL`](#process-fpl)[tag function](#tag-functions) or automatically by toggling the [automatic processing](#toggle-automatic-processing) setting on.
59
60
@@ -103,6 +104,25 @@ Indicates pilot filed a VFR flightplan, so little to no validations can be perfo
103
104
Info, green color.
104
105
Indicates pilot filed a processed VFR flightplan, so little to no validations can be performed. This just serves as an additional reminder about VFR flights.
105
106
107
+
##### `MIN`
108
+
109
+
Caution, orange color.
110
+
Indicates, that the Requested Flight Level RFL is below the minima for the filed route.
111
+
The altitudes are maintained in the routing.json and can be disregarded by the controller if necessary (e.g. depeding on active/inactive military areas along the route).
112
+
113
+
##### `MAX`
114
+
115
+
Caution, orange color.
116
+
Indicates, that the Requested Flight Level RFL is above the maxima for the filed route.
117
+
The altitudes are maintained in the routing.json and can be disregarded by the controller if necessary (e.g. depeding on active/inactive military areas along the route).
118
+
119
+
120
+
##### `INV`
121
+
122
+
Caution, orange color.
123
+
Indicates, that the filed route is not valid according to the maintained routings (routing.json). Those routings are e.g. the compulsory SAXRFRA routings for LOWW-departures or in case of a Vatsim Event.
124
+
Indication becomes active as soon as the flightplan has been processed (SID is set and a valid SID exit point is in the FP).
0 commit comments