DCS M2000C ILS

[TomCatMucDe]

I think there is a bug when you intersect - not capture - the glide slope. It is impossible to center the open box, much less place the fpm within the box; it's been impossible to center it on the HUD. I'm no expert and I'm probably wrong as to what to fly once you intersect the GS, but getting the fpm inside the open box has been impossible. Once the Glideslope is catured and the open box becomes a closed box, everything seems to be working as it should. Perhaps someone can clarify what indicators to fly prior to glide slope intersect - the open box phase.

 

 

I have the same observation

[PiedDroit]

I think there is a bug when you intersect - not capture - the glide slope. It is impossible to center the open box, much less place the fpm within the box; it's been impossible to center it on the HUD. I'm no expert and I'm probably wrong as to what to fly once you intersect the GS, but getting the fpm inside the open box has been impossible. Once the Glideslope is catured and the open box becomes a closed box, everything seems to be working as it should. Perhaps someone can clarify what indicators to fly prior to glide slope intersect - the open box phase.

What do you mean by "intersect - not capture"?

The open box does not appear when you receive glideslope data, only when the localizer data is received but not glideslope (or you're not within 9 nm).

And you can't place your FPM in that open box, as it is linked to the horizon.

 

So, if I do a chronology, we have:

1- receive localizer => open box appears on the horizon, as well as the dashed deviation line.

2- receive glideslope, be within 9nm => closed box appear, anchored to FPM

 

Edit: That open box gives the same info as the dashed deviation line.

If you're right of path, that box will appear on the left, along the horizon line, regardless of your direction of flight (the waypoint indicator is giving you the direction to runway, not the open box) and the dashed line will be drawn from center to left, downwards.

Edited January 2, 2016 by PiedDroit
Corrected left of path => actually right of path

[jojo]

The open box gives LOC deviation.

So with FPM on horizon you should be able to put FPM inside.

 

You're supposed to capture LOC first, fly level, close in then capture GLIDE from under.

 

Start to descend when you capture GLIDE.

[Toertchen]

So, if I do a chronology, we have:

1- receive localizer => open box appears on the horizon, as well as the dashed deviation line.

2- receive glideslope, be within 9nm => closed box appear, anchored to FPM

 

Thats how it works :thumbup:

 

 

Good to know: In RL you should capture the LOC before the GS in IMC, due to safeness. In VMC its allowed to capture the GS first.

Edited January 3, 2016 by Toertchen

[=4c=Nikola]

Good to know: In RL you can't capture the GS before the LOC, don't know if it is implementet in DCS?!

 

That's not true, I've done it many times, although it's not a smart thing to do in IMC. Maybe the M2000C's equipment is not capable?

[Toertchen]

That's not true, I've done it many times[...]

Where? In real life or in DCS?

 

It is how it works, due to safeness. If you capture the GS without the LOC you "can" land in the middle of nowhere or at the false runway. So in real life it is allowed to capture the GS befor the LOC in VMC.

Edited January 3, 2016 by Toertchen

[PiedDroit]

That's not true, I've done it many times, although it's not a smart thing to do in IMC. Maybe the M2000C's equipment is not capable?

IRL it probably can (why wouldn't it? a glideslope antenna is no rocket science). The question is, how is it coded in the sim?

I don't see the point anyway, in DCS with a normal profile you will probably get the LOC first.

 

Edit: if you get the GS before the LOC, it's possible, it only means you're way out of the LOC beam.

Edited January 3, 2016 by PiedDroit

[=4c=Nikola]

Where? In real life or in DCS?

 

It is how it works, due to safeness. If you capture the GS without the LOC you "can" land in the middle of nowhere or at the false runway. So in real life you only can capture the GS after the LOC.

 

IRL of course. It's completely safe thing to do in VMC, and there's really nothing to stop you. Some aircraft has autopilot constraint so you cannot capture GS before LOC unless you switch to manual flight.

[Toertchen]

The question is, how is it coded in the sim?

 

Another interesting DCS related thing:

If you look at the Black Sea Map, you've Vaziani with ILS-Freq.: 108.75 Mhz - in both directions, that would never work

So if you try it, you've got the signal for RWY14.

 

Edit:

[...]It's completely safe thing to do in VMC[...]

In VMC you don't necessarily need ILS but in IMC it would be fatal if you catch the GS first or withour LOC.

Edited January 3, 2016 by Toertchen

[PiedDroit]

Another interesting DCS related thing:

If you look at the Black Sea Map, you've Vaziani with ILS-Freq.: 108.75 Mhz - in both directions, that would never work

So if you try it, you've got the signal for RWY14.

It's possible IRL if you use back course, same frequency for both.

However you can't use glideslope when in back course, only localizer.

I didn't try in DCS though.

 

Side note: glideslope frequencies are different from localizer frequencies. However we usually only dial localizer frequency because it is paired with a fixed glideslope frequency (that we don't need to know).

That's why you can't have localizer and glideslope on same frequency for both runways, because you can't tune to another glideslope frequency and the glideslope transmitter work only in one direction.

Edited January 3, 2016 by PiedDroit

[=4c=Nikola]

That's why you can't have localizer and glideslope on same frequency for both runways, because you can't tune to another glideslope frequency and the glideslope transmitter work only in one direction.

 

KJFK 13L-31R both at 111.50 + 332.90. Although they probably cannot be powered at the same time (not sure).

[Toertchen]

[...] they probably cannot be powered at the same time (not sure).

 

Thats it. I heard somewhere to switch the RWY HDG you need approximately 15 minutes. That's what I've not considered by Vaziani. I've tested it, it works. :pilotfly:

[IvanK]

Thats it. I heard somewhere to switch the RWY HDG you need approximately 15 minutes. That's what I've not considered by Vaziani. I've tested it, it works. :pilotfly:

 

Doesnt take 15mins I have seen it switched in LAX in around 20seconds from a Radio call to turn the ILS around

[Toertchen]

Doesnt take 15mins I have seen it switched in LAX in around 20seconds from a Radio call to turn the ILS around

Thank you for the information.

 

You never stop learning :book:

[cmbaviator]

Thats how it works :thumbup:

 

 

Good to know: In RL you can't capture the GS before the LOC, don't know if it is implementet in DCS?!

 

 

 

 

Not true, you capture le GS before the loc at least on commercial aircraft

 

 

CMB

 

Sent from Tapatalk

[PiedDroit]

Not true, you capture le GS before the loc at least on commercial aircraft

 

 

CMB

 

Sent from Tapatalk

 

What's the point of this answer? It was elaborated enough already.

Yes this is how it's supposed to work.

And yes, you can botch your approach and catch GS first.

Also yes, some airports have more than one GS transmitter using same frequency.

This is starting to look like the proverbial dead horse :music_whistling:

[Toertchen]

Not true, you capture le GS before the loc at least on commercial aircraft

 

Aircraft are usually vectored to intercept the localizer approximately 1-2nm before final approach fix, where the glideslope is captured (if you capture the localizer you have to report to ATC "ILS established"). It is the normal procedure to capture the localizer at a hight lower than the glideslope, so you capture the glideslope after the localizer. If an aircraft is not established on the localizer, there is no point in continuing the approach, so it will be canelled by ATC and the aircraft revectored. After all, i learned it is allowed to capture the glideslope first when you are in VMC.

 

Report: Flybe DH8D at Manchester on Nov 16th 2011, descended on glideslope without being established on localizer

http://avherald.com/h?article=44de3425