NTSB investigations: Lycoming IO-320 series
18 cases on aircraft whose registry engine model is Lycoming IO-320 series, where the first occurrence was “Airframe/component/system failure/malfunction”. 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 |
|---|---|
| 1983 | 1 |
| 1984 | 2 |
| 1988 | 1 |
| 1989 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 1998 | 1 |
| 1999 | 2 |
| 2000 | 2 |
| 2001 | 1 |
| 2005 | 1 |
| 2006 | 2 |
| 2007 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41509')
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\" = 130))
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 ('41509')
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" = 130))
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 DEN07LA160Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Lawrence, KSTotal failure of the landing gear retraction/extension assembly. Contributing factors in this accident were worn parts in the landing gear retraction/extension assembly, and mechanical binding of the extension assembly.NTSB CHI06CA270Accident · No injuriesData collectionFinal reportDevereux Mustang II · Auburn, INThe failure of the left main landing gear attachment weld which resulted in the pilot's inablility to maintain directional control of the airplane during the landing roll.NTSB DEN06LA041Accident · Minor injuriesLimited investigationFinal reportPiper PA-30 · Greeley, COthe pilot's flight into adverse weather conditions, the airframe ice, and the wheels up landing. Factors contributing to the accident were the icing conditions, the frozen landing gear, the frozen alternate gear extension system, and the runway sign.NTSB SEA05CA183Accident · No injuriesData collectionFinal reportBellanca 7KCAB · Chiloquin, ORThe failure of the left chain link which permits the pilot to control the tailwheel, and the subsequent inability of the pilot to control the airplane during the landing roll.NTSB FTW01LA082Accident · Serious injuriesLimited investigationFinal reportChampion 7KCAB · Ragley, LAthe loose clamp (Nicopress fitting) on the elevator control cable due to inadequate quality control during the cable's manufacturing, which allowed the cable to disconnect and restricted the pilot's control of the airplane during landing.NTSB SEA00LA118Accident · No injuriesLimited investigationFinal reportBellanca 8KCAB · Bend, ORImproper preflight preflight planning/preparation by the pilot-in-command. Factors included a worn tailwheel tire and the VASI lighting system.NTSB ATL00LA073Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Key West, FLA landing gear collapse resulting from the pilot's unsuccessful attempt to complete the manual gear extension due to physical strength overload. A factor was the complete electrical system failure during cruise flight.NTSB DEN00LA013Accident · No injuriesLimited investigationFinal reportBellanca 8KCAB · Grand Junction, COA failure of the left main landing gear attachment (u-bolt) due to fatigue.NTSB FTW99LA145Accident · No injuriesLimited investigationFinal reportBellanca 8KCAB · Lufkin, TXThe loss of control due to the separation of the left main landing gear as a result of the fatigue failure of the U-bolt which attaches the landing gear to the airframe.NTSB ATL98LA118Accident · No injuriesLimited investigationFinal reportPiper PA-30-39 · Greenville, NCA loose wiring connection at the landing gear motor relay that prevented the electrical extension of the landing gear.NTSB ATL93LA049Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Crossville, TNThe pilot's failure to follow checklist procedures in that he did not utilize the alternate gear extension method when electrical power was lost. A factor was his failure to follow the checklist when he failed to turn on the generators prior to flight, which…NTSB BFO92LA129Accident · Serious injuriesLimited investigationFinal reportPiper PA-30K · Schaghticoke, NYThe loss of total engine power due to fuel starvation. Contributing to the accident was the loss of total electrical power.NTSB ATL89LA101Accident · No injuriesLimited investigationFinal reportChampion 7KCAB · Steubenville, OHThe rudder control cable failed which rendered the control surface inoperative. The loss of rudder precluded the pilot from maintaining directional control after landing.NTSB MIA88LA113Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Jupiter, FLThe plt stated that he had completed a ldg away from his home base without the gear down & locked lights being illuminated. He stated that he had assumed the lights were 'burned out'. Upon departure, he retracted the gear & flew to his home airport. Upon…NTSB MIA85LA060Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Jacksonville, FLElectrical malfunctions caused the loss of air to ground communications and acft navigational equipment. The plt became lost about 70 mi east of Jacksonville, FL. With the help of another acft the plt located the arpt and radio communications were temporarily…NTSB ATL84LA258Accident · No injuriesLimited investigationFinal reportBellanca 7KCAB · Virginia Beach, VAAfter a banner tow pick-up, rudder jammed full right. Plt applied both feet to left rudder pedal in attempt to control direction of flt. Left rudder cable then failed in overload as banner engaged power line and broke free. Directional control requirements on…NTSB NYC83FHM02Accident · 1 fatalFinal reportDial-Thorp T-18 · Morristown, NJThe plt had been active in organizing an air show, but was not considered a participant. However, his home built acft was on static display. On the 2nd day of the show, the chairman of the event gave him permission to do a fly-by. Subsequently, he initiated a…NTSB CHI82FA211Accident · No injuriesField investigationFinal reportPiper PA-30 · Vandalia, OHDuring descent at 215 mph the acft entered violent buffeting. Recovery was initiated by reducing power & the acft landed without any further incident. Examination revealed the horizontal stabilator was permanently bent downward on both sides. The acft was…