January 22, 201412 yr Hi everybody. This is the first time I am flying a route from Europe to North America, and I ran into a problem. Here is the route from EGKK - KBOS. EGKK SAM1X SAM L620 GIBSO UN514 DIDEL UL149 MERLY UL22 MOPAT DCT MALOT 5420N 5530N 5440N 5250N CRONO DOTTY N162B TOPPS J581 ENE ENE.OOSHN2 KBOS The FMC in my iFly 737 won't accept "5420N 5530N 5440N 5250N" as waypoints. Are these even waypoints I need to program into my FMC or something else? Also the star "ENE.OOSHN2" the FMC can't find. I hope you can help me! - Nikolas FSX-SE
January 22, 201412 yr Author - I use Vroute for this route. I usually use Vatroute.net or Simroutes.com FSX-SE
January 22, 201412 yr I don't have the iFly, so just a guess, try N54W20 etc OOSHN2 is a valid arrival, are you adding it via the Dep/Arr page? You would need to add the arrival there, then select ENE as the trans. Barry Friedman
January 22, 201412 yr Author Thanks for the reply! I'll let you know if it worked, when I've tried later tonight or tomorrow. FSX-SE
January 22, 201412 yr Author Hi again. The arrival "OOSHN2" worked fine, thank you! N54W20 didn't work though. I have no idea what to enter and what exactly this is :-S FSX-SE
January 23, 201412 yr 5420N 5530N 5440N 5250N The 737 fmc only accepts this format in the LEGS page, so make sure you aren't in RTE N54W020 N55W030 N54W040 N52W050
January 23, 201412 yr I see the answer on page 387 of the Operations Manual. Do you have the Ops Manual? dv Win 10 Pro || i7-8700K || 32GB || ASUS Z370-P MB || NVIDIA GeForce GTX 1080 Ti 11Gb || 2 960 PRO 1TB, 840 EVO My Files in the AVSIM Library
January 23, 201412 yr Good reading for trans-Atlantic flights: http://library.avsim.net/search.php?SearchTerm=Michikian+Krikor&CatID=root&Go=Search The points are lat/long coordinates for a North Atlantic Track (NAT). 5420N is North 54 W 20 N162B is a standard North American Route (NAR): http://www.nyartcc.org/pilotcenter/narsw In this case: DOTTY (Direct 264°/071° 581 NM) TOPPS Barry Friedman
January 23, 201412 yr Author I figured it out, thanks guys! I entered N52W020 N55W030 and so on. - Nikolas FSX-SE
January 23, 201412 yr Author I figured it out, thanks guys! I entered N52W020 N55W030 and so on. - Nikolas FSX-SE
Create an account or sign in to comment