Fatal NTSB investigations: Continental O-470 series, 2003
19 cases on aircraft whose registry engine model is Continental O-470 series. 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 | 9 |
|---|---|
| 1965 | 5 |
| 1966 | 2 |
| 1967 | 10 |
| 1968 | 2 |
| 1969 | 6 |
| 1970 | 7 |
| 1971 | 2 |
| 1972 | 5 |
| 1973 | 4 |
| 1974 | 2 |
| 1975 | 4 |
| 1976 | 6 |
| 1977 | 10 |
| 1978 | 25 |
| 1979 | 15 |
| 1980 | 12 |
| 1981 | 12 |
| 1982 | 15 |
| 1983 | 19 |
| 1984 | 16 |
| 1985 | 12 |
| 1986 | 13 |
| 1987 | 12 |
| 1988 | 6 |
| 1989 | 8 |
| 1990 | 9 |
| 1991 | 10 |
| 1992 | 6 |
| 1993 | 6 |
| 1994 | 7 |
| 1995 | 9 |
| 1996 | 3 |
| 1997 | 3 |
| 1998 | 8 |
| 1999 | 10 |
| 2000 | 3 |
| 2001 | 8 |
| 2002 | 11 |
| 2003 | 19 |
| 2004 | 15 |
| 2005 | 7 |
| 2006 | 16 |
| 2007 | 19 |
| 2008 | 5 |
| 2009 | 11 |
| 2010 | 5 |
| 2011 | 12 |
| 2012 | 7 |
| 2013 | 7 |
| 2014 | 6 |
| 2015 | 12 |
| 2016 | 8 |
| 2017 | 4 |
| 2018 | 5 |
| 2019 | 7 |
| 2020 | 3 |
| 2021 | 6 |
| 2022 | 4 |
| 2023 | 5 |
| 2024 | 6 |
| 2025 | 2 |
| 2026 | 4 |
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 year(c.\"eventDate\") = 2003
AND c.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17026'))
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") = 2003
AND c."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17026'))
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 FTW04FA044Accident · 1 fatalField investigationFinal reportBeech H-35 · Mena, ARThe pilot's failure to maintain proper altitude and clearance from terrain. Contributing factors were the mountainous terrain, fog, clouds, and turbulence.NTSB FTW04FA025Accident · 2 fatalField investigationFinal reportBeech A45 · Montgomery, TXThe non-compliance with applicable Airworthiness Directives which required wing spar inspections, and the continued operation of the aircraft beyond the compliance time extension granted as per the approved alternate means of compliance (AMOC). Also causal…NTSB NYC04FA033Accident · 2 fatalField investigationFinal reportCessna 180 · Westerly, RIThe Piper pilot's improper decision to continue a landing on an occupied runway, which resulted in an in-flight collision with the departing Cessna. Factors related to the accident were the departing Cessna pilot's inattentive radio communications, and the…NTSB SEA03LA190Accident · 2 fatalLimited investigationFinal reportCessna 182 · Challis, IDThe pilot's failure to maintain clearance from trees while maneuvering. Factors include mountainous terrain and trees.NTSB CHI03FA251Accident · 1 fatalField investigationFinal reportCessna 182G · Topeka, KSThe pilot's failure to maintain adequate airspeed resulting in a stall during takeoff. Contributing factors were the low altitude he was at during the takeoff, and the trees.NTSB DEN03FA137Accident · 1 fatalField investigationFinal reportCessna 182P · Antonito, COThe pilot's improper in-flight planning/decision and his failure to maintain clearance from the trees. Factors contributing to the accident were the low altitude, the trees, and the mountainous terrain.NTSB LAX03FA224Accident · 1 fatalField investigationFinal reportCessna 182Q · Saugus, CAin-flight collision with terrain for undetermined reasons.NTSB ANC03LA067Accident · 3 fatalLimited investigationFinal reportCessna 180 · Anchor Point, AKAn in-flight collision with water for an undetermined reason.NTSB FTW03FA174Accident · 1 fatalField investigationFinal reportCessna 182H · Cushing, OKThe pilot's failure to maintain airspeed which resulted in an inadvertent stall/spin.NTSB MIA03FA124Accident · 5 fatalField investigationFinal reportCessna 172N · Deerfield Beach, FL**This case was revised 6/10/2005 and 2/24/2016. Refer to the public docket for this accident for details.** The failure of the pilot of N4903F, the Cessna 172, and the pilot of N759XA, the Cessna 182, to see and avoid each other while operating in Class E…NTSB CHI03FA141Accident · 1 fatalField investigationFinal reportCessna 182Q · Gettysburg, SDThe pilot not maintaining aircraft control in cruise flight leading to his inadvertent spiral. A factor was the pilot's in-flight encounter with moderate to heavy rain.NTSB SEA03FA092Accident · 1 fatalField investigationFinal reportCessna 180H · Yellow Pine, IDThe pilot's failure to maintain clearance while maneuvering. Trees, a box canyon and rising terrain were factors.NTSB IAD03FA053Accident · 3 fatalField investigationFinal reportBeech 24R · Wauseon, OHThe pilots failure to maintain control during the approach-to-landing. Factors were the high wind gusts and turbulence, and the pilot's decision to fly in those conditions.NTSB ATL03FA075Accident · 2 fatalField investigationFinal reportCessna 180 · Oxford, ALThe pilot's continued VFR flight into IMC conditions and his failure to maintain obstacle clearance. A factor was low ceilings.NTSB LAX03FA116Accident · 1 fatalField investigationFinal reportCessna 182G · Santa Maria, CAthe pilot's failure to maintain proper runway alignment during the takeoff ground roll, which resulted in the left wing contacting the brush lining the runway edge. The combined effects of the brush and tree contact retarded the airplanes acceleration and…NTSB CHI03FA088Accident · 1 fatalField investigationFinal reportCessna 182R · North English, IAThe pilot's failure to maintain adequate airspeed which resulted in a stall. Contributing to the accident was the CFI's improper decision to attempt to takeoff from a short, grass taxiway instead of departing from a runway aligned with the prevailing winds,…NTSB NYC03FA058Accident · 1 fatalField investigationFinal reportCessna 182G · Renfrew, PAThe pilot's failure to maintain control of the airplane while maneuvering to land. Factors in the accident were the pilot's decision to fly into forecasted\known icing conditions, and the accumulation of structural ice.NTSB NYC03LA054Accident · 1 fatalLimited investigationFinal reportCessna 182P · So. Charleston, WVThe pilot's failure to perform a go-around prior to touchdown. Factors in the accident were the rising terrain and tail wind.NTSB LAX03FA066Accident · 2 fatalField investigationFinal reportCessna 182H · Parker, AZfailure of both pilot's to see and avoid one another while maneuvering in the traffic pattern. A factor in the accident was the inability of the Cessna pilot to communicate on the CTAF frequency due to the limitations of his radios.