|
Getting your Trinity Audio player ready...
|

As a C-130H instructor pilot, I train new crew members for the Air National Guard, Air Force Reserve, and our foreign partners.
As a C-130H instructor pilot with the Arkansas Air National Guard, I train new crew members—pilots, flight engineers, navigators, and loadmasters—for the Air National Guard, Air Force Reserve, and our foreign partners. We often fly the C-130H in challenging conditions, including at night on NVGs, in formation in the weather, and using electronic systems to maintain precise position. It’s a great job, and I enjoy teaching and mentoring new aviators in the art and science of tactical airlift.
One August night I was flying lead of a two-ship formation out of Little Rock AFB. We were in IMC, descending from 6,000 to 4,000 feet on our route to the drop zone, followed by an instrument recovery back to base. In my aircraft were a student pilot, a student loadmaster, a brand-new flight engineer, and an experienced navigator. It was a solid training mix for all of us.
As we leveled at 4,000 feet, I felt a slight surge from the right side of the aircraft. It was subtle, but distinct. It passed, and then returned. Concurrently, the tone of the engines shifted—a tell-tale sign of a fluctuating propeller RPM. The flight engineer confirmed the number 3 prop was fluctuating about 1.5%, which was over the 0.5% limit set in our manual.
The student pilot in the right seat spoke up: “That’s one of our shutdown conditions.”
“Yes it is,” I replied. “But let’s take this slow.”
In the Air Force we are taught from day one to approach emergencies with a standardized response. The acronym MATL is ingrained in every pilot’s mind. It stands for Maintain Aircraft Control, Analyze the Situation, Take Proper Action, and Land as soon as Conditions Permit. The challenge is staying disciplined when the workload spikes.
That night, the MATL acronym proved as valuable as ever.
Maintain Aircraft Control
Flying the airplane comes first. I confirmed we were stable at 4,000 ft, trimmed, maintaining 210 knots. Instruments were steady, and the aircraft was flying ok despite the surging propeller. Only once that box was ticked did I move to the next step.
Analyze the Situation
This wasn’t a simple engine malfunction. I was leading formation, in the weather, with student crewmembers and a wing-ship also full of students, about to perform a drop. Shutting down an engine was absolutely the right call, but doing so in formation IMC, at that point in the mission, added layers of complexity: formation separation, training continuity, and teaching value.
It became a real opportunity to teach: we could allow our wingman to continue the drop while we dealt with the emergency and returned to base, preserving the training value for the students in the other aircraft.
“Okay,” I told the crew, “we’re going to break up the formation and shut down number 3. Co-pilot, execute the engine shutdown checklist for number 3.”
I radioed our wingman: “Two, we’re shutting down our number 3 engine for an emergency. I’ll coordinate for you to descend to 2,000 ft and assume the callsign for the drop. I’ll handle our return individually.”
“Two,” they acknowledged.
Take Proper Action
With tasks assigned, the co-pilot and flight engineer began the shutdown procedure on engine number 3. I scanned the “six-pack,” adjusted pitch, and set trim to maintain 4,000 ft with the loss of one engine. Once again: keep control.
Next, I contacted Little Rock Approach, declared our emergency and our plan, and requested clearance. My wingman descended to 2,000 ft for the drop, while I returned direct to base at 4,000 ft under a new squawk and callsign. Formation separation complete. Now we focused individually.
“Cleanup complete, sir,” the flight engineer reported. “That’s my first actual shutdown!”
“Mine too,” added the co-pilot.
Re-Analyze & Plan
Now that the engine was secured, I took a moment to reassess: number 3 instruments were all zeros, condition lever fully back at feather, fire handle out, no agent discharged. The transponder was set with a new squawk, and the flight ID displayed our new callsign. Everything properly set.
“Pilot, we can turn east and set up for the ILS to runway 25,” the navigator suggested.
“Good idea. Co-pilot, let Approach know we’re ready for vectors to the ILS.”
We turned east into the “dead” engine. That’s not inherently dangerous, but you must respect the aerodynamics and always stay above two-engine minimum control speed (VMC). I set power and trim accordingly.
We briefed the one-engine-out approach, systems impacted, when to configure, and emergency egress if needed. By final vector onto the localizer, everyone knew the plan.
Land as Soon as Conditions Permit
We broke out around 800 ft AGL, the approach lights and runway emerged ahead. The landing was smooth. We taxied clear without incident. We’d made a stressful problem almost a non-event by taking our time.
During the debrief I walked the students through our actions using MATL:
-
Maintain Aircraft Control – we held off distractions and flew the airplane.
-
Analyze the Situation – we took the time to consider mission, formation, crew, and weather.
-
Take Proper Action – we executed the procedure, coordinated with ATC, and kept our wingman on task for the mission.
-
Land as Soon as Conditions Permit – we prioritized a safe, deliberate recovery.
This simple four-step framework kept a complicated, high-workload emergency from escalating. It also reinforced effective crew resource management by assigning tasks according to position and experience, keeping communication open, and maintaining situational awareness.
The student pilot told me later that talking about emergencies and performing them in the simulator is one thing, but watching it in real time means something else entirely. That’s the kind of training payoff instructors hope for.
Key takeaways
Emergencies don’t come in slow motion. They arrive with noise, distraction, and urgency. The difference between chaos and control often comes down to task prioritization—and a simple, reliable framework:
-
Maintain aircraft control.
-
Analyze the situation before acting.
-
Take deliberate, proper action.
-
Land when it’s safe.
That night this simple acronym and systematic approach to an emergency worked. The airplane came home safely, both crews learned something valuable, and a new generation of tactical airlifters saw how calm professionalism turns an emergency into a lesson worth remembering.
- Task Prioritization in a C-130H Emergency - January 19, 2026
- When Special VFR Is the Right Call - October 1, 2025





This strictly-GA (sailplane-only/former-)pilot agrees with the USAF’s MATL approach…and successfully put it to use (long before encountering the “MATL” acronym) in the wake of a similarly-subtle/repeating event occurring on a “soft soaring day” when ~3,000′ directly above my takeoff airport. The symptom was a “very-slight, weird-fishlike-wriggle” never-before-felt in the glider in which I had ~1500 hours. Had it occurred on a stronger day, hindsight suggests it wouldn’t have been separable – then, but not later – from routine thermic turbulence. The first occurrence was a “Was that real?” mental event. Re-occurring soon thereafter provided the “Yup” confirmation. Other than that the ship was acting entirely normally, so (M)aintaining A/C control wasn’t an issue. Without intending false dramatics, two choices existed: proceed more-or-less directly to a landing attempt on the field directly beneath, or bail out. (Parachutes are routinely worn by sailplane pilots; non-contest types (me) view them in the same light as seatbelts….potentially immensely useful, but unlikely ever to be needed, since fewer operator-controlled risks exist, flying vs.driving.) Obviously(?) my preference was to land the ship, but (A)nalyzing possible causes of the wriggle raised some alarming (to me, anyway) possibilities, the least-worst being a rudderless approach and landing. My working conclusion settled eventually upon rudder flutter as the most-likely wriggle-source, which in fact it proved to be. This suggested (T)aking a proper course of action included attempting (L)anding. Fortunately pattern conditions proved benign (almost zero crosswind), and after a larger-/higher-than-normal approach, minimizing need for rudder inputs, routine touchdown ensued, the by-now-constant fluttering ceasing during the roundout. Subsequent inspection revealed a failing weld in a rudder bell-crank connecting rudder pedal cables to the rudder actuation pushrod.
Depending upon aircraft structural material (metal, wood, composites), and driving energy (speed), flutter can range from “immediately catastrophic” to “merely alarming.” I was fortunate on all fronts: low-speed; fiberglass ship (“overstrong” – for stiffness/flutter-prevention-reasons!); least-critical control surface; benign conditions aloft. Some pre-existing knowledge surrounding “the flutter situation” was also (hugely!) beneficial…
Thanks for sharing. Methodical and logical thought can help bring clarity to a potentially emotional event. Great job landing the sailplane.