Recently my JS41 does not lock on the ILS at all. Previously there were times when the Glidepath was ok but the Glideslope didn't engage. Now, neither will lock on. Both Nav1 and Nav2 are set to the correct frequency and Nav2 gauge is totally accurate. I used it to get on glideslope/glidepath then tried to engage the APPR for Autopilot but no joy. Once nearing destination I switch out of LNAV for controllers directions, sett in the ILS freq and set the course bug to runway heading..I must be doing something wrong with Nav1 settings but cannot figure out what it is. Will someone walk me through the details?ThanksNeal Howard

Recently my JS41 does not lock on the ILS at all. Previously there were times when the Glidepath was ok but the Glideslope didn't engage.Now, neither will lock on. Both Nav1 and Nav2 are set to the correct frequency and Nav2 gauge is totally accurate. I used it to get on glideslope/glidepath then tried to engage the APPR for Autopilot but no joy. Once nearing destination I switch out of LNAV for controllers directions, sett in the ILS freq and set the course bug to runway heading..I must be doing something wrong with Nav1 settings but cannot figure out what it is. Will someone walk me through the details?ThanksNeal Howard

Well I agree you have to get used to this plane. especially when you fly a lot with big ones.No doubt you did this but to be sure....did you fly the tutorial flight. It gives a step by step tutorial how to set up an ILS landing.I must admit it isn't the best tutorial ever, but if you read very carefully and do it ones or twice things get clear and after practicing it is a bit less difficult to fly with the J41. And for nav settings .. don't forget to push the "insert" button after you set the right numbers (it is the button top right, with the hooked line on it)Good luck.Eric

After disengaging LNAV, do You engage the VOR/LOC mode? It's the V/L button near the LNAV button.For me it works this way, after disengaging the LNAV navigation I press the V/L button and set the LOC course. Then I press and "arm" the APR button and automatically it capture the localizer when it's in range. To do all this You should be under the Transition Level.I had the same issue as You, but I understood I need to press the V/L button before capturing the localizer.I hope this helps

For me it works this way, after disengaging the LNAV navigation I press the V/L button and set the LOC course. Then I press and "arm" the APR button and automatically it capture the localizer when it's in range. To do all this You should be under the Transition Level.[/Quote]That is exactly the way I do it Sebastiano and it suddenly just will not work.Today here is what happened nearing KOAK (Oakland) with active RWY 29: 1.Nearing descent time I disengaged NAV and hit the V/L key to get out of LNAVmode2. Checked HSI to erify that VOR 1 was set3.Set both NAV 1 and NAV 2 set to ILS freq for RWY 295. AS I neared the glidepath radial, VOR 2 was already reading but Nav 1 was not registering anything.6. I never could get NAV1 to switch to LOC mode however NAV 2 went into LOC mode with no problem.4. Followed the usual descent and heading instructions from controllers.I have flown the JS41 for several months and never had a problem until now. Additionally, beginning yesterday I am not getting any call-outs (flaps 9, 70 knots, etc).Couple more days trying to sort it out and then a reinstall I fear.

I am having a similar problem, but obviously have much less experience than you. I haven't ventured from the tutorial yet, but I have not been able to get the ILS to capture... I press the V/L switch one time and then set up for the RW heading with the magenta line.. but should I press it a second time to disengauge it. I have read and re-read it a number of times, and I know athat I am missing something? Any ideas and thanks?Also I have been at 4000 ft in the tutorial.. Am I too high?Bob

Bob:

Also I have been at 4000 ft in the tutorial.. Am I too high?[/Quote]That depends on distance from the runway dogs and the glideslope angle. Most controllers level us at anywhere from 2800 to around 4800. I believe that Anchorage Intl is a 4800 feet glideslope capture.In any event you should be able to see the glideslope location on your VOR. I prefer tobe "reasonably" close to both glideslope and glidepath before engaging the approach. The AP should certainly lock on in that situation instead of going to "ARM". I haven't used the JS41 since my last post but plan to give it another try this week. Maybe it will decide to work.....Good luckNeal

This morning I gave it another try at KOAK (Oakland) on Runway 29, ILS freq108.7( as I recall.) At 4000' and headed 020 to intercept the Glide Path the AP locked on, turned left, made corrections to get on the path and all was good. We were above the Glide slope slightly and the AP began descending to correct that also. Unfortunately, we continued to descend well below the glide slope with no correction initiated. At 1200 feet, well below the slope, I took over and climbed back to the proper altitude. The AP was again set to Approach but still could not follow the slope so I flew in manually and made my usual unbelievably perfect crash, ahem landing that is.Something is definitely wrong somewhere. I never uninstall/reinstall until I have tried every other possibility for a fix but maybe that is what is needed.

After disengaging LNAV, ...

...1.Nearing descent time I disengaged NAV and hit the V/L key to get out of LNAVmode...

Guys, why are you 'disengaging'?According to the tutorial, that is not the correct way to transition to ILS.

LNAV to ILS Transition: Crossing TICON the airplane will turn to follow LNAV toward MOSBY. When the airplane initiates the turn toward MOSBY, press the APR button on the flight director one time. This will arm localizer and Glide Slope capture on the flight director and you will see the white LOC armed mode appear on the EADI.As the ILS comes into field, the moving map will be replaced by an HSI display pre-set for the ILS 01R final approach course of 011 degrees as we’d specified earlier on the approach. (Pretty nifty, eh?)

Take a look at the last 3 pages of AOM.

Folks,The first thing to check , if you cannot align with the ILS, on autopilot, or manual (the needles don't line up), is if the airport uses the same ILS frequency for different runways. Example: JFK ILS 4R and ILS 22R use the same frequency in FSX and in real life, 109.5. The problem is, FSX defaults to a mode where it always recognizes the backcourse of an ILS...and consequently, it picks the closest ILS antenna, which, btw, is at the END of the runway...so to make a long story short...I was lined up on the localizer for 4R at JFK , NAV 1 tuned to 109.5, and my JS41 was picking up the ILS 22R backcourse localizer, and it was just not lining up, of course not, they are different runways. In real life, the tower has toggle switches, and they would rarely have them turned on both at once. OK , now that I muddy up the waters nice and proper , here is the fix. I downloaded a freeware airport editor for FSX AFCAD files, and along with FSX SDK (Software Development Kit), I removed the backcourse option for those two runways, (at least the folks who designed FSX , gave us the opiton). I would have to do that at any airport which use the same ILS frequency for different runways. It works great, and is easy to do. I just can't fly the backcourse on those ruways, big whoop.I really hope I didn't confuse the heck out of everyone.Good flying, keep the shiny side up and oily side down.Jim WarrenKPOU-PPL, Treasurer, Grasshopper Flying Club

Thanks for all the good info, especially that back course "bug"..I have run into it also.To clarify my remark "1.Nearing descent time I disengaged NAV and hit the V/L key to get out of LNAV mode"This is referring to my descent from FL or cruise altitude and is usually just minutes before a controller begins vectoring the aircraft. I took the Jetstream into Dulles 1R this morning and the ILS lock-on was perfect (or would have been if REX Weather engine would stop with the "Wind Shear")