NTSB investigations: Rotax SEE BOMBADIER
5 cases on aircraft whose registry engine model is Rotax SEE BOMBADIER, 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
| 1997 | 1 |
|---|---|
| 2003 | 1 |
| 2004 | 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.engine_model_code IN ('55555')
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.engine_model_code IN ('55555')
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 LAX06LA236Accident · Serious injuriesLimited investigationFinal reportHammack Air Command Elite · Hilo, HIan in-flight separation of a control rod joint assembly, which resulted in the pilot's loss of control. The underlying reason for the separation could not be determined.NTSB CHI05CA003Accident · No injuriesData collectionFinal reportSinclair Zenith 701 · Augusta, KSThe manufacturer's inadequate design/production of the landing gear axle leading to its separation and the airplanes subsequent nose over during the landing roll.. A factor was the axle's separation from its spring.NTSB SEA04LA103Accident · No injuriesLimited investigationFinal reportD'Amico Kitfox Series 7 · Caldwell, IDThe disconnection of the elevator pitch control assembly and the pitch rod during the takeoff as a result of an unsecured bolt.NTSB FTW03LA196Accident · No injuriesLimited investigationFinal reportHolmes Challenger II · Eldorado, TXThe loss of engine power during the takeoff/initial climb following the separation of the front cockpit throttle control cable resulting from inadequate maintenance.NTSB SEA97LA096Accident · Minor injuriesLimited investigationFinal reportHendrix Talon XP · Redmond, ORincomplete installation (omission of the aft control stick and interlink tube) of the flight control system, resulting in failure of the combined (torque) elevator and aileron rod and a disconnection of the forward flight control stick from the ailerons and…