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 ('1152930')
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 ('1152930')
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 WPR25FA240Accident · 4 fatalClass 3 · FieldPreliminary reportBeech 300 · Chinle, AZOn August 5, 2025, about 1245 mountain daylight time, a Beech 300, N534AW, was destroyed when it was involved in an accident near Chinle, Arizona. The pilot, co-pilot and two medical crew members were fatally injured. The airplane was operated as a Title 14…NTSB ERA24LA354Accident · No injuriesClass 4 · LimitedFinal reportBeech 300 · Asheboro, NCThe pilot’s failure to extend the landing gear before landing.NTSB ERA24LA012Accident · No injuriesClass 3 · LimitedFinal reportBeech 300 · Atlanta, GAThe pilot’s failure to maintain a proper approach speed, which resulted in a runway overrun. Contributing to the runway overrun were the pilot’s application of full reverse at an airspeed higher than that allowed by the system, which added power and forward…NTSB WPR17FA057Accident · 2 fatalField investigationFinal reportBeech 300 · Tucson, AZThe pilot's exceedance of the airplane's critical angle of attack during takeoff, which resulted in an aerodynamic stall. Contributing to the accident was the pilot's impairment by the effects of a combination of psychoactive substances.NTSB CEN11LA120Accident · No injuriesLimited investigationFinal reportBeech 300 · Minneapolis, MNThe pilot's failure to follow the aircraft checklist in locking the cabin door prior to departure which resulted in its in-flight separation.NTSB OPS10IA155Incident · No injuriesIncident investigationFinal reportBeech 300 · Chicago, ILThe air traffic controller's issuance of an improper takeoff clearance to the pilot of the Embraer. Contributing to the incident was the instructor’s inadequate monitoring of the trainee local controller.NTSB MIA04LA071Accident · Serious injuriesLimited investigationFinal reportBeech Be-300 · Daytona Beach, FLThe pilot's inadequate management of the airplane's fuel system, which resulted in fuel starvation, a loss of engine power, a forced landing, and damage to the airplane during the landing.NTSB LAX01LA019Accident · Serious injuriesLimited investigationFinal reportBeech 300 · Concord, CAthe pilot's delayed decision to abort the takeoff and his failure to utilize the propeller's reverse pitch function.NTSB ATL99FA044Accident · 2 fatalField investigationFinal reportBeech 300 · Cullman, ALThe pilot's failure to adhere to the missed approach procedure resulting in a collision with terrain. Contributing factors were fog and the rotorcraft rated pilot's lack of fixed wing certification/experience.NTSB CHI97LA057Accident · No injuriesLimited investigationFinal reportBeech 300 · Bloomington, INthe pilot's excessive distance/speed during the landing which led to his failure to attain a proper touchdown point on the runway. The factors involved were: the pilot's inadequate in-flight planning/decision, his failure proceed to the destination airport,…NTSB DCA94GA010Accident · 3 fatalClass 1Final reportBeech 300/F · Front Royal, VAthe failure of the pilot-in-command to ensure that the airplane remained in visual meteorological conditions over mountainous terrain, and the failure of the Federal Aviation Administration executives and managers responsible for the FAA flying program to:…NTSB MIA90IA039Incident · No injuriesIncident investigationFinal reportBeech 300 · Ormond Beach, FLFailure of the pilot in command in the Beech 300 to comply with an ATC clearance in a timely manner, while diverting his attention, and failure of the ATC controller to assure that IFR separation was maintained.
Back to Beech 300