Engine Failure on Climb — Venice Municipal
Total power loss in a fuel-injected trainer over open water and residential terrain — forced landing site selection and execution under pressure
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 04, climbing out on a 045° heading. Elevation 18 ft MSL. The runway is short and narrow — 5,000 ft of asphalt — and the departure environment off the north end (Runway 04) is open water: the Gulf of Mexico and coastal wetlands. Off the south end (Runway 22) is residential development and open fields.
It is a clear, calm Florida morning: OAT 22°C, altimeter 29.98, light winds from the south. Visibility 10 SM. You are flying a Diamond DA20-C1 — a light, slippery composite trainer with a fuel-injected Continental IO-240, fixed gear, fixed-pitch prop, and a single fuel tank with an ON/OFF selector. The DA20 is responsive and efficient, but it is unforgiving of fuel mismanagement: there is no left/right tank selection, no fuel crossfeed, no redundancy. The fuel tank is either ON or OFF.
You are 600 ft AGL, climbing through 75 KIAS (Vy), heading 045°, when the engine begins to lose power. The RPM is dropping. The engine is not running rough — it is simply dying. You have roughly 30 seconds of useful decision time before altitude becomes critical. The water of the Gulf is ahead and below. Residential areas and small fields are to your left and right.
Aircraft: Diamond DA20-C1, solo, 1,400 lb loaded weight (within limits). Fuel tank selector is ON. You did a preflight fuel check — you saw fuel in the tank. You did not measure it with a dipstick; you visually confirmed the sight glass. The engine was started and run-up was normal. Nothing was written up.
Pilot: you — a Private pilot, current, roughly 250 hours total. You departed KVNC on a local flight with no specific destination — a 'local area flight' to practice slow flight and steep turns. You did not file a flight plan. You did not brief an alternate. You did not calculate endurance. You assumed the fuel was sufficient for a local flight.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'DA20'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you already know about engine failure in the DA20-C1? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR23LA324 (2023): A Diamond DA20 on an instructional flight lost total engine power during a simulated engine failure when the student advanced the throttle with the mixture leaned. The pilot made a forced landing off-airport. The probable cause was improper fuel management and failure to follow the engine failure checklist. The flight instructor did not follow the airplane's checklist.
NTSB GAA19CA569 (2019): A Diamond DA20 experienced total engine power loss on approach due to fuel exhaustion after four flights in one day. The pilot made a forced landing on a service road between buildings and struck a tree, sustaining substantial damage. The probable cause was improper preflight fuel planning that led to fuel exhaustion.
NTSB ERA19LA074 (2018): A Diamond DA20 on a post-maintenance test flight experienced partial engine power loss during climb due to debris obstructing the metering plug orifice in the throttle and metering unit. The pilot made a forced landing to a clearing, impacting trees. The probable cause was a partial loss of engine power due to debris obstructing the metering plug orifice.
NTSB ERA19LA029 (2018): A Diamond DA20 experienced partial engine power loss during cruise flight and made a forced landing in a field. The probable cause was multiple discrepancies in the engine's ignition system, including worn magnetos and damaged ignition harnesses.
NTSB CEN16LA018 (2015): A Diamond DA20-C1 on a personal night flight made a forced landing in a field after total engine failure due to fuel exhaustion. The probable cause was the pilot's decision to operate the airplane without the owner's permission and inadequate preflight planning.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Venice Municipal Airport. KVNC has its own accident history (LOSS_OF_CONTROL_INFLIGHT 24.4%, FORCED_LANDING 12.2%, SPATIAL_DISORIENTATION 12.2%, HARD_LANDING 12.2%, LOSS_OF_CONTROL_GROUND 12.2%), but these specific DA20 engine-failure events happened elsewhere. The scenario is localized to KVNC to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: the DA20-C1 has a single fuel tank with an ON/OFF selector. There is no left/right tank management, no fuel crossfeed, and no redundancy. Fuel exhaustion is the dominant cause of engine failure in this type. Improper preflight fuel planning — visual fuel checks without dipstick measurement, 'local flights' without endurance calculation, and multi-flight days without fuel accounting — is the root cause in most accidents. The second-most-common cause is post-maintenance debris or ignition system discrepancies that are not caught by a thorough preflight.
Off Runway 04 at KVNC, the off-field environment is open water — the Gulf of Mexico and coastal wetlands. An engine failure on the Runway 04 departure at low altitude is a ditching, not a field landing. The DA20's bubble canopy is a liability in water: egress is difficult and water ingress is rapid. A controlled ditching is survivable only if executed correctly — flaps down for slowest touchdown speed, canopy unlatched, master off before impact, and immediate egress.
Key lesson — The DA20-C1's single fuel tank and ON/OFF selector make fuel management a quantity-only issue — but that issue is critical. Fuel exhaustion is the dominant cause of engine failure in this type. A complete preflight fuel check requires a dipstick measurement, not a visual sight-glass check. A 'local flight' still requires an endurance calculation and a fuel plan. Off Runway 04 at KVNC, the off-field environment is open water — a forced landing there is a ditching, not a field landing. Establish best glide (73 KIAS) immediately, scan for a landing site, and execute the approach cleanly. If the airport is reachable, make it your target. If not, a field landing in the residential area south of the airport is safer than a water landing.
Debrief — teaching points
Fuel exhaustion is the dominant cause of engine failure in the DA20-C1.
The DA20-C1 has a single fuel tank with an ON/OFF selector. There is no left/right tank management, no fuel crossfeed, and no redundancy. Fuel exhaustion is the only fuel-related failure mode. A complete preflight fuel check requires a dipstick measurement — not a visual sight-glass check. The sight glass can be misleading; a dipstick measurement is the only way to know actual fuel quantity and to detect contamination. A 'local flight' still requires an endurance calculation. Know your fuel burn rate (typically 5.5–6.5 GPH in cruise), calculate endurance, and plan for a 30-minute reserve minimum.
Best glide in the DA20-C1 is 73 KIAS — establish it immediately on engine failure.
The DA20-C1 is a light, slippery airplane. Best glide is 73 KIAS at gross weight. This speed maximizes glide distance and gives the most time to assess options and execute a forced landing. At 600 ft AGL with best glide, you have roughly 5–6 minutes of glide time. Use that time to establish the glide, scan for a landing site, and plan the approach. Do not waste time trying to restore power; if the engine is failing, accept the failure and manage the forced landing.
Off Runway 04 at KVNC, the off-field environment is open water — a ditching, not a field landing.
The off-field environment off Runway 04's departure end (heading 045°) is open water — the Gulf of Mexico and coastal wetlands. There is no alternate landing surface. An engine failure on the Runway 04 departure at low altitude is a ditching. The DA20's bubble canopy is a liability in water: egress is difficult and water ingress is rapid. A controlled ditching is survivable only if executed correctly: flaps down for slowest possible touchdown speed (impact energy rises with the square of speed), canopy unlatched before water contact, master off just before impact, and immediate egress. Know this before you line up on Runway 04.
The turn-back decision at low altitude is marginal — know your limits.
At 600 ft AGL, a 180° turn back to the airport is feasible in the DA20-C1, but it is marginal. The turn consumes altitude rapidly. At 400 ft AGL, the turn is tight and leaves little margin for error. If the engine is failing and altitude is low, consider landing in a nearby field or open area rather than committing to a turn back to the airport. A field landing in the residential area south of KVNC is safer than a water landing or a failed turn-back attempt.
Flaps are critical in a forced landing — use full flaps for slowest touchdown speed.
In a forced landing, the dominant value of full flaps is the slowest possible touchdown speed. Impact energy rises with the square of speed; a 10 KIAS reduction in touchdown speed significantly reduces impact energy. In a field landing, full flaps (78°) will increase the descent rate slightly, but the touchdown speed will be minimized. In a water landing (ditching), full flaps is even more critical — the slowest possible touchdown speed is the difference between survival and a fatal impact. Add full flaps as the landing site is made and slow to Vref (55 KIAS) for approach.
Built from the real accident record
Scenario built from NTSB WPR23LA324 (2023 DA20 fuel mismanagement / engine failure on climb), GAA19CA569 (2019 DA20 fuel exhaustion / forced landing), ERA19LA074 (2018 DA20 partial power loss / post-maintenance), ERA19LA029 (2018 DA20 ignition system failure), CEN16LA018 (2015 DA20 fuel exhaustion / night forced landing), and CEN15WA043 (2014 DA20 power loss / forced landing). Localized to KVNC.
NTSB reports: WPR23LA324 · GAA19CA569 · ERA19LA074 · ERA19LA029 · CEN16LA018 · CEN15WA043
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors · PA.II.B — Engine Starting / Systems Preflight
Relevant FARs: §91.3 · §91.13 · §91.185
Step through the full decision tree, make the calls, and see where each choice leads — then debrief it with your CFI.
Open the interactive scenario →All sample scenarios · More Diamond DA20-C1 scenarios · More scenarios at KVNC