Jeeeno ,

"Too far away from the TDZ. What happens at 200ft agl? Still 2white and 2red and the glideslope still perfectly centered? "

Note: the glide slope and VASI are not coincident KLAX ILS24R

Do you have screenshots or  video?

 

 

Edited January 8, 20233 yr by vonmar

20 minutes ago, Jeeeno said:

Too far away from the TDZ. What happens at 200ft agl? Still 2white and 2red and the glideslope still perfectly centered?

Yes, at 200 feet, that is when the GS starts to take it's 1,000 fpm dive to the touchdown zone. Seen this hundreds of times at airports all over the MSFS world. I am usually flying the Fenix A 320, but now I am using the C 310, I will see what happens with a slower approach speed. 

Edited January 8, 20233 yr by Bobsk8

12 minutes ago, Bobsk8 said:

Yes, at 200 feet, that is when the GS starts to take it's 1,000 fpm dive to the touchdown zone. Seen this hundreds of times at airports all over the MSFS world. I am usually flying the Fenix A 320, but now I am using the C 310, I will see what happens with a slower approach speed. 

Just to verify you are on autopilot at 200 feet?

Other poster (Jeeeno) was talking about VGSI lights all the way down to the deck on an ILS G/S?

 

Edited January 8, 20233 yr by vonmar

1 minute ago, vonmar said:

Just to verify you are on autopilot at 200 feet?

Other poster (Jeeeno) was talking about VGSI lights all the way down to the deck on an ILS G/S?

 

I disengage AP usually around 700 feet, follow GS down until around 200 agl, and then have to enter a dive to follow GS. Never flew any aircraft in real life that behaved that way, in fact I can remember instructors telling me "never to dive for the runway, go around. "

8 minutes ago, Bobsk8 said:

I disengage AP usually around 700 feet, follow GS down until around 200 agl, and then have to enter a dive to follow GS. Never flew any aircraft in real life that behaved that way, in fact I can remember instructors telling me "never to dive for the runway, go around. "

Have you tested a jet with autoland ?

I have experienced what Bob is talking about. You can be on a perfectly stabilized approach on the glide slope at the proper speed, and it feels like the glide slope itself has changed to a steeper angle right out from underneath you. 

If you let the AP take it below that point before you take over,  everything will be fine. 

But it doesn't happen all the time for me. And as I said, sometimes it will also make me land short instead of long but I have seen it both ways. 

Edited January 8, 20233 yr by MDFlier

5 minutes ago, vonmar said:

Have you tested a jet with autoland ?

I never use Autoland, but how would that effect what I am seeing. If  you trim the aircraft for a descent rate, i.e. 700 fpm, then at 200 agl you have to push forward on the controls, to increase the descent rate to keep the GS centered, something is wrong. 

Next time it happens I'll take a screenshot. BTW I always use the PMDG 737 or 738, but I don't think it's an aircraft issue. 

24 minutes ago, Jeeeno said:

Next time it happens I'll take a screenshot. BTW I always use the PMDG 737 or 738, but I don't think it's an aircraft issue. 

Has the G/S signal caused a PMDG737 autoland problem for you?

 

47 minutes ago, Bobsk8 said:

I never use Autoland, but how would that effect what I am seeing. If  you trim the aircraft for a descent rate, i.e. 700 fpm, then at 200 agl you have to push forward on the controls, to increase the descent rate to keep the GS centered, something is wrong. 

Just wanted to know if the autoland behavior (elevator pushes forward) was the same as you mentioned for the visual approach ("at 200 agl you have to push forward on the controls")?

17 hours ago, MattNischan said:

No, it is not. It has been updated, somewhat recently. So has the magvar data.

If folks have examples of broken ILS glideslopes, I would certainly be curious. We do so much autopilot work and I haven't seen one not hit the 1000ft marker on the GS in forever.

Nice! Yes, I just loaded the MSFS scenery library into LNM and can confirm that the two outer markers at my home airport (which were decommissioned in 2014) are no longer present. 

3 hours ago, Bobsk8 said:

I never use Autoland, but how would that effect what I am seeing. If  you trim the aircraft for a descent rate, i.e. 700 fpm, then at 200 agl you have to push forward on the controls, to increase the descent rate to keep the GS centered, something is wrong. 

As I wrote earlier, I did an auto-land at KLAX 24R today. No such behaviour. Super steady descent. If this stuff happens regularly it would be nice you or anybody could provide one or more examples to check. I usually don't do autolands, of course, but I can't remember stuff like that.

Only error in KLAX 24R seems to be that PAPI and ILS seem to be perfectly aligned, which per info of one user here in reality they are not.

3 hours ago, Bobsk8 said:

I disengage AP usually around 700 feet, follow GS down until around 200 agl, and then have to enter a dive to follow GS. Never flew any aircraft in real life that behaved that way, in fact I can remember instructors telling me "never to dive for the runway, go around. "

Yep, I can also confirm this. I usually forget the GS indicator on short final because it does not make sense anymore. Instead I concentrate on PAPI lights for a proper good landing. 

On 1/7/2023 at 6:10 AM, crimplene said:

Could you name some examples? I did a lot of ILS and RNAV approaches in the past few weeks and can't remember a single one that was wrong.

1.   KJAC  AXONOS   ver 1.0.0   ILS  none       Should be 109.1

2.   PAKT   Northern Sky  ver  1.2 ILS    none      Should be  109.3

To view the airport's published frequencies, spawn at the airport and use new Garmin GPS to access "nearest A/P" and then go to airport info>frequencies and scroll through them if they exist. look for ILS freq.  The above two airports have this data missing and will fail to auto-switch to localizer during RNAV approaches. There may be newer versions which will work, but I don't have them. I encountered these two just today within an hour !

The workaround is to preread the actual chart ILS frequencies and force them into the NAV freq fields in the GPS...

 

 

 

Edited January 10, 20233 yr by Eclex

17 minutes ago, Eclex said:

1.   KJAC  AXONOS   ver 1.0.0   ILS  none       Should be 109.1

2.   PAKT   Northern Sky  ver  1.2 ILS    none      Should be  109.3

To view the airport's published frequencies, spawn at the airport and use new Garmin GPS to access "nearest A/P" and then go to airport info>frequencies and scroll through them if they exist. look for ILS freq.  The above two airports have this data missing and will fail to auto-switch to localizer during RNAV approaches. There may be newer versions which will work, but I don't have them. I encountered these two just today within an hour !

The workaround is to preread the actual chart ILS frequencies and force them into the NAV freq fields in the GPS...

 

 

 

Are you saying the above airports actually do have a working ILS, but the problem is that the frequencies do not autoload? I see they are evidently both third-party airport sceneries - if so you would have to contact the author/publisher of the add-ons regarding the errors as it is not really a bug in MSFS itself.