iFly Developer Team
—————————————————————————————
1. Introduction
All of iFly Jets Advanced Series add-ons use a common navigation database. For
MSFS2020, the default folder is at “Community\ifly-aircraft-max8\Data\navdata”
There are 3 sub-folders in the navdata folder. The folder called “FLTPLAN” is
used for storing pre-defined routes.
The “Permanent” folder is used to store the full navdata from Navigraph or other
navigation data supplier. In the folder there are 3 sub-folders and several .txt/data
files, which are the navdata itself. All related procedure data is stored in SID and
STAR folders. The SUPP folder is used to store additional airport data.
The “Supplemental” folder is used to store user created navdata which is not
available from navigation data suppliers. Data in the Permanent and
Supplemental folder share the same format. The Supplemental folder may
contain only specific navdata. If the Supplemental folder has the same
SID/STAR procedures contained in the Permanent folder database, the system
will use the Supplemental folder database as it has higher priority.
——————————————————————————————————
Page 1
iFly Developer Team
—————————————————————————————
2. Navigation data file
extensions
The SID folder stores the procedures for takeoff: SID and SID TRANS. A SID
procedure file is named “ xxxx.sid”, and SID TRANS procedure file is named
“xxxx.sidtrs”. The “xxxx” is the ICAO code for the airport.
The STAR folder stores the procedures for landing, including STAR, STAR
TRANS, APPROACH and APPROACH TRANS. A STAR file is named
“xxxx.star”; STAR TRANS f i l e i s n a m e d “ xxxx.startrs”. An
APPROACH procedure f i l e i s n a m e d “ xxx.app, and an APPROACH
TRANS procedure file is named “xxxx.apptrs”. The “xxxx” is the ICAO code for
the airport.
The SUPP folder stores supplementary airport data files, which are named
“xxxx.supp”. The“xxxx” indicates the airport ICAO code.
There are seven “.txt” files and one “.dat” file in the main navdata folder, which
are the AIRAC files. Note the “WPNAVGLS.txt: file
“WPNAVGLS.txt” contains GLS landing procedures, which are the same
format as “WPNAVAID.txt”, except:
1. The freq xxx.xx(Mhz, 5 digital with one decimal) is changed to
xxxxx(Channel, 5 digital).
2. Five (5) character GLS ID is after runway height data.
3. The G/S angle (3 digs with one decimal) is after GLS ID.
All the files can be opened with Windows Notepad or any text editor.
——————————————————————————————————
Page 2
iFly Developer Team
—————————————————————————————
3. SID/STAR Data format
Each SID/STAR filehas the same format.
3.1 [list] Section
There must be one [list] section in the file, otherwise the file will be ignored.
T h e f i l e lists all procedures of an airport. The format is
“Procedure.AA=BB.CC”.
AA: It is index number, start from “0” and up to “255”. Do not add the leading
zero. For example, Procedure.01 must be written as Procedure.1,
Procedure.010 must be written as Procedure.10.
BB: This is the procedure name, which is used for displaying on the CDU DEP
ARR and RTE pages. String combination such as “A”~“Z” and “0”~“9” are
allowed. The maximum length of each string is 12 characters.
CC: This data is used to link other procedure.
For a SID, this data is the runway identifier. xx, xxL, xxR, xxC are allowed.
“xx" is from “001” to “36”
For a SID TRANS, this data is the SID identifier. String combinations such
as “A”~“Z” and “0”~“9” are allowed. The maximum length of each string is
12 characters.
For a STAR, this data is the runway identifier, xx, xxL, xxR, xxC are allowed.
“xx” is from “001” to “36”
For a STAR TRANS, this data is the STAR identifier. String combinations
such as “A”~“Z” and “0”~“9” are allowed. The maximum length of each
string is 12 characters.
For an APPR, this data is the runway identifier. xx, xxL, xxR, xxC are
allowed. “xx” is from “001” to “36”
For an APPR TRANS, this data is the APPR identifier. String combinations
such as “A”~“Z” and “0”~“9” are allowed. The maximum length of each
string is 12 characters.
If one TRANS can link to multiple SID/STAR/APP, or one SID/STAR/APP
can link to multiple RUNWAYS, multiple procedures must be created. For
example, if SID ”AJ1G” can used for 05L, 05R, 23L, 23R, procedures must
be written as fol l ows :
Procedure.0=AJ1G.05L
Procedure.1=AJ1G.05R
Procedure.2=AJ1G.23L
Procedure.3=AJ1G.23R
3.2 [BB.CC.DD] Section
Each “Procedure.AA=BB.CC” item must have at least one [BB.CC.DD] section,
which is used to define each waypoint.
BB: Same as the BB in [list] above.
——————————————————————————————————
Page 3
iFly Developer Team
—————————————————————————————
CC: Same as the CC in [list] above.
DD: Is the index number, starting from “0” and up to “255”. Do not add the
leading zero. For example, [AJ1G.05L.01] must be written as
[AJ1G.05L.1], and [AJ1G.05L.010] must be written as [AJ1G.05L.10].
Description of all items in the [BB.CC.DD] Section:
Name Value Example
Leg Leg types. The following leg Leg=CA
types may be used: PI, HA, HF,
HM, FM, VM, AF, CA, VA,
CD,VD, CF, CI, VI, CR, VR,
DF,FA, FC, FD, RF, TF, IF.
Note：The CDU will translate
HA, HF, HM as a HOLD
point.
Name The waypoint name. Up to 12 name=TP050
characters
Latitude The latitude of the waypoint. Latitude=25.128333
Range: -90.0~90.0
Longitude The longitude of the waypoint. Longitude=121.286667
Range: -180.0~180.0
CrossThisPoint 0: fly-by CrossThisPoint=1
1: fly-over
Heading The course to the waypoint. Heading=53
Range: 0.0~360.0. When set to
0.0, the CDU will calculate the
course.
TurnDirection The turn direction. TurnDirection=R
R: right turn
L: left turn
Speed The speed constraint. Speed=210B
xxx: “at” restriction
xxxA: “at or above” restriction
xxxB: “at or below” restriction
Altitude The altitude constraint. Altitude=00600A
xxx: “at” restriction Altitude=0600A1200B
——————————————————————————————————
Page 4
iFly Developer Team
—————————————————————————————
xxxA: “at or above” restriction Altitude=FL060
xxxB: “at or below” restriction Altitude=MAP
xxxAxxxB: “within” restriction
xxx can be FL180,
FL080,0600,1600
MAP If it is a missed approach point, MAP=1
then set it to “1”. One approach
must have one MAP. All
waypoints behind this point are
normal waypoint and all
waypoints after this point are
GA section.
Frequency The frequency of a signal Frequency=TIA
station which the airplane will Frequency= 114.30
use with. The format is XXX,
XXX.X, XXX.XX. This field
can be a frequency or identifier.
If there is more than one ILS
freq for one runway, then this
field can be used to define
which ILS freq is use for this
procedure.
Slope The flight path angle. Slope=2.8
Positive mean descent,
Negative mean climb.
NavBear Radial from the station NavBear=231.0
NavDist DME from the station NavDist=12.0
Dist Distance for PI/HA/HF/HM/FC Dist=12.5
leg
CenterLat Latitude of center point for RF CenterLat=52.298333
leg
CenterLon Longitude of center point for CenterLon=4.683611
RF leg
——————————————————————————————————
Page 5
iFly Developer Team
—————————————————————————————————————————————————
3.3 Minimum data items for all leg type
The following chart describes the minimum data items needed for every leg type
Leg Name Latitude/ Cross Heading Turn Speed Altitude MAP Frequency Slope NavBear NavDist Dist CenterLat/
Longitude This Direction CenterLon
Point
PI √ √ √ √ √ √ √ (1)
HA √ √ √ √ (2)
HF √ √ √ √ (2)
HM √ √ √ √ (2)
FM √
VM √
AF √ √ √
CA √ √
VA √ √
CD √ √ √
VD √ √ √
CF √ √
CI √
———————————————————————————————————————————————————————Page 6
iFly Developer Team
—————————————————————————————————————————————————
VI √
CR √ √ √
VR √ √ √
DF √
FA √ √
FC √ √ √
FD √ √ √ √
RF √ √
TF √
IF √
(1). If not set or is “0”, FMC will use 7.0 as a default distance
(2). If not set or is “0”, FMC will use 1 minute or 1.5 minute as a default distance.
If set to a distance, the value must below 1000.
If set to a time, set 10000 for one minute, e.g. 12000=1.2min, 55000=5.5mins, 150000=15mins
———————————————————————————————————————————————————————Page 7
iFly Developer Team
—————————————————————————————
3.4 Leg Description
3.4.1 PI leg
PI leg uses Latitude/Longitude item to define the point A, and uses Frequency/
NavBear/ NavDist item to define point B. Then PI uses Dist and Heading to fly
the Procedure Turn. In this illustration the TurnDirection is “R”.
Note: If Dist is not defined, then FMC will use 7.0 as a default distance.
Note: If Frequency/NavBear/NavDist is not defined, then FMC will use Dist*2.0
as a default distance.
Note: The leg next to the PI leg must define a heading data.
3.4.2 HA, HF, HM leg
HA, HF are all only handled as an HM leg. Use Latitude/Longitude t o define
point A, and use Dist to define length of the hold. When Dist<1000.0, it is in
“NM”, if Dist>1000, then it will be in “MINUTE”, and t h e FMC will use
Dist/10000 as the time. For example, Dist=10.5 mean distance=10.5nm, Dist=15000
means distance=1.5 mins. In this illustration the TurnDirection is “R”.
3.4.3 FM, VM leg
The FMC will translate these 2 types of legs to the conditional waypoint as “heading
vectors to a course or fix”. The aircraft needs a heading to fly the FM/VM leg. If the
aircraft is in LNAV mode, the FMC will continue fly FM/VM heading and not switch
———————————————————————————————Page 8
iFly Developer Team
—————————————————————————————
the next waypoint. If not in LNAV mode, the aircraft will switch to the next waypoint
when the distance to the next waypoint is less than 3nm.
3.4.4 AF leg
The aircraft uses Frequency and NavDist to track the AF leg.
3.4.5 CA, VA leg
The FMC will translate these 2 type legs to the conditional waypoint as “climb/descent
through an altitude”. The aircraft needs a heading to fly the CA/VA leg. When
reaching the altitude, the FMC will switch to the next waypoint.
3.4.6 CD, VD leg
The FMC will translate CD/VD leg to conditional waypoint as “flying a heading to a
radial or DME distance”. The aircraft will fly to specified heading and use Frequency
and NavDist f o r navigation.
3.4.7 CF leg
When the aircraft passes the previous waypoint, it will make a turn and intercept the
course in the Heading field.
Note: The FMC will use one ARC and one STRAIGHT LINE to fly the CF. In the
following illustration, leg B is the correct CF leg, and leg C is not. The FMC will
change leg C from CF leg to DF leg.
3.4.8 CF leg
When the aircraft passes the previous waypoint, it will make a turn and intercept the
course in the Heading field.
———————————————————————————————Page 9
iFly Developer Team
—————————————————————————————
3.4.9 CI, VI leg
The FMC will translate CI/VI leg to conditional waypoint as “flying a heading to a
radial or DME distance” or “intercepting a course”.
If the next leg is an AF leg, it will translate to “flying a heading to a radial or DME
distance”.
If the next leg is not an AF leg, it will translate to “intercepting a course”. And the next
leg must have heading data, or be an IF/TF leg.
3.4.10 CR, VR leg
The FMC will translate CR/VR leg to conditional waypoint as “flying a heading to a
radial or DME distance”. The aircraft will fly to specified heading and use Frequency
and NavBear for navigation.
3.4.11 DF leg
The FMC needs the Latitude/Longitude to navigation
3.4.12 FA leg
The FMC will translate CD/VD leg to conditional waypoint as “passing through an
altitude”. T h e a i r c r a f t will fly to specified heading and switch to the next
waypoint when passing through the specified altitude.
3.4.13 FC leg
The Latitude/Longitude (point A) item in a FC leg is not the position the FMC will
use, as it is only a base position. The FMC uses Latitude/Longitude, Heading and Dist
to calculate the final waypoint position (point B). In the CDU/ND, the position of the
waypoint is B.
———————————————————————————————Page 10
iFly Developer Team
—————————————————————————————
3.4.14 FD leg
The Latitude/Longitude (point A) item in a FD leg is not the position FMC will use, as
it is only a base position. The FMC uses Latitude/Longitude, Heading, Frequency and
NavDist to calculate the final waypoint position (point B). In the CDU/ND, the
position of the waypoint is B.
3.4.15 RF leg
The FMC needs Latitude/Longitude (point A) and CenterLat/CenterLon (point B) for
the aircraft to fly a RF leg.
3.4.16 TF, IF leg
The FMC needs the Latitude/Longitude to navigate. The FMC will translate CD/VD leg
to conditional waypoint as “passing through an altitude”.
———————————————————————————————Page 11
iFly Developer Team
—————————————————————————————
4. SUPP Data
The SUPP folder stores supplementary airport data. A supplementary file is named
“xxxx.supp”. The “xxxx” is the airport ICAO code.
All items in the supplementary file are described as follows:
Section Name Value Example
[GATE]
The name of Latitude,
Gate 11=30.235467,120.431075
the gate longitude.
B1=30.232091,120.432147
Any speed, in
Speed [Speed_Transition]
IAS
Speed_Transition Speed=281
Any altitude, in
Altitude Altitude=10000
feet
Any altitude, in [Transition_Altitude]
Transition_Altitude Altitude
feet Altitude=14000
Any altitude, in [Transition_Level]
Transition_Level Altitude
feet Altitude=16000
5. FlightPlan Data
See Flightplan Introduction.pdf for more details..
———————————————————————————————Page 12
