NTSB investigations: Continental TSIO-520 series, ID
58 cases on aircraft whose registry engine model is Continental TSIO-520 series. 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, 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_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.\"eventStateOrRegion\" = 'ID' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17040'))
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_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."eventStateOrRegion" = 'ID' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17040'))
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 SEA83FA057Accident · 1 fatalField investigationFinal reportCessna TU206G · Soda Springs, IDA search for the aircraft was begun after the pilot's relatives reported it was overdue and residents near the crash site heard the sounds of a low flying plane suddenly terminate. Unofficial reports of the weather indicated it was about 200 ft obscured, 1/4…NTSB SEA83LA008Accident · No injuriesLimited investigationFinal reportCessna T210M · Ashton, IDDuring a flight from el paso, TX to three forks, MT, the pilot noted clouds below his cruising altitude while crossing the Montana border. When he arrived at his destination, he was above a solid overcast, so he diverted to west yellowstone, MT. During…NTSB SEA82FYA08Accident · 1 fatalFinal reportCessna T210M · Shoshone, IDThe aircraft crashed in a near level attitude and at a high rate of speed. Neither the seat belt nor shoulder harness was fastened. The pilot's blood alcohol level was 236 mg%.NTSB SEA82DA038Accident · No injuriesFinal reportCessna 340 · Idaho Falls, IDThe pilot reported that during an ILS approach, he broke out at about 500 ft AGL. He stated that he did not properly arrest the sink rate and struck the runway. He also stated that there probably was some ice under the wings that had accumulated during…NTSB SEA82FA032Accident · 4 fatalField investigationFinal reportCessna P210N · Boise, IDAfter takeoff while climbing through 10,000 ft MSL the pilot declared an emergency. The pilot stated he was having vacuum problems and was on partial panel. Salt lake city ARTCC answered his request for guidance to a VFR landing with no gyro vector…NTSB SEA81FYP03Accident · Minor injuriesClosedCessna TU206G · Salmon, IDNTSB SEA80FA024Accident · 1 fatalClosedCessna T210L · Pocatello, IDNTSB SEA76DYA11Accident · No injuriesClosedRiley Super 340 · Boise, ID