NTSB investigations: Rotorway RI-162F, 2007
3 cases on aircraft whose registry engine model is Rotorway RI-162F. 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
| 2007 | 3 |
|---|---|
| 2008 | 2 |
| 2009 | 1 |
| 2010 | 2 |
| 2011 | 2 |
| 2012 | 1 |
| 2014 | 1 |
| 2015 | 3 |
| 2018 | 1 |
| 2023 | 2 |
| 2024 | 2 |
| 2025 | 4 |
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 year(c.\"eventDate\") = 2007
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('55007'))
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 year(c."eventDate") = 2007
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('55007'))
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 SEA08CA055Accident · No injuriesData collectionFinal reportBrooks Exec 162F · Santa Maria, CAThe pilot's failure to maintain control of the helicopter during hover. Contributing to the accident was the pilot's lack of experience in rotorcraft.NTSB DFW07LA167Accident · No injuriesLimited investigationFinal reportRotorway 162F · Stratford, OKThe loss of engine power due to a seized supercharger. A contributing factor was the lack of suitable terrain for the forced landing.NTSB CHI07CA094Accident · No injuriesData collectionFinal reportMcCall Rotorway 162F · Malta, ILThe pilot's improper use of the rotorcraft flight controls resulting in a dynamic rollover during takeoff. A factor was the soft ground that the left skid encountered.