NTSB investigations: Lycoming IO-320 series, SC
10 cases on aircraft whose registry engine model is Lycoming IO-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
| 1966 | 2 |
|---|---|
| 1978 | 1 |
| 1981 | 1 |
| 2003 | 1 |
| 2005 | 1 |
| 2007 | 1 |
| 2012 | 1 |
| 2021 | 1 |
| 2025 | 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\" = 'SC' 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 ('41509'))
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" = 'SC' 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 ('41509'))
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 ERA25LA153Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-30 · Anderson, SCThe pilots’ overcorrection during the landing roll which resulted in a loss of directional control and runway excursion. Contributing was the flight instructor’s inability to correct the pilot’s actions because due to brakes only being installed on the…NTSB ERA22FA047Accident · 1 fatalClass 3 · FieldFinal reportPiper PA30 · Rock Hill, SCThe pilot’s exceedance of the airplane's critical angle of attack while troubleshooting a landing gear indication, which resulted in an aerodynamic stall at low altitude.NTSB ERA12CA333Accident · Minor injuriesData collectionFinal reportLuttenbacher Kurt Bushby Mustang 2 · Kingstree, SCThe pilot’s failure to maintain airplane control during the approach to landing, which resulted in a collision with terrain short of the runway. Contributing to the accident was the pilot's lack of experience in the airplane.NTSB SEA07LA190Accident · Serious injuriesLimited investigationFinal reportChampion 7KCAB · Orangeburg, SCThe pilot's failure to maintain airspeed during go-around which resulted in a stall. The tailwind was a factor.NTSB ATL05FA043Accident · 1 fatalField investigationFinal reportPiper PA-30 · Charleston, SCThe pilot's inadequate preflight and mismanagement of the fuel supply, which resulted in fuel exhaustion.NTSB ATL04FA027Accident · 1 fatalField investigationFinal reportPiper PA-30 · Spartanburg, SCThe pilot's failure to follow IFR procedures and descent below the glide path, which resulted in an inflight collision with trees during an instrument approach. A factor was the pilot's impairment due to the sedating effects of medication.NTSB ATL81FLG11Accident · No injuriesClosedPiper PA-30 · Hilton Head Is, SCNTSB MIA78FLG17Accident · Minor injuriesClosedPiper PA-30 · Landrum, SCNTSB MIA67F0373Accident · No injuriesClosedPiper PA-30 · Greenville, SCNTSB MIA67F0252Accident · No injuriesClosedPiper PA-30 · Columbia, SC