Narrative:

Normal cruise, FL350, overheat detection light came on. #1 overheat light was illuminated. Complied with checklist, reduced power and descended. Light went out. After consulting with maintenance and increasing power on that engine, the light came back on and did not go out. We then complied with engine fire/severe damage and shut the engine down. After several mins and after discharging both bottles, the light went out. Landed in ZZZ single engine, otherwise uneventful. Callback conversation with reporter revealed the following information: the reporter noted the logbook had an entry for 'B' fire warning loop on #1 engine deferred as inoperative. The reporter does not have any information on the cause of the overheat and details on the fix.

Google
 

Original NASA ASRS Text

Title: A B737-300 IN CRUISE AT FL350 DECLARED AN EMER AND DIVERTED DUE TO L ENG OVERHEAT LIGHT ILLUMINATED. ENG SHUTDOWN. BOTTLES DISCHARGED.

Narrative: NORMAL CRUISE, FL350, OVERHEAT DETECTION LIGHT CAME ON. #1 OVERHEAT LIGHT WAS ILLUMINATED. COMPLIED WITH CHKLIST, REDUCED PWR AND DSNDED. LIGHT WENT OUT. AFTER CONSULTING WITH MAINT AND INCREASING PWR ON THAT ENG, THE LIGHT CAME BACK ON AND DID NOT GO OUT. WE THEN COMPLIED WITH ENG FIRE/SEVERE DAMAGE AND SHUT THE ENG DOWN. AFTER SEVERAL MINS AND AFTER DISCHARGING BOTH BOTTLES, THE LIGHT WENT OUT. LANDED IN ZZZ SINGLE ENG, OTHERWISE UNEVENTFUL. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR NOTED THE LOGBOOK HAD AN ENTRY FOR 'B' FIRE WARNING LOOP ON #1 ENG DEFERRED AS INOP. THE RPTR DOES NOT HAVE ANY INFO ON THE CAUSE OF THE OVERHEAT AND DETAILS ON THE FIX.

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.