In essence, it has me flying from Magee to OY directly over the runway, performing a u-turn to CF25 and beginning the ILS approach. MSFS wont allow me to delete the OY waypoint. Both LittleNavMap and MSFS are using the same AIRAC cycle (2104).
Is there anyway to fix this? Or am I not doing it correctly??
Maybe different Airac versions between LNM und MSFS. Please try to update the LNM data. At the moment I don’t know exactly where it is, but must be somewhere in the Menu of LNM.
The Full Transition isn’t being well understood by the sim’s internal flight planning software. We’re hoping Working Title will fix this too as part of the Garmin updates on SU5 onwards.
The best bet for now is to build a VFR GPS Plan.
Put ML25 as your end point, work your way backwards to FF25, CF25 and MAGEE.
Follow the alt fixes at CF25 onwards for either the ILS Y or Z per LNM, verify the NAV radio is set to 109.9 and switch the FMS to LOC before CF25. I don’t know what the guidance will do past ML25, but you’d be close enough and at MDA most likely to disconnect and complete the landing anyway.
This kind of thing has happened to me before. In LNM, try including the initial approach fix as the last waypoint before loading the approach in the plan and see if that makes any difference when you import it into FS.
OK. LittleNavMap File Menu → Export Options → Enable Approaches, SIDs, STARs, Airways. I think this may fix the problem. Will have a play around to check…
EDIT: Seems to work for me with this fix! You can insert an approach in LNM but I now tend to leave out the approach in the initial plan and add it inflight via the Garmin when advised by ATC which approach to take.
