OnCourse Software

A320Flyer wrote: *

Mon Jan 22, 2024 7:21 pm

Hi Dave,

On my last few flights, I have been given instruction to reduce speed to 260kts whilst still above FL130, sometimes as much as FL180. Both the attached sets of logs it happened. I'm not certain of IRW, but this doesn't seem very realistic?

On today's flight, I was given a SID for RW28, but told to taxi to RW10!! Also on approach, I was directed towards the Localiser, but was not cleared for it. After passing through it, cleared to land was given about 10 miles later. By this time, I had to divert due to an approaching mountain, so ignore anything that happened after that (I had to land on the opposite runway ;-(.

Cheers
Bill

Logs210124.rarLogs220124.rar

2024-01-23_131842.jpg (95.53 KiB) Viewed 1996 times

2024-01-23_133034.jpg (243.19 KiB) Viewed 1996 times

A320Flyer wrote: *

Mon Jan 22, 2024 10:08 pm

Hi Dave,

On tonight's flight, instructed to reduce speed whilst at FL200. Then cleared for the localiser whilst still at FL150. I had to pass through the localiser, circle around whilst I lost altitude, and approach from the other side.

Bill

Logs.rar

Quote:

I used SimBrief as usual. I don’t normally alter any of the altitudes and Pf3 handles the step descents fine.

Quote:

Some changes to the following which was released in Beta 3.21.88

OLD
-----
ADDED a new option to the Advanced Options page called 'Flight Plan Filter'. Basically this option provides a means by which you can use a flight plan, containing a SID and/or a STAR, which you would normally load into your flight plan and PF3 will remove the SID (except the SID exit waypoint) and the STAR (except the enstry waypoint). Currently it's quite difficult to load most SIDs/STARs into PF3 as most of the waypoints are very close together, so you can end up have two flight plans... one for your FMC and the other for PF3. Full details for this option are provided in the updated PF3 User Guide

NEW
-----
ADDED a new option to the Advanced Options page called 'Flight Plan Filter'. Basically this option provides a means by which you can use a flight plan, containing a SID and/or STAR, which you would normally load into your FMC and PF3 will remove the SID (except the SID exit waypoint) and the STAR (except the entry waypoint). Currently it's quite difficult to load most SIDs/STARs into PF3 as most of the waypoints are very close together, so you can end up have two flight plans... one for your FMC and the other for PF3. The SID exit point altitude will be retained from your original flight plan, as will the altitude for the STAR entry point. The descent profile will also be retained from the original flight plan but PF3 will continue to put your cruise altitude into the first waypoint following your SID exit point (if included), upto and including the original flight plan's TOD. You will not be able to alter any of the altitudes from within PF3 when loading such a flight plan as we've had many users voicing their desire for PF3 not to change their flight plan, especially the descent profile. Full details for this option are provided in the updated PF3 User Guide.

In addition to the above you can also load a flight plan containing no procedures at all when this Flight Plan Filter option is selected and in that scenario PF3 will again enter your cruise altitude in the first waypoint and all those waypoints upto and including your original flight plan's TOD. The descent profile will remain unchanged. When using such a flight plan (with no SID and STAR) you will be able to adjust your altitudes as you can now.

This feature will only work with a valid flight plan. Basically that means it should be in XML format and each waypoint should have a valid altitude, so default FS9 or FSX flight plans would not be valid. The former as it's not XML and the later as the XML file does not include waypoint altitudes.

A320Flyer wrote: *

Tue Jan 23, 2024 5:59 pm

"PF3 will continue to do so but you would have to turn the 'Use Filtered Flight Plan' OFF"

I clearly didnt fully understand the implications of using this filter.