Uncommanded roll during cruise, Airbus A , April 28, 1995

Similar documents
Pitch control problems, Boeing , March 27, 2001

Flight attendant fall off Boeing , May 4, 1997

Galley lift injury, Boeing , June 9, 1999

In-Flight Fire/Emergency Landing, Federal Express Flight 1406 Douglas DC-10-10, N68055, Newburgh, New York September 5, 1996

Fast level off produces broken leg, Boeing , June 2, 2002

FACTUAL REPORT AVIATION

In-flight maneuvering injury, Airbus A , June 15, 2001

This space for binding 04/24/1990. Occurrence Date: Accident. Occurrence Type: Off Airport/Airstrip. Model/Series. Air Medical Transport Flight:

Failure of retract actuator, Boeing , December 6, 1999

FACTUAL REPORT AVIATION

Landing gear strut door separation, L , May 15, 1997

Cracked main landing gear cylinder, Douglas DC-8-61, July 4, 1997

FACTUAL REPORT AVIATION

Turbulence injury, Boeing , November 1, 1995

FACTUAL REPORT AVIATION

Hard landing, McDonnell Douglas MD-88, July 27, 1993

Tailstrike on landing, Boeing , June 5, 2001

Turbulence injury, Boeing , G-BNLS, April 1, 2002

Uncontained engine failure, Boeing , N107BV, August 2, 1993

FACTUAL REPORT AVIATION

Injury to worker while opening door of pressurized airplane, Douglas DC F, March 6, 1998

Tailstrike on landing, Boeing APF, December 25, 1994

Turbulence injury, Bombardier DHC-8-102, September 27, 1998

Nose gear-up landing, Boeing C, February 22, 1996

Collision with tug, Boeing , January 6, 1998

FACTUAL REPORT AVIATION

FACTUAL REPORT AVIATION

Landing gear failure, Boeing , July

Bird ingestion and dual engine failure, Boeing 757, February 22, 1999

Partial runway excursion, Boeing , May 10, 1996

FACTUAL REPORT AVIATION

FACTUAL REPORT AVIATION

FACTUAL REPORT AVIATION

Stuck elevator, Airbus A320, November 24, 1996

Assault on flight attendant and self-evacuation, Boeing , May 20, 2000

Wheel separation, Boeing 727-2K5, N900PG, March 10, 1997

Turbulence injuries, Boeing , June 20, 1995

Ground collision with fuel truck, Douglas DC-9-30, September 2, 1998

FACTUAL REPORT AVIATION

Ground collision between a McDonnell Douglas DC-9-32 and tug, Dulles, January 20, 2002

FACTUAL REPORT AVIATION

Taxiway landing, Boeing , February 24, 2004

Smoke emergency and evacuation on ground, Airbus A300B4-605R, February 20, 1996

FACTUAL REPORT AVIATION. Location/Time. Aircraft Information Summary. Revenue Sightseeing Flight: No Narrative. Air Medical Transport Flight:

Wing walker injured by nosewheel, Lockheed L-1011, March 27, 1997

Uncontained engine failure, Boeing B, July 29, 1999

Headset operator injury, Boeing , August 19, 1994

FACTUAL REPORT AVIATION

FACTUAL REPORT AVIATION

Collision with boarding gate, Boeing R, Orlando, July 2, 2000

Contained engine failure, Douglas DC-9-51, February 9, 1998

Injury while closing cargo door, Boeing 727, January 13, 1999

Collision between Boeing and snow plow, January 8, 2005

FACTUAL REPORT AVIATION

FACTUAL REPORT AVIATION

Smoke evacuation, McDonnell Douglas MD-82, April 1, 2000

FACTUAL REPORT AVIATION

Uncommanded pitch-up, McDonnell Douglas MD-11, July 13, 1996

Engine fire, McDonnell Douglas DC-10-30, G-NIUK, May 11, 1997

Engine detector fire, Boeing , October 2, 2003

Tailpipe fire, McDonnell Douglas MD-88, December 26, 1998

Collision with de-icing truck, Airbus A319, October 10, 2005

Runway excursion, hydraulic failure, Boeing RS, September 24, 1997

Hard landing, Boeing 737-4Y0, April 13, 1995

Ground collision btween tug and McDonnell Douglas MD-80, December 5, 1996

Broken ankle on landing, McDonnell Douglas MD-88, September 3, 1993

TCAS maneuver injury, Boeing , July 31, 2000

Erroneous airspeed indications/stickshaker, Boeing , VH-NHX, February 28, 2006

Runway overrun, Boeing F, October 15, 2000

Ground collision, Douglas DC-9-31 and Airbus A340, Chicago O'Hare, December 13, 2000

Collision with wing walker, Boeing , September 23, 2001

Electrical problems, Boeing , November 11, 1999

