An A319 flight crew suffered repeated failures of the elac 2 computer that responded only momentaril...

Narrative:

Briefed by inbound crew [that the] elac (elevator aileron computer) 2 failed twice in flight; but did not recur after their second reset. Maintenance troubleshot and signed off the defect after landing. They experienced no issues on their next leg.on our flight; the elac 2 tripped off just prior to top of descent. We applied the ECAM/FM irregular procedure and elac 2 reset ok. We reported the event to maintenance on ACARS. Elac 2 tripped off again several minutes later and again reset ok. It then tripped off for the third time accompanied with an elev servo fault ECAM message during an intermittent level off at FL250. Applied ECAM/FM procedure; but chose not to reset elac 2 a third time based on the accompanying elev servo fault; the elac reset history; and the fact that we were running short on time in the final descent. We reported the elev servo fault via ACARS.before landing we applied the landing distance correction for landing and notified ATC of the flight control issue; however no emergency was declared. The subsequent flaps 3 altn law approach and direct law landing were uneventful.this was a red eye flight. The captain and I were both anxious to get on our way to get some sleep. We debriefed; but did not discuss any requirements to report the issue other than the log write-up and ACARS notification. It occurred to me after getting some rest that this may qualify as a flight control malfunction; thus requiring notification to company and the FAA.

Original NASA ASRS Text

Title: An A319 flight crew suffered repeated failures of the ELAC 2 computer that responded only momentarily to ECAM correction procedures before failing again. They landed safely at their destination using ALTN and DIRECT LAW approach and landing procedures.

Narrative: Briefed by inbound crew [that the] ELAC (Elevator Aileron Computer) 2 failed twice in flight; but did not recur after their second reset. Maintenance troubleshot and signed off the defect after landing. They experienced no issues on their next leg.On our flight; the ELAC 2 tripped off just prior to top of descent. We applied the ECAM/FM irregular procedure and ELAC 2 reset ok. We reported the event to Maintenance on ACARS. ELAC 2 tripped off again several minutes later and again reset ok. It then tripped off for the third time accompanied with an ELEV SERVO FAULT ECAM message during an intermittent level off at FL250. Applied ECAM/FM procedure; but chose not to reset ELAC 2 a third time based on the accompanying ELEV SERVO FAULT; the ELAC reset history; and the fact that we were running short on time in the final descent. We reported the ELEV SERVO fault via ACARS.Before landing we applied the landing distance correction for landing and notified ATC of the flight control issue; however no emergency was declared. The subsequent flaps 3 ALTN LAW approach and DIRECT LAW landing were uneventful.This was a red eye flight. The Captain and I were both anxious to get on our way to get some sleep. We debriefed; but did not discuss any requirements to report the issue other than the log write-up and ACARS notification. It occurred to me after getting some rest that this may qualify as a flight control malfunction; thus requiring notification to company and the FAA.

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.

Attributes
ACN	934998
Time
Date	201102
Local Time Of Day	0001-0600
Place
Locale Reference	ZAU.ARTCC
State Reference	IL
Environment
Light	Night
Aircraft 1
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Component
Aircraft Component	Aeroplane Flight Control
Person 1
Function	First Officer Pilot Not Flying
Experience	Flight Crew Last 90 Days 95 Flight Crew Total 8500 Flight Crew Type 155
Events
Anomaly	Aircraft Equipment Problem Critical Deviation - Procedural FAR

An A319 flight crew suffered repeated failures of the elac 2 computer that responded only momentarily to ECAM correction procedures before failing again. They landed safely at their destination using altn and direct law approach and landing procedures.