NTSB investigations: Lycoming 0-320 series, CA
16 cases on aircraft whose registry engine model is Lycoming 0-320 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 per year
| 1982 | 2 |
|---|---|
| 1983 | 1 |
| 1984 | 3 |
| 1988 | 1 |
| 1990 | 3 |
| 1993 | 1 |
| 1994 | 1 |
| 1997 | 1 |
| 1999 | 2 |
| 2000 | 1 |
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\" = 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."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" = 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 LAX01LA021Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Half Moon Bay, CAA local windshear condition that exceeded the airplane's climb performance capability during landing approach and resulted in the runway overrun during an attempted go-around.NTSB LAX99LA109Accident · No injuriesLimited investigationFinal reportCessna 172P · Death Valley, CAThe pilot's use of an excessive approach reference speed and his misjudged distance/speed relationship to the runway, which resulted in a landing overrun. The pilot's failure to execute a timely go-around was also causal.NTSB LAX99LA082Accident · No injuriesLimited investigationFinal reportCessna 172L · Santa Paula, CAThe instructor pilot's misjudged altitude and speed, which resulted in a failure to attain the proper touchdown point causing an overrun and collision with a block wall. A factor was the wet runway, which may have hindered brake effectiveness.NTSB LAX97LA199Accident · No injuriesLimited investigationFinal reportCessna 172N · El Monte, CAthe student pilot's misunderstanding of the controller's clearance during an aborted touch-and-go landing.NTSB LAX94LA228Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Sonoma, CAThe pilot's failure to attain the proper touchdown point and his failure to initiate a go-around.NTSB LAX94LA086Accident · No injuriesLimited investigationFinal reportCessna 172N · El Monte, CAThe pilot's delayed decision to abort the takeoff and improper use of the airplane's throttle.NTSB LAX90LA287Accident · No injuriesLimited investigationFinal reportCessna 172P · Coalinga, CAThe failure of the student pilot to accurately interpret the wind sock, and his inadvertent attempt to perform a downwind landing.NTSB LAX90LA237Accident · No injuriesLimited investigationFinal reportCessna 172M · El Cajon, CAThe pilot-in-command's failure to abort the landing after touchdown past the touchdown zone.NTSB LAX90LA118Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Redding, CAThe pilot's decision not to use full flaps which resulted in a long landing on a wet runway.NTSB LAX89LA026Accident · No injuriesLimited investigationFinal reportBeech 23 · San Carlos, CADuring a telephone interview the pilot stated that he landed too FAR down runway 12. He said that when he considered going around, he was already committed to complete the landing. Winds at the time of the accident were reported to be from 360 degrees at 5…NTSB LAX85LA056Accident · Serious injuriesLimited investigationFinal reportGulfstream AA-5A · Llano, CAThe plt of the departing acft reported that he broadcast his intentions of takeoff & he made a 360 deg clearing turn to check for inbnd acft before beginning his takeoff roll on rwy 07. Prior to becoming airborne the plt observed an acft on short final apch…NTSB LAX84LA310Accident · No injuriesLimited investigationFinal reportGlobe GC-1B · Death Valley, CAAccording to the plt, the approach to rwy 33 was in a 'no-wind condition until about 30-40 ft AGL when a strong tail wind came up.' He stated that it appeared that there was sufficient rwy remaining and when he realized it was too late to stop or go around he…NTSB LAX84LA212Accident · No injuriesLimited investigationFinal reportCessna 172P · Pacoima, CADuring the overflight of the uncontrolled field, both plts noticed that the wind tee indicated rwy 12 as the landing direction. During landing, the acft floated & touched down about 2/3 down the rwy. The acft struck a fence & trees at the end of the rwy.…NTSB LAX83LA187Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Fair Oaks, CAThe acft collided with terrain when it overran the runway on a pleasure flight. Night visual meteorological conditions prevailed. The pilot stated that upon arrival he was unable to see the 'wind indicator', however, when he saw an acft land to the north he…NTSB LAX82DUQ18Accident · No injuriesFinal reportCessna 172N · Burbank, CAPilot doing touch and go cut off carb. Heat waited for full flap retraction then added power for takeoff. When plane did not climb out of ground effect he closed throttle, landed, and ground looped into wall to avoid blast fence head on.NTSB LAX82DA319Accident · No injuriesFinal reportPiper PA-28-140 · Twenty-Nine Pal, CAWhile preparing to takeoff, the pilot taxied to a position near the midpoint of runway 8/26 where it intersected with a 750 ft taxiway. At that point, the taxiway angled toward the south-southwest to the north end of runway 17/35. The pilot mistook the…