Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Pop Mech article on PCL 3701

  • Thread starter Thread starter Rogue5
  • Start date Start date
  • Watchers Watchers 10

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web

Rogue5

Adult Swim junkie
Joined
Jul 16, 2002
Posts
882
http://www.popularmechanics.com/science/aviation/2156137.html

'We don't have any engines'

Two joyriding pilots took a jet to its 41,000-ft. ceiling--and paid for the stunt with their lives. PM investigates the crash of Flight 3701.
BY JIM GORMAN

Published in the January, 2006 issue.

For three and a half minutes on the night of Oct. 14, 2004, Capt. Jesse Rhodes and First Officer Peter Cesarz were on top of the world. The two Pinnacle Airlines pilots had pushed their twin-engine, 50-seat regional jet to its maximum altitude and were now proud members of the "410 club," an unofficial society of Pinnacle airmen who've attained 41,000 ft. in a Bombardier CRJ200.

Rhodes went to the galley to grab cold Pepsis to celebrate. He was barely settled back in the cockpit when the plane's radio crackled. "Are you a RJ [regional jet] 200?" inquired an air traffic controller in Olathe, Kan. "I've never seen you guys up at forty-one there."

"Yeah ... we don't have any passengers on board so we decided to have a little fun and come on up here," Rhodes replied.

The fun was short-lived. Moments later, both engines flamed out.
The fate of Flight 3701 is the subject of an intensive investigation by the National Transportation Safety Board (NTSB), which is expected to issue a final report on the accident in the next few months. Until then, neither Pinnacle Airlines, which operates connecting flights for Northwest Airlines, nor Bombardier and General Electric--the airplane and engine manufacturers--can comment on the cause of the accident. However, the pilots' taped cockpit conversations and preliminary hearings last June suggest a scenario involving poor judgment, insufficient training and the complications that can occur when a plane is pushed beyond its capabilities.

TO THE LIMIT
Rhodes, 31, and Cesarz, 23, were on what pilots call a deadhead, transferring an empty plane overnight from Little Rock, Ark., to Minneapolis so it could be ready for a morning flight. The Canadian-built CRJ200 is Pinnacle's workhorse, making short and midrange hops mostly in the Midwest. From wheels-up, it was clear that Rhodes and Cesarz intended to see what the CRJ200 could do.

Four seconds after takeoff at 9:21 pm, the two pilots did a "pitch up" maneuver that pinned them in their seats with 1.8 g's of force and momentarily triggered an alert from the airplane's stall warning system.

Minutes later, Rhodes and Cesarz again yanked back on the control column, rocketing the plane upward and generating over 2.3 g's of force before they eased off the flight controls. After briefly leveling off at 37,000 ft., the crew set the autopilot to climb at 500 ft. per minute--more than twice the fastest recommended rate--to the airplane's maximum altitude of 41,000 ft.

As the plane rose, it succumbed to the physics of high-altitude flight: Thin atmosphere offers less lift and robs the engine of air. Stuck in an aggressive climbing mode, Flight 3701's speed began to drop. To maintain the rate of climb, the autopilot angled the nose of the aircraft up, slowing it further. By the time the aircraft reached 41,000 ft. and leveled off, it was flying slowly, at 150 knots indicated airspeed, and was perilously close to losing aerodynamic lift--or stalling.

"This thing ain't gonna [expletive] hold altitude," Cesarz said.

"It can't man," Rhodes replied. "We [cruised/greased] up here but it won't stay."

The combination of high altitude and low speed once again triggered the Bombardier's stall warning system. First, "stick shakers" rattled the control columns and disengaged the autopilot to alert the crew of an imminent stall. When the crew didn't lower the plane's nose to gain speed, "stick pushers" forced the control columns forward. The flight data recorder shows that Rhodes and Cesarz overrode the stick pushers three times and forced the plane's nose back up. At 9:55 pm, as they pulled up for the last time, both engines flamed out.

"We don't have any engines," one of the pilots said.

FAILED EFFORTS
While the altimeter spun downward, the crew hurriedly reviewed their options for restarting the engines. At that altitude, there were six suitable airports within reach for a forced landing. Despite the serious nature of their predicament, the pilots did not notify air traffic control (ATC) of their situation or request emergency landing clearance.

First, they tried a "windmill restart" by diving to increase airspeed. The maneuver is intended to force air into the engine housing, spinning the rotors and creating enough compression for ignition. The procedure requires at least 300 knots of airspeed. But at 20,000 ft. and only 236 knots, the crew pulled up, and decided instead to try a second option: Drop to 13,000 ft. and attempt to relight the engines using the plane's auxiliary power unit (APU), which generates pneumatic pressure to spin the engine's core.

