1.0.9 arrival time and EFOB still a mess

[swissdani]

At the moment flying from London to Cape Town. I have all the winds loaded before departure. After takeoff my EFOB was just unter 10t, and my expected landing time was 1712z, now after around 3/4 of the flight the EFOB did rise to 14.6t. According ot the simbrief planning, around 11.3t would have been expected. Where does this huge difference come from? The winds are spot on, as planned in the flight plan. Also the arrival time has now fallen back to 1752z. How is this possible to have a 40mins gap (no reroutes or detour) but having more fuel left at the end?

[swissdani]

Another 2 hours later the ETA has dopped to 1803z and the EFOB to 15.9t. How is this plane so inaccurate?

[Anatoly]

The same for me. Flight time from OMDB to SBGL was calculated around 11:30 instead of minimum 14 hours (around 6500 miles). And EFOB was 27t which is so unrealistic. After take off and climb ETA started to increase and EFOB decrease. And finaly after just 2 and hulf hours of flyinf I got CTD. So disapointed by update honestly. Grounded this plane till it's more stable and close to real life.

[N77022]

VHHH to KDFW, EFOB 0.4T with winds and steps. Simbrief has it EFOB 10.0T.... of course EFOB gradually started increasing until the CTD after 6hrs of flying. Grounded the A350 as well. 

Makes me wonder what the beta team is testing? Pattern work at their local airfield?

Edited Saturday at 10:06 PM by N77022

[ShogunAssassin]

I’m also experiencing this issue specially as to estimated time. I’m not sure if the CDA implementation messed up my arrival time or this was already an issue which I failed to notice in the previous versions but as you can see in the first screenshot (Screenshot 1) I have attached to this comment, the plane estimates me at Flaps 2 by 8:12 and at LL613 at 8:15 UTC. But as you can also see, the current UTC time is 7:42, and I am 1 nautical mile away from the flaps 2 marker shown on the ND and roughly 3 nautical miles from LL613. It’s hard to believe that it would take me 30 more minutes to reach a point which is already only 1-3nm away from me. After passing LL613, the UTC time changed and showed beside it was the time I actually passed it, which was 7:42 (Screenshot 2). But the estimated arrival time  changed from 8:15 to 8:17, yet I was already by the gate at 7:55 UTC. So there is probably something wrong with how the plane estimates its arrival on certain points specially upon final approach and landing. 

Edited Sunday at 01:02 AM by ShogunAssassin

[JS2Tango]

ETA and other timings appear to be worse in v1.0.9 than they were in v1.0.8.

[Greydog]

I updated things yesterday in MSFS 2020 and was flying the A350 from TNCM to PANC and all was fine, but then I encountered EFOB errors and half way in the flight it went up to 15 .4. Later, I tried a much shorter flight and all was fine.

[ykeyre]

Are you guys using 2020 or 2024?

[C. Schaffhausen]

We are the beta team lol

On 5/11/2025 at 6:05 AM, N77022 said:

VHHH to KDFW, EFOB 0.4T with winds and steps. Simbrief has it EFOB 10.0T.... of course EFOB gradually started increasing until the CTD after 6hrs of flying. Grounded the A350 as well. 

Makes me wonder what the beta team is testing? Pattern work at their local airfield?

 

[C. Schaffhausen]

Same issues as OP has, inaccurate arrival time and fuel predictions.

[Greydog]

On 5/12/2025 at 12:45 PM, Greydog said:

I updated things yesterday in MSFS 2020 and was flying the A350 from TNCM to PANC and all was fine, but then I encountered EFOB errors and half way in the flight it went up to 15 .4. Later, I tried a much shorter flight and all was fine.

Did you find what was wrong with the EFOB because I tried it yesterday and changed the FL, up two positions for a total of 4,000 feet, and all was fine but the top of descent never showed and I just had to wing it, so to speak.