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 ('2076018', '207601A')
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 ('2076018', '207601A')
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 WPR25LA218Accident · No injuriesClass 3 · LimitedPreliminary reportCessna 425 · Round Rock, AZOn July 17, 2025, about 1600 mountain daylight time, a Cessna 425, N425D, was substantially damaged when it was involved in an accident near Round Rock, Arizona. The pilot receiving instruction and the flight instructor were not injured. The airplane was…NTSB CEN23LA103Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 425 · Bismarck, NDA loss of braking due to inadequate servicing of brake fluid by the pilot/mechanic, which resulted in a loss of airplane control on the ground.NTSB WPR21LA313Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 425 · Helena, MTA flameout of both engines due to fuel starvation for reasons that could not be determined due to the airplane’s damage.NTSB CEN19LA300Accident · No injuriesClass 3 · LimitedFinal reportCessna 425 · Bethany, OKA loss of control during the initial climb for undetermined reasons, which resulted in an aborted takeoff and runway excursion.NTSB CEN19FA161Accident · 1 fatalClass 3 · FieldFinal reportCessna 425 · Butler, MOThe pilot’s loss of airplane control during a descent to a diversion airport with only the left engine operating. Contributing to the accident was a malfunction of the right engine throttle, the cause of which could not be determined.NTSB CEN11LA251Accident · Minor injuriesLimited investigationFinal reportCessna 425 · Canadian, TXThe pilot’s continuation of the approach with excessive airspeed, which resulted in a hard landing and a loss of directional control.NTSB CHI07LA059Accident · Minor injuriesLimited investigationFinal reportCessna 425 · Harbor Springs, MIThe pilot's failure to maintain aircraft control and adequate airspeed during landing flare. Contributing to the accident was the aerodynamic stall/mush encountered at a low altitude.NTSB CHI07CA033Accident · No injuriesData collectionFinal reportCessna C-425 · Menominee, MIThe pilot failed to maintain control of the aircraft while parking the aircraft, and failed to maintain clearance from the building as the airplane taxied forward. A factor was the terminal.NTSB SEA06FA022Accident · 1 fatalField investigationFinal reportCessna 425 · Belgrade, MTThe pilot's failure to maintain airspeed during the approach which resulted in an inadvertent stall. Factors associated with the accident were dark night conditions, clouds, icing conditions, low visibility and snow.NTSB DEN05FA126Accident · 4 fatalField investigationFinal reportCessna 425 · Lone Tree, COThe pilot's failure to properly execute the published instrument approach procedure, which resulted in controlled flight into terrain.NTSB DEN03LA095Accident · No injuriesLimited investigationFinal reportCessna 425 · Pueblo, COthe pilot's inadvertent flight into adverse weather conditions. Contributing factors include the encounter with severe turbulence and hail.NTSB LAX02FA101Accident · 3 fatalField investigationFinal reportCessna 425 · San Jose, CAthe pilot's loss of control and resulting exceedence of the design stress limits of the aircraft, which led to an in-flight structural failure. The pilot's loss of control was due in part to the loss of primary airspeed reference resulting from pitot tube…NTSB SEA01FA017Accident · 2 fatalField investigationFinal reportCessna 425 · Idaho Falls, IDThe pilot-in-command's failure to maintain adequate airspeed with an asymmetric thrust condition, resulting in a loss of aircraft control. A factor was an asymmetric engine thrust condition, which was present for undetermined reasons.NTSB NYC97LA166Accident · Minor injuriesLimited investigationFinal reportCessna 425 · Perkasie, PAthe pilot's inadequate preflight, by failing to verify the fuel supply, which led to subsequent fuel exhaustion and loss of engine power. A related factor was: the inaccurate fuel quantity gauge.NTSB LAX97LA125Accident · No injuriesLimited investigationFinal reportCessna 425 · Fresno, CAfailure of the right brake to function, due to the installation mechanic's failure to completely bleed all air from the lines. A factor in the accident was the pilot's decision to fly the unairworthy aircraft before the engine/propeller installation had been…NTSB NYC97FA030Accident · 3 fatalField investigationFinal reportCessna 425 · Bohemia, NYthe pilot's early descent to decision height and his failure to perform the missed approach procedure. A factor was the failure of air traffic control to issue a safety advisory.NTSB LAX96LA328Accident · No injuriesLimited investigationFinal reportCessna 425 · Auburn, CAfailure of the right brake system (master cylinder O-ring seal). Factors relating to the accident were: the narrow runway, and the presence of a ditch adjacent to the runway.NTSB BFO94LA027Accident · Serious injuriesLimited investigationFinal reportCessna 425 · London, KYLoss of engine power due to fuel contamination.NTSB MIA92LA169Accident · No injuriesLimited investigationFinal reportCessna 425 · Greenwood, MSFailure of the pilot-in-command to maintain his descent rate resulting in an undershoot. Contributing to the accident was the chip detector failure due to improper quality control by the manufacturer.NTSB MIA92FA085Accident · 1 fatalField investigationFinal reportCessna 425 · Lakeland, FLLoss of control in flight by the pilot for undetermined reasons.NTSB LAX92FA090Accident · 7 fatalField investigationFinal reportCessna 425 · Las Vegas, NVThe pilot's failure to maintain aircraft control due to spatial disorientation. Factors in this accident were: 1) the pilot's failure to obtain a preflight weather briefing and to properly evaluate the existing weather conditions prior to flight, and 2)…NTSB ATL90LA059Accident · No injuriesLimited investigationFinal reportCessna 425 · Augusta, GAFailure of the pilot to maintain control of the aircraft during the go-around. A factor related to the accident was: the pilot's delay in initiating the go-around.NTSB MIA88FA105Accident · 1 fatalField investigationFinal reportCessna 425 · Sanford, FLThe flt was cleared for a night ILS apch & advised that twr at dest had closed. Twr had rptd at closing that fog was forming & the flt was advised of the fog. The acft was located on a remote part of the arpt the next morning. The ELT had activated but the…NTSB DEN86MA061Accident · 5 fatalMajor investigationFinal reportCessna 425 · Granby, CODrg arrival, the plt advised ARTCC that the destination arpt appeared to be covered with fog. She then canceled her IFR flt plan. According to ground witnesses, the acft made several passes over the arpt. Witnesses also rprtd that the horizontal visibility…NTSB DEN85LA244Accident · No injuriesLimited investigationFinal reportCessna 425 · Boulder, COThe plt said he made a normal ldg. During ldg roll the left brake would not respond to pedal application. The plt errored by incorrectly feathering both props. The a/c went off the eng of r/w and struck a fence. Examination of the brake system revealed a…NTSB NYC84FA092Accident · Minor injuriesField investigationFinal reportCessna 425 · Dryden, NYThe plt stated that he was utilizing the autopilot and flt director to execute the ILS appch to rwy 32. The autopilot was tracking the localizer while the pilot controlled the rate of descent along the glideslope with pitch command wheel on the autopilot,…NTSB NYC84FA052Accident · 1 fatalField investigationFinal reportCessna 425 · Newburgh, NYDuring arrival, there were indefinite delays at white plains, NY, so the plt diverted to Newburgh, NY. He was vectored for an ILS rwy 9 apch. While en route, the plt requested & was given the ILS freq, mins for the apch, the arpt elevation(491 ft MSL), the…NTSB ATL82FA018Accident · 1 fatalClosedCessna 425 · Natchez, MS
Back to Cessna 425