Narrative:

Dec/wed/02, a B767-200 aircraft departed ZZZ airport bound for los angeles. On taxi out, the crew experienced an EICAS message 'right engine eec probe,' the indication light was also illuminated. There was one previous occurrence of this fault registered in the aircraft history. The crew contacted my office through a commercial radio patch. As the aircraft was on the ground, it was decided to attempt a circuit breaker reset in order to clear the message and light. This proved unsuccessful. The crew reported that the fault was intermittent. It was, therefore, decided to defer the item per the MEL. I looked for the reference which I subsequently passed to the crew. The reference I gave them was MEL 3034F. This reference indicated no restrs with 1 inoperative per engine. The item was entered into the aircraft log via computer. The information was sent to the aircraft printer and the flight proceeded to depart. As I entered my log record and rechked the problem, I realized that I had given the incorrect MEL reference. I went through the problem again looking at all the available information and found I had used the incorrect page of the MEL to give the flight crew. My first reaction was to inform the dispatcher of the problem, as with the correct reference there were a number of flight restrs to be applied. I then informed the crew by ACARS traffic of my mistake. The correct MEL reference should in fact be 3034B. The dispatcher worked on the required flight plan issues and the crew had replied to me that the system had in fact operated without fault since takeoff. Which is indeed fortunate, however, the incorrect MEL reference was applied by me to the situation. The item was assigned to maintenance department for subsequent resolution. The system did in fact operate without fault for the trip.

Google
 

Original NASA ASRS Text

Title: A B767-200 WAS DISPATCHED IN NON COMPLIANCE WITH AN ENG ELECTRONIC PROBE DEFERRED INCORRECTLY USING THE WRONG MEL REF.

Narrative: DEC/WED/02, A B767-200 ACFT DEPARTED ZZZ ARPT BOUND FOR LOS ANGELES. ON TAXI OUT, THE CREW EXPERIENCED AN EICAS MESSAGE 'R ENG EEC PROBE,' THE INDICATION LIGHT WAS ALSO ILLUMINATED. THERE WAS ONE PREVIOUS OCCURRENCE OF THIS FAULT REGISTERED IN THE ACFT HISTORY. THE CREW CONTACTED MY OFFICE THROUGH A COMMERCIAL RADIO PATCH. AS THE ACFT WAS ON THE GND, IT WAS DECIDED TO ATTEMPT A CIRCUIT BREAKER RESET IN ORDER TO CLR THE MESSAGE AND LIGHT. THIS PROVED UNSUCCESSFUL. THE CREW RPTED THAT THE FAULT WAS INTERMITTENT. IT WAS, THEREFORE, DECIDED TO DEFER THE ITEM PER THE MEL. I LOOKED FOR THE REF WHICH I SUBSEQUENTLY PASSED TO THE CREW. THE REF I GAVE THEM WAS MEL 3034F. THIS REF INDICATED NO RESTRS WITH 1 INOP PER ENG. THE ITEM WAS ENTERED INTO THE ACFT LOG VIA COMPUTER. THE INFO WAS SENT TO THE ACFT PRINTER AND THE FLT PROCEEDED TO DEPART. AS I ENTERED MY LOG RECORD AND RECHKED THE PROB, I REALIZED THAT I HAD GIVEN THE INCORRECT MEL REF. I WENT THROUGH THE PROB AGAIN LOOKING AT ALL THE AVAILABLE INFO AND FOUND I HAD USED THE INCORRECT PAGE OF THE MEL TO GIVE THE FLC. MY FIRST REACTION WAS TO INFORM THE DISPATCHER OF THE PROB, AS WITH THE CORRECT REF THERE WERE A NUMBER OF FLT RESTRS TO BE APPLIED. I THEN INFORMED THE CREW BY ACARS TFC OF MY MISTAKE. THE CORRECT MEL REF SHOULD IN FACT BE 3034B. THE DISPATCHER WORKED ON THE REQUIRED FLT PLAN ISSUES AND THE CREW HAD REPLIED TO ME THAT THE SYS HAD IN FACT OPERATED WITHOUT FAULT SINCE TKOF. WHICH IS INDEED FORTUNATE, HOWEVER, THE INCORRECT MEL REF WAS APPLIED BY ME TO THE SIT. THE ITEM WAS ASSIGNED TO MAINT DEPT FOR SUBSEQUENT RESOLUTION. THE SYS DID IN FACT OPERATE WITHOUT FAULT FOR THE TRIP.

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.