NTSB investigations: Schweizer 269C
6 cases on aircraft the registry lists as Schweizer 269C, where the first occurrence was “Loss of engine power(total) - mech failure/malf”. 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
| 1997 | 2 |
|---|---|
| 1998 | 1 |
| 2002 | 2 |
| 2006 | 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\" = 351))
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" = 351))
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 NYC06LA106Accident · Minor injuriesLimited investigationFinal reportSchweizer 269C · Kings Park, NYLoss of engine power due to the failure of the number 3 connecting rod bearing. A contributing factor was the lack of suitable terrain for the emrgency landing.NTSB LAX03LA052Accident · No injuriesLimited investigationFinal reportSchweizer 269C · Los Banos, CAThe improper engine overhaul by other maintenance personnel, which resulted in an exhaust valve failure and a total loss of engine power while in maneuvering flight.NTSB ATL02LA159Accident · Serious injuriesLimited investigationFinal reportSchweizer 300C · Haleyville, ALThe failure of maintenance personnel to perform an adequate inspection of loose intake components, which resulted in a total loss of engine power and subsequent emergency descent, forced landing, and collision with terrain in dark night conditions.NTSB IAD99GA013Accident · 1 fatalFinal reportSchweizer 269C · Baltimore, MDinadequate assembly instructions from the engine manufacturer which resulted in improper engine assembly, and subsequent power loss over unsuitable terrain, with insufficient altitude for a successful autorotation.NTSB NYC97GA148Accident · Serious injuriesFinal reportSchweizer 269C · Baltimore, MDA total loss of engine power which was a result of incomplete and improper engine overhaul by company maintenance personnel. A factor in the accident was the unsuitable forced landing area terrain.NTSB IAD97GA054Accident · No injuriesFinal reportSchweizer 269C · Cleveland, OHThe engine failure from the rod cap bolt being sheared and the separation of the number two cylinder separating from the crankcase.