Can't Hit The Localizer

**MSYAIRTRAN** · 10-22-2007, 11:15 PM

When I am given off to approach and on final with the APP on and the NAV1 on the right freq. Sometimes I can't get established on the localizer. Most times I have to go missed. Tonight I flew from KAUS to KMSY. They gave me rwy 19. After I was heading toward the rwy and the ATC told me to maintain 180 it stayed there. It did not lower me and this was 4 miles out. I even tried a short final on rwy 28 and had the same results. I had to just shut down FS after 3 misses. Any help on this issue is needed.

**Captain America** · 10-22-2007, 11:41 PM

Try it without ATC interference.

**MSYAIRTRAN** · 10-23-2007, 06:26 PM

Tried that still wont hit the localizer.

**Captain America** · 10-23-2007, 06:43 PM

>Sometimes I can't get established on the localizer.

That implies that sometimes you do engage the localizer?
What's different?

Make sure the runway has a localizer. With NAV1 set to correct ILS Freq, you hit the APP button after the localizer is detected and everything should work. GPS/NAV switch should be in NAV position.
Watch your speed and approach angle. Too fast and too steep will
cause you to miss the beam.

That's all I can think of. I hope it helps.

**MSYAIRTRAN** · 10-23-2007, 06:53 PM

I do nothing different at these airports as others. My NAV1 is set at the time I get the active runway from ATIS. I fly the altitude that ATC gives me until established on the localizer. My speed as always been around 140K and dont have this problem if I land say at KAUS or KSAT. Think it has something to do with the back course which i'm turning off in FSNavigator. And if that dont work I will cut it off in AFCAD.

**ronzie** · 10-23-2007, 07:05 PM

If you have a runway with the same localizer frequency at each end, use AFCAD to shut off the backcourse at each end as you stated. This keeps the avionics from trying to lock on to the wrong one.

Typically, unless this is done, the wrong beam will be tracked until you are within two degrees from the extended centerline of the runway. You can verify this by looking at the localizer readout ident or listening to the morse code audio ident depending on how your avionics is equipped.

**MSYAIRTRAN** · 10-23-2007, 09:03 PM

Ok. I just flew the same flight and this time where I think I have been missing it is that my FA NAV1 wasn't set to the ILS freq. This time since he had the controls I set his too and this time the APP came on and everything was ok. Now i'm going to fly the seconr leg from KMSY to KJAX and see if I can to the same there. I did uncheck the back course in FSNavigator also. Will give an update when i'm done.

**MSYAIRTRAN** · 10-23-2007, 11:49 PM

Ok just finished the KMSY to KJAX flight. I missed the approach because I was waiting for ATC to turn me and line me with the runway and I didn't set the approach heading so it was a miss. But after i went miss and ATC brought me back all went well this time. Guess it was the back course in FSNavigator.

**InsyleM** · 03-21-2008, 06:00 PM

Back Course in FSNavigator???
Does Back Course work alone in FS2004?
I dont have FS Navigator,
However I tried to fly down a Back Course Localisor approch,
and turning on back course had no effect.
THis was in the Beech King Air at Lihue in Hawaii.

All back course does (or suposed to do)
Is swap your localisor signals left/right to right/left
so that you can approch the runway from the oppsite end.
-Jonathan