FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA00LA144 · Cessna 152

4 May 2000 · Sanford, FL, United States

Comair Aviation Academy Cessna 152 · Accident: on ground/water collision with object while taxiing

From Orlando Sanford International Airport (SFB) to an unrecorded destination

Report a problem

Event

NTSB case
MIA00LA144
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
0
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
N92995
Onboard fatalities
Unknown
Route
From Orlando Sanford International Airport (SFB)To 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
Taxi · to runway
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

  • Dual student › Visual lookout, improper
  • Pilot in command(cfi) › Supervision, inadequate

Approximate · Estimated position: the centre of Sanford, FL, the place the record names. Not the accident site.

NTSB narrative

The flight instructor stated that the student was taxiing the airplane and he was preoccupied looking at a problem with the low voltage light. He said that he had noticed that the airplane was being taxied fast, was to the left of the centerline, and close to a fence. He said he took over the controls, applied the brakes, retarded the throttle, and applied right rudder, but could not avoid the collision. The left wing of the airplane collided with the fence, and the airplane incurred substantial damage. The student said that he was looking at the right wing trying to see if he was clear of parked airplanes when the wing hit the fence.

Probable cause

the dual student's improper visual lookout and the flight instructor's inadequate supervision that resulted in the airplane colliding with a fence post.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA00LA144
Event ID
20001212X21061
Case number
MIA00LA144
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: db4b07fabbd91543a94ef34a5d74171da74085f63576df3b225d46e0e978bd27; retrieved 2026-09-22T12:55:31.859Z.