NTSB investigations: Lycoming 0-320 series, CT
92 cases on aircraft whose registry engine model is Lycoming 0-320 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 | 1 |
|---|---|
| 1965 | 3 |
| 1966 | 5 |
| 1967 | 4 |
| 1968 | 2 |
| 1969 | 4 |
| 1970 | 4 |
| 1971 | 3 |
| 1972 | 1 |
| 1973 | 3 |
| 1974 | 3 |
| 1975 | 2 |
| 1976 | 3 |
| 1977 | 1 |
| 1979 | 3 |
| 1980 | 1 |
| 1983 | 2 |
| 1984 | 2 |
| 1986 | 1 |
| 1987 | 4 |
| 1991 | 2 |
| 1993 | 2 |
| 1994 | 1 |
| 1995 | 2 |
| 1996 | 2 |
| 1998 | 1 |
| 1999 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2003 | 1 |
| 2004 | 3 |
| 2006 | 3 |
| 2007 | 1 |
| 2011 | 4 |
| 2012 | 1 |
| 2013 | 1 |
| 2014 | 2 |
| 2017 | 2 |
| 2018 | 4 |
| 2019 | 1 |
| 2022 | 1 |
| 2024 | 1 |
| 2025 | 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\" = 'CT' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41508'))
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" = 'CT' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41508'))
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 ERA26LA033Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Oxford, CTThe pilot’s failure to compensate for gusty crosswind conditions, which resulted in a loss of control of the airplane and subsequent collision with terrain.NTSB ERA25LA361Accident · Minor injuriesClass 3 · LimitedPreliminary reportCessna 172K · Salisbury, CTOn September 20, 2025, about 1733 eastern daylight time, a Cessna 172K, N78938, was substantially damaged when it was involved in an accident near Salisbury, Connecticut. The flight instructor and pilot receiving instruction sustained minor injuries. The…NTSB ERA24LA241Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172 · Terryville, CTA total loss of engine power for undetermined reasons.NTSB ERA22LA152Accident · No injuriesClass 4 · LimitedFinal reportAmerican Champion 7GCBC · Plainville, CTThe pilot’s failure to maintain directional control during the landing roll.NTSB GAA20CA094Accident · Minor injuriesData collectionFinal reportPiper PA28 · Simsbury, CTThe automobile driver's incursion onto an active runway, which resulted in a collision with a landing airplane.NTSB ERA19LA030Accident · Minor injuriesLimited investigationFinal reportPiper PA28 · Simsbury, CTMaintenance personnel's inadequate inspection of the wheel brake system during the airplane's most recent 100-hour inspection, which resulted in a loss of hydraulic fluid and the pilot's inability to control the airplane during the landing.NTSB ERA18FA189Accident · 1 fatalField investigationFinal reportRutan Defiant · Plainville, CTThe pilot's loss of airplane control during climb for reasons that could not be determined based on the available information.NTSB WPR18LA173Accident · No injuriesClass 3 · LimitedFinal reportPiper PA 28-140 · Hartford, CTA loss of engine power for undetermined reasons because postaccident examination of the engine and fuel system did not reveal any anomalies that would have precluded normal operation, which led to the pilot’s forced landing and subsequent runway overshoot and…NTSB ERA18LA071Accident · Serious injuriesLimited investigationFinal reportPiper PA28 · Meriden, CTThe pilot's inadequate preflight fuel planning and his improper in-flight decision-making, which resulted in a total loss of engine power due to fuel exhaustion.NTSB GAA17CA530Accident · Minor injuriesData collectionFinal reportCessna 172 · Plainville, CTThe pilot’s failure to properly execute the go-around, which resulted in the airplane failing to maintain a climb, which resulted in collision with a tree.NTSB ERA17FA272Accident · 1 fatalField investigationFinal reportCessna 172 · New Milford, CTThe flight instructor's failure to ensure that the wing flaps were properly configured for takeoff, which resulted in an aerodynamic stall and loss of control during the initial climb.NTSB ERA14CA430Accident · Minor injuriesData collectionFinal reportCessna 172M · Watertown, CTThe pilot's decision to takeoff from a field which resulted in a collision with trees and the ground. Contributing to the accident was the pilot's failure to correctly identify the destination airport and runway, which resulted in an off-airport landing in…NTSB ERA14CA314Accident · No injuriesData collectionFinal reportCessna 172L · Danbury, CTThe pilot's use of a person unfamiliar with aviation and his failure to properly secure the airplane during hand starting of the engine.NTSB ERA13LA116Accident · Minor injuriesLimited investigationFinal reportRobinson Helicopter R22 Beta · Ellington, CTThe separation of the collective push-pull tube and jackshaft assembly, which resulted in the total loss of helicopter control and collision with terrain. Contributing to the accident was the inadequate supervision of maintenance personnel by the operator…NTSB ERA12FA483Accident · 1 fatalField investigationFinal reportCessna 172P · Plainville, CTThe pilot's failure to maintain the proper glidepath during final approach in visual meteorological conditions, resulting in collision with a berm.NTSB ERA11IA320Incident · No injuriesIncident investigationFinal reportRobinson Helicopter R22 Mariner · Redding, CTThe pilot's inadequate helicopter preflight inspection and the mechanic’s inadequate annual inspection, both of which failed to detect a worn bolt in the tail rotor teeter hinge prior to its fracture due to fatigue.NTSB ERA11LA264Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Meriden, CTMaintenance personnel's inadequate inspection of the main landing gear, which resulted in a failure of the right main landing gear’s inboard torque link lug due to a fatigue fracture. Contributing to the accident was owner's lack of compliance with a factory…NTSB ERA11CA187Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Oxford, CTThe student pilot's inadequate landing flare and the certified flight instructor's inadequate remedial action, resulting in a hard landing.NTSB ERA11CA138Accident · No injuriesData collectionFinal reportCessna 172 · Meriden, CTThe student pilot's loss of directional control during the landing rollout, resulting in a runway excursion.NTSB NYC07CA235Accident · No injuriesData collectionFinal reportCessna 172 · Meriden, CTThe student pilot's inadequate recovery from a bounced landing.NTSB NYC07CA045Accident · No injuriesData collectionFinal reportPiper PA-28-151 · Danbury, CTThe student pilot's inadequate recovery from a bounced landing, which resulted in a hard landing.NTSB NYC06CA057Accident · No injuriesData collectionFinal reportPiper PA-28-161 · New Haven, CTThe student pilot's improper flare and inadequate recovery from a bounced landing, which resulted in a loss of aircraft control during landing and subsequent impact with a ditch.NTSB NYC06CA056Accident · Serious injuriesData collectionFinal reportPiper PA-28-140 · East Killingly, CTThe flight instructor's delayed decision to discontinue the simulated forced landing, which resulted in a collision with trees.NTSB NYC05FA005Accident · 2 fatalField investigationFinal reportPiper PA-28-161 · Madison, CTA loss of engine power due to separation of the propeller due to under-torqued retention bolts.NTSB NYC04CA104Accident · No injuriesData collectionFinal reportCessna 172N · Bridgeport, CTThe pilot's inadequate compensation for wind conditions and his failure to maintain aircraft control which resulted in a hard landing. A factor was the gusty winds.NTSB NYC04FA056Accident · Serious injuriesField investigationFinal reportPiper PA-28-151 · Danbury, CTThe loss of engine power for undetermined reasons, and the pilot's failure to maintain adequate airspeed.NTSB NYC03LA064Accident · No injuriesLimited investigationFinal reportPiper PA-22/20-150 · South Woodstock, CTThe pilot's failure to maintain directional controlNTSB NYC01LA219Accident · No injuriesLimited investigationFinal reportCessna 172M · Danbury, CTAn inoperative airspeed indicator and the pilot's improper recovery from the bounced landing.NTSB NYC00LA151Accident · No injuriesLimited investigationFinal reportMeadows Pitts Special S-1 · Meriden, CTThe pilot's loss of control of the airplane during the landing roll, due to his locking of the brakes.NTSB NYC99FA097Accident · 1 fatalField investigationFinal reportIves Sonerai II-L · Eastford, CTInadequate welding of the airplane's spar-box by the owner/builder, which resulted in a total spar-box failure in-flight. A factor in the accident was the pilot's decision to perform aerobatics.NTSB IAD98LA108Accident · No injuriesLimited investigationFinal reportPiper PA-18-150 · Oxford, CTThe pilot's inability to maintain directional control during the landing roll due to separation of the tailwheel spring assembly.NTSB NYC97LA033Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Ellington, CTice ingestion into the engine from the carburetor air box, which resulted in a loss of engine power and a subsequent forced landing, off airport, on unprepared terrain.NTSB NYC96LA133Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Bridgeport, CTthe student pilot's improper flare and improper recovery from a bounced landing, which resulted in a hard landing.NTSB NYC96LA033Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Meriden, CTThe pilot's improper flare and improper recovery from a bounced landing. The unfavorable wind condition was a related factor.NTSB NYC95LA135Accident · No injuriesLimited investigationFinal reportCessna 172M · Bridgewater, CTthe loss of engine power for undetermined reasons resulting in a forced landing, and a subsequent collision with trees.NTSB NYC94LA093Accident · No injuriesLimited investigationFinal reportCessna 172M · Groton, CTthe pilot's inadequate visual lookout during taxi, which resulted in the airplane's wing tip striking ground support equipment.NTSB NYC93LA136Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Voluntown, CTThe pilot's failure to achieve the proper touchdown point which resulted in an overrun of the runway and collision with trees. A factor is the pilot's improper compensation for the wind condition.NTSB NYC93LA060Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Danbury, CTThe pilot's improper emergency procedures for an engine fire during starting which resulted in the substantial damage. Factors related to the accident were the pilot's improper starting procedure and his lack of total experience.NTSB NYC91LA130Accident · No injuriesLimited investigationFinal reportRobinson R-22B · Ellington, CTThe failure of the pilot to maintain directional control, and his inadequate compensation for winds, while maneuvering close to the ground. A factor relating to the accident was the adverse wind conditions.NTSB NYC91LA106Accident · No injuriesLimited investigationFinal reportCessna 172P · Burlington, CTThe failure of the pilot to maintain directional control during the landing. Factors related to the accident were: improper use of the flight controls by the pilot, his lack of recent experience and total time, and the crosswind.NTSB NYC87LA213Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainfield, CTWhile landing in crosswind conditions, the pilot failed to compensate for the conditions and lost directional control of the aircraft. The aircraft went down an embankment, collided with a fence and then flipped inverted.NTSB NYC87LA228Accident · No injuriesLimited investigationFinal reportCessna 172 · Groton, CTThe aircraft was taxiing to the ramp after landing. While the pilot was maneuvering the aircraft into a parking space, the aircraft was positioned in such a way that the sun had blinded him temporarily. As the pilot turned the aircraft the left wing contacted…NTSB NYC87LA154Accident · No injuriesLimited investigationFinal reportCessna 172 · New Haven, CTDrg a night flt from new bedford to bridgeport, the plt enctrd visibility problems & believed that fuel consumption was higher than normal. He obtained radar vectors to New Haven. After seeing the arpt, he flew over to establish the runway pattern. However,…NTSB NYC87LA134Accident · No injuriesLimited investigationFinal reportRobinson R-22 · Ellington, CTDuring an instructional flight, the instructor pilot simulated a forced landing at about 250 feet and 60 KIAS. The student pilot at this time entered an autorotation and the helicopter started to descend. Collective was pulled but this failed to stop the…NTSB NYC86LA087Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Hartford, CTThe cross country solo flight was taking off on runway 02 at Hartford, Connecticut. The pilot performed a runup and was cleared for takeoff. The pilot attempted rotation at about 60 KIAS, but aircraft did not lift off. Trim tab was set at neutral on runup. As…NTSB NYC85LA002Accident · Minor injuriesLimited investigationFinal reportPiper PA-18-150 · Waterbury, CTAfter liftoff, the plt initiated a turn into the crosswind to maintain runway heading. As he did so, a wind gust tipped the acft in the direction of the turn. Ground contact occurred before corrective control inputs by the plt could take effect.NTSB NYC84LA173Accident · No injuriesLimited investigationFinal reportBeech B19 · Danbury, CTThe plt stated while performing the last landing of the day a gust of wind blew the left wing up as the acft was being flared. The acft landed hard and bounced back into the air. A go-around was initiated but when another taxing acft was viewed in the…NTSB NYC83LA161Accident · No injuriesLimited investigationFinal reportCessna 172P · Redding, CTThe flight originated at ramapo, NY. During a preflight check, the plt noted that the fuel gauges indicated full. When he visually checked the fuel tanks, he estimated that the fuel level in each tank was about 1 inch from being full. The fuel capacity of…NTSB NYC83FA122Accident · Serious injuriesField investigationFinal reportCessna 172N · N. Stonington, CTThe acft collided with a tree during a go-around at night following a downwind precautionary landing. During the flt the plt had noted the fuel gauges at low readings and said he suspected a 'fuel leak'. He made radio calls to try to go to an arpt before fuel…NTSB NYC81FNE06Accident · Serious injuriesClosedPiper PA-28 · Chester, CT