A B737-300 had an autoplt mode control altitude alerting system deferred per MEL. Inbound crew descr...

Attributes
ACN	635045
Time
Date	200410
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : orf.tracon
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	ground : parked ground : maintenance
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	maintenance : technician other personnel other
Qualification	technician : powerplant technician : airframe
Experience	maintenance technician : 6
ASRS Report	635045
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	aircraft equipment problem : critical maintenance problem : non compliance with mel non adherence : far non adherence : published procedure
Independent Detector	aircraft equipment other aircraft equipment : mode control panel other flight crewa other flight crewb
Resolutory Action	aircraft : equipment problem dissipated none taken : detected after the fact
Consequence	other other
Factors
Maintenance	contributing factor : briefing performance deficiency : logbook entry performance deficiency : non compliance with legal requirements
Supplementary
Problem Areas	Chart Or Publication Flight Crew Human Performance Aircraft Maintenance Human Performance
Primary Problem	Maintenance Human Performance

Narrative:

Flight crew inbound into ZZZ had ACARS defect of 'altitude alert window on MCP inoperative on both autoplts and also with autoplts disengaged. Had continuous altitude warning going off in descent.' also noted that the 'altitude hold did capture during cruise flight.' after debriefing the inbound crew, it was felt that the problem was with the altitude alerting system. The discrepancy was deferred per the MEL. Discussed with the outbound crew, and they requested, when aircraft arrived in ZZZ1 that our maintenance folks see if they can fix problem before they head on to ZZZ2. I agreed with the crew and notified ZZZ1 of the problem coming in, and suggested having an MCP panel on hand in case it was required. After departed from ZZZ to ZZZ1 and flight crew sent me an ACARS message, noting that all indications were normal, no discrepancies as previously reported. I updated the current deferral with the crew's comments. Discussed problem with avionics technician in ZZZ1 and we both agreed if no problems were found during bite tests, that the deferral would be cleared and no need to replace the MCP panel. Later on the technician called back and informed me that there was an intermittent problem with the MCP altitude window changing from 10000 ft to FL500 without any power interruptions. He informed me that he tried a new panel and the intermittent problem was still present. After much deliberation, no relief was found in our MEL, for that problem that was now present. I had the aircraft grounded for this problem and a new write-up created to reflect the problem and the current deferral cleared, in order to avoid confusion on what the real problem may have been originally. Reviewing what occurred, I should have further questioned the original crew's discrepancy, in particular the comment of 'altitude alert window' this statement led me to believe the problem was associated with the altitude alert system, but then again on the ground in ZZZ neither crew reported the altitude window jumping to FL500 and outbound crew reported no problems.

Original NASA ASRS Text

Title: A B737-300 HAD AN AUTOPLT MODE CTL ALT ALERTING SYS DEFERRED PER MEL. INBOUND CREW DESCRIPTION OF DISPLAY WINDOW DEFECT INACCURATE.

Narrative: FLT CREW INBOUND INTO ZZZ HAD ACARS DEFECT OF 'ALT ALERT WINDOW ON MCP INOP ON BOTH AUTOPLTS AND ALSO WITH AUTOPLTS DISENGAGED. HAD CONTINUOUS ALT WARNING GOING OFF IN DSCNT.' ALSO NOTED THAT THE 'ALT HOLD DID CAPTURE DURING CRUISE FLT.' AFTER DEBRIEFING THE INBOUND CREW, IT WAS FELT THAT THE PROB WAS WITH THE ALT ALERTING SYS. THE DISCREPANCY WAS DEFERRED PER THE MEL. DISCUSSED WITH THE OUTBOUND CREW, AND THEY REQUESTED, WHEN ACFT ARRIVED IN ZZZ1 THAT OUR MAINT FOLKS SEE IF THEY CAN FIX PROB BEFORE THEY HEAD ON TO ZZZ2. I AGREED WITH THE CREW AND NOTIFIED ZZZ1 OF THE PROB COMING IN, AND SUGGESTED HAVING AN MCP PANEL ON HAND IN CASE IT WAS REQUIRED. AFTER DEPARTED FROM ZZZ TO ZZZ1 AND FLT CREW SENT ME AN ACARS MESSAGE, NOTING THAT ALL INDICATIONS WERE NORMAL, NO DISCREPANCIES AS PREVIOUSLY RPTED. I UPDATED THE CURRENT DEFERRAL WITH THE CREW'S COMMENTS. DISCUSSED PROB WITH AVIONICS TECHNICIAN IN ZZZ1 AND WE BOTH AGREED IF NO PROBS WERE FOUND DURING BITE TESTS, THAT THE DEFERRAL WOULD BE CLRED AND NO NEED TO REPLACE THE MCP PANEL. LATER ON THE TECHNICIAN CALLED BACK AND INFORMED ME THAT THERE WAS AN INTERMITTENT PROB WITH THE MCP ALT WINDOW CHANGING FROM 10000 FT TO FL500 WITHOUT ANY PWR INTERRUPTIONS. HE INFORMED ME THAT HE TRIED A NEW PANEL AND THE INTERMITTENT PROB WAS STILL PRESENT. AFTER MUCH DELIBERATION, NO RELIEF WAS FOUND IN OUR MEL, FOR THAT PROB THAT WAS NOW PRESENT. I HAD THE ACFT GNDED FOR THIS PROB AND A NEW WRITE-UP CREATED TO REFLECT THE PROB AND THE CURRENT DEFERRAL CLRED, IN ORDER TO AVOID CONFUSION ON WHAT THE REAL PROB MAY HAVE BEEN ORIGINALLY. REVIEWING WHAT OCCURRED, I SHOULD HAVE FURTHER QUESTIONED THE ORIGINAL CREW'S DISCREPANCY, IN PARTICULAR THE COMMENT OF 'ALT ALERT WINDOW' THIS STATEMENT LED ME TO BELIEVE THE PROB WAS ASSOCIATED WITH THE ALT ALERT SYS, BUT THEN AGAIN ON THE GND IN ZZZ NEITHER CREW RPTED THE ALT WINDOW JUMPING TO FL500 AND OUTBOUND CREW RPTED NO PROBS.

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.

A B737-300 had an autoplt mode control altitude alerting system deferred per MEL. Inbound crew description of display window defect inaccurate.