Hello. I’ve been using Charts for many years now. Setting a polar route from PANC (Anchorage) to EGLL (London) I asked Charts to ‘Generate’ a route, which it did. But, the waypoint names would not be accepted by the PMDG 777-200 LR FMC saying ‘Not in Database’. These are the generated points… 74N32..77N18..8094N..8065N..7841N..7426N..7017N..6511N. Not sure how to correct these. Also, when I manually tried to find waypoints for this route, they seemed very sparse. Is that normal for this high altitude zone ?
Many thanks. Your products are brilliant and much appreciated. Bob Reardon
These are shorthand forms for latitude/longitude coordinates. Some of them exist as waypoints in the database, others not.
When you mean not accepted, do you mean you tried to type them manually into the FMC or did you use Simbrief import from the FMC instead?
If you use the default LIDO format, the navlog part of the briefing will list them in non-abbreviated form as well:
DCT 330 020 .83 216/068 M50 56.9 18.7
74N132W N7400.0 0002 ... 26 042 485 P067 P01
74N32 W13200.0 0144 ... 33 3056 552 2 318 .... ....
DCT 330 032 .83 234/078 M55 53.0 22.6
77N118W N7700.0 0030 ... 72 046 479 P076 M04
77N18 W11800.0 0214 ... 276 2780 555 1 334 .... ....
AWY FL IMT MN WIND OAT EFOB PBRN
POSITION LAT EET ETO MORA ITT TAS COMP TDV
IDENT LONG TTLT ATO DIS RDIS GS SHR TRP AFOB ABRN
FREQ
--------------------------------------------------------------------
330 108 .83 251/042 M55 49.5 26.1
ETP1 N7918.4 0028 ... 95 075 479 P038 M04
W10235.2 0242 ... 233 2547 517 1 330 .... ....
DCT 330 108 .83 251/042 M55 47.9 27.7
80N094W N8000.0 0011 ... 95 075 479 P038 M04
8094N W09400.0 0253 ... 102 2445 517 1 330 .... ....
NUUK FIR FIR
-BGGL N7959.0 0016 ...
W06744.9 0309 ... 271 2174
EDMONTON FIR
-CZEG N7959.0 0000 ...
W06733.9 0309 ... 2 2172
DCT 330 150 .83 302/013 M54 43.2 32.4
80N065W N8000.0 0021 ... 106 101 480 P009 M03
8065N W06500.0 0330 ... 26 2146 489 0 322 .... ....
DCT 350 163 .83 170/003 M51 38.3 37.3
78N041W N7800.0 0037 ... 108 130 483 M001 P04
7841N W04100.0 0407 ... 297 1849 482 1 312 .... ....
DCT 350 162 .83 152/013 M53 33.2 42.4
74N026W N7400.0 0041 ... 75 140 481 M012 P02
7426N W02600.0 0448 ... 322 1527 469 1 320 .... ....
350 166 .83 129/021 M50 31.9 43.7
ETOPS N7253.4 0012 ... 20 152 483 M021 P05
EXIT W02259.4 0500 ... 84 1443 462 1 303 .... ....
REYKJAVIK FIR
-BIRD N7119.5 0013 ...
W02000.0 0513 ... 109 1334
DCT 350 166 .83 129/021 M50 28.6 47.0
70N017W N7000.0 0013 ... 20 152 483 M021 P05
7017N W01700.0 0526 ... 99 1235 462 1 303 .... ....
DCT 350 163 .83 193/050 M47 23.2 52.4
65N011W N6500.0 0044 ... 20 154 486 M039 P08
6511N W01100.0 0610 ... 330 905 447 3 302 .... ....
You can use these for FMC input: 74N32 becomes 74N132W or if that doesn’t work then N74W132 should, I think.
If you use a different format, some of them still list the associated coordinates which you can reference to figure out what do enter:
N8000.0
W09400.0
…becomes N80W094 or 80N094W and so on.
Regards,
Tim
Hello Tim,
Thank you for replying.
I should have mentioned that I have the latest version of Msfs2024, Charts and PMDG 777-200LR loaded on a PC with Windows 10.
I start with Charts to make my plan but this time I use the Charts ‘Generate’ to get a plan, rather than manually selecting each waypoint.
I can then see the Charts map with the full plan showing: the origin A/P, the SID, all the waypoints, the STAR and finally the destination A/P.
I then load up FS2024/777 and manually enter the full plan into the FMC.
But each waypoint that was generated by Charts is rejected with the ‘Not in Database’ error message.
If I enter a waypoint that is shown on the Charts map from that high latitude area, it is accepted.
Ie. Charts listed a waypoint 8065N. Looking at the charts map, I can see 8066N and 8064N, but not 8065N.
Waypoint 8065N is rejected by the FMC, but the 8064N is accepted.
So I was wondering is charts generating a waypoint that is not in the database ?
I would like to add these manually to the Database but I would need to understand the layout and how to do that.
Or, how can I tell if I have the latest Database loaded, and if not , how can I load the latest.
Thanks for your examples. I will try them next time and let you know.
Thank you,
Bob
These are shorthand forms for latitude/longitude coordinates. Some of them exist as waypoints in the database, others not.
As you’ve discovered, 8066N and 8064N are in the database but not 8065N – indeed.
That doesn’t make 8065N “invalid” per se, although typically then you would use a non-abbreviated form like 80N065W or N80W065 as I explained earlier. Probably Navigraph Charts should do the same in this case.
If you use Navigraph Chart’s “Export” function, select “PMDG Flightplan”, save the file somewhere and open it in a plain text editor (e.g. Notepad), you will notice Charts automatically converts 8065N to the non-abbreviated form N80W065 in its export.
You could use the exported file as a reference to manually enter your route in the FMS, or you can actually use this file as a “company route” in the PMDG if you save it to the correct folder.
Unfortunately I am not sure exactly what the correct path is as I prefer to import directly from Simbrief, but in theory it should be somewhere like described in the following avsim forum post:
https://www.avsim.com/forums/topic/618709-where-is-the-pmdg-flt-plan-folder/
Regards,
Tim
Hi Tim,
Once again thanks for your quick reply.
I was thinking of what you said about entering IDs in a non-abbreviated manner and realized that PMDG FMS accepts that format.
I’ve got so used to entering IDs that I select off the Charts map, that I totally forgot about entering non-abbreviated formats.
I’ll give it a try and let you know.
Thanks for the tips about export/import, but I always prefer to enter the values manually.
Anyway, very much appreciated.
Bob
Hi Tim,
Just tried your suggestion and it worked.
I entered 8065N as N80W065 and it was accepted.
So now I can recreate a flight I took when I was 12.
Many thanks again,
Happy flying…
Bob