37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 303243 |
Time | |
Date | 199504 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : dca |
State Reference | DC |
Altitude | agl bound lower : 150 agl bound upper : 150 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : dca |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | descent : approach landing other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : flight engineer pilot : instrument pilot : atp |
Experience | flight time last 90 days : 250 flight time total : 5000 flight time type : 2400 |
ASRS Report | 303243 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 150 flight time total : 14000 flight time type : 800 |
ASRS Report | 303407 |
Events | |
Anomaly | aircraft equipment problem : critical |
Independent Detector | other flight crewa |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | other |
Narrative:
Day VFR, river runway 18, B757 7 mi ahead, wind 220 degrees/18 KTS/gusting 26. Hand flown approach at approximately 150 ft AGL the airplane started to roll left and right approximately 15 degrees aob 4-5 times. Executed missed approach. At level off we discussed causes and options. Elected to attempt another river visual runway 18. Systems ok till the flare, roll started again. Landed aircraft autothrust disenabled. We grounded aircraft and had lengthy conference call with the company maintenance found nothing wrong with airplane. Crew elected to go dca-dtw. That leg went without incident (visual runway 21R dtw gusty right crosswind). Took same aircraft to bwi (dtw-bwi). Level flight autoplt engaged at FL280 280 KTS noted small but rapid rolls and had a flight computer failure (elevator aileron computer 1). We elected to reset computer. Same situation occurred. Turned elevator aileron computer 1 off and landed but without incident. We are not sure if it was environmental (tower reported 10 KTS loss of airspeed on final) (no airspeed loss was noted) or a system problem. It is still under investigation. I would not have changed my decisions because we recognized the problem and too immediate action (missed approach) then got as many people involved in the decision process as we could. (On 2ND landing a 727 took off ahead of us). Our training and ability to talk openly about the situation I feel led to timely safe conclusions. Callback conversation with reporter revealed the following: though, unable to contact the reporter, another pilot with the same company, had previously sent a report and on that callback mentioned this incident. He had been the A320 air safety representative when the company debriefed the incident. He had also said if he could be of further assistance he would be happy to help, so a call was made to that pilot. He said that their company had previously required approachs with the A320 to be made with flaps 3 degrees at dca for noise abatement, but after this incident that was discontinued and full flaps are now used. He also said that with flaps 3 degrees, the controls are more sensitive. The company final resolution of this incident was that the rolls on final approach were pilot induced. It would appear to this analyst that the use of flaps 3 degrees was a poor procedure for several reasons: 1) causes the flight controls to be more sensitive in a more difficult than usual approach, 2) the A320 is one of a few aircraft that is unrestr at national because of it's low noise profile and 3) the runway is shorter than most and flaps 3 degrees requires extra ground roll due to extra speed. Supplemental information from acn 303407: unable to control airplane, did a go around. On second landing it happened again just prior to landing. Callback conversation with reporter revealed the following: the reporter flies the A-320 for a major united states air carrier. This incident was written up in the aircraft logbook and 'ground checked ok' by dca maintenance. Later that day, the same crew had some unwanted aileron input in cruise. Another crew had another incident where there was another unwanted aileron input. The aircraft was then taken OTS and maintenance found that there were spurious inputs from the first officer's control stick. The reporter believes 'that the aircraft did something on its own' and that there was no wake turbulence.
Original NASA ASRS Text
Title: UNCOMMANDED ROLL ON FINAL APCH -- HAPPENED TWICE AT SAME ARPT.
Narrative: DAY VFR, RIVER RWY 18, B757 7 MI AHEAD, WIND 220 DEGS/18 KTS/GUSTING 26. HAND FLOWN APCH AT APPROX 150 FT AGL THE AIRPLANE STARTED TO ROLL L AND R APPROX 15 DEGS AOB 4-5 TIMES. EXECUTED MISSED APCH. AT LEVEL OFF WE DISCUSSED CAUSES AND OPTIONS. ELECTED TO ATTEMPT ANOTHER RIVER VISUAL RWY 18. SYSTEMS OK TILL THE FLARE, ROLL STARTED AGAIN. LANDED ACFT AUTOTHRUST DISENABLED. WE GNDED ACFT AND HAD LENGTHY CONFERENCE CALL WITH THE COMPANY MAINT FOUND NOTHING WRONG WITH AIRPLANE. CREW ELECTED TO GO DCA-DTW. THAT LEG WENT WITHOUT INCIDENT (VISUAL RWY 21R DTW GUSTY R XWIND). TOOK SAME ACFT TO BWI (DTW-BWI). LEVEL FLT AUTOPLT ENGAGED AT FL280 280 KTS NOTED SMALL BUT RAPID ROLLS AND HAD A FLT COMPUTER FAILURE (ELEVATOR AILERON COMPUTER 1). WE ELECTED TO RESET COMPUTER. SAME SIT OCCURRED. TURNED ELEVATOR AILERON COMPUTER 1 OFF AND LANDED BUT WITHOUT INCIDENT. WE ARE NOT SURE IF IT WAS ENVIRONMENTAL (TWR RPTED 10 KTS LOSS OF AIRSPD ON FINAL) (NO AIRSPD LOSS WAS NOTED) OR A SYS PROB. IT IS STILL UNDER INVESTIGATION. I WOULD NOT HAVE CHANGED MY DECISIONS BECAUSE WE RECOGNIZED THE PROB AND TOO IMMEDIATE ACTION (MISSED APCH) THEN GOT AS MANY PEOPLE INVOLVED IN THE DECISION PROCESS AS WE COULD. (ON 2ND LNDG A 727 TOOK OFF AHEAD OF US). OUR TRAINING AND ABILITY TO TALK OPENLY ABOUT THE SIT I FEEL LED TO TIMELY SAFE CONCLUSIONS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: THOUGH, UNABLE TO CONTACT THE RPTR, ANOTHER PLT WITH THE SAME COMPANY, HAD PREVIOUSLY SENT A RPT AND ON THAT CALLBACK MENTIONED THIS INCIDENT. HE HAD BEEN THE A320 AIR SAFETY REPRESENTATIVE WHEN THE COMPANY DEBRIEFED THE INCIDENT. HE HAD ALSO SAID IF HE COULD BE OF FURTHER ASSISTANCE HE WOULD BE HAPPY TO HELP, SO A CALL WAS MADE TO THAT PLT. HE SAID THAT THEIR COMPANY HAD PREVIOUSLY REQUIRED APCHS WITH THE A320 TO BE MADE WITH FLAPS 3 DEGS AT DCA FOR NOISE ABATEMENT, BUT AFTER THIS INCIDENT THAT WAS DISCONTINUED AND FULL FLAPS ARE NOW USED. HE ALSO SAID THAT WITH FLAPS 3 DEGS, THE CTLS ARE MORE SENSITIVE. THE COMPANY FINAL RESOLUTION OF THIS INCIDENT WAS THAT THE ROLLS ON FINAL APCH WERE PLT INDUCED. IT WOULD APPEAR TO THIS ANALYST THAT THE USE OF FLAPS 3 DEGS WAS A POOR PROC FOR SEVERAL REASONS: 1) CAUSES THE FLT CTLS TO BE MORE SENSITIVE IN A MORE DIFFICULT THAN USUAL APCH, 2) THE A320 IS ONE OF A FEW ACFT THAT IS UNRESTR AT NATIONAL BECAUSE OF IT'S LOW NOISE PROFILE AND 3) THE RWY IS SHORTER THAN MOST AND FLAPS 3 DEGS REQUIRES EXTRA GND ROLL DUE TO EXTRA SPD. SUPPLEMENTAL INFO FROM ACN 303407: UNABLE TO CTL AIRPLANE, DID A GAR. ON SECOND LNDG IT HAPPENED AGAIN JUST PRIOR TO LNDG. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: THE RPTR FLIES THE A-320 FOR A MAJOR UNITED STATES ACR. THIS INCIDENT WAS WRITTEN UP IN THE ACFT LOGBOOK AND 'GND CHKED OK' BY DCA MAINT. LATER THAT DAY, THE SAME CREW HAD SOME UNWANTED AILERON INPUT IN CRUISE. ANOTHER CREW HAD ANOTHER INCIDENT WHERE THERE WAS ANOTHER UNWANTED AILERON INPUT. THE ACFT WAS THEN TAKEN OTS AND MAINT FOUND THAT THERE WERE SPURIOUS INPUTS FROM THE FO'S CTL STICK. THE RPTR BELIEVES 'THAT THE ACFT DID SOMETHING ON ITS OWN' AND THAT THERE WAS NO WAKE TURB.
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.