Fatal NTSB investigations: Aero Commander 680-F
14 cases on aircraft the registry lists as Aero Commander 680-F. 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
| 1964 | 1 |
|---|---|
| 1967 | 1 |
| 1973 | 1 |
| 1974 | 2 |
| 1975 | 1 |
| 1976 | 2 |
| 1978 | 1 |
| 1979 | 1 |
| 1983 | 1 |
| 1985 | 2 |
| 1993 | 1 |
Where
Latest 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 ('0141606'))
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 ('0141606'))
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 FTW93WA270Accident · 3 fatalForeign investigationAero Commander 680F · Chihuahua, MexicoNTSB ATL85FA224Accident · 1 fatalField investigationFinal reportAero Commander 680-FP · Chesapeake, OHAs near as can be determined, this was the plt's second flt since obtaining his multi engine rating and third flt since obtaining his com'l plt certificate from a designated p.e. the acft was observed to depart lawrence co. arpt and upon reaching a point over…NTSB SEA85FA056Accident · 4 fatalField investigationFinal reportGulfstream AC-680F · Central Point, ORThe plt reported a loss of power on both engs during descent to land. Aprx 3 mins prior, twr gave plt option of 'straight-in' to rwy 14 or reg pattern to rwy 32. The plt hesitated & said 'just a minute' & twr offered wind info as '210 at 13.' Plt replied,…NTSB FTW83FA299Accident · 2 fatalField investigationFinal reportAero Commander 680-F · Norman, OKThe acft crashed after starting a go-around or aborted landing at normal ok. The acft was on a x-country from dallas to wichita. There was no radio communication with the acft after it was cleared to land. The approach looked ok but on short final the acft…NTSB FTW79FA041Accident · 3 fatalClosedAero Comdr 680FP · El Reno, OKNTSB MIA78FA060Accident · 1 fatalClosedAero Comdr 680F · Fellsmere, FLNTSB SEA76A5071Accident · 1 fatalClosedAero Comdr 680FP · Fall City, WANTSB MIA76DKT48Accident · 1 fatalClosedAero Comdr 680-F · Fort Myers, FLNTSB MKC76AK036Accident · 1 fatalClosedAero-Comdr 680F · Owensville, MONTSB IAD74AI042Accident · 3 fatalClosedAero Comdr 680FP · Cynthiana, KYNTSB LAX74AL052Accident · 1 fatalClosedAero Comdr 680F · Sells, AZNTSB SEA73AS025Accident · 3 fatalClosedAero Comdr 680F · Battle Grnd, WANTSB NYC67A0140Accident · 2 fatalClosedAero Comdr 680F · Reynoldsdale, PANTSB UNK64X2195Accident · 1 fatalClosedAero Cmdr 680F · Del Cabo Baja, Mexico