ILS at Ronald Reagan in Washington DC

[metz]

I left another message on this topic - the ILS is definitely not set up right.

Basically the localizer portion is not aligned correctly, and the glideslope is not located correctly on the airport. The localizer is correctly positioned, as touchdown point is at 1.0 DME.

I'm glad others have noticed it - I was worried that it was my airplane.

The bummer is that I simulate going in and out of there often, and now I have to mark that approach out of service, until there's a fix for it.

-Tim Metzinger
Commercial Pilot, ASMEL-IA
http://www.metzair.com/atop/sm-captain-tim.jpg

[metz]

The BOS approach is vectors-only, but the DCA ILS 1 approach can be shot without radar, using the Nottingham (I think) VOR as the approach fix.

> The
>reason for no procedure turns
>is because they are radar-vectored
>approaches. This is why it
>says "Radar Required" for the
>approach. No full-approaches here. The
>problem you are encountering must
>be a mistake on microsoft's
>part, unless i am mistaken...

Tim Metzinger
Commercial Pilot, ASMEL-IA
http://www.metzair.com/atop/sm-captain-tim.jpg

[acaldwell]

Tim, we need to be able to correct these faulty ILSs somehow. It is a VERY widespread problem. I'm sure some of these Gurus know how to do it. It might be done using airport 2.60. does anyone know and if so how about a little guidance.

Major Alan L. Caldwell (mostly B-47 and C-130)

[jase439]

[font size="1" color="#FF0000"]LAST EDITED ON Jan-01-02 AT 01:16AM (EDT)[/font][p]I don't know about Airport 2.6, but in ASD 2.1, you would create an exclusion area for navaids (a geographic area in lat/long that is entered in the scenery.cfg file) that "blots" out the default navaids in that region. You would then (at your option) import the underlying airports into the tool to use as a visual template. This is not absolutely necessary though if you have all the "hard numbers" on the navaids (position, frequency, signal strength, glideslope angles, marker placement, etc...) I like to do this as a sanity check so I can visually correlate the placement of a navaid with the airport. From there, you just drop in the navaids where they *should* go, generate a navaid BGL and drop it in your ADDON SCENERY folder.

For localizers, the exclusion area would be quite small, so at most you might have to recreate a VOR or NDB stationed at the airport.

I don't know what facilities Airport 2.6 has, but this kind of thing can be done relatively quickly in ASD.

J