Protocols for Handling Engine Surge and Stall Situations in Flight

Introduction to Engine Surge and Stall Events

Engine anomalies during flight rank among the most time-critical emergencies a pilot can face. While modern turbine and piston engines are highly reliable, surges and stalls remain real possibilities—especially in adverse weather, with improper throttle handling, or following mechanical degradation. Knowing the difference between these two events and having a rehearsed response is not optional; it is the foundation of safe single‑pilot and crew operations.

An engine surge typically manifests as a sudden, transient increase in thrust accompanied by loud bangs, vibrations, or backfires. It results from an imbalance in the airflow‑fuel mixture inside the compressor or combustor section. A stall, by contrast, means the engine can no longer sustain normal airflow through the compressor or turbine—or, in a broader aviation context, the wing has stalled. This article focuses specifically on engine stall (compressor stall) and surge, not aerodynamic stall, though the two can coexist in upset scenarios.

Distinguishing Surge from Stall

Engine Surge (Compressor Surge)

In a gas turbine engine, the compressor must deliver smooth, high‑pressure airflow to the combustion chamber. When the airflow separates from the compressor blades (often due to a sudden reduction in rotational speed or an upstream disturbance), the compressor can “surge.” This causes the engine to alternate between pumping and flowing, producing loud bangs and noticeable thrust fluctuations. Surge events can be self‑correcting if power is reduced immediately, but repeated surges can damage blades, seals, and bearings.

Compressor Stall

A compressor stall occurs when the airflow over the compressor blades becomes disrupted to the point that blade stalls occur across one or more stages. This can be triggered by foreign object damage, ice ingestion, high‑angle‑of‑attack flight, or rapid throttle movements. Unlike a surge, a stall may continue with a continuous grinding or howling noise and a loss of thrust. In some engines, a stall can lead to a full surge if the compressor fails to recover.

Why Terminology Matters

Pilots must use the correct checklist terminology because aircraft manufacturers often specify separate procedures for surge vs. stall. Treating a stall as a simple surge could delay critical steps such as shutting down the engine or initiating an in‑flight restart. Knowing what your engine instruments are telling you is the first line of defense.

Recognizing the Signs in the Cockpit

Before executing any protocol, the pilot must confirm the anomaly. Key indicators to monitor:

Exhaust Gas Temperature (EGT): A sudden spike followed by a drop often signals a surge. A sustained high EGT with reduced RPM suggests a stall.
RPM/Propeller Speed: Erratic RPM needle movement or a rapid decay points to a stall.
Engine Vibration: Low‑frequency vibration is typical of a surge; high‑frequency vibration may indicate mechanical failure.
Noise: Popping or banging sounds are classic surge cues. A continuous roar or rumble accompanied by power loss indicates a stall.
Fuel Flow: Fluctuating fuel flow can accompany a surge; stable high or low flow with no thrust response suggests a stall.

Note: In multi‑engine aircraft, the crew must also compare engine parameters side‑by‑side to detect an anomaly early.

Immediate Actions: The First 10 Seconds

Whether you face a surge or a stall, the initial steps follow a similar pattern. The highest priority is maintaining aircraft control, then protecting the engine from further damage.

1. Maintain Positive Aircraft Control

Fly the airplane first. Do not become absorbed in diagnosing the engine while the aircraft departs controlled flight. Set the attitude for the best single‑engine climb speed (if applicable) or for a safe glide. In most transport‑category aircraft, a pitch of 5° to 10° nose‑up with wings level is a good starting point. In a single‑engine aircraft, lower the nose to maintain above a target airspeed—typically best glide speed.

2. Reduce Throttle Smoothly

For a surge, reducing throttle to idle or near‑idle often stops the condition immediately. For a stall, a reduction in power can allow the compressor to stabilize. Never slam the throttle closed; a smooth reduction prevents a pressure shock that might worsen the situation. If the surge stops, you may be able to advance the throttle slowly and continue. If not, proceed to the stall procedure.

3. Identify the Specific Problem

Cross‑check instruments: Look for EGT spikes, RPM decay, vibrations, and audible cues. In multi‑engine aircraft, the failing engine will show asymmetric torque, N1, and N2. Use the engine trend monitoring system if available. Once confirmed, announce the condition: “We have a #2 engine surge – reducing power.”

Protocol for Engine Surge Recovery

Once you have reduced power and verified that it is a surge (and not a full stall or fire), attempt recovery using the following steps. These are based on generic best practices; always consult your aircraft’s flight manual.

Step 1 – Throttle to Idle: Hold idle for 10–15 seconds to allow the compressor to settle.
Step 2 – Monitor: Check if the surge stops. If EGT and RPM stabilise, slowly advance the throttle (1–2% per second) while watching for a repeat surge.
Step 3 – Reduce Aircraft Angle of Attack: If the surge was induced by high‑angle flight (e.g., during a go‑around or steep turn), reduce the angle of attack and ensure airflow is smooth into the intake.
Step 4 – Activate Continuous Ignition: If the engine relights automatically, keep the ignition on to stabilise combustion. Most turbine engines have a continuous ignition switch for this purpose.
Step 5 – If Surge Repeats: Retard the throttle again and consider reducing fuel flow to the affected engine (in multi‑engine operations). If repeated surges occur, shut the engine down to prevent catastrophic failure.

In some aircraft, the surge may be accompanied by an engine fire warning. In that case, follow the engine fire drill before attempting any surge recovery.

Protocol for Engine Stall (Compressor Stall)

A compressor stall often requires more aggressive action because the engine may be unable to sustain combustion. The following sequence applies to turbine engines. For piston engines, a different procedure is needed—usually a mixture adjustment and throttle setting check.

Throttle to Idle: Immediately reduce power to idle. This decreases the pressure differential across the compressor and may allow re‑establishing airflow.
Increase Airspeed: In most aircraft, pushing the nose down to accelerate helps increase airflow into the engine intake. Aim for a speed 20–30 knots above the normal approach speed if safe altitude permits.
Activate Starter (if permitted): In many turbine engines, engaging the starter while at idle can assist in re‑spooling the compressor. Check your flight manual; some engines prohibit this above certain altitudes.
Monitor for Relight: If the engine relights, you will see a rise in EGT and RPM. Keep the throttle at idle until the parameters stabilise, then slowly advance.
If Stall Persists: Shut down the engine by closing the fuel shutoff valve. Secure it according to the engine‑out checklist. Do not attempt repeated restart attempts at risk of a tailpipe fire or explosion.

In a multi‑engine aircraft, once the engine is secured, fly with the remaining engine(s) and proceed to the nearest suitable airport. Declare an emergency with ATC.

Engine Failure After a Surge or Stall

Sometimes a surge or stall degrades into a complete engine failure—either due to mechanical breakage, flameout, or damage to the turbine blades. The moment thrust is lost, transition to engine‑out procedures:

Verify the failure: Check RPM, EGT, fuel flow, and engine instruments for zero or decaying readings.
Apply the memory items from your aircraft’s engine failure checklist: e.g., fuel shutoff, generator off, feather the propeller (if applicable).
Begin the forced landing or diversion plan.
Communicate: Declare Mayday and provide position, remaining fuel, souls on board, and intentions.

For single‑engine aircraft, the focus shifts immediately to selecting a suitable landing site. Do not waste time troubleshooting if the engine cannot be restarted quickly.

Post‑Event Considerations

After successfully recovering from a surge or stall—or after shutting down an engine—your duties continue:

Park and Secure: Once on the ground, do not taxi the aircraft if the engine has been compromised. Shut down all engines and request a tow if needed.
Document the Event: Record all observed parameters, timing, and actions in the aircraft logbook or flight report. This is critical for maintenance troubleshooting.
Maintenance Inspection: Even if the engine appeared to recover fully, a thorough borescope inspection and performance run are required before the next flight. Surges and stalls can cause hidden blade cracks or seal damage.
Review and Debrief: Analyze why the event occurred—was it pilot technique (abrupt throttle movement), weather (icing or turbulence), or a mechanical issue? Use the experience to improve future handling.

Preventive Practices to Reduce Risk

The best way to handle an engine surge or stall is to avoid one. Incorporate the following habits into every flight:

Smooth Throttle Inputs: Avoid rapid power changes, especially at high altitude or in turbulence. Give the compressor time to spool.
Monitor Engine Trends: Log EGT, RPM, and fuel flow during cruise. A slow upward creep in EGT can signal an impending stall.
Avoid High‑AOA Engine Operations: During go‑arounds or low‑speed maneuvering, ensure the aircraft is not at an extreme nose‑high attitude while applying full power.
Anti‑Ice Systems: In icing conditions, use engine anti‑ice as recommended. Ice ingestion can trigger a surge or stall.
Pre‑Flight Care: Check intakes for foreign debris, damaged blades, and proper compressor case clearances. Any abnormal vibration during engine run‑up should be investigated before flight.

Training and Simulation Resources

Hands‑on practice in a simulator is invaluable. Many training organisations offer scenario‑based modules where pilots experience realistic surge and stall events. The FAA Airplane Flying Handbook provides foundational knowledge, while the AOPA Online Learning Center offers courses on engine management and emergency procedures. Additionally, the EASA Engine Training Guidelines cover European regulatory expectations for recognition and response.

Consider also reviewing manufacturer‑specific publications, such as the Pratt & Whitney PT6A Troubleshooting Guide or the Continental/Sky-Tech Engine Manuals, which contain detailed surge/stall recovery steps for popular engines.

Summary of Decision Flow

When any engine anomaly occurs, follow this mental flow:

Is the aircraft under control? If not – recover attitude and speed first.
Is it a surge, a stall, or a fire? Use instrument and auditory clues.
Reduce throttle to idle.
Evaluate: Does the condition clear? If yes – cautiously advance power. If no – proceed to engine stall procedure or engine shutdown.
Declare emergency, divert or land as needed.
After landing – preserve data, perform inspection, and debrief.

Every aircraft is different. The procedures above are generic and should never replace the specific checklist in your Pilot’s Operating Handbook (POH) or Flight Manual. Rehearse these steps in the simulator so that when a real surge or stall occurs, the response is automatic. Quick, precise action can save the engine—and the flight.