FTW95LA110 · Cessna 172M
Cessna 172M · Accident: overrun during takeoff
From 1V5 to 1V5 · CO
Event
- NTSB case
- FTW95LA110
- 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
- N80893
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 1V5To 1V5 · CO
- 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 › Rotation, premature
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT RELATED TO A FAA INSPECTOR THAT HE MADE A 'ROLLING TAKEOFF,' SLOWLY INCREASING POWER TO FULL THROTTLE. WHEN THE AIRPLANE ATTAINED AN INDICATED AIRSPEED OF 60 KNOTS, HE FELT THE AIRPLANE WAS NOT ACCELERATING RAPIDLY ENOUGH AND HE ABORTED THE TAKEOFF. HE APPLIED MAXIMUM BRAKING AND THE RIGHT MAIN TIRE BLEW OUT. THE AIRPLANE WENT OFF THE END OF THE RUNWAY, ACROSS THE RUNWAY OVERRUN, WENT DOWN AN EMBANKMENT, AND COLLIDED WITH A DITCH. IN HIS WRITTEN STATEMENT, HE REPORTED THAT AFTER TAKEOFF THE AIRPLANE 'HAD INSUFFICIENT POWER TO LEAVE GROUND EFFECT.' HE ALSO INDICATED THAT THERE WERE NO MECHANICAL MALFUNCTIONS.
Probable cause
THE PILOT'S PREMATURE ROTATION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW95LA110
- Event ID
- 20001207X02963
- Case number
- FTW95LA110
- 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: 941c82f7138ffbaf5319deae78998c58065b678f1c14945a94b21b8ea03541ba; retrieved 2026-09-23T00:16:28.148Z.