Boeing Boeing 737 Cargo Plane Ditches off Honolulu

  • Thread starter Thread starter berkeman
  • Start date Start date
  • Tags Tags
    Plane
AI Thread Summary
A Boeing 737 cargo plane ditched off Honolulu, resulting in severe injuries to both pilots, with one in critical condition. The aircraft lost both engines shortly after takeoff, complicating the ditching process as they had no landing lights. The U.S. Coast Guard responded quickly but faced challenges due to darkness and debris in the water. Discussions highlighted the pilots' reliance on checklists instead of prioritizing immediate emergency procedures, raising questions about aviation protocols. The incident underscores the rarity of dual engine failures and the need for improved emergency response strategies in such scenarios.
berkeman
Admin
Messages
69,127
Reaction score
24,063
Yikes, this was a lot harder ditch/landing than I initially thought from the first reports. I thought they came in for the ditch with landing lights on so the pilot could judge the touchdown, but apparently with both engines off they had no lights (the APU can't power the landing lights?). No wonder the injuries to the pilot and co-pilot were so severe. I hope they both survive, although the one in critical condition sounds dicey...

https://abc7news.com/2-pilots-alive-after-plane-crashes-near-hawaii/10853475/

One pilot, a 58-year-old man, was hospitalized in critical condition, according to the Honolulu Fire Department.

The second pilot, who is 50, suffered a head injury and multiple lacerations, and was hospitalized in serious condition, according to Honolulu EMS.

The U.S. Coast Guard arrived at the scene of the crash within minutes of the call to them, but roughly an hour after the crash, the agency said.

The Coast Guard said rescuers were dealing with 17 mph winds, and even with night vision goggles it was extremely dark. By the time they arrived, there was a large oil slick in the water and lots of debris around the crash site.

At that time, they saw one of the cargo plane's pilots on the tip of the downed air plane waving his hands, and the other pilot bobbing in the ocean on a cargo load.

The Coast Guard said the intention was to rescue the pilot floating on the cargo first, but within seconds the tail of the plane began to disappear so they deployed a rescue swimmer to help the pilot who had been on the tail."It is extraordinary that both of the pilots survived this, because it was the middle that night," said ABC News contributor and retired Marine Col. Steve Ganyard. "They were trying to ditch with no engines and no lights ... not [able] see the tops of the waves."
 
  • Wow
  • Informative
  • Like
Likes Klystron, Astronuc and Lnewqban
Physics news on Phys.org
berkeman said:
Yikes, this was a lot harder ditch/landing than I initially thought from the first reports. I thought they came in for the ditch with landing lights on so the pilot could judge the touchdown, but apparently with both engines off they had no lights (the APU can't power the landing lights?).
If memory serves from The Miracle on the Hudson, that wasn't on any of the relevant checklists, and Sully elected to do it on his own. Not sure if the checklists have changed...

But yeah, it's hard enough to land on a calm river in the daytime.
 
The U.S. Coast Guard arrived at the scene of the crash within minutes of the call to them, but roughly an hour after the crash, the agency said.

That's odd. The ABC news report said that the pilots asked for the Coast Guard before they ditched. Why the hour delay?
 
  • Like
Likes FactChecker
Helicopters be slow...
 
berkeman said:
Helicopters be slow...
Yes, and in aviation and SAR work, sometimes you are better off not rushing out too fast. SOPs are good. SAR rule #1: don't add your name to the list of victims.

I also think that old phrase "work smarter, not harder" may come into play. The pacific ocean is a big place. The goal isn't to search, it's to find and rescue.

None of us are in a position to know how fast these guys should have been.
 
Last edited:
  • Informative
  • Like
Likes phinds, Klystron and nsaspook
The U.S. Coast Guard arrived at the scene of the crash within minutes of the call to them, but roughly an hour after the crash, the agency said.

I think this part of the reporting is just wrong. The VASA transcript of the radio traffic (below) shows that the CG was called even before the plane crashed. There was no hour delay before notifying the CG.

The cause of the engine failures is not obvious. It doesn't sound like bird strikes. Since the pilots elected to use a long checklist rather than an immediate return, it suggests that they expected the 2nd engine to continue working. They were wrong about that and they got caught by surprise too far away from the airport to glide back.

The results of the investigation will be interesting to read.
 
  • Like
  • Wow
Likes Astronuc, russ_watters and FactChecker

 
Last edited:
They probably could have made Kalaeloa, if they had requested or were informed earlier. But the runways at Kalaeloa seem shorter.

Boeing/airlines will have to think about how an aircraft functions with loss of two engines. All critical equipment that needs electrical power should receive power from the APU. Then again, I've seen cases where the APU has been out of service.

Aircraft N810TA, Boeing 737-275C(A), First flight July 23, 1975, almost 46 years old! Engines 2x PW JT8D-9A
 
Last edited:
  • #10
Astronuc said:
They probably could have made Kalaeloa, if they had requested or were informed earlier. But the runways at Kalaeloa seem shorter.
Much better than Kelaeloa, they could have stayed within gliding range of their takeoff runway the whole time. They declared an emergency early, so the controllers would have kept everyone else away if requested. I think they trusted that the 2nd engine would not fail.

Deploying the APU creates more drag and thus reduces your gliding radius. Your strategy when gliding at low altitude is very different than when powered or when gliding at ample altitude.
 
  • Like
Likes russ_watters
  • #11
anorlunda said:
I think they trusted that the 2nd engine would not fail.
The audio recording indicated that they were expecting to lose the second engine (it was running hot). The reports indicated both engines had failed before the crash. The aircraft was at 2000 ft, and not much elevation for distance.
 
  • #12
Astronuc said:
The audio recording indicated that they were expecting to lose the second engine (it was running hot).
Yes, but look at their position when they reported that. They were too far away and too low to glide back by the time they reported trouble with the second engine. They could have stayed within a mile or two of the runway the whole time, but they chose not to.
 
  • Like
Likes russ_watters
  • #13
anorlunda said:
Yes, but look at their position when they reported that. They were too far away and too low to glide back by the time they reported trouble with the second engine. They could have stayed within a mile or two of the runway the whole time, but they chose not to.
Ok, I understand you point now. I was thinking about where they turned. The pilot does mention delaying the turn back while they do their checklist.
 
  • #14
All pilots are schooled on their three priorities which they must never forget. 1-Aviate, 2-navigate, 3-communicate. Use checklists doesn't appear as one of the priorities; perhaps it should be. There have been several crashes where the pilots focused on emergency procedure checklists to the exclusion of aviate/navigate/communicate.

Cockpit resource management dictates delegation of tasks. One should aviate/navigate/communicate while the 2nd pilot does other important things.

In December of 1972, Eastern Airlines Flight 401, ferociously collided with the Florida Everglades. The plane was an L-1011-1 Tristar jumbo jet, which marked the first crash of a widebody aircraft. Reports claimed that the entire crew was busy attending to a faulty light bulb, and they were completely oblivious to the fact they were rapidly falling in altitude.
 
  • Like
Likes russ_watters
  • #15
anorlunda said:
Deploying the APU creates more drag and thus reduces your gliding radius.
I think you're confusing this with a RAT. The APU is a small gas turbine generator that has essentially no additional drag. However, the pilot would have to turn it on.
 
  • Like
Likes russ_watters
  • #16
anorlunda said:
I think they trusted that the 2nd engine would not fail.
Astronuc said:
Boeing/airlines will have to think about how an aircraft functions with loss of two engines

This is very, very rare. This has happened, as far as I can tell, five times with the 737. Two were double-flameouts in thunderstorms (one as the plane was about to touch down). One was running out of fuel. One was a famous double bird strike (US1549) and one was pilot error: one engine failed and the crew shut down the other one by mistake.

This is over 184 million flights. It's a 3 x 10-8 problem. It's not surprising that the pilots worked the "what to do when you lose one engine" problem first. Put another way, the frequency of a double-engine loss per aircraft is once per 7000 years or so.
 
  • Like
  • Informative
Likes russ_watters and nsaspook
  • #17
Astronuc said:
Boeing/airlines will have to think about how an aircraft functions with loss of two engines.
They do put a lot of thought into this, that's one reason there's an APU. However, there is a limit to what you can do with an airplane with no engines. Also, remember that the 737-200 was designed in the mid-1960's.
 
  • #18
anorlunda said:
All pilots are schooled on their three priorities which they must never forget. 1-Aviate, 2-navigate, 3-communicate. Use checklists doesn't appear as one of the priorities; perhaps it should be.
I’m about a month from my private pilot checkride. Some expansion/clarification: ABC is always overriding, but specific circumstances carry additional requirements, including checklists.

In a small/single engine plane engine failure, you have:

A - Airpeed for best glide ratio
B - [identify]Best place to land
C - Checkists; memory items first, more detailed ones as the situation permits.
D - Declare an emergency
E - Execute the landing

Obviously the specifics of the situation dictate the specific approach. I agree that at least it would be good to stay close to the airport.

https://studentpilotnews.com/2019/04/22/if-faced-with-an-engine-failure-remember-your-abcs/

Dual engine failures often have a common cause. It will be interesting to see what this one was.
 
  • #19
russ_watters said:
C - Checkists; memory items first, more detailed ones as the situation permits.
Situation permitting is the key. One obvious situation not permitting is when you meet the ground before finishing reading the checklist.

I assume that the VASA transcript is real time.
  • At 0:26 in the VASA transcript, Flight 810 was cleared for takeoff.
  • At 0:36 in the VASA transcript, Flight 810 said, "We'll have to return."
  • For more than a minute, it sounded like the controller did not hear 810's transmissions, and also confused 810 with the inbound flight 809.
  • At 1:50 in the VASA transcript, the controller cleared 810 to return to the airport. Flight 810's reply was, "We are going to have to run some checklists, if we could get delay vectors..."
  • At 3:17 in the VASA transcript, the pilot asked to return to the airport, and said that they no longer had the airport in sight.
  • At 3:42 in the VASA transcript, Flight 810 said, "We might lose the other engine as well."
So they spent at least 87 seconds on the checklist, all the while heading out to sea away from the safe landing site at the airport, and eventually out of visual range of the airport. I am not trying to suggest that the pilots were in error. Only the NTSB can pronounce the final cause.

With only 10 seconds between takeoff clearance and the pilot's call to return, it sounds like the first engine failed during or immediately after takeoff.
 
  • Like
Likes russ_watters
  • #20
anorlunda said:
Since the pilots elected to use a long checklist rather than an immediate return
It appears that the checklist was the one for landing a 737 on one engine. Things like turning on the APU. Also, if you listen to the ATC, this event really did not unfold in a whole lot of time.
 
  • #21
I'm guessing that turning on the APU will be moved up in the 1-engine checklist now when it is dark. Landing in the water or on land in the total dark versus with landing lights on seems very problematic.
 
  • #22
berkeman said:
I'm guessing that turning on the APU will be moved up in the 1-engine checklist now when it is dark
Maybe. Maybe not. One needs to keep in mind that 99.5% of the time losing one engine does not cause loss of the second, but does lead to a safe landing. You don't want to make changes to improve the 0.5% and in the process make the 99.5% worse.
 
  • Like
Likes russ_watters and anorlunda
  • #23
It's really astonishing that if you lose an engine, your odds of survival are still ~99.8%. (99.5% you keep the other engine, and even if both are lost, the survival rate seems to be over 50%)

It's hard to imagine independently losing two engines.

I was looking up NTSB reports of double engine losses, and found one due to fuel contamination. UA310 LAX-DEN on 19 August 1983 lost power in both engines "the inability of the engines to accelerate after the manually induced surge was due to contaminated fuel nozzles [emphasis mine] which significantly reduced combustion chamber efficiencies & which resulted in a subidle stall."

The same plane experienced a double flameout 2-1/2 years later, apparently due to pilot error.

Jet engines will burn pretty much anything that can burn. I suspect that "fuel contamination" really means "fuel filter clogged by contaminants".
 
  • #24
Out of fuel is another reason. It applies regardless of how many engines you have.

Of course all common mode multiple failures are not statistically independent events, so the usual way to compute probabilities doesn't apply. Nor are they reported as multiple engine failures.

High AOA can also stall all engines. Faulty maintenance can also be a common mode failures.Once in the UK, the right engine failed, but the pilot mistakenly shut down the left engine. Not a multiple engine failure.

IMO in this case in Hawaii, the probability of a common mode cause (like bird strikes) is high
 
  • #25
anorlunda said:
Once in the UK, the right engine failed, but the pilot mistakenly shut down the left engine. Not a multiple engine failure.
I included that one.
anorlunda said:
IMO in this case in Hawaii, the probability of a common mode cause (like bird strikes) is high

I can't think of any large birds native to Oahu. There is the nene, of course, but not so many on Oahu. They're also more walkers than flyers. I won't say this is imposible, but not the first thing to come to mind.
 
  • #26
https://www.travelandleisure.com/travel-tips/responsible-travel/hawaii-largest-protected-area

1625519612926.png


Debris on the runway is another possible common cause. We can probably think of several other common causes.
 
  • Informative
Likes Klystron, Vanadium 50 and berkeman
  • #27
Look at all the targets! :wink:

Thing is, this isn't anywhere near Oahu. I'm not arguing that there were two independent failures - that's ridiculously improbable - just that a flock of birds is not high on my list of likely culprits. Debris is certainly one possibility. Engine damage of some sort on the inbound that worsened when the engines were powered down is a possibility. My favorite at the moment is fuel contamination of some sort. The Oracle of Google tells me there have been three incidents involving DEF contamination in jet fuel.
 
  • Like
Likes DaveE and anorlunda
  • #28
I haven't been keeping up -- did they locate the plane on the bottom and have they recovered the data recording boxes?
 
  • #29
I did a quick Google search, and it looks like they are working on the recovery...

1625523300351.png
 
  • #30
The water is quite deep - a few hundred feet. (I know...Pearl Harbor would be a swell place to put a Navy base) It may take some specialized gear.
 
  • #31
Vanadium 50 said:
Jet engines will burn pretty much anything that can burn. I suspect that "fuel contamination" really means "fuel filter clogged by contaminants".
Water is a common contaminant.
 
  • Like
Likes Vanadium 50
  • #32
They said the second engine was overheating. Does anyone know what makes a jet engine overheat?
 
  • #33
Oil starvation.
 
  • Like
Likes Astronuc, russ_watters and anorlunda
  • #34
Do the engines share a common fuel supply? or does each have its own tank(s)?
 
  • #35
gmax137 said:
Do the engines share a common fuel supply? or does each have its own tank(s)?
Typically, each engine has its own tank. There is a valve that can be opened to transfer from one tank to the other, but that valve is normally closed.

But both tanks may have been filled from a common source.

In searching for a common cause, I would skip all possibilities that do not lead to engine overheating. But the term overheating is not precise. EGT, exhaust gas temperature is my first guess, but there can be other temperature sensors on the engines.

Below is some discussion from another site. It suggests that internal damage can cause high EGT. That would make high EGT a secondary effect, not the primary one.
https://www.airliners.net/forum/viewtopic.php?t=762413
high EGT is due to high fuel flow. As an engine gets older the fuel flow and EGT will increase as the compressors and turbines get worn and have to work harder to do the job. I have seen over 50degC different EGT between two engines on the same aircraft, due to age. So you need to boroscope the engine to check the complete gas path for damage, not only blades and NGVs, but also the inside of the combuster for damage.. Take out the burners and check they are clean, they easily get clogged with carbon.
 
  • Like
Likes russ_watters
  • #36
russ_watters said:
I’m about a month from my private pilot checkride. Some expansion/clarification: ABC is always overriding, but specific circumstances carry additional requirements, including checklists.

In a small/single engine plane engine failure, you have:

A - Airpeed for best glide ratio
B - [identify]Best place to land
C - Checkists; memory items first, more detailed ones as the situation permits.
D - Declare an emergency
E - Execute the landing

Obviously the specifics of the situation dictate the specific approach. I agree that at least it would be good to stay close to the airport.

https://studentpilotnews.com/2019/04/22/if-faced-with-an-engine-failure-remember-your-abcs/

Dual engine failures often have a common cause. It will be interesting to see what this one was.
I think "often" is underselling it a bit. Has there ever, in the history of commercial jet aviation, been a dual independent failure? I certainly can't think of one. There are certainly cases where all engines failed on multiengine jets, but every case I can think of is common cause (flying into an ash cloud, flying into a goose cloud, flaws in the design of fuel filters combined with extremely cold fuel causing ice buildup and fuel starvation, running out of fuel due to improper unit conversion, etc). In addition, single engine failure isn't all that uncommon, so it's extremely understandable that the pilots would've been perfectly comfortable exiting gliding range (but still staying relatively near to the airport) while troubleshooting, executing checklists, evaluating the aircraft behavior, etc.

At least on the surface level, this doesn't appear to be something that would require a major change in procedure or aircraft design philosophy to fix, aside from perhaps just advising pilots that it is best practice to remain within gliding distance (if possible) while performing evaluations and troubleshooting after an engine failure.
 
  • Like
Likes russ_watters
  • #37
gmax137 said:
Do the engines share a common fuel supply? or does each have its own tank(s)?
Typically, tanks are in the wings, with each engine drawing from the tank on its own wing, but the 737 does have a center tank as well. In addition, there are pumps that can move fuel around between tanks, so it's at best only somewhat isolated. This is because a side to side weight imbalance would be a very serious problem, and the engines do not burn precisely identical amounts of fuel, so it's very common to move a little back and forth to keep the plane balanced during flight. Adding to this, once you have a single engine failure, you would only be burning fuel from one side, so if you did need to proceed for a substantial amount of time on one engine, you would definitely be transferring fuel from the shutdown side to the operating side to keep it in balance.

The center tank would only be used for long flights, as structurally it's better to carry fuel in the wings, and I do not know if it was used on this flight. That having been said, whether the center tank was used or not, it's fairly safe to consider both engines as effectively running off the same fuel, and it certainly would've been sourced from the same place and no care would've been taken to prevent mixing.
 
  • Informative
  • Like
Likes DaveE and gmax137
  • #38
anorlunda said:
They said the second engine was overheating. Does anyone know what makes a jet engine overheat?
In addition to the oil starvation mentioned above (which I would honestly consider fairly unlikely), there are a number of other possible causes. A dirty or damaged compressor or turbine could cause this, as it would decrease efficiency and require more fuel to generate the same RPM and thrust. A bleed air leak would also lead to high EGTs, as it would reduce airflow to the combustor without reducing the power demand on the turbine. There could also be a problem with the fuel control unit, but on an aircraft this old, I'd probably suspect FOD, contamination, or wear on the compressor or a bleed leak before suspecting anything about the fuel control, since it's pretty simple on an engine like this (on a more modern engine, that could be a cause though).

EDIT: In addition, the fact that it only started overheating after the first engine failed supports the thought that it's related to compressor damage or wear (or turbine, but compressor seems more likely to me). Even with a worn, contaminated, or damaged compressor, the engine likely could perform OK at lower thrust settings or even for the brief high thrust at takeoff, but that would severely harm its ability to run continuously at higher thrust settings like would be required after the other engine failed. Granted, severe enough damage, contamination, or wear such that it couldn't even maintain level flight on a single engine is pretty extreme, but several accounts I'm reading about this airline and aircraft indicate that it was very near end of life, and the airline was suspected of poor maintenance practices, so that's my best guess right now.
 
Last edited:
  • #39
cjl said:
I think "often" is underselling it a bit. Has there ever, in the history of commercial jet aviation, been a dual independent failure? I certainly can't think of one. There are certainly cases where all engines failed on multiengine jets, but every case I can think of is common cause (flying into an ash cloud, flying into a goose cloud, flaws in the design of fuel filters combined with extremely cold fuel causing ice buildup and fuel starvation, running out of fuel due to improper unit conversion, etc). In addition, single engine failure isn't all that uncommon, so it's extremely understandable that the pilots would've been perfectly comfortable exiting gliding range (but still staying relatively near to the airport) while troubleshooting, executing checklists, evaluating the aircraft behavior, etc.

At least on the surface level, this doesn't appear to be something that would require a major change in procedure or aircraft design philosophy to fix, aside from perhaps just advising pilots that it is best practice to remain within gliding distance (if possible) while performing evaluations and troubleshooting after an engine failure.
There is the possibility that there was initially only a single engine problem, and pilot error in shutting down the good engine caused the subsequent failure. Shutting down and restarting a jet engine at low altitude isn't trivial, nor is it good for the engine. Yes, they ought to know not to make that mistake, but neither would they have been the first crew to do that.
 
  • #40
This source says one engine failure every 375,000 flight hours. If an aircraft flies for an average of one hour after a single engine failure (?) and we neglect four-engine aircraft we should expect completely unrelated double-engine failures every 375,000 single engine failures. With ~15,000 aircraft in the air and assuming they all have two engines we expect such an incident every 500 years. Things are not completely unrelated of course - things like the age and airline lead to a correlated risk.
 
  • Like
Likes russ_watters
  • #41
cjl said:
I think "often" is underselling it a bit.
Agreed.
cjl said:
In addition, single engine failure isn't all that uncommon, so it's extremely understandable that the pilots would've been perfectly comfortable exiting gliding range (but still staying relatively near to the airport) while troubleshooting, executing checklists, evaluating the aircraft behavior, etc.

At least on the surface level, this doesn't appear to be something that would require a major change in procedure or aircraft design philosophy to fix, aside from perhaps just advising pilots that it is best practice to remain within gliding distance (if possible) while performing evaluations and troubleshooting after an engine failure.
Isn't a single engine failure an instant/automatic emergency? I'd really like to know what the procedure/checklist says. I don't see what benefit you get from flying away from the airport vs orbiting off the end of the runway.

I'd also like to know if this was a true case of a rare dual engine failure with unrelated causes or if the pilots initially missed that the second engine was in the process of failing while they troubleshot the first engine. At least in some cases it is clear-cut whether you have an isolated single engine or dual engine failure.
mfb said:
If an aircraft flies for an average of one hour after a single engine failure (?) and we neglect four-engine aircraft we should expect completely unrelated double-engine failures every 375,000 single engine failures. With ~15,000 aircraft in the air and assuming they all have two engines we expect such an incident every 500 years.
Note that unlike the odds at a roulette table or of an individual radioactive atom decaying, those odds increase with time/age.
Things are not completely unrelated of course - things like the age and airline lead to a correlated risk.
Yes, what I was thinking was that after the first engine fails you are then forced to run the other engine at higher power/for longer, putting additional strain on it, further increasing the risk.
 
Last edited:
  • #42
russ_watters said:
I don't see what benefit you get from flying away from the airport vs orbiting off the end of the runway.
The perceived benefit could be to put the plane on autopilot to allow both pilots to focus on the first engine restart. That would be a violation of cockpit resource management protocol.

It seems to echo the case of Eastern flight 401. The aftermath of that crash spawned the idea of cockpit resource management.

https://en.wikipedia.org/wiki/Eastern_Air_Lines_Flight_401#Cause
The final NTSB report cited the cause of the crash as pilot error, specifically: "the failure of the flight crew to monitor the flight instruments during the final four minutes of flight, and to detect an unexpected descent soon enough to prevent impact with the ground. Preoccupation with a malfunction of the nose landing gear position indicating system distracted the crew's attention from the instruments and allowed the descent to go unnoticed.
 
  • #43
It is true that with one engine out, the odds of a second engine failure go way up - a factor of 1000 perhaps. However, it is also true that the vast majority of time (99.5%) you have a single engine failure, you have only a single engine failure. I'd be wary of changing the procedure to improve the outcome of the 1/200 case if it makes the 199/200 case potentially worse.
 
  • #44
And an interesting new development...

Air cargo company that ditched plane in ocean off Hawaii is grounded​


The Federal Aviation Administration said Friday that it will bar Rhoades Aviation of Honolulu from flying or doing maintenance inspections until it meets FAA regulations.

The agency did not detail Roades' alleged shortcomings. The company did not immediately respond to phone and email messages for comment.

The decision to ground the carrier, which operates as Transair, is separate from the investigation into the July 2 ditching of a Boeing 737, the FAA said. Two pilots were rescued by the Coast Guard after the nighttime crash.

The company had one plane still in operation this week, a Boeing 737-200 like the one that crashed.

The FAA said it began investigating Rhoades Aviation's maintenance and safety practices last fall and told the company about two weeks before the crash that it planned to revoke its authority to do maintenance inspections. The company did not appeal the FAA's decision within the 30 days as required if it wanted the case reconsidered, the FAA said.

1626878651830.png
 
  • #45
To me, the surprising thing comes at 1:50 of the VASA radio transcript. Prior to that, flight 810 said that they had to return to the airport. The controller (after some confusion) cleared them to immediately return and to land. But 810 said, "Rhodes 810, we're going to have to run some checklists if we could get delay vectors."

That suggests that they changed their minds about an ASAP return to the airport and instead do something else. While doing the something else, they flew out to sea, away from the airport. I suspect the something else was the engine restart procedure, but the radio transcript does not say that explicitly.

I have listened to many such transcripts from VASA Aviation, and to every recreation produced on Air Crash Investigations. The "usual" decision in such cases is to return to the airport ASAP.

There is no need to restart the failed engine in order to make a safe landing. IMO, their choice should have been to begin the landing checklist, not to request a delay to do something else.
 
  • Like
Likes russ_watters
  • #46
The only upside I can think of to their choice is if they were clawing for altitude then keeping the wings level helps. But that's a lose-lose proposition unless you can dump fuel to lighten the plane. Running checklists itself does not require flying away from the airport.

I did watch one of those VASA videos where a pilot orbited in an area abeam the runway, designated for fuel dumping.

I doubt they could have used autopilot on a compromised plane, but if so, autopilot can turn a plane.
 
Last edited:
  • #47
For fun, I downloaded the 737 "Quick Reference Handbook, which at 822 pages stretches the definition of "handbook". And probably quick.

The single engine out checklist begins on page 7.16 (148) and you need to get to Step 13 to reach "Plan to land at the nearest airport". Step 12 allows for an attempt at an engine restart. A successful restart (11 steps) does not require an immediate landing, although laws, regulations, and common sense might.

The one engine inoperative landing checklist is 4 pages long, not counting the direction to check a table on page 378.

Page 7.6 is the six page gem "Loss of Thrust on Both Engines". Interestingly, the checklist does not give an action for what to do if neither engine restarts.

How much time were they running checklists before turning to HNL? As far as I can tell from posted audio, a few seconds under two minutes,
 
  • Like
Likes russ_watters
  • #48
A big part of the pilot's responsibility is to decide which strategy and therefore, which checklist to use. Consider two cases.
  1. An engine failure at 30000 feet, when it will take 20 minutes to descend with or without engines.
  2. An engine failure during takeoff roll, or during final approach to landing, 10 seconds from touchdown.
Obviously, the engine restart checklist should be use in case 1, but not in case 2. But there will always be borderline cases where things are not obvious. That's when we most need a thoughtful and well trained pilot.
Vanadium 50 said:
How much time were they running checklists before turning to HNL? As far as I can tell from posted audio, a few seconds under two minutes,
Right; it was 87 seconds (see #19). But they started at a place close to the runway to which they could glide with no engines, to (87 seconds later) a place miles out to sea, and out of visual contact with the airport. IMO, that was the primary error that caused the crash. If they had circled close to the airport, they could have survived the 2nd engine failure. If they had landed immediately, they would have been on the ground before the 2nd engine failed.
 
  • Like
Likes russ_watters
  • #49
Multiple engine failures has been discussed before, see

https://www.physicsforums.com/threa...n-free-fall-from-12-496km.991918/post-6374219

That post attached a report that says:

A DOUBLE ENGINE FLAMEOUT DUE TO WATER INGESTION WHICH OCCURRED AS A
RESULT OF AN INFLIGHT ENCOUNTER WITH AN AREA OF VERY HEAVY RAIN AND
HAIL. A CONTRIBUTING CAUSE OF THE INCIDENT WAS THE INADEQUATE DESIGN OF
THE ENGINES AND THE FAA WATER INGESTION CERTIFICATION STANDARDS WHICH
DID NOT REFLECT THE WATERFALL RATES THAT CAN BE EXPECTED IN MODERATE
OR HIGHER INTENSITY THUNDERSTORMS.

"Water ingestion" -- That's kind of surprising.

EDIT - I'm not suggesting that has any relevance to the incident in this thread.
 
  • #50
I'm an outcomes guy, not a process guy. Clearly in this case it would have been better to have turned around. That doesn't mean that in general turning around is a better use of time than a restart checklist. We don't expect our pilots to be robots, but we don't expect them to be precognitive either: at the time of that message, they had only lost one engine.

Had the outcome been different - say a runway accident with 809 - because they turned back immediately after losing one engine, would we not criticize them for turning back too soon rather than attempting a restart? Would we not be saying "in the vast majority of cases, restart attempts are successful"?
 
  • Like
Likes russ_watters

Similar threads

Replies
1
Views
10K
Replies
65
Views
10K
Back
Top