37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 417469 |
Time | |
Date | 199810 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : zzz airport : zzz |
State Reference | US |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B727-200 |
Flight Phase | ground other : taxi other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 417469 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | aircraft equipment problem : critical non adherence : published procedure non adherence : far other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Air Traffic Incident | other |
Narrative:
Taxiing out of ZZZ the stick shaker went off 3 or 4 times. We checked the MEL and contacted maintenance and returned to a hard stand. A mechanic came to the cockpit. He reached down and touched the stick shaker mechanism for approximately 2 seconds. He then picked up the logbook to clear item which stated 'on taxi out stall warning/stick shaker activated 3 times.' the maintenance clearing entry was 'cleaned and reseated plug on stick shaker checks good, employee #abzcx.' the mechanic did not do anything at all. He did not clean, reseat, or check anything. I then told him we were going to discuss his actions after he left and would most likely find that we were not satisfied with his fix. He said he would check some switches in the wheel well and to taxi out and try it again. I asked about what troubleshooting procedure there might be. He said try it again and if we had a problem he would follow the procedure. I told him that we had come back and called maintenance so we could follow the procedure. He paid no attention to my concern. He left the cockpit and about 5 mins later he said over the interphone that he had found the vane in the vertical position and had spun it around and thought that we would have seen the stick shaker activate. It did not activate. This mechanic displayed an obvious disregard for this entry. In our opinion he did nothing even at our further request to troubleshoot the system. We returned to the gate and I called air carrier tech and talked to controller. I told him the story and said we needed maintenance. The same guy came to the cockpit and started giving me trouble because I said that he did not clean and reseat the plug. He actually tried to tell us that he had when we were right there and knew that he had done nothing except pencil whip the logbook. I told him we were not stupid and knew that nothing was done. When he continued arguing I told him to get the hell out and that we needed real maintenance. He left the airplane. I talked again to air carrier tech but could not get any further maintenance action of any kind. We were now having a maintenance standoff. They were playing games at the expense of safety and passenger convenience. I tried for close to 1 hour to get maintenance with no success. Maintenance told the supervisor (xyz, I think) that they did not see a problem with the airplane. They would not come back to the airplane. The cockpit crew went illegal, and the flight was canceled. We inconvenienced 130 passenger and created a real mess for the station. Thousands of dollars in revenue were lost and thousands more probably lost due to having to ferry the airplane to YYY. The main problem is their neglect of procedures and willingness to compromise safety. The MEL, our procedures and maintenance, are there for a reason. They should be followed. I contacted the chief pilot. He advised me of an appropriate follow-up write-up, request further action on previous PIREP. Not satisfied with maintenance action taken. The clearing entry was as follows: replaced asa vane and control module operations check normal, change for crew precautionary reason. Maintenance action was finally taken but it is obvious that ZZZ maintenance still had an attitude and that safety was not their only concern. I also informed the ZZZ city manager that same evening. Dispatch and air carrier tech were continually involved and tried to resolve our problem with no success. Callback conversation with reporter revealed the following information: the reporter stated the mechanic did absolutely nothing to put this airplane back in service. The reporter said what was really a bad experience was local management and the maintenance controller unable to control this situation. The reporter stated it was a standoff with nothing done on the aircraft with passenger waiting to depart.
Original NASA ASRS Text
Title: A B727-200 RETURNED TO THE GATE DUE TO STALL WARNING STICK SHAKER ACTIVATION AND ASSIGNED MECH ATTEMPTED TO PENCIL WHIP THE RPT WITH NO MAINT ACTION.
Narrative: TAXIING OUT OF ZZZ THE STICK SHAKER WENT OFF 3 OR 4 TIMES. WE CHKED THE MEL AND CONTACTED MAINT AND RETURNED TO A HARD STAND. A MECH CAME TO THE COCKPIT. HE REACHED DOWN AND TOUCHED THE STICK SHAKER MECHANISM FOR APPROX 2 SECONDS. HE THEN PICKED UP THE LOGBOOK TO CLR ITEM WHICH STATED 'ON TAXI OUT STALL WARNING/STICK SHAKER ACTIVATED 3 TIMES.' THE MAINT CLRING ENTRY WAS 'CLEANED AND RESEATED PLUG ON STICK SHAKER CHKS GOOD, EMPLOYEE #ABZCX.' THE MECH DID NOT DO ANYTHING AT ALL. HE DID NOT CLEAN, RESEAT, OR CHK ANYTHING. I THEN TOLD HIM WE WERE GOING TO DISCUSS HIS ACTIONS AFTER HE LEFT AND WOULD MOST LIKELY FIND THAT WE WERE NOT SATISFIED WITH HIS FIX. HE SAID HE WOULD CHK SOME SWITCHES IN THE WHEEL WELL AND TO TAXI OUT AND TRY IT AGAIN. I ASKED ABOUT WHAT TROUBLESHOOTING PROC THERE MIGHT BE. HE SAID TRY IT AGAIN AND IF WE HAD A PROB HE WOULD FOLLOW THE PROC. I TOLD HIM THAT WE HAD COME BACK AND CALLED MAINT SO WE COULD FOLLOW THE PROC. HE PAID NO ATTN TO MY CONCERN. HE LEFT THE COCKPIT AND ABOUT 5 MINS LATER HE SAID OVER THE INTERPHONE THAT HE HAD FOUND THE VANE IN THE VERT POS AND HAD SPUN IT AROUND AND THOUGHT THAT WE WOULD HAVE SEEN THE STICK SHAKER ACTIVATE. IT DID NOT ACTIVATE. THIS MECH DISPLAYED AN OBVIOUS DISREGARD FOR THIS ENTRY. IN OUR OPINION HE DID NOTHING EVEN AT OUR FURTHER REQUEST TO TROUBLESHOOT THE SYS. WE RETURNED TO THE GATE AND I CALLED ACR TECH AND TALKED TO CTLR. I TOLD HIM THE STORY AND SAID WE NEEDED MAINT. THE SAME GUY CAME TO THE COCKPIT AND STARTED GIVING ME TROUBLE BECAUSE I SAID THAT HE DID NOT CLEAN AND RESEAT THE PLUG. HE ACTUALLY TRIED TO TELL US THAT HE HAD WHEN WE WERE RIGHT THERE AND KNEW THAT HE HAD DONE NOTHING EXCEPT PENCIL WHIP THE LOGBOOK. I TOLD HIM WE WERE NOT STUPID AND KNEW THAT NOTHING WAS DONE. WHEN HE CONTINUED ARGUING I TOLD HIM TO GET THE HELL OUT AND THAT WE NEEDED REAL MAINT. HE LEFT THE AIRPLANE. I TALKED AGAIN TO ACR TECH BUT COULD NOT GET ANY FURTHER MAINT ACTION OF ANY KIND. WE WERE NOW HAVING A MAINT STANDOFF. THEY WERE PLAYING GAMES AT THE EXPENSE OF SAFETY AND PAX CONVENIENCE. I TRIED FOR CLOSE TO 1 HR TO GET MAINT WITH NO SUCCESS. MAINT TOLD THE SUPVR (XYZ, I THINK) THAT THEY DID NOT SEE A PROB WITH THE AIRPLANE. THEY WOULD NOT COME BACK TO THE AIRPLANE. THE COCKPIT CREW WENT ILLEGAL, AND THE FLT WAS CANCELED. WE INCONVENIENCED 130 PAX AND CREATED A REAL MESS FOR THE STATION. THOUSANDS OF DOLLARS IN REVENUE WERE LOST AND THOUSANDS MORE PROBABLY LOST DUE TO HAVING TO FERRY THE AIRPLANE TO YYY. THE MAIN PROB IS THEIR NEGLECT OF PROCS AND WILLINGNESS TO COMPROMISE SAFETY. THE MEL, OUR PROCS AND MAINT, ARE THERE FOR A REASON. THEY SHOULD BE FOLLOWED. I CONTACTED THE CHIEF PLT. HE ADVISED ME OF AN APPROPRIATE FOLLOW-UP WRITE-UP, REQUEST FURTHER ACTION ON PREVIOUS PIREP. NOT SATISFIED WITH MAINT ACTION TAKEN. THE CLRING ENTRY WAS AS FOLLOWS: REPLACED ASA VANE AND CTL MODULE OPS CHK NORMAL, CHANGE FOR CREW PRECAUTIONARY REASON. MAINT ACTION WAS FINALLY TAKEN BUT IT IS OBVIOUS THAT ZZZ MAINT STILL HAD AN ATTITUDE AND THAT SAFETY WAS NOT THEIR ONLY CONCERN. I ALSO INFORMED THE ZZZ CITY MGR THAT SAME EVENING. DISPATCH AND ACR TECH WERE CONTINUALLY INVOLVED AND TRIED TO RESOLVE OUR PROB WITH NO SUCCESS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THE MECH DID ABSOLUTELY NOTHING TO PUT THIS AIRPLANE BACK IN SVC. THE RPTR SAID WHAT WAS REALLY A BAD EXPERIENCE WAS LCL MGMNT AND THE MAINT CTLR UNABLE TO CTL THIS SIT. THE RPTR STATED IT WAS A STANDOFF WITH NOTHING DONE ON THE ACFT WITH PAX WAITING TO DEPART.
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.