Rhodes and Cesarz tried at least four times to jumpstart the engines using the APU. On each attempt the engine cores recorded no rotation.

At 10:03 pm, the crew radioed ATC that they had a single engine failure. Five minutes later, at an altitude of 10,000 ft., and descending at 1500 ft. per minute, Rhodes and Cesarz were running out of options for restarting the engines. Finally, 12 minutes after the twin flameout, they revealed to ATC that they had a double engine failure. The plane's landing choices were now limited to two airports.

With the runway lights of Jefferson City airport in sight, but altitude slipping away, Rhodes and Cesarz realized they were in big trouble.

"Dude, we're not going to make this," Rhodes said. "We're gonna hit houses, dude."

They crashed 2-1/2 miles shy of the runway--behind a row of houses. On impact, the plane split apart, flipped over and caught fire. Rhodes and Cesarz were killed. Miraculously, no one on the ground was injured.

THE INVESTIGATION
An area of contention during the NTSB hearings about Flight 3701 has been whether a condition called "core lock" contributed to the fatal crash. Under normal conditions, the rotating parts inside a General Electric CF34-3B1 turbofan engine slip by each other in a finely tuned choreography.

However, when an engine is shut down suddenly at high torque, high altitude, and it isn't restarted immediately, metal parts inside the engine begin to cool and contract at different rates. In rare cases, metal can contact metal and prevent the core from rotating freely--core lock.

The Air Line Pilots Association suggests that core lock, rather than pilot error, might have been the primary cause of the accident. But, a review of the flight data recorder makes clear that the pilots made a series of poor, and potentially fatal, decisions irrespective of whether the engines experienced core lock.

The Bombardier has a 41,000-ft. service ceiling. However, according to the climb profiles in the crew's flight manual, the maximum altitude for the 500-ft.-per-minute climb the pilots set was only 38,700 ft., based on the atmospheric conditions and the aircraft's weight that night.

By operating outside the airplane's performance envelope, Rhodes and Cesarz subjected the engines to tremendous stress. The flight data recorder shows that soon after the crew ignored the fourth stall warning, the core temperature of the right engine reached 2200 degrees--almost 600 degrees above redline.

When investigators pulled apart the right engine, they found that the ends of the high-pressure turbine blades had liquefied, resolidifying on the low-pressure blades behind them. This leads some industry experts to question if the right engine ever could have restarted.

Whether the left engine locked up is still being investigated. GE helped the NTSB disassemble Flight 3701's engines. Edward Orear, GE's former program manager for the CF34-3B1 engine, testified to the NTSB that neither engine showed evidence of core lock.

THE OBJECT LESSON
The data recorder shows that the pilots failed to follow proper procedures for restarting a flamed-out engine when they pulled out of their dive before reaching the necessary speed to spin the core. Whether the apparently undamaged left engine could have restarted if they had windmilled correctly may never be known. It's also unresolved why the left engine didn't restart when the pilots used the APU.

Since the crash, Pinnacle has set a ceiling of 37,000 ft. for all CRJ200 flights. It has also added detailed climb profiles to the pilots' quick reference guides. And the airline has modified its simulator training program, incorporating dual engine failure and stall recovery scenarios.

Although Flight 3701 ended tragically, it illustrates how many safety features protect commercial passengers. The crew misused the auto-pilot, took the plane outside its envelope and repeatedly overrode the safety system. As one pilot told PM: "It's an object lesson in how many things you have to get wrong in order to crash your plane."

Links referenced within this article

taped cockpit conversations

http://www.popularmechanics.com/specials/what_went_wrong/1958917.html

http://media.popularmechanics.com/documents/WWWrong106.pdf

Find this article at:
http://www.popularmechanics.com/science/aviation/2156137.html
 
Technical jargon

Dude, when you like, barbecue an engine up there, it gets like, so hot, dude, that it like, freaks out and stuff, and then it, like, totally, like, stops, dude.

Dude, have you ever snorted liquified turbine blades? Totally hot, like, such a rush!

Du-hu-hu-hude! I'm an airline pilot!
 
I wonder if there's a correlation between this and the "Gulfstream Academy"?
 
I hope once the final NTSB report comes out and it becomes official that FL410 didn't "cause" this accident, that the knee-jerk reaction at our company will be over and we can have 410 back for our CR7's. There is no good reason to limit them to 390. It's a totally different animal than the CRJ-200, and doesn't deserve to be lumped together with it.
 
A disgrace, and a shame, and a very clear testimony to the quality of many airline "professionals" these days.

