CEN22LA004 · Cessna 195 B
Cessna 195 B · Accident: system/component malfunction/failure (non-power) during landing
From Astronaut Kent Rominger Airport (RCV) to Colorado Air and Space Port (CFO)
Event
- NTSB case
- CEN22LA004
- 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 195 B
- Aircraft type
- Cessna 195
- 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
- N3027B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Astronaut Kent Rominger Airport (RCV), Del Norte, COTo Colorado Air and Space Port (CFO), Watkins, CO
- Aircraft age
- About 69 years (built 1952)
- 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
- System/component malfunction/failure (non-power)
- 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
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 he was landing from a personal flight in his tailwheel-equipped airplane when it suddenly swerved to the right shortly after the tailwheel contacted the runway surface during the landing roll. The pilot applied left rudder and brake to regain directional control, but the airplane veered off the right side of the runway into a level grass area. The left main landing gear (MLG) spring fractured where the spring entered the fuselage, which resulted in the airplane coming to rest on the lower left fuselage in a left wing down attitude. The left wing, left aileron, and the fuselage sustained substantial damage. Postaccident examination of the left MLG spring revealed a preexisting fatigue crack that initiated from the upper forward edge of the spring adjacent to the fuselage. The fatigue crack likely reduced the overall strength of the landing gear spring which resulted in its separation during the landing roll.
Probable cause
The separation of the left main landing gear spring during landing roll due to a preexisting fatigue crack.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA004
- Event ID
- 20211004104042
- Case number
- CEN22LA004
- 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: 6ebe6ae27197f41d414ad9056a5433eb967d077dd82fe62112bff48645ac49e5; retrieved 2026-09-16T14:37:37.887Z.