Vaziani ILS works in one .miz, but not another

[Bahger]

I made an air-start night mission to demonstrate an ILS approach to Vaziani at night, and another, a runway start out of Vaziani, with a full flightplan, targets etc., also at night. Whereas the ILS for Vaziani works perfectly in the first .miz, in the second, the localizer, glideslope and beacon tones never come alive even with:

 

- ILS receiver tuned, and ON, emitting tone

- correct final approach course entered in HSI

- ILS ON in front panel (behind joystick)

 

In each case I follow the tower's given heading after I check in, and navigate to intercept the glideslope at 5000ft for Runway 14. Using the HSI CDI in the second mission I can approach and land very accurately but I wonder why the localizer and glideslope don't show up? Is there anything I should be enabling, either in the ME or the airplane, that I might be unaware of?

 

Many thanks for any assist.

[Bahger]

Anybody? I tried it again tonight, same approach (from the NW at Angels 20) as the mission where the ILS works, but in this one I get tone but no localiser, GS or beacon tone...what on earth can be the issue?

[RogueRunner]

 

Make sure you are within the cone to receive the signal. FL200 is most prob way way too high.

[MTFDarkEagle]

http://forums.eagle.ru/showpost.php?p=1165436&postcount=14

[luza]

Make sure you unstowed the ILS needles

[MTFDarkEagle]

Make sure you unstowed the ILS needles

(that's what my link above points to, with a discription where the switch is)

[Bahger]

DarkEagle, I bet that's my issue, thanks. This is the problem with starting missions in the air or on the runway ( I only do either for training/testing); there are occasional inconsistencies re. what gets switched on. I will test this, many thanks.

 

RogueRunner, it's not receiving a signal when I am at 12 nm and 5000ft that bothers me!

Edited April 7, 2011 by Bahger

[Bahger]

Thanks Nicola. I'm IFR-qualified in r/l but without published procedure altitudes, there is a certain amount of improvisation in DCS A-10.

 

In approaching Vaziani from the NW, I use 5k as both a Minimum Safe Altitude and a Glideslope Intercept Altitude. At about 12 nm out, it does indeed capture the GS from below, resulting in a nice, easy 3 -4 degree pitch down descent to the threshold after the GS passes through the center of the AI.

[GGTharos]

At 12nm it should be capturing it from above ... 300' per nm. You should be on the needles at 3600' at 12nm.

 

Thanks Nicola. I'm IFR-qualified in r/l but without published procedure altitudes, there is a certain amount of improvisation in DCS A-10.

 

In approaching Vaziani from the NW, I use 5k as both a Minimum Safe Altitude and a Glideslope Intercept Altitude. At about 12 nm out, it does indeed capture the GS from below, resulting in a nice, easy 3 -4 degree pitch down descent to the threshold after the GS passes through the center of the AI.

[Bahger]

Thanks, Tharos. I'll try using a GS intercept alt of 3600'.

 

(Don't forget, field elevation at Vaziani is nearly 1500' [1492']).

[GGTharos]

Ah, that makes more sense then - yes, you should add the 3600' to that :) Now it makes sense that at 5000' you intercept it from below. I had completely forgotten! :P

[Bahger]

Ha, yeah, that may be what Nikola neglected to consider, too. Using 3600' MSL as a guideslope intercept altitude for Vaziani Runway 14 approach might fly you into those tower blocks just outside the outer marker!