Plane crash on FL freeway

Question for two pilot cockpits. If Captain decides what action is to be taken just like this example and FO disagrees does Captain have the final word?
Yeah pretty much, the CA has the final word. Don't like it, don't fly crew.

Certainly one of the major reasons I've been dissuaded from pursuing it post .mil life. I did it for a while; didn't enjoy SIC life one bit. Closest I've ever got to dying by airplane miscontrol was in a crew wagon, and I fly with 100-hour neophites 3 feet from another airplane in IMC mind you. The only time I've ever had to write down phone numbers was during my tenure as a gear polisher, on account of the walking liability to my left. Absolutely cured me, I almost quit pro flying outright.

Students are much more ham handed and unpredictable on average, but they have never put me as close to the handle as peers have, precisely because of these power dynamics. Absolutely hate sharing a cockpit with peers. Same reason I don't fly with rated pilots recreationally.

In fairness, not all operations are created equal. Part 121 is probably the most standarized. Part 91 and 135 is russian roulette. No thanks.
 
Yeah pretty much, the CA has the final word. Don't like it, don't fly crew.

Certainly one of the major reasons I've been dissuaded from pursuing it post .mil life. I did it for a while; didn't enjoy SIC life one bit. Closest I've ever got to dying by airplane miscontrol was in a crew wagon, and I fly with 100-hour neophites 3 feet from another airplane in IMC mind you. The only time I've ever had to write down phone numbers was during my tenure as a gear polisher, on account of the walking liability to my left. Absolutely cured me, I almost quit pro flying outright.

Students are much more ham handed and unpredictable on average, but they have never put me as close to the handle as peers have, precisely because of these power dynamics. Absolutely hate sharing a cockpit with peers. Same reason I don't fly with rated pilots recreationally.

In fairness, not all operations are created equal. Part 121 is probably the most standarized. Part 91 and 135 is russian roulette. No thanks.

Curious, how much crew time do you have flying 121, Part 91 and 135?
 
I believe the water the FO saw was on the west side of the road. Go north aways, it's a lake not a ditch.
Whatever
I thing I see what you're saying. The lake on the West side of I-75, just South of Pine Ridge Rd?

Ooofff. Seems like an option, but still not a good one. Looks to be maybe slightly over 2500 ft long? With houses on either side? Maybe it would have worked better, maybe not.
 
For context, my question is why the owner/operator didn't follow the recommended GE maintenance procedures for CF34 engines operated in salt-laden environments to prevent such failures as documented in other similar operations?
I mean, just like any other similar situation where something wasn't accomplished / was pencil whipped.

Because money.

Will hold judgement until the final report is out, but it wouldn't be the first time a Pt 135 operator pencil-whipped required inspections that resulted in a fatality.
 
I mean, just like any other similar situation where something wasn't accomplished / was pencil whipped.
Except in the context of my comment you can’t pencil whip something that is not there. Per the docket, the GE standard engine wash interval was 400hrs with that being lowered to 300hrs or less in severe environments. The aircraft mx records show engine washes at 800hrs which was a carryover from the previous owner’s approved mx program and is plenty long enough to allow corrosion to develop. And given the posted aircraft maintenance history was performed by 3rd party shops vs internal company mechanics, I seriously doubt there was any pencil-whip involved.
 
Thought I'd trace their path to better discuss their other options.

From the Flightaware track, this appears to be about the point they lost the engines. The next data point shows a 20 kt loss in speed.

1757619476089.png

Seconds later they have lost speed and are turning towards the airport.

1757619520952.png

The last actual hit on Flightaware shows them approximately 500 feet, 112 knots and already abeam the one larger pond on the west side of the road. Personally I don't think they would have been able to maneuver to that pond. The time between each of these screenshots is about 20-30 seconds. They were low, slow, over heavily populated area, with not a lot of options. The fact they almost landed and had survivors is nothing short of a miracle of itself. If they hadn't gone for the road, they would have ended up in a neighborhood, and likely killed all on board and who knows what on the ground.

1757619559759.png
 
Thought I'd trace their path to better discuss their other options.

From the Flightaware track, this appears to be about the point they lost the engines. The next data point shows a 20 kt loss in speed.

View attachment 145017

Seconds later they have lost speed and are turning towards the airport.

