NTSB investigations: Bellanca 17-30A, AZ
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
| 1980 | 1 |
|---|---|
| 1982 | 1 |
| 1986 | 1 |
| 1988 | 1 |
| 1992 | 1 |
| 1997 | 1 |
| 1998 | 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\" = 'AZ' 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" = 'AZ' 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 LAX98LA132Accident · Minor injuriesLimited investigationFinal reportBellanca BL17-30A · Prescott, AZThe pilot's failure to attain directional control after swerving off the runway and impacting a ditch.NTSB LAX97LA098Accident · Minor injuriesLimited investigationFinal reportBellanca 17-30A · Scottsdale, AZfuel exhaustion due to the pilot's improper fuel management.NTSB LAX92LA341Accident · No injuriesLimited investigationFinal reportBellanca 17-30A · Sedona, AZThe failure of the fixed base operator to properly conduct an annual inspection and inadequate compliance with the airworthiness directive. Contributing to this accident was the total failure of the main landing gear trunion due to fatigue.NTSB LAX88LA266Accident · No injuriesLimited investigationFinal reportBellanca 17-30A · Springerville, AZShortly after takeoff, the engine experienced a loss of power. The pilot made a forced landing where during the landing roll, the airplane collided with the terrain. During the engine inspection, it was found that the left magneto fired only one sparkplug.…NTSB LAX87FA200Accident · 2 fatalField investigationFinal reportBellanca 17-30A · Flagstaff, AZThe plt & his wife desired to return to their Flagstaff, AZ, home following a weekend at stockton, CA., & they departed sck in VFR weather conditions. The weather at the destination arpt had been below VFR minimums all morning & it was forecast to remain poor…NTSB LAX83FA050Accident · 4 fatalField investigationFinal reportBellanca 17-30A · Williams, AZThe original departure point was camarillo, CA. Before departing camarillo, the pilot obtained a weather briefing for a flight to flagstaff, AZ. At about that time, the flagstaff weather was, in part: zero ceiling, 1/16 mi visibility. The pilot was warned of…NTSB LAX81FA009Accident · Minor injuriesClosedBellanca 17-30A · Phoenix, AZ