NTSB investigations: Cessna 195

22 cases on aircraft the registry lists as Cessna 195, where the first occurrence was “Loss of control - on ground/water”. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.

Cases per year

19832026
NTSB investigations: Cessna 195 per year, 1983–2026: 22 cases
19831
19852
19861
19871
19881
19902
19911
19931
19941
19952
19981
20011
20021
20031
20042
20051
20061
20071

Latest cases

Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
  FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
  WHERE c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073102')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 260))
  ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"

Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.

NTSB CHI07CA172Accident · No injuriesData collectionFinal reportCessna 195 · Battle Creek, MIThe pilot's failure to maintain directional control of the aircraft during the landing roll which resulted in a ground loop.Jun 19, 2007 · N4358V · Substantial damageNTSB SEA06CA132Accident · No injuriesData collectionFinal reportCessna 195 · Great Falls, MTThe pilot's loss of aircraft control during the takeoff roll, and the subsequent inadvertent ground loop.Jul 3, 2006 · N6857D · Substantial damageNTSB CHI05CA157Accident · Minor injuriesData collectionFinal reportCessna 195 · Peru, ILThe pilot not maintaining directional control during the landing and the ground loop he encountered.Jun 28, 2005 · N355ST · Substantial damageNTSB LAX04LA199Accident · No injuriesLimited investigationFinal reportCessna 195 · Riverside, CAthe pilot's failure to maintain directional control, resulting in a veer off the runway and collision with terrain.May 1, 2004 · N195AF · Substantial damageNTSB SEA04LA070Accident · No injuriesLimited investigationFinal reportCessna 195 · Everett, WAThe pilot's failure to maintain directional control of the aircraft as a result of a locked main gear brake during the landing roll. An inadvertent ground loop was a factor.Apr 17, 2004 · N127DD · Substantial damageNTSB FTW03CA205Accident · No injuriesData collectionFinal reportCessna 195 · Sand Springs, OKThe pilot's failure to maintain directional control during the landing roll.Aug 22, 2003 · N9882A · Substantial damageNTSB CHI02LA273Accident · No injuriesLimited investigationFinal reportCessna 195 · Shenandoah, IAThe pilot's inadequate compensation for wind, and the locked brake. A factor associated with the accident was the crosswind.Aug 30, 2002 · N4331N · Substantial damageNTSB IAD01LA085Accident · No injuriesLimited investigationFinal reportCessna 195 · Moultonboro, NHThe pilot's failure to maintain directional control of the airplane. A factor was the crosswind.Jul 24, 2001 · N4352V · Substantial damageNTSB CHI99LA015Accident · No injuriesLimited investigationFinal reportCessna 195 · Rugby, NDthe pilot failed to maintain directional control.Oct 26, 1998 · N1003D · Substantial damageNTSB FTW95LA403Accident · No injuriesLimited investigationFinal reportCessna 195 · Moriarty, NMthe pilot's inadequate compensation for the winds. A factor was the crosswind.Sep 24, 1995 · N4494C · Substantial damageNTSB LAX95LA084Accident · No injuriesLimited investigationFinal reportCessna 195 · Phoenix, AZthe failure of the left main strut due to a pre-existing crack.Jan 22, 1995 · N195JB · Substantial damageNTSB FTW94LA066Accident · No injuriesLimited investigationFinal reportCessna 195 · Watkins, COThe loss of directional control by the pilot rated passenger. A factor was inadequate supervision by the pilot in command.Jan 10, 1994 · N9355A · Substantial damageNTSB SEA93LA163Accident · No injuriesLimited investigationFinal reportCessna 195 · Pray, MTThe PIC failed to maintain directional control. A factor relating to the accident was the tailwind weather condition.Jul 27, 1993 · N9836A · Substantial damageNTSB CHI91LA190Accident · No injuriesLimited investigationFinal reportCessna 195 · Detroit, MIFailure to maintain directional control, and inadequate aircraft preflight. A factor related to the accident is the instructor pilot's lack of experience in the type aircraft.Jun 13, 1991 · N4351V · Substantial damageNTSB FTW91LA015Accident · No injuriesLimited investigationFinal reportCessna 195 · N. Little Rock, ARThe failure of the right brake system to release after application for unknown reasons.Nov 18, 1990 · N4320V · Substantial damageNTSB MKC90LA058Accident · No injuriesLimited investigationFinal reportCessna 195 · Garden City, KSDirectional control not maintained by the pilot in command.Mar 1, 1990 · N4332V · Substantial damageNTSB NYC88LA070Accident · No injuriesLimited investigationFinal reportCessna 195 · Meriden, CTAfter performing several touch and go landings, the student pilot made a landing right of the center line. The aircraft drifted to the right, struck a snowbank, sheared off the left main landing gear, then groundlooped. The aircraft came to rest on the grass…Jan 31, 1988 · N1077D · Substantial damageNTSB DEN87LA239Accident · Minor injuriesLimited investigationFinal reportCessna 195 · Colorado Sprgs, COThe plt stated that after he lndd to pick up a pax, he engaged the control lock fm habit, but did not shut dwn the eng. He got clnc to taxi back to the rwy & takeoff, but 'forgot to release control lock.' The Cessna 195 has a combination control lock and…Sep 25, 1987 · N3006B · Substantial damageNTSB LAX86LA306Accident · No injuriesLimited investigationFinal reportCessna 195 · Ramona, CAThe aircraft owner stated that the purpose of the flight was to obtain 5 hours of transition training in the tail dragger and accomplish a bfr. After departure the CFI had the pilot perform airwork maneuvers enroute to the Ramona area. The pilot said that a…Jul 28, 1986 · N3899V · Substantial damageNTSB ATL85LA133Accident · No injuriesLimited investigationFinal reportCessna 195 · Lexington, KYDuring ldg roll-out the plt applied brake press in order to turn onto the taxiway & the rt brake grabbed causing the acft to ground loop. The left landing gear spring strut separated from the fuselage attachment point.Apr 12, 1985 · N4408C · Substantial damageNTSB LAX85LA237Accident · No injuriesLimited investigationFinal reportCessna 195 · Tucson, AZThe student lost control & ground looped the acft during rollout from the fifth landing while practicing for his bfr. The CFI reported that the accident might have been prevented had he been more attentive and/or provided better supervision.Apr 6, 1985 · N4331N · Substantial damageNTSB LAX84LA081Accident · No injuriesLimited investigationFinal reportCessna 195 · El Cajon, CAThe pilot stated that the acft veered to the right during landing. The pilot tried left brake with no success. The acft groundlooped and the left gear failed. The brakes were examined after the accident but due to the damage to the lines & and fittings no…Nov 29, 1983 · N9335A · Substantial damage