NTSB investigations: Lycoming 0-320 series, CA
41 cases on aircraft whose registry engine model is Lycoming 0-320 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 | 2 |
|---|---|
| 1983 | 2 |
| 1984 | 3 |
| 1985 | 2 |
| 1986 | 1 |
| 1987 | 2 |
| 1988 | 2 |
| 1989 | 4 |
| 1990 | 1 |
| 1991 | 1 |
| 1992 | 2 |
| 1993 | 3 |
| 1994 | 4 |
| 1995 | 1 |
| 1996 | 1 |
| 1999 | 1 |
| 2000 | 3 |
| 2001 | 1 |
| 2002 | 1 |
| 2005 | 1 |
| 2006 | 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.\"eventStateOrRegion\" = 'CA' 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')
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."eventStateOrRegion" = 'CA' 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')
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 LAX08CA020Accident · Serious injuriesData collectionFinal reportPiper PA-28-140 · Fresno, CAThe pilot's failure to maintain the proper glide path to clear objects during approach for landing.NTSB LAX07FA241Accident · 1 fatalField investigationFinal reportPiper PA-28-140 · S. Lake Tahoe, CAThe pilot's inadequate preflight planning/decision, and his failure to maintain clearance from trees during takeoff-initial climb. Contributing to the accident were turbulence, downdrafts, and rising terrain.NTSB LAX06CA125Accident · Minor injuriesData collectionFinal reportCessna 172N · Compton, CAcontrol interference by the student pilot during a go-around that resulted in an in-flight collision with power lines.NTSB LAX05LA064Accident · 1 fatalLimited investigationFinal reportJimmy Hill Lancair 235 · El Cajon, CAthe pilot's failure to maintain the proper glidepath to avoid obstacles and terrain.NTSB LAX02FA234Accident · 1 fatalField investigationFinal reportPiper PA-28-140 · Kneeland, CAThe pilot's failure to maintain clearance with the trees while executing an instrument approach. Contributing factors were the clouds and obscuration weather conditions.NTSB LAX02LA023Accident · No injuriesLimited investigationFinal reportPiper PA-18-150 · Herald, CAThe pilot's delay initiating a go-around during a downwind approach to a short runway.NTSB LAX00LA267Accident · Minor injuriesLimited investigationFinal reportPiper PA-22-160 · Lancaster, CAThe pilot's inadequate compensation for gusty winds conditions that resulted in the collision with a power line during final approach.NTSB LAX00LA152Accident · No injuriesLimited investigationFinal reportCessna 172N · Lakeport, CAThe pilot's decision to continue with a high, steep, and fast approach, which resulted in a touchdown beyond the halfway point of the runway and the inability to stop on the remaining pavement, and, his delayed decision to initiate a landing abort. Also…NTSB LAX00TA125Accident · Serious injuriesFinal reportPiper PA-18-150 · Rio Vista, CAfailure of the pilot to maintain clearance from power lines while maneuvering at a low altitude. A factor was glare from the sun.NTSB LAX99FA301Accident · 1 fatalField investigationFinal reportPiper PA-22-150 · Strathmore, CAThe failure of the pilot to maintain an adequate terrain and obstacle clearance altitude, which resulted in a collision with power transmission wires.NTSB LAX97LA079Accident · Minor injuriesLimited investigationFinal reportGrumman American AA-5A · Banning, CAThe pilot's intentional low flight in an area of foothills and canyons at an altitude insufficient to maintain clearance from obstacles.NTSB LAX95LA191Accident · Minor injuriesLimited investigationFinal reportRobinson R-22 · Redding, CAthe pilot's improper use of the flight controls. The downward-sloping terrain and the intermittent gusty wind conditions were factors in this accident.NTSB LAX94LA350Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Rescue, CAThe pilot's delayed go-around. His inadequate compensation for the wind was a factor.NTSB LAX94LA234Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Simi Valley, CAThe student pilot's failure to properly align the airplane's flightpath over the runway during initial climb. A contributing factor was the student pilot's total lack of recent flying experience.NTSB LAX94FA214Accident · 2 fatalField investigationFinal reportRobinson R-22 · Hacienda Height, CAThe pilot's selection of an en route cruise altitude which provided insufficient obstruction clearance, and his inadequate visual lookout. Factors in the night time accident were the reduced visibility as a result of the fog and haze.NTSB LAX94LA176Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Gasquet, CAThe failure of the pilot to adequately compensate for the cross- wind conditions, and to maintain proper alignment with the runway.NTSB LAX94LA061Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Panoche, CAthe pilot's improper approach speed and glide path, and his delayed initiation of a go-around. A factor in the accident was the wind shear condition created by the hills immediately off the departure end of the dirt airstrip.NTSB LAX93FA215Accident · 2 fatalField investigationFinal reportPiper PA-28-161 · Grass Valley, CAThe pilot prematurely raising the airplane's flaps at an airspeed insufficient to maintain flight which resulted in an inadvertent stall mush condition. A factor in this accident was the darkness of the night.NTSB LAX93LA092Accident · Minor injuriesLimited investigationFinal reportRobinson R-22 Beta · Watsonville, CAPilot's poor visual look-out. A factor relating to this accident was that the pilot diverted his attention.NTSB LAX93LA059Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-140 · Lost Hills, CAThe pilot's poor preflight planning/preparation, poor fuel consumption calculations, and delay in effecting any remedial action. Contributing to this accident was the pilot inadvertently becoming Lost/disoriented and the dark night.NTSB LAX92LA306Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Kernville, CAThe pilot's selection of the wrong runway; poorly planned approach; failure to attain the proper touch down point; and delay in executing the go-around. Contributing to this accident was the existing tailwind and crosswind.NTSB LAX91LA068Accident · No injuriesLimited investigationFinal reportCessna 172N · Ukiah, CAThe failure of the pilot to maintain an adequate clearance from ground obstructions. A factor in the accident was: failure of the pilot to maintain an altitude sufficient to clear all obstructions along his route of flight.NTSB LAX91FA012Accident · 1 fatalField investigationFinal reportCessna 172M · Goleta, CAThe pilot's failure to maintain proper glidepath while on final approach. A contributing factor was sunglare.NTSB LAX90LA023Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · S. Juan Batista, CAThe pilot's intentional buzzing and failure to see and avoid a guy wire.NTSB LAX89FA241Accident · 3 fatalField investigationFinal reportCessna 177 · Hesperia, CAAn inflight collision with a power line while maneuvering at low altitude shortly after departure on a dark night over an area with few ground reference lights. The reasons for the aircraft's flight path and altitude profile are undetermined. A factor in the…NTSB LAX89LA109Accident · No injuriesLimited investigationFinal reportCessna 172M · Sacramento, CAThe pilot's selection of the wrong runway for landing and his delay in initiating a go-around after landing long. Contributing factors were: light conditions as dusk and a tailwind.NTSB LAX89FA092Accident · 2 fatalField investigationFinal reportRobinson R22A · Santa Barbara, CAFailure of the pilot to maintain adequate altitude, proper airspeed for the reduced visibility, and an adequate visual outlook to avoid a collision with power transmission cable. Contributing to the accident was reduced visibility due to fog.NTSB LAX89LA004Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Auberry, CAThe pilot was unfamiliar with the area that he was attempting to land in and circled to familiarize himself with the terrain. He then made a low pass over the dirt runway and circled to land. The first attempt was discontinued because the pilot felt that he…NTSB LAX88LA214Accident · Minor injuriesLimited investigationFinal reportRobinson R22 · Bakersfield, CAWhile on an instructional flt, the CFI instructed the student to fly above the power line poles at all times. While in cruise flight the instructor was looking away when the helicopter collided with power lines. The instructor took control of the helicopter…NTSB LAX87LA258Accident · No injuriesLimited investigationFinal reportCessna 172 · Hawthorne, CADrg an apch to rwy 25, the acft collided with the omni directional apch lighting system (odals). The plt indcd that she enctrd a downdraft on short final & applied full power; however, the acft contd to dscnd & struck one of the odals light cover lenses with…NTSB LAX87LA249Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Auberry, CADuring an approach into a private airstrip, the student pilot touched-down, then decided that there was not enough stopping distance and elected to go-around. On the initial climb-out the aircraft struck an object that made the aircraft yaw right then left.…NTSB LAX86LA213Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Crescent City, CAThe pilot reported due to severe turbulence he decided to land long. Upon realizing that the airplane was too high he added full flaps. Shortly after touchdown the plt began to lose control of the airplane and elected to takeoff. During the initial climb the…NTSB LAX85LA242Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Springville, CAAfter overflying the uncharted, private airstrip & evaluating its size, the PIC attempted to land on the narrow rwy. Only about 900 ft of the rwy was usable. After touching down, the plt realized the acft could not be stopped on the remaining available strip,…NTSB LAX85LA144Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Healdsburg, CAWhile on a local flt, the acft collided with trees in a canyon. The plt reported the acft's alt was lower than anticipated & the terrain in the canyon rose rapidly. Full eng power was not sufficient to negotiate the rising terrain. The plt reported the acft's…NTSB LAX84LA446Accident · No injuriesLimited investigationFinal reportBellanca 7GCBC · Coalinga, CAThe acft struck power lines about 50 ft AGL while on a x-country. The plt made a successful landing after the collision at an arpt about 30 miles away. The plt said the accident could have been prevented by not flying so low.NTSB LAX84FA193Accident · 2 fatalField investigationFinal reportRobinson R22 · Thousand Oaks, CAThe helicopter collided with 2 cables supported by 150 ft tall twin towers. It then went out of control & crashed into a 15 ft deep drainage ditch & burned. The plt had been cited on 2/20/84 for 'careless & reckless operation of an acft.' Another person who…NTSB LAX84LA148Accident · No injuriesLimited investigationFinal reportCessna 172 · Oakland, CAThe acft collided with wires during a descent through the clouds. The student plt had found himself on top of an overcast and managed to descend through it but in doing so a power line was hit. The plt climbed back on top and continued to destination without…NTSB LAX83LA423Accident · Serious injuriesLimited investigationFinal reportCessna 172 · S. Lake Tahoe, CAAccording to tower personnel, the plt landed aprx 2000 ft down the rwy, then initiated a go-around. As the acft was climbing, the nose was in a higher than normal attitude, the airspeed was slow, and the acft drifted to the right. Subsequently, it impacted…NTSB LAX83LA344Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Columbia, CAThe acft contacted a powerline 100 ft above the water at new mellones reservoir. The acft was landed at Columbia. CA without further incident. An inspection of the acft revealed that the top portion of the vertical stabilizer was missingand the rudder was…NTSB LAX82DA326Accident · No injuriesFinal reportCessna 172M · San Jose, CAThe aircraft was substantially damaged when a landing gear, damaged by a wire strike, collapsed during landing. Witnesses indicated that the aircraft had entered a narrow valley at treetop level. Broken power lines started a grass fire which was eventually…NTSB LAX82FVD18Accident · No injuriesFinal reportCessna 172 · Mckinleyville, CAThe aircraft struck and severed 3 power lines about 3 miles south of the departure airport. Prior to the accident, it was observed flying at low altitude in the vicinity. The pilot stated that he flew by a mobile home park to verify that a trailer had been…