37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1050939 |
Time | |
Date | 201211 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | MD-82 |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Component | |
Aircraft Component | Aileron |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
While leveled off at 23;000 ft with autopilot on; ATC gave us a turn direct. We noticed the autopilot disconnected and I (pilot flying) took over the controls noticing the ailerons were jammed. I could not move the ailerons while we were at wings level flight. I brought it to the captain's attention and; while I had the radios and the controls; I asked him to reference the QRH for aileron jam. He referenced the QRH and informed me that there was nothing available for any type of aileron malfunction. By applying 20 to 30 pounds of force; the captain was able to break the aileron jam; even though the ailerons were binding. We continued climbing to our final cruising altitude. Later; ATC gave us another turn (we had wings level and autopilot on) and the autopilot disconnected again. The ailerons were jammed again. I could not turn the ailerons. The captain took over the controls and broke the aileron jam. We; again; could move the ailerons but they were still binding. A third aileron jam happened later; again; when autopilot was on and was not able to turn on the routing for the next fix. This time; I (first officer); was able to break the jam by applying 20 to 30 pounds of force. Ailerons were still binding. I; twice; told the captain that we should declare an emergency with ATC. He decided not to do it since the ailerons were still operable. Dispatch was advised of the situation. During the descent; approach; and landing there were no aileron jams or bindings at speeds of less than 190 KTS. On the ground the ailerons worked fine. Dispatch/maintenance control sent a local mechanic for assistance; and a rescue flight was sent to our destination. After looking over the logbook once again after the flight; aircraft had three previous write ups in relation to aileron binding. Hours later; the aircraft was ferried back to a maintenance base by another crew for a maintenance check and a test flight (days later). Looking at the history of the aircraft in the logbook prior to the flight; the aircraft had 3 aileron write ups. We made the 4th report after this event. The aircraft should have been grounded the first time this occurred. The aircraft should have returned to revenue service only after passing a test-flight. The aircraft should have been released into revenue service not only by dispatch/maintenance control and flight operations. There are no abnormal procedures in our QRH for an aileron jam or any aileron malfunction. Those procedures need to be added to our QRH for standardization purposes. A declaration of emergency should be mandatory for this type of problem.
Original NASA ASRS Text
Title: An MD-82's ailerons jammed three times during flight so the aircraft was removed from service; ferried to a maintenance station and the crew later discovered three previous similar anomalies on the aircraft. A servo fault and lack of lubrication are believed to be the causes.
Narrative: While leveled off at 23;000 FT with autopilot ON; ATC gave us a turn direct. We noticed the autopilot disconnected and I (pilot flying) took over the controls noticing the ailerons were jammed. I could not move the ailerons while we were at wings level flight. I brought it to the Captain's attention and; while I had the radios and the controls; I asked him to reference the QRH for Aileron Jam. He referenced the QRH and informed me that there was nothing available for any type of aileron malfunction. By applying 20 to 30 LBS of force; the Captain was able to break the aileron jam; even though the ailerons were binding. We continued climbing to our final cruising altitude. Later; ATC gave us another turn (we had wings level and autopilot ON) and the autopilot disconnected again. The ailerons were jammed again. I could not turn the ailerons. The Captain took over the controls and broke the aileron jam. We; again; could move the ailerons but they were still binding. A third aileron jam happened later; again; when autopilot was ON and was not able to turn on the routing for the next fix. This time; I (First Officer); was able to break the jam by applying 20 to 30 LBS of force. Ailerons were still binding. I; twice; told the Captain that we should declare an emergency with ATC. He decided not to do it since the ailerons were still operable. Dispatch was advised of the situation. During the descent; approach; and landing there were no aileron jams or bindings at speeds of less than 190 KTS. On the ground the ailerons worked fine. Dispatch/Maintenance Control sent a Local Mechanic for assistance; and a rescue flight was sent to our destination. After looking over the logbook once again after the flight; aircraft had three previous write ups in relation to aileron binding. Hours later; the aircraft was ferried back to a maintenance base by another crew for a maintenance check and a test flight (days later). Looking at the history of the aircraft in the logbook prior to the flight; the aircraft had 3 aileron write ups. We made the 4th report after this event. The aircraft should have been grounded the first time this occurred. The aircraft should have returned to revenue service only after passing a test-flight. The aircraft should have been released into revenue service not only by Dispatch/Maintenance Control and Flight Operations. There are no abnormal procedures in our QRH for an aileron jam or any aileron malfunction. Those procedures need to be added to our QRH for standardization purposes. A declaration of emergency should be mandatory for this type of problem.
Data retrieved from NASA's ASRS site as of July 2013 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.