37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 827605 |
Time | |
Date | 200903 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZOA.ARTCC |
State Reference | CA |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR Sunset |
Flight Plan | IFR |
Component | |
Aircraft Component | Electrical Wiring & Connectors |
Person 1 | |
Function | Captain Pilot Flying |
Experience | Flight Crew Last 90 Days 105 Flight Crew Total 8754 Flight Crew Type 25 |
Events | |
Anomaly | Aircraft Equipment Problem Critical Inflight Event / Encounter Unstabilized Approach |
Narrative:
Passing FL210 in the descent; a power supply interruption was experienced; manifested with ECAM messages and irregular procedure reference actions. Affected electrical component: AC bus 2 CRT displayed ECAM irregular procedures: 1) autoflight facility 2 fault. 2) fuel center tank pump 2 low pressure. Other systems interrupted; but no associated reference actions: FCU; dmc 1+3; sdcu; autoflight rudder trim 2; autoflight rudder travel limited 2; dc bus tie; navigation FM/GPS; ADF 1; mcdu 1+3; cids 2; elac 2; ADR2; sfcc 2; angle of attack sensor 2; fwc 1. Because of the cid's interruption (cabin intercommunication data system) the flight attendants reported all video monitors ceased/retracted; and all cabin lighting momentarily went out. All components/systems automatically reset or were addressed/restored with the 2 aforementioned ECAM procedures. A visual approach with ILS backup was conducted to runway 1L. On downwind; the first officer reported that the mcdu/FMGC had dumped the approach and would not reload; however; ILS information was tuned and available. Controller vectors on downwind and turn to final were very tight. At 500 ft; airspeed was 15-20 KTS fast. I decided that the safest course of action was to continue. (Knowing from the log history that maintenance work that was thought to have corrected the problem had found evidence of arcing and a burned connector.) landing was on-speed and in the TDZ.
Original NASA ASRS Text
Title: A320 flight crew experienced a power supply interruption due to an arcing and burned connector which resulted in multiple ECAM messages and irregular procedure reference actions.
Narrative: Passing FL210 in the descent; a power supply interruption was experienced; manifested with ECAM messages and irregular procedure reference actions. Affected electrical component: AC Bus 2 CRT displayed ECAM irregular procedures: 1) Autoflight FAC 2 Fault. 2) Fuel Center Tank Pump 2 Low Pressure. Other systems interrupted; but no associated reference actions: FCU; DMC 1+3; SDCU; Autoflight Rudder Trim 2; Autoflight Rudder Travel Limited 2; DC Bus Tie; Navigation FM/GPS; ADF 1; MCDU 1+3; CIDS 2; ELAC 2; ADR2; SFCC 2; Angle of Attack Sensor 2; FWC 1. Because of the CID's interruption (Cabin Intercommunication Data System) the Flight Attendants reported all video monitors ceased/retracted; and all cabin lighting momentarily went out. All components/systems automatically reset or were addressed/restored with the 2 aforementioned ECAM procedures. A visual approach with ILS backup was conducted to Runway 1L. On downwind; the First Officer reported that the MCDU/FMGC had dumped the approach and would not reload; however; ILS information was tuned and available. Controller vectors on downwind and turn to final were very tight. At 500 FT; airspeed was 15-20 KTS fast. I decided that the safest course of action was to continue. (Knowing from the log history that maintenance work that was thought to have corrected the problem had found evidence of arcing and a burned connector.) Landing was on-speed and in the TDZ.
Data retrieved from NASA's ASRS site as of April 2012 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.