A320 CAPT REPORTS AILERON SERVO ECAM DURING TAXI OUT. AFTER CONSULTING FOM; ECAM IS CLEARED AND FLT DEPARTS. ENROUTE FLIGHT CONTROL PAGE SHOWS AILERON FAULT PRESENT; ALTHOUGH STATUS PAGE SHOWS NOTHING.

Date: 2008-08 · Aircraft: A320

Anomalies: aircraft-equipment-problem-less-severe|deviation-discrepancy-procedural-published-material-policy

Synopsis

A320 CAPT REPORTS AILERON SERVO ECAM DURING TAXI OUT. AFTER CONSULTING FOM; ECAM IS CLEARED AND FLT DEPARTS. ENROUTE FLIGHT CONTROL PAGE SHOWS AILERON FAULT PRESENT; ALTHOUGH STATUS PAGE SHOWS NOTHING.

Narrative

ON TAXI OUT -- RECEIVED ECAM MESSAGE; 'AILERON SERVO INOP.' AFTER REVIEWING COCKPIT OPERATING MANUAL -- MESSAGE WAS DELETED. PRIOR TO DEP; 'STATUS PAGE' WAS CALLED UP AND NOTHING WAS INDICATED AS INOP SYSTEMS. IN CRUISE -- A RANDOM CHK OF THE FLT CONTROL PAGE INDICATED THE AILERON SERVO WAS STILL INOP -- BUT NEVER ILLUMINATED AS AN INOP SYSTEM; SO I BELIEVE THE SERVO WAS PROBABLY INOP DURING TKOF ALSO. THE AIRBUS SYSTEM SEEMS TO HAVE A 'HIDDEN THREAT' IN ITS MONITORING SYSTEM. YOU CAN ACTUALLY HAVE AN INOP SYSTEM AND NOT HAVING IT SHOWN ON THE 'INOP STATUS' PAGE. I DON'T KNOW HOW THE BOEING MONITORING SYSTEM WORKS -- BUT I DOUBT IT WOULD 'HIDE' AN INOP SYSTEM LIKE THE 'AIRBUS' SYSTEM SEEMS TO DO.CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE REPORTER BELIEVED THAT THE SERVO FAULT HAD CORRECTED ITSELF PRIOR TO TKOF DUE TO ITS ABSENCE FROM THE STATUS PAGE. ELAC 1 HAD FAULTED AT THE GATE AND WAS RESET BY MAINTENANCE PRIOR TO PUSH BACK. IT IS LIKELY THAT THE AILERON SERVO FAULT CAUSED THE ELAC FAULT AND WAS INTERMITTENT IN NATURE.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.