Final NTSB investigations: Starduster Too SA300
6 cases on aircraft the registry lists as Starduster Too SA300. 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
| 1970 | 1 |
|---|---|
| 1973 | 1 |
| 1979 | 1 |
| 1983 | 1 |
| 1985 | 1 |
| 2000 | 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.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('86601M5'))
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."completionStatus" = 'Completed'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('86601M5'))
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 FTW00LA177Accident · No injuriesLimited investigationFinal reportStarduster Too SA300 · Spicewood, TXThe pilot's failure to maintain directional control of the airplane during the landing roll. A factor was the muddy terrain condition.NTSB FTW86LPA06Accident · Minor injuriesFinal reportHomebuilt Starduster II SA300 · Canton, TXThe plt reported that after a low pass (300 ft AGL) over a tree line, the acft suddenly lost alt. He stated the throttle was advanced however, an increase in pwr was not experienced. The acft continued to descend to ground contact.NTSB LAX83LA196Accident · No injuriesLimited investigationFinal reportHomebuilt Starduster TWO · El Monte, CAThe acft was obsved by a twr ATC specialist to make a normal 3 pt lndg and enter into a l gd loop while exiting the rwy abt 1400 ft fm the threshold. He further stated that the acft was traveling at a 'moderate speed' while exiting the rwy. Another acft was…NTSB NYC79FNA17Accident · Minor injuriesClosedStarduster SA-300 · Boxboro, MANTSB CHI73FEG30Accident · No injuriesClosedStarduster SA-200 · New Carlisle, OHNTSB CHI70FGA07Accident · Minor injuriesClosedStarduster TOO · Tremont City, OH