OnCourse Software

Got ATIS for VIDP in cruise which told me rwy in use was 09 - prepped for that. On approach, told to expect rwy 27, so set up for that instead. On downwind for 27, told clear for ILS rwy 10.

Landed rwy 27 without clearance or any other intervention from ATC.

This is with STARs active as last night I did a flight without this ticked and ATC had me at 240 knots at 1000' radio for 30 miles eventually overflying the AD at a strange angle before about ten minutes later putting me on a 20nm intercept, so thought I'd do it myself this time. Alas.

Log file is >10mb so here it is - https://we.tl/t-Qjhc4mL98G

Thanks

Forgot to mention also - not sure if there's anything there in the log representing this, but the keybinding CTRL+SHIFT+W (change runway) didn't have any effect for some reason

Firstly, you would have been able to upload your log directly to the forum if you had first made it a zip file, as highlighted above (size then ~1.6MB).

The final runway assignment was determined by the AI traffic at VIDP which was using Rwy 10; to avoid traffic issues, PF3 will generally use that information to override a weather-based runway selection (which would have been runway 27, as previously indicated) - that change takes place on the handover to Approach. The set-up of your PF3 flight plan wasn't ideal for runway 27 anyway, it was based on an approach for runway 11L.

I have been looking at how we might better handle STARs to allow for runway changes, so here's an idea on how you might improve things at the moment:

The BAVOX6x approaches cover all of the various runways and share a path until waypoint SAPLO; ideally this would be set as your approach handover point (STAR exit), but this is quite a way out, so you should choose FS711 or DP504 instead (depends on STAR being used) - the altitude at this waypoint should probably be set to 3000 as that is the minimum needed there if landing on runways 27/28/29L/29R. And I would set waypoint BUKLO as your STAR entry point; you then need to remove all of the waypoints after FS711/DP504 as these aren't needed by PF3 and will vary dependent on final runway assignment.

Update:
Here is a copy of the BAVOX6x STAR chart for VIDP, and a couple of screenshots showing how I would set this up: If you set the STAR data for VIDP like this PF3 will use the correct STAR name when assigning the runway: This is how I would set the STAR entry point and altitudes before waypoint deletion: And this is what the final flight plan used by PF3 would look like after deletions: You'll see that I deleted the first waypoint, BBM, as it is not needed, and also the waypoints between DP504 and VIDP (DP608, DP609 and FS811).

I would be interested in your feedback if you decide to give this a try - you should have time to reset your arrival if the runway changes when being handed over to Approach.

I couldn't see why your Ctrl-Shift-W request for a runway change didn't work, but it may not have been available when you requested it.

Hope this helps,
Martin

Just a thought . . . when I first started using PF3, I could never get Ctrl-Shift-W to work - I suspected it clashed with other add-ons. I re-assigned it to Ctrl-Shift-R and it has worked perfectly ever since.

That might be worth a try if Ctrl-Shift-W doesn't ever work for any of its functions (it should also skip a TGS waypoint and warp to a flight waypoint).

John

Hi both - thanks very much for the detailed information, I'll bear this in mind on future flight plans - think I'm still getting to grips with the way PF3 is 'thinking' and interpreting the plans I inject into it.