Fatal NTSB investigations: Aero Commander 100-180
12 cases on aircraft the registry lists as Aero Commander 100-180. 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
| 1971 | 2 |
|---|---|
| 1972 | 1 |
| 1973 | 1 |
| 1976 | 1 |
| 1978 | 2 |
| 1981 | 1 |
| 1984 | 1 |
| 1988 | 1 |
| 1993 | 1 |
| 1997 | 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('0140208'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('0140208'))
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 CHI98FA010Accident · 3 fatalField investigationFinal reportAero Commander 100-180 · Auburn, NEthe pilot misjudged distance/altitude to the runway, while on final approach to land, allowing the airplane to get too low and collide with a truck. A related factor was: the proximity of the truck (and highway) to the runway.NTSB LAX94LA079Accident · 1 fatalLimited investigationFinal reportAero Commander 100 · Chico, CAIssuance of an improper (special VFR) clearance by the tower controller, while the visibility was less than one mile, continued VFR flight by the pilot into instrument meteorological conditions (IMC), and the pilot's failure to maintain control of the…NTSB SEA88FA160Accident · 3 fatalField investigationFinal reportAero Commander 100-180 · John Day, ORWhile elk spotting in mountainous terrain, the aircraft collided with trees in a nose low turn similar to the intermediate stages of a stall. A severe post impact fire erupted. The density altitude at the accident site elevation was approximately 10,100 feet.…NTSB DEN84FA188Accident · 1 fatalField investigationFinal reportRockwell 100-180 · Franktown, COThe plt attempted to takeoff downwind (wind 310 degrees @22 knots) with a density altitude calculated to be 9190 ft MSL. According to the acft manufacturer, the acft would require 2,535 ft for a ground run. Rwy 17, a grass strip used for the takeoff was 1800…NTSB CHI81FA079Accident · 3 fatalClosedAero Comdr 100 · Columbia Stat, OHNTSB IAD78FA105Accident · 2 fatalClosedCessna 150 · Louisville, KYNTSB SEA78FA055Accident · 3 fatalClosedAero Comdr 100 · Bly, ORNTSB MIA76AM099Accident · 1 fatalClosedAero Comdr 100 · Donaldsonville, GANTSB LAX74OL032Accident · 2 fatalClosedAero Comdr 100 · Hermosillo, MexicoNTSB MIA73AM033Accident · 2 fatalClosedAero Comdr 100 · Tarrant City, ALNTSB MKC72AK033Accident · 1 fatalClosedAero Comdr 100 · Albert Lea, MNNTSB FTW72AF010Accident · 4 fatalClosedAero Comdr 100 · Georgetown, TX