I am taking a trip to EGLL soon and would like to replicate a real-world flight plan in AirTrack FMC beforehand, but am getting stuck with the LATLON coordinates that are found on sites like Flightaware. Any guidance on how to manually input into the FMC would be appreciated!

Flight plan:
ORCKA5 LAS Q70 BLIPP Q842 WINEN FFU BIL RUDVI 5300N/10000W 5830N/09000W RONPU TEFFO BERUS KETLA 6200N/05000W 6030N/04000W 5900N/03000W 5700N/02000W PIKIL SOVED LUTOV KELLY L10 WAL UY53 MOGTA UY53 NUGRA NUGRA1H

P.S. the “World Routes” that are auto pulled from VATSIM input seems to fail

Hi,

I'm sorry, I need to look into the decoder which doesn't seem to support the format of 6200N/05000W, 6030N/04000W and such likes currently. I'll add it to the ToDo list to see if this format can be added / supported.

One option is to create these points manually as custom waypoints; the 5300N/10000W should be 53 latitude -100 longitude, the 5830N/09000W should be 58.5 latitude -90 longitude and so forth.

You can do this either here on the air account under routes, or in the app. Select KLAX as departure, EGLL as destination.

ORCKA5 is the SID and NUGRA1H is the STAR I believe. So your plan would be:

LAS Q70 BLIPP Q842 WINEN FFU BIL RUDVI 5300N/10000W 5830N/09000W RONPU TEFFO BERUS KETLA 6200N/05000W 6030N/04000W 5900N/03000W 5700N/02000W PIKIL SOVED LUTOV KELLY L10 WAL UY53 MOGTA UY53 NUGRA

Replacing the ones that can't be decoded by custom ones.

Alternatively if you use the Navigraph data, it comes with a set of waypoints for fixed coordinates.

5300N/10000W = 53N00
5830N/09000W = N5390
6200N/05000W = 6250N
6030N/04000W doesn't seem to exist AFAICS
5900N/03000W = 5930N
5700N/02000W = 5720N

Hope this helps,
Sorry for the limitation,
Joao @ haversine

Thanks Joao

Is there a place to look up the translation from the long LATLON coding to what Navigraph has in its AIRAC?

Best,

I think and it looks like Navigraph/Jeppesen is following the ARINC 424 naming convention (7.2.5) for encoding positions of oceanic North Atlantic waypoints for NATS.

These are meant to be used in the FMS, they are encoded with 5 characters. Roughly it goes like this:

“N” for North Latitude and West Longitude
“E” for North Latitude and East Longitude
“S” for South Latitude and East Longitude
“W” for South Latitude and West Longitude

- Two digits for latitude first and then 2 digits for longitude.

- For longitudes lower than 100 the character comes first, for longitudes higher than 100 the character comes after the longitude digits.

- It then varies a bit for half degree latitudes. In this case the character goes before latitude if half latitude and longitude lower than 100, and on the second character if half degree and longitude higher than 100.

Bear in mind that not all points are present. I guess they only encoded the ones used in NATS. For instance the 6030N/04000W from your example should be encoded as: N6040 since it is a half degree latitude and longitude lower than 100, but it doesn't seem to be present in the latest navdata set. I guess this is what Jeppesen puts there.

A quick google for ARINC 424 oceanic waypoints returned these which might help:

https://code7700.com/arinc_424_shorthand.htm

https://skybrary.aero/sites/default/files/bookshelf/4309.pdf

Also although unrelated, bear in mind that NAT tracks change everyday so a route one day will be different from the route for the next day.

hope this helps,
joao