NTSB investigations: Cessna 120

7 cases on aircraft the registry lists as Cessna 120, where the first occurrence was “In flight collision with object”. 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.

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

19822026

NTSB investigations: Cessna 120 per year, 1982–2026: 7 cases
1982	1
1986	1
1988	1
1989	1
1991	1
1994	1
2001	1

Where

Open the map

Latest cases

Query with SQL

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 ('2071402') 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" = 220)) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

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 ('2071402')
      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\" = 220))
  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.

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 ('2071402')
    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" = 220))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

Run it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.

NTSB SEA01LA138Accident · Serious injuriesLimited investigationFinal reportCessna 120 · Troutdale, ORthe pilot's inadvertent visual flight rules ( VFR) flight into instrument meteorological conditions (IMC) during cruise flight. Factors include his attention being diverted to the indications presented by his Global Positioning System (GPS), and low ceiling…Jul 21, 2001 · N90077 · Destroyed NTSB BFO94LA039Accident · Serious injuriesLimited investigationFinal reportCessna 120 · Chittenango, NYThe pilot's inadequate planning/decision to take off with the presence of a tailwind.Feb 12, 1994 · N1626V · Substantial damage NTSB NYC91FA095Accident · 2 fatalField investigationFinal reportCessna 120 · Simsbury, CTThe pilot's intentional flight into terrain. Contributing to the accident were psychological conditions.Mar 21, 1991 · N4117N · Destroyed NTSB CHI89LA178Accident · Minor injuriesLimited investigationFinal reportCessna 120 · Brooklyn, MIFailure of the pilot to see-and-avoid power lines in his flight path during a go-around. The power lines and his lack of familiarity with the airport were contributing factors.Aug 31, 1989 · N2101V · Destroyed NTSB FTW88FA057Accident · Serious injuriesField investigationFinal reportCessna 120 · Ada, OKThe pilot was flying low up the river and hit the upper strand of a two strand high voltage power line. Both the pilot and passenger received serious injuries when the airplane crashed on a sand-bar in the river.Feb 10, 1988 · N2431N · Destroyed NTSB ATL86FA178Accident · 2 fatalField investigationFinal reportCessna 120 · Marlton, NJAbout 10 min after takeoff, the acft collided with trees & crashed while the plts were performing aerobatic maneuvers. According to witnesses, aerobatics were being performed at an about 500 ft AGL. They rprtd that the plts had made an overhead maneuver…Jun 21, 1986 · N89789 · Destroyed NTSB MKC82DA105Accident · No injuriesFinal reportCessna 120 · Gardner, KSDuring takeoff, the aircraft struck a fence near the departure end of the runway. After hitting the fence, it traveled about 37 yards before nosing over in an adjacent wheat field. The field was soft due to recent rains. The pilot said the 1300 ft runway was…Jun 17, 1982 · N1993V · Substantial damage