B737 CAPT REPORTS ACFT WITH MEL'ED APU IS TOWED TO GATE WITH APU RUNNING. APU IS USED TO START ENGINES.
Synopsis
B737 CAPT REPORTS ACFT WITH MEL'ED APU IS TOWED TO GATE WITH APU RUNNING. APU IS USED TO START ENGINES.
Narrative
UPON MY ARR AT THE GATE FOR AN ORIGINATING FLT; THE ACFT WAS IN THE PROCESS OF BEING TOWED FROM A REMOTE PARKING SPOT. I REVIEWED THE RELEASE AND NOTICED AN MEL APU INOP. HOWEVER; WHEN THE ACFT ARRIVED AT THE GATE; THE APU WAS RUNNING. IT HAD BEEN STARTED IN ERROR BY THE RAMPER RIDING THE BRAKES. I REVIEWED THE LOGBOOK AND THE APU WRITE-UP WAS 2 DAYS OLD. IT INDICATED THAT THE OIL LOW PRESSURE LIGHT REMAINED ILLUMINATED AND FREQ AND VOLTAGE READINGS READ ZERO. ADDITIONALLY; THERE WAS A STICKER AT THE SWITCH AND A STICKER INSIDE THE FRONT COVER OF THE LOGBOOK. HOWEVER; AT THIS TIME; THE APU WAS PERFORMING AS IT WAS SUPPOSED TO; THE LOW OIL PRESSURE LIGHT WAS OUT AND THE FREQ AND VOLTAGE READINGS WERE CORRECT. THE RAMPER HAD XFERRED PWR TO THE GENERATOR BUSSES. BOTTOM-LINE; THE APU WAS NOT INOP. I DID NOT NOTICE ANY HISTORICAL WRITE-UPS IN THE LOGBOOK THAT CONCERNED THE APU (THERE MAY HAVE BEEN SOME; I DID A FAIRLY QUICK SCAN). I CALLED DISPATCH TO INFORM THEM THAT IT APPEARED THE WRITE-UP MAY BE IN ERROR. I WAS TOLD THAT IT WOULD COST TOO MUCH TO CORRECT IT IN ZZZ AND HE WOULD PASS THE INFO TO MAINT AND IT WOULD BE ADDRESSED WHEN WE ARRIVED AT OUR FIRST DEST. THE DISPATCHER INDICATED THAT THE APU SHOULD NOT HAVE BEEN STARTED. I AGREED BUT SINCE IT HAD BEEN AND WAS WORKING APPROPRIATELY; I ELECTED TO USE IT. IN RETROSPECT; I PROBABLY SHOULD HAVE JUST SHUT IT DOWN AND PRESSED ON WITHOUT IT. INFLT I MESSAGED MAINT REQUESTING SOMEONE MEET ME AT THE GATE TO ADDRESS THE SITUATION. UPON ARR; I WAS MET BY A MECH WHO SAID THAT; 'MAINT WAS A BIT UP IN ARMS THAT WE HAD USED THE APU. IT HAD A HISTORY OF LOW OIL PRESSURE PROBS.' HE PULLED A CIRCUIT BREAKER TO ENSURE IT COULD NOT BE STARTED AND MADE AN ADDITION TO THE SP PORTION OF THE WRITE-UP. WE CONTINUED ON. A. MY PART (2 THINGS): 1) I DID A FAIRLY QUICK SCAN OF THE LOGBOOK AFTER I FOUND THE ORIGINAL WRITE-UP. IT'S POSSIBLE THERE MAY HAVE BEEN HISTORY. I DID NOT NOTICE ANY; BUT NEITHER CAN I SAY WITH ABSOLUTE CERTAINTY THAT THERE WASN'T ANY. I NEED TO BE MORE THOROUGH IN MY REVIEW. 2) A MORE CONSERVATIVE APCH BY ME MAY BE WARRANTED NEXT TIME. I'LL JUST RETURN THE ACFT TO ITS MEL'ED STATUS UNTIL THE WRITE-UP IS ACTUALLY CLRED. B. RAMP PERSONNEL: THE PERSON THAT STARTED THE APU IN THE FIRST PLACE NEEDS TO BE REFRESHED ON THE NEED FOR LOGBOOK REVIEW AND STICKER OBSERVANCE (THERE WAS A STICKER BY THE APU SWITCH). C. MAINT -- 2 THINGS: 1) MAYBE A BETTER WRITE-UP WOULD HAVE HELPED PREVENT THIS TYPE OF EVENT. APU INOP DIDN'T REALLY TELL THE CORRECT STORY; IT WASN'T INOP IT JUST HAD SOME PROBS THAT REQUIRED IT TO NOT BE USED. 2) SINCE MAINT WAS RILED UP THAT I USED THE APU; MY GUESS IS THAT THE DISPATCHER PASSED THE WORD TO THEM CONCERNING OUR CONVERSATION. IF THE PROB WAS SUCH THAT IT EXCITED THEM; MAYBE THEY OR DISPATCH COULD HAVE LET ME KNOW ABOUT THEIR CONCERNS BEFORE I REACHED THE MAINT BASE (I'M THINKING THE APU IS GOOD -- IF SOME TYPE OF EVENT HAD REQUIRED ITS USE; I WOULD HAVE USED IT). FURTHER; SINCE IT WAS IMPORTANT ENOUGH AN ISSUE THAT THEY EVENTUALLY PULLED A CIRCUIT BREAKER TO PREVENT FUTURE STARTS; MAYBE THAT SHOULD BE AN INITIAL PRECAUTIONARY MEASURE IN APU PROBS LIKE THIS. SUM: I AM NOT AWARE OF ANY SIGNIFICANT PROB THAT RESULTED FROM THIS EVENT. HOWEVER; IT IS A GOOD EXAMPLE OF HOW CONTRIBUTIONS FROM DIFFERENT ENTITIES CAN LEAD TO A POTENTIALLY BAD SITUATION. IF THE RAMPER HADN'T STARTED THE APU THERE WOULD HAVE BEEN NO PROB. IF THE LOGBOOK ENTRY HAD PROVIDED SOME MORE ENLIGHTENING INFO OR MAINT CONCERNS HAD BEEN RELAYED; I'D HAVE SHUT IT DOWN WITHOUT RESERVATION AND THERE WOULD HAVE BEEN NO SUBSEQUENT PROBS. IF I'D HAVE TAKEN A MORE CONSERVATIVE APCH AND SHUT IT DOWN; AGAIN THERE WOULD HAVE BEEN NO SUBSEQUENT PROBS. IF THE CIRCUIT BREAKER HAD BEEN PULLED IN THE FIRST PLACE; THERE WOULD HAVE BEEN NO PROB. IN MY CASE -- LESSON LEARNED.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.