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.

Flying in Europe

Featured Replies

In my effort to learn the FMC I have been trying to follow some tutorials written by Chris Willis at BAV and another by Tom Evans at Speedbird. These tutorials refer to inputing airways that have "U" prefixes. Well and good, but the FMC database does not have them. FSNav and FS Build do have them. I have updated the navdata to each as they were issued. Is there something I am too blind to see here?These tutorials are very helpfull at least for me, my thanks to them both.Thanks, Sinbad

It depends on which Airac cycle you were/are using and which airways you are trying to input.The latest, and sadly the last, airac cycle from Richard included major airway name changes for the UK.First make sure the updated navdata files have actually been installed to the correct location fs2002fmcwpnavdata, the latest files are dated 23/11/2003.Second, open wpNavRTE.txt in wordpad then use 'find' to find the 'U' airways you say are missing. If they are not found post 3 or 4 of them here and we will see if we can help.

The only thing I can think of is that you enter the airway like U/N872, when it should be entered like UN872.I just opened up wpNavRTE.txt and it's got loads of "Upper" routes. (U means Upper).Martin767 fetishistIt's a lot like life and that's what's appealing

Gentlemen,Thanks for the help. I did a search in the wpNavRTE text file and sure enough they are there. In particulatr UA1,UL612,UG32, and others. Obviously I have done something wrong in the inputing of these. I will try again. Thanks for all the help. Sinbad

Greetings,When you are entering the airway name, are you doing it on the left side LSK in the RTE page? The other thing to check is that your waypoint on the right side exists in the airway. If you have a VOR or intersection (for example) that's not a part of the airway it won't link.Something that helped me figure it out is to think of entering the path on the RTE page the way you'll be using it in flight - first waypoint right side, then use this airway on the left side to go to new waypoint on the right side, etc etc etc.What is the path you're trying to take? Perhaps we can try and enter it ourselves and see what might be wierd for you?

correct Darylthey are still changing though.Cheers

The first route is from EGLL to EDDF and is as follows:Dct DVR UG1 KONAN UL607 SPI UT180 ROLOR T180 EPINOThe second on is from EGLL to LIMC and is as follows:MID UA1 VEULE UL612 MILPA UG32 MOBLO UG32 TOP.Sinbad

EGLL to EDDF.Should now be DVR UL9 KONAN.EGLL to LIMC Should now be MID UN615 XAMAB.Large number of airway designators in the UK changed name on the 27th November 2003. The current Navdata base is accurate and reflects these changes.More info on these changes can be found at www.vatsim-uk.org

Thank you Mark,I'll give these a try. Sinbad

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.