Got this off flightawarehttp://flightaware.com/live/flight/UPS65MDO 5500N 14100W 5000N 13700W 4500N 13200W REDWD AMAKR OAK J1 AVE PMD ZIGGY4I put that into fsbuild and it went crazy. I guess I translate those coordinates to a different format that the fmc can understand?

Got this off flightawarehttp://flightaware.com/live/flight/UPS65MDO 5500N 14100W 5000N 13700W 4500N 13200W REDWD AMAKR OAK J1 AVE PMD ZIGGY4I put that into fsbuild and it went crazy. I guess I translate those coordinates to a different format that the fmc can understand?

Try:PANC MDO 5500N/14100W 5000N/13700W 4500N/13200W REDWD AMAKR OAK J1 AVE PMD ZIGGY4 KONT

Just looking at it quickly, it looks like the (5500N 14100W) (5000N 13700W) (4500N 13200W) is three waypoints that could be entered 55N141W; 50N137W; 45N132W, but I'm just guessing.CharlesEDIT Too slow! ;)

Try entering this into FSB:PANC SID MDO 5500N14100W 5000N13700W 4500N13200W REDWD AMAKR OAK J1 AVE PMD ZIGGY4 KONTThis should give you the correct TRANSAT waypoints.Regards

See also PMDG Ops article on WP Entry for shortcuts: http://ops.precisionmanuals.com/wiki/FMC_WP_Entry_Notes

I enter it as a raw co-ordinate to the LEGS page RTE page Try this:(5500N 14100W) = N55W141(5000N 13700W) = N50W137(4500N 13200W) = N45W132Dilip

This worked:PANC MDO 5500N14100W 5000N13700W 4500N13200W REDWD AMAKR OAK J1 AVE PMD ZIGGY4 KONTTake out the space between the N and W parameters since it is a coordinate pair. Make sure your airports are in the route box or selected in the airport boxes since they don't show in the paste from the flightaware route.You may also have to change the version of a SID or STAR to match what is in your FSB database as shown in the dropdown in each airport window if the SID or STAR does not expand. Free FSB AIRAC updates are on the fsbuild.com site.If you use the SID-STAR database in FSBuild and export to FS and the FMC, you'll be in sync with ATC. If you use the FMC DEP/APPR database it may not match what you exported to FS and you might have ATC synch problems. I always use the APP approach (runway right side on APP page) either way once the destination runway is announced.You also have the option depending on how you are using ATC to just include the transition points in your exported plan to the FMC and FS and the use the SID-STAR FMC database.

MDO 5500N 14100W 5000N 13700W 4500N 13200W REDWD AMAKR OAK J1 AVE PMD ZIGGY4In 747-400 language this isMDO N55W141 N50W137 N45W132 REDWD AMAKR OAK J1 AVE PMD ZIGGY4Please note: The Lat/Long waypoints must be inserted in the LEGS page and not the RTE page for this to work.In MD-11 language this isMDO N5500.0W14100.0 N5000.0W13700.0 N4500.0W13200.0 REDWD AMAKR OAK J1 AVE PMD ZIGGY4

Can you explain why it should be entered into the legs page of the 747? Thank you everyone for your help

Please sign your name to posts in this forum.The RTE page is useful for stringing together airways and named fixes, but you have to use the LEGS page to enter unnamed/derived waypoints.

Why do you have to? I have programmed nat tracks above into the route page and it worked fine. Alex

Okay, I am wrong on this one. You only need to use the LEGS page to enter derived waypoints. Good, thanks for pointing that out.

Got this off flightawarehttp://flightaware.com/live/flight/UPS65MDO 5500N 14100W 5000N 13700W 4500N 13200W REDWD AMAKR OAK J1 AVE PMD ZIGGY4I put that into fsbuild and it went crazy. I guess I translate those coordinates to a different format that the fmc can understand?

See also PMDG Ops article on WP Entry for shortcuts: http://ops.precisionmanuals.com/wiki/FMC_WP_Entry_Notes

I know this is a dead horse...Using the link Dan provided, you can also enter the Latitude/Longitude waypoints as follows:55N41 for 5500N 14100W50N37 for 5000N 13700W45N32 for 4500N 13200WIt would save you a little bit of typing.Steve W.

Related question: is it possible to put an AR into the FMS in the 744? I did a flight from JFK to MIA, and a chunk is over the atlantic on AR22 (and others) the FMS said my AR22 entry for via was invalid. Is there a trick, or is that not in the model? Thanks in advance.Doug O.

Tip: Look in navdata file wpNavRTE.txt for any questions reqarding airway fixes. The airway use in the FMS requires that you start and end on a fix that is defined for that airway. The fixes for AR22 are:AR22 001 RB 74.746892 -94.995147AR22 002 YHK 68.626072 -95.858334AR22 003 YBK 64.318889 -96.104722AR22 004 YRT 62.813920 -92.117464AR22 005 DIW 34.568533 -77.452933AR22 006 SEELO 32.023408 -78.256953AR22 007 JENKS 30.635358 -78.695442AR22 008 HOAGG 29.784364 -78.842736AR22 009 BGDOG 29.293492 -78.908264AR22 010 JORAY 28.342814 -79.034967Note that this defines two segments in the world known as AR22 unless it actually connects between YRT and DIW.