Loss of fan cowl, Airbus A , July 13, 2004

Clogged fuel filter, Airbus A320, February 16, 1998

90 degree nosewheel rotation on landing, Airbus A320, February 16, 1999

FACTUAL REPORT AVIATION

Dual engine failure and loss of directional control, Douglas DC-9-32, December 19, 1995

Ground collision between an Airbus A319 and Boeing 757, JFK, January 19, 2003

FACTUAL REPORT AVIATION

Ground collision with tug, McDonnell Douglas MD-88, April 22, 2003

Runway overrun, McDonnell Douglas MD-83, 9Y-THQ, Miami, January 1, 2002

In-flight upset, Boeing , G-BDXL, February 27, 2000

Nosewheel stuck 90, Airbus A320, N536JB, September 21, 2005

Shimmy on landing, boeing 737-3TO, November 6, 1998

FACTUAL REPORT AVIATION

National Transportation Safety Board Aviation Accident Final Report

FACTUAL REPORT AVIATION

Tailpipe fire, Boeing , January 19, 1999

Wheel separation on takeoff, Boeing , April 7, 1995

Near-miss, British Airways Boeing , G-AWNM, and United Airlines DC-10, February 25, 1995, neaer Chicago

Landing gear failure, Boeing , July 9, 1997

FACTUAL REPORT AVIATION

FACTUAL REPORT AVIATION

Main landing gear failure on landing, Boeing , July 6, 1997

Ground collision between two Boeing 777s, October 7, 2003

In-flight flap separation, Boeing , March 27, 1997

CSD overheat resulting in engine shutdown, Boeing , June 17, 1996

Wheels-up landing, Douglas DC-8-71F, April 26, 2001

National Transportation Safety Board Aviation Accident Final Report

In-flight thrust reverser deployment, Boeing 717, February 19, 2001

Transcription:

Uncommanded roll during cruise, Airbus A32-2, April 28, 995 Micro-summary: This Airbus A32-2 experienced uncommanded rolls due to a faulty potentiometer in the captain's sidestick. Event Date: 995-4-28 at 2 CDT Investigative Body: (NTSB), USA Investigative Body's Web Site: http://www.ntsb.gov/ Cautions:. Accident reports can be and sometimes are revised. Be sure to consult the investigative agency for the latest version before basing anything significant on content (e.g., thesis, research, etc). 2. Readers are advised that each report is a glimpse of events at specific points in time. While broad themes permeate the causal events leading up to crashes, and we can learn from those, the specific regulatory and technological environments can and do change. Your company's flight operations manual is the final authority as to the safe operation of your aircraft! 3. Reports may or may not represent reality. Many many non-scientific factors go into an investigation, including the magnitude of the event, the experience of the investigator, the political climate, relationship with the regulatory authority, technological and recovery capabilities, etc. It is recommended that the reader review all reports analytically. Even a "bad" report can be a very useful launching point for learning. 4. Contact us before reproducing or redistributing a report from this anthology. Individual countries have very differing views on copyright! We can advise you on the steps to follow. Aircraft Accident Reports on DVD, Copyright 26 by Flight Simulation Systems, LLC All rights reserved. www.fss.aero

