CHIEF WARRANT OFFICER 2 LOGAN M. BOULET
15th Military Intelligence Battalion
Fort Hood, Texas
In Army aviation, crew resource management (CRM) is not a buzzword; it is a combat multiplier. Aircraft systems can fail without warning, but disciplined communication, clearly defined roles and mutual trust between crew members are what prevent emergencies from becoming mishaps. CRM ensures that the workload is shared, decisions are deliberate and critical actions are executed without hesitation. In high-performance, multi-engine aircraft like the C-12, especially during time-critical phases of flight, survival often depends less on individual skill and more on how effectively the crew functions as a team.
During a routine standardization evaluation, a U.S. Army C-12 experienced a real-world single-engine failure during climb. The crew consisted of a pilot in command (PC) and a pilot (PI). The PI was on the controls, and the PC was monitoring. The mission brief was standard, and fuel samples taken immediately after refueling appeared normal —although later it was determined those samples were not taken in accordance with the technical manual.
After departure, the aircraft climbed through approximately 4,000 to 5,000 feet mean sea level, roughly 3,000 to 4,000 feet above ground level, in a standard tactical departure profile. The PC was heads-down momentarily changing frequencies when the first indication occurred: a noticeable yaw followed immediately by the auto-feather of the propeller. The PC looked up and observed the No. 1 torque rolling back. Almost simultaneously, the PI stated, “We lost the No. 1,” and moved his hand to the power levers.
The crew contacted air traffic control, declared an emergency and requested vectors for the instrument landing system. The decision to stay close to the departure airfield was deliberate. In a twin-engine aircraft, one failure raises the immediate question of reliability in the remaining engine. Extending away from the airport would have increased risk unnecessarily. The crew executed the approach and landed without further incident.
Fuel samples taken after landing showed clear evidence of contamination. Earlier samples had been taken immediately after fueling, which was not in accordance with the manual. Additionally, unknown at the time, the new contracted fuel supplier had not been using PRIST additive, leading to biological growth in the fuel system. This aircraft had also undergone two fuel control unit (FCU) replacements in the previous three months due to fuel flow indication problems. All other systems appeared stable, but the pattern should have triggered deeper concern.
The PC later reflected that the fuel had often appeared unusually yellow. However, this time the fuel was clear and looked more normal. When he initially questioned the color change during a previous departure, he was told the contract had changed. That response was accepted at the time. The lesson learned was clear: as a PC, diligence cannot stop at cockpit procedures. Oversight includes awareness of maintenance trends, recurring discrepancies and even fuel quality. If something doesn't look right, it likely isn't.
Initially, the PI believed the engine failure might be simulated, given the evaluation environment. However, the thoroughness of the pre-mission brief quickly removed any doubt. The crew had clearly discussed the exact sequence of events and how a real engine failure would be handled during departure. Because those expectations were established ahead of time, the PI was able to rapidly transition from thinking it was part of the evaluation to recognizing it as an actual emergency. That clarity prevented hesitation, reinforced role execution and allowed both pilots to respond immediately and professionally.
The focus of this event centers on three fundamentals: thorough pre-mission briefing, disciplined CRM and the responsibility of the PC to exercise diligence beyond the cockpit. A detailed brief that encourages questions and clearly defines expectations sets the conditions for decisive action when things go wrong. Effective CRM ensures that roles are understood and the workload is managed under pressure. At the same time, a PC’s responsibility extends beyond flying the aircraft. It includes maintaining awareness of maintenance trends, fuel quality and any factors that impact safety of flight.
What prevented this situation from escalating was not luck. It was strong crew coordination, disciplined execution of procedures, conservative decision-making and leadership that extended beyond the flight controls. The crew responded exactly as trained, and because of that, the aircraft landed safely on one engine.