37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1025009 |
Time | |
Date | 201207 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | A319 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Component | |
Aircraft Component | Air Data Computer |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
During takeoff roll around 100 KTS I lost my airspeed indication on my primary flight display (pfd). I immediately looked over to the first officer's pfd; noticed his airspeed indication was normal; decided to continue the takeoff; and verbalized 'continuing.' I rotated when the first officer said rotate. We raised the landing gear and around 200 ft AGL we got a master warning; master caution; and several ECAM messages with the associated crc and chimes. We also lost our flight directors; auto thrust; and the autopilot 2 would not engage. I transferred control to the first officer and tried to sort through the ECAM messages using our non-normal methodology. We had the following ECAM warning messages-automatic flight rud trv lim system; automatic flight a/thr off; automatic flight; F/control elac 1 pitch fault; F/control; navigation IAS discrepancy. The maintenance post flight report recorded all of the above messages at our takeoff time. Some of the ECAM messages cleared with no action and some did not. Some ECAM messages reappeared after a few seconds and it was difficult to determine which messages were valid. The last ECAM message navigation IAS discrepancy remained and I accomplished the ECAM action by switching the air data switch to captain on 3. I got back my airspeed indication and then more ECAM messages reappeared. The first officer and I decided to declare an emergency and return. I felt that with the multiple chimes every 5-10 seconds and computer faults we could not safely continue to destination. Computer faults; maybe pitot static system faults. [I] had a rest of 9+31 (block to block) prior to this duty period. This rest includes travel time to the hotel and 1 hour reporting time and did not provide 8 hours sleep. All airlines should implement the new FAA rest rules now.
Original NASA ASRS Text
Title: A319 Captain experiences loss of airspeed indication at 100 KTS and continues the takeoff; noting that the First Officer's indications are normal. Once airborne; many ECAM warnings associated with the loss of ADR 1 are annunciated. With the Captain's PFD using ADR 3; airspeed indication returns; but other anomalies remain and the crew elects to return to the departure airport.
Narrative: During takeoff roll around 100 KTS I lost my airspeed indication on my Primary Flight Display (PFD). I immediately looked over to the First Officer's PFD; noticed his airspeed indication was normal; decided to continue the takeoff; and verbalized 'continuing.' I rotated when the First Officer said rotate. We raised the landing gear and around 200 FT AGL we got a master warning; master caution; and several ECAM messages with the associated CRC and chimes. We also lost our flight directors; auto thrust; and the Autopilot 2 would not engage. I transferred control to the First Officer and tried to sort through the ECAM messages using our Non-Normal Methodology. We had the following ECAM Warning Messages-AUTO FLT RUD TRV LIM SYS; AUTO FLT A/THR OFF; AUTO FLT; F/CTL ELAC 1 PITCH FAULT; F/CTL; NAV IAS discrepancy. The Maintenance post flight report recorded all of the above messages at our takeoff time. Some of the ECAM messages cleared with no action and some did not. Some ECAM messages reappeared after a few seconds and it was difficult to determine which messages were valid. The last ECAM message NAV IAS discrepancy remained and I accomplished the ECAM Action by switching the air data switch to CAPT on 3. I got back my airspeed indication and then more ECAM messages reappeared. The First Officer and I decided to declare an emergency and return. I felt that with the multiple chimes every 5-10 seconds and computer faults we could not safely continue to destination. Computer faults; maybe pitot static system faults. [I] had a rest of 9+31 (block to block) prior to this duty period. This rest includes travel time to the hotel and 1 hour reporting time and did not provide 8 hours sleep. All airlines should implement the new FAA rest rules now.
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.