FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA99LA259 · Cessna 172N

19 Sept 1999 · MOONTOWN, AL, United States

Rocket Aviation Cessna 172N · Accident: overrun during takeoff

From M82 · Meridianville, AL to Moontown Airport (3M5)

Report a problem

Event

NTSB case
MIA99LA259
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 172N

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
N734TC
Onboard fatalities
Unknown
Route
From M82 · Meridianville, ALTo Moontown Airport (3M5)
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
Overrun
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 › Proper touchdown point, not attained
  • Pilot in command › Wrong runway, selected

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

NTSB narrative

After landing on runway 27, during a touch and go landing, the pilot stated there was not enough runway remaining to takeoff again. He aborted the takeoff, overran the runway, collided with a ditch, and nosed over. The wind at the Huntsville Airport, located about 16 miles southwest of the accident site, 27 minutes before the accident, were from 150 degrees at 9 knots.

Probable cause

The pilot's decision to land on a runway with a quartering tailwind, his failure to obtain the proper touchdown point on the runway, and his delay in aborting the takeoff phase of a touch and go landing, resulting in the aircraft overrunning the runway, colliding with a ditch, and nosing over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA99LA259
Event ID
20001212X19835
Case number
MIA99LA259
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: 56b82d0dc15fc5dda04a447729e3410e7de9366ca4171dfbda003bd91ee8c493; retrieved 2026-09-22T14:04:58.406Z.