A B737-300 WAS DISPATCHED IN NON COMPLIANCE WITH NO MAINT RELEASE SIGNED IN THE LOGBOOK. HAD GND PWR RECEPTACLE REPLACED.

Date: 2003-04 · Aircraft: B737-300 · Phase: ground

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

Synopsis

A B737-300 WAS DISPATCHED IN NON COMPLIANCE WITH NO MAINT RELEASE SIGNED IN THE LOGBOOK. HAD GND PWR RECEPTACLE REPLACED.

Narrative

ACFT WAS A MAINT FERRY FROM ZZZ1 TO FIX A BROKEN EXTERNAL PWR RECEPTACLE ASSEMBLY. IT ARRIVED IN ZZZ FOR THE REPAIRS AND DEPARTED AT XA15 WITHOUT THE ACFT RELEASE. IN ACCORDANCE WITH OUR PROC; AN ACFT RELEASE IS REQUIRED. AS THE SUPVR ON DUTY; I FEEL IT WAS MY RESPONSIBILITY TO INFORM THE NEW LEAD THAT CAME ON DUTY AT XD30 THAT THIS ACFT WAS A FERRY FLT INTO ZZZ. ON MAY/MON/03; THE ACFT WAS IN AND MAINT RECEIVED A GATE CALL. THE CREW INFORMED THE MECHS THAT THE LOGBOOK HAD NO ACFT RELEASE AFTER THE FERRY FLT. AN ACFT RELEASE WAS ENTERED INTO THE LOGBOOK AT THAT TIME. I FEEL THAT LACK OF COM; INFORMING THE ON-COMING LEAD MECH LED TO THIS MISSED DOCUMENTATION. TO PREVENT THIS OCCURRENCE AGAIN; ALL ACFT FERRIES TO US WILL GO ON OUR STATUS BOARD THAT A RELEASE IS REQUIRED. A CONTRIBUTING FACTOR ALSO WAS THAT THE FERRY PERMIT WAS SEVERAL PAGES BACK IN RELATION TO THE CURRENT PAGE IN THE LOGBOOK. ONLY THE CURRENT WRITE-UP IN THE LOGBOOK WAS FOCUSED UPON. SUPPLEMENTAL INFO FROM ACN 580281: I WAS INFORMED BY MAINT THAT I HAD FLOWN AN ACFT WITHOUT A PROPER AIRWORTHINESS RELEASE. THE AIRWORTHINESS RELEASE WAS NOT UPDATED; AND THAT THE PRESENT ONE WAS FOR A ONE TIME FLT ONLY.

More incidents for this aircraft family →

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