![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1446969 |
| Time | |
| Date | 201705 |
| Place | |
| Locale Reference | ZZZ.ARTCC |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Engine Control |
| Person 1 | |
| Function | Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 60 Flight Crew Total 10848 Flight Crew Type 5601 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
While in cruise (FL350) we got an ECAM on some navigation anomaly; immediately followed by a fadec engine 1 fault and then fadec engine 2 fault ECAM with a list of items; shortly after we got a dual engine fail ECAM. However; engine indications were normal. This continued for 1-2 minutes then stop; then after a short while; maybe 5-8 minutes; the same scenario would repeat itself. We then contacted dispatch and maintenance to formulate a plan of action if needed; and started the APU. We agreed that if it occurred again we would deviate. We continued with a normal flight until starting our descent; at which time the above scenario repeated itself almost continuously; with short stop intervals! Emergency cancel button was ineffective. We continued with uneventful approach and landing; all flight controls; avionics and engine instruments were normal.
Original NASA ASRS Text
Title: A319 Captain reported several ECAM messages that would clear after 1 or 2 minutes then repeat 5 to 8 minutes later. Flight continued to destination.
Narrative: While in cruise (FL350) we got an ECAM on some NAV anomaly; immediately followed by a FADEC engine 1 fault and then FADEC engine 2 fault ECAM with a list of items; shortly after we got a DUAL ENG FAIL ECAM. However; engine indications were normal. This continued for 1-2 minutes then stop; then after a short while; maybe 5-8 minutes; the same scenario would repeat itself. We then contacted Dispatch and Maintenance to formulate a plan of action if needed; and started the APU. We agreed that if it occurred again we would deviate. We continued with a normal flight until starting our descent; at which time the above scenario repeated itself almost continuously; with short stop intervals! Emergency cancel button was ineffective. We continued with uneventful approach and landing; all flight controls; avionics and engine instruments were normal.
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.