Could someone please help with the remaining waypoints of these 2 flight plans found on Flightaware.1.)V36 YVV J531 SSM NCA15 YNE NCA14 LITGO NCA14 GKN J124 BGQ NODLE2.)V34 YEE J556 YYB NCA31 KEBVA NCA30 BTT OTZ B244 UHMAAnd by the way for some reason, I did not have "UHMA" in the database?Thanks in advance,Ken

You might do weel by visiting the NGA website and download the high altitude enroute charts for Eastern Europe/Asia as well as the Pacific/Australasia/Antartica. In there you will be able to plot where you FlightAware plan left off.https://www2.nima.mil/products/digitalaero/charts.cfmI know how frustrating it sometimes is with FlightAware. Their flight tracking stops when the aircraft leaves US monitored airspace.

Try this plan:CYYZ DCT YMS J600 YSB NCA22 YSF NCA23 ALSAB NCA19 FAI J502 OTZ B244 UHMA G212 UHMG B337 ODORA B233 LANRI B916 AKOLA B233 DE B467 KAE G597 KARBU STAR RKSIWhere it says "DCT and STAR" insert your SID/STAR's.I use routefinder ( http://rfinder.asalink.net/free ) when generating international flight plans. You can also select any daily restrictions, etc. Enter your airports and you'll see the entire plan. You'll learn how to read it and enter it correctly once you see it.Usually you can figure out by the first waypoint in the flight plan what SID you might use, but you need to double check that and edit your plan accordingly sometimes.Finding SID/STAR's can equally be a major 'hunt'. Most of the times you can find them through VATSIM's or IVAO's division pages because those folks have found real world charts for the areas you're flying in.Hope that helps a bit more.

Thanks Ted. Thanks Jeff. Much appreciated.Ken

Ken, for whatever reason, the PMDG FMC does not accept 4 character waypoints that have the same name as an airport. The only places that this has caused a problem for me is over Russian airspace where the "UHHH" is the transition point from one airway to another. There is a workaround, but it is a bit cumbersome. If the real world FMC does this, then I am a bit baffled that it would allow such a thing. So I suspect, maybe wrongfully, that this is a shortcoming in the PMDG FMC.

>Ken, for whatever reason, the PMDG FMC does not accept 4>character waypoints that have the same name as an airport. The>only places that this has caused a problem for me is over>Russian airspace where the "UHHH" is the transition point from>one airway to another. There is a workaround, but it is a bit>cumbersome. If the real world FMC does this, then I am a bit>baffled that it would allow such a thing. So I suspect, maybe>wrongfully, that this is a shortcoming in the PMDG FMC.hmmmmmmmmmmm. Thanks Dan.

That 4 letter waypoint you're referencing may be a foreign airway which needs to go into the route pages not the legs pages.Just a guess.

>That 4 letter waypoint you're referencing may be a foreign>airway which needs to go into the route pages not the legs>pages.>>Just a guess.>>That's when I received the "Not in database" error, while programming in the routes page.

Just to be clear, it was the "airport" waypoint that it wouldn't accept? Try just leaving it out or using a VOR on the field.

>Just to be clear, it was the "airport" waypoint that it>wouldn't accept? Try just leaving it out or using a VOR on>the field.I did not have 2 selections appear, neither the airport or VOR station appeared as selections, just "Not in database."Ken

It may very well not be in the data base then. I think you can contact the makers of the navdata (here in these forums), if I'm not mistaken, and possibly have that info corrected, or you can also add it to your navdata somehow.

UHMA is an airway, but I believe it is one of the Polar routes.

>UHMA is an airway, but I believe it is one of the Polar>routes.Thanks for that info Ben.Ken