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.

Localizer Approach Problem

Featured Replies

When I attempt a Localizer Approach, the callouts I get are out of sequence. ILS approaches work just fine.Here's the sequence I follow:On the Approach Briefing Page, the STAR is set to Generic ILS, approach type is NP LOCAs the localizer comes alive, I generate the "Localizer alive" call with a click of the ASI.The next click on the ASI is garbled, with a couple of different callouts together, but I end up with flaps at 15, and no gear down. Turing the autopilot off, generates the "standby mode, set go-around altitude" call.Once I've lowered the gear, the next ASI click generated the "contact landing" call.Over the threshold, a couple of calls happen: "Gear 30" "Before Landing Checklist"Just wondering what part of the sequence I'm doing wrong.By the way, these are short flights in the KLAX area, using Radar Contact, so perhapsFS2Crew needs a longer enroute segment for the program to work properly.Thanks in advance.Slugger

  • Commercial Member
When I attempt a Localizer Approach, the callouts I get are out of sequence. ILS approaches work just fine.Here's the sequence I follow:On the Approach Briefing Page, the STAR is set to Generic ILS, approach type is NP LOCAs the localizer comes alive, I generate the "Localizer alive" call with a click of the ASI.The next click on the ASI is garbled, with a couple of different callouts together, but I end up with flaps at 15, and no gear down. Turing the autopilot off, generates the "standby mode, set go-around altitude" call.Once I've lowered the gear, the next ASI click generated the "contact landing" call.Over the threshold, a couple of calls happen: "Gear 30" "Before Landing Checklist"Just wondering what part of the sequence I'm doing wrong.By the way, these are short flights in the KLAX area, using Radar Contact, so perhapsFS2Crew needs a longer enroute segment for the program to work properly.Thanks in advance.Slugger
Hi Slugger,Pls sake a 2nd look at the Non Precision section in the manual.I don't think the length of the flight is the issue.Try this:1. Click the ASI to call "Loc Alive".2. Use the Main button as you would during a regular ILS approach for the remaining calls (gear, flaps, speed, etc).3. With the gear down, click the ASI to call "Contact landing" after you've completed the landing checklist.Cheers,Bryan
  • 3 weeks later...
  • Author
Hi Slugger,Pls sake a 2nd look at the Non Precision section in the manual.I don't think the length of the flight is the issue.Try this:1. Click the ASI to call "Loc Alive".2. Use the Main button as you would during a regular ILS approach for the remaining calls (gear, flaps, speed, etc).3. With the gear down, click the ASI to call "Contact landing" after you've completed the landing checklist.Cheers,Bryan
Hi Bryan!Thanks for the reply. The suggestion works great. I enjoy flying non precision approaches because theyinvolve a bit more skill than simply catching the glide slope.Thanks again for taking the time to answer.Slugger

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.