0% found this document useful (0 votes)
6 views3 pages

Flight Plan File Format Guide

Uploaded by

arthuraugustofm
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views3 pages

Flight Plan File Format Guide

Uploaded by

arthuraugustofm
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

iFly Developer Team

—————————————————————————————
1. Introduction
This document describes the format of our flight plan file (.route). We strongly
recommend that third-party software export the route data ONLY, and not export
the SID/STAR/APP data. User input in the CDU may not contain the same
SID/STAR/APP which is in the flight plan file, which most likely will cause
unknown issues.

2. Flight plan data file location


All pre-defined MSFS2020 flight plan files (.route) are stored in Community\ifly-
aircraft-737max8\Data\navdata\FLTPLAN.

Flight plan files can be opened with Windows Notepad or other text editor.

3. Data format
3.1 [RTE] Section
The [RTE] sections stores the Origin and Destination airport of the planned flight.
There must be one [RTE] section in the file, otherwise the flight plan will be
ignored.

Name Value Example

The ICAO code of origin


ORIGIN_AIRPORT ORIGIN_AIRPORT=ZSHC
airport

The ICAO code of


DEST_AIRPORT DEST_AIRPORT=ZLXY
destination airport

3.1 [CDU] Section


To avoid Step Climb calculation issues, we recommend these be left “Blank” for
user input.
Name Value Example

Cruise altitude. Can be CRZ_ALT=33000 or


CRZ_ALT
blank, if not used CRZ_ALT=

Cost index. Can be blank, COST_INDEX=100 or


COST_INDEX
if not used COST_INDEX=

———————————————————————————————Page 1
iFly Developer Team
—————————————————————————————

3.2 [[Link]] Section


This section is used to define each waypoint of the route.
xx: Is the index number, start from “0”. Do not add a leading zero.
For example, [RTE.01] must be written as [RTE.1], [RTE.010] must be written
as [RTE.10].
All items in the [[Link]] section are described below:

Name Value Example Optional

RouteName The name of the route. Up RouteName=R343


to 12 characters.

If blank, CDU will
display “DIRECT”

Name The waypoint name. Up Name=MADUK


to 12 characters

Latitude The latitude of the Latitude=31.718333


waypoint. Range:
- 90.0~90.0

Longitude The longitude of the Longitude=118.105


waypoint. Range: -
180.0~180.0

CrossThisPoint 0: fly-by CrossThisPoint=1


1: fly-over √
Default value: 0

Heading The course to the Heading=53


waypoint. Range: 0~360.
When set to 0, the
CDU will calculate the
course. √

To define a heading use:


1~360
Default value: 0

SpeedConstraint 0: waypoint has no SpeedConstraint=1


speed constraint
1: waypoint has a speed √
constraint
Default value: 0

———————————————————————————————Page 2
iFly Developer Team
—————————————————————————————
Speed The speed constraint. Speed=210
xxx: “AT” restriction Speed=210A
Speed-210B
xxxA: “AT or ABOVE”
restriction
xxxB: “AT or BELOW” √
restriction
0 means there is no
speed constraint.

AltitudeConstraint 0: waypoint has no AltitudeConstraint=1


altitude constraint
1: waypoint has an √
altitude constraint
Default value: 0

Altitude The altitude constraint. Altitude=0600


xxx: “AT” restriction Altitude=0600A
xxxA: “AT or ABOVE” Altitude=25000B
restriction Altitude=0600A1200B
xxxB: “AT or BELOW”
restriction

xxxAxxxB: “WITHIN”
restriction.
xxx can be
0600,1600,16000,26000
When set to 0, there is
no altitude constraint.

Frequency* The Frequency at VOR or Frequency= 114.30


NDB waypoints.

The format is XXX,
XXX.X, [Link].

FrequencyID* The Identifier at VOR or FrequencyID=TIA



NDB waypoints.

*: Only enter one item (Frequency or FrequencyID). The CDU will automatically
generate the other item.

———————————————————————————————Page 3

You might also like