Usually after any kind of incident on an airliner, reporters interview distraught passengers who are only all too willing to relay the terrible circumstances that existed on the doomed jet. These sort of interviews make for great television, as our brains instinctively fill in all the missing bits of drama that we know must have occurred. After all, we’ve seen this script played out for years in aviation disaster movies.
The engine failure, aborted takeoff, and fire which occurred on a British Airways 777-200 in Las Vegas last month, however, was the real deal, and serves as every pilot’s nightmare. If Sully’s river landing was the miracle on the Hudson, this should be called the Vegas miracle, because those people may not know how truly close they came to being incinerated onboard the aircraft. Of the 157 passengers and 13 crew aboard, there were only 13 minor injuries, which is a borderline miracle.
After being incredibly unlucky enough to experience an uncontained engine failure, the odds of which happening are vanishingly small, everyone on the airplane saw the flip-side of the lucky coin in that the incident happened early in the takeoff and that the fire department was very quick to respond. Reports show that the flames were extinguished a mere four minutes after the aircraft first reported trouble, which proves to be a remarkable feat for any airport fire department.
Kudos of course have to be given to both the pilots and cabin crews who no doubt had a large part in determining the positive outcome of this potential disaster. Much opprobrium has been ladled out, however, to some of the passengers who grabbed their luggage before exiting the evacuation slides. I’m willing to give a small pass to those folks who might have grabbed their under seat items such as purses, but not so much to those who took time to open the overhead bins to grab rollaboards. Their actions might have prevented someone behind them from getting out at all.
The NTSB (National Transportation Safety Board) is reporting that there were several breaches of the engine casing, and that several parts of the high-pressure compressor spool were found on the runway. What this means is that the engine threw itself apart, most likely due to some sort of flaw or failure in a compressor blade or the spool that holds them.
This failure will likely be a high interest item as failures of this sort are not supposed to happen under any circumstances. These engines are constructed of high strength steel and titanium. Other than spinning on their bearings, the compressor parts are essentially non-moving parts unlike, say, the pistons in your car. Jet turbines are the most reliable of all engine designs, and I wouldn’t be surprised if this failure is tied back to an undetected crack or casting flaw.
When you look into the mouth of a jet engine, you are seeing the fan blades. Behind the fan blades are multiple sets of hundreds or more blades, each subsequently set together making up the compressor section. The compressor feeds very high temperature and high-pressure air into the combustion chamber where it is combined with fuel and ignites. Hot exhaust gases then travel over multiple sets of turbine blades which are connected to a shaft which turns the compressor and fan. It is the rotation of the fan which produces most of the thrust.
While this serves as a simple explanation of what happens normally, engines are designed so that should a failure of any component in the core of the engine fail, the casing of the engine is designed to contain the flying parts. In fact, during engine certification, explosives are attached to fan blades and detonated while running at full power to demonstrate this capability.
Because there were breaches of the engine casing, this failure is considered “uncontained.” The dangers of uncontained failures are manifest including parts being flung into the cabin, other engines, or the wing where the fuel is stored. In 1996, several passengers were killed by parts thrown from a catastrophic engine failure on an MD-88 during takeoff. That aircraft had the engines attached to the fuselage.
The most famous uncontained engine failure was that of United Flight 232, a DC-10 bound from Denver to Chicago in July of 1989. While at cruising altitude, the tail-mounted engine suffered a failure in the number one fan spool due to metallurgical fatigue. Thrown parts severed the lines in all three of the aircraft’s hydraulic systems rendering all of the jet’s flight controls useless. Manipulation of the throttles on the two remaining engines allowed the pilots to make a controlled crash in Sioux City which minimized casualties.
Should We Evacuate?
Reports from the incident indicate that the aircraft had barely rolled 1000ft before the engine failed and the pilots rejected their takeoff. This means that the abort was a relatively slow speed one. Having the engine fail so early in the takeoff was fortuitous. Had it happened at a speed closer to V1 or decision speed, it would have been more difficult to stop the airplane, and the pilots would not have had the use of the reverse thrust mechanism on the failed engine. Having the engine fail right after getting airborne might have been the worst case scenario.
Rejecting a takeoff, the terminology used when stopping before being committed to flying, is not in itself a particularly difficult maneuver, and is practiced routinely in the simulator by all airline pilots. Automatic brake systems help by applying full braking when the throttles are closed. Likewise, having an engine fail directly after lifting off, known affectionately by pilots as a “V1 cut,” is also practiced often in the simulator.
Once stopped, one of the more vexing decisions pilots can face is determining whether or not to evacuate their aircraft. It really isn’t as clear cut as it may seem. Calling for an evacuation will nearly always result in at least some minor injuries while the potential always exists for more serious ones. Passengers will tend to run in all directions and are at danger of being hit by responding emergency vehicles during a full blown evacuation.
There are many situations where keeping passengers on the aircraft might be the safest course of action. After any rejected takeoff, and especially after a high speed one, there may be some smoke from the tires and brakes. This doesn’t mean that a fire is im minent. If emergency response vehicles are already at the aircraft to monitor the situation, an evacuation may not be the wisest choice.
Flight attendants, who will have the best information concerning smoke and fire in the cabin, are empowered to initiate an evacuation on their own. That may have been what happened in this instance. Passengers interviewed afterwards reported a loud bang followed by the aircraft slowing and smoke entering the cabin.
The most dangerous type of evacuation is the self or passenger initiated one as happened recently on an Allegiant flight after someone thought they saw a fuel spill. The danger here is the contagion of panic to the rest of the airplane. This scenario has a great likelihood for injuries.
Will it Fly Again?
Personally, I’d bet against it. Heat strong enough to melt plexiglass windows and burn through aluminum may have compromised the structure of the aircraft to where repair is not cost effective. This aircraft was delivered in 1999, and while not ready for retirement at 16 years of age, was not new.
There were also some breathless reports by the crack aviation teams on network news that the fire suppression system was used but did not work. Those systems consist of a bottle or two of Halon and are designed to extinguish a flame in the accessory drive compartment. As the Halon is supposed to work by denying oxygen to fire in the enclosed spaces of the engine, it clearly wasn’t designed to put out a fuel-fed fire engulfing the engine. Fuel lines may have been severed by the engine failure as well which would have caused further issues.
Having an engine come apart in as dramatic a fashion as this is a truly rare event. Thankfully, professional responses by the crew and first responders kept it from becoming a real disaster.
About the guest author…
I am currently a captain flying a Boeing 737 for a major American airline. I’ve been flying since joining the Air Force in the early 1980s and retired from the service in 2003, spending nine years on active duty and eleven in the AF Reserve. I flew many aircraft for the military include the T-37 primary trainer, the KC-135 tanker and the C-5 cargo aircraft. I’ve been based in Texas, California, Arizona and Okinawa, Japan.
I have a degree in electrical engineering from Bucknell University and was commissioned into the Air Force through the AF Officer Training School, Medina Annex, Lackland AFB, in San Antonio, Tx.
I’ve been employed with my current company since the late 1980s flying various Boeing aircraft and have been a captain for over 10 years.
This post was written by Rob Graves. You can view his site here.
Want to join the team full time? Look for more information at the very bottom of the website.
Latest posts by Guest Author (see all)
- “Superb Owl” Photoshop of MSP Tram Raises Eyebrows, Awareness - January 31, 2018
- Trip Report: Comparing the Airbus A321s of America’s Ultra Low-Cost Carriers - December 3, 2017
- A First-Hand Perspective: Onboard KLM’s Final Fokker 70 Flight from London to Amsterdam - November 2, 2017