NTSB investigations: Bellanca 17-30
5 cases on aircraft the registry lists as Bellanca 17-30, where the first occurrence was “In flight encounter with weather”. 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
| 1986 | 1 |
|---|---|
| 1997 | 1 |
| 1999 | 1 |
| 2000 | 1 |
| 2001 | 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\" = 240))
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" = 240))
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 DEN01LA091Accident · No injuriesLimited investigationFinal reportBellanca BL17-30 · Columbus, NMThe impact with terrain following an inadvertent stall/mush by the pilot during a go-around. A contributing factor was a dust devil.NTSB LAX00FA324Accident · 2 fatalField investigationFinal reportBellanca 17-30 · Scottsdale, AZthe pilot's failure to maintain adequate terrain clearance during a cruise descent, which resulted in controlled flight into mountainous terrain during dark night conditions. Contributing factors were the rain, thuderstorm, and dust storm weather conditions,…NTSB DEN00FA135Accident · 2 fatalField investigationFinal reportBellanca 17-30 · Lake City, COthe pilot's inadequate flight planning and preparation, and his inadvertent flight into adverse weather during a cross-country flight over mountainous terrain. Contributing factors were, the cloudy obscuration weather condition, the high density altitude, and…NTSB CHI98LA059Accident · 2 fatalLimited investigationFinal reportBellanca 17-30 · Independence, KSthe pilot's intentional flight into adverse weather. Contributing factors were low ceilings, fog, and the guy wire.NTSB ATL86FA223Accident · 2 fatalField investigationFinal reportBellanca 17-30 · West Green, GAThe plt took off at 1259 EDT, & at 1318, he reported level at 10,000'. There was no further comm with the acft. At about 1342, radar contact was lost. Subsequently, the acft wreckage was fnd scattered over a 425 yd area, along a sw azmith, aprx 1/2 mi from…