NTSB investigations: Bellanca 17-30A, TN
7 cases on aircraft the registry lists as Bellanca 17-30A. 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
| 1976 | 1 |
|---|---|
| 1983 | 1 |
| 1999 | 1 |
| 2000 | 1 |
| 2005 | 1 |
| 2008 | 1 |
| 2019 | 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.\"eventStateOrRegion\" = 'TN' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1220433'))
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" = 'TN' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1220433'))
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 ERA19LA080Accident · 2 fatalLimited investigationFinal reportBellanca 1730 · Soddy-Daisy, TNThe pilot's improper decision to attempt an aerobatic maneuver at low altitude, which led to an aerodynamic stall and spin from which the pilot could not recover.NTSB MIA08LA185Accident · No injuriesLimited investigationFinal reportBellanca 17-30A · Sparta, TNFailure of the nose landing gear mount during a normal landing due to an improper weld.NTSB ATL05CA056Accident · Minor injuriesData collectionFinal reportBellanca 17-30A · Eagleville, TNThe pilot's mismanagement of the fuel supply by his failure to switch the fuel selector position , which resulted in a loss of engine power due to fuel starvation.NTSB ATL00FA019Accident · 2 fatalField investigationFinal reportBellanca BL-17-30A · Monteagle, TNThe pilot's failure to adequately evaluate weather conditions that resulted in the continuation of visual flight into instrument weather conditions and the subsequent collision with trees.NTSB MIA99LA234Accident · Serious injuriesLimited investigationFinal reportBellanca 17-30A · Robbins, TNThe total loss of engine power due to failure of maintenance personnel to assure that the thru bolt nut at the Nos. 2 and 3 cylinders was adequately torqued following removal and replacement of the No. 3 cylinder approximately 328 hours earlier. Also, the…NTSB ATL83LA153Accident · Minor injuriesLimited investigationFinal reportBellanca 17-30A · Shelbyville, TNThe acft collided with a power line during a forced landing after power loss due to fuel exhaustion. The acft was on thefinal approach. The pilot said he would be landing short of the rwy. When asked the nature of his emergency he said 'I think I am running…NTSB IAD76FKW30Accident · No injuriesClosedBellanca 17-30A · Lebanon, TN