NTSB investigations: Bell 205A-1
5 cases on aircraft the registry lists as Bell 205A-1, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1983 | 2 |
|---|---|
| 1984 | 1 |
| 1990 | 1 |
| 1996 | 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 ('1181414')
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\" = 130))
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 ('1181414')
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" = 130))
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 ATL96LA068Accident · No injuriesLimited investigationFinal reportBell 205A-1 · Grove Hill, ALfatigue failure of the vertical fin forward spar in an area that was not accessible to inspection. A factor relating to the accident was: guidance for inspection of the area (where the fatigue occurred) was insufficiently defined by the manufacturer.NTSB ATL90FA100Accident · 1 fatalField investigationFinal reportBell 205A-1 · Moncks Corner, SCThe in-flight separation of the main rotor because of the failure of a pillow block bolt, and the failure of the operator/repair station to follow the overhaul procedures.NTSB ANC84LA089Accident · No injuriesLimited investigationFinal reportBell 205A-1 · Talkeetna, AKThe plt had just picked up an external 'sling' load of 2700 lbs of back-fill in a cement bucket. At 900 ft AGL the acft started a vertical vibration. As collective was bottomed a large piece of one main rotor blade separated. The plt said he jettisoned the…NTSB SEA83FA198Accident · Serious injuriesField investigationFinal reportBell 205A-1 · Elk Rock, WAThe acft was climbing thru about 800 ft AGL, when the plt noted a severe shudder & vibration. He lowered the collective, then noticed that the N2 & rotor RPM were pegged at 110%. As he reapplied the collective to stop the overspeed, he noted a loss of thrust…NTSB SEA83LA119Accident · No injuriesLimited investigationFinal reportBell 205A-1 · Near Randle, WAThe acft was engaged in log slinging operations and had just released a load and initiated a climb away from the site when according to the pilot the engine started to spool down, although the pilot was able return to the log-landingarea there was…