NTSB investigations: Lycoming TI0-540 series
69 cases on aircraft whose registry engine model is Lycoming TI0-540 series, where the first occurrence was “In flight collision with object”. 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 | 4 |
|---|---|
| 1983 | 3 |
| 1984 | 5 |
| 1985 | 4 |
| 1986 | 4 |
| 1987 | 1 |
| 1988 | 2 |
| 1989 | 2 |
| 1990 | 1 |
| 1991 | 4 |
| 1992 | 2 |
| 1994 | 2 |
| 1995 | 5 |
| 1996 | 2 |
| 1998 | 1 |
| 1999 | 1 |
| 2000 | 3 |
| 2001 | 6 |
| 2002 | 2 |
| 2003 | 2 |
| 2004 | 7 |
| 2005 | 2 |
| 2006 | 2 |
| 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 ('41533')
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\" = 220))
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 ('41533')
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" = 220))
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 SEA08FA046Accident · 1 fatalField investigationFinal reportPiper PA-28-236 · Orting, WAThe pilot's failure to maintain clearance from trees while maneuvering. A contributing factor was the dark night.NTSB ATL07FA069Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300T · Andrews, NCThe pilot's misjudgment of distance and altitude during a night approach for landing, resulting in an in flight collision with wires and the ground.NTSB NYC07LA027Accident · 1 fatalLimited investigationFinal reportPiper PA-32R-300 · Williamsburg, VAThe pilot's improper decision to depart into adverse weather conditions. Contributing was the gusty wind conditions.NTSB LAX06CA084Accident · No injuriesData collectionFinal reportCessna T206H · Palo Alto, CAthe pilot's failure to maintain proper runway alignment, which resulted in a collision with multiple objects.NTSB CHI06FA032Accident · 1 fatalField investigationFinal reportAero Commander 500B · Gaylord, MIThe clearance not maintained with terrain during a nonprecision approach. Contributing factors were the ceiling, visibility, night conditions, and trees.NTSB DFW05CA077Accident · No injuriesData collectionFinal reportCessna 182 · Graham, TXThe airplane's collision with a deer during a go-around. A contributing factor was the prevailing night condition.NTSB NYC05LA040Accident · No injuriesLimited investigationFinal reportPiper PA-46-350P · Hartford, CTThe pilot's failure to maintain adequate clearance from trees during the approach to the runway. A factor related to the accident was the nighttime conditions.NTSB NYC05FA028Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Vandalia, OHThe pilot's failure to maintain adequate altitude\clearance while on approach, which resulted in an in-flight collision with trees. Factors in the accident were the fog and low ceiling conditions.NTSB ATL04LA177Accident · 2 fatalLimited investigationFinal reportPiper PA-23-250 · Lake Wales, FLThe pilot's inadequate preflight planning and preparation, and his inadequate visual lookout, which resulted in a collision with a television tower.NTSB SEA04LA180Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Picabo, IDThe pilot's failure to set the propeller control for takeoff performance needed to outclimb obstacles. The pilot's failure to use the checklist, trees, and a fence are contributing factors.NTSB FTW04FA204Accident · 6 fatalField investigationFinal reportPiper PA-60-601P · Lakeway, TXThe pilot's failure to successfully perform a short-field takeoff and his subsequent failure to maintain adequate airspeed during climbout, which resulted in an aerodynamic stall.NTSB IAD04FA030Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · Ticonderoga, NYReason for occurrence undetermined.NTSB FTW04CA061Accident · No injuriesData collectionFinal reportPiper PA-32R · Poynor, TXThe pilot's failure to maintain aircraft control while on final approach. A factor was the downdraft.NTSB CHI03LA130Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-260 · Blaney Park, MIThe pilot's failure to maintain clearance with the tree line. Factors contributing to this accident were the wind gusts and the trees.NTSB LAX03LA154Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-301T · Paulden, AZthe pilot's failure to attain and maintain the proper climb airspeed. The high density altitude condition was a factor.NTSB ANC02LA117Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Manley Hot Spgs, AKA bird strike during takeoff, which resulted in substantial damage to the right wing.NTSB MIA02FA067Accident · 1 fatalField investigationFinal reportPiper PA32R-300 · Broadway, NCThe pilot's inadequate visual lookout and his failure to maintain obstacle clearance.NTSB LAX02LA048Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Groveland, CAThe pilot's collision with an unobserved animal that entered the active runway during the dark nighttime when the pilot's visibility was diminished.NTSB FTW02LA052Accident · Serious injuriesLimited investigationFinal reportPiper PA-23-250 · Duncan, OKThe pilot's descent below the minimum descent altitude, and his failure to maintain obstacle clearance. Contributing factors were the below approach/landing minimum weather, the dark night conditions, and the inoperative REIL's.NTSB DEN01FA161Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · Pagosa Springs, COthe flight crews' intentional low altitude flight, and failure to maintain obstacle clearance.NTSB CHI01FA312Accident · Serious injuriesField investigationFinal reportPiper PA-32R-301T · Downers Grove, ILthe improper preflight planning/preparation and the short field take off/procedure not followed by the pilot. Contributing factors were the airplane's forward center of gravity, the variable gusting wind and improper weight and balance calculations by…NTSB FTW01LA158Accident · 1 fatalLimited investigationFinal reportPiper PA-32R-300 · Belle Chase, LAthe pilot's failure to maintain clearance with a utility pole while maneuvering. Contributing factors were the pilot's impairment due to alcohol intoxication and the night light conditions.NTSB CHI01LA076Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Fulton, MOthe pilot not maintaining altitude/clearance from the power line during the circling approach. Factors were the power transmission wire, the plowed field, and that the pilot's lookout was not possible through the built up ice on the windshield.NTSB CHI01LA042Accident · No injuriesLimited investigationFinal reportAerostar PA-60-601P · Preston, MNaltitude/clearance from the trees not being obtained/maintained by the pilot. Factors to the accident were the trees and the contamination of the pitot/static system.NTSB SEA00LA162Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Birkenfeld, ORThe pilot's delayed go-around, which resulted in the aircraft not clearing the fence posts. A contributing factor was the fence posts.NTSB NYC00LA065Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Harpswell, MEwas the improper decision of the pilot to depart at night, from an unlighted runway with no visual references to obstructions on the sides of the runway. Factors were the dark night conditions, and the lack of runway side lights.NTSB ANC00LA004Accident · No injuriesLimited investigationFinal reportPiper PA-31 · Soldotna, AKAn in-flight collision with a bird.NTSB CHI98LA219Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Mobridge, SDThe pilot's failure to maintain clearance from the power lines. Factors associated with the accident were the power lines, and the separation of the vertical stabilizer and rudder which resulted in the pilot's inability to maintain directional control of the…NTSB FTW97LA029Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Stanton, TXPilot's failure to maintain clearance with a wire resulting in the separation of the rudder and a loss of aircraft control.NTSB FTW96GA365Accident · 2 fatalFinal reportPiper PA-23-250 · Jennings, LAThe pilot's failure to maintain clearance. Factors were the pilot's lack of recent experience in the make and model of airplane, the dark night, and fog.NTSB ATL96LA024Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Monroe, NCThe pilot's inadequate planning and failure to follow operating procedures resulted in his descent below the decision height while on final approach.NTSB LAX96FA050Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Fullerton, CAthe pilot-in-command's failure to follow IFR procedures in that he descended below the minimum descent altitude and failed to execute a missed approach. Contributing to the accident was the pilot-in-command's self-induced pressure to get to work.NTSB FTW95FA363Accident · Serious injuriesField investigationFinal reportPiper PA-32R-300 · Wichita Falls, TXthe pilot's failure to maintain airspeed while diverting attention to an open cargo door. A factor was the pilot's inadequate preflight inspection.NTSB FTW95LA311Accident · No injuriesLimited investigationFinal reportBellanca 17-31ATC · Hico, TXThe pilot's failure to attain the proper touchdown point and the delayed go-around.NTSB SEA95LA039Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · La Grande, ORFailure of the pilot to maintain proper altitude/clearance from higher terrain that was located near the airport. Factors related to the accident were: low ceiling, fog, false/incorrect indication of the NDB, failure of other personnel to properly issue a…NTSB FTW94FA241Accident · 1 fatalField investigationFinal reportSchweizer G-164B · Foules, LAThe pilot's failure to maintain obstacle clearance.NTSB CHI94DCG02Accident · 1 fatalFinal reportAero Commander Calair A-9B · Excelsior Sprgs, MOThe pilot's failure to maintain altitude clearance above the powerlines during his maintenance test application run.NTSB LAX92LA399Accident · No injuriesLimited investigationFinal reportPiper 601P · Bakersfield, CAThe pilot's selection of an inadequate altitude for an intentional low pass. Contributing to the accident was the dusk light conditions, and the pilots improper inflight planning and decision.NTSB BFO92FA032Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Sandston, VAThe pilot's improper in-flight planning/decision failure to follow the missed approach procedure.NTSB CHI92LA026Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Charles City, IAProper glide path not maintained. Factors in the accident are the premature landing gear extension and inadequate airspeed by the pilot in command.NTSB NYC92LA020Accident · Serious injuriesLimited investigationFinal reportPiper PA-23-250 · Groton, CTThe pilot's failure to maintain the minimum descent altitude during the approach. A factor was pilot fatigue.NTSB ATL91FA047Accident · 3 fatalField investigationFinal reportPiper PA-24-260 · Cordele, GAFailure of the pilot to attain proper runway alignment and to maintain proper altitude. Related factors were: darkness and the pilot becoming lost/disoriented.NTSB ATL91FA040Accident · 4 fatalField investigationFinal reportRockwell 114 · Bessemer, ALFailure of the pilot to follow instrument flight rules (IFR) and maintain the minimum descent altitude (mda) during the VOR approach. Factors related to the accident were: darkness and the adverse weather conditions.NTSB MIA90LA160Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Plymouth, FLThe pilots decision to depart for his destination airport in the path of approaching thunderstorms resulting in the encounter with wind gusts during landing which exceeded his limitations.NTSB NYC90FA011Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Glastonbury, CTThe pilot-in-command's failure to maintain adequate altitude control during maneuvering flight. Contributing to the accident was the failure of the airplane's electrical system and the pilot's operation at night, without emergency lighting (flashlight).NTSB FTW89FA137Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Celina, TXImproper planning/decision by the pilot. Related factors were: failure of the pilot to use all of the available runway area, the runway/terrain conditions, and obstructions/power lines beyond the departure end of the runway.NTSB MIA88LA193Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Lake Wales, FLDuring takeoff from the grass strip, the left main landing gear and wingtip collided with runway lights & a fencepost. The acft was slow to climb. After clearing trees at the departure end of the rwy, the acft descended below treetop level, then continued to…NTSB MIA88FA083Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Pembroke Park, FLThe non-instrument rated private pilot obtained a weather briefing that indicated the weather would be deteriorating to IMC, but he attempted a flight anyway. During the flight, he became disoriented and penetrated 2 control zones and then struck an antenna…NTSB MIA87LA206Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Hastings, FLThe plt stated that he had just lifted from the 2300 ft wet grass strip, where he estimated the grass to be about 6 in to 1 ft high, when he sustained a partial power loss. The acft struck an embankment at the end of the rwy & sheared the gear. Air temp in…NTSB SEA87LA040Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Gates, ORThe plt was attempting to land the aircraft at night on an unlit grass airstrip. Prior to reaching the airstrip the plt collided with an apple tree. Both wings were severed from the aircraft and it went inverted before striking the ground in a slightly nose…