Aircraft Registration Number: N33NW Occurrence Date: Occurrence Type: 4/28/995 Incident Most Critical Injury: Investigated By: NTSB Location/Time Nearest City/Place MINNEAPOLIS Zip Code Local Time Time Zone MN 5545 2 CDT Airport Proximity: Off Airport/Airstrip Aircraft Information Summary Aircraft Manufacturer Airbus Industrie Distance From Landing Facility: Model/Series A32-2 Direction From Airport: Type of Aircraft Sightseeing Flight: No Air Medical Transport Flight: Narrative Brief narrative statement of facts, conditions and circumstances pertinent to the accident/incident: History of Flight No On April 27, 995, at 245 central daylight time (cdt), an Airbus A32-2, N33NW, operated as Northwest Airlines Flight 42, from Detroit, Michigan, to Baltimore, Maryland, experienced an uncommanded roll during cruise flight at an altitude of 33, feet mean sea level (msl). Neither the crew nor the passengers were injured. The airplane was not damaged. The 4 CFR Part 2 flight continued on to land at the Baltimore-Washington International Airport (BWI), Baltimore, Maryland, without further incident. The flight had departed Minneapolis, Minnesota, at 27 cdt. The Captain's write-up of the events which occurred on Flight 42 stated "See earlier ASR on same aircraft same day. DCA-DTW nothing happened. DTW-BWI F/CTL ELAC fault. There might be a connection. Prior to ELAC mess there was a roll right to left but to a lesser degree." Upon landing at BWI, the # Elevator Aileron Computer (ELAC) was removed and replaced. On the following day, April 28, 995, the airplane was flown to the Minneapolis-St. Paul International Airport (MSP) without incident. The Digital Flight Data Recorder (DFDR) was removed and replaced when the airplane landed in MSP. Later that same day, at 55 cdt, the same airplane, N33NW, operated as Northwest Airlines Flight 5, once again experienced an uncommanded roll during climb to cruise following takeoff from MSP. No injuries were reported by either the crew or passengers and the airplane was not damaged. The flight had departed Minneapolis at 45 cdt, with a destination of Orange County, California. The Captain's report of the events which occurred on Flight 5 stated, "On climb at 25, aircraft rolled right, ELAC # fault followed (655 GMT) reset ELAC # operation normal. (658 GMT) Aircraft rolled right. CFDS indicated ELAC #2 problem." The flight crew leveled the airplane at 3, feet msl, slowed the airspeed to 25 KIAS, disconnected the autopilot and returned to MSP for an uneventful landing. Upon landing the DFDR, both sidestick transducer units (SSTU) and both ELACs were removed and replaced. Flight Recorders Both DFDRs were sent to the NTSB Flight Data Recorder Laboratory, Washington, D.C. for analysis. A review of the data for Flight 42 revealed, "... climb to cruise altitude (33, feet) were uneventful. Approximately 25 minutes into the flight, an ELAC (roll) fault was set and an uncommanded roll of -3.87 degrees was recorded. During the 69 seconds prior to the ELAC fault a series of roll oscillations of up to 2.8 degrees were also recorded. The ELAC fault was cleared 62 seconds later and the autopilot remained on. A second ELAC fault was recorded 5 seconds after the first ELAC fault.... The altitude values indicated the start of descent at approximately the - Page

Narrative (Continued) same time as the second ELAC fault; the autopilot remained engaged. The ELAC fault remained set for the remainder of the flight. The autopilot was disengaged and the st officers side stick became active at approximately,2 feet...." A review of the data from Flight 5 revealed, "An uncommanded roll accompanied by an ELAC No. (roll) fault was recorded approximately minutes into the flight at an altitude of 23, feet and an indicated airspeed of 35 knots. The airplane departed wings level flight rolling to the left -4.9 degrees in.66 seconds and rolled back to -.8 degrees in the following second. The airplane returned to wings level in the following 2.5 seconds. The side stick controllers remained inactive, and autopilot No. 2 remained engaged during this period. The ELAC fault remained set for 48 seconds. At an altitude of 27, feet the autopilot No. 2 was disengaged. The flight reached an altitude of 3, feet before returning to MSP. While at 3, feet autopilot No. was engaged and remained on until the flight descended through 5, feet." Tests and Research The A32 flight control system features fly-by-wire technology, meaning that inputs from the flightcrew are transmitted electronically rather than mechanically to the flight control surface actuators. The airplane is equipped with two sidesticks in the cockpit, which replace the conventional control columns. Sidestick movements are mechanically transferred to the SSTU which contains 2 potentiometers. Each potentiometer is linked to one channel in the flight control computers, either the ELAC or Spoiler/Elevator Computer (SEC). Testing of the ELACs was performed at Aerospatiale facilities in France under the direction of the French Bureau Enquetes- Accidents (BEA). No anomalies were found during the testing. Bench testing and inspection of the SSTUs was performed at the manufacturer, SARMA, in France, also under the direction of the BEA. Testing of the co-pilots SSTU failed to reveal any anomalies. Testing of the captains SSTU revealed voltage spikes when the sidestick was near the neutral position. The voltage spikes were generated by a physical intermittent loss of contact between the wiper and the track inside the potentiometer which corresponded to the ELAC-. This loss of contact resulted in the ELAC- input being disrupted. Teardown of the potentiometer revealed a "micro-cut" or groove in the track at the point where the wiper arm rests when the sidestick is in a neutral position. Examination of the groove revealed a built-up of lubricating grease that normally coats the track. The detected voltage spike had an amplitude corresponding to full sidestick deflection for a period of one second. This voltage spike amplitude resulted in the ELAC sensing a command for an airplane roll. Internal diagnostics in the ELAC then determine that the spike is not a valid signal and the roll command ceases. A spike of a higher amplitude would have triggered the range monitoring function within the ELAC and the spike would have been ignored. A spike of a longer duration would have triggered an ELAC- fault, and the system would have automatically switched to the ELAC-2. Prior to this incident, Airbus developed two modifications addressing similar uncommanded roll events which have occurred since 99. Service Bulletin A32-27-84, dated June, 995, adds a resistor to the sidestick potentiometer to reduce the magnitude of the voltage spike. Service Bulletin A32-27-82, dated April, 995, addresses a software modification which will allow the ELAC to identify a voltage spike as an invalid command more rapidly, therefore, minimizing the commanded roll. Neither of these Service Bulletins had been incorporated on N33NW at the time of the incident. - Page a

