CEN26LA053 · Piper PA-22-108
Aerostyles Piper PA-22-108 · Accident: loss of control on ground during landing
From La Junta Municipal Airport (LHX) to City of Colorado Springs Municipal Airport (COS)
Event
- NTSB case
- CEN26LA053
- 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
Piper PA-22-108
- Aircraft type
- Piper PA-22
- 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
- N4588Z
- Operator
- Aerostyles
- Onboard fatalities
- Unknown
- Route
- From La Junta Municipal Airport (LHX), La Junta, COTo City of Colorado Springs Municipal Airport (COS), Colorado Springs, CO
- Aircraft age
- About 64 years (built 1961)
- 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 · flare/touchdown
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that during he felt a gust of wind from the left that lifted the left wing. The pilot stated that he overcorrected, the airplane became unstable, and he decided to perform a go-around. After the pilot initiated the go-around, the airplane veered to the right of the runway, struck a runway distance remaining sign, and then became airborne. The pilot reported that the elevator became jammed in a nose-up attitude after it struck the sign. The airplane reached an altitude of about 400 ft above ground level before the pilot regained control and returned to land without further incident. During the accident sequence, the airplane sustained substantial damage to the left wing strut, elevator, and horizontal stabilizer. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The pilot further reported that the accident could have been prevented if he had established better directional control before initiating the go-around.
Probable cause
The pilot’s failure to maintain directional control during the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN26LA053
- Event ID
- 20251201202076
- Case number
- CEN26LA053
- 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: 3e9c1c308cbfb0b8f68bf67b7c93df7404873cb6e7511757c0664c1b7180dd2f; retrieved 2026-09-16T20:34:38.963Z.