Search the Community
Showing results for tags 'ils g/s'.
-
I've looked elsewhere for this topic and have not found anything recent or exactly pertinent to my issue. I'm running X-Plane 11.55 in Experimental Flight Model, Downwind ILS not disabled. I have 2 years of X-Plane - I'm retired - it's COVID - so I likely have over 1000 hours in on X-Plane. So not a newbie. I have not had this AC previously and so had a clean install of the latest version about 3 weeks ago. I'm running through the IXEG tutorials that are dated 2016, so not sure if there's something wrong with those. (KLAS ILS info has changed but I've taken care of that). Anyway I've run Tutorial 1 a number of times and am now comfortable with the basics of flying this aircraft. I've been in Tutorial 2; Autopilot and Flight Director for a week now - probably over 50 hours trying to get the ILS Dual Channel Autoland sequence to work. I've been successful 6 times with likely over 60 attempts and cannot duplicate those particular runs. The issue is that even though I approach the G/S from below, am right on with the heading and inline with the ILS for runway 26L at McCarren Las Vegas the VOR/LOC and G/S armed, they are not captured (with a few exceptions) and I wind up heading for the dirt quite a distance from the runway. As far as I can tell I have the AC configured and positioned as the Tutorial describes. In an effort to cut down on the amount of time required to keep trying this I am now using the X-Plane function to place the AC 10nm out from 26L. I've attached the pics for the initial configuration and position when I'm spawned 10nm out. Then I have a pic of the result of that as the approach progresses and attached the log which I'm pretty sure will be useless. I also pasted the procedure I'm using below. I suspect it's some very subtle timing and/or positional issue. Additional info: Coming back to this after a few hours I was able to get it working 4 times in a row, then after that - changing nothing - very weird behaviors primarily with altitude. Basically not holding the altitude specified, or not acquiring the altitude specified. Gradual ascents or descents or yo yoing - everything is setup exactly as before when it worked several times. Also when the plane spawns the aircraft config can be very different; A/T off, FDs off, N1 on instead of SPEED, ALT HDG, APP and ALT HOLD buttons not operational. Very unpredictable and unreliable. Anyway if anyone has an explanation for this - I would love to hear it! 737-300 ILS Dual Channel Autoland Procedure Set plane 10nm out from RNWY 26L McCarren KLAS Put flaps and throttle in approximate position needed after spawn. Spawn, let equilibrate for 5 seconds or more so to acquire altitude, speed etc. Then hit pause and check configuration and set as necessary. Use the EHSI Map setting – 20 nm, EXP VOR/ILS VOR/ADF Tune Nav 1 and Nav 2 radio to the ILS frequency for the runway 111.50 Set the CRS 1 and 2 and Heading to match the runway heading and make sure it’s in MCP HDG SEL. (259) Set MCP SPD at 140 kts flaps 25 Set MCP ALT to 3800 ft. and MCP ALT HLD AP CMD A on APP Mode on FD’s on, A/T armed, SPEED mode on Unpause. Press CMD B for the AP. This will set up the dual channel autoland. The AP should now keep the plane on the ILS heading and will eventually intercept and then fly the glideslope. Make sure it’s not coming in above the glideslope as that does not work. When the glideslope is captured the green G/S annunciator will appear. When on final speed will be at Vref +5, (127) flaps 40 for low visibility. When the glideslope is captured the MCP HDG, APP indicators go dark and only the Speed MCP is active, along with the CMD A and B indicators of course. Airplane lands. ( I wish) X-Plane Screenshot 2021.11.15 - 12.25.32.78-compressed.pdf X-Plane Screenshot 2021.11.15 - 12.28.46.56-compressed.pdf X-Plane Screenshot 2021.11.15 - 09.49.51.85-compressed.pdf
-
Hello everyone! I'm having an error with the TBM 900 on the X-plane 11.50, when tuning the ILS frequency, the aircraft does not pick up the signal on the radio, but the green magenta appears on the g1000 panel, but the aircraft does not start the decision procedure, it doesn't seem to capture the Glide Slope, and the LOC bar in NAV1 doesn't appear as it should, and the rain effects don't work either, would anyone have a solution for such problems? Thank you.
- 10 replies
-
I set a FIX way point and then flew a heading away from the location of the FIX. When I turned on the NAV ir immediately captured the FIX but 180 out. I had to hit the BC button to get the NAV to track the fix point. When I switched to track an NDB or VOR it worked fine. In he above situation I had set the proper frequency for an ILS landing at KGGG. When I thought it should have captured the localizer and it did not I checked the frequency and both the one in the VLOC and the one in NAV 1 had changed. after changing the frequency setting the system captured as it should except the G/S. The plane flew right over the airport at the altitude it had been flying at. the G/S bug was sitting right on the mark like it was on G/S.
-
- Nav to a fix
- ILS Freq Change
-
(and 1 more)
Tagged with: