Date: 201303
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Situational Awareness; Distraction
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Became Reoriented
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: We experienced a Thrust Instability Event (TIE) on climb. Having read recent safety reports on TIE's and discussed this at great length during my annual Quality Check; I had carefully studied and reviewed the Engine Limit/Surge/Stall checklist should this ever happen to me in flight. The TIE occurred about 30 miles from the expected handoff [on an overwater flight]. I accomplished the checklist correctly from memory to the point that we had a fully recovered engine; but before I could call for the checklist; the First Officer expressed concern with getting turned around before ATC wanted to hand us off to [Oceanic] Radio. The engine was running fine with no need to consider an engine shutdown (which would have then definitely driven us to the checklist); so I concentrated on advising the Company of our situation; coordinating with ATC; and notifying the cabin crew - planning to then pull the checklist out. After coordinating our course of action with the Company and reversing course with ATC; we were very close to our top of descent back to [departure station]. I briefed the planned approach; and as I called for the descent checklist with the intent to refer to the engine checklist afterwards; I asked the First Officer; 'Is there anything else you can think of; we need to do?' He then mentioned we should pull out the checklist. I didn't take the time to say that was my plan; instead; I asked him to read and call out the checklist and every required item had been correctly accomplished in accordance with the checklist. Though I was totally certain all checklist items were accomplished; and the checklist as planned was later pulled out for review after first 'flying the aircraft' for a return; 'Refer to the checklist' should have been done sooner.


Second narrative: After we got established back toward [departure airport] and we were reviewing the event I realized that we had not run the Engine Limit/Surge/Stall checklist from the QRH. I then asked for the QRH and completed the checklist. Due to my surprise and workload at the time of the event there was a delay in running the QRH checklist. Although the QRH preamble allows completing actions from memory; I would have been more comfortable having the QRH checklist drive the procedure. I will definitely in the future 'pause' and seek a checklist that is appropriate for the event to ensure proper procedures and demonstrate proper 'checklist discipline.'


Synopsis: B737-800 flight crew reported engine surge that drove a decision to return to departure airport. Workload caused a slight delay in running the checklists.