I am experiencing a consistent issue in both the default Microsoft Flight Simulator A320neo and the FlyByWire A32NX. Whenever I set up a flight and select an RNAV (GNSS) approach in the MCDU, the aircraft still behaves as if an ILS approach is active. Problem description: In RAD NAV, an ILS frequency is always present, even on cold & dark start. If I try to delete or change this frequency, it either returns automatically or gives a format error. After loading a route and powering the aircraft, the ILS frequency is always auto-tuned regardless of airport or runway. Even at airports or runways without ILS, the system still shows or uses an ILS frequency from another airport or previous state. Flight behavior issue: When I select an RNAV approach in the MCDU, the Flight Mode Annunciator never shows FINAL APP. Instead, when pressing APPR, the aircraft always enters ILS logic: LOC (armed and captured) G/S (armed and captured) There is no indication of RNAV vertical guidance at any point. What I expected: For RNAV approaches, I expect FINAL APP mode instead of LOC/G/S. ILS frequencies should not affect RNAV approach logic. RAD NAV should not remain “locked” to an ILS frequency across flights. What I have already tested: Happens in both default A320neo and FlyByWire A32NX Happens on cold & dark starts Happens at multiple airports and different routes Happens even when selecting RNAV-only approaches Summary: It seems like the aircraft is permanently defaulting to ILS approach logic and auto-tuning ILS frequencies regardless of selected RNAV procedures. I am unsure whether this is: a nav data issue, a simulator assistance setting conflict, or an avionics state persistence bug. Any guidance or fix would be appreciated. Thank you.