Night flying has always been where aviation feels the most honest. The distractions fall away, the wind calms, and the world below turns into a quiet, shimmering outline. I have always enjoyed teaching night flying for exactly that reason— students absorb more, stay focused, and experience precisely the kind of disciplined flying that makes them stronger pilots.
On January 6 during what should have been a routine night of full-stop pattern work at DeLand Municipal Airport (KDED) in Florida, that sense of calm evaporated in a single second. In the space between a normal climbout and the engine’s sudden silence, I went from instructor to emergency pilot executing the very decision we all hope we never have to make—the “impossible turn.”
If you’re not already a subscriber, what are you waiting for? Subscribe today to get the issue as soon as it is released in either Print or Digital formats.
I was flying with my student, practicing nighttime takeoff and landing procedures. We had already completed two full-stop patterns with no anomalies. Our Cessna 172 had approximately three hours of fuel remaining, an adequate amount of oil, and a perfectly normal run-up. The weather was calm, visibility unrestricted, and there was not a hint of trouble in the air.
On the third takeoff from Runway 5, as we climbed through roughly 450 feet agl, the engine gave a single, sharp cough—a noise I had never heard from this aircraft before. It wasn’t a gradual roughness, not a sputter, not a loss of rpm. Just one abrupt cough and then total silence.
- READ MORE: Pilot Peril: ‘Kenny’s Upside Down!’ the Voice Crackled Back
- READ MORE: Student Pilot Learns Value of Making Quick Decisions
The propeller wound down and stopped completely. Not windmilling, not rotating—slowly stopped. That alone is a chilling sight, especially at night.
In less than a second, my brain switched into emergency mode. I took control from the student, lowered the nose instantly to preserve glide speed, and ran the memorized flow—mixture full rich, fuel both, carb heat on, mags both. None of it mattered.
The throttle was jammed fully open. It wouldn’t move at all—frozen in place.
We were now a powerless, forward-gliding mass with only 450 feet of altitude and a black Florida night ahead of us.
A pilot’s choices in an EFATO (engine failure after takeoff) scenario are few and unforgiving. Straight ahead was darkness—huge dark forest, trees, obstacles. Turning shallowly to the downwind would not leave us enough altitude to complete a pattern.
The reciprocal runway—Runway 23—was directly behind us. Calm winds, a familiar airport layout, and no traffic in the pattern. If there was ever a moment where the impossible turn was possible, this was it. But it had to be immediate. No hesitation. No second-guessing.
I committed to the 180-degree turn.
I kept my bank angle controlled and smooth—no aggressive inputs, no overbanking that would risk a stall. The goal wasn’t speed. It was coordination and energy conservation. Slowly, the runway lights of 23 came into view, lined up like a lifeline against the dark background.
We rolled wings level with just enough altitude to flare and land. The propeller remained completely stationary throughout the descent. Touchdown was firm but controlled, and we rolled out entirely on rudder control, exiting onto the nearest taxiway before bringing the aircraft to a stop.
Only after stopping safely did the reality of what had happened settle in. That entire sequence—from power loss to rollout—lasted maybe 30 seconds. But in the moment it felt much longer.
Post-landing mechanical inspection confirmed what I already suspected. The throttle was found stuck in the open position with no available power. A broken valve had detached and fallen into the carburetor inside the engine. Neither magneto was producing a spark. The propeller was extremely difficult to rotate by hand, indicating probable internal engine seizure. Engine restart was not possible, especially at 450 feet. The failure was complete and unrecoverable.
While the flight ended safely, the learning didn’t stop on the runway.
In the days following the incident, I decided to file a report with NASA’s Aviation Safety Reporting System (ASRS). There had been no crash, no violation, and no official investigation requiring it, but I submitted the account as a precaution and part of responsible airmanship. Aviation safety relies heavily on shared information, and sometimes the smallest details can contribute to a larger understanding of risk.
Several weeks later, I received a written acknowledgment from NASA confirming the details of the report and documenting the event. Seeing the incident formally recorded was an interesting moment of reflection. It reinforced something many pilots hear early in training but don’t always fully appreciate until later in their careers—when in doubt, report.
Filing the ASRS report reminded me that aviation regulations and reporting systems are not designed to punish pilots. They exist to protect us and to improve the safety of the system. They provide a structured way for pilots to share experiences, highlight potential hazards, and contribute to collective learning within the aviation community.
For me, that became another lesson from this event. Emergencies don’t end when the airplane stops moving. Sometimes the most valuable learning occurs afterward—during the debrief, the maintenance inspection, and the reflection that follows.
For many pilots, the decision to turn back after an engine failure is one of the most debated topics in aviation safety. The “impossible turn” has earned its name for good reason—most attempted turnbacks end poorly. But emergencies aren’t academic. They aren’t theoretical case studies. They’re real, dynamic, and unforgiving.
The decision to turn back worked for several reasons. We had enough altitude—not much, but enough. The winds were calm. Runway geometry was favorable. Training and briefing reduced confusion. The turn was executed immediately and decisively.
I share this story not because everything went perfectly, but because it didn’t. Emergencies rarely unfold like the textbook diagrams. They require patience, judgment, decisiveness, and the ability to rely on training even when adrenaline is pumping.
That night reminded me that even as an experienced pilot and instructor with over 2,000 flight hours, aviation will always remain humbling. It demands respect. It demands preparation.
And sometimes, when everything goes wrong, it demands the impossible.
This column first appeared in the June Ultimate Issue 971 of the FLYING print edition.
