NTSB investigations: Continental IO-360 series
24 cases on aircraft whose registry engine model is Continental IO-360 series, where the first occurrence was “In flight collision with object”. 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
| 1982 | 1 |
|---|---|
| 1986 | 4 |
| 1987 | 2 |
| 1988 | 2 |
| 1990 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 2001 | 1 |
| 2002 | 3 |
| 2004 | 3 |
| 2005 | 1 |
| 2007 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17025', '17045')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17025', '17045')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220))
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 NYC08FA041Accident · 1 fatalField investigationFinal reportCirrus Design SR20 · New Windsor, NYThe pilot's failure to maintain the proper glidepath during an instrument-landing-system approach in fog. Contributing to the accident were pilot fatigue and air traffic control's failure to issue a minimum safe altitude warning.NTSB ANC07LA108Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Bethel, AKThe pilot's failure to maintain clearance from trees while landing.NTSB DFW05FA192Accident · 2 fatalField investigationFinal reportAero Commander 112 · Junction, TXThe pilot's failure to attain the proper climb rate resulting in the airplane's wing colliding with a tree and subsequent impact with the ground. Contributing factors were the pilot's improper use of the airplane's flaps, and the rising terrain.NTSB ATL05FA034Accident · 3 fatalField investigationFinal reportDiamond DA40-180 · Pelzer, SCThe pilot's failure to follow IFR procedures and to maintain assigned altitude resulting in a collision with a transmission wire and trees.NTSB LAX04CA309Accident · Minor injuriesData collectionFinal reportCessna 172S · Willits, CAthe pilot's inadvertent descent and controlled flight into obstacles while maneuvering to land. Contributing factors were the dark, nighttime condition, which impaired the pilot's visual perceptions, and the pilot's failure to obtain a pertinent Notice to…NTSB NYC04FA127Accident · 1 fatalField investigationFinal reportMooney M20J · Oxford, CTThe pilot's failure to maintain altitude/clearance during an instrument approach, which resulted in a collision with trees prior to the runway. Factors were nighttime conditions and cloud cover.NTSB SEA02LA181Accident · Minor injuriesLimited investigationFinal reportCessna R172K · Shaw Island, WAThe pilot's failure to adequately compensate for ambient wind conditions. Factors include the pilot's misjudgment of distance/altitude, gusting crosswinds, and trees growing near the edge of the airstrip.NTSB NYC02LA113Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-200 · Gettysburg, PAThe pilot's failure to accurately compute takeoff performance and his failure to establish a positive climb resulting in a collision with trees.NTSB MIA02LA085Accident · 1 fatalLimited investigationFinal reportGrote Cruiser TR-4 · Pembroke Pines, FLthe pilot-in-command delayed initiating a go-around and failed to obtain sufficient altitude to clear obstacles at the departure end of the airport which resulted in an in-flight collision with power lines.NTSB LAX01LA205Accident · No injuriesLimited investigationFinal reportCessna 337G · Temecula, CAThe pilot's intentional flight into adverse weather while operating under visual flight rules, his failure to maintain a cruising altitude sufficient to remain clear of power transmission wires, and his failure to maintain a visual lookout sufficient to see…NTSB NYC98LA110Accident · 1 fatalLimited investigationFinal reportCessna 337B · Montgomery, NYthe pilot's improper decision to initiate a takeoff with the rear engine inoperative, which resulted in an airplane that could not climb sufficiently to clear obstacles (trees).NTSB FTW98LA083Accident · Serious injuriesLimited investigationFinal reportCessna R172K · Lakeview, ARthe pilot's failure to maintain runway alignment during the approach, and his delayed decision to execute a go-around. A related factor was the sunglare interfering with the pilot's view.NTSB SEA93LA114Accident · No injuriesLimited investigationFinal reportMaule M-4-210C · Moscow, IDThe inadequate visual lookout by the pilot and his failure to maintain clearance from electrical transmission wires. Factors relating to the accident were the sunglare and the presence of the wires.NTSB DEN92LA053Accident · No injuriesLimited investigationFinal reportCessna R172E · Colorado Spring, COThe pilot did not maintain clearance and the airplane collided with a fence post.NTSB FTW90GA088Accident · 1 fatalFinal reportCessna 337G · Notrees, TXThe pilot's decision to continue VFR flight into known IMC.NTSB MIA88FA179Accident · 1 fatalField investigationFinal reportCessna 172K · Lake City, FLThe acft, while on a local flight, struck a telephone transmission line on the approach end of runway 1. Witnesses stated that they saw the acft takeoff to the west and make a right turn and go out of sight. Aprx three to five minutes later, they heard the…NTSB ATL88LA141Accident · No injuriesLimited investigationFinal reportCessna 170A · Athens, GAThe plt of a Cessna 170A had departed albany, GA VFR with no flt plan for Athens, GA. A Cessna R172K from the Athens airport was engaged in local flying. The 172 retd from doing airwork and was making a full stop ldg. During his landing roll the plt reptd…NTSB BFO87LA051Accident · Minor injuriesLimited investigationFinal reportMaule M-4-210C · Burnt Chimney, VAThe plt attempted to land on a 1400 ft grass airstrip. The plt later stated that during the lndg roll the passg alerted him to the fact that they would not stop on the rwy. This caused the plt to start a go-around followed by a 2nd attempt to stop. The plt…NTSB SEA87FA135Accident · 2 fatalField investigationFinal reportMaule M-4-210C · Sitka, AKPlt was on local VFR flight plan. Witnesses observed acft flying at low level along beaches. Later, witness saw smoke rising from wooded terrain about two miles inland from nearest beach. Investigation revealed no evidence of inflight failure of malfunction…NTSB MKC87LA024Accident · No injuriesLimited investigationFinal reportCessna 177XP · Camden, ARThe pilot stated he was on approach during IMC and had the airport in sight when he flew into another cloud and had started a missed approach when he collided with a tree. He completed the missed approach and diverted to monroe, LA.NTSB BFO86FID05Accident · No injuriesFinal reportMaule M-4-210C · Saluda, VAWhile on final apch, the acft struck the top side of a van which was on a road off the apch end of the rwy. Both main landing gear were sheared off and the plt landed the acft in a grass area along the side of the rwy. The plt reported that a high sink rate…NTSB SEA86FA053Accident · 1 fatalField investigationFinal reportCessna 172XP · Napa, CABefore taking off, the plt appeared to have difficulty following taxi instructions. He then took off without clearance against crossing traffic. When he returned to land, he was cleared for rgt traffic to rwy 18. The acft entered a left downwind for rwy 24…NTSB ATL86FA055Accident · 2 fatalField investigationFinal reportCessna T337B · Talladega, ALThe acft collided with trees during the final approach to landing. The light conditions were dark, skies were clear and winds were calm. Prior to the accident, the plt had landed and visited the FBO from where the acft was recently purchased to correct some…NTSB ANC82DA065Accident · No injuriesFinal reportMaule M-4-210C · Eagle River, AKThe pilot reported that he preflighted the float plane, pumped the floats, and checked for water. After the engine start, taxi, and pretakeoff checks, he set the flaps at the first notch. He aborted his first takeoff run and taxied back for a longer run. The…