View attachment 145018

The last actual hit on Flightaware shows them approximately 500 feet, 112 knots and already abeam the one larger pond on the west side of the road. Personally I don't think they would have been able to maneuver to that pond. The time between each of these screenshots is about 20-30 seconds. They were low, slow, over heavily populated area, with not a lot of options. The fact they almost landed and had survivors is nothing short of a miracle of itself. If they hadn't gone for the road, they would have ended up in a neighborhood, and likely killed all on board and who knows what on the ground.

View attachment 145019
Some on here would suggest they could have done a right 360 and landed on the golf course.
 
What was elapsed time between first indication of problem and touchdown?
 
74 seconds before they died, 2 pilots started making decisions that were their most important ever.

They selected a potential landing place from the options visible ahead, no look back for better behind them.

They configured the plane for landing, and arrived at ground level, still in control of the plane.

Things outside their control ruined the landing.

Their customers survived, and were at their destination!

No one on the ground died.

Unfortunately, both of those pilots died.

For my money, there was no better that they could have been expected to do.

Looking at the Google Earth images scares me , there is very little that I would have liked to put my Cessna 172 down on. At that altitude, the places visible ahead are the only ones that should be considered. 74 seconds... and dead. Bad luck, not bad decisions.

The condition that failed the engines were not something they could have found on preflight.

Continuing sympathy for their next of kin, they were great pilots to the end.

edited to add, as Ted says in the next post, "IT IS POSSIBLE TO MAKE NO MISTAKES, AND LOSE"
 
Last edited:
I don't work at the meatball engine company anymore, but when I did, I worked in the group that supported the CF34. Most of the work was on the -8s (like what @SixPapaCharlie now flies - CRJ 700/900/1000 and ERJ 170 engine) and the -10s (Embraer 190 and ARJ21 engine). It's important to note that the -3s (Challenger and CRJ 100/200 engines) are completely different from the -8s and especially the -10s. The -10s are basically a CFM56 (737 engine) that got put on a Xerox machine with a scale of 75%. The -8s were a "growth" development from the -3s to originally support the larger CRJ models, but were really more like a new design. They were all put under the same team, among other reasons, to make it easier for the OEMs who were consuming the engines on what amounted to the same platform. The -3s, -8s, and -10s share no components. The -3s are fully mechanical engines, while the -8s and -10s are FADEC controlled.

@Tools asked the question of whether the CF34-3s in this Challenger shared anything in common with the TF34. The answer is yes. The original CF34-1 (go back to earlier Challenger 600 series planes, used right after the ALF engine) was itself effectively a civilian derivative of the TF34. Certain items were changed for cost/practicality/use of the engines in civilian vs. military applications. The -3s were pretty similar to the -1s, I forget the specific changes made. This is an engine that has been around in some form or another since well before I was born and there is a tremendous amount of service history on it in military (TF34), civilian/GA (Challenger) and airline/121 (CRJ) applications.

Yes, for the sorts of military operations where TF34s were used (these engines were designed for landing on aircraft carriers - i.e. high salt environment, and have very strong bearings to handle those repeated impacts) it doesn't surprise me that a compressor wash/rinse was a daily item both because of the environment and also because the maintenance burden was minimal. The only time I've seen that done to some degree as a daily item was on off shore helicopters that are flying lower and right over the ocean. For fixed wing, even in more corrosive environments (like south Florida or the Caribbean), I've never seen a daily or even weekly wash as a requirement. Some form of hours is the norm.

As someone who used to look at these photos from engines that had had failures, I can tell differences between the accident engines and the "clean" engines, but it's not like you're looking at some bucket of compressed rust that's been at the bottom of the ocean. The corrosion inside the bore holes of the VSVs is of particular note, and it is also something that is completely invisible to a borescope, and also in an area where a compressor wash may or may not have successfully reached.

The data indicates that these engines had never come off wing of the aircraft, with something pushing 10k hours. This is normal. Engines of this level are very reliable and designed for long time on wing. On these engines, they become due for a "performance restoration" (basically a hot section inspection) on condition basis. From memory, the performance restoration is triggered by margin between redline T5 (ITT) and the T5/ITT temperature observed on takeoff. That may have been the -8s and -10s, again it's been a while. But I will say that 15k was a fairly typical number that we saw engines come in. 10k hours on a Challenger, I would completely believe those engines had not had cause to get pulled off wing, and weren't even necessarily all that close to needing it. There are life limited parts, but my recollection is that those don't come into play until later, more like the 25k hour range.

