Fatal NTSB investigations: Cessna 525

8 cases on aircraft the registry lists as Cessna 525. 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

19982026
Fatal NTSB investigations: Cessna 525 per year, 1998–2026: 8 cases
19981
19991
20001
20071
20081
20161
20182

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.\"highestInjuryLevel\" = 'Fatal'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2076601', '2076653'))
  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 CEN18FA326Accident · 1 fatalField investigationFinal reportCessna 525 · Payson City, UTThe pilot's intentional flight into his residence.Aug 13, 2018 · N526CP · Substantial damageNTSB ERA18FA127Accident · 1 fatalField investigationFinal reportCessna 525 · Crozet, VAThe pilot's loss of control while operating in night instrument meteorological conditions as a result of spatial disorientation. Contributing to the accident was the pilot's decision to operate an airplane after consuming alcohol and his resulting…Apr 16, 2018 · N525P · DestroyedNTSB WPR16FA054Accident · 2 fatalField investigationFinal reportCessna 525 · Cedar Fort, UTThe pilot's loss of control due to spatial disorientation while operating in instrument meteorological conditions, which resulted in an exceedance of the airplane's design stress limitations, and a subsequent in-flight breakup. Contributing to the accident…Jan 18, 2016 · N711BX · DestroyedNTSB MIA08MA051Accident · 2 fatalMajor investigationFinal reportCessna 525 · West Gardiner, METhe pilot's spatial disorientation and subsequent failure to maintain airplane control.Feb 1, 2008 · N102PT · DestroyedNTSB LAX07MA069Accident · 2 fatalMajor investigationFinal reportCessna 525 · Van Nuys, CAThe pilot's failure to maintain an adequate airspeed during the initial climb resulting in an inadvertent stall/spin. Contributing to the accident were the second pilots inadequate preflight, failure to properly secure the front baggage door, and the front…Jan 12, 2007 · N77215 · DestroyedNTSB FTW00FA103Accident · 1 fatalField investigationFinal reportCessna 525 · Buda, TXthe pilot's inadequate in-flight decision to continue a visual approach in instrument meteorological conditions which resulted in his failure to maintain terrain clearance. Contributing factors were the fog, drizzle, and low ceilings.Mar 26, 2000 · N130MR · DestroyedNTSB CHI00FA040Accident · 6 fatalField investigationFinal reportCessna 525 · Branson, MOthe pilot descended below the minimum altitude for the segment of the GPS approach. Factors relating to the accident were low ceilings, rain, and pilot fatigue.Dec 9, 1999 · N525KL · DestroyedNTSB ATL98FA060Accident · 5 fatalField investigationFinal reportCessna 525 · Marietta, GAThe failure of both pilots to see and avoid conflicting traffic, and the failure of the 172 pilot to operate the transponder as required by current regulations. Factors were the controller's failure to observe the traffic conflict, the lack of radar conflict…Apr 4, 1998 · N111LR · 2 aircraft · Destroyed