FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN26LA092 · Cessna 172 N

7 Jan 2026 · San Marcos, TX, United States

US Aviation Academy Cessna 172 N · Accident during takeoff

From San Marcos Regional Airport (HYI) to San Marcos Regional Airport (HYI)

Report a problem

Event

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

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
N5136E
Onboard fatalities
Unknown
Route
From San Marcos Regional Airport (HYI), San Marcos, TXTo San Marcos Regional Airport (HYI), San Marcos, TX
Aircraft age
About 48 years (built 1978)
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
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

  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The flight instructor was going to demonstrate to the pilot receiving instruction, a short-field takeoff, with a simulated loss of engine power, as required per the flight school lesson plan. The flight instructor reported that he configured the airplane for the takeoff. Once the airplane had climbed to about 100 ft agl, he reduced the engine power to idle and began the descent back to the runway. The flight instructor noticed that the flight controls “seemed heavy” and the airplane was “descending fast.” The airplane landed hard on the runway and came to rest upright. The airplane taxied to the ramp without further incident, the airplane was shut down, and both occupants departed. The airplane sustained substantial damage to the fuselage. Postaccident examination of the airplane found the elevator trim was set to the full nose down position for the takeoff. The operator reported there were no preimpact mechanical malfunctions or failures with the airframe or the engine that would have precluded normal operation. The operator further reported that the accident could have been prevented if the flight instructor had adhered to the published maneuver procedure and profile, for the maneuver that was being demonstrated. The airplane’s before takeoff checklist includes a step to configure the elevator trim for the takeoff. The FAA Aviation Instructor’s Handbook FAA-8083-9B discusses checklists and states in part: Checklists are essential flight deck resources for verifying that the aircraft instruments and systems are checked, set, and operating properly, as well as ensuring that the proper procedures are performed if there is a system malfunction or inflight emergency.

Probable cause

The flight instructor’s failure to properly configure the elevator trim for the takeoff, that resulted in a hard landing. Contributing to the accident was the flight instructor’s failure to follow the before takeoff checklist.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN26LA092
Event ID
20260115202304
Case number
CEN26LA092
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, cause areas. 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: 0095572c12439e7ca99a822379e04e43794de77441937f2868fabdc578a540bf; retrieved 2026-09-16T20:40:41.135Z.