When I’m landing at a busy airport w/ IFATC, sometimes Tower instructs a last minute runway switch. Obviuosly that’s realsitic and understandable, but can also pose a significant approach challenge. Specifically, since I originally planned on RWY 16R at SYD, my NAV1 is tuned to the frequency for runway 16R ILS. I often manually adjust the NAV course to the heading stated on the approach chart (which has proven to be more accurate then the one autofilled by IF). I am prepared to manually fly to plan using the gs/LOC for reference. However, at ~8 nm out, before I even intercepted 16R glideslope, I was asked to switch to 16L, a runway near and parallel to 16R. Problem is now I has no LOC/glideslope reference, and also didnt intercept the “cone” for 16L at the same position I left 16R’s “cone.” I barely had the runway in sight and could not see the PAPI lights. I ended up landing well enough on 16L, but was low at 300 ft 5nm away from airport.
so after that whole context, why can’t we have a second runway (parallel) ILS tuned to NAV2 as a quick backup plan?
should I make a feature request for it?