B737-300 dispatch release incorrect when omitting the MEL'ed item in logbook at cmh, oh.

Attributes
ACN	521320
Time
Date	200108
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : cmh.airport
State Reference	OH
Altitude	agl single value : 0
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-300
Flight Phase	ground : maintenance
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer
Experience	flight time last 90 days : 150 flight time total : 11000 flight time type : 5000
ASRS Report	521320
Events
Anomaly	aircraft equipment problem : less severe non adherence : far non adherence : company policies other anomaly other
Resolutory Action	none taken : detected after the fact
Consequence	other
Supplementary
Problem Areas	Company Flight Crew Human Performance Aircraft
Primary Problem	Flight Crew Human Performance

Narrative:

First officer informs me 25 mins prior to push that the left front navigation light is inoperative and I call maintenance. They arrive 20 mins prior to push to replace bulb. Maintenance returns mins later to inform me they cannot replace bulb but can defer it, (shift change). Maintenance does the write-up and returns logbook to cockpit and informs me that maintenance control knows of problem and will 'get it down-line.' I checked the logbook entry, the first officer started a new page and we depart for cmh. Arrived on time at cmh where I received dispatch release for flight's next leg to ZZZ1. The dispatch did not include the current MEL item (navigation lights) and I did not catch it. Maybe because of the new logbook page or maybe the sticker was out of view (regardless I did not catch it). I departed cmh with an inaccurate release. After landing ZZZ1 and receiving paperwork for flight ZZZ1 to ZZZ2 I realized my error when I got my first copy of the MEL text. The cmh-ZZZ1 leg did not include the text. I called dispatch to inform them of the oversight. Then I called ZZZ chief pilot and related the information to him. He advised me to file this report. I'll never depart again without first speaking to maintenance and dispatch in person, to get the release amended.

Original NASA ASRS Text

Title: B737-300 DISPATCH RELEASE INCORRECT WHEN OMITTING THE MEL'ED ITEM IN LOGBOOK AT CMH, OH.

Narrative: FO INFORMS ME 25 MINS PRIOR TO PUSH THAT THE L FRONT NAV LIGHT IS INOP AND I CALL MAINT. THEY ARRIVE 20 MINS PRIOR TO PUSH TO REPLACE BULB. MAINT RETURNS MINS LATER TO INFORM ME THEY CANNOT REPLACE BULB BUT CAN DEFER IT, (SHIFT CHANGE). MAINT DOES THE WRITE-UP AND RETURNS LOGBOOK TO COCKPIT AND INFORMS ME THAT MAINT CTL KNOWS OF PROB AND WILL 'GET IT DOWN-LINE.' I CHKED THE LOGBOOK ENTRY, THE FO STARTED A NEW PAGE AND WE DEPART FOR CMH. ARRIVED ON TIME AT CMH WHERE I RECEIVED DISPATCH RELEASE FOR FLT'S NEXT LEG TO ZZZ1. THE DISPATCH DID NOT INCLUDE THE CURRENT MEL ITEM (NAV LIGHTS) AND I DID NOT CATCH IT. MAYBE BECAUSE OF THE NEW LOGBOOK PAGE OR MAYBE THE STICKER WAS OUT OF VIEW (REGARDLESS I DID NOT CATCH IT). I DEPARTED CMH WITH AN INACCURATE RELEASE. AFTER LNDG ZZZ1 AND RECEIVING PAPERWORK FOR FLT ZZZ1 TO ZZZ2 I REALIZED MY ERROR WHEN I GOT MY FIRST COPY OF THE MEL TEXT. THE CMH-ZZZ1 LEG DID NOT INCLUDE THE TEXT. I CALLED DISPATCH TO INFORM THEM OF THE OVERSIGHT. THEN I CALLED ZZZ CHIEF PLT AND RELATED THE INFO TO HIM. HE ADVISED ME TO FILE THIS RPT. I'LL NEVER DEPART AGAIN WITHOUT FIRST SPEAKING TO MAINT AND DISPATCH IN PERSON, TO GET THE RELEASE AMENDED.

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