NTSB investigations: Bellanca 17-30A, VA
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
| 1972 | 1 |
|---|---|
| 1980 | 1 |
| 1984 | 1 |
| 1985 | 1 |
| 1996 | 1 |
| 2000 | 1 |
| 2016 | 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\" = 'VA' 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" = 'VA' 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 GAA16CA294Accident · No injuriesData collectionFinal reportBellanca 17 30 · Fredericksburg, VAThe pilot's failure to maintain directional control during the landing roll in gusting wind resulting in a runway excursion and substantial damage.NTSB IAD00LA028Accident · No injuriesLimited investigationFinal reportBellanca B17-30A · Shenandoah, VAthe pilot's failure to maintain control during landing roll-out. A factor was the pilot's lack of total experience.NTSB IAD96LA087Accident · Minor injuriesLimited investigationFinal reportBellanca 17-30A · New Market, VAa loss of engine power as a result of the failure of the left exhaust tailpipe and led to a shorted ignition system. A related factor was the unsuitable terrain in which the aircraft landed.NTSB BFO85FA032Accident · Serious injuriesField investigationFinal reportBellanca 17-30A · Roanoke, VAThe plt reported he ran a fuel tank dry during flt at 6000 ft. he switched fuel tanks, turned on the boost pump & manip-ulated the eng controls, but was unable to restart the eng. During a forced landing on I-581, the acft struck a pickup truck (traveling in…NTSB ATL84FA164Accident · Serious injuriesField investigationFinal reportBellanca 17-30A · Painter, VAAfter encountering low ceilings, the plt attempted a precautionary ldg. Upon realizing lights from the ground were on a house, a go-around was initiated with a climbing left turn. The acft then flew into trees one fourth to one half mile from the house.NTSB ATL80FID24Accident · Serious injuriesClosedBellanca 17-30A · Tappahannock, VANTSB NYC73AN034Accident · 1 fatalClosedBellanca 17-30A · Abingdon, VA