Narrative:

On departure from msp detected airframe vibration similar to being in continuous light chop. Vibration persisted. Contacted dispatch and maintenance. Coordinated with maintenance and tried various airspeed, pitch, and bank combinations. Vibration persisted. I decided to return to msp. Advised cabin crew, dispatch, and ATC. Approach was normal until last 200 ft. When correcting for gusts and crosswind controls felt very sluggish, roll response was very slow. Landing was hard, ailerons required full opposite control input to keep wings level. After landing passenger gave me a note describing a 'fluttering' right aileron. Our maintenance personnel also noticed right aileron fluttering as we were taxiing in. Problems: we had a vibration from an unknown source. With fly by wire we had no control service feedback indicating a flight control problem. Aircraft automatic flight system 'masked' flight control problem. We discovered aileron degradation during last 200 ft of approach. Not a good situation. Here is a case of automation masking root cause of a potentially serious problem. Callback conversation with reporter revealed the following information: the reporter stated that the crew was flying an A320 aircraft. The crew had no eicam failure mode annunciation. Air carrier maintenance found a failed elac (elevator and aileron computer). None of the self test diagnostic routines disclosed a problem. Only during a maintenance shop test did a problem surface. The right aileron was the affected flight control. Pilot control effectiveness was either doubled or cut in half depending on whether the pilot input was in phase or out of phase with the faulty elac computer. The captain said that the aircraft has two of these computers and when one becomes faulty it is suppose to disengage itself. This did not happen.

Google
 

Original NASA ASRS Text

Title: CREW HAD AIRFRAME VIBRATION AND REDUCED CTL EFFECTIVENESS.

Narrative: ON DEP FROM MSP DETECTED AIRFRAME VIBRATION SIMILAR TO BEING IN CONTINUOUS LIGHT CHOP. VIBRATION PERSISTED. CONTACTED DISPATCH AND MAINT. COORDINATED WITH MAINT AND TRIED VARIOUS AIRSPEED, PITCH, AND BANK COMBINATIONS. VIBRATION PERSISTED. I DECIDED TO RETURN TO MSP. ADVISED CABIN CREW, DISPATCH, AND ATC. APCH WAS NORMAL UNTIL LAST 200 FT. WHEN CORRECTING FOR GUSTS AND XWIND CONTROLS FELT VERY SLUGGISH, ROLL RESPONSE WAS VERY SLOW. LNDG WAS HARD, AILERONS REQUIRED FULL OPPOSITE CTL INPUT TO KEEP WINGS LEVEL. AFTER LNDG PAX GAVE ME A NOTE DESCRIBING A 'FLUTTERING' RIGHT AILERON. OUR MAINT PERSONNEL ALSO NOTICED RIGHT AILERON FLUTTERING AS WE WERE TAXIING IN. PROBLEMS: WE HAD A VIBRATION FROM AN UNKNOWN SOURCE. WITH FLY BY WIRE WE HAD NO CTL SERVICE FEEDBACK INDICATING A FLIGHT CTL PROBLEM. ACFT AUTO FLT SYSTEM 'MASKED' FLT CTL PROBLEM. WE DISCOVERED AILERON DEGRADATION DURING LAST 200 FT OF APCH. NOT A GOOD SIT. HERE IS A CASE OF AUTOMATION MASKING ROOT CAUSE OF A POTENTIALLY SERIOUS PROB. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THAT THE CREW WAS FLYING AN A320 ACFT. THE CREW HAD NO EICAM FAILURE MODE ANNUNCIATION. ACR MAINT FOUND A FAILED ELAC (ELEVATOR AND AILERON COMPUTER). NONE OF THE SELF TEST DIAGNOSTIC ROUTINES DISCLOSED A PROB. ONLY DURING A MAINT SHOP TEST DID A PROB SURFACE. THE RIGHT AILERON WAS THE AFFECTED FLT CTL. PLT CTL EFFECTIVENESS WAS EITHER DOUBLED OR CUT IN HALF DEPENDING ON WHETHER THE PLT INPUT WAS IN PHASE OR OUT OF PHASE WITH THE FAULTY ELAC COMPUTER. THE CAPT SAID THAT THE ACFT HAS TWO OF THESE COMPUTERS AND WHEN ONE BECOMES FAULTY IT IS SUPPOSE TO DISENGAGE ITSELF. THIS DID NOT HAPPEN.

Data retrieved from NASA's ASRS site as of July 2007 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.