since the latest update I’ve done three flights in the longitude at different airports and will not intercept the localizer or glide slope anyone else noticing this?
I haven’t had it do that. I’ve done several flights with it, and for me, it’s not following its GPS path accurately (typically off to one side or another). It will intercept the LOC and capture the GS, but it brings me down a few hundred meters to the right of the runway.
These are airports I land at regularly and haven’t seen this issue before with the Longitude or other planes at these locations.
1 Like
That’s interesting I’m using the g3000 mod are you?
I am. I had some weird issues with the TBM and ILS as well in my first few flights after the patch, but for the life of me, I can’t seem to reproduce those any more.
With the Longitude, I’ve noticed that if it follows the GPS line perfectly (as it should) during the flight, ILS will be fine. If it doesn’t, I’d better be prepared to turn off AP and hand fly it down from 3-4 miles out from touchdown, or I’m going to land in water, a residential neighbourhood, or something. lol
Exactly the same behavior I am seeing .
I’m getting the same thing. So frustrating, they fixed the rocking after 32000FT but now cant capture LOC. They fix something but fixing one issue seems to cause others. Feels like an endless chase.
I flew from Shannon to Inverness on the citation longitude. Fully IFR planned via the world map and even used auto throttle whilst cruising. It seemed to work ok, though I think I may have activated the approach manually, however it did intercept the localiser and then capture the glide scope. It was bang on center on the ILS. Probably a little short but I always go manual about 100 feet anyway.
I did turn off the auto throttle as I was entering the approach too, which was more tricky, had to press ALT + R to disengage.
But it followed the plan, approach and the ILS.
Not modded, just stock.
Same with cj4 and a320 also won’t follow flight plan with nav mode sometimes it’ll follow for the first half of the flight then randomly isn’t able to lock onto flight path won’t even bank I have to hand fly the rest of an hour flight it’s pretty frustrating
I just flew the Longitude earlier today and I flew the ILS RWY 02 approach into PHOG (Maui) and I saw no issue with it capturing both the localizer and the glide slope. The one issue I did see was that it did not maintain the altitude while en-route.
I’ve had 2 flights with it today with no issues. 1 of those was repeating one of the problematic flights I had yesterday, complete with landing on the same ILS. No issues.
I wish I could find a way to reproduce the problem.
To all you guys with the Longitude and seeing this problem, please read on…
I just had the same issue I decribed in my post above flying the SR22. My plane was off to the right of it’s GPS line the whole trip, and the ILS took me down about 100m right of the runway threshold. Or at least would have had I not cancelled AP and flown it manually.
And this made me realize something - what I did differently on my flights with the ILS not working. I hand flew the plane for quite a distance after takeoff vs getting it to a safe altitude and just letting AP do its thing. I remember having hand-flown the Longitude and TBM for a while before punching in the AP when I encountered this issue.
Can you guys potentially test this hypothesis as well?
And to those NOT having issues - please refrain from cluttering up the thread with posts of how you’re not having issues. We know now everyone seems to be affected. It would be nice to have a clean thread to make collaborating on debugging this a bit easier.
2 Likes
So it turns out hand flying as I mentioned in my post above makes no difference.
But what seems to be consistent is that if it’s not following its GPS path exactly during the flight, that same offset will be applied to the localizer path on the way down the glideslope and it will miss the runway.
I can’t deliberately replicate it unfortunately
1 Like
What airport and what runway are you testing against ?
I will see if I can do some testing tomorrow or the next day but want to fly the same location and ILS as you.
I haven’t been in the cockpit of the Citation but I can confirm that runway headings and proper capture of an ILS is a hit-and-miss at this point in time in every aircraft I’ve flown since the update.
Sometimes it works; sometimes it does not.
Which airport or ILS doesn’t seem to matter. What matters is that if your plane is off from its GPS path in flight (following it, but flying to the left or right of the path), it will ahve that same offset at the ILS.
If it’s following the path, you’ll have no issues. It seems random to me. Thought I had figured out what broke it, but unfortunately not. 
I’ve had the issue in the TBM and Longitude more than any other, but also had this same issue in the Bonanza and SR22. The symptoms are the same. If it’s not perfectly following the GPS route en route to destination, it will have that same offset when trying to land it.
I don’t know what causes it. And it doesn’t happen very often for me. Probably 1 in 5 flights at most.
Same experience. SR22 today flew quite well right up until ILS capture… here’s my recap, with a screenshot showing the offset.
That looks exactly like what I was seeing as well. And I bet if you used the AP along the route, your plane was slightly offset to the right of your magenta line on your map as well. It followed the route, but wasn’t perfectly on the line like it normally is.
1 Like
Well I’m going to try an RNAV approach next time to see if that’s any better anyone try that yet?
If I understand correctly, yours won’t intercept the localizer at all?
No it will not multiple different airports It doesn’t intercept it whatsoever