NTSB investigations: Bellanca 17-30A, MN
8 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
| 1973 | 1 |
|---|---|
| 1977 | 1 |
| 1985 | 1 |
| 2002 | 1 |
| 2016 | 1 |
| 2019 | 1 |
| 2020 | 1 |
| 2023 | 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\" = 'MN' 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" = 'MN' 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 CEN23LA177Accident · No injuriesClass 4 · LimitedFinal reportBellanca 17-30A · Longville, MNThe pilot’s failure to maintain directional control during the landing roll with an unexpected windshift, which resulted in a runway excursion.NTSB CEN21LA073Accident · No injuriesClass 3 · LimitedFinal reportBellanca 17-30A · Arden Hills, MNIncorrect connecting rod installation, which resulted in the failure of the nos. 5 and 6 connecting rods and subsequent total loss of engine power.NTSB CEN20CA026Accident · No injuriesData collectionFinal reportBellanca 1730 · Clear Lake, MNThe pilot's focus inside the cockpit during the base turn and final approach, which led to a high sink rate developing and a subsequent hard landing short of the runway.NTSB CEN17LA058Accident · No injuriesLimited investigationFinal reportBellanca 17 30A · Blaine, MNA total loss of engine power due to a lack of crankshaft lubrication to the No. 4 connecting rod journal.NTSB CHI02LA070Accident · 2 fatalLimited investigationFinal reportBellanca 17-30A · Alexandria, MNThe pilot's disregard of the weather evaluation and his attempt to fly into known adverse weather without an instrument rating. Factors in the accident were the low ceiling, the low visibility, and the icing conditions.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 MKC78DER09Accident · No injuriesClosedBellanca 17-30A · Lakeville, MNNTSB MKC74DER15Accident · No injuriesClosedBellanca 17-30A · Lake Elmo, MN