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 ('1152920')
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 ('1152920')
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 ERA26LA349Accident · No injuriesClass 3 · LimitedInvestigation openBeech 200 · Dothan, ALNTSB WPR26LA334Accident · Minor injuriesClass 3 · LimitedPreliminary reportBeech 200 · Roswell, NMOn September 8, 2026, about 0044 mountain daylight time, N393JW, a Beech 200, was substantially damaged when it was involved in an accident near Roswell, New Mexico. The two pilots and two of the medical crew members were not injured, a third medical crew…NTSB ANC24LA007Accident · No injuriesClass 4 · LimitedFinal reportBeech 200 · New Stuyahok, AKThe pilot’s loss of directional control during landing flare resulting in substantial damage to the left wing.NTSB CEN23LA387Accident · No injuriesClass 4 · LimitedFinal reportBeech 200 · Henderson, KYAn in-flight collision with a bird shortly after takeoff.NTSB CEN23LA052Accident · No injuriesClass 4 · LimitedFinal reportBeech 200 · Del Rio, TXThe pilot’s failure to maintain control of the airplane that resulted in an uncontrolled descent and overstress of the airframe during his recovery of the airplane.NTSB CEN22LA138Accident · No injuriesClass 3 · LimitedFinal reportBeech 200 · Gulfport, MSThe failure of the right main landing gear actuator, which led to a gear-up landing.NTSB WPR22LA063Accident · No injuriesClass 4 · LimitedFinal reportBeech 200 · Eugene, ORThe pilot’s improper checklist use, which resulted in an electrical malfunction and subsequent gear up landing.NTSB ERA22LA019Accident · No injuriesClass 3 · LimitedFinal reportBeech 200 · Mount Pleasant, SCThe pilot’s failure to maintain clearance with the parked fuel truck while taxiing for takeoff. Contributing to the outcome was the pilot’s decision to park the airplane in the congested ramp area and his excessive taxi speed.NTSB CEN20LA352Accident · 1 fatalClass 3 · LimitedFinal reportBeech 200 · Rockford, ILThe pilot’s failure to maintain airplane control following a reduction of thrust in the left engine during takeoff. The reason for the reduction in thrust could not be determined based on the available evidence.NTSB GAA20CA054Accident · Serious injuriesData collectionFinal reportBeech 200 · New Braunfels, TXThe airplane’s in-flight collision with a bird.NTSB CEN18FA387Accident · 1 fatalField investigationFinal reportBeech 200 · Oscoda, MIThe pilot's descent below minimum descent altitude during the nonprecision instrument approach for reasons that could not be determined based on the available information.NTSB CEN17LA043Accident · Minor injuriesLimited investigationFinal reportBeech 200 · Moorhead, MNThe pilot's failure to attain a positive climb rate during an attempted missed approach in night instrument meteorological conditions that were at/near approach minimums, which resulted in controlled flight into terrain.NTSB GAA16CA475Accident · No injuriesData collectionFinal reportBeech 200 · Apopka, FLThe pilot's failure to maintain directional control during an attempted aborted landing in gusty crosswind conditions, which resulted in a runway excursion and an impact with a tree.NTSB ERA16CA080Accident · No injuriesData collectionFinal reportBeech 200 · Clearwater, FLThe pilot's failure to properly configure the airplane's landing gear prior to landing, which resulted in a gear-up landing.NTSB WPR11FA166Accident · 5 fatalField investigationFinal reportBeech 200 · Long Beach, CAThe pilot's failure to maintain directional control of the airplane during a momentary interruption of power from the left engine during the initial takeoff climb. Contributing to the accident was the power interruption due to water contamination of the fuel,…NTSB WPR09FA165Accident · No injuriesField investigationFinal reportBeech 200 · Henderson, NVThe pilot's failure to monitor and maintain clearance from an obstacle during taxi.NTSB CEN09RA052Accident · 1 fatalForeign investigationBeech 200 · Punta Chivato, MexicoOn November 3, 2008 at approximately 1800 pacific standard time (PST) a twin-engine turbo prop, Beechcraft BE200, N200JL, was destroyed when it impacted terrain shortly after takeoff from Punta Chivato Airstrip, located near Punto Chivato, Baja California…NTSB SEA08FA042Accident · 2 fatalField investigationFinal reportBeech 200 · Salmon, IDAn in-flight loss of control due to the pilot's failure to remove ice and snow from the airplane prior to takeoff. Contributing to the accident were the pilot's improper preflight preparation/actions, falling snow, and a low ambient temperature.NTSB DEN07LA090Incident · No injuriesLimited investigationFinal reportBeech 200 · Angel Fire, NMThe pilot's inability to maintain clearance from the snow bank. Contributing factors were the pilot's failure to perform a go-around/missed approach procedure after observing snow removal equipment on the runway, the pilot's improper in-flight planning and…NTSB SEA07FA051Accident · 3 fatalField investigationFinal reportBeech 200 · Belgrade, MTThe pilot's failure to maintain an adequate altitude and descent rate during a night visual approach. Dark night conditions and mountainous terrain are factors in the accident.NTSB ATL06FA044Accident · 6 fatalField investigationFinal reportBeech 200 · N Myrtle Beach, SCThe pilot's failure to maintain control during landing approach for undetermined reasons.NTSB DFW05LA034Accident · No injuriesLimited investigationFinal reportBeech BE-200 · Bay View, TXThe pilot's failure to maintain directional control as result of his improper runway selection for takeoff. A contributing factor was the prevailing right quartering tailwind.NTSB IAD05MA006Accident · 10 fatalClass 1 · MajorFinal reportBeech 200 · Stuart, VAThe flight crew's failure to properly execute the published instrument approach procedure, including the published missed approach procedure, which resulted in controlled flight into terrain. Contributing to the cause of the accident was the flight crew's…NTSB CHI04LA167Accident · No injuriesLimited investigationFinal reportBeech 200 · Green Bay, WIThe loss of engine power after takeoff for an undetermined reason.NTSB NYC04FA139Accident · 2 fatalField investigationFinal reportBeech 200 · Rupert, WVThe pilot-in-command's improper decision to continue VFR flight into IMC conditions, which resulted in controlled flight into terrain. Factors were the FAA Principle Operations Inspector's inadequate surveillance of the operator, and a low ceiling.NTSB FTW04LA090Accident · No injuriesLimited investigationFinal reportBeech BE-200 · Springdale, ARThe failure of the right main landing gear actuator clevis bolt for undetermined reasons.NTSB DCA03WA056Accident · 9 fatalForeign investigationBeech King Air B200 · Madeira Islands, PortugalNTSB ATL03LA038Accident · No injuriesLimited investigationFinal reportBeech 200 · Jackson, MSThe failure of the landing gear system for undetermined reasons.NTSB MIA03LA033Accident · No injuriesLimited investigationFinal reportBeech 200 · Jacksonville, FLFailure of the main landing gear locking mechanism for undetermined reasons, which resulted in the main landing gear collapsing, and damage to the airplane during landing.NTSB NYC02TA029Accident · Minor injuriesFinal reportKaman K-1200 · Bloomfield, CTThe pilot's failure to maintain aircraft control while hovering. A factor related to the accident was the pilots lack of experience in type of aircraft.NTSB CHI02LA012Accident · No injuriesLimited investigationFinal reportBeech 200 · Osage Beach, MOThe inadequate planning/decision and the exceeded crosswind component by the pilot. The gusts were a contributing factor.NTSB NYC01FA215Accident · 1 fatalField investigationFinal reportBeech BE-200 · Piqua, OHThe pilot's improper decision to attempt a visual landing under instrument meteorological conditions and his failure to maintain adequate altitude/clearance, which resulted in an in-flight collision with trees. A factor in this accident was the ground fog.NTSB DEN01IA108Incident · No injuriesIncident investigationFinal reportBeech 200 · Greeley, COjamming of the nose landing gear actuator due to improper painting procedures by other maintenance personnel which resulted in a wheels up landing.NTSB SEA01TA050Accident · No injuriesFinal reportBeech 200 · Olympia, WAThe pilot's failure to attain the proper touchdown point for landing. A factor was weather conditions below published approach minimums.NTSB DCA01MA017Accident · 10 fatalClass 1 · MajorFinal reportBeech 200 · Strasburg, COThe pilot’s spatial disorientation resulting from his failure to maintain positive manual control of the airplane with the available flight instrumentation. Contributing to the cause of the accident was the loss of a.c. electrical power during instrument…NTSB MIA01LA054Accident · No injuriesLimited investigationFinal reportBeech 200 · Naples, FLThe failure of the pilot to obtain assistance from the FBO in the form of a marshaller and failure of the pilot to maintain clearance resulting in the on-ground collision with the light pole.NTSB CHI00FA027Accident · 3 fatalField investigationFinal reportBeech 200 · Chicago, ILOn ground collision with the lake for undetermined reasons.NTSB NYC00FA006Accident · 2 fatalField investigationFinal reportRaytheon Corporate Jets BE-200 · Williamstown, MAThe pilot-in-command's failure comply with an air traffic control clearance which resulted in a collision with terrain. A factor in this accident was clouds.NTSB SEA99LA029Accident · No injuriesLimited investigationFinal reportBeech 200 · Weiser, IDAirport snow removal was not properly performed. A snowbank was a factor.NTSB MIA98WA043Accident · No injuriesForeign investigationBeech BE-200 · Huarmey, PeruNTSB MIA97FA232Accident · 1 fatalField investigationFinal reportBeech 200 · Dalton, GAthe pilot's improper IFR procedure, by failing to maintain the minimum descent altitude (MDA) during the ILS localizer approach, until the runway environment was in sight, which resulted in a collision with terrain short of the runway. Factors relating to the…NTSB NYC92FA118Accident · 4 fatalField investigationFinal reportBeech BE-200 · New Castle, DEThe pilot's improper execution of an emergency procedure, after an engine failure, which resulted in a loss of airspeed and subsequent stall at an altitude too low for recovery. A factor related to the accident was the fatigue failure of a compressor turbine…NTSB NYC91LA068Accident · No injuriesLimited investigationFinal reportBeech 200 · Johnstown, PAThe pilot's failure to maintain proper directional control of the airplane during landing, resulting in a collision with a snow bank and runway marker. A factor relating to the accident was the low visibility during landing.NTSB CHI91LA067Accident · No injuriesLimited investigationFinal reportBeech 200 · Vichy, MOA restricted visual outlook and go-around was not performed by the pilot. Factors related to the accident were a dark night, fog and glare, ice covered runway and whiteout conditions.NTSB LAX89FA192Accident · 1 fatalField investigationFinal reportBeech 200 · Azusa, CAImproper in-flight planning/decision by the pilot, which resulted in has inadvertent flight into instrument meteorological conditions (IMC) and subsequent collision with mountainous terrain. The weather and terrain conditions were considered to be related…NTSB ATL89MA123Accident · 3 fatalMajor investigationFinal reportBeech 200 · Pensacola, FLAn in flight cabin fire of undetermined origin, and smoke (toxic condition) in the crew compartment, which resulted in physical impairment of the flight crew.NTSB FTW88IA165Incident · Minor injuriesIncident investigationFinal reportBoeing 727-200 · Dfw Airport, TXFatigue failure of the left main landing gear door actuator pivot trunnion shaft which subsequently became lodged in the actuator clevis preventing the door unlock mechanism from actuating during gear extension.NTSB DEN88FA202Accident · 1 fatalField investigationFinal reportBeech 200 · Jackson, WYThe plt and his two pax had just arrived at the Jackson hole airport (jax) approximately 30 minutes prior to the accident. The plt dropped off his pax and stepped into operations for a short break. He then returned to the acft by himself for a return flt to…NTSB NYC85FA141Accident · 2 fatalField investigationFinal reportBeech BE-200 · Hamptonburgh, NYPlt filed IFR for 2 flight legs; baltimore, MD to teterboro, NJ & teterboro to montgomert, NY (orange co arpt). The plt received a preflight wx briefing & was advised that the forecast for stewart, NY, about 10 mis form montgomery was sky partially obscured…NTSB ANC82FA080Accident · 6 fatalClosedBeech 200 · King Cove, AK
Back to Beech 200