Given that, you have two engines that would, in fact, have had what amount to identical hours, cycles, environmental exposure, and conditions - exactly the sort of scenario that would potentially set this aircraft up for this sort of highly improbable failure when combined with a plane that had lived its life in this more corrosive environment of south Florida and the Caribbean.

On a Part 25 aircraft, the statistical probability that is required is a chance of a dual engine failure less than 10^-9. With every engine failure that occurred, we had to run the models to determine if we were above or below that number, and if above, we had to make changes to get back below it. I was in many of those meetings. We tend to think that probability is equal to 0. However it is not equal to 0, it is just very close to 0. Very low probability events can still happen. You do end up lowering your probability of a dual engine failure by having split engines on the aircraft (engines with different times/cycles/histories). There have been situations where this was intentionally done on certain aircraft fleets to mitigate/lower this risk when there was a known issue, although this is obviously impractical on a new aircraft and generally something that's more done in larger fleets. It is also very, very rare to have any cause to do this and this single event would not be a cause to do that. The document from GE indicates some changes to be made which look to be appropriate, and undoubtedly there is going to be more emphasis looking at hung starts and indications of issues with VSV actuation.

It's easy to Monday morning quarterback a lot of things - the engine limitations, the pilots decisions, the potential leading indicators of hung starts that didn't result in a deeper investigation. It would've been very likely that the miracle on the Hudson (another highly improbable dual engine failure, albeit for different reasons) had ended this way, were it not for a combination of luck and skill - and I would argue luck more than skill.

This is very sad, I think we can all agree on that. What comes to mind me above all else is:

"It is possible to commit no mistakes and still lose."
 
For fixed wing, even in more corrosive environments (like south Florida or the Caribbean), I've never seen a daily or even weekly wash as a requirement. Some form of hours is the norm.
Just to add, if you look deep enough, you’ll find similar recommendations on the fixed wing engine side, but as you note they are seldom followed outside the wash schedule. They touched on this in the docket report as noted below and even discussed FAA AC43-3 recommendations as well.

1757865366642.png
 
75 seconds or so.

That is about the same time I had in my one power loss event, which was an infinitely less challenging scenario. But the thing I remember most is how fast it happened. Time is unforgiving. It cannot be slowed or reversed. Every second elapsed is gone forever.

I am in awe that these pilots put their aircraft on the ground in a way that allowed all their passengers to survive. Stone cold heroes.
 
Looking back I still find it unbelievable that two engines would quit simultaneously from corrosion at the exact same time.
I accept the report just strange to me.
 
Looking back I still find it unbelievable that two engines would quit simultaneously from corrosion at the exact same time.
I accept the report just strange to me.

The only part that makes it somewhat believable, although almost odd, is both engines were installed new on the airframe and never were changed or received any heavy maintenance. They were as match a set of engines as you could find.
 
The only part that makes it somewhat believable, although almost odd, is both engines were installed new on the airframe and never were changed or received any heavy maintenance. They were as match a set of engines as you could find.

Piston twins almost never have the same TSMOH. One always goes before the other.
 
Looking back I still find it unbelievable that two engines would quit simultaneously from corrosion at the exact same time.
Seems like the VSVs liked getting stuck relatively frequently in the past few months of the aircraft's history. That's what caused the hung starts.
So you're not looking at a 1 in a million probability anymore, but maybe 1 in 10. With two engines, the probability of both of them experiencing the fault at the same time becomes 1 in 100, instead of 1 in 1 trillion. Still an unlucky day goe the crew, but it definitely becomes quite probable.

I'll ask the people that have experience flying those jets, how common is pulling them back to idle during approach? It seems to be the one thing that caused the compressors to stall once the VSVs stuck. Maybe if they had kept a bit more power on approach the compressor stalls wouldn't have happened.
 
