Professional Documents
Culture Documents
1. Introduction
iFly Jets: The 737NGs FMC (Flight Management Computer) supports various
standard procedures which including SID, SID TRANS, STAR TRANS, STAR,
APPROACH TRANS and APPROACH. We didnt provide procedures in the pack.
We only provide the format of our procedures. You can find procedures in many FS
website, such as http://PlanePath.com
3. Data format
Each line of data stands for one navigation point. Among the line each particular
data is separated by comma. The first one and second data item can have different
meaning against various procedures. Other than these differences, all the rest of
information shares the same properties.
Page 1
3.1.2 The first two data items in SID TRANS procedure file
First data item: Allows string combination such as A~Z and 0~9. And
the maximum length of each string is 12 characters. It stands
for the name of one SID TRANS procedure, which used for
displaying on the DEP ARR and RTE pages.
Second data item: Allows string combination such as A~Z and 0~9.
And the maximum length of each string is 12 characters. It
stands for the name of the SID procedure which corresponding
to this SID TRANS procedure. Used for displaying on the SID
TRANS and SID pages.
Starting from the third data item, they are all universal data formats. Please refer
to chapter 3.2.
Page 2
Page 3
Page 4
Universal data item 6: All three numbers indicates the heading of this waypoint
(in degree format). The heading digits must be provided with all three numbers. If it
is 000, it means the FMC will calculate this heading automatically. Using 360
instead of 000, if you want to be heading for north.
When the universal data item 7 is 0 and the Universal data item 5 is 3, the
universal data item 6 indicates the radial when finish the leg.
When the universal data item 7 is 0 and the Universal data item 5 is 4, the
universal data item 6 must be set.
The prefix L or R can be added to specify the direction of turn..
L: Turn left
R: Turn right
Universal data item 7: It is a flag which indicates whether this waypoint is a
conditional point.
0: It is not a conditional point.
1: It is a conditional point.
Universal data item 8: It is a flag which indicates whether this waypoint needs
speed constraint.
0: It does not needs speed constraint.
1: It need speed constraint.
Universal data item 9: Speed (knot). If the universal data item 8 is 1, the
FMC will use universal data item 9 as place to store the speed constraint data. If the
universal data item 8 is 0, it means the FMC will calculate this speed automatically.
Universal data item 10: It is a flag which indicates the type of altitude
constraints on this waypoint.
0: No altitude constraints.
1: Lower than altitude (E.g., FL120B, 3000B shown on CDU)
2: Higher than altitude (E.g., FL120A, 3000A shown on CDU)
3: Within altitudes (E.g., FL120AFL150B, 3000A5000B shown on CDU)
4: Pass altitude (E.g., FL120, 3000 shown on CDU)
Universal data item 11: The numbers indicates the altitude (In feet format) of
the constraint.
When universal data item 10 is 0: Only 0 (zero) is allowed to input.
When universal data item 10 is 1: Input altitude constraint (in feet format)
When universal data item 10 is 2: Only 0 (zero) is allowed to input.
When universal data item 10 is 3: Input the upper bound of altitude constraint
(in feet format).
When universal data item 10 is 4: Input altitude constraint (in feet format)
Universal data item 12: The numbers indicates the altitude (In feet format) of
the constraint.
When universal data item 10 is 0: Only 0 (zero) is allowed to input.
When universal data item 10 is 1: Only 0 (zero) is allowed to input.
When universal data item 10 is 2: Input altitude constraint (in feet format)
When universal data item 10 is 3: Input the lower bound of altitude constraint
(in feet format).
Page 5
Page 6
Page 7