NTSB investigations: Lycoming 0-320 series, NC
11 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Loss of control - on ground/water”. 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 | 1 |
|---|---|
| 1986 | 1 |
| 1993 | 1 |
| 1998 | 2 |
| 2001 | 1 |
| 2002 | 2 |
| 2003 | 2 |
| 2006 | 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\" = 'NC' 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\" = 260))
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" = 'NC' 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" = 260))
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 ATL07CA022Accident · No injuriesData collectionFinal reportCessna 172N · Reidsville, NCThe pilot's failure to maintain directional control of the airplane during landing roll, which resulted in an on ground collision with trees.NTSB ATL04LA040Accident · No injuriesLimited investigationFinal reportCessna 172 · Hickory, NCThe CFI inadequate supervision, and failure to maintain directional control during the attempted touch-and-go landing.NTSB ATL04LA018Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Sanford, NCThe student pilot's failure to maintain directional control on landing roll resulting in a collision with a ditch, and subsequent nose over.NTSB MIA02LA158Accident · No injuriesLimited investigationFinal reportCessna 172N · Tarboro, NCThe failure of the solo student to maintain directional control of the airplane during the takeoff roll/run which resulted in the airplane veering off the runway and impacting trees, incurring substantial damage.NTSB ATL02LA039Accident · No injuriesLimited investigationFinal reportCessna 172M · Sanford, NCThe pilots failure to maintain directional control during landing roll that resulted in a collision with an airport sign. Factors were wet runway surface and wind gust.NTSB ATL02LA001Accident · No injuriesLimited investigationFinal reportCessna 172 · Goldsboro, NCThe student pilot's failure to maintain directional control during a touch-and-go landing.NTSB ATL98LA132Accident · No injuriesLimited investigationFinal reportCessna 172P · Farmville, NCThe pilot's failure to maintain directional control of the aircraft and his improper use of the brakes, which led to the aircraft departing the left side of the runway. Contributing factors were the wet runway and the vehicle.NTSB MIA98LA208Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Carthage, NCThe failure of the pilot to maintain directional control of the airport resulting in the collapse of the nose and left main landing gears.NTSB ATL93LA130Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Poplar Branch, NCThe pilot's failure to maintain directional control during landing.NTSB ATL86LA078Accident · No injuriesLimited investigationFinal reportCessna 172N · Washington, NCThe student pilot stated that the aircraft encountered a gust of wind during landing flare causing the aircraft to drift to the left upon touchdown. In an attempt to correct for the drift the student pilot applied left brake pressure as well as left rudder…NTSB ATL82FA224Accident · No injuriesField investigationFinal reportCessna 172 · Mt Airy, NCAfter arriving at the destination, the pilot landed on runway 36 with a westerly wind at about 7 gusting 10 KTS. After touchdown, the plane veered to the right, hit a ditch and was damaged. A post crash examination revealed no discrepancies with the braking…