CREW OF MLG DEPARTS MKE WITHOUT ACFT LOGBOOK.

Date: 1999-07 · Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng · Phase: ground

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

Synopsis

CREW OF MLG DEPARTS MKE WITHOUT ACFT LOGBOOK.

Narrative

IN MILWAUKEE THE CAPTAIN REVIEWED THE ACFT MAINT LOGBOOK. COMPANY MAINT WAS FAXING A MECHANICAL ITEM. WE RETURNED TO THE ACFT AND ACCOMPLISHED CHKLIST; PAX STARTED BOARDING AND THE LOGBOOK WAS LEFT IN MAINT. IN CRUISE WE REALIZED THE LOGBOOK WAS NOT ONBOARD THE ACFT. WE CALLED DISPATCH AND HAD THEM FAX THE APPROPRIATE DOCUMENTS TO OUR NEXT STOP. THE CAPT HAD PERFORMED THE IN-SVC ACFT ACCEPTING CHK AND RELAYED THIS INFO TO ME IN MILWAUKEE BEFORE WE DEPARTED. WHEN WE ARRIVED AT OUR NEXT SCHEDULED STOP WE RECEIVED THE APPROPRIATE FAXES AND CONTINUED OUR TRIP. HUMAN NATURE CAME INTO PLAY WHEN WE GOT INVOLVED IN RUNNING CHKLIST AND FORGOT TO CONFIRM THE LOGBOOK WAS ONBOARD. DUE TO OUR COMPANY PROCS; LOGBOOKS ARE ROUTINELY REMOVED FROM THE ACFT WHEN MAINT IS CORRECTING MECHANICAL ITEMS. IN LIGHT OF THAT IT IS VERY POSSIBLE TO BE WAITING FOR THE MECHS AND GET SIDE-TRACKED WITH OTHER COMPANY PROCS. TO REMEDY THIS LIKELY SIT; THE LOGBOOK SHOULD NEVER LEAVE THE ACFT. AS A DOUBLE-CHK FOR THE FLC THE FIRST ITEM ON THE BEFORE START CHKLIST SHOULD BE 'LOGBOOK' WITH A RESPONSE BY BOTH CREW MEMBERS OF 'CHKED.'

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