Cessna 320F
NTSB investigations · 17
Matched to the registry by N-number and event date, newest first.
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.aircraft_model_code IN ('2074516')
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.aircraft_model_code IN ('2074516')
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun 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 WPR11LA292Accident · No injuriesLimited investigationFinal reportCessna 320F · Phoenix, AZThe mechanic's failure to properly secure the nose landing gear actuator push-pull tube to the landing gear door hinge clevis, which resulted in the gear jamming and not fully retracting after takeoff.NTSB CEN11LA307Accident · 1 fatalLimited investigationFinal reportCessna 320 · Lake Heron, NMThe pilot’s controlled flight into terrain while conducting a flight at low altitude in instrument meteorological conditions.NTSB NYC98LA070Accident · No injuriesLimited investigationFinal reportCessna 320F · Lincoln, METhe pilot's failure to maintain adequate altitude which resulted in left main landing gear contacting a snowbank during the landing approach.NTSB CHI91DEX03Accident · No injuriesFinal reportCessna 320F · Washington, INExceeding the aircraft's proper descent rate by the pilot in command. Factors related to the accident were inoperative runway edge lights, proper alignment not attained, improperly planned approach, and inadequate facility maintenance.NTSB DEN82FA056Accident · 3 fatalField investigationFinal reportCessna 320F · Missoula, MTDuring arrival for an ILS-2 approach to runway 11, the pilot was advised to hold at the kona NDB while snowplows finished clearing the runway. At that time, the Missoula weather was 1200 ft obscured, 2 mi visibility with light snow and fog, temperature and…NTSB FTW81FQA43Accident · No injuriesClosedCessna 320F · Ruidoso, NMNTSB FTW80FPG10Accident · No injuriesClosedCessna 320F · Little Rock, ARNTSB IAD79FA078Accident · No injuriesClosedCessna 320F · Chestertown, MDNTSB OAK78DXQ38Accident · No injuriesClosedCessna 320 · Mammoth Lakes, CANTSB ANC78FAA22Accident · Serious injuriesClosedCessna 320F · Galena, AKNTSB SEA76DYI10Accident · No injuriesClosedCessna 320F · Riley Junction, ORNTSB OAK74FVG39Accident · No injuriesClosedCessna 320F · Redding, CANTSB MKC73AK035Accident · 2 fatalClosedCessna 320F · Ashland, KSNTSB MKC72FCJ52Accident · No injuriesClosedCessna 320F · Omaha, NENTSB MKC70F0009Accident · No injuriesClosedCessna 320F · Eden Prairie, MNNTSB MIA69D0484Accident · No injuriesClosedCessna 320F · Ft Lauderdale, FLNTSB MIA69F0184Accident · Serious injuriesClosedCessna 320 · Pine Mountain, GA
Back to Cessna 320F