37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1339691 |
Time | |
Date | 201603 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZZ.Airport |
State Reference | FO |
Environment | |
Flight Conditions | Mixed |
Light | Night |
Aircraft 1 | |
Make Model Name | MD-11 |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Component | |
Aircraft Component | Electrical Distribution Busbar |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 160 Flight Crew Total 22300 Flight Crew Type 4506 |
Person 2 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 150 Flight Crew Total 9900 Flight Crew Type 2200 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
On initial descent; we got a level 1 bus right emergency dc off alert which caused auto pilot (ap) 2 and FD2 to fail. Captain as pilot monitoring selected ap 1 and directed first officer (first officer) to FD1 to regain automation on the right side of the cockpit. First officer continued as pilot flying. Captain retained radio because right acp failed.a review of the engine and alert display (ead) presented the following: L1 bus right emergency dc off; L2 FCC 2B data fault L1 sel lsas lob off; L1 sel yaw upr a off. First actions were to satisfy ead prompts at lsas lob and yaw upr a. After this; we accomplished aom procedures for FCC 2B data fault and bus right emergency dc off. At the conclusion of those checklists; we had time to brief the arrival and discussed the likelihood of a configuration problem since we had flap segment indicators on the pfd; two of which were 'X' presenting no data.we decided to configure early several miles out on base. At slats extend; we got an immediate L2 slat disag alert and entered a checklist for that. The aom procedure led us to an abnormal configuration for landing (28/ret) and a moderate speed increase on final. We informed approach control. Our approach and landing were conducted at flaps 28; slats retracted; GPWS flap override on. Rollout to parking was uneventful.
Original NASA ASRS Text
Title: Aircrew experienced an electrical failure resulting in multiple systems degradation. Successfully landed in an emergency status.
Narrative: On initial descent; we got a Level 1 BUS R EMER DC OFF alert which caused Auto Pilot (AP) 2 and FD2 to fail. Captain as Pilot Monitoring selected AP 1 and directed First Officer (FO) to FD1 to regain automation on the right side of the cockpit. FO continued as Pilot Flying. Captain retained radio because right ACP failed.A review of the Engine and Alert Display (EAD) presented the following: L1 BUS R EMER DC OFF; L2 FCC 2B DATA FAULT L1 SEL LSAS LOB OFF; L1 SEL YAW UPR A OFF. First actions were to satisfy EAD prompts at LSAS LOB and YAW UPR A. After this; we accomplished AOM procedures for FCC 2B DATA FAULT and BUS R EMER DC OFF. At the conclusion of those checklists; we had time to brief the arrival and discussed the likelihood of a configuration problem since we had flap segment indicators on the PFD; two of which were 'X' presenting no data.We decided to configure early several miles out on base. At slats extend; we got an immediate L2 SLAT DISAG alert and entered a checklist for that. The AOM procedure led us to an abnormal configuration for landing (28/RET) and a moderate speed increase on final. We informed approach control. Our approach and landing were conducted at flaps 28; slats retracted; GPWS flap override on. Rollout to parking was uneventful.
Data retrieved from NASA's ASRS site 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.