 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
BE30 pilot reported overshooting assigned altitude because of an air data computer failure shortly after takeoff.
| Attributes | |
| ACN | 1312856 |
| Time | |
| Date | 201511 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | BUR.Airport |
| State Reference | CA |
| Environment | |
| Flight Conditions | Mixed |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Super King Air 300 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Air Data Computer |
| Person 1 | |
| Function | Single Pilot |
| Qualification | Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
| Experience | Flight Crew Last 90 Days 50 Flight Crew Total 10200 Flight Crew Type 3000 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Altitude Overshoot Deviation - Procedural Clearance |
Narrative:
[After departure;] just before hand off to socal; the air data computer failed (airspeed went to zero). I switched over to socal and started trying to figure out the problem (air data failure or airspeed indicator failure). At this time I was flying on the copilot's airspeed indicator and altimeter while comparing other air data computer instruments to determine what had failed. I did not want to connect the autopilot to any air data instruments until I had determined what was accurate and valid. It appeared the heading information was accurate so the autopilot was connected in the heading and attitude (pitch) mode. Then I did determine that the altitude information was correct but went through the socal assigned altitude before I connected the autopilot in the altitude hold mode. I was able to reset the air data computer and the rest of the flight was normal.having an airspeed failure in the first one thousand feet of a departure at night in scattered cloud conditions is distracting and challenging. The extra workload caused me to go through my assigned level off altitude.
Original NASA ASRS Text
Title: BE30 pilot reported overshooting assigned altitude because of an air data computer failure shortly after takeoff.
Narrative: [After departure;] just before hand off to SoCal; the Air Data Computer failed (airspeed went to zero). I switched over to SoCal and started trying to figure out the problem (air data failure OR airspeed indicator failure). At this time I was flying on the Copilot's airspeed indicator and altimeter while comparing other air data computer instruments to determine what had failed. I did not want to connect the autopilot to any Air Data instruments until I had determined what was accurate and valid. It appeared the heading information was accurate so the autopilot was connected in the heading and attitude (pitch) mode. Then I did determine that the altitude information was correct but went through the SoCal assigned altitude before I connected the autopilot in the altitude hold mode. I was able to reset the air data computer and the rest of the flight was normal.Having an airspeed failure in the first one thousand feet of a departure at night in scattered cloud conditions is distracting and challenging. The extra workload caused me to go through my assigned level off altitude.
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.