FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA01LA200 · Cessna 182Q

28 Jul 2001 · Ocala, FL, United States

Cessna 182Q · Accident: on ground/water collision with object during takeoff

From Ocala, FL to St. Petersburg Clearwater International Airport (PIE)

Report a problem

Event

NTSB case
MIA01LA200
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 182Q

Aircraft type
Cessna 182
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
N78234
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ocala, FLTo St. Petersburg Clearwater International Airport (PIE), St Petersburg, 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
Takeoff · rejected takeoff
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
On ground/water collision with object
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 › Aborted takeoff, delayed
  • Pilot in command › Distance, misjudged
  • Pilot in command › Planning/decision, improper

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot said that there were five people on board the aircraft, and he was attempting a soft field takeoff but the aircraft was not accelerating in ground effect. He said that with about a third of the runway left, he believed that he could easily stop the aircraft, but when he applied the brakes the aircraft did not slow down, so he aimed for what looked like the lowest part of the fence ahead of him. He said he was about to pull the mixture, when he decided to add power and jump the fence instead, and the aircraft struck the fence with the undercarriage and tail, incurring substantial damage. According to the pilot, prior to the accident there had been no mechanical failure or malfunction to the aircraft or any of its systems.

Probable cause

the pilot's improper planning/decision and failure to properly judge takeoff distance, and his delayed decision to abort the takeoff, which resulted in the aircraft colliding with a fence at the end of the runway, and incurring substantial damage.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA01LA200
Event ID
20010813X01675
Case number
MIA01LA200
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. 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: c3fe544ca343513b7cd3480a65b19c1dec3a01f2ad8288707f9b4602f63464c4; retrieved 2026-09-22T11:42:40.600Z.