NTSB investigations: Bellanca 17-30
6 cases on aircraft the registry lists as Bellanca 17-30, where the first occurrence was “Loss of engine power(total) - mech failure/malf”. 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
| 1982 | 1 |
|---|---|
| 1983 | 1 |
| 1990 | 1 |
| 1993 | 1 |
| 1997 | 1 |
| 2000 | 1 |
Where
Open the mapLatest 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1220432', '1250020')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 351))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1220432', '1250020')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 351))
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 FTW01LA009Accident · Minor injuriesLimited investigationFinal reportBellanca BL17-30 · Waller, TXthe loss of engine power during climb to cruise due to the failure of the crankshaft counterweight. A contributing factor was the lack of suitable terrain for the forced landing.NTSB ATL97LA045Accident · Minor injuriesLimited investigationFinal reportBellanca 17-30 · Aikens, SCexcessive wear of the fuel metering unit/shaft, which resulted in a fuel leak and premature exhaustion of the fuel supply.NTSB CHI93LA324Accident · Minor injuriesLimited investigationFinal reportBellanca BL-17-30 · Lee'S Summit, MOimproper maintenance which resulted in a disconnected throttle lever linkage.NTSB BFO90IA039Incident · No injuriesIncident investigationFinal reportBellanca 17-30 · Davis, WVThe improper installation of the connecting rod bearings on the number one cylinder.NTSB FTW84LA051Accident · Serious injuriesLimited investigationFinal reportBellanca 17-30 · Moore, OKThe acft crashed during a forced landing after the engine quit. The acft had a prior forced landing and the fuel pump was suspect. Post accident investigation showed that only one safety pin was installed in the fuel selector shaft allowing excessive free…NTSB ATL82DA138Accident · No injuriesFinal reportBellanca 17-30 · Havelock, NCAbout eight minutes after takeoff, the pilot declared an emergency and reported an engine failure. He diverted, but was unable to reach the airport. A gear-up landing was made about one mile short of the runway. An examination of the aircraft revealed that…