37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 226229 |
Time | |
Date | 199211 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : dtw |
State Reference | MI |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Small Transport, Low Wing, 2 Turboprop Eng |
Flight Phase | climbout : takeoff other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : commercial pilot : atp pilot : flight engineer pilot : cfi pilot : instrument |
Experience | flight time last 90 days : 160 flight time total : 3125 flight time type : 525 |
ASRS Report | 226229 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | aircraft equipment problem : critical other anomaly |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : rejected takeoff |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | other |
Narrative:
We accomplished a normal preflight according to company procedures. Passenger loading, start-up and taxi out were all accomplished without incident. All procedures were completed with use of company checklist. On this leg, it was the first officer's turn to fly. On runway 21C, control of the aircraft was turned over to the first officer after the runway items checklist had been completed and a takeoff clearance received. The takeoff was initiated V1 speed obtained. Vr speed was then obtained. All of these speeds are verbally called out by the PNF. When I called vr, the first officer moved the control column aft to initiate rotation, no rotation occurred. The control column was pulled further aft and still no rotation was effected. At this point, I called for the first officer to abort the takeoff. The takeoff was aborted, the aircraft brought to taxi speed, and we taxied clear of the runway. We stopped the aircraft investigated all takeoff settings but could find nothing out of proper indication range. At this point we returned to the gate and deplaned. On my post-flight inspection I noted the horizontal stabilizer was near the top of its up travel. The cockpit trim indicator indicated the stabilizer trim was mid- range. This extreme up travel of the stabilizer would have created the downward pitch moment to prevent rotation. This discrepancy was noted in the maintenance log and the aircraft turned over to company maintenance for inspection and repair. Contributing factors: lack of system redundancy. Callback conversation with reporter revealed the following information: very cooperative reporter said this aircraft has a takeoff warning horn. The trim indicator is in the cockpit and is biased by the pitch trim computer. He is not sure how the stabilizer came to be full nose down but he said it was not a runaway stabilizer. There is a 'beeper' that sounds intermittently as the stabilizer is trimmed. He probably would have heard this if the stabilizer ran away. The trim indicator/pitch trim computer triggers the takeoff warning horn independently of the stabilizer itself.
Original NASA ASRS Text
Title: SMT TKOF ABORTED WHEN UNABLE TO RAISE THE NOSE FOR LIFTOFF. STABILIZER TRIM INDICATOR IN COCKPIT INDICATED NORMAL TRIM BUT THE STABILIZER ITSELF FOUND TO BE IN THE FULL NOSE DOWN POS.
Narrative: WE ACCOMPLISHED A NORMAL PREFLT ACCORDING TO COMPANY PROCS. PAX LOADING, START-UP AND TAXI OUT WERE ALL ACCOMPLISHED WITHOUT INCIDENT. ALL PROCS WERE COMPLETED WITH USE OF COMPANY CHKLIST. ON THIS LEG, IT WAS THE FO'S TURN TO FLY. ON RWY 21C, CTL OF THE ACFT WAS TURNED OVER TO THE FO AFTER THE RWY ITEMS CHKLIST HAD BEEN COMPLETED AND A TKOF CLRNC RECEIVED. THE TKOF WAS INITIATED V1 SPD OBTAINED. VR SPD WAS THEN OBTAINED. ALL OF THESE SPDS ARE VERBALLY CALLED OUT BY THE PNF. WHEN I CALLED VR, THE FO MOVED THE CTL COLUMN AFT TO INITIATE ROTATION, NO ROTATION OCCURRED. THE CTL COLUMN WAS PULLED FURTHER AFT AND STILL NO ROTATION WAS EFFECTED. AT THIS POINT, I CALLED FOR THE FO TO ABORT THE TKOF. THE TKOF WAS ABORTED, THE ACFT BROUGHT TO TAXI SPD, AND WE TAXIED CLR OF THE RWY. WE STOPPED THE ACFT INVESTIGATED ALL TKOF SETTINGS BUT COULD FIND NOTHING OUT OF PROPER INDICATION RANGE. AT THIS POINT WE RETURNED TO THE GATE AND DEPLANED. ON MY POST-FLT INSPECTION I NOTED THE HORIZ STABILIZER WAS NEAR THE TOP OF ITS UP TRAVEL. THE COCKPIT TRIM INDICATOR INDICATED THE STABILIZER TRIM WAS MID- RANGE. THIS EXTREME UP TRAVEL OF THE STABILIZER WOULD HAVE CREATED THE DOWNWARD PITCH MOMENT TO PREVENT ROTATION. THIS DISCREPANCY WAS NOTED IN THE MAINT LOG AND THE ACFT TURNED OVER TO COMPANY MAINT FOR INSPECTION AND REPAIR. CONTRIBUTING FACTORS: LACK OF SYS REDUNDANCY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: VERY COOPERATIVE RPTR SAID THIS ACFT HAS A TKOF WARNING HORN. THE TRIM INDICATOR IS IN THE COCKPIT AND IS BIASED BY THE PITCH TRIM COMPUTER. HE IS NOT SURE HOW THE STABILIZER CAME TO BE FULL NOSE DOWN BUT HE SAID IT WAS NOT A RUNAWAY STABILIZER. THERE IS A 'BEEPER' THAT SOUNDS INTERMITTENTLY AS THE STABILIZER IS TRIMMED. HE PROBABLY WOULD HAVE HEARD THIS IF THE STABILIZER RAN AWAY. THE TRIM INDICATOR/PITCH TRIM COMPUTER TRIGGERS THE TKOF WARNING HORN INDEPENDENTLY OF THE STABILIZER ITSELF.
Data retrieved from NASA's ASRS site as of July 2007 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.