NTSB investigations: Continental O-470 series
105 cases on aircraft whose registry engine model is Continental O-470 series, where the first occurrence was “Overrun”. 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, newest first
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 ('17026')
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\" = 340))
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 ('17026')
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" = 340))
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 ATL93LA086Accident · Serious injuriesLimited investigationFinal reportCessna 182P · Macon, GAThe pilot's failure to attain the proper touchdown point. A factor was the pilot's failure to select another airport for landing and the intermittant runway and VASI lighting system.NTSB DEN92LA086Accident · No injuriesLimited investigationFinal reportCessna 182Q · Crested Butte, COThe pilot's selection of the wrong runway for landing, and the use of a flap setting less than a landing flap configuration.NTSB SEA92LA187Accident · No injuriesLimited investigationFinal reportCessna 182F · Alderwood Manor, WAThe pilot selected the wrong runway for wind conditions.NTSB SEA92LA176Accident · No injuriesLimited investigationFinal reportCessna 180K · Wibaux, MTA poorly planned approach.NTSB LAX92LA221Accident · No injuriesLimited investigationFinal reportCessna 182E · Lone Pine, CAThe pilot's encounter with a sudden and strong quartering tailwind after landing on a short dirt runway, and the failure of the pilot to select the other airport runway, which was longer and more aligned with the wind, for the approach and landing.NTSB DEN92FA052Accident · Serious injuriesField investigationFinal reportCessna 182 · Frederick, COThe pilot and operator attempting to operate the aircraft over maximum gross weight.NTSB SEA92LA050Accident · No injuriesLimited investigationFinal reportCessna 182D · Monroe, UTAn aborted takeoff was not performed. The wet, soft runway was a factor.NTSB CHI92LA069Accident · No injuriesLimited investigationFinal reportCessna 182 · Lake Elmo, MNThe proper touchdown point was not attained and an aborted landing was delayed by the pilot. A factor related to the accident was the icy runway conditions.NTSB ATL91LA151Accident · No injuriesLimited investigationFinal reportCessna 182L · Macon, NCThe pilot's failure to accurately judge the distance required to stop the airplane. A factor in the accident was the wet, grass runway surface at the time of the accident.NTSB FTW90LA159Accident · No injuriesLimited investigationFinal reportCessna 182N · Justin, TXThe unexpected impairment of the pilot. Factors related to the accident were: the pilot's selection of a short grass runway with a tailwind, the high air temperature, and the obstructions (fence & power line) at the end of the runway.NTSB SEA90LA015Accident · No injuriesLimited investigationFinal reportCessna 182P · Hillsboro, ORFailure of the pilot to attain the proper touchdown point or go around while there was still sufficient runway and speed remaining. The tailwind was a related factor.NTSB ATL90LA011Accident · No injuriesLimited investigationFinal reportCessna 182Q · Cumming, GAA lack of fluid in the brake system and an inadequate annual inspection.NTSB ANC89LA174Accident · No injuriesLimited investigationFinal reportCessna 180 · Redoubt Bay, AKImproper planning/decision by the pilot. Factors related to the accident were: the unfavorable runway and terrain conditions.NTSB SEA89LA069Accident · No injuriesLimited investigationFinal reportCessna 182 · Arlington, ORThe student pilot touched down too FAR down the runway to allow him to stop before running into a trailer.NTSB CHI89LA051Accident · No injuriesLimited investigationFinal reportCessna 182A · Baldwin, WIFailure of the pilot to go around when he landed long with too much speed for the conditions. Factors related to the accident were: the pilot's excessive airspeed, his failure to attain the proper touchdown point, the crosswind, snowy/icy runway conditions,…NTSB BFO88LA079Accident · No injuriesLimited investigationFinal reportCessna 180 · Harding, WVThe pilot departed morgantown, WV, en route to a private airstrip, durrett air ranch, near Harding, WV to attend a Cessna 180 fly-in. He stated he circled the airstrip to determine the wind and rwy conditions. He also called UNICOM for active rwy info but did…NTSB MIA88LA205Accident · No injuriesLimited investigationFinal reportCessna 182R · Tampa, FLThe plt rprtd that drg the takeoff roll, he 'rotated aircraft at 65 kts' but it would not become airborne. He then aborted the takeoff, but was unable to stop on the remaining rwy. After departing the rwy, the acft hit a ditch & nosed over. An exam of the flt…NTSB SEA88LA112Accident · Minor injuriesLimited investigationFinal reportCessna 182B · Athol, IDPlt landed long to avoid potential conflict with truck waiting to cross rwy. The pilot stated he experienced a tailwind after touchdown. He initiated a go-around but contacted rough terrain in overrun before becoming airborne.NTSB FTW88LA137Accident · No injuriesLimited investigationFinal reportCessna 182D · Gilmer, TXThe pilot said he made two approaches to runway 17 and two go-arounds. He said the wind then changed direction and he set-up for landing on runway 35. He said he should have gone around for the third time but instead he landed long, went through a fence and…NTSB CHI87LA181Accident · No injuriesLimited investigationFinal reportCessna 182J · Lansing, ILWhile landing on runway 27, the pilot overshot the runway and rolled into a shallow ditch.NTSB ANC87FA110Accident · Minor injuriesField investigationFinal reportCessna 182P · Anchorage, AKThere was hvy traffic when the plt of N1946M contacted Anchorage (anc) intl twr for lndg instrns at the lake hood strip. Anc twr ctld traffic at the nrby lake hood strip & lake hood seaplane base, as well as at the anc intl arpt. The wnd at lake hood had been…NTSB NYC87LA153Accident · No injuriesLimited investigationFinal reportCessna 182 · Ellington, CTThe pilot stated that while making a standard left traffic pattern, the wind at the north end of the airport shifted from the southeast to the northwest. The acft touched down with excessive ground speed, ran off the end of the rwy and came to rest on a…NTSB NYC87LA148Accident · No injuriesLimited investigationFinal reportCessna 182 · Honeoye Falls, NYThe acft was landed on a 1695 ft turf runway with dew covered grass that was aprx 3 inches tall. After touchdown, the plt applied brakes, but the acft skidded about 1000 ft, went off the dep end of the rwy & collided with a trailer. The trailer was moved…NTSB LAX87LA166Accident · No injuriesLimited investigationFinal reportCessna 310 · Agua Dulce, CAThe non-multiengine rated pilot attempted to land his multiengine airplane on a 4600 foot runway. The aircraft touched down approximately half way down the runway and slid off the departure end. The aircraft impacted trees after departing the runway.NTSB NYC87LA053Accident · Serious injuriesLimited investigationFinal reportCessna 180 · Goffstown, NHThe Cessna 180 made a touch and go on a 2100 ft long runway. The touchdown was described as past the first third of the runway. There were two rated pilots and a passenger in the aircraft. The co-pilot thought the aircraft would be unable to clear powerlines…NTSB MKC86LA141Accident · No injuriesLimited investigationFinal reportCessna 182 · Siloam Springs, ARThe PIC was practicing touch and go landings, and decided to change rwys for his final landing. The PIC stated he landed long on the 1650 foot turf rwy, but went off the end. The PIC stated he should have added pwr and made a go around. The PIC was late in…NTSB LAX86LA257Accident · No injuriesLimited investigationFinal reportCessna 182L · Lodi, CAA acft collided with a gravel pile after overrunning the 2,070 ft asphalt rwy. The plt indicated that the wind sock at the arpt was indicating a variable wind direction from 200 deg to 230 deg. The plt elected to land on rwy 12. He stated he would have had…NTSB MIA86LA140Accident · No injuriesLimited investigationFinal reportCessna 182P · Hastings, FLThe plt stated she landed long and over ran the runway. She continued to state a go-around should have been performed.NTSB CHI86FEE02Accident · Serious injuriesFinal reportCessna 182Q · Lansing, ILWhile on the return flt to Lansing, IL, the plt checked the midway ATIS for info. He believed that just before landing at the Lansing muni arpt, the wind had shifted to the east. According to witnesses, the acft touched down on the last 1/3 of the 2432 ft…NTSB LAX86LA116Accident · No injuriesLimited investigationFinal reportCessna 182M · Healdsburg, CAOn February 8, 1986, at 1430 PST a Cessna 182, N91614, overran the landing surface and nosed over at a dirt strip. VMC prevailed at the time. The winds were generally calm with sporadic gusts from the north at approximately 10 knots. There was no indication…NTSB SEA85LA200Accident · No injuriesLimited investigationFinal reportCessna 180A · Buxton, ORThe pilot misjudged his touchdown point on the 1,000 foot airstrip and had an excess of airspeed. And overrun occurred and the aircraft went down an embankment. At the time of touchdown, there was only about 4 KTS of headwind available.NTSB BFO85LA030Accident · No injuriesLimited investigationFinal reportCessna 182G · Bridgewater, VADue to excess altitude, during his 1st apch to land, the plt executed a go-around. The 2nd apch resulted in proper altitude, but high airspeed. Crosswind conditions & gusts up to 22 KTS existed at the time & touchdown occurred aprx half way down the 2755 ft…NTSB ATL84LA283Accident · No injuriesLimited investigationFinal reportCessna 182B · Kannapolis, NCThe plt reported that because of grnd fog in wilkersboro, NC, he diverted to Kannapolis, NC. Upon arriving over enochuille airport, he observed that grnd fog was present on the lake which is located adjacent to the arpt. Due to the fog, the plt elected to…NTSB ANC84LA168Accident · No injuriesLimited investigationFinal reportCessna Ector 305A · Anchorage, AKLanding area selected by plt was slick due to mud from recent tidal waters. Acft slid on touchdown and plt was unable to stop. Applied full pwr in attempt to clear a gully at end of landing area. Main gear contacted FAR edge of gully and acft nosed over.NTSB LAX84FA389Accident · 4 fatalField investigationFinal reportCessna 180 · Randsburg, CAPlt attempted to land on a 1200 ft long airstrip. He landed the acft with a tailwind and touched down aprx 600 ft from the apch end of the rwy. The acft skidded off the right side of the rwy and collided with a caterpillar tractor. The four occupants were…NTSB SEA84LA188Accident · No injuriesLimited investigationFinal reportCessna 182 · Craigmont, IDAccording to the plt, during landing the brakes failed and the acft came to a stop about 10 ft beyond the end of the rwy after rolling into a shallow ditch. Maint personnel examined the right wheel brake system and found no mechanical malfunction or leakage…NTSB MKC84LA191Accident · No injuriesLimited investigationFinal reportCessna 182N · Beaver City, NEThe acft was landed on an uncontrolled arpt toward the nnw, & after touchdown, it did not slow down adequetely. According to the plt, he elected to ground loop the acft rather than to continue off the end of the rwy. During the attempted ground loop, the acft…NTSB FTW84LA251Accident · No injuriesLimited investigationFinal reportCessna 182Q · Whitney, TXAccording to the plt, he was unable to stop the acft after landing on a 2000 ft asphalt rwy. The acft overran the end of the rwy & hit a ditch. The nose gear collapsed & the acft nosed over. The wind was reported blowing from 210 deg at 20 gusting 25 KTS.…NTSB LAX83LA465Accident · Minor injuriesLimited investigationFinal reportCessna 182P · Empire, NVThe plt said that a gust of wind blew the acft half way down the rwy. The touchdown was long and the acft ran off the end of the rwy into a dirt bank and nosed over. Winds were gusting to 20 KTS.NTSB ANC83LA160Accident · No injuriesLimited investigationFinal reportCessna 180 · Nr Anchorage, AKThe plt reported that the accident occurred when he was landing on a sandbar that he had previously used 3 times, earlier the same day. Reportedly, he overran the landing area by about 50 ft & encountered an area of soft clay & mud. The right wheel sank into…NTSB CHI83LA386Accident · No injuriesLimited investigationFinal reportCessna 182 · Joliet, ILAcft landed long & ran off the end of the rwy. The left tire blew prior to departing the rwy, & after departing the rwy the acft collided with an arpt warning sign. A 3,452 ft turf rwy, 4/22, was available.NTSB MKC83LA180Accident · No injuriesLimited investigationFinal reportCessna 182Q · Hunter, KSThe plt reported that during arrival at the private strip, his apch was a bit hi & slightly fast. While landing, the acft floated in ground effect. Subsequently, it overran the rwy & impacted a wire fence & dirt bank.NTSB CHI83LA328Accident · No injuriesLimited investigationFinal reportCessna 182Q · Turner, MIThe plt reported that during a landing, the acft touched down at about the midpoint of a 2140 ft, grass rwy. When he applied braking action, the acft skidded on the grass surface & the plt was unable to stop on the landing area. After departing the rwy, the…NTSB ATL83LA258Accident · No injuriesLimited investigationFinal reportCessna 182L · Charlotte, NCThe acft ran off the departure end of the rwy during landing. The wind was light and variable to calm. The plt used aerodynamic braking until it was too late to go around. When he applied the brakes he found that they were spongy and ineffectual. An after…NTSB LAX83LA326Accident · No injuriesLimited investigationFinal reportCessna 182Q · Buckeye, AZThe pilot stated that two attempts to land at turkey airstrip resulted in difficulty in achieving a proper final approach path. After some maneuvering on the 2nd approach the acft landed. One witness described the landing as hot with some floating and a late…NTSB ANC83LA101Accident · No injuriesLimited investigationFinal reportCessna 182 · Bettles, AKThe acft went off the departure end of the runway during a night landing and nosed over. The pilot stated that he pulledoff power for the flare and the acft seemed to gain airspeed. He decided to go-around, added full power, but saw the end of the runway and…NTSB DEN83LA126Accident · Minor injuriesLimited investigationFinal reportCessna 182Q · New Harmony, UTThe acft ran off the departure end of the rwy during landing after going through a fence/bushes and the acft nosed over. The pilot had made one go-around because of excessive airspeed. He said the windsock was limp as he obseved it. However,winds at cedar…NTSB LAX83LA118Accident · No injuriesLimited investigationFinal reportCessna 182J · Peoria, AZThe acft collided with a sign and a wall during an attempted go-around after an overrun. The pilot was practicing and had made 2 short field landings on the 3rd approach he forgot to lower flaps. His approach was fast and long and he landed too FAR down the…NTSB FTW82DA298Accident · No injuriesFinal reportCessna 182E · Albuquerque, NMThe pilot stated that after a normal approach, the aircraft touched down at about 90 mph on the first 1/4 to 1/3 of the runway. He raised the flaps and applied brakes. He noticed that there was insufficient braking action to stop on the wet runway, but by the…NTSB FTW82DA278Accident · Minor injuriesFinal reportCessna 182 · Mckinney, TXAfter a normal skydiver drop, the pilot spiraled down for a normal landing on a 2000 ft gravel runway with a powerline at the approach end. The wind was reported as variable at 5 KTS. The pilot reported that during the landing, the aircraft touched down on…