NTSB investigations: Lycoming 0-320 series
240 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 | 15 |
|---|---|
| 1983 | 22 |
| 1984 | 19 |
| 1985 | 12 |
| 1986 | 5 |
| 1987 | 6 |
| 1988 | 10 |
| 1989 | 11 |
| 1990 | 14 |
| 1991 | 10 |
| 1992 | 15 |
| 1993 | 12 |
| 1994 | 9 |
| 1995 | 7 |
| 1996 | 3 |
| 1997 | 8 |
| 1998 | 4 |
| 1999 | 8 |
| 2000 | 8 |
| 2001 | 4 |
| 2002 | 9 |
| 2003 | 9 |
| 2004 | 7 |
| 2005 | 6 |
| 2006 | 5 |
| 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 ('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."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 CHI08CA038Accident · No injuriesData collectionFinal reportPiper PA-22-150 · Plato Center, ILThe excessive airspeed used by the pilot which resulted in an overrun, impact with a ditch and subsequent nose over. The ditch was a factor.NTSB CHI07CA134Accident · Minor injuriesData collectionFinal reportCessna 172I · Shelby, OHThe pilot's failure to properly achieve the correct touch down point which resulted in a runway over run and subsequent nose over into a ditch. Other factors were the pilot's improper decision to land with a tailwind and the ditch.NTSB ATL06CA123Accident · No injuriesData collectionFinal reportCessna 172P · Chester, SCThe CFI's failure to initiate a go-around when he noticed the flight was high and fast during the approach resulting in the flight landing long, overrunning the runway, and colliding with trees. Factors in the accident were a tail wind and a wet runway.NTSB CHI06CA182Accident · No injuriesData collectionFinal reportCessna 172L · Waterford, OHThe pilot's selection of unsuitable terrain for landing. The runway's downhill slope, the wet grass, the fence, and the embankment were factors.NTSB ATL06CA084Accident · No injuriesData collectionFinal reportCessna 172L · Lexington, TNThe pilot's failure to attain the proper touchdown point during landing.NTSB ATL06CA065Accident · No injuriesData collectionFinal reportCessna 172 M · Griffin, GAThe pilot's failure to achieve the proper touchdown point, which resulted in an overrun of the runway, collision with an embankment, and subsequent nose over.NTSB MIA06CA080Accident · Minor injuriesData collectionFinal reportAero Commander 100 · Englewood, FLThe pilot's failure to abort the takeoff in time to stop on the remaining runway, which resulted in the airplane overrunning the runway.NTSB MIA06CA032Accident · No injuriesData collectionFinal reportCessna 172P · Hialeah, FLThe failure of the CFI to perform a go-around following a long landing resulting in overrun, on ground encounter with soft terrain, and subsequent nose over.NTSB NYC06CA037Accident · No injuriesData collectionFinal reportGrumman AA5A · Maceo, KYThe pilot's misjudged distance/speed, and his failure to properly seat the airplane's recently installed brakes. A factor was the quartering tailwind.NTSB CHI05CA224Accident · Minor injuriesData collectionFinal reportPiper PA-28-140 · Mount Ayr, IAThe pilot's selection of a wrong runway, and the misjudged distance/speed which resulted in an overrun. Contributing factors were the tailwind, and the ditch.NTSB ANC05CA147Accident · No injuriesData collectionFinal reportCessna 172 · Anchorage, AKThe pilot's misjudgment of distance/speed during landing, which resulted in an overrun, a loss of directional control, and a nose over during the landing roll.NTSB NYC05CA122Accident · No injuriesData collectionFinal reportGulfstream American AA-5A · Schroon Lake, NYThe pilot's misjudgment of speed/distance which resulted in an overrun.NTSB NYC05CA073Accident · No injuriesData collectionFinal reportCessna 172N · Wellington, OHThe pilot's failure to obtain the proper touchdown point, and his failure to initiate a go-around, which resulted in an overrun during landing. A factor in the accident was the tail wind.NTSB CHI05CA034Accident · No injuriesData collectionFinal reportCessna 172N · Lakeville, MNThe pilot misjudged his distance and speed which resulted in an overrun.. Factors were the wet runway, the grass and the berm.NTSB SEA04CA193Accident · No injuriesData collectionFinal reportPiper PA-28 · Deer Harbor, WAThe pilot's failure to perform remedial action during the landing sequence. A factor contributing to the accident was the wet runway surface.NTSB CHI04LA201Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Custer, SDThe pilot's poor preflight planning/preparation and the pilot used improper aborted takeoff procedures by not reducing the throttle. Factors associated with the accident were the high density altitude and the tailwind.NTSB MIA04CA118Accident · No injuriesData collectionFinal reportPiper PA-28-151 · Sugar Loaf Key, FLThe failure of the pilot to attain the proper touchdown point resulting in a landing overrun and subsequent on-ground collision with trees.NTSB MIA04CA094Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Lake Wales, FLThe pilot's delay in aborting the takeoff resulting in an overrun of the runway and subsequent impact with water. A finding in the accident was the pilot's failure to extend the flaps to the second notch (25 degrees).NTSB SEA04LA096Accident · No injuriesLimited investigationFinal reportCessna 172M · Vernonia, ORThe instructor pilot's misjudgment of speed and distance and his failure to execute a go-around resulting in an overrun of the runway.NTSB SEA04LA081Accident · No injuriesLimited investigationFinal reportCessna 172P · Battle Ground, WAThe student pilot's misjudgment of distance and his failure to do a go-around. Also causal was the instructor's inadequate supervision of the flight. Factors include gusty crosswinds, the dual student's failure to adequately compensate for those winds, a wet…NTSB NYC04CA028Accident · No injuriesData collectionFinal reportCessna 172K · Kilbourne, OHThe pilot's failure to obtain the proper touchdown point which resulted in an overrun and subsequent nose over.NTSB MIA04CA005Accident · Minor injuriesData collectionFinal reportCessna 172N · Everglades City, FLThe pilot's improper preflight planning/preparation which resulted in the airplane's gust lock being left installed, which resulted in the airplane not being able lift off during the takeoff roll, and damage to the airplane when it overran the runway and…NTSB CHI03LA250Accident · No injuriesLimited investigationFinal reportCessna 172M · La Monte, MOThe pilot's misjudgment of speed and distance resulting in an overrun of the runway.NTSB FTW03LA175Accident · Serious injuriesLimited investigationFinal reportCessna 172L · San Antonio, TXThe pilot misjudged his altitude and airspeed, and his failure to perform a go-around.NTSB SEA03LA084Accident · No injuriesLimited investigationFinal reportCessna 172 N · Center Island, WAThe pilot did not attain the proper touchdown point during landing. The pilot's diverted attention, deer near the runway, and trees were factors.NTSB FTW03LA155Accident · No injuriesLimited investigationFinal reportOMF 100-160 · San Antonio, TXThe pilot's failure to land at the proper touchdown point, which resulted in the overrun of the runway.NTSB MIA03LA098Accident · No injuriesLimited investigationFinal reportCessna 172N · Foxworth, MSThe failure of the pilot to perform a go-around, his failure to attain the proper touchdown point, and his delay in applying the normal brakes resulting in his inability to stop the airplane and subsequent on-ground collision with a fence.NTSB ATL03LA067Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Savannah, GAThe pilot misjudged the landing distance, landed with excessive airspeed, did not attempt a go-around resulting in the airplane going off the overrun, and colliding with trees.NTSB LAX03LA103Accident · No injuriesLimited investigationFinal reportPiper PA-18-150 · Chandler, AZthe CFI's inadequate supervision and delayed decision to abort the takeoff resulted in the runway overrun.NTSB NYC03LA034Accident · No injuriesLimited investigationFinal reportSocata TB 9 · Mount Union, PAThe pilot's delay in aborting the takeoff. A factor was the soft runway.NTSB CHI02LA280Accident · No injuriesLimited investigationFinal reportCessna 172P · Sturtevant, WIThe proper touchdown point not attained and the approach speed not obtained/maintained by the pilot.NTSB FTW02CA249Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Graham, TXthe pilot's failure to attain the proper touchdown point which resulted in a runway overrun.NTSB ANC02LA112Accident · No injuriesLimited investigationFinal reportPiper PA-18 · Anchorage, AKThe pilot's failure to attain the proper touchdown point on a remote airstrip, and his failure to perform a go-around that resulted in the airplane overrunning the end of the strip. Factors in the accident were the pilot's inadequate evaluation of a tailwind…NTSB CHI02LA265Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-140 · Elwood, INThe pilot's misjudgment of speed/distance and his failure to perform a go-around. The pilot's inaccurate evaluation of the wind, a tailwind, selection of the wrong runway, and wet grass are contributing factors.NTSB ANC02LA100Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Sparrevohn, AKThe pilot's inadequate evaluation of wind conditions while landing, which resulted in a downwind landing and an encounter with rough terrain when the airplane overran the intended landing area. Factors associated with the accident were a tailwind, and rough…NTSB MIA02LA132Accident · No injuriesLimited investigationFinal reportCessna 172N · Pickens, SCThe pilot's improper preflight planning/preparation that resulted in the airplane's gust lock being left installed which resulted in a loss of control during the takeoff roll and damage to the airplane when it exited the departure end of the runway and…NTSB NYC02LA064Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-140 · Argyle, NYThe pilot's improper in-flight decision to land on a contaminated runway. A factor was the contaminated runway.NTSB NYC02LA052Accident · No injuriesLimited investigationFinal reportSocata TB-9 · Marlborough, MAThe pilot's failure to achieve a proper touchdown point on the runway which resulted in an overrun. A factor was the pilot's lack of experience in short field operations.NTSB CHI02LA031Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · New Ulm, MNThe student and flight instructor not using all of the available runway, the inadequate supervision by the flight instructor and the unsuccessful remedial action by the flight instructor. The student not attaining the proper touchdown point and the plowed…NTSB ATL02LA002Accident · Minor injuriesLimited investigationFinal reportBeech 19 · St Clair Spring, ALThe pilot misjudged the touchdown point that resulted in the runway overrun.NTSB ANC01LA133Accident · No injuriesLimited investigationFinal reportPiper PA-12 · Tok, AKThe pilot's failure to abort the landing. Factors associated with the accident were the pilot's selection of an unsuitable landing area, and his failure to attain a proper touchdown point. An additional factor was a ditch.NTSB ANC01LA085Accident · No injuriesLimited investigationFinal reportCessna 172K · Wasilla, AKThe pilot's delay in aborting the takeoff roll.NTSB SEA01LA012Accident · No injuriesLimited investigationFinal reportCessna 172P · Waldron Island, WAThe pilot's improper distance/speed during the approach, which lead to an overrun during the landing roll and subsequent collision with trees. A factor was the trees beyond the upwind end of the runway.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 ATL01LA006Accident · No injuriesLimited investigationFinal reportCessna 172K · Indiantown, FLThe pilot had excessive airspeed, misjudged the landing distance, and did not perform a go-around, which resulted in a nose over. The ditch was a contributing factor.NTSB CHI00LA259Accident · No injuriesLimited investigationFinal reportCessna 172M · Harbor Springs, MIthe pilot's long touchdown, and inadequate braking to stop on the runway. Factors relating to this accident were the pilot's improper in-flight planning and decision resulting in the long touchdown, and the fence.NTSB SEA00LA125Accident · No injuriesLimited investigationFinal reportCessna 172I · Sandy, ORThe pilot's failure to attain the proper touchdown point for landing, and his failure to go around from the improperly executed approach. Factors included the pilot's failure to attain the proper glidepath on the approach, a short landing runway, and…NTSB CHI00LA192Accident · No injuriesLimited investigationFinal reportCreed Lancair 235 · Hot Springs, SDthe failure of the pilot to select the correct runway for takeoff. Factors to the accident were the inadequate preflight planning/preparation, the aborted takeoff not performed, and the tailwind.NTSB CHI00LA128Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Fulton, MOthe pilot's poor inflight planning which resulted in exceeded the proper touchdown point on the runway. A factor associated with the accident was the ditch that the airplane contacted.NTSB NYC00LA109Accident · No injuriesLimited investigationFinal reportCessna 172 · North Adams, MAThe pilot's failure to obtain the proper touchdown point. A factor was a tailwind.