FBW A320 AP1 drops out and will NEVER engage, until pilot corrects the problem

Cruising at FL390 over Europe following a SimBrief flight plan, for some reason the FBW autopilot drops out and will never engage again.

After pressing AP1 the button light briefly flashes, I hear 3 warning sounds, 3 different warning sounds and AP1 does not engage.

What on earth is happening and how do I save the plane and passengers!?

I have checked everything, tried to go Direct To the next waypoint, the FMC does that but the autopilot will never engage, ATHR stays engaged though.

Running SU15 Beta. Havenā€™t a clue if Iā€™m missing something or itā€™s a bug.

image

Long answer short. Youā€™re too slow. AP just work under certain condition and youā€™re out of it.
Youā€™re short before a stall.

2 Likes

and you are probably too high, maximum ceiling for the A320neo is 39,100ā€“39,800 ft, and you are probably above the possible ceiling depending on your gross weight

Yeah, this might be the reason for the speed. Or probably wrong AP setting for the speed.

Yes speed wrong, height wrong but I could not get the plane under control and A/THR was playing up, engines falling back to idle on their own despite throttle on CLB.

Iā€™ve reverted back to SU14ā€¦and guess what, the FMS seems much better.

Yeah, I may have got the FMS into an unhappy place. But Iā€™d be scared ********* if the AP never engaged in real life.

Why did Simbrief choose FL390? I chose the FBW airframe.
EDIT: Flying East requires an odd numbered flight level.

I engaged the AP soon after wheels up. Perhaps I missed an altitude requirement on a waypoint so the AP bailed out, for me to correct manually?

Running the flight again to FL370.

The FBW A320 should handle FL390 with no problem.
I just had that FL last evening with the FBW.

Well, donā€™t know what youā€™ve done before, but when the automatic fails itā€™s your part as the pilot to fly manually until you find out whatā€™s going wrong. Even an Airbus can be flown completely manually without autothrust and autopilot.

Probably itā€™s because of the beta, probably because of bad pilots skills. Without more information itā€™s impossible to find out for us.

Even on max payload you can go to FL390. Slowly and maybe not on a direct way but it is possible. You have to handle the plane very carefully then.

My money goes on bad pilot haha Thanks everyone for your help.

I did notice the left fuel tank was a lot lower than right, but not empty. Perhaps the FMS sees that as a bad imbalance; I turned on cross flow but that may have been too late.

Iā€™ll have to read up about pumping fuel left-right.

So youā€™ve breached whatā€™s known as Alpha floor protection, this basically is a system which kicks off the autopilot whenever a breach to normal operating conditions is observed. You in this case have breached the minimum safe operating speed so the AP has been turned off to force the pilot to make an alteration, in this case, increase your speed. The AP will not reconnect until this condition is met. The first comment is entirely correct but I thought Iā€™d shed some light upon whatā€™s actually caused this to happen to you. If you need to find out any more on this, google ā€œalpha floor protectionā€ and thereā€™s plenty information regarding this. Hope this helps you.

1 Like

Odd that your FMS is not indicating A.FLOOR or TOGA LK. Maybe you havenā€™t yet triggered it?

Thanks, yes I knew about alpha floor protection. I have a feeling engine 1 idled because of low fuel, which I didnā€™t notice.

Other aircraft are more forgiving with the AP kicking back in. The FBW does it correctly of course.

I got the fuelling balanced on the latest flight. Brussels Centre, radar contact FL390.

My wife will be amused as its the flight we will take to visit her brother.

EDIT: A.FLOOR did kick in. I got the speed back up but was trying to climb as well. Next time Iā€™ll fly her out of the problem, instead of expecting the AP to fix the problem.

On a sombre note I remember the A320 crash into the forest at the Air Show in 1988. Too low, too slow.

2 Likes

Glad you knew mate, thereā€™s so much to learn and discover when flying simulated aircraft and I thought Iā€™d try to be as helpful as possible. Iā€™ve only just had the time to read over what I had commented and I must apologise if I came across as condescending, it was not my intention in the slightest.

It took me a decade of flying in simulators and frequent research before ā€œaviate, navigate, communicateā€ finally sunk in but these things happen.

Iā€™m not advanced in age enough to remember that event but I have seen it covered on various documentaries to include Air crash investigation, terrible incident which essentially, could have been avoided but alternatively, we learn from our mistakes. Hope you have many more uneventful miles in the flybywire!

That was not the main reason for the crash. It happened because the engines didnā€™t spool up within the maximum allowed 8sec.
Airbus ā€˜modifiedā€™ the CVR and FDR tapes to disguise this fact.

None of these messages exist on the FMS (at least not IRL)

No worries.

The issue that tripped me up is that both stable and development FBW planes boot up with a significant difference between left and right inner fuel tanks, 14% and 79%. This seems unlikely in real life.

The MSFS sliders for fuel are ignored, you have to set the fuel via the fly bag which has an algorithm to fill the tanks in a specific order depending on how much fuel is required. As soon as the refill button is pressed, all the tanks are balanced which would involve pumping from right to left.

This quick video shows how the ground crew refill, https://www.youtube.com/watch?v=iiyQjDQCdk4

Yes, I meant PFD

I guess, really, the FMA on the PFD.

Please insert your favorite acronyms here ā†’

1 Like

Folks, this topic is not about real world incidents, please stick to the topic at hand.
FBW A320 AP1 drops out and will never engage again.

1 Like

I concur with the moderator. The specific problem is losing the AP, which was down to my lack of fuel management which caused engine 1 to idle, then A.Floor kicked in at high altitude.

Iā€™ve also noticed that saving the flight at altitude then loading it needs care with the Airbus throttle settings. Make sure throttle is on CLB, engines switched on, gear up, no flaps or speed brake before loading the saved flight. Get something wrong and the AP wonā€™t kick in, accidentally have engines off and A.FLOOR will kick in, pilot then has to fix everything before AP will engage.
Remember Captain Sully thought through the problem of no engines and turned on the APU to get hydraulic bleed to start them.

Iā€™ll amend the title to what I should have done :grinning:

1 Like