OnCourse Software

Ok, thanks for the reply. That explains it, but I think that when the program adds waypoints that are not in the flightplan, it should recalculate them too should the altitude of airway waypoints be altered. As a user I am not interested in the added waypoints. I hope this can be part of a future ...

I added the old debug_monitor file as I believe I deleted the original when opening PF3 again after the flight to check altitudes. It seems PF3 is maintaining the altitudes it originally calculates. the 5th XXX waypoint is only 7 miles from BOOTH and was set at FL340 by PF3. I changed BOOTH from ...

The descent instructions were correct as you had set the altitude for BOOTH to 20,000'. VITEV was not ignored as such but it was only 6 miles from BOOTH so a little too close to be of much help Ok, I did not see BOOTH as the approach charts do not mention a specific altitude for BOOTH. It does ...

The descent instructions were correct as you had set the altitude for BOOTH to 20,000'. VITEV was not ignored as such but it was only 6 miles from BOOTH so a little too close to be of much help Ok, I did not see BOOTH as the approach charts do not mention a specific altitude for BOOTH. It does ...

Attached the log file of a flight from CYYC to CYVR. About 250 miles out of CYVR ATC already instructs to descent to FL200 and maintains that for over 100 miles. Great for sightseeing but not for fuel consumption.... :D It ignores the manually added FL210 at VITEV and I am not sure if it really ...

Ok, thank you. i ignored ATC today, so that will not be a fair observation. Next flight I shall send the log files.

I have been using PF3 for a week now and I am puzzled as to how to get ATC make me descent to the right altitudes for a STAR. I import my flightplan into PF3 and then I adjust the altitudes as per the approach charts. In most cases PF3 intents to maintain a much higher flight level then in reality ...

Same issue here, solved it!

Thanks
Menno