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.

FSX, MD-11

Featured Replies

The localizer offset should be noted on the approach chart if it is realistic. For example, KJFK ILS RNW 22R has an offset localizer and autoland will not work... also many LDA approaches are like this (PHNL or KSTL come to mind). However, I notice in the pic's that the aircraft is not keeping the localizer deviation indicator in the PFD centered but the flight director steering cue bars are not calling for correction. This is why I thought it might be the registry error.

Dan Downs KCRP

The localizer offset should be noted on the approach chart if it is realistic. For example, KJFK ILS RNW 22R has an offset localizer and autoland will not work... also many LDA approaches are like this (PHNL or KSTL come to mind). However, I notice in the pic's that the aircraft is not keeping the localizer deviation indicator in the PFD centered but the flight director steering cue bars are not calling for correction. This is why I thought it might be the registry error.
Dan,You'r still fully correct.The picture from TOM indicates a registry problem.The situation RON writes about is a misaligned Localizer at CYYZ 23 that should have no offset according the charts.Regards,Harry
Ron,Think your problem is different from Tom's and the same for all , me included, that use the FSX default scenery at CYYZ rwy23.The Localizer for rwy23 is misaligned to the runway heading by 0.7 degrees. Enough to Autoland the plane outside the runway boarder.(can be corrected by using programs like "Airport Design Editor", ADE).Hope this explains your situation.Regards,Harry
Thanks Harry for clarifying that. I didn't realize that it was a known FSX problem with the default scenery. I'll look into Airport design editor to try and correct the problem. Good thing I didn't reinstall :(

Regards,

Ron Gautreau

 

CYYZ

Boeing777_Banner_Pilot.jpg

  • Author
The above pics are a symptom of a registry problem. Please try the repair tool.
OK!! Back in business, many thanks!! It works, even with the FRA addon.Thanks to all of you!

CU, Tom Morello- FSX SP 2, WIN 7, 64Bit.

OK!! Back in business, many thanks!! It works, even with the FRA addon.Thanks to all of you!
Tom,Thanks for the feedback and providing the missing 1%.Instead of being 99% sure this would solve your offsets, I'am 100% sure now.Regards,Harry
Thanks Harry for clarifying that. I didn't realize that it was a known FSX problem with the default scenery. I'll look into Airport design editor to try and correct the problem. Good thing I didn't reinstall :(
Ron,For me also it wasn't a 'known' problem of the default scenery. But investigating it because of this thread, showed the reason of your misaligned Autolands.ADE is a great program to keep default scenery up to date as much as possible for the airports you frequently use.Glad the clarification saved a complete reinstall.Regards,Harry

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.