Fatal NTSB investigations: Aero Commander 680FL
20 cases on aircraft the registry lists as Aero Commander 680FL. 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
| 1965 | 1 |
|---|---|
| 1967 | 1 |
| 1968 | 1 |
| 1970 | 1 |
| 1973 | 1 |
| 1978 | 2 |
| 1979 | 1 |
| 1980 | 3 |
| 1981 | 1 |
| 1983 | 1 |
| 1985 | 1 |
| 1986 | 2 |
| 1988 | 1 |
| 1992 | 1 |
| 1998 | 1 |
| 2010 | 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 ('0141608'))
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 ('0141608'))
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 WPR11FA078Accident · 1 fatalField investigationFinal reportAero Commander 680FL · Perris, CAThe pilot’s decision to continue visual flight into instrument meteorological conditions, which resulted in an in-flight collision with mountainous terrain.NTSB SEA98FA100Accident · 1 fatalField investigationFinal reportAero Commander 680FL · Helena, MTThe pilot's failure to maintain the correct altitude while turning inbound during a procedure turn to the ILS final approach course. Factors include hilly/mountainous terrain and clouds in the area where the course reversal was performed.NTSB SEA93FA046Accident · 1 fatalField investigationFinal reportAero Commander 680FL · Lester, WAUndetermined.NTSB SEA88FA069Accident · 2 fatalField investigationFinal reportAero Commander 680FL · Soda Springs, IDWhile en route on a night IFR cargo flt, the plt reqd & was clrd for a dscnt from an IFR cruise alt of 16,000 ft to proceed vfr-on-top. The last transmission from the acft was at 2106 when the plt acknowledged that he was familiar with the terrain along the…NTSB NYC86FA201Accident · 1 fatalField investigationFinal reportAero Commander 680FL · Duxsbury, VTThe plt was on a VFR flight from montpelier, VT to burlington, VT; a distance of about 80 mis. A mountain range is between the two location. Shortly after takeoff the plt radioed burlington approach control and requested an IFR clearance to land at…NTSB MKC86FA101Accident · 1 fatalField investigationFinal reportAero Commander 680FL · Grand Island, NEThe twin eng acft crashed and burned 4 miles north of the arpt while on an instrument apch. The plt had transmitted that he had an engine problem. The #5 cylinder was found detached from the left engine but the left propeller was not feathered. An engine…NTSB DEN85FA240Accident · 1 fatalField investigationFinal reportAero Commander 680FL · Fort Collins, COThe plt was operating his acft under the rules of 14 CFR 135, I.e., a scheduled domestic cargo flt. He made a normal departure and climb en route to salt lake city, Utah. Normal communications and radar flt following was established with denver ARTCC.…NTSB DEN83FA131Accident · 2 fatalField investigationFinal reportAero Commander 680FL · Monticello, UTThe acft crashed while doing magnetometer surveys at low altitude. The right engine had lost power then regained it for a short period and lost it again. A videotape in the acft recorded the plt saying, 'I changed that # just in time.' The acft yawed and the…NTSB MIA81FA105Accident · 4 fatalClosedAero Comdr 680FL · St.Croix, VINTSB ANC81DA013Accident · 1 fatalClosedAero Comdr 680-FL · Gambell, AKNTSB CHI80FA067Accident · 1 fatalClosedAero Comdr 680FL · Chicago, ILNTSB MIA80FA032Accident · 2 fatalClosedAero Comdr 680FL · Sebring, FLNTSB NYC79FA082Accident · 3 fatalClosedAero Comdr 680FL · Rexville, NYNTSB MIA78DA115Accident · 2 fatalClosedAero Comdr 680F · Ngreat Inagua (Atlantic Ocean)NTSB IAD78FA041Accident · 4 fatalClosedAero Cmdr 680FL · Morrisville, NCNTSB LAX74AL027Accident · 1 fatalClosedAero Comdr 680FL · Van Nuys, CANTSB NYC71AN007Accident · 3 fatalClosedAero Comdr 680-FL · Butler, PANTSB FTW69A0005Accident · 1 fatalClosedAero Comdr 680-FL · Paris, TXNTSB NYC68A0027Accident · 1 fatalClosedAero Comdr 680-FL · Greenland Ice Cap, GreenlandNTSB ANC66A0009Accident · 4 fatalClosedAero Comm 680 · Lk.Tustumena, AK