 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B747-400 first officer commanded a rejected takeoff after 50 knots when he realized that the right air data computer had failed.
| Attributes | |
| ACN | 1079872 |
| Time | |
| Date | 201304 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Make Model Name | B747-400 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Air Data Computer |
| Person 1 | |
| Function | Check Pilot First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical Deviation - Procedural Published Material / Policy |
Narrative:
We were cleared for takeoff and at about 50 knots I noticed my airspeed indicator make a fast and significant speed change to about 75 knots then back down to just over 50 knots at which point I called out 'airspeed.' I thought we might be experiencing severe windshear so I looked over at the captain's airspeed indicator to confirm and noticed not the same indications. I then looked back at my pfd and realized I had lost my entire air data computer system and announced 'I have lost everything' and then 'reject' at which point the captain performed the rejected takeoff procedure. We rejected below 80 knots and did not activate the rejected takeoff autobrakes; contacted tower and exited the runway. I realize our manuals state the captain has the sole responsibility for the decision to reject a takeoff but during this event I was concerned with the slow or lack of response from the captain after I first announced that we had an 'airspeed' problem and then a failure of the air data computer system shortly following. Although I was operating as a first office on this flight I am also a check airman and felt prompting the captain to perform a rejected takeoff before reaching 80 knots per our SOP's was the correct and safest course of action.
Original NASA ASRS Text
Title: A B747-400 First Officer commanded a rejected takeoff after 50 knots when he realized that the right air data computer had failed.
Narrative: We were cleared for takeoff and at about 50 knots I noticed my airspeed indicator make a fast and significant speed change to about 75 knots then back down to just over 50 knots at which point I called out 'Airspeed.' I thought we might be experiencing severe windshear so I looked over at the Captain's airspeed indicator to confirm and noticed not the same indications. I then looked back at my PFD and realized I had lost my entire Air Data Computer system and announced 'I have lost everything' and then 'Reject' at which point the Captain performed the Rejected Takeoff Procedure. We rejected below 80 knots and did not activate the RTO autobrakes; contacted Tower and exited the runway. I realize our manuals state the Captain has the sole responsibility for the decision to reject a takeoff but during this event I was concerned with the slow or lack of response from the Captain after I first announced that we had an 'airspeed' problem and then a failure of the Air Data Computer system shortly following. Although I was operating as a First Office on this flight I am also a Check Airman and felt prompting the Captain to perform a Rejected Takeoff before reaching 80 knots per our SOP's was the correct and safest course of action.
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.