APPTRANS is optional and can follow APP, just like STARTRANS is optional after the STAR.
APP and APPTRANS can be omitted if no instrument approach is desired. If any off APP or STAR is set, the DESRWY is required! STAR and STARTRANS can be omitted if no arrival is desired. It is similarly structured to the departure block and can include destination airport, runway, arrival, arrival transition, approach and approach transition: ADES KRDU If the flightplan starts at a point other than an airport the departure block looks like this: DEP CTFĬTF in this case represents a VOR, more precise information on this point is then given in the enroute section of the flightplan. If no departure procedures are available or no loading of a procedure desired, the DEPRWY line can be omitted. If the departure has no transitions, the SIDTRANS line can be omitted. If no departure procedure is part of the flightplan, the SID and SIDTRANS lines can be omitted.
Optionally, the lines for departure runway, instrument departure and transition can follow: DEPRWY RW14 In case of an airport, the departure block will look like this ADEP KGSO Next is the departure block, which can be either an airport or any named point in the X-Plane nav database. It is given as a four-digit number: CYCLE 1710 This line is mandatory as the third line of the file. Next is the AIRAC cycle number of the cycle the file was created with. The currently supported versions are 3 (legacy, not written but still loaded by X-Plane 11) and 1100 (current).
Since this is a plain text file with no binary data, there’s no difference between ‘I’ or ‘A’ as the first line. Spaces or tabs are allowed as whitespace.
#Create flight plan xplane 11 windows#
fms file is a text file – Unix or Windows line endings are legal and the character set should be UTF-8. Flightplan files must be located in the Output/FMS plans/ directory.
0 kommentar(er)
