FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14CA023 · Cessna 172R R

10 Oct 2013 · Tomball, TX, United States

Cessna 172R R · Accident: collision during takeoff/landing

From David Wayne Hooks Memorial Airport (DWH) to David Wayne Hooks Memorial Airport (DWH)

Report a problem

Event

NTSB case
CEN14CA023
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 172R R

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
N999UF
Operator
Unknown
Onboard fatalities
Unknown
Route
From David Wayne Hooks Memorial Airport (DWH), Tomball, TXTo David Wayne Hooks Memorial Airport (DWH), Tomball, TX
Aircraft age
About 15 years (built 1998)
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 · landing roll
Defining eventThe 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
Collision during takeoff/landing
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

  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The solo student pilot was performing a touch-and-go landing and touched down too far down the runway. The student pilot trimmed the airplane, raised the flaps and advanced the throttle for takeoff. He became unsure of the runway distance remaining so he reduced the throttle to idle and applied the brakes to abort the takeoff. The brakes locked up several times while he kept the airplane on the runway centerline. Realizing the airplane was not slowing enough, the student pilot lowered the airplane's flaps to 30 degrees and pushed forward on the control yoke to add drag and decrease lift. The airplane slowed, but not enough to stop it from going off the end of the runway and impacting trees. The student pilot reported that there were no mechanical malfunctions or failures with the airplane prior to the accident.

Probable cause

The student pilot delay in aborting the takeoff which resulted in the airplane going off the end of the runway and impacting trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14CA023
Event ID
20131028X32032
Case number
CEN14CA023
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 0d0f9f16f41a59dd170efb5cd0010f8de1d6beb99e44e77655dafe8b8341690c; retrieved 2026-09-15T23:02:10.871Z.