Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

NGX FMC distance calculations wrong involving high lattitudes?

Featured Replies

I've just run into a bit of a snag on a flight from CYWG to a fictional airport I created in the arctic, just north of N78*... The total distance the FMC is calculating is about 450nm longer than the FSX flight planner is giving me, and the total sum of the individual leg distances on the LEGS page when I manually add them.

 

When I manually add the leg distances on the LEGS page, I get a value approximately the same as the FSX flight planner, about 1878nm. However, the total distance on the FMC's PROG page for the flight is 2328nm. Not seeing anything unexpected when stepping through the flight plan on the MFD.

 

I'm in the middle of FS2Crew's pre-flight to fly this flight anyway and see what the FMC does. In the meantime, any ideas what might be wrong, or am I missing anything? I've flown to higher lattitudes than this with no problems and have never encountered this on other flights (that has not been a result of a mistake in the flight plan, that is).

 

Thanks,

Dave Coulter

StoneC0ld_zps439869f4.png

Declared weather:  FSX: ASN / FS9: ASE

 

Hello Dave

 

Did you set the correct position of your fictional airport/RWYs in the FMC database?

 

Are you sure there is no name conflict?

 

Are the coordonates correctly set in the definition of the airport in scenery?

 

Give us the airport entries so we can see them and the actual coordinates where you want the airport. Pay special attention to the Lat/Long format and conversions!

 

Ionut "John" Micu

Check against CYLT and/or ENSB. If they are correct, then the problem is in how your fictional airport is set up.

Paul Smith.

  • Author

Sorry for the delay, just managed to get the time to take another look at this....

 

Just as I was gathering the information from the navdata files to post on here, I stumbled onto the problem....

 

I narrowed things down to the mysterious distance disappearing as soon as I chose the approach and arrival runway on the arrival page. (I had done this at the exact same time as I crossed the YCB vor on Wednesday, so I couldn't specifically figure out which of these removed the mileage at the time.)

 

I had originally made the airport in one location, but didn't like how it turned out and opted to just delete it entirely and start from scratch in a different location (where it is now). Reconfigured everything in the navdata files, EXCEPT airports.dat, which I just discovered still had the old co-ordinates. So, apparently the new location is 450nm away from the old one.

 

Thanks a lot, guys :)

Dave C.

StoneC0ld_zps439869f4.png

Declared weather:  FSX: ASN / FS9: ASE

 

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.