FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA01LA086 · Cessna 152

25 Feb 2001 · Naples, FL, United States

Cessna 152 · Accident: loss of control on ground/water during landing

From Naples Municipal Airport (APF) to an unrecorded destination

Report a problem

Event

NTSB case
MIA01LA086
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

Cessna 152

Aircraft type
Cessna 152
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
N942AC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Naples Municipal Airport (APF), Naples, FLTo not recorded
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
Landing · flare/touchdown
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 on ground/water
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 › Directional control, not possible
  • Pilot in command › Recovery from bounced landing, improper

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

NTSB narrative

According to the student, he departed his home field in light and variable wind conditions on his fourth solo flight to practice his flight maneuvers. When he returned to the field to conduct landings, the wind had increased, and he was directed to a runway he was not familiar with. His landing flare resulted in a hard touchdown and bounce causing the aircraft to enter a porpoise maneuver that collapsed the nose landing strut. The aircraft departed the runway and sustained damage to the propeller, nose strut mount, and the firewall.

Probable cause

The student's failure to maintain control of the aircraft during landing due to his improper landing flare height and improper recovery from a bounced landing, resulting in a nose landing gear collapse, and excursion off the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA01LA086
Event ID
20010227X00514
Case number
MIA01LA086
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: 95943afa1f2faae38f2476972117b663138fff18b41bf499c4e7c91f0fdaab63; retrieved 2026-09-22T12:08:46.893Z.