Flight Plan
The flight planning tool accessible from the "NAV" panel can export and import files in JSON format.
The route in these JSON files is represented by an array of waypoint objects with the following properties:
- ident (can be null, empty or omitted) (string): the ICAO identification of the waypoint when it is a known navaid. FIX way point will bear the "FIX" ident code.
- type (can be null, empty or omitted) (string): the type of waypoint. Any value will be accepted but specific GeoFS types are:
- DPT for departure airport. Only valid as first entry in the route array. Used to set aircraft in initial takeoff position. (The waypoint must also provide a "heading" value in order to set takeoff position correctly.)
- DST for destination airport. Only valid as last entry in the route array. Used to instruct autopilot to use ILS localizer and glide slope for automatic approach. (The waypoint must also provide a "heading" value in order to set generic ISL approach path)
- RNW, WPT, FIX, ILS, DME, NDB, NDB-DME, VOR, VOR-DME, TACAN, VORTAC
- lat (float): latitude, rounded to 5 decimals in GeoFS exports
- lon (float): longitude, rounded to 5 decimals in GeoFS exports
- alt (can be null, empty or omitted) (string or int): used to set autopilot altitude at each waypoint and specify a basic altitude profile. Can be given in feet as int or in flight level as string (ie. "FL350"). Must be set to 0 for DPT and DST waypoints.
- spd (can be null, empty or omitted) (int): used to set autopilot speed hold at each waypoint. Can be given in knots as int or as Mach when prefixed with M (is. "M0.85")
- vspd (not yet implemented) (int): vertical speed in m/s used to set autopilot vertical speed at each waypoint
- heading (can be null, empty or omitted) (float): rounded to 2 decimals in GeoFS export. Used with DPT and DST waypoint types to set aircraft orientation and approach configuration
At minima, a waypoint must have lat and lon properties.
The first and last waypoints can optionally be of type DPT and DST to help positioning the aircraft departure position and configure automatic approach. Those need a heading property and an altitude set to 0
This is an example of a short flight plan from KSFO to KLAX with a route using a mixture of navaids and GPS FIX as waypoints:
[
{
"ident": "KSFO",
"type": "DPT",
"lat": 37.62872,
"lon": -122.39335,
"alt": 0,
"spd": "",
"heading": 117.9
},
{
"ident": "HYP",
"type": "VOR-DME",
"lat": 37.2194,
"lon": -120.4,
"alt": "10000",
"spd": "300"
},
{
"ident": "KSMX",
"type": "VORTAC",
"lat": 35.2523,
"lon": -120.76,
"alt": "FL350",
"spd": "M0.85"
},
{
"ident": "FIX",
"type": "FIX",
"lat": 33.8846112757352,
"lon": -118.87756347656251,
"alt": "8000",
"spd": "300"
},
{
"ident": "KLAX",
"type": "DST",
"lat": 33.93365,
"lon": -118.41903,
"alt": 0,
"spd": "150",
"heading": 82.95
}
]