37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1071070 |
Time | |
Date | 201302 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Make Model Name | A300 |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Component | |
Aircraft Component | AHRS/ND |
Person 1 | |
Function | Captain |
Experience | Flight Crew Last 90 Days 90 Flight Crew Total 10000 Flight Crew Type 3000 |
Events | |
Anomaly | Aircraft Equipment Problem Critical Inflight Event / Encounter Weather / Turbulence |
Narrative:
On climbout the aircraft was struck by lightning. The first officer immediately lost all airspeed and attitude information and it returned in approximately 60 seconds. Additionally the autopilot number 1 temporarily disconnected. The number 2 yaw damper also failed at the time of the strike. The first officer lost the instruments again about 3 minutes later; and they did not return. We followed ECAM procedures and immediately contacted dispatch about proceeding to [the nearest airport] (non maintenance) or [a second airport] which was nearly equidistant at this point. Dispatch relayed they wanted aircraft in [the first airport]. I then asked my dispatcher to remind planning that a very heavy winter storm was just outside of the [divert] area and would arrive before any maintenance contract or other could arrive. I want to mention at this point that the weather and aircraft status for both fields were compatible and there was no safety of flight issues driving us in picking one over the other. Unfortunately planning did not seem to use any of the inputs the crew had offered in their decision matrix. They unwisely choose to send us to [the first airport].
Original NASA ASRS Text
Title: A300 Captain reports a lightning strike that knocks out several aircraft systems; including the First Officer's airspeed and attitude information. Dispatch is contacted and a diversion is suggested for the required maintenance but the planners do not agree and the flight continues to destination.
Narrative: On climbout the aircraft was struck by lightning. The First Officer immediately lost all airspeed and attitude information and it returned in approximately 60 seconds. Additionally the autopilot number 1 temporarily disconnected. The number 2 yaw damper also failed at the time of the strike. The First Officer lost the instruments again about 3 minutes later; and they did not return. We followed ECAM procedures and immediately contacted Dispatch about proceeding to [the nearest airport] (non maintenance) or [a second airport] which was nearly equidistant at this point. Dispatch relayed they wanted aircraft in [the first airport]. I then asked my Dispatcher to remind Planning that a very heavy winter storm was just outside of the [divert] area and would arrive before any Maintenance Contract or other could arrive. I want to mention at this point that the weather and aircraft status for both fields were compatible and there was no safety of flight issues driving us in picking one over the other. Unfortunately Planning did not seem to use any of the inputs the crew had offered in their decision matrix. They unwisely choose to send us to [the first airport].
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.