37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 876161 |
Time | |
Date | 201002 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Component | |
Aircraft Component | Air Data Computer |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 240 Flight Crew Total 16000 Flight Crew Type 400 |
Person 2 | |
Function | Pilot Flying First Officer |
Experience | Flight Crew Last 90 Days 80 Flight Crew Total 25000 Flight Crew Type 2000 |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
During takeoff roll; with the first officer (first officer) as pilot flying (PF); shortly after the 80kts call; I noticed the first officer's airspeed needle seemed to be lagging. I did not think this warranted a high speed abort; as all other indications appeared normal; with no EICAS warnings. Rotation was normal; but during initial climb; the first officer's airspeed; vertical speed indicator (vsi); and altimeter were giving erroneous indications; compared to mine and the standby instruments. We also lost both flight directors. After the flaps-up call; the first officer transferred aircraft control to me. I engaged the autopilot at about 8;000 feet MSL; and at some point the flight directors came back on. We then got an EICAS mach speed trim and rudder ratio message; along with associated lights on the overhead panel. At this point the first officer's pitot static instruments were completely failed; and we suspected an air data computer (air data computer) failure. ZZZ departure was very helpful in giving us vectors; and eventually holding at xyz VOR; as we were not sure at that point whether we were going back to ZZZ. We contacted dispatch and maintenance control; and after consultation we switched the first officer's (first officer) air data to alternate; at which time his instruments were fully restored. After evaluating weather; fuel; and aircraft condition; we all concurred that the safest course of action was to continue to ZZZ1. I gave the purser a cabin advisory; and subsequently advised of our decision to continue. I also advised the passengers. The flight continued normally to ZZZ1. During discussions with maintenance control; we learned that maintenance had worked on the standby instruments and air data computer the previous evening. I would like to find out the reason for the failure.
Original NASA ASRS Text
Title: A Captain and First Officer report about losing both Flight Directors on their B757-200 during initial climb going into IMC conditions. The First Officer; who was the Pilot Flying; noticed his Airspeed roll back to 110 knots; his Vertical Speed Indicator showed 500 feet per minute (FPM) down and the Altimeter frozen at 5;300 feet. A cabin pressurization problem also developed at 10;000 feet.
Narrative: During takeoff roll; with the First Officer (F/O) as Pilot Flying (PF); shortly after the 80kts call; I noticed the F/O's Airspeed needle seemed to be lagging. I did not think this warranted a high speed abort; as all other indications appeared normal; with no EICAS warnings. Rotation was normal; but during initial climb; the F/O's Airspeed; Vertical Speed Indicator (VSI); and Altimeter were giving erroneous indications; compared to mine and the standby instruments. We also lost both Flight Directors. After the Flaps-Up call; the F/O transferred aircraft control to me. I engaged the Autopilot at about 8;000 feet MSL; and at some point the Flight Directors came back on. We then got an EICAS Mach Speed Trim and Rudder Ratio message; along with associated lights on the Overhead Panel. At this point the F/O's Pitot Static instruments were completely failed; and we suspected an Air Data Computer (ADC) failure. ZZZ Departure was very helpful in giving us vectors; and eventually holding at XYZ VOR; as we were not sure at that point whether we were going back to ZZZ. We contacted Dispatch and Maintenance Control; and after consultation we switched the First Officer's (F/O) Air Data to Alternate; at which time his instruments were fully restored. After evaluating weather; fuel; and aircraft condition; we all concurred that the safest course of action was to continue to ZZZ1. I gave the Purser a cabin advisory; and subsequently advised of our decision to continue. I also advised the passengers. The flight continued normally to ZZZ1. During discussions with Maintenance Control; we learned that Maintenance had worked on the Standby Instruments and ADC the previous evening. I would like to find out the reason for the failure.
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.