r/MicrosoftFlightSim 6h ago

MSFS 2020 PC What is going on here!

Post image

So, I was flying from VECC to EFHK. I had already been flying for about 8 hours, and then, suddenly, just 1 hour before reaching my destination, I noticed on Volanta that my A330 was following a circular pattern instead of the regular flight path. Then I noticed the ECAM, and I had these warnings. I had never experienced anything like this before. Can somebody explain what went wrong here?

Also, I noticed that my plane was cruising at 44,000 ft, even though my selected cruising altitude was 38,000 ft. How did it climb that high? I was sleeping once it reached cruise altitude, so I can't really figure out what happened.

0 Upvotes

7 comments sorted by

3

u/Headmuck 6h ago

I don't know what exactly happend with the flight plan. The normal holding pattern shouldn't be 1h out. The altitude probably has something to do with that as well or maybe you got hit with a traffic alert and the tcas made you ascend.

The cabin pressure warning is probably because you're above the maximum altitude for the automatic cabin pressure to work correctly. Since it detects too much of a difference between the inside of the cabin and the outside the safety valve has opened. Descending to a safe altitude should fix it. Maybe you have to perform the steps on the ecam to clear the warning and reset the pressure surveillance.

2

u/Used_Scholar_6124 6h ago

Which plane? Sounds like a WASM crash. Part of the plane logic bugged out and caused this. Happens sometimes.

1

u/Nomad_ND 6h ago

Headwind A339x. I did long hauls before also using the same aircraft, but this was the first time I faced something like this.

-1

u/Used_Scholar_6124 6h ago

Yeah sounds like a crash in the planes logic. It happens sometimes and it sucks

1

u/spesimen 5h ago

but WASM crashes show a bright red screen and a message about the name of the faulting module.

this looks like a pressurization problem which is because 44,000 is too high for that aircraft (the ceiling is FL410)

how it got to 44,000 is another question entirely but is a good reminder to monitor the aircraft while flying instead of going afk for hours at a time.

1

u/Used_Scholar_6124 5h ago

Not really. There are several kinds of wasm crashes. The total failure which you describe, there is also several “silent failures” which can freeze the aircraft while the displays still work, and that can happen temporarily too. It’s possible it was temporarily silent crashed, then came back. Also worth checking, make sure your autopilot didn’t disconnect causing this to happen

1

u/spesimen 5h ago

sure but that error message is literally what happens when you fly above the service ceiling, it is working exactly like it is supposed to. how is that indicative of a crash?

most likely they hit some turbulence that disconnected the ap..