37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 807326 |
Time | |
Date | 200808 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : zzz.airport |
State Reference | US |
Altitude | agl single value : 0 |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : preflight |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : relief pilot |
ASRS Report | 807326 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | aircraft equipment problem : critical maintenance problem : improper maintenance non adherence : far non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | other |
Factors | |
Maintenance | performance deficiency : fault isolation performance deficiency : inspection performance deficiency : non compliance with legal requirements performance deficiency : testing |
Supplementary | |
Problem Areas | Aircraft Maintenance Human Performance |
Primary Problem | Maintenance Human Performance |
Narrative:
The captain questioned the placarding of the first officer airspeed indicator (great smart move; captain -- kudos!) and the right autoplt from a previous write-up 3-4 days prior. The right autoplt was also placarded from the next day; I believe. When questioned about the original write-up during preflight; maintenance decided to change the right air data computer. The original write-up had 2 problems listed. Maintenance placarded the first officer's speed tape from that write-up. But it referenced another possible discrepancy also. Maintenance signoff of that original write-up included that the air data computer was ok! (Which makes me wonder why they changed their mind and wanted to change that piece.) while changing the air data computer the maintenance guy checked and found the right angle of attack vane was broken and decided that needed to be changed as well. Maintenance guy showed us the angle of attack vane and said that a static discharge caused the problem (visible discoloring; etc). Maintenance aid they were taking the aircraft OTS even though the guy said he could have the aircraft ready in 20 mins. The maintenance people had already taken the logbook; I questioned him about whether a lightning strike inspection was going to be done or not; and he did not know. The reason I am sending this is that I am not sure proper checks/analysis was done after the first write-up. Secondly; I want to give a kudos to the maintenance guy who found the angle of attack vane busted. Callback conversation with reporter revealed the following information: reporter stated the right angle of attack (aoa) vane was damaged from static discharge limiting the smooth rotation of the vane airfoil. Reporter stated there was a rough feel and a grinding sound when he and the mechanic tried to rotate the vane.
Original NASA ASRS Text
Title: A B767-300 RELIEF PILOT REPORTS ON QUESTIONABLE MAINT TROUBLE SHOOTING AND SIGNING OFF OF THE RIGHT AIR DATA COMPUTER; PLACARDING OF THE FO'S AIRSPEED INDICATOR AND RIGHT AUTOPILOT. AOA VANE FOUND DAMAGED.
Narrative: THE CAPT QUESTIONED THE PLACARDING OF THE FO AIRSPD INDICATOR (GREAT SMART MOVE; CAPT -- KUDOS!) AND THE R AUTOPLT FROM A PREVIOUS WRITE-UP 3-4 DAYS PRIOR. THE R AUTOPLT WAS ALSO PLACARDED FROM THE NEXT DAY; I BELIEVE. WHEN QUESTIONED ABOUT THE ORIGINAL WRITE-UP DURING PREFLT; MAINT DECIDED TO CHANGE THE R ADC. THE ORIGINAL WRITE-UP HAD 2 PROBS LISTED. MAINT PLACARDED THE FO'S SPD TAPE FROM THAT WRITE-UP. BUT IT REFED ANOTHER POSSIBLE DISCREPANCY ALSO. MAINT SIGNOFF OF THAT ORIGINAL WRITE-UP INCLUDED THAT THE ADC WAS OK! (WHICH MAKES ME WONDER WHY THEY CHANGED THEIR MIND AND WANTED TO CHANGE THAT PIECE.) WHILE CHANGING THE ADC THE MAINT GUY CHKED AND FOUND THE R ANGLE OF ATTACK VANE WAS BROKEN AND DECIDED THAT NEEDED TO BE CHANGED AS WELL. MAINT GUY SHOWED US THE ANGLE OF ATTACK VANE AND SAID THAT A STATIC DISCHARGE CAUSED THE PROB (VISIBLE DISCOLORING; ETC). MAINT AID THEY WERE TAKING THE ACFT OTS EVEN THOUGH THE GUY SAID HE COULD HAVE THE ACFT READY IN 20 MINS. THE MAINT PEOPLE HAD ALREADY TAKEN THE LOGBOOK; I QUESTIONED HIM ABOUT WHETHER A LIGHTNING STRIKE INSPECTION WAS GOING TO BE DONE OR NOT; AND HE DID NOT KNOW. THE REASON I AM SENDING THIS IS THAT I AM NOT SURE PROPER CHKS/ANALYSIS WAS DONE AFTER THE FIRST WRITE-UP. SECONDLY; I WANT TO GIVE A KUDOS TO THE MAINT GUY WHO FOUND THE ANGLE OF ATTACK VANE BUSTED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: REPORTER STATED THE RIGHT ANGLE OF ATTACK (AOA) VANE WAS DAMAGED FROM STATIC DISCHARGE LIMITING THE SMOOTH ROTATION OF THE VANE AIRFOIL. REPORTER STATED THERE WAS A ROUGH FEEL AND A GRINDING SOUND WHEN HE AND THE MECHANIC TRIED TO ROTATE THE VANE.
Data retrieved from NASA's ASRS site as of May 2009 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.