OnCourse Software

Please kindly explain why Westbound flights (i.E LOWW to EDDS ) are to be flown on uneven
fligtlevel such as 270 0r 290 when according to my knowledge even has to be used.I filed
flightlevel 280
Thnks nd brgds
Bernhard

PF3 does not know anything about this, it uses the cruise altitude from your flight plan.

Bernhard48 wrote: *

Thu Feb 02, 2017 5:31 pm

Please kindly explain why Westbound flights (i.E LOWW to EDDS ) are to be flown on uneven
fligtlevel such as 270 0r 290 when according to my knowledge even has to be used.I filed
flightlevel 280
Thnks nd brgds
Bernhard

As Thomas says PF3 uses your fpl information. So it's your fpl software that has given PF3 the incorrect information. Fpl software both payware and freeware is notoriously iffy on many ocassions. You "always" need to check what is generated.

The way i understand do you mean that by use of VROUTE flightplanner were i set a flightlevel of 280 and Export same
to PF3 , were it is clearly seen that Level 280 is filed , an uneven will be demanded by ATC? Sorry but this is really strange.

Bernhard48 wrote: *

Fri Feb 03, 2017 6:02 pm

The way i understand do you mean that by use of VROUTE flightplanner were i set a flightlevel of 280 and Export same
to PF3 , were it is clearly seen that Level 280 is filed , an uneven will be demanded by ATC? Sorry but this is really strange.

No. If your flightplan is set up for FL280 cruise, that is what PF3 will give you. There must have been an error in your flightplanner. Can you find the original sim fliightplan that you created with VROUTE and zip it up and post it on here. If you include in the zip the contents of PF3 folder Flight, that will help too.

In addition to what Peter has suggested, you can also zip and attach the debug_monitor.log (located in the PF3\Logs directory) for the flight, if you still have it available. This should show your filed altitude as well as altitudes to which you were cleared en route.

Thnks fr your support, please find attachment u hve req.

Code: Select all title=LOWWEDDS description=LOWW, EDDS type=IFR routetype=2 cruising_altitude=28000

I only took a fast look at the debug log. The cruise altitude from your flight plan was FL280, but it looks like all of the waypoint altitudes on the FP adjustment page have been adjusted, with the cruise altitude changed to FL290. Did you adjust the altitudes for all of the waypoints? Reload the flight plan and check the altitudes on the FP adjustment page. Also note it is recommended that you leave the altitude for your first waypoint set at your cruise altitude and let PF3 handle the step-climbs (see p. 72 of the User Guide).

If you delete the altitude adjustments on the FP adjustment page, your assigned cruise altitude should be exactly what you filed in your flight plan.

Dan77 wrote: *

Sat Feb 04, 2017 3:04 pm

Code: Select all title=LOWWEDDS description=LOWW, EDDS type=IFR routetype=2 cruising_altitude=28000

I only took a fast look at the debug log. The cruise altitude from your flight plan was FL280, but it looks like all of the waypoint altitudes on the FP adjustment page have been adjusted, with the cruise altitude changed to FL290.

Odd thing is though Dan, there is nothing in his FPP folder that indicates that a change to FL290 was made ?

pschlute wrote: *

Sat Feb 04, 2017 5:02 pm

Odd thing is though Dan, there is nothing in his FPP folder that indicates that a change to FL290 was made ?

Agreed, but the altitudes for all the waypoints have been changed.