FMS not tracking flight.
I thought I had the problem with my FMS sorted but today I have spotted a really weird problem that stops my FMS working. I am using P3Dv4.5 on windows 10. Today I flew from EGNX (East midlands UK) to EGPB (Shetland). So EGNX>TNT 18.2 nm. TNT>SAB 172.2 nm. SAB>ADN 84.2 nm. ADN>SUM 157.1 nm. SUM>EGPB 0.3 nm. This is from the default flight planer in P3D. But when I enter the waypoints into the FMS it reads as follows. EGNX, TNT 2841 nm, SAB 3095 nm, ADN 157.1 nm, SUM 0.3 nm.
This throw the fuel computer out and I can not fly in LNAV. Any ideas as to what is wrong? Using the LIST function is no use as the waypoint aren't any page. Despite this I am still enjoying the 146.
Hi @old-john, looks like the FMC may be pulling up the wrong 'TNT' waypoint, and that's throwing out your flightplan. It could possibly be an issue with your navigation database - which nav database are you currently using? When you turn the FMC on the initial page (showing position, date etc) should also tell you when the nav database expires, though given the Trent VOR is significantly older than I am and I'm no spring chicken, you shouldn't necessarily need the latest navigational data for this to work correctly.
For reference, I use payware Navigraph data (AIRAC version 2109, expires 6 October 2021), and I've tried your example - after inserting EGNX as the first entry on the FPL page, pressing 'list' presents a list of all navaids and waypoints in the area (27 pages of them in fact!) - TNT is the first entry in the 'VOR' section.
Alternatively, if the 'List' function isn't working for you, typing TNT directly into the FPL page should give you four potential candidates in order of distance (nearest first) - Trent, Trento, Toncontin and Tachikawa. To avoid confusion, nav points sharing the same initials are typically placed well away from each other so the accompanying lat/long co-ordinates, and the distance and direction to the waypoint shown in magenta on the FPL page, should serve as a sense check.
In this case, the TNT we're looking for is 'Trent' (N53 3.2, W001 40.2) which is indeed 18.2nm from EGNX.
I'm not sure which version of the 146 you're currently running but it may be worth uninstalling and deleting the accompanying folders and then reinstalling the latest version (v1.7) again to see if this problem persists?
@geordie Hi Geordie.
I am running the latest version of the 146, and my Navigraph cycle is AIRAC 2109. Today day I thought I'd try using the active sky flight plan and putting that data into the FMC. EGPB>TNT>LEE>SAB>ADN>KWL>EGPB. Everything is fine until I input SAB it the gives 2108.2nm. So I tried again but missing out SAB and going from LEE to ADN that's ok. But of course it would not have flown the flight path. I'll give it a try tomorrow.