Energy Management at Venice
A slippery DA40, excess approach energy, and the decision to go around — runway excursion risk on a short final
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 13, a 5,640 ft asphalt runway. Elevation 18 ft MSL. You are on a solo instructional flight in a Diamond DA40, a composite, fuel-injected, constant-speed-prop airplane with a glass G1000 panel. The DA40 is known for its efficiency and clean aerodynamics — which means it floats on approach if energy is not managed precisely.
Conditions: VFR, clear skies, light winds from 160° at 4 knots. OAT 24°C. Visibility 10 SM. You have been flying the pattern for the past 20 minutes, practicing approaches. This is your third landing of the session. Your CFI is on the ground, observing.
You are on short final to Runway 13, 400 ft AGL, descending at 70 KIAS (Vref — approach speed). The runway is made. However, you notice the descent rate is shallower than expected — the airplane is floating. You are 1,200 ft down the runway and still 150 ft AGL. The DA40's slippery airframe and the light wind mean the airplane is not sinking as quickly as you anticipated. You have roughly 3,800 ft of runway remaining, but the float is eating into your margin.
Aircraft: Diamond DA40, solo, within limits. Fuel selector on LEFT tank (full). Constant-speed prop at 2,000 RPM. Flaps in landing configuration (full down). Trim set for approach. Nothing is broken; the airplane is flying normally — it is just floating.
Pilot: you — a Commercial pilot, current, roughly 350 hours total. You have 40 hours in the DA40. You are familiar with the airplane's tendency to float in light-wind conditions, but you have not yet developed the muscle memory to manage it consistently. This is a learning flight.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'DA40'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you already know about the DA40's approach and landing characteristics? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB GAA19CA582 (2019): A Diamond DA40 on an instructional flight experienced a loss of control during an aborted go-around when the pilot cut power and applied brakes with insufficient runway remaining. The pilot initiated a go-around from short final but did not have adequate runway distance to execute it safely. The probable cause was the pilot's decision to abort the go-around without adequate runway distance and his failure to accurately communicate his intentions to air traffic control.
NTSB ERA21LA039 (2020): A Diamond DA40 on a Part 91 supervised solo instructional flight lost directional control during landing when the aircraft bounced and drifted left. The student pilot's attempt to abort the landing was unsuccessful, and the aircraft struck a taxiway sign and cartwheeled before impacting a security fence. The probable cause was the pilot's loss of directional control while landing, which resulted in a runway excursion.
NTSB GAA19CA038 (2018): A Diamond DA40 flown by a solo student pilot experienced a runway excursion and struck a taxiway sign after landing with excessive speed. The accident was attributed to the student pilot's excessive taxi speed during a turn from the runway to a taxiway. The probable cause was the student pilot's excessive taxi speed during a turn from the runway to a taxiway, which resulted in a runway excursion and collision with a taxiway sign.
The common thread across all three accidents: the DA40's slippery airframe and efficient design mean it floats on approach in light-wind conditions. Pilots who do not manage energy aggressively — through prop RPM reduction, slips, or early go-around decisions — end up floating far down the runway. When the float is combined with a late go-around decision or a bounce on landing, a runway excursion is the result. The DA40 is a high-performance airplane; it demands precise energy management.
At KVNC, Runway 13 is 5,640 ft long — adequate for normal landings, but a go-around from short final with insufficient runway remaining is a runway excursion risk. The off-field environment at the Runway 13 departure end (heading 315°) is open water — a forced landing there would be a ditching. The off-field environment at the Runway 13 arrival end (heading 135°) is open field and built-up area — a runway excursion in that direction is a collision risk.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Venice Municipal Airport. KVNC has its own accident history (see field dominant patterns: 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 DA40 runway excursion events happened elsewhere. The scenario is localized to KVNC to make the runway length and off-field environment real and consequential for you as a student here.
The consistent lesson: in the DA40, energy management on approach is not optional. The airplane floats. Reduce prop RPM, enter a slip, or go around early — do not float the airplane down the runway hoping it will eventually touch down. The decision to go around must be made early enough to have adequate runway distance to execute it safely. A go-around from 50 ft AGL with 2,600 ft of runway remaining is an emergency procedure, not a normal go-around.
Key lesson — The DA40's composite airframe and clean design mean it floats significantly on approach in light-wind conditions. Manage energy aggressively: reduce prop RPM, enter a slip, or go around early. A go-around from short final must be initiated early enough to have adequate runway distance to execute it safely. At KVNC Runway 13 (5,640 ft), a late go-around or a float that extends the landing distance into the runway excursion zone is a real risk. Know the airplane's float characteristics and plan your energy management accordingly.
Debrief — teaching points
The DA40 floats — this is not a bug, it is a feature of the airframe design.
The DA40's composite construction and clean aerodynamic design make it efficient in cruise, but they also mean the airplane has low drag and floats on approach. In light-wind conditions, the DA40 can float 1,500+ ft down the runway if energy is not managed precisely. This is not a failure of the airplane or the pilot — it is the characteristic of a high-performance, efficient airframe. Expect it, plan for it, and manage energy aggressively to control it.
Vref is 70 KIAS — but that is the target speed, not a guarantee of descent rate.
Vref (70 KIAS) is the approach speed that minimizes float and maximizes descent rate. However, Vref alone does not guarantee a steep descent — especially in light-wind conditions. You must also manage prop RPM, flap configuration, and pitch attitude to control descent rate. If the airplane is floating at Vref, you need additional corrective action: reduce prop RPM, enter a slip, or go around.
Reduce prop RPM to increase drag and arrest float.
The DA40's constant-speed prop is a powerful tool for energy management on approach. Reducing RPM from 2,000 to 1,500 or 1,200 increases drag and descent rate. This is the first corrective action to try when the airplane is floating. Reduce RPM smoothly and monitor the descent rate. Once the descent rate is positive and the float is arrested, you can stabilize the approach.
A forward slip is a valid corrective action for float, but it requires precision.
A forward slip — cross-control ailerons and rudder — increases drag dramatically and steepens the descent. A slip is a valid corrective action for float, especially when the float is severe. However, a slip requires precise coordination to recover at the moment of touchdown. If you enter a slip, plan to recover the slip before touchdown and resume a normal landing attitude. Landing in a slip is possible but requires skill.
A go-around from short final must be initiated early enough to have adequate runway distance.
If the float threatens runway safety — if you are floating so far down the runway that you will not have adequate landing distance remaining — a go-around is the correct decision. However, the go-around must be initiated early enough to have adequate runway distance to execute it safely. A go-around from 400 ft AGL with 3,800 ft of runway remaining is safe. A go-around from 50 ft AGL with 2,600 ft of runway remaining is an emergency procedure. Make the decision early.
Increase prop RPM to full 2,700 RPM immediately on a go-around.
When you declare a go-around, advance the throttle to full power AND increase the prop RPM to full 2,700 RPM immediately. The constant-speed prop at 2,000 RPM reduces climb power. Full RPM maximizes climb power and ensures a safe departure from the landing area. Do not leave the prop at 2,000 RPM on a go-around — it will reduce your climb rate and margin.
Built from the real accident record
Scenario built from NTSB GAA19CA582 (2019 DA40 aborted go-around / runway excursion), ERA21LA039 (2020 DA40 loss of directional control / bounce on landing), and GAA19CA038 (2018 DA40 excessive speed landing). Anonymized and localized to KVNC.
NTSB reports: GAA19CA582 · ERA21LA039 · GAA19CA038
ACS tasks: PA.II.F — Approach and Landing · PA.II.G — Go-Around / Rejected Landing · PA.I.F — Weather Information · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
Relevant FARs: §91.3 · §91.13 · §91.103
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 DA40 scenarios · More scenarios at KVNC