X-Plane 11.10 can still load the following other, older formats of flightplans: This is an example of a valid v11 flightplan. The fifth and six columns are the latitude and longitude of the waypoint, given in decimal degrees and correspond to the fourth and fifth column of a v3. The fourth column is the required altitude in feet and corresponds to the third column in a v3. It can have the following values: ADEP/ADES for departure or destination airport of the flightplan, DRCT for a direct or random route leg to the waypoint, or the name of an airway or ATS route to the waypoint. The third column is the via/special column. The second column is the identifier of the waypoint, and corresponds to the second column in a v3. It is 1 for airport, 2 for NDB, 3 for VOR, 11 for named fix and 28 for unnamed lat/lon waypoints. The first column is the type of waypoint, and corresponds to the first column in a v3. The format is similar to the v3 flightplan, but adds a field for the via airway or other special rule of the waypoint. The waypoints listed can be either direct (DRCT) legs or via an ATS airway. This is the number of waypoints in the flightplan that are NOT part of an instrument departure, arrival, transition, approach or missed approach. It starts with the number of enroute waypoints: NUMENR 9 Next is the enroute block of the flightplan. RDU in this case represents a VOR, more precise information on this point is then given in the enroute section of the flightplan. If the flightplan ends at a point other than an airport the destination block looks like this: DES RDU The name of the approach must be given in the format of ARINC 424.18+, section 5.10. In this case, the loading of STARs prior to this approach is limited to STARs with non-empty trunk routes, as with no runway, no runway transition can be loaded. APPTRANS can be omitted if no transitions are available for the given approach or vector to final is desired.Īn exception to the above rule is a circling approach with no runway, in which no DESRWY will be set. 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.
#Skymaxx pro v3 in x plane 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)
