A B737-700 captain reports a logbook discrepancy caused by a MEL publication error.

Attributes
ACN	576218
Time
Date	200303
Day	Tue
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : yng.tower
Operator	common carrier : air carrier
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	ground : preflight ground : parked
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time total : 15000
ASRS Report	576218
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 200 flight time total : 12500 flight time type : 1600
ASRS Report	576217
Events
Anomaly	aircraft equipment problem : less severe maintenance problem : improper documentation non adherence : published procedure non adherence other
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	other
Factors
Maintenance	contributing factor : manuals performance deficiency : logbook entry
Supplementary
Problem Areas	Maintenance Human Performance Chart Or Publication Flight Crew Human Performance
Primary Problem	Chart Or Publication

Narrative:

Aircraft was received with MEL 28-17 fuel scavenger system. This MEL required compliance with special procedure 1 and special procedure 3 for all aircraft types. Special procedure 3 was not complied with. Dispatcher was contacted, and the call was conferenced with duty control. Duty control said that special procedure 3 did not apply, because 'the -700 does not have a connector.' I requested that the chief pilot on duty be contacted. He was called, and I discussed my concerns with him and the dispatcher. I felt that some reference to special procedure 3 was required. The chief pilot said that it was on 'MEL anomaly.' I was told to continue the flight. The first officer and I felt uncomfortable with this decision.

Original NASA ASRS Text

Title: A B737-700 CAPT RPTS A LOGBOOK DISCREPANCY CAUSED BY A MEL PUB ERROR.

Narrative: ACFT WAS RECEIVED WITH MEL 28-17 FUEL SCAVENGER SYS. THIS MEL REQUIRED COMPLIANCE WITH SPECIAL PROC 1 AND SPECIAL PROC 3 FOR ALL ACFT TYPES. SPECIAL PROC 3 WAS NOT COMPLIED WITH. DISPATCHER WAS CONTACTED, AND THE CALL WAS CONFERENCED WITH DUTY CTL. DUTY CTL SAID THAT SPECIAL PROC 3 DID NOT APPLY, BECAUSE 'THE -700 DOES NOT HAVE A CONNECTOR.' I REQUESTED THAT THE CHIEF PLT ON DUTY BE CONTACTED. HE WAS CALLED, AND I DISCUSSED MY CONCERNS WITH HIM AND THE DISPATCHER. I FELT THAT SOME REF TO SPECIAL PROC 3 WAS REQUIRED. THE CHIEF PLT SAID THAT IT WAS ON 'MEL ANOMALY.' I WAS TOLD TO CONTINUE THE FLT. THE FO AND I FELT UNCOMFORTABLE WITH THIS DECISION.

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.