Joshua Green

I think this needs to be marked as unsolved again, and investigated a little more. Something still isn't right.

I'll see what I can do. Naturally, the drift takes some time to occur, so to illustrate it happening would be a long-ish video.

I have this behaviour too.

Since 1.06, it seems, manual waypoint entry triggers the aircraft to immediately sequence to the next waypoint EVEN when the waypoint being edited is NOT the current OR the next waypoint. The issue does not occur in manual mode, but I don't think it should happen in auto mode either, unless the waypoint being edited is part of the current leg.

I've noticed during radio navaid tracking, that it is still not holding a proper WCA. The aircraft will slowly drift downwind over time.

After departure in TOGA mode, selected VNAV and INS modes on the FD. FD began vertical guidance, but the lateral FD kept jumping around. Once the AP is engaged, the lateral guidance became correct.

If one of the INS units does not have a track initialised, it will not show wind data when that mode is selected. It should, since the only data required to compute this is the aircraft heading vs the sensed track.

I went through the PMS setup process whilst using the new progressive aircraft loading system. I noticed that as soon as I entered the fuel and gross weight, those numbers began increasing in real time. This suggests that rather than using fuel flow data to subtract from the initial total entered during setup, this page is actually directly connected to the GW and fuel on board values. (This is also true of the EFDARS thumbwheels, which adjust for every change in weight). This cannot be accurate, since if the aircraft were able to sense FOB and GW on its own, there would be no need to enter these values into the PMS (as it is on more modern aircraft) I suspect it's supposed to only have access to fuel flow values and subtract from the totalizer. However, I could be wrong....

Something is still going on. It's a bit hard to determine what the mechanism is. I just did a Seattle to Boston flight. Nearly 6 hours in the air. During the flight, I updated INS postions 1 & 2 as I passed over VORs. I did NOT update INS 3 during the entire flight. However, upon arrival, INS 3 showed less than a mile of drift, whilst INS 1 & 2 showed 0.4nm and 3.1nm of drift respectively. (You can see this in screenshot 1) In screenshots 2 &3, you can see the sensed position and actual position of INS 3. Although the position is NOT identical to the real position, it does not seem quite right that it drifted so little. It still seems like it's getting a bit of a correction from some operation during flight.

I'm guessing there probably wasn't enough time for this to make it into the current patch, am I correct? Or should I put this to the test?

That's an excellent update, and thank you for the updated procedures as well.

They're working for me.

Wait a sec. If this is true, then how does one change from GPS enroute NAV to an ILS approach if BOTH use the "radio" selection? How does it know whether to follow the nav radios or the GPS? How would it know when to switch from one to the other just by changing from "VOR" to "LOC"? What displays on the HSI when both a tuned VOR AND a GPS route are loaded? Which distance and time values are displayed?

I tested this, and as far as I can tell, it does not.

Duplicate post, but correct.