FS9 flight plan format (.pln file) - explanation anyone please?

[martinlest2 58]

This is a flight plan (.pln) from LSGG to EGMC, created by FS Navigator and exported to FS9:

 

[flightplan]
title=LSGG to EGMC
description=LSGG, EGMC
type=IFR
routetype=1
cruising_altitude=35000
departure_id=LSGG, N46* 14.28', E6* 6.53', +001410.76
departure_position=GATE 12
destination_id=EGMC, N51* 34.28', E0* 41.73', +000049.21
departure_name=Geneva
destination_name=Southend
waypoint.0=LSGG, A, N46* 14.28', E6* 6.53', +001410.76,
waypoint.1=DJL, V, N47* 16.26', E5* 5.89', +000000.00,
waypoint.2=TRO, V, N48* 15.07', E3* 57.79', +000000.00,
waypoint.3=BSN, V, N49* 11.30', E3* 3.39', +000000.00,
waypoint.4=BNE, V, N50* 37.49', E1* 54.43', +000000.00,
waypoint.5=DVR, V, N51* 9.75', E1* 21.55', +000000.00,
waypoint.6=EGMC, A, N51* 34.28', E0* 41.73', +000049.21,

 

This is one (different waypoints) automatically created from within FS9 itself:

 

[flightplan]
AppVersion=9.1.40901
title=LSGG to EGMC
description=LSGG, EGMC
type=IFR
routetype=1
cruising_altitude=35000
departure_id=LSGG, N46* 13.91', E6* 6.49', +001410.99
departure_position=GATE 12
destination_id=EGMC, N51* 34.46', E0* 42.12', +000049.01
departure_name=Geneva
destination_name=Southend
waypoint.0=, LSGG, , LSGG, A, N46* 13.91', E6* 6.49', +001410.99,
waypoint.1=, GVA, , GVA, V, N46* 15.24', E6* 7.93', +001410.76,
waypoint.2=LF, TRO, , TRO, V, N48* 15.07', E3* 57.79', +000388.00,
waypoint.3=LF, MTD, , MTD, V, N49* 33.16', E2* 29.37', +000396.99,
waypoint.4=LF, ABB, , ABB, V, N50* 8.11', E1* 51.28', +000220.00,
waypoint.5=EG, LYD, , LYD, V, N50* 59.98', E0* 52.72', +000030.00,
waypoint.6=, EGMC, , EGMC, A, N51* 34.46', E0* 42.12', +000049.01,
 

 

The main difference is that the values at the end of each line are not zero in the plan created by FS9, as they are in a flight plan exported to FS9 by FSNav. But what do those values actually represent? +00140.99 is the elevation at Geneva and +000049.01 that at Southend. But what do the numbers at the waypoints mean? As elevations they make no sense. And as all my FS9 flight plans have been created by FS navigator, does that mean, given all the zeroes in those, I have important data missing?

 

I ask (partly) because I use the FS9 flight plans in a 3rd. party ATC programme, PF3, and if elevation data is absent that is probably going to have repercussions (and may partly at least explain the problems I have with ATC in PF3 not giving me proper descent instructions).

 

Thanks!

[edetroit 933]

Your "other" waypoints are VOR's and the numbers at the end are the VOR altitudes.

 

Here is a pic of my beloved 742 flying your flight plan approaching the Troyes VOR (TRO)

 

You can see the Troyes VOR frequency and altitude in the Litton-72.

 

[martinlest2 58]

Thanks - yes, I selected the VORs myself to form the flight plan (in the first example). The data at the end is the altitude of the VOR beacon itself then (above sea level)? Does it matter that the numbers are all zero?

 

And so where does FS9 get the data about altitude when crossing the waypoints? Or does it not actually get this information at all (presumably not, as it doesn't figure in the flight plan!) and just climb and descend between the airport elevations and the cruise altitude?

 

That would mean step climbs programmed into FSNav will not be executed in FS9.

 

Odd that this is not clear to me after so many years at this hobby!

[edetroit 933]

The data at the end is the altitude of the VOR beacon itself then

 

Yes

 

 

 

Does it matter that the numbers are all zero?

 

No, waypoints other than VOR/NDBs will have 0 altitude with the FS flight planner. If you made the VOR/NDB alts zero you would still have a flight plan. In fact I'm pretty sure you could write in your own fictional waypoint (using text edit) and you would STILL have a flight plan. (meaning a waypoint that is not in the FS database)

 

 

FSNav will not be executed in FS

 

I have never used FSNav so I cannot comment.

[ubersu 78]

 

 

No, waypoints other than VOR/NDBs will have 0 altitude with the FS flight planner. If you made the VOR/NDB alts zero you would still have a flight plan. In fact I'm pretty sure you could write in your own fictional waypoint (using text edit) and you would STILL have a flight plan. (meaning a waypoint that is not in the FS database)

 

Ed is quite right - FS doesn't check to make sure a waypoint is in its database. That's why we can use up to date nav data and flight plans from external sources. FS also doesn't do anything with altitude data.

 

DJ

[edetroit 933]

...deleted
 

[martinlest2 58]

OK, many thanks