777 ILS autoland approach

[Clive2670]

Anyone having the same problem as I am? Everytime I try and do an ILS autoland with 777 into any ILS Cat 1 airport I set radio Nav 2 to CORRECT settings according to "onboard" map I.E ILS (radio) frequency CRS settings. Get the localiser plane descends normally finds the G/S continues normally, shows "flare" & Rollout" in display, continues normally dead centre of runway within 50 feet it makes a SHARP turn either left or right and ends up on the the grass!!! NEVER lands on the runway. So frustrating!!! Thanks Clive

[wkitty42]

can you provide an airport to use as an example?

could it be that you're passing the localizer beacon and turning to it?

[Clive2670]

can you provide an airport to use as an example?

could it be that you're passing the localizer beacon and turning to it?

Hi wkitty42, here is the tutorial that I've referenced to do an autoland, FYI this happens on ANY airport ( I always try to use CAT 1 airports) Heathrow, Stanstead, Manchester, Gatwick, in the UK, as I'm still finding my feet on this wonderful sim' just fly between them to get used to all autopilot settings used this tutorial https://youtu.be/ToOD8fAlme8 . Hope this helps? Cheers Clive

[Hyde]

See this issue report.
https://sourceforge.net/p/flightgear/codetickets/45/

Long standing issue. Please fix.

[wkitty42]

yes, that is exactly why i asked had you passed the localizer and it simply turned to it...

the bug report exists so it won't be forgotten... there's a lot of work being done on the sim right now... maybe this bug will be found and corrected soon... i don't know if it will be in the upcoming 2016.3 due for release in about 25 days, though... i haven't seen any comments about it in the dev list and nothing has stood out in the commit logs...

[Clive2670]

OK thanks all who replied just curious about the demonstration in the youtube video I've seen (Link above) if this "bug" exists why is this player/pilot able to land at PHNL, is it only this airport that is immune from this "bug" Thanks all again Clive

[biloute974]

Hi,

on the video (link below), the pilot don't use autoland... because he shut A/P before landing and CATIII ILS is more usable to autolanding. See this video, it's a full autoland at KSFO: https://www.youtube.com/watch?v=p9mzT5SMpZ8

[wkitty42]

just curious about the demonstration in the youtube video I've seen (Link above) if this "bug" exists why is this player/pilot able to land at PHNL,

probably because that video is from Mar 2013 and he's using FGFS v2.10 which is pretty old these days

[Thorsten]

Long standing issue. Please fix.

Ought to be trivial to fix this airplane-side by freezing the location of the localizer if you get closer than a cutoff distance and using the deviation to that for the final part of the flight.

It's no more than a couple of Nasal lines - I can't believe people have been waiting for years for this to be fixed FG side (which apparently is far from trivial).

[CaptB]

This bug while annoying is hardly a showstopper. An autoland is almost never performed on CAT I, you'd be flying manually well above the mentioned 50ft simply following the FD until minima, which for CAT I operations is 200ft.

[Hyde]

Actually there is another bug related to ILS as I reported on https://forum.flightgear.org/viewtopic.php?f=66&t=29869

As you can see that the 28R ILS frequency is wrong. It should be 111.70 instead of 110.75.
And feather shape on map is also wrong because using LDA's wrong frequency.
If LDA is also displayed then antenna position is wrong ether. It's not at RWY threshold.
To solve this, ILS and LDA should be separated and user selectable. It will solve this same frequency of ILS issue too.
I notice more LDA data has been added in the latest X_Plane nav.dat. With that data, RJTT will be a mess.

[Clive2670]

UPDATE- just managed to land on KFSO 28R and LEPA 24L, (Also LEMG RWY31 works as well using online map server as this gives more accurate ILS frequencies THAT WORK!!!) using ILS map data within FG. Landed smack bang on target and in centre line, maybe a little late on touchdown (beyond solid white square) but managed to do it and stop with autobrakes 2 and reverse thrust. Now going to try other "single ILS" runways at some other airports, as mentioned earlier, it may be that the ILS at either end is conflicting and aircraft is trying to turn around on itself "looking" for other ILS signal. But that aside, it's very satisfying to know that all the AP settings from my point of view that I set worked, and I got the aircraft and my "passengers" safely on the ground without incident.

[Hyde]

Long standing issue. Please fix.

Ought to be trivial to fix this airplane-side by freezing the location of the localizer if you get closer than a cutoff distance and using the deviation to that for the final part of the flight.

It's no more than a couple of Nasal lines - I can't believe people have been waiting for years for this to be fixed FG side (which apparently is far from trivial).

Thorsten,

This is not simple as you mention.
Besides, this same frequency issue causes another issue such as we can not use KJFK-22L ILS at all.
Same frequency is used on KJFK-04L (different runway) and this is always activated and 22L is never.
Isn't it time to fix all of these ILS, LDA issues?

Hyde

[Hooray]

I tend to agree with Thorsten, using a few helpers from geo.nas should make it possible to come up with a workaround.
However, what exactly would be your "perfect" core change regarding the LDA/ILS change ? Is this is about the navdb or what is the underlying problem/fix that you'd see addressed ?

(Note that any ND/MapStructure code can easily circumvent all of the hard-coded autopilot, route-manager and navdb machinery - artix implemented wrappers for those for Airbus aircraft, which would also be possible to come up with your own scheme for things that have been broken for years)

[Hyde]

My expectation is ILS/LDA should be activated by user independently. Not automatically all on default.

Anyway, isn't it a show stopper that we can not use KJFK-22L ILS?