A B737-700 was dispatched with a logbook write-up not cleared or deferred. The logbook item was #2 b...

Attributes
ACN	713367
Time
Date	200610
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	ground : parked
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 221 flight time type : 18500
ASRS Report	713367
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 184
ASRS Report	713926
Events
Anomaly	aircraft equipment problem : critical maintenance problem : improper documentation non adherence : far non adherence : published procedure
Independent Detector	other other : 3
Resolutory Action	none taken : detected after the fact
Consequence	other other
Factors
Maintenance	contributing factor : schedule pressure contributing factor : work cards performance deficiency : scheduled maintenance performance deficiency : logbook entry performance deficiency : non compliance with legal requirements
Supplementary
Problem Areas	Chart Or Publication Maintenance Human Performance Company Environmental Factor Flight Crew Human Performance Aircraft
Primary Problem	Maintenance Human Performance

Narrative:

I departed ZZZ with an open write-up in the logbook. The aircraft had come from the hangar that morning. A mechanic had entered a discrepancy for #2 brake worn. The bottom of the logbook page was completed for position #2; tag no X; part number off xxy; serial number off Y; part number YYY; serial number west; and oil quantity added for both engines by the mechanic. However; the action taken block had not been signed off. When looking at the logbook I saw the above items below the type deferral block and must have considered the maintenance action complete. The matter was brought to my attention by the oncoming captain when I handed him the aircraft in ZZZ1 at the completion of my day. I called a ZZZ1 mechanic to come and assist me with the logbook write up. He called air carrier line maintenance who informed him that the aircraft brake repair had been done at the hangar. He then called the ZZZ hangar and was informed that (incredibly!) they already knew that an open write-up existed; and that since the aircraft was going to terminate in ZZZ2 that evening; they were going to facsimile the page to ZZZ2 and have them make an entry stating that the brake had been repaired. There was no consideration of informing the multiple crews who were going to fly the aircraft throughout the day; nor did the hangar personnel inform dispatch or maintenance control. Mine was an error of omission; theirs were errors of omission and commission. When we make a honest mistake; we must be proactive; admit our mistakes; and correct them at the soonest possible moment. On my part; I was tired from not getting a good night's sleep; which probably led to me missing the incomplete documentation. This is not the first time that I have discovered incomplete documentation with aircraft coming from the hangar. It is just the first time I did not catch the error before departure.

Original NASA ASRS Text

Title: A B737-700 WAS DISPATCHED WITH A LOGBOOK WRITE-UP NOT CLRED OR DEFERRED. THE LOGBOOK ITEM WAS #2 BRAKE WORN. THE BRAKE WAS ACTUALLY REPLACED PRIOR TO FLT BUT NOT SIGNED OFF.

Narrative: I DEPARTED ZZZ WITH AN OPEN WRITE-UP IN THE LOGBOOK. THE ACFT HAD COME FROM THE HANGAR THAT MORNING. A MECH HAD ENTERED A DISCREPANCY FOR #2 BRAKE WORN. THE BOTTOM OF THE LOGBOOK PAGE WAS COMPLETED FOR POS #2; TAG NO X; PART NUMBER OFF XXY; SERIAL NUMBER OFF Y; PART NUMBER YYY; SERIAL NUMBER W; AND OIL QUANTITY ADDED FOR BOTH ENGS BY THE MECH. HOWEVER; THE ACTION TAKEN BLOCK HAD NOT BEEN SIGNED OFF. WHEN LOOKING AT THE LOGBOOK I SAW THE ABOVE ITEMS BELOW THE TYPE DEFERRAL BLOCK AND MUST HAVE CONSIDERED THE MAINT ACTION COMPLETE. THE MATTER WAS BROUGHT TO MY ATTN BY THE ONCOMING CAPT WHEN I HANDED HIM THE ACFT IN ZZZ1 AT THE COMPLETION OF MY DAY. I CALLED A ZZZ1 MECH TO COME AND ASSIST ME WITH THE LOGBOOK WRITE UP. HE CALLED ACR LINE MAINT WHO INFORMED HIM THAT THE ACFT BRAKE REPAIR HAD BEEN DONE AT THE HANGAR. HE THEN CALLED THE ZZZ HANGAR AND WAS INFORMED THAT (INCREDIBLY!) THEY ALREADY KNEW THAT AN OPEN WRITE-UP EXISTED; AND THAT SINCE THE ACFT WAS GOING TO TERMINATE IN ZZZ2 THAT EVENING; THEY WERE GOING TO FAX THE PAGE TO ZZZ2 AND HAVE THEM MAKE AN ENTRY STATING THAT THE BRAKE HAD BEEN REPAIRED. THERE WAS NO CONSIDERATION OF INFORMING THE MULTIPLE CREWS WHO WERE GOING TO FLY THE ACFT THROUGHOUT THE DAY; NOR DID THE HANGAR PERSONNEL INFORM DISPATCH OR MAINT CTL. MINE WAS AN ERROR OF OMISSION; THEIRS WERE ERRORS OF OMISSION AND COMMISSION. WHEN WE MAKE A HONEST MISTAKE; WE MUST BE PROACTIVE; ADMIT OUR MISTAKES; AND CORRECT THEM AT THE SOONEST POSSIBLE MOMENT. ON MY PART; I WAS TIRED FROM NOT GETTING A GOOD NIGHT'S SLEEP; WHICH PROBABLY LED TO ME MISSING THE INCOMPLETE DOCUMENTATION. THIS IS NOT THE FIRST TIME THAT I HAVE DISCOVERED INCOMPLETE DOCUMENTATION WITH ACFT COMING FROM THE HANGAR. IT IS JUST THE FIRST TIME I DID NOT CATCH THE ERROR BEFORE DEP.

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

A B737-700 was dispatched with a logbook write-up not cleared or deferred. The logbook item was #2 brake worn. The brake was actually replaced prior to flight but not signed off.