Default A320-Neo, APU, and engine losing PSI mid-flight

Bug Reporting Hub Aircraft & Systems
, , , ,
1

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

2 tags are required: One for platform, and one for aircraft.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

Yes

Which aircraft are you reporting an issue about? (Please also add the proper tag for it)

A320

Which aircraft version are you experiencing this issue on? (You can find this listed in the Content Manager under the Aircraft Name)

Latest default version

Brief description of the issue:

  1. When manually going through startup checklist, APU doesn’t spool up past about 8%. Mid-flight, right engine loses all PSI and stops responding. Both of these go away if I turn on unlimited fuel.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Turn off unlimited fuel
Start flight cold & dark. Go through checklist. APU won’t spool up past 8%. You can get past this using Ctrl+E, but then right engine consistently loses all PSI after about an hour.

PC specs and/or peripheral set up if relevant:

Build Version # when you first started experiencing this issue:

Just started flying again last weekend (after updating everything) so whatever the latest versio is.

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

3

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes

Provide extra information to complete the original description of the issue:

Ever since the 1.35.21.0 update I cannot start the A320 APU manually from cold / dark. The APU only gets to a few percent before switching back to off. Even the auto-complete option doesn’t work.

If relevant, provide additional screenshots/video:

4

I have had the same issues (XBOX) ever since this update Asobo’s A320Neo has this PSI issue.

5

I have been told that you should press the APU start button if this happens.

My issue is this should not be happening at all.

Also, I understand what you mean when you do auto start up and the APU doesn’t past 8% then drops to 0%.

What you need to do (on your XBOX) do a short cut method - (Right bumper and and left button) that triggers the engine to start up.

But I have noticed after this update that A320 default has been having errors midlight that NEVER happened before.

I just hope there will be another update that sorts this all out cos it does ruin the flight.

6

Are you using Developer Mode or made changes in it?

No

Brief description of the issue:
All of a sudden, within the past week, with no recent updates (since the latest USA update), engine #2 on the default A320 Neo fails after 1-2 hours of flight on each flight. Gen2 Fault displays on the overhead panel. N1 drops to no engine thrust. When cruising at FL370-390, I have to descend because I’m unable to maintain altitude on one engine. Engine 2 will not restart, either with re-doing the in-sim checklist or by using Ctrl+E.

**I confirmed all failures are OFF on the flight planning “failures” screen.
**I am using no add-ons and the default A320 Neo.
**I am not manually turning the engine off by accident during flight - it happens during straight & level cruise with autopilot engaged. The fuel switch is ON following the failure and ignition set to “norm.”
**I use the default in-sim engine start procedure prior to taxi/takeoff.
**There is plenty of fuel.

Detailed steps to reproduce the issue encountered:

Just plan a flight with the default A320 Neo, cruise at altitude for 1-2 hours, using real time & weather.

PC specs and/or peripheral set up if relevant:

Higher-end Dell G5, playing at high-ultra. Hasn’t happened before. Happens with every flight with the A320 Neo now.

Build Version # when you first started experiencing this issue:

1.26.5.0

7

I’m strictly guessing that there is some peripheral issue or keybind conflict or accidentally mapped control or failing button somewhere.

If you can get it to happen 100% of the time like you indicated, start up a long flight and after reaching cruise, unplug all of your peripherals (joysticks/gamepads/throttle quadrants/keyboard/etc…) and see if it still happens.

8

I did check for accidental failure mapping but found that apparently there is no command regarding an engine failure that can be mapped. Plus, I have not recently changed any peripheral mapping recently.

I have had control flutter recently even after joystick calibration and setting a null zone that seems to come and go.

I suppose I can give this a try but I’m interested in seeing if this is happening to anyone else.

One bonus to this is that after landing and taxi and at shutdown of engine 1, the sim seems to include the sound of the Power Transfer Unit!

9

Tried three and two hour flights in other twin jets (default 787 and default Citation Longitude) without changing any peripherals or key/button mapping - no similar result. Both engines ran without fault/error throughout he whole flight in those two other default planes.

10

“after joystick calibration and setting a null zone that seems to come and go.” This is not a normal behavior that require an investigation on your periferals settings .For istance,make sure that you don’t have duplicate settings like “thrust” or “rudder” on joystick and TCA quadrant (or similar devices).I have noticed that sometime settings that are good for some aircraft are bad for others.

11

I had recently calibrated my joystick and adjusted the null zone because of a joystick problem. This was prior to these engine 2 failures.

I tried a few additional 1.5-3 hour flights in the other twins (including the King Air and the two default Cessna jets).

I also have tried two more long (2hr plus) flights with the default A320 Neo, and it did not happen again.

But I wouldn’t call this solved because I still have no idea how it happened in the first place.

12

Well,it sounds like an hardware problem .You had a joystick problem and after the adjustment you faced these problems .It could be that the joystick has an electrical failure that comes and go.On older thread in the forum I remember of some “repairs” on the Thrustmaster joystick because the electrical cables inside the stick were badly positioned .You may retrace that thread to be inspired…

13

This has not happened recently. I have been pretty conservative and non-experimental in adjusting any settings since installing the sim, and was conservative in making adjustments before/after this odd situation. I can say that it hasn’t happened in the past several flights in the default A320. I suppose it was a fluke of some kind, or user error on my part that I just haven’t figured out. Thanks for the suggestions.

14

I have the same problem on Xbox and also with the A321neo and the Boeing 777-300/200

2 Likes
15

Hey, found a fix, start APU and the engine will start, happened to me in a321 too

1 Like
16

I had the exact same problem. I turned both engines anti-ice buttons on and it was fixed.

17

Thanks! This solved it! This didn’t happen before… I had to re-install MSFS because installation broke after latest update and it started occurring after a few hrs of flight at cruising altitudes of 30+Kfeet. Only happening with Asobo’s default A320N but I haven’t tested any other aircraft after re-installation yet.

18

I literally have same issue (XBOX) engine two the PSI failes after a few hours (never was like this before).

My thing is this - this should not be happening AT ALL.

APU start during flight fixes it? Anti Ice buttons?

Okay well I just rebooted the engines with a short cut buttons on XBOX.

But was never like this before the update…

19

Did this restart the engines??? Or did it just keep engine 2’s PSI from failing?

22

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes, every time when starting cold and dark in the 320N
Provide extra information to complete the original description of the issue:

Found a pretty simple and logical fix: APU needs Fuel! Activate fuel pumps before starting APU and it’ll spool up just fine.
If relevant, provide additional screenshots/video:

23

I have the same issue on Xbox S. I can restart the engine mid flight and it doesn’t happen a second time on that flight. Restart a new flight and it happens after >2 hours every flight. Must be a bug.