PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Rotorheads (https://www.pprune.org/rotorheads-23/)
-   -   Caverton AW139 incident in Jan 2024 (https://www.pprune.org/rotorheads/658260-caverton-aw139-incident-jan-2024-a.html)

nowherespecial 20th Mar 2024 05:15

Caverton AW139 incident in Jan 2024
 
Summary: Loss of AP while airborne leads to unusual attitudes for several minutes in flight. Many unhappy passengers.

This looks like it was a bit exciting. Anyone have any insight as to if the correct procedures were followed?

https://nsib.gov.ng/wp-content/uploa...t_5N-BSG-1.pdf


Nescafe 20th Mar 2024 05:28

The QRH states that following a single AP Fail

”- If subsequent 1-2 AP fail caution illuminates
- Continue flight manually not exceeding 140 KIAS (100 KIAS in turbulence,
IMC or approach)”

Nowhere does it mention resetting them repeatedly or shutting off the gang bar.

torqueshow 20th Mar 2024 06:14

Anecdotally the 139 year would regularly drop APs, especially on approach and it wasn’t uncommon for the PM to “guard” the AP buttons on the AFCS panel for a quick attempted reengagement.

Nothing wrong with seeing if it will come back on. But 5 attempted resets followed by turning off both generators at the same time in flight via the gang bar is bizarre.

The 139 can be a handful without the APs but not 3000ft to 300ft in 45s, perhaps more time should be spent on training manual control of the aircraft with and without AP. Seems like subsequent loss of AP1 after messing around with the electrics wasn’t expected followed by panicked over controlling.

nowherespecial 20th Mar 2024 06:22

Megan, I think Nescafe was referring to the QRH not mentioning resetting the Gangbar. The report clearly states that's what the crew did.

Thanks all for the information. Sounds like a major mishandling of the aircraft then.

griffothefog 20th Mar 2024 07:48

It’s always ok when everything works, but simple failures offered in the sim result in the most bizarre behaviours in my experience ( as a former TRE on the 139 ), some would have me tightening the seatbelt even… 🤭

deeceethree 20th Mar 2024 08:46

The Preliminary Report makes disturbing reading. The two pilots seem utterly preoccupied in keeping the autopilots engaged, and repeated pressing of buttons seems to be their preferred course of action, during which the aircraft is all over the place:

According to FDR data, simultaneous with the attempts to re-engage the AFCS, the aircraft climbed to about 3,500 ft within a period of 1 min and 40 s, followed by a rapid descent to 330 ft in 45 s. FDR shows that the aircraft commenced another climb to 2,500 ft in the next 2 mins within which period, several pitch and roll control inputs were recorded; pitch angle varied between 28° pitch up and 12o pitch down before a maximum 25° pitch down motion was recorded, simultaneous with the maximum recorded roll angle of 37° to the right.

Over the next 44 s, the PF attempted to correct the right roll unto datum and continued into a left roll to a maximum angle of 15° before recovering to level flight 9 min later, following a series of roll attitude corrections.

The 'Initial Findings' section of the Prelim report states "8. The serious incident occurred in Instrument Meteorological Conditions (IMC)." The preoccupation with autopilot engagement (never mind the 45 second dive from 3500 ft to 330 feet!) leaves me with a distinct impression that the pilots were very reluctant to manually fly the aircraft! Is that because they are not confident about doing so in IMC, perhaps rarely practising doing so?

A few more items of interest from 'Initial Findings' section of the Prelim Report:

3. The First Officer’s medical certificate validity expired on 15th January 2024.
[Expired 5 days before this incident, which occurred 20th January 2024.]
......
9. The crew experienced failure of the Auto Pilot systems (AP 1 and AP 2) and the
aircraft entered ’unusual attitude’.
......
10. The FDR captured multiple unusual attitudes within a 5-min period.
......
16. The CVR recordings of the event were overwritten."

Additionally, "The aircraft sustained minor damage.":

The following damages were observed during post occurrence inspection of the aircraft:
1. Two cabin windows were blown out in flight, and missing on ground.
2. Debris from a broken third window was found in the cabin.
3. A main rotor blade had a broken glass shrapnel stuck to the blade root.
4. The main rotor lightning conductor was broken.
5. A cabin light lens and transparent light cover were broken.


Originally Posted by nowherespecial (Post 11619670)
Many unhappy passengers.

Yes, I can sympathise with that. 😲

212man 20th Mar 2024 10:45

I am in no way defending the crew's actions but, when discussing manual flying, I think it's worth remembering that having turned off the generators they were left with standby instruments only and zero stabilisation (in IMC), so it was a bit more complicated than simply hand flying. Nonetheless, pretty astonishing to have been out of control for that length of time. I find the crew's actions in making non-standard interventions, resulting in a loss of control, reminiscent of the AirAsia accident a few years ago: https://en.wikipedia.org/wiki/Indone...ia_Flight_8501

n December 2015, the Indonesian National Transportation Safety Committee (KNKT or NTSC) released a report concluding that a non-critical malfunction in the rudder control system prompted the captain to perform a non-standard reset of the on-board flight control computers. Control of the aircraft was subsequently lost, resulting in a stall and uncontrolled descent into the sea. Miscommunication between the two pilots was cited as a contributing factor.[1][2][3]
It will be very interesting to see the final report and more data on the flight trajectory. Anecdotally I have heard they fell out of the cloud base at 1500 ft doing 13,000 ft/min (7 seconds to impact) and pulled 4g in the recovery!

EDIT - I am hearing from a friend that when you move the electrical gangbar it takes out the battery too, so also the standby instruments (an integrated EFIS). So, even when you realise your error and reset it, everything has to power up, go through their BITs etc and come on line. So, unstabilised in IMC with no instruments - sporty!

Can any 139 pilots confirm?

malabo 20th Mar 2024 17:26

The 139 was developed and marketed as a fully PC1 aircraft, including procedures and profiles to deal with that dreaded single engine failure.
On approach, the profile will settle you in a high vibration regime that could kick the AP's off. If you'd flown a 500 and instinctively minimized time in paint-shaker mode you'd be up in front of the FDM board explaining why you deviated from the PC1 profile.
I don't know Caverton's training, but likely focussed on engine failures (PC1 myopia). Not much time left over for AP's off, or standby instrument recovery from IMC. Not much different in the rest of the world.
I flew for a large operator that would regularly do both AP off training in the 139 aircraft, as did the factory. I noted other operators prohibited their training staff from doing this, citing a POH limitation.
Nothing like lifting off a deck at night with both AP's still off ....

I recall another highly-feted Nigerian crew ditching an S76 offshore after forgetting the AP's and deeming the aircraft too unstable to fly. Limited training time, focus on what the regulator wants to prioritize. In another case a droopy-eyed expat lost it in cloud between the beach and PH, saved by his sharp Nigerian national copilot.

212man 20th Mar 2024 19:32


I recall another highly-feted Nigerian crew ditching an S76 offshore after forgetting the AP's and deeming the aircraft too unstable to fly.
Not quite - left the compasses in DG then the AP didn’t behave as they expected. But, hailed as heroes in the local press


or standby instrument recovery from IMC.
Seems like they may not have had any instruments for a bit - see my last post.

Nescafe 20th Mar 2024 21:26


​​EDIT - I am hearing from a friend that when you move the electrical gangbar it takes out the battery too, so also the standby instruments (an integrated EFIS). ​​ ​​​
From the AW139 Technical Notes

”Red Gang Bar moved backwards cuts off all aircraft electrical power sources at the same time. (Gen 1 & 2 and Battery Master switches are moved to OFF all together.)”

The Battery Master switch needs to be on to enable the Main and Aux to be connected to Main Bus 1 & 2.

212man 20th Mar 2024 21:45


Originally Posted by Nescafe (Post 11620257)
From the AW139 Technical Notes

”Red Gang Bar moved backwards cuts off all aircraft electrical power sources at the same time. (Gen 1 & 2 and Battery Master switches are moved to OFF all together.)”

The Battery Master switch needs to be on to enable the Main and Aux to be connected to Main Bus 1 & 2.

Thanks - seems to corroborate my info. So, given that most AHRS normally take about 30” to come online when sitting on the ground motionless, and a minute or two in flight, or on a moving deck, one can imagine that they take a bit longer while doing aerobatics!

casper64 20th Mar 2024 22:52

Just FLY the damn chopper! Or have we forgotten how???

212man 21st Mar 2024 09:59


Originally Posted by casper64 (Post 11620342)
Just FLY the damn chopper! Or have we forgotten how???

I don't think anybody would argue with that sentiment, but it's not clear what phase of this event you're referring to? With the AP drop out, then of course fly the aircraft and follow the QRH - which says decouple the Flight Director, ergo fly manually with the remaining AP in ATT mode. Some OEMs say try to attain VMC, but I see the 139 QRH does not say this. It does say that if the other AP fails then reduce speed to below 100 KIAS, and it also says (in the limitations section) that taking the APs out of ATT mode in IMC is forbidden.

However, from what we are now learning, the captain used the electrical gangbar, which turned off all the electrics at once, leaving them with no flight instruments at all, and a totally unstabilised aircraft which, I am sure, would have rapidly departed normal flight. Even with the electrics restored immediately, there would not have been any usable attitude information for quite some time, so the concept of "just flying the damn aircraft" is a bit moot at this point - they were essentially passengers. I think that had the cloud base (which gave them the visual references for recovery) been much lower this would have been a fatal accident.

Caverton has a Level D FFS in their main base, so it would be very interesting to see how this event looks like replicated in there! No doubt, that has already happened....

Uplinker 21st Mar 2024 15:01

A graphic example of why it is a very bad idea to make up your own drills or actions. Thank goodness that all survived this, with only minor damage to their underwear.

This gang-bar reset thing sounds as if the Captain had done it before, but didn't think about the battery also going off and losing the standby instruments - I mean who would intentionally switch off ALL electrical sources in flight, unless the actual published QRH or published memory drill demanded it ?

Out of interest; what caused the windows to smash in this incidence ?

Aser 21st Mar 2024 15:11


Originally Posted by 212man (Post 11620582)
With the AP drop out, then of course fly the aircraft and follow the QRH - which says decouple the Flight Director,

If during Non SAR mission
- Continue flight attentive do not exceed Vne-27 KIAS in level flight, or 100 KIAS and 1000 fpm in climb.
- Decouple FD (below 500 ft (152 m) AGL fly manually) unless in approach, missed approach,AFCS approach and departure to/from hover and hover

As another pprune user usually says, just start the clock and don't touch anything... :}

212man 21st Mar 2024 15:41


Originally Posted by Aser (Post 11620819)
If during Non SAR mission
- Continue flight attentive do not exceed Vne-27 KIAS in level flight, or 100 KIAS and 1000 fpm in climb.
- Decouple FD (below 500 ft (152 m) AGL fly manually) unless in approach, missed approach,AFCS approach and departure to/from hover and hover

As another pprune user usually says, just start the clock and don't touch anything... :}

I have an old uncontrolled copy that has similar but slightly different wording - thanks for the update.


Out of interest; what caused the windows to smash in this incidence ?
​​​​​​​My assumption is either fuselage flexing, or extreme side-winds, but just a guess.

Bravo73 21st Mar 2024 18:34


Originally Posted by Uplinker (Post 11620814)
Out of interest; what caused the windows to smash in this incidence ?

It could have been the passengers, looking for a way out.

Wouldn't you consider it if you were down the back?

Uplinker 21st Mar 2024 19:03

To get out on the ground, possibly if the door didn't open and getting out was imperative. But there was no reason to exit in an emergency, was there ?

For some reason, I thought they meant the windows had smashed in flight somehow.

Captain Catastrophy 21st Mar 2024 19:32

Interestingly this recently cropped up in the sim ( unrelated ) and - as stated - the gangbar shuts down everything and takes about 30 seconds for everything to reboot during which time the aircraft could do anything. In this case the aircraft was recoverable but was in a very unusual attitude when the lights came back on.............. Turning everything off ON THE GROUND was an unofficial engineering CTR ALT DEL to clear snags otherwise requirering a shutdown etc etc. It was never recommended to crews and certainly not in flight...

212man 21st Mar 2024 20:26

Nagging question for 139 experts - how was the FDR recording the flight parameters after the power was cut? I can imagine it was powered up immediately after the gangbar use, but what about the data?


All times are GMT. The time now is 14:05.


Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.