Landing Facility/Approach Information Airport Name Airport ID: Airport Elevation Runway Used Runway Length Runway Width Ft. MSL Runway Surface Type: Runway Surface Condition: Type Instrument Approach: VFR Approach/Landing: Aircraft Information Aircraft Manufacturer Airbus Industrie Model/Series A32-2 Serial Number 38 Airworthiness Certificate(s): Transport Landing Gear Type: Retractable - Tricycle Homebuilt Aircraft? No Number of Seats: 56 Engine Type: Turbo Fan - Aircraft Inspection Information Type of Last Inspection Continuous Airworthiness - Emergency Locator Transmitter (ELT) Information Certified Max Gross Wt. Engine Manufacturer: GE Date of Last Inspection 45 LBS Number of Engines: 2 Model/Series: Rated Power: CFM-56-5 235 LBS Time Since Last Inspection Hours Airframe Total Time Hours ELT Installed? Yes ELT Operated? No ELT Aided in Locating Accident Site? Owner/Operator Information Registered Aircraft Owner NORTHWEST AIRLINES, INC Operator of Aircraft Same as Reg'd Aircraft Owner Street Address 5 NORTHWEST DRIVE City ST. PAUL Street Address Same as Reg'd Aircraft Owner City MN Zip Code 55 Zip Code Operator Does Business As: NORTHWEST AIRLINES - Type of U.S. Certificate(s) Held: Air Carrier Operating Certificate(s): Flag Carrier/Domestic Operator Designator Code: NWAA Operating Certificate: Operator Certificate: Regulation Flight Conducted Under: Part 2: Air Carrier Type of Flight Operation Conducted: Scheduled; Domestic; Passenger Only - Page 2

First Pilot Information Name On File City On File Date of Birth Age On File Sex: M Seat Occupied: Left Principal Profession: Civilian Pilot Certificate Number: On File Certificate(s): Airline Transport Rating(s): Multi-engine Land Rotorcraft/Glider/LTA: Instrument Rating(s): Instructor Rating(s): Type Rating/Endorsement for Accident/Incident Aircraft? Yes Current Biennial Flight Review? Medical Cert.: Class Medical Cert. Status: Unknown Date of Last Medical Exam: 3/995 - Flight Time Matrix All A/C This Make and Model Single Engine Mult-Engine Night Actual Instrument Simulated Rotorcraft Glider Lighter Than Air Total Time 4 953 Pilot In Command(PIC) Instructor Last 9 Days Last 3 Days Last 24 Hours Seatbelt Used? Yes Shoulder Harness Used? No Toxicology Performed? No Second Pilot? Yes Flight Plan/Itinerary Type of Flight Plan Filed: IFR Departure Point Airport Identifier Departure Time Time Zone Same as Accident/Incident Location MSP 45 CDT Destination Airport Identifier ORANGE COUNTY CA SNA Type of Clearance: Type of Airspace: IFR Class A Weather Information Source of Briefing: Company Method of Briefing: - Page 3

Weather Information WOF ID Observation Time Time Zone WOF Elevation WOF Distance From Accident Site Direction From Accident Site Ft. MSL NM Deg. Mag. Sky/Lowest Cloud Condition: Clear Ft. AGL Condition of Light: Day Lowest Ceiling: Ft. AGL Visibility: 2 SM Altimeter: 3. "Hg Temperature: 4 C Dew Point: C Wind Direction: 8 Density Altitude: Ft. Wind Speed: 5 Gusts: Weather Condtions at Accident Site: Visual Conditions Visibility (RVR): Ft. Visibility (RVV) SM Intensity of Precipitation: Unknown Restrictions to Visibility: Type of Precipitation: Accident Information Aircraft Damage: Aircraft Fire: Aircraft Explosion Classification: U.S. Registered/U.S. Soil - Injury Summary Matrix First Pilot Second Pilot Student Pilot Flight Instructor Check Pilot Flight Engineer Cabin Attendants Other Crew Fatal Serious Minor TOTAL 4 4 Passengers 84 84 - TOTAL ABOARD - 9 9 Other Ground - GRAND TOTAL - 9 9 - Page 4

Administrative Information Investigator-In-Charge (IIC) PAMELA S. SULLIVAN Additional Persons Participating in This Accident/Incident Investigation: ROBERT HENLEY FAA, 8 INDEPENDENCE AVE. S.W WASHINGTON, DC 259 HELENE LANDURE BEA, AEROPORT DU BOURGET LE BOURGET, OF 9335 MARTEN BOSMAN AIRBUS INDUSTRIE TOULOUSE, OF JOHN DELISI NTSB, 49 L'ENFANT PLAZA S.W. WASHINGTON, DC 2594 - Page 5