Piston twins almost never have the same TSMOH. One always goes before the other.
No comparison really. At this level those engines are designed to be maintained "on-wing" for many 1000s of hours and is actually rather common to see from a maintenance point of view. Had these engines followed the OEM's recommendations from day one they probably would have made a few more 1000s of hours before hitting a cyclic limit or other life limit. Even other type turbine engines like PT6s can go around 7000hrs before removal on certain mx programs and have a similar result on a King Air or other twin where the engines time out together.
 
Seems like the VSVs liked getting stuck relatively frequently in the past few months of the aircraft's history. That's what caused the hung starts.
So you're not looking at a 1 in a million probability anymore,
but maybe 1 in 10. With two engines, the probability of both of them experiencing the fault at the same time becomes 1 in 100, instead of 1 in 1 trillion. Still an unlucky day goe the crew, but it definitely becomes quite probable.

Of course it is, and agreed. That's why I disagree with the prior arguments upthread of it being a gee chucks golden BB bad timing accident. Those engines were failing for a while, and the OEM engine addendum is damning. Of course, the maintenance derelicts are going to hide behind the CYA paperwork of whatever FAA-blessed crRtIfEd program sophistry to keep them out of prison, but it is nonetheless a case of cost-cutting dereliction to not wash those things off with any frequency, and it got people killed.

As you point out, with the documented history of start issues as a result of the materials degradation and outright partial seizure of bearings/engine subcomponents, for dozens of flights leading to the accident, those engines were not at their OEM assumed probabilities of failure. It's disingenuous to express this accident as a golden BB case. (Psub0) * (Psub0) is not what we're dealing with; this was a lot more probable. To add insult to injury, even the engines tried to save these people on the ground, over dozens of hung starts, signatories kept declaring them G2G. The "cld not replicate on gnd" brigade doing what they do best. From our wider-aperture folks over on reddit:

1757976971122.png


1757977076194.png

I also refer to the OEM here, when I refer to mx dereliciton. Not just the field people. The AD in question was not extended to the engines in question. In the spirit of my health insurance company: Delay, Deny, Defend. And I'll digress on Mario's brother retort to that shtick, because IBTL.
 
I'll ask the people that have experience flying those jets, how common is pulling them back to idle during approach?
It’s not uncommon to keep speed up and then reduce to idle to slow down until you can configure and add drag..
 
Of course, the maintenance derelicts are going to hide behind the CYA paperwork of whatever FAA-blessed crRtIfEd program sophistry to keep them out of prison
The interesting thing to your usual diatribe, is you still don’t get it when it comes to aircraft maintenance on any level. All maintenance starts and ends with the owner. You might think its all on the mechanic side, but I haven’t figured out yet if that is simply due to ignorance or you have never been taught properly how it works.

In the case of these CF34 engines, both the original owner and the 2nd owner elected the mx program to wash the engines at 800hrs vs what the OEM recommended for the environment they operated in. No different than your average Part 91 weekend warrior owner who only wants the minimum done. For example, on your former Piper, did you require your mechanic to perform all mx and inspections per the OEM inspection guides, SBs, SIs, and other bulletins? Or, did you request only the basics due to cost?

So I think you’ll find if the mechanics were actually in charge of the maintenance decisions, the CF34 engine wash would have been at a 200 hour interval with a fresh water rinse after each flight day and the hung start troubleshooting would have included the MP68 check of the IVG and VGs. But you know those owners and their money….
 
Of course it is, and agreed. That's why I disagree with the prior arguments upthread of it being a gee chucks golden BB bad timing accident. Those engines were failing for a while, and the OEM engine addendum is damning. Of course, the maintenance derelicts are going to hide behind the CYA paperwork of whatever FAA-blessed crRtIfEd program sophistry to keep them out of prison, but it is nonetheless a case of cost-cutting dereliction to not wash those things off with any frequency, and it got people killed.

As you point out, with the documented history of start issues as a result of the materials degradation and outright partial seizure of bearings/engine subcomponents, for dozens of flights leading to the accident, those engines were not at their OEM assumed probabilities of failure. It's disingenuous to express this accident as a golden BB case. (Psub0) * (Psub0) is not what we're dealing with; this was a lot more probable. To add insult to injury, even the engines tried to save these people on the ground, over dozens of hung starts, signatories kept declaring them G2G. The "cld not replicate on gnd" brigade doing what they do best. From our wider-aperture folks over on reddit:

View attachment 145141


