NTSB investigations: Schweizer 269C
6 cases on aircraft the registry lists as Schweizer 269C, where the first occurrence was “In flight collision with object”. 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
| 1989 | 1 |
|---|---|
| 1990 | 1 |
| 1993 | 1 |
| 1995 | 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.\"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\" = 220))
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" = 220))
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 CHI98LA332Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Decker, INThe pilot's failure to maintain obstacle clearance resulting in a collision with a fence.NTSB CHI98LA021Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Grand Forks, NDthe pilot's inadequate preflight planning which resulted in a low fuel state, and his inability to see the wire which the helicopter contacted. Factors associated to the accident were the precautionary landing, the dark night conditions, and the wire which…NTSB CHI95LA222Accident · No injuriesLimited investigationFinal reportHughes 269C · Crete, NEthe pilot's failure to maintain clearance with the runway marker.NTSB CHI93LA208Accident · No injuriesLimited investigationFinal reportHughes 269 · Valley City, NDthe pilot-in-command's failure to maintain clearance from a tree during an aerial application manuever.NTSB FTW90FA111Accident · No injuriesField investigationFinal reportSchweizer 269C · Tallulah, LALoss of control due to a multiple bird strike and incorrect control inputs by the pilot in the flare. Contributing factors were the bird strike induced vibrations and the main rotor blade contact with the tail rotor drive shaft.NTSB SEA89LA052Accident · Minor injuriesLimited investigationFinal reportSchweizer 269C · Forrest Grove, ORThe pilot's misjudgment of his altitude and clearance while attempting to sling-load a trailer.