NTSB investigations: Bellanca 17-30A
11 cases on aircraft the registry lists as Bellanca 17-30A, where the first occurrence was “Loss of control - on ground/water”. 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
| 1984 | 1 |
|---|---|
| 1986 | 1 |
| 1987 | 1 |
| 1995 | 1 |
| 1996 | 2 |
| 1998 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2003 | 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\" = 260))
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" = 260))
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 CHI04LA049Accident · Minor injuriesLimited investigationFinal reportBellanca 17-30A · Wellington, KSThe pilot not maintaining directional control during the landing roll. Factors were the dry grass and the concrete box he encountered during his excursion off the runway.NTSB MIA03LA010Accident · No injuriesLimited investigationFinal reportBellanca 17-30A · Pell City, ALThe pilot's failure to maintain directional control following landing touchdown, resulting in a runway excursion and collision with a ditch off the left side of the runway.NTSB MIA01LA092Accident · No injuriesLimited investigationFinal reportBellanca BL-17-30A · Sylacauga, ALThe pilot's failure to maintain directional control during landing rollout, and the subsequent runway excursion and collision with trees.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 FTW98LA418Accident · No injuriesLimited investigationFinal reportBellanca 17-30A · Alpine, TXThe pilot's failure to maintain directional control of the airplane for undetermined reasons. A factor was the loose gravel composition of the runway.NTSB FTW97LA053Accident · No injuriesLimited investigationFinal reportBellanca 17-30A · Ruidoso, NMfailure of the pilot to maintain directional control during landing roll, and his delayed aborted landing. The gusty crosswind and blown left main tire were considered to be related factors.NTSB LAX96LA211Accident · No injuriesLimited investigationFinal reportBellanca 17-30A · Fallbrook, CAfailure of the pilot to attain the proper touchdown point on the runway, and his failure to maintain directional control of the airplane. Factors relating to the accident were: the excessive airspeed on final approach, and the short and wet condition of the…NTSB FTW95LA157Accident · No injuriesLimited investigationFinal reportBellanca 17-30A · Midland, TXThe pilot's failure to maintain directional control.NTSB DEN87LA072Accident · No injuriesLimited investigationFinal reportBellanca 17-30A · Greeley, CODuring landing roll, after a normal pattern, an unusual noise was heard by the pilot. He described it as a 'thud' or a loud 'pop' noise. The pilot lost directional control and departed the runway to the left. The landing gear was severely damaged. No prempact…NTSB MIA86LA107Accident · No injuriesLimited investigationFinal reportBellanca 17-30A · Ft. Lauderdale, FLThe non-certificated student plt was making an unauthorized night solo x-country flt. He attempted a landing at his destination with a left 60 deg, 12 kt x-wind. During the landing roll the acft veered to the right and the plt correctedby applying 'extreme'…NTSB DEN84LA072Accident · Serious injuriesLimited investigationFinal reportBellanca 17-30A · Angel Fire, NMAfter making a x-country flt from Oklahoma city, ok to Angel Fire, NM, the plt landed on a snow covered rwy at an elevation of 8382 ft. during the landing, the acft bounced, drifted to the left side of the rwy, then hit a 3-1/2 ft snowbank. The plt reported…