While enroute, flight crew discovered logbook maintenance item that had not been cleared prior to de...

Attributes
ACN	119229
Time
Date	198908
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : lmt
State Reference	OR
Altitude	msl bound lower : 26000 msl bound upper : 26000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zse
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	cruise other cruise other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 225 flight time total : 15000 flight time type : 3500
ASRS Report	119229
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Events
Anomaly	aircraft equipment problem : less severe non adherence : far other anomaly other
Independent Detector	other flight crewa
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

En route oak/sea second officer discovered logbook write-up which had not been cleared prior to our departure. None of our preflight materials, afpam, or aircraft maintenance history, indicated the write-up. In addition, no mention was made to our second officer when he met the crew. We called system aircraft maintenance (sam) and dispatch, neither of whom were aware of it. Sam deferred it 'ok to continue, 'antiskid inoperative for landing'.' contributing factors included: a new inbound second officer, write-up was 1ST item on new page which escaped our second officer's attention. Reliance north electronically generated maintenance information during flight planning has relegated the aircraft log to a secondary resource status, especially since no historical maintenance is displayed except on the very latest write-ups. Finally, short turn times, in this case about 20 mins block in to block out, compresses the workload of the second officer's well below the :45 mins contemplated by our SOP. In this case a good second officer simply missed the item and I personally failed to back up his review of the log. It won't happen again.

Original NASA ASRS Text

Title: WHILE ENROUTE, FLT CREW DISCOVERED LOGBOOK MAINTENANCE ITEM THAT HAD NOT BEEN CLEARED PRIOR TO DEP.

Narrative: ENRTE OAK/SEA S/O DISCOVERED LOGBOOK WRITE-UP WHICH HAD NOT BEEN CLRED PRIOR TO OUR DEP. NONE OF OUR PREFLT MATERIALS, AFPAM, OR ACFT MAINT HISTORY, INDICATED THE WRITE-UP. IN ADDITION, NO MENTION WAS MADE TO OUR S/O WHEN HE MET THE CREW. WE CALLED SYSTEM ACFT MAINT (SAM) AND DISPATCH, NEITHER OF WHOM WERE AWARE OF IT. SAM DEFERRED IT 'OK TO CONTINUE, 'ANTISKID INOP FOR LNDG'.' CONTRIBUTING FACTORS INCLUDED: A NEW INBND S/O, WRITE-UP WAS 1ST ITEM ON NEW PAGE WHICH ESCAPED OUR S/O'S ATTN. RELIANCE N ELECTRONICALLY GENERATED MAINT INFO DURING FLT PLANNING HAS RELEGATED THE ACFT LOG TO A SECONDARY RESOURCE STATUS, ESPECIALLY SINCE NO HISTORICAL MAINT IS DISPLAYED EXCEPT ON THE VERY LATEST WRITE-UPS. FINALLY, SHORT TURN TIMES, IN THIS CASE ABOUT 20 MINS BLOCK IN TO BLOCK OUT, COMPRESSES THE WORKLOAD OF THE S/O'S WELL BELOW THE :45 MINS CONTEMPLATED BY OUR SOP. IN THIS CASE A GOOD S/O SIMPLY MISSED THE ITEM AND I PERSONALLY FAILED TO BACK UP HIS REVIEW OF THE LOG. IT WON'T HAPPEN AGAIN.

Data retrieved from NASA's ASRS site as of August 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.

While enroute, flight crew discovered logbook maintenance item that had not been cleared prior to departure.