FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24LA280 · Cessna 195A

19 Jul 2024 · Greenville, MI, United States

Cessna 195A · Accident: loss of control on ground during landing

From Cynthiana-Harrison County Airport (0I8) to an unrecorded destination

Report a problem

Event

NTSB case
CEN24LA280
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 195A

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
N1524D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Cynthiana-Harrison County Airport (0I8), Cynthiana, KYTo not recorded
Aircraft age
About 72 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
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
  • 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 upon landing the tailwheel equipped airplane swerved to the left and he applied right rudder and brake to correct. The airplane then ground looped to the right before coming to a stop. The pilot was able to taxi to parking. The pilot believed that the left tire of the airplane was flat which caused him to lose directional control of the airplane. The airplane received substantial damage to the fuselage. Examination of the runway revealed that skid marks were produced by both main landing gear tires at various times before the ground-loop occurred, and that the left tire was not flat until it was side-loaded during the event. The pilot did not submit the National Transportation Safety Board Pilot/Operator Aircraft Accident/Incident Report Form 6120.1.

Probable cause

The pilot’s loss of directional control during landing which led to a ground-loop.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24LA280
Event ID
20240723194750
Case number
CEN24LA280
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: e2807d23cf8cb2988e72b60bb90248983be702c06ebe8b9db845328f1efb0b0c; retrieved 2026-09-16T19:04:33.085Z.