37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1214178 |
Time | |
Date | 201410 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Speed All Types Flight Deck / Cabin / Aircraft Event Other / Unknown Inflight Event / Encounter Loss Of Aircraft Control |
Narrative:
On our climb to altitude ATC requested best rate for conflicting traffic so I had the plane climbing at a high vertical speed. During that time my lunch plate spilled onto the floor and against my better judgment I leaned down to clean it up. At the same time the pilot monitoring was dealing with a paper jam in the printer so both our eyes were off the instruments for a brief period of time. The airspeed bled off quickly and the autopilot clicked off as the shaker alerted us to our slow speed; I did the recovery procedure with a change in pitch to 5-10 degrees down and max power and we descended 4000 feet to recover. We told ATC immediately we needed lower as we started down and right away we were cleared 4000 feet lower. There was no traffic conflict and while in hindsight I would have declared an emergency our hands were full with getting the plane to a safe airspeed and altitude again. After the rush of getting the airspeed back and since we were already cleared lower it didn't seem to make sense to declare an emergency after the fact; which is the only reason we didn't do it. ATC didn't seem concerned with our sudden descent and no phone number was given. I've flown this aircraft type for 13 years without an event like this ever occurring so it was eye opening to see how fast it happened. Obviously lack of attention to the instruments was the contributing factor and as PIC I was responsible and feel terrible about it. Looking ahead I will never allow anything to take my eyes off the instruments during s climb because this is a vulnerable phase of flight for this to occur. I do want to point out that I've done this exact recovery in sim the last two times I've been back for recurrent and I was grateful to have had that training because we did get the plane under control very quickly. Most importantly; I was glad to know ahead of time that you have to accept the altitude loss and get the angle of attack pitched down because that is what I did instead of trying to power out of it. The training definitely kept a bad situation from getting worse and I am very grateful for it. I would strongly recommend that this recovery procedure stay in the maneuvers syllabus for our check rides.
Original NASA ASRS Text
Title: CRJ700 flight crew reports being asked by ATC for their best rate to FL350; then being distracted by minor tasks that allow the aircraft to slow to 180 knots and sticker activation. A text book recovery is performed.
Narrative: On our climb to altitude ATC requested best rate for conflicting traffic so I had the plane climbing at a high vertical speed. During that time my lunch plate spilled onto the floor and against my better judgment I leaned down to clean it up. At the same time the pilot monitoring was dealing with a paper jam in the printer so both our eyes were off the instruments for a brief period of time. The airspeed bled off quickly and the autopilot clicked off as the shaker alerted us to our slow speed; I did the recovery procedure with a change in pitch to 5-10 degrees down and max power and we descended 4000 feet to recover. We told ATC immediately we needed lower as we started down and right away we were cleared 4000 feet lower. There was no traffic conflict and while in hindsight I would have declared an emergency our hands were full with getting the plane to a safe airspeed and altitude again. After the rush of getting the airspeed back and since we were already cleared lower it didn't seem to make sense to declare an emergency after the fact; which is the only reason we didn't do it. ATC didn't seem concerned with our sudden descent and no phone number was given. I've flown this aircraft type for 13 years without an event like this ever occurring so it was eye opening to see how fast it happened. Obviously lack of attention to the instruments was the contributing factor and as PIC I was responsible and feel terrible about it. Looking ahead I will never allow anything to take my eyes off the instruments during s climb because this is a vulnerable phase of flight for this to occur. I do want to point out that I've done this exact recovery in sim the last two times I've been back for recurrent and I was grateful to have had that training because we did get the plane under control very quickly. Most importantly; I was glad to know ahead of time that you have to accept the altitude loss and get the angle of attack pitched down because that is what I did instead of trying to power out of it. The training definitely kept a bad situation from getting worse and I am very grateful for it. I would strongly recommend that this recovery procedure stay in the maneuvers syllabus for our check rides.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.