NTSB investigations: Schweizer 269C
6 cases on aircraft the registry lists as Schweizer 269C, 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
| 1992 | 1 |
|---|---|
| 1996 | 1 |
| 2000 | 1 |
| 2002 | 1 |
| 2005 | 2 |
Where
Latest 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 ('8059502')
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 ('8059502')
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 CHI06TA033Accident · No injuriesFinal reportSchweizer 269C · Manhattan, KSThe binding of the main rotor blade's tachometer cable during cruise flight resulting in an observed split tachometer indication/aural alarm and perceived mechanical emergency and the unsuitable terrain the pilot encountered during the emergency landing. A…NTSB IAD05LA046Accident · Serious injuriesLimited investigationFinal reportSchweizer 269C · Leet, WVA fatigue fracture of the main transmission drive pinion. Also causal was the manufacturer's failure to remove the affected pinions from service during the period that transpired between the initial failures and the accident flight.NTSB DEN02LA098Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Broomfield, COmaintenance personnel's failure to secure the landing skid oleo strut bolt during the last 50-hour inspection, causing the left rear skid to collapse and the tail rotor to strike the ground.NTSB FTW00LA216Accident · Minor injuriesLimited investigationFinal reportSchweizer 269C · Sherman, TXthe total failure of the clutch cable during landing, which resulted from fatigue cracking of the cable's individual wires.NTSB FTW96LA095Accident · No injuriesLimited investigationFinal reportSchweizer 269C · San Ygnacio, TXFailure of the rotor drive system clutch assembly (separation of the swedge ball from the end of the clutch control cable), which resulted in disengagement of the rotor drive system, while the helicopter was in lateral movement at low altitude.NTSB CHI93GA046Accident · 2 fatalFinal reportSchweizer 269C · Kansas City, MOThe pilot-in-command's misjudging the distance during the autorotation.