37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 585146 |
Time | |
Date | 200306 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
State Reference | OH |
Altitude | msl bound lower : 31000 msl bound upper : 31700 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zob.artcc |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | cruise : enroute altitude change cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 13000 flight time type : 500 |
ASRS Report | 585146 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | aircraft equipment problem : critical altitude deviation : overshoot non adherence : published procedure non adherence : company policies non adherence : far other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : autoplt disconnect wailer other flight crewa other flight crewb |
Resolutory Action | flight crew : returned to assigned altitude other |
Consequence | other |
Supplementary | |
Problem Areas | Maintenance Human Performance Aircraft Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On climb out, captain (PF) initially had trouble engaging autoplt #1. Autoplt #2 was engaged and used for a short period of time, followed by #1 autoplt finally being engaged and used. At FL310, aircraft began to level off, and the FMA pitch window read 'altitude acquired.' I told captain I'd be off frequency to call company on #2 radio to check our 'out' and 'off' times. ACARS clock was incorrect. The autoplt aural warning (disconnected) got my attention. I looked up, and aircraft was climbing through FL315, and captain had both hands on control yoke pushing forward. He got the climb stopped at about FL317, and descended back to FL310. ATC said nothing as we tried to figure out what just happened. Earlier in the flight, when the captain had trouble engaging autoplt #1, there were several times the stabilizer out of trim light came on. Also, after the incident, and back to level flight, the captain re-engaged autoplt, and it would not hold altitude. That was about the time I told the captain that I didn't think the autoplt trim was working, as the trim wheel was not moving when the autoplt was engaged. We found a circuit breaker tripped. After several mins of discussion, we agreed it would be ok to reset circuit breaker and check the autoplt again. We did, and autoplt operated properly. During landing checklist 'recall-checked' master caution and speed trim fail lights illuminated (single channel failure). Captain called maintenance upon arrival at gate. The captain made a comment to me when we picked up the plane at approximately XA30 local that it was an originating flight (unusual), and had had maintenance on stabilizer. I don't know what type of work and if the circuit breaker had been pulled by maintenance. We both arrived at XA25 for XA50 departure (unscheduled aircraft swap) and could have missed the circuit breaker if it were already tripped. Whatever the reason the circuit breaker tripped, the autoplt was unable to level off and maintain altitude without the trim operating. I don't know if maintenance and/or speed trim 'fail' were in any way related to or cause of altitude deviation/autoplt failure.
Original NASA ASRS Text
Title: B737-300 CREW FORCED AN AUTOPLT TO ENGAGE. THEY HAD AN ALTDEV WHEN IT DISCONNECTED, AND THE ACFT WAS NOT IN TRIM.
Narrative: ON CLBOUT, CAPT (PF) INITIALLY HAD TROUBLE ENGAGING AUTOPLT #1. AUTOPLT #2 WAS ENGAGED AND USED FOR A SHORT PERIOD OF TIME, FOLLOWED BY #1 AUTOPLT FINALLY BEING ENGAGED AND USED. AT FL310, ACFT BEGAN TO LEVEL OFF, AND THE FMA PITCH WINDOW READ 'ALT ACQUIRED.' I TOLD CAPT I'D BE OFF FREQ TO CALL COMPANY ON #2 RADIO TO CHK OUR 'OUT' AND 'OFF' TIMES. ACARS CLOCK WAS INCORRECT. THE AUTOPLT AURAL WARNING (DISCONNECTED) GOT MY ATTN. I LOOKED UP, AND ACFT WAS CLBING THROUGH FL315, AND CAPT HAD BOTH HANDS ON CTL YOKE PUSHING FORWARD. HE GOT THE CLB STOPPED AT ABOUT FL317, AND DSNDED BACK TO FL310. ATC SAID NOTHING AS WE TRIED TO FIGURE OUT WHAT JUST HAPPENED. EARLIER IN THE FLT, WHEN THE CAPT HAD TROUBLE ENGAGING AUTOPLT #1, THERE WERE SEVERAL TIMES THE STABILIZER OUT OF TRIM LIGHT CAME ON. ALSO, AFTER THE INCIDENT, AND BACK TO LEVEL FLT, THE CAPT RE-ENGAGED AUTOPLT, AND IT WOULD NOT HOLD ALT. THAT WAS ABOUT THE TIME I TOLD THE CAPT THAT I DIDN'T THINK THE AUTOPLT TRIM WAS WORKING, AS THE TRIM WHEEL WAS NOT MOVING WHEN THE AUTOPLT WAS ENGAGED. WE FOUND A CIRCUIT BREAKER TRIPPED. AFTER SEVERAL MINS OF DISCUSSION, WE AGREED IT WOULD BE OK TO RESET CIRCUIT BREAKER AND CHK THE AUTOPLT AGAIN. WE DID, AND AUTOPLT OPERATED PROPERLY. DURING LNDG CHKLIST 'RECALL-CHKED' MASTER CAUTION AND SPD TRIM FAIL LIGHTS ILLUMINATED (SINGLE CHANNEL FAILURE). CAPT CALLED MAINT UPON ARR AT GATE. THE CAPT MADE A COMMENT TO ME WHEN WE PICKED UP THE PLANE AT APPROX XA30 LCL THAT IT WAS AN ORIGINATING FLT (UNUSUAL), AND HAD HAD MAINT ON STABILIZER. I DON'T KNOW WHAT TYPE OF WORK AND IF THE CIRCUIT BREAKER HAD BEEN PULLED BY MAINT. WE BOTH ARRIVED AT XA25 FOR XA50 DEP (UNSCHEDULED ACFT SWAP) AND COULD HAVE MISSED THE CIRCUIT BREAKER IF IT WERE ALREADY TRIPPED. WHATEVER THE REASON THE CIRCUIT BREAKER TRIPPED, THE AUTOPLT WAS UNABLE TO LEVEL OFF AND MAINTAIN ALT WITHOUT THE TRIM OPERATING. I DON'T KNOW IF MAINT AND/OR SPD TRIM 'FAIL' WERE IN ANY WAY RELATED TO OR CAUSE OF ALTDEV/AUTOPLT FAILURE.
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.