MIA99LA207 · Cessna 172M
Aviation Training Associates Cessna 172M · Accident during landing
From Orlando Sanford International Airport (SFB) to Orlando Sanford International Airport (SFB)
Event
- NTSB case
- MIA99LA207
- 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 172M
- Aircraft type
- Cessna 172
- 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
- N9880V
- Operator
- Aviation Training Associates
- Onboard fatalities
- Unknown
- Route
- From Orlando Sanford International Airport (SFB), Sanford, FLTo Orlando Sanford International Airport (SFB), Sanford, 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
- Landing
- 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
- Miscellaneous/other
- 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(cfi) › Aborted takeoff, delayed
- Pilot in command(cfi) › Proper touchdown point, not attained
- Pilot in command(cfi) › Touch-and-go, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was conducting dual flight instruction and had just completed a short field landing, continued the rollout, and transitioned to a soft field take off, when he noticed the engine was not producing full power and he felt he was not going to make it. The pilot further stated that there was a lack of acceleration so he aborted the takeoff, but the wheels locked on the wet grass and the aircraft overan the runway. Examination by an FAA inspector after the accident showed that the airplane landed long, with about 1,300 feet of the 2,800 foot turf runway remaining. Postcrash running of the engine by the FAA inspector revealed that the engine developed power in accordance with the Cessna pilot operating handbook, and showed no defects.
Probable cause
the flight instructor's (pilot in command) failure to achieve the proper touch down point, his improper decision to continue the touch and go, and failure to abort the takeoff in sufficient time, resulting in the aircraft overrunning the runway and colliding with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99LA207
- Event ID
- 20001212X19323
- Case number
- MIA99LA207
- 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: 5433e4081140f71c948a0cf2e94a7aa73ff9abcb8ea3511ee9531d590340c08f; retrieved 2026-09-22T14:22:08.203Z.