hi all, i am looking for some help. i am trying a route over the pond for the first time using Routefinder.asalink. i am flying the md11 and the route is from egpf(glasgow) to kjfk(Kennedy) the route in the FMC is ok to the waypoint PIKIL after which lat.long takes over and the lat.long. is 57N020W, 57N030W, 56N050W, 53N050W, but i cannot get the FMC to accept these numbers, i get messages in the scratchpad saying not allowed, not in database, and i referred to the download pmdg md11 fms preflight pages but could not find any reference to the installing of lat.long in the FMC but there is a reference relating to Place/Bearing/Distance lat.long which i dont know if this couples up with the FMC. routing. anyone with suggestions would be gratefully acknowledged. richard welsh.

Hi,check MD-11 manual FMS.100.4

57N020W, 57N030W, 56N050W, 53N050W

So, those should be insert into the FMC like this:- N5700.0/W02000.0- N5700.0/W03000.0- N5600.0/W05000.0- N5300.0/W05000.0And than FMC will show 57N020W, 57N030W, 56N050W, 53N050W in the F-PLN page.Hope I helped :( Gr, Aljaz Prislan

Hi,check MD-11 manual FMS.100.4So, those should be insert into the FMC like this:- N5700.0/W02000.0- N5700.0/W03000.0- N5600.0/W05000.0- N5300.0/W05000.0And than FMC will show 57N020W, 57N030W, 56N050W, 53N050W in the F-PLN page.Hope I helped :( Gr, Aljaz Prislan

hi Aljaz, copied down your numbers and tried installing, got message not allowed, thanks. richard welsh

hi Aljaz, copied down your numbers and tried installing, got message not allowed, thanks. richard welsh

Just type: 5720N 5730N and so on RGDS

hi all, i am looking for some help. i am trying a route over the pond for the first time using Routefinder.asalink. i am flying the md11 and the route is from egpf(glasgow) to kjfk(Kennedy) the route in the FMC is ok to the waypoint PIKIL after which lat.long takes over and the lat.long. is 57N020W, 57N030W, 56N050W, 53N050W, but i cannot get the FMC to accept these numbers, i get messages in the scratchpad saying not allowed, not in database, and i referred to the download pmdg md11 fms preflight pages but could not find any reference to the installing of lat.long in the FMC but there is a reference relating to Place/Bearing/Distance lat.long which i dont know if this couples up with the FMC. routing. anyone with suggestions would be gratefully acknowledged. richard welsh.

Try 5720N 5730N 5650N and 5350N. RalfTom was quicker. :-) Ralf

See also: http://ops.precisionmanuals.com/wiki/FMC_WP_Entry_Notes

hi everyone, to the guys who gave me the numbers, i tried putting them into the scratchpad one set at a time but i still got the message not in database or not allowed, for example 5720N into lsk3L, I have every confidence in routefinder routes so i dont know where the problem lies, to Dan Downs i will have a look at the link you provided. thanks all. richard welsh

hi everyone, to the guys who gave me the numbers, i tried putting them into the scratchpad one set at a time but i still got the message not in database or not allowed, for example 5720N into lsk3L, I have every confidence in routefinder routes so i dont know where the problem lies, to Dan Downs i will have a look at the link you provided. thanks all. richard welsh

May be a sreenshot can help?!

hi everyone, Tom Morello suggested screenshots of the FMC, that might help with an answer. richard welsh

Richard, don't use the AIRWAYS page to enter fixes... use NEXT WPT on the LAT REV page instead of AIRWAY.The airway entries require a named airway and named fixes on that airway, and are stored in navdata file wpNavRTE.txt; if the airway/fix isn't in that file, it won't be accepted.The fix entries that can be directly inserted with the NEXT WPT key must match a fix named in the wpNavFIX.txt navdata file; if the fix isn't in that file, it won't be accepted. If you view that file you will see that all the short entries for lat/lon such as 3010N are in that file, and that is why the shortcuts work.

Richard, you need a LAT REV from your last fix - then input WPT xxxxN. You've tried to add a waypoint as an airway hence the not found/allowed.Look near the end of the FMS guide for the MD-11, it's there.Damn, too slow lolJohn Ellison

Pics say more than... :( Is it working now?Enjoy your NAT x-ing!

Pics say more than... :( Is it working now?Enjoy your NAT x-ing!

hello everyone, many thanks for all the replies, John and Dan hit the answer on the head. going into lat rev instead of going into Airways enter the lat.long into the box below =next waypoint- . its easy when someone else knows the correct procedure. richard welsh