CEN26LA187 · Cessna 172S
US Aviation Academy Cessna 172S · Accident: flight control system malfunction/failure during takeoff
From an unrecorded airport to Mineral Wells Regional Airport (KMWL)
Event
- NTSB case
- CEN26LA187
- 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
- Ongoing
- Event fatalities
- Unknown
- 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 172S
- 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
- N2134M
- Operator
- US Aviation Academy
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Mineral Wells Regional Airport (KMWL), Mineral Wells, TX
- Aircraft age
- About 23 years (built 2003)
- 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
- 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
- Flight control system malfunction/failure
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On May 13, 2026, about 1815 central daylight time, a Cessna 172S, N2134M, sustained substantial damage when it was involved in an accident near Denton, Texas. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that during takeoff roll the airplane hit something on the runway (later determined to be a gas cap from another airplane) that caused the airplane to become airborne below normal rotation (Vr) speed. The pilot stated that he attempted to reduce airplane pitch by pushing the yoke in, but the yoke was stuck and would not move. The airplane drifted to the left which the pilot attempted to counter with aileron and rudder input. Since he was unable to lower the nose of the airplane, and he was only about 5 to 7 feet above the ground, he elected to reduce engine power and the airplane impacted the ground.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record CEN26LA187
- Event ID
- 20260514202991
- Case number
- CEN26LA187
- 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: 03f5a2e6fc676accb07dcbf4ee98ceb74f3ed41bb47f6df86f7118fe379c245e; retrieved 2026-09-16T21:28:40.948Z.