Narrative:

On jun/mon/04, component change order CFM56-7b22 to cfm567b24 rating (upgrade the engine from 22K thrust to 24K thrust) was released to perform on aircraft due to an engine change. The document was placed on hold on jun/tue/04 pending the revision of work instructions. Revision #1 of the component change order was released on jun/fri/04. I was told verbally by manager of planning to place it on hold over the wkend to prevent planning from issuing. This would be the first time this document was issued to several stations. On jun/mon/04, I was extremely busy and I failed to remember to open the document back up. There was a scheduled engine change on aircraft #1's engine in ZZZ1. Due to the component change order being placed on hold, the document was not issued. I released the document on jun/tue/04 to planning. That afternoon, I was reminded that aircraft had an engine change on monday. I immediately looked in system to see if the document may have been added to the package and closed. I did not see anything. I then looked at the write-ups in system to see if a non routine card was written for the component change order. When I did not see any accomplishment of the component change order, I notified my manager and the manager of maintenance control of the possible intermix of the engines, looked to see where the aircraft was going to terminate. He stopped the aircraft in ZZZ1 at XA55 and the component change order to convert the engine was issued as well as the aircraft change order. FMC dip switch change in support of 24K thrust rating. The aircraft departed at XE35 and terminated in ZZZ2. I believe this event could have been prevented if documents did not have to be placed on hold to prevent issuing in lieu of tools currently in place that communicate requirements. These tools are system document information, and the document. However, I feel that regardless whether or not the document was open or on hold, the maintenance task card to remove and install the engine should be more specific to check both engines' data plate to confirm if it is 24K. It was not real clear how the mechanic was to verify the engines.

Related reports:

Google
 

Original NASA ASRS Text

Title: A MAINT PLANNER RPTS THAT AFTER COMPLETION OF A COMPONENT CHANGE ORDER TO UP-RATE B737 ENGS FROM 22K THRUST TO 24K THRUST, IT IS UNCLR HOW THE TECHNICIAN IS TO VERIFY THE ENG.

Narrative: ON JUN/MON/04, COMPONENT CHANGE ORDER CFM56-7B22 TO CFM567B24 RATING (UPGRADE THE ENGINE FROM 22K THRUST TO 24K THRUST) WAS RELEASED TO PERFORM ON ACFT DUE TO AN ENG CHANGE. THE DOCUMENT WAS PLACED ON HOLD ON JUN/TUE/04 PENDING THE REVISION OF WORK INSTRUCTIONS. REVISION #1 OF THE COMPONENT CHANGE ORDER WAS RELEASED ON JUN/FRI/04. I WAS TOLD VERBALLY BY MGR OF PLANNING TO PLACE IT ON HOLD OVER THE WKEND TO PREVENT PLANNING FROM ISSUING. THIS WOULD BE THE FIRST TIME THIS DOCUMENT WAS ISSUED TO SEVERAL STATIONS. ON JUN/MON/04, I WAS EXTREMELY BUSY AND I FAILED TO REMEMBER TO OPEN THE DOCUMENT BACK UP. THERE WAS A SCHEDULED ENG CHANGE ON ACFT #1'S ENG IN ZZZ1. DUE TO THE COMPONENT CHANGE ORDER BEING PLACED ON HOLD, THE DOCUMENT WAS NOT ISSUED. I RELEASED THE DOCUMENT ON JUN/TUE/04 TO PLANNING. THAT AFTERNOON, I WAS REMINDED THAT ACFT HAD AN ENG CHANGE ON MONDAY. I IMMEDIATELY LOOKED IN SYS TO SEE IF THE DOCUMENT MAY HAVE BEEN ADDED TO THE PACKAGE AND CLOSED. I DID NOT SEE ANYTHING. I THEN LOOKED AT THE WRITE-UPS IN SYS TO SEE IF A NON ROUTINE CARD WAS WRITTEN FOR THE COMPONENT CHANGE ORDER. WHEN I DID NOT SEE ANY ACCOMPLISHMENT OF THE COMPONENT CHANGE ORDER, I NOTIFIED MY MGR AND THE MGR OF MAINT CTL OF THE POSSIBLE INTERMIX OF THE ENGS, LOOKED TO SEE WHERE THE ACFT WAS GOING TO TERMINATE. HE STOPPED THE ACFT IN ZZZ1 AT XA55 AND THE COMPONENT CHANGE ORDER TO CONVERT THE ENG WAS ISSUED AS WELL AS THE ACFT CHANGE ORDER. FMC DIP SWITCH CHANGE IN SUPPORT OF 24K THRUST RATING. THE ACFT DEPARTED AT XE35 AND TERMINATED IN ZZZ2. I BELIEVE THIS EVENT COULD HAVE BEEN PREVENTED IF DOCUMENTS DID NOT HAVE TO BE PLACED ON HOLD TO PREVENT ISSUING IN LIEU OF TOOLS CURRENTLY IN PLACE THAT COMMUNICATE REQUIREMENTS. THESE TOOLS ARE SYS DOCUMENT INFO, AND THE DOCUMENT. HOWEVER, I FEEL THAT REGARDLESS WHETHER OR NOT THE DOCUMENT WAS OPEN OR ON HOLD, THE MAINT TASK CARD TO REMOVE AND INSTALL THE ENG SHOULD BE MORE SPECIFIC TO CHK BOTH ENGS' DATA PLATE TO CONFIRM IF IT IS 24K. IT WAS NOT REAL CLR HOW THE MECH WAS TO VERIFY THE ENGS.

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.