"Just teach me what I need to know to pass the test, dude, so that I can get into that shiny jet right away, dude. I'll pick up the rest on the job."
 
Ganja60Heavy said:
Dude, when you like, barbecue an engine up there, it gets like, so hot, dude, that it like, freaks out and stuff, and then it, like, totally, like, stops, dude.

Dude, have you ever snorted liquified turbine blades? Totally hot, like, such a rush!

Du-hu-hu-hude! I'm an airline pilot!


I'll be sure to talk sh*t about you when your dead too.
 
Sorry DoinTime . . . it's like if you drink a lot of alcohol and then go in your car and don't wear a seatbelt and then get in a single-car accident and don't take anybody else out when you do this . . . it sucks to be you but as they say, "they have fortunately eliminated themselves from the gene pool."
 
Sounds like Core Lock has as much to do with this accident as the fence off the end of a runway when an idiot takes off 20% over gross on a 9000' DA day! Good Work ALPA!
 
IP076 said:
Sounds like Core Lock has as much to do with this accident as the fence off the end of a runway when an idiot takes off 20% over gross on a 9000' DA day! Good Work ALPA!

Yeah, I can't believe ALPA acknlowledged these fools were actually members.
 
Who cares if you fly at 410 anyway? I don't know any pilots that think that makes you .... "cool" or whatever. Just makes you absorb more radiation from the sun. Unless you flew the U-2 or worked for NASA, you shouldn't be bragging about how high you flew anyway.
 
A couple things I think the PM missed on this article. I think that a lot of the blame needs to be attributed to the pilots, however I think that there are a few things that needed to be addressed with this incident.

First, I think that ALPA was right in addressing corelock. Until this incident, not a lot of regional pilots really understood the danger of corelock. There was a good reason that the Bombardier QRH states that in the case of a dual engine failure, the pilots must maintain 240 knots UNTIL they are sure that there is no chance of a relight, only at that point will you maintain max glide speed. In a long conversation I had with a Bombardier test pilot, he stated that during flight testing the 200 had a lot of difficulty getting the engines to relight. The 700, 705, and 900 did not seem to have the same issues with their power plants.

Secondly, I think this incident highlighted the need for training in high altitude aerodynamics at the regional level. With the rapid expansion and popularity of RJ's, many regionals were faced with accelerating training to try and fill seats and I think high altitude/high speed aerodynamics was a topic that was typically glossed over during ground/flight training.

Its easy to assume that the 700 does not have the same difficulty at high altitudes as the 200 because of the higher thrust-to-weight ratio. However, the 700 also has a history of stick shaker incidents at 410. I believe that both Mesa and Horizon have had some isolated incidents as well as Air Canada Jazz's incident stick shaker incident over Colorado Springs in the 705. In fact, when the 700 was first introduced, there was a rash of stick shakers at altitudes as low as 370 because operators were training their crews to use the same climb profiles that they had been using in the 200 and the airplanes were never able to accelerate once they got to altitude.

In closing, the Pinnacle crew was definitely at fault but I believe that in the final report we will see that there were a number of other factors that came to play in this incident.
 
Turtlesfly said:
Sorry DoinTime . . . it's like if you drink a lot of alcohol and then go in your car and don't wear a seatbelt and then get in a single-car accident and don't take anybody else out when you do this . . . it sucks to be you but as they say, "they have fortunately eliminated themselves from the gene pool."


I never said what they did was excusable. It is most certainly not.

These men paid the ultimate price for their mistakes and thankfully they didn't take anyone with them. While I cannot forgive them for their actions I have enough respect to allow them to rest in peace. Maybe when you grow up you can extend them this same courtesy.
 
Unbelievable what unprofessional and reckless behavior these two displayed. It's unfortunate because they had several opportunities to save themselves, but their immature and unprofessional judgment did them in. Makes me wonder how they would handle a similar emergency with passengers on board.
 
Hey starship...thanks for the good info
 
100LL... Again! said:
A disgrace, and a shame, and a very clear testimony to the quality of many airline "professionals" these days.

"Just teach me what I need to know to pass the test, dude, so that I can get into that shiny jet right away, dude. I'll pick up the rest on the job."

Agree 100%. This is what happens when children are put in charge of an airliner. They might have been 31 and 23 but their maturity levels were closer to 21 and 13. Just the kind of "professionals" I want flying my family and friends around in a jet, shiny or not.

Make all the excuses you want, object to disparaging their behavior even though they're dead or not, they were incompetent and stupid and it killed them, and luckily it didn't kill anyone innocent. Argue that. The CVR transcript says it all. While many accident chains contain links that are beyond the control of the flight crew, this isn't one of them.
 

Latest resources

Back
Top