FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA07LA053 · Piper PA-28-181

25 Feb 2007 · Venice, FL, United States

Piper PA-28-181 · Accident: loss of control in flight on approach

From Venice Municipal Airport (KVNC) to Venice Municipal Airport (KVNC)

Report a problem

Event

NTSB case
MIA07LA053
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA-28-181

Aircraft type
Piper PA-28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N2213Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Venice Municipal Airport (KVNC), Venice, FLTo Venice Municipal Airport (KVNC), Venice, FL
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR go-around
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Airspeed, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The student pilot performed four landings with his certified flight instructor (CFI), then departed on a solo flight remaining in the traffic pattern. He performed two go-arounds, departed the traffic pattern, then returned for a full-stop landing on runway 13. The wind velocity had increased but he continued his approach. The airplane drifted left of centerline, and he added full power to perform a go-around. The airplane stalled when the flight was at 50 feet, descended left wing low, and impacted the ground. The student pilot further reported there was no mechanical failure or malfunction.

Probable cause

The failure of the student pilot to maintain airspeed during a go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA07LA053
Event ID
20070313X00283
Case number
MIA07LA053
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: d6a8f51b91bf254c0fda551e7552b81be3bbb52a82337f64233de658e05706c6; retrieved 2026-09-21T08:50:41.403Z.