January 11, 201511 yr What would be the number one reason that even though I'm heading straight to intercept the glideslope for a final approach that the LOC button doesn't want to work? I ensured that in NAV RAD that the ILS frequency and heading are put in there. But for some reason the localizer button just doesn't want to click. It was for KIAD landing at ILS 1L. Has this happen to anyone before? I don't understand why sometimes it clicks and sometimes it doesn't. -Andrew Coste Andrew Coste
January 11, 201511 yr Are you using the default FSX KIAD, or an add-on? The KIAD ILS 01L in default FSX is on a frequency of 111.3 MHz, but the real-world frequency has since changed to 110.75. If you are using current charts, and tuning your nav receiver to 110.75, that would explain your problem. Try 111.3, and it should work. You could also correct the problem by updating the airport in FSX. There are probably some free AFCAD updates for IAD here in the AVSIM file library. If there is one by author Ray Smith, you can install it with confidence, as his airport upgrades are always first rate. There is also the payware FlightBeam KIAD airport add-on. I don't own it, but I believe it has pretty good reviews. Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
January 11, 201511 yr Author Are you using the default FSX KIAD, or an add-on? The KIAD ILS 01L in default FSX is on a frequency of 111.3 MHz, but the real-world frequency has since changed to 110.75. If you are using current charts, and tuning your nav receiver to 110.75, that would explain your problem. Try 111.3, and it should work. You could also correct the problem by updating the airport in FSX. There are probably some free AFCAD updates for IAD here in the AVSIM file library. If there is one by author Ray Smith, you can install it with confidence, as his airport upgrades are always first rate. There is also the payware FlightBeam KIAD airport add-on. I don't own it, but I believe it has pretty good reviews. Thank you so much Jim. That was the problem. Under map in FSX it actually showed 110.70 instead of 110.75 like Pro ATC X and other addons show. So I guess I need to update my AFCAD for IAD. Also, it let me use 111.30 as well and DME showed up correctly. Not sure whats going on. -Andrew Coste Andrew Coste
January 11, 201511 yr Thank you so much Jim. That was the problem. Under map in FSX it actually showed 110.70 instead of 110.75 like Pro ATC X and other addons show. So I guess I need to update my AFCAD for IAD. Also, it let me use 111.30 as well and DME showed up correctly. Not sure whats going on. -Andrew Coste Another test you could do to verify the problem would be to load an aircraft right on the threshold of KIAD runway 01L. I'd suggest using the default FSX 172 Cessna. Turn on the battery and avionics, and tune your #1 NAV radio, first to 111.300, then 110.750. If the problem is as I've described, the nav flag on the #1 CDI should disappear, and the glideslope needle move full up when you tune 111.300, but not when you tune 110.750... Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
Create an account or sign in to comment