Narrative:

Equipment arrived ZZZ with the flight data recorder on placard which required a fix or an attempt to fix per MEL 31-2 to 737. After a discussion with technician it was decided to try and reload the flight data acquisition unit since ZZZ1 tried and failed, maybe we might be successful. Our ramp tower was advised of the problem, but was told go ahead and board we might have a fix. Meantime, avionics was gathering some procedures together to reload the flight data acquisition unit. When they arrived at the gate with the software, the plane was off the gate and gone. Technical service was advised and a no fix/no fly was assigned to the aircraft on its return from ZZZ2.

Google
 

Original NASA ASRS Text

Title: A B 737-800 WAS DISPATCHED IN NON COMPLIANCE WITH THE FLT DATA RECORDER DEFERRED PER MEL. STATION DID NOT ADHERE TO REQUIREMENT OF MUST FIX FIRST STATION WHERE REPAIRS OR REPLACEMENTS AVAILABLE.

Narrative: EQUIP ARRIVED ZZZ WITH THE FLT DATA RECORDER ON PLACARD WHICH REQUIRED A FIX OR AN ATTEMPT TO FIX PER MEL 31-2 TO 737. AFTER A DISCUSSION WITH TECHNICIAN IT WAS DECIDED TO TRY AND RELOAD THE FLT DATA ACQUISITION UNIT SINCE ZZZ1 TRIED AND FAILED, MAYBE WE MIGHT BE SUCCESSFUL. OUR RAMP TWR WAS ADVISED OF THE PROB, BUT WAS TOLD GO AHEAD AND BOARD WE MIGHT HAVE A FIX. MEANTIME, AVIONICS WAS GATHERING SOME PROCS TOGETHER TO RELOAD THE FLT DATA ACQUISITION UNIT. WHEN THEY ARRIVED AT THE GATE WITH THE SOFTWARE, THE PLANE WAS OFF THE GATE AND GONE. TECHNICAL SVC WAS ADVISED AND A NO FIX/NO FLY WAS ASSIGNED TO THE ACFT ON ITS RETURN FROM ZZZ2.

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.