NTSB investigations: Bellanca 17-30A
5 cases on aircraft the registry lists as Bellanca 17-30A, where the first occurrence was “In flight collision with object”. 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
| 1983 | 1 |
|---|---|
| 1985 | 1 |
| 1986 | 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 ('1220433')
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\" = 220))
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 ('1220433')
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" = 220))
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 CHI00FA145Accident · 2 fatalField investigationFinal reportBellanca 17-30A · Taylor, MOflight into known adverse weather conditions and the altitude/clearance not maintained by the pilot. An additional cause was the improper in-flight planning/decision by the pilot. Contributing factors were the weather below approach/landing minimums, night…NTSB IAD98LA017Accident · Serious injuriesLimited investigationFinal reportBellanca 17-30A · Steubenville, OHCollision with deer on runway during initial takeoff and climb.NTSB CHI86FA102Accident · 3 fatalField investigationFinal reportBellanca 17-30A · Frankfort, MIThe plt was taking off from his local arpt and local residents described conditions of 100 ft vis in heavy ground fog. After lift-off he began a left turn toward a 300 ft high ridge topped by 100 ft trees. The acft struck the tree tops, the plt lost control…NTSB CHI85LA140Accident · No injuriesLimited investigationFinal reportBellanca 17-30A · Marshall, MNThe acft contacted 10 ft high trees during takeoff from a gravel taxiway. The plt then performed a forced landing in a cultivated fld during which the landing gear separated from the acft.NTSB FTW83LA285Accident · Serious injuriesLimited investigationFinal reportBellanca 17-30A · Clifton, TXOn final apch to land, the plt saw 2 buzzards & added power while maneuvering to avoid theem, then continued the apch. This resulted in landing beyond the intended touchdown point. The middle of the rwy was higher than either end; therefore, the plt was…