Fatal NTSB investigations: Continental O-470 series, OR
14 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
| 1976 | 1 |
|---|---|
| 1984 | 1 |
| 1987 | 3 |
| 1989 | 1 |
| 1990 | 2 |
| 2001 | 1 |
| 2004 | 1 |
| 2006 | 1 |
| 2010 | 1 |
| 2011 | 2 |
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.\"eventStateOrRegion\" = 'OR' AND c.\"eventCountry\" = 'USA'
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 c."eventStateOrRegion" = 'OR' AND c."eventCountry" = 'USA'
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 WPR12FA021Accident · 1 fatalField investigationFinal reportCessna 182R · Lexington, ORThe pilot’s failure to maintain situational awareness and terrain clearance on a dark night during the approach to landing.NTSB WPR11FA116Accident · 3 fatalField investigationFinal reportCessna 182K · Adrian, ORThe non-instrument-rated pilot did not maintain sufficient altitude to clear mountainous terrain while in cruise flight in the dark.NTSB WPR10GA113Accident · 2 fatalFinal reportCessna 182R · Corvallis, ORThe pilot’s failure to maintain clearance from terrain while operating into a known area of mountain obscuration due to low clouds, precipitation, and mist.NTSB SEA06FA119Accident · 4 fatalField investigationFinal reportCessna 180 · Agness, ORThe pilot's failure to maintain obstacle clearance while maneuvering at low altitude, which resulted in an in-flight collision with a tree and subsequent collision with rocky terrain. A contributing factor was the sun glare.NTSB SEA04FA060Accident · 3 fatalField investigationFinal reportCessna 182Q · Santiam Junc., ORThe pilot's failure to maintain adequate airspeed which resulted in a stall while attempting a low-level crossing of a ridge from the leeward to the windward side. Factors include low-level maneuvering, strong gusty winds, and downdrafts.NTSB SEA01LA170Accident · 1 fatalLimited investigationFinal reportCessna 182J · Gold Beach, ORThe pilot's failure to attain proper alignment while on final approach and clearance from trees. The pilot's lack of total experience in this type of mountain flying operation was a factor.NTSB SEA91FA038Accident · 2 fatalField investigationFinal reportCessna 182B · Estacada, ORA power loss due to carburetor ice, and missing muffler cones as a result of inadequate maintenance inspection. In addition, the pilot failed to maintain adequate airspeed during the forced landing which resulted in a stall.NTSB SEA90FA064Accident · 3 fatalField investigationFinal reportCessna 182M · North Bend, ORThe pilot did not follow the published IFR procedure.NTSB SEA89FA183Accident · 3 fatalField investigationFinal reportCessna 182F · Diamond Lake, ORImproper inflight planning and decision by the pilot in command who continued VFR flight into IMC conditions while attempting to fly through a mountain pass. Contributing factors were the low ceiling and rain weather conditions and the mountainous, hilly…NTSB SEA88FA034Accident · 3 fatalField investigationFinal reportCessna 182J · Molalla, ORThe recently certificated, non-instrument rated, pvt plt flew into the an area of low ceilings, low vis, rain & snw w/o filing a flt plan. No record of a wx briefing was fnd. A surviving pax rprtd that drg flt, the plt flew into clds that were initially…NTSB SEA88FA011Accident · 3 fatalField investigationFinal reportCessna 180K · Walton, ORWitnesses observed the aircraft flying westbound toward a pass at a low altitude above the ground near the base of low stratus clouds. The aircraft struck a tree at the top of a ridgeline in mount/hilly terrain on a northeasterly heading, traveled 1/2 mile…NTSB SEA87FA060Accident · 2 fatalField investigationFinal reportCessna 182 · North Bend, ORPlt was inbound to VORTAC in clouds for localizer approach to rwy 4. Wx at arpt reporting 1500 ft bkn. Plt expected to make missed approach to continue VFR to another arpt. Plt reported inbound in and out of clouds at 1300 ft. acft crashed 4 NM beyond arpt,…NTSB SEA85FA012Accident · 4 fatalField investigationFinal reportCessna 182B · Tiller, ORThe acft collided with rising terrain about 1800 ft below the crest of a ridge while on a personal flt in wx which had multiple cloud layers obsuring the mountains. A cap acft on a search mission in the same area at the aprx time reported multiple cloud…NTSB SEA76AS053Accident · 1 fatalClosedCessna 182P · Klamath Falls, OR