View attachment 145142

I also refer to the OEM here, when I refer to mx dereliciton. Not just the field people. The AD in question was not extended to the engines in question. In the spirit of my health insurance company: Delay, Deny, Defend. And I'll digress on Mario's brother retort to that shtick, because IBTL.
Having been on the "other end" (manufacturer) for a couple of decades prior to retirement (and also publishing the repair specs for many engines) I can say that it's likely that the GE people assume that all recommended maintenance has been performed and give their recommendation based on that.
 
Does being arrogant and condescending come naturally for you, or do you have to work at it? Just wondering…

iu
 
I can say that it's likely that the GE people assume that all recommended maintenance has been performed and give their recommendation based on that.
Exactly. Troubleshooting processes are designed to give guidance to fix a specific problem based on historical data. Not to determine the overall condition of the aircraft. That is what the mx program is for. Unfortunarely, GE will now be penalizing all CF34 owners with added mx costs in light of the findings with this incident.
 
Of course it is, and agreed. That's why I disagree with the prior arguments upthread of it being a gee chucks golden BB bad timing accident. Those engines were failing for a while, and the OEM engine addendum is damning. Of course, the maintenance derelicts are going to hide behind the CYA paperwork of whatever FAA-blessed crRtIfEd program sophistry to keep them out of prison, but it is nonetheless a case of cost-cutting dereliction to not wash those things off with any frequency, and it got people killed.

As you point out, with the documented history of start issues as a result of the materials degradation and outright partial seizure of bearings/engine subcomponents, for dozens of flights leading to the accident, those engines were not at their OEM assumed probabilities of failure. It's disingenuous to express this accident as a golden BB case. (Psub0) * (Psub0) is not what we're dealing with; this was a lot more probable. To add insult to injury, even the engines tried to save these people on the ground, over dozens of hung starts, signatories kept declaring them G2G. The "cld not replicate on gnd" brigade doing what they do best. From our wider-aperture folks over on reddit:

View attachment 145141


View attachment 145142

I also refer to the OEM here, when I refer to mx dereliciton. Not just the field people. The AD in question was not extended to the engines in question. In the spirit of my health insurance company: Delay, Deny, Defend. And I'll digress on Mario's brother retort to that shtick, because IBTL.
Your buddy Occam left you hangin’ on this one.
 
Still find it hard to believe both engines froze up simultaneously.
 
They suffered compressor stalls, cause by seizure of the adjustable vanes, not seizure of the rotating assembly. In my rapid read, anyway.
I know. What’s the chance both at the same time? Has it ever happened before?
 
Can someone explain to me what this means?
In general, turbine engines are designed to operate per a specific fuel schedule throughout the power cycle. When the fuel flow does not match the internal airflow, its considered "out of schedule" and will not operate within its design specifications. In these engines, the VGs were sticking due to the corrosion, which led to the compressor stalls and lost of thrust.

Still find it hard to believe both engines froze up simultaneously.
Both engines were maintained in an identical manner that did not follow the recommended process for operations in a salt-laden environment. Given both engines were original to the aircraft and probably never removed, I would have been suspect if they hadn't degraded at the same or similar rate.
 
I know. What’s the chance both at the same time? Has it ever happened before?
One out of 33. See top of page 3 in the report. The previous 32 flights apparently didn't encounter the exact same set of factors.
 
One out of 33. See top of page 3 in the report. The previous 32 flights apparently didn't encounter the exact same set of factors.
They say hung starts? Really don’t know what that is. Like a hot start? I was thinking in flight engine failures instead like the accident.
 
They say hung starts? Really don’t know what that is. Like a hot start?
No. In a hung start the engine lights off normally but at some point, before idle speed, the engine RPM does not accelerate. With these engines, it became apparent during the investigation the hung starts were related to the sticking VG system. However, the previous start problems were corrected prior to reaching the VG system check in the T/shoot procedures.

I was thinking in flight engine failures instead like the accident.
I believe there had been 1 or 2 other dual engine decels but do not recall the cause. Regardless, the current and previous operators created a perfect storm condition with this aircraft that evaded normal mx practices until the accident. Fortunately, or unfortunately, this specific cause will not be duplicated given the extensive mitigative changes put in place since the accident.
 
Last edited:
Back
Top