error message on b-777 fms while loading a lat long position on fix page.
Thread Starter
Joined: May 2016
Posts: 3
Likes: 0
From: delhi
error message on b-777 fms while loading a lat long position on fix page.
last flight i got fmc message "not in database" while trying to put a lat long 7020E on the fix page while crossing NAT though it took all the earlier wayoints smoothly as 7200E and 7320W. any one got this glitch any explanation.
Joined: Feb 2001
Posts: 6,729
Likes: 105
From: The Winchester
Just a wild guess but it there any possibility it's exactly "what it says on the tin" (to quote a UK TV advert)?
In other words is it possible the FMC database simply doesn't hold all short format lat/longs as waypoints.
In other words is it possible the FMC database simply doesn't hold all short format lat/longs as waypoints.
Joined: Sep 1998
Posts: 1,615
Likes: 1
From: wherever
Just a formatting problem. It didn't recognise it as a LL and searched the DB for a waypoint with the name. Check your FMS handbook for the correct format. Probably needs 3 digits for Longitude. or a N/S for the Lat.
Joined: Feb 2001
Posts: 6,729
Likes: 105
From: The Winchester
FE H.
For info some(?all) 777 FMC's certainly do allow a short format (5 character) naming convention for some lat/long entries, a couple of examples being:
N50 W040 coded as 5040N,
and
N70 W170 coded as 75N70
The convention over the placement of the alphabetical character is all important but my FCOM lists 5020E as being correct for N50 E020, so at first glance the OP's 7020E looks correct for N70 E020.
Edit to add:
Question for the OP: Did 7020E work OK as a waypoint on the legs page? If it did then I have no idea why you had your problem.
If it didn't then perhaps it's something to do with the fact that in the manuals this particular 5 character naming convention only comes up in the context of Oceanic Control reporting points. I may well be wrong but I recall being informed at some point that if you do enter way points in this manner the FMC doesn't construct them, it calls them up from the database (we certainly treat them as database waypoints for the purposes of route verification).
Given where N70 E020 is on the globe I wonder if my original reply in post #2 holds good and 7020E simply isn't held in the database. The answer might be found in the Nav data page.
For info some(?all) 777 FMC's certainly do allow a short format (5 character) naming convention for some lat/long entries, a couple of examples being:
N50 W040 coded as 5040N,
and
N70 W170 coded as 75N70
The convention over the placement of the alphabetical character is all important but my FCOM lists 5020E as being correct for N50 E020, so at first glance the OP's 7020E looks correct for N70 E020.
Edit to add:
Question for the OP: Did 7020E work OK as a waypoint on the legs page? If it did then I have no idea why you had your problem.
If it didn't then perhaps it's something to do with the fact that in the manuals this particular 5 character naming convention only comes up in the context of Oceanic Control reporting points. I may well be wrong but I recall being informed at some point that if you do enter way points in this manner the FMC doesn't construct them, it calls them up from the database (we certainly treat them as database waypoints for the purposes of route verification).
Given where N70 E020 is on the globe I wonder if my original reply in post #2 holds good and 7020E simply isn't held in the database. The answer might be found in the Nav data page.
Last edited by wiggy; 6th May 2016 at 12:06. Reason: Formatting
