A320 FLT CREW LAMENTS ABUNDANCE OF 'HELP' OFFERED DURING MAINTENANCE TROUBLESHOOTING EXERCISE AT BUSY ARPT BY ATC; OPS; MAINTENANCE; AND FA'S.

Date: 2008-05 · Aircraft: A320 · Phase: taxi

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

Synopsis

A320 FLT CREW LAMENTS ABUNDANCE OF 'HELP' OFFERED DURING MAINTENANCE TROUBLESHOOTING EXERCISE AT BUSY ARPT BY ATC; OPS; MAINTENANCE; AND FA'S.

Narrative

ON PUSHBACK; WE NOTICED BLUE HYD SYS PAGE HAD AN INDICATION OF PARTIAL PRESSURE. WE TOLD GND WE WOULD BE A WHILE AS WE WOULD HAVE TO HANDLE THE ISSUE WITH MAINT AND ASKED WHERE THEY WOULD LIKE US TO PARK. THEY DIRECTED US TO A SPOT. WE TAXIED OVER TO THE SPOT AND CONTACTED MAINT. WE GOT A HOLD OF MAINT AND BEGAN TO TROUBLESHOOT THE PROB. IT INITIALLY TOOK A WHILE AS MAINT WAS THINKING THE PROB TO BE SOMETHING OTHER. I EXPLAINED TO MAINT THAT I KNOW THE PROB TO BE A PRESSURE FAULT SENSOR AS I AM FAMILIAR WITH IT. BASICALLY WE WERE FINALLY ON AGREEMENT BUT IT TOOK A WHILE TO RESOLVE THE CLARITY OF THE PROB. THE PROB WAS THAT WHILE WORKING WITH MAINT; THE FLT ATTENDANTS CALLED TO ADVISE THAT A PAX NEEDED TO GO TO THE LAVATORY; THEN GND CTL DIRECTED US TO CALL OPS. ATC THEN BEGAN TO QUERY US HOW LONG IT WOULD TAKE US TO MOVE AND WE TOLD THEM WE WERE STILL WORKING ON THE MAINT ISSUE TROUBLESHOOTING. ATC BEGAN TO GET IMPATIENT. THE FO THEN CALLED OPS AND BEGAN TO HAVE TO ANSWER A LOT OF UNNECESSARY QUESTIONS AS TO WHAT OUR SITUATION WAS AND DETRACTING HIS ABILITY TO CONTINUE TO HELP WITH THE TROUBLESHOOT AND MAINTAIN VIGILANT SITUATIONAL AWARENESS WHILE HOLDING AT A PRECARIOUS SPOT AS ACFT WERE TAXIING FOR TKOF ALL AROUND US. AS THE FO WAS STILL INVOLVED WITH OPS; THE FLT ATTENDANT CALLED TO ADVISE US OF THE PAX STATUS AND AT THAT SAME MOMENT I HEAR THE 'MECH' CALL BUZZER GO OFF?! NEEDLESS TO SAY; IT CAUGHT ME TOTALLY BY SURPRISE. I ANSWERED THE CALL AND FOUND MYSELF TALKING TO A GND CREW?! WHEN I ANSWERED; HE SAID THAT OPS SENT HIM OUT?! TO AN ACTIVE TXWY WITHOUT OUR KNOWLEDGE?! I IMMEDIATELY TOLD HIM WE DID NOT NEED HIM AND TO DISCONNECT. THE MULTIPLE CALLS FROM MAINT; FLT ATTENDANTS; GND CTL; OPS AND GND CREW WAS HAZARDOUS AND CAUSED MOMENTARY LOSS OF COM WITH GND AND CREATED SERIOUS SITUATIONAL AWARENESS DISTR AT A CRITICAL POINT; ON THE GND ON AN ACTIVE TXWY NEAR THE DEP END. I ALSO AM ALARMED TO HAVE HAD THE GND CREW APCH THE AIRPLANE WITHOUT MY CLR UNDERSTANDING OR KNOWLEDGE OF THIS INTENT AS IT WAS AND COULD HAVE BEEN DANGEROUS. WE WERE JUST ABOUT TO START THE ENGS AND TAXI AND THIS WOULD HAVE POSED THE GND CREW TO BE IN DANGER! OPS ACTED OVERZEALOUSLY IN SENDING OUT THE GND CREW WITHOUT MY KNOWLEDGE AND CONCURRENCE AND THEIR PRIME OBJECTIVE IS TO SUPPORT OUR OP AND NOT VICE VERSA. TO FINISH THE EVENT AS WE WAITED FOR MAINT TO SEND THE NEW RELEASE OUR PRINTER PAPER WAS OUT AND WE HAD TO RESTOCK CAUSING ANOTHER DELAY AS THE PRINT WAS IN MID PROCESS. WHILE WE WAITED FOR THE RELEASE; GND CTL WAS ALLOWING AIRPLANES (B757'S) TO TAXI BTWN OUR SPOT AND THE TERMINAL! IN THE WAKE OF OUR MANDATORY ON-THE-LINE DAY COURSE; I FIND THE CHAIN OF EVENTS TO BE UNPROFESSIONALLY AND UNSAFELY HANDLED AT SUCH A CRITICAL POINT OF FLT WITH LITTLE PATIENCE AND THE PRESSURE TO HURRY AND ANSWER TO ALL. I; HOWEVER; DID NOT ALLOW THIS TO EXACERBATE AND SLOWED THE TEMPO AND MADE SURE EVERYTHING WAS DONE CALCULATING AND SAFELY.

More incidents for this aircraft family →

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