CEN24LA071 · Cessna 172N
Optima Aviation Cessna 172N · Accident: loss of control on ground during landing
From Aero Valley Airport (52F) to an unrecorded destination
Event
- NTSB case
- CEN24LA071
- 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
- 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 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
- N4501E
- Operator
- Optima Aviation
- Onboard fatalities
- Unknown
- Route
- From Aero Valley Airport (52F), Roanoke, TXTo not recorded
- Aircraft age
- About 45 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
- 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
- Loss of control on ground
- 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 oper/perf/capability
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot stated that when he entered the destination airport traffic pattern for landing, there were strong wind gusts that were not on the automated weather observing system report. He said the airplane’s descent during the approach was stable, so he decided to continue the approach for landing. He said that shortly after the airplane’s nose wheel landing gear touched down on the runway, the airplane caught a strong wind gust that resulted in a weathervane effect and a sharp change in its direction to the right. He then applied left rudder control input, but the airplane veered to the right and off the runway where it impacted terrain. The airplane sustained substantial damage to the fuselage. The pilot stated there was no preaccident failures or malfunctions the airplane that would have precluded normal operations.
Probable cause
The pilot’s failure to maintain directional control during landing that resulted in an impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA071
- Event ID
- 20231226193565
- Case number
- CEN24LA071
- 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, 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: 57aabbde154e4faf2dd24fc80d031830db4a2aae6c04f34bda05e9ba4f5be6f2; retrieved 2026-09-16T18:23:21.476Z.