NTSB investigations: Lycoming TI0-540 series
56 cases on aircraft whose registry engine model is Lycoming TI0-540 series, where the first occurrence was “In flight collision with terrain/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 | 6 |
|---|---|
| 1983 | 2 |
| 1984 | 8 |
| 1985 | 3 |
| 1986 | 3 |
| 1987 | 4 |
| 1988 | 3 |
| 1989 | 1 |
| 1991 | 2 |
| 1993 | 1 |
| 1994 | 1 |
| 1995 | 1 |
| 1997 | 1 |
| 1998 | 2 |
| 1999 | 2 |
| 2000 | 2 |
| 2001 | 2 |
| 2002 | 2 |
| 2003 | 3 |
| 2004 | 2 |
| 2005 | 3 |
| 2006 | 2 |
Where
Latest 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\" = 230))
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" = 230))
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 SEA06CA177Accident · No injuriesData collectionFinal reportCessna 182RG · Shelton, WAThe pilot's failure to extend the landing gear prior to a practice soft-field landing, and the certified flight instructor's failure to take remedial action. Factors include the pilot's failure to use a checklist.NTSB CHI06LA061Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Worthington, MNThe missed approach not performed by the pilot and the directional control not maintained by the pilot during landing. Contributing factors were the crosswind, wind information not available due to inoperative meteorological equipment, and a Notices to Airman…NTSB CHI05CA275Accident · No injuriesData collectionFinal reportCessna T206H · Sturgeon Bay, WIThe unexpected wave that the airplane encountered during the landing flare.NTSB CHI05FA260Accident · 4 fatalField investigationFinal reportPiper PA-32-300 · Wabash, INThe pilot's spatial disorientation that resulted in his failure to maintain clearance from terrain. Factors to the accident were the pilot's lack of recent night experience and the hazy night conditions.NTSB ATL05FA066Accident · 2 fatalField investigationFinal reportCessna T206H · Johns Island, SCThe pilot's failure to follow instrument flight procedures and descent below the published minimum descent altitude, which resulted in an in-flight collision with terrain during an instrument approach.NTSB FTW04FA172Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Hot Springs, ARThe pilot's failure to fly a stabilized, published instrument approach procedure, which resulted in a collision with mountainous terrain. Factors were the clouds and the air traffic controllers' failure to provide known information that may have assisted the…NTSB LAX04FA102Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Big Pine, CAfailure of the pilot to maintain clearance with mountainous terrain for undetermined reasons.NTSB LAX03FA166Accident · 4 fatalField investigationFinal reportRockwell 114 · Bishop, CAThe pilot's failure to maintain an adequate airspeed while maneuvering close to the ground over mountainous terrain in a high density altitude environment near the upper performance capability of the airplane, which resulted in an inadvertent stall/mush into…NTSB ANC03LA044Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Kotzebue, AKThe pilot's failure to maintain adequate altitude/clearance, which resulted in an in-flight collision with terrain during cruise flight. Factors associated with the accident were flat light conditions, and snow-covered terrain.NTSB LAX03FA076Accident · 2 fatalField investigationFinal reportPiper PA-60-601P · Scottsdale, AZthe pilot's failure to maintain an adequate altitude clearance from mountainous terrain. Contributing factors were dark night conditions, mountainous terrain, and the pilot's diverted attention.NTSB LAX02LA248Accident · Minor injuriesLimited investigationFinal reportMooney M20M · Gualala, CAThe pilot's delayed decision in executing a go-around. Contributing factors were the pilot's limited experience landing on short fields and the rising terrain.NTSB LAX02FA166Accident · 2 fatalField investigationFinal reportSocata TB-21 · New River, AZthe pilot's failure to maintain an adequate terrain clearance altitude during a cruise descent that resulted in controlled flight into terrain (CFIT). Factors in the accident were the rising mountainous terrain, the dark nighttime lighting condition, and the…NTSB MIA01FA193Accident · 1 fatalField investigationFinal reportPiper PA-46-350P · Black Mountain, NCThe pilot's continued VFR flight into IMC conditions resulting in the airplane colliding with mountainous terrain.NTSB MIA01FA107Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300 · Concord, NCAn in-flight collision with terrain for undetermined reasons.NTSB CHI00LA255Accident · No injuriesLimited investigationFinal reportPiper PA-31-325 · Omaha, NEthe landing gear not deployed, the checklist not followed, the lack of familiarity with the airplane, the landing gear warning system not understood, and the landing gear warning disregarded by the pilot.NTSB DEN00FA086Accident · 2 fatalField investigationFinal reportSmith, Ted Aerostar Aerostar 601 · Estes Park, COA descent below the surrounding terrain, by the pilot, in IMC conditions. Factors were high mountainous terrain, clouds, inaccurate weather evaluation by the pilot, and the pilot's flight into IMC conditions.NTSB MIA00FA043Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Pelham, ALThe student pilot's decision to continue the visual flight rules flight into deteriorating visibility, and his failure to maintain altitude clearance with the terrain.NTSB MIA99LA155Accident · 1 fatalLimited investigationFinal reportAero Commander 500B · Atlantic Ocean (Atlantic Ocean)an in-flight collision with water for undetermined reasons, due to the wreckage never being recovered from the water.NTSB NYC98LA119Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Hanover, PAfailure of the pilot to obtain current information for the divert airfield, and his selection of an unsuitable area for landing. Related factors included: the lower ambient light conditions at dusk, construction on the airfield, and an over-reliance on the…NTSB SEA98FA101Accident · 2 fatalField investigationFinal reportPiper PA-46-350P · Bigfork, MTThe pilot's failure to maintain terrain clearance for undetermined reasons. Contributing factors were the mountainous terrain, trees, dark night conditions, clouds and pilot fatigue.NTSB FTW97FA171Accident · 3 fatalField investigationFinal reportPiper PA-32RT-300T · Rye, COThe pilot initiating flight into IMC conditions in mountainous terrain. Factors were mountainous terrain, low ceiling, snow, preflight planning, and in-flight planning and decision making.NTSB ANC95LA050Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Dillingham, AKThe pilot's inadequate preflight planning and preparation. Factors associated with the accident are: the dispatcher's decision to dispatch a multi-engined airplane to a short, soft airstrip, and inadequate company management oversight/surveillance.NTSB ANC94FA087Accident · Serious injuriesField investigationFinal reportPiper PA-31-310 · Mccarthy, AKThe pilot's inadvertent use of the parking brake during the takeoff and not aborting the takeoff. A factor in the accident was the pilot's improper use of the airplane checklist.NTSB ANC93FA134Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Atigun Pass, AKThe pilot-in-command's intentional VFR flight into instrument meteorological conditions and his unfamiliarity with the geographical area. Factors were the rain and fog.NTSB NYC91LA167Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Rhinebeck, NYThe pilot did not calculated the airplane's performance data to insure that he had enough runway to clear an obstacle at the end of the field, which resulted in the airplane's landing gear striking high hedges, subsequently the pilot elected to land in a…NTSB ATL91FA052Accident · 4 fatalField investigationFinal reportPiper PA-31-350 · Munford, ALThe pilot attempting visual flight in instrument meteorological conditions below the minimum safe altitude for terrain clearance. Contributing factors were the low ceiling and mountainous terrain.NTSB MIA90FA022Accident · 1 fatalField investigationFinal reportPiper 601P · Fort Myers, FLFailure of the pilot to properly follow the IFR procedure and to identify the decision height. Factors related to the accident were: the adverse weather conditions, darkness, the pilot's lack of visual perception without the approach lights, and tree(s) in…NTSB LAX89FA025Accident · 2 fatalField investigationFinal reportPiper PA31P-350 · Redlands, CAThe pilot's inadvertent selection of an inappropriate altitude for the attempted night special VFR circle to land maneuver. Contributing to the accident was the dark night, restricted visibilities and lack of ground reference lights. Also contributing to the…NTSB FTW88LA148Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · Edna, TXA delay in initiation of the go-around during the pilot's second attempt to land in the dark night conditions. Contributing to the accident was the runway closure due to construction, which resulted in no runway lights illuminated, and the fact that the pilot…NTSB ATL88IA096Incident · No injuriesIncident investigationFinal reportPiper PA-23-250 · Elyria, OHNTSB MKC87FA169Accident · 1 fatalField investigationFinal reportPiper PA-24-260 · Kanorado, KSThe fss stated they had personally briefed the student pilot on the wx en route for this night flight and told him VFR was not recommended. At the first stop, he called the co-owner of the airplane and told her he had been flying around storms. At the next…NTSB FTW87FA184Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Imperial, TXAfter takeoff, the plt elected to fly low over a reservoir. He stated that as he began a pass, not FAR from the water's edge, the acft enctrd a sink. He said he ' . . . Checked power, all ok, plane just seemed to lose all lift . . .' Subsequently, the acft…NTSB MIA87LA102Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · St. ThomasThe pilot stated that as he lifted off the aircraft encountered a gust of wind. The pilot lost control of the aircraft and it struck a displaced threshold sign and the ground.NTSB ANC87IA032Incident · No injuriesIncident investigationFinal reportPiper PA-31-350 · Barter Island, AKThe pilot flew into rising terrain during a night VFR flight. After shutting down the right engine and achieving only partial propeller feather he elected to make a gear up landing. The plt was flying at 500 ft AGL when he wandered from over water to on-shore…NTSB MIA87LA024Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Homestead, FLThe plt stated that he thought he had put the gear handle down but on touchdown the gear was up and the aircraft slid to a stop on the runway. Post crash examination of the landing gear system revealed that the landing gear was up when it contacted the runway…NTSB DEN87FA046Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · Leyba, NMThe plt departed albuquerque on October 29, 1986, in his acft for an unknown destination. When he failed to return to his home, relatives notified local authorities. A search was begun and on January 23, 1987, the wreckage was found. The pilot was deceased…NTSB CHI86FER16Accident · No injuriesFinal reportAero Commander Callair A9B · Argyle, MNWhile setting up for a swath run the pilot struck the ground in a wings level descent. He stated that a 'whirlwind' or 'downdraft' prevented him from pulling up in time to pre-vent impact with the ground.NTSB NYC86LA044Accident · Minor injuriesLimited investigationFinal reportPiper Aztec · North Adams, MAThe flight departed albany new york under VFR conditions and picked up IFR clearance to pittsfield, MA. The pilot flew the approach until reaching VFR under a cloud layer at about 2500 ft. continuing VFR toward no. Adams at an altitude of 2000 ft, the pilot…NTSB MIA85LA199Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-250 · Opa Locka, FLThe plt was landing after a x-country flt when the right wing & the prop contacted the rwy. The plt stated that the gear had collapsed during a go-around. However, the landing gear was intact, except for impact damage on the right main gear. No gear…NTSB MIA85LA151Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Miami, FLThe plt stated that he permitted a non-plt pax to close the cabin door & he, the plt did not check it. Shortly after liftoff the landing gear was retracted & the door popped open. The pax turned in his seat to close the door & bumped the yoke forcing the acft…NTSB ATL85FA055Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Burlington, KYAcft ferried VFR by owner. Radios repaired before departure, glide slope receiver found inop. At fuel stop wx was forecast IFR for destination. An IFR instructor was then hired for the remaining flt. Owner showed work order to CFI who incorrectly concluded…NTSB FTW85FA054Accident · 1 fatalField investigationFinal reportBellanca 17-31ATC · Allen, TXThe acft collided with the ground as the plt, who was not current for night/instrument flt, tried to maneuver beneath a low overcast on a dark night. Although seriously injured during the accident sequence, the plt was able to tell rescue workers that he 'was…NTSB LAX85LA016Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Sonoma, CAPlt made inadvertant gear up landing. Plt stated he forgot to lower the gear when his attention was diverted to the cabin door which came open in-flight.NTSB MIA84LA214Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Espanola, FLThe acft without flt plan and no flt history was found abandoned in a field with 14 bales of marijuana located in and around the wreckage. No owner or plt has been located. Customs agents tracking the acft lost contact in a thunderstorm between daytona and…NTSB LAX84FA328Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · Baker, CAThe acft was found where it had crashed & burned on a rough lava bed. The crash site was about 1 mi northeast of a road where drug smuggling acft had been known to land in the past. There was evidence that cocaine had been removed from the accident site. The…NTSB LAX84FA277Accident · 3 fatalField investigationFinal reportPiper PA-23-250 · Ukiah, CADuring arrival, the plt was cleared for a loc/dme rwy 15 apch to the Ukiah arpt. At 1307 PDT, he began the apch at the tucci intersection, 15.5 mi north of the rwy. At 1311:04 the last radar contact showed that the acft was about 5 mi north of the arpt. At…NTSB FTW84LA210Accident · No injuriesLimited investigationFinal reportBellanca 17-31ATC · Rocksprings, TXThe plt stated that the cabin door opened in-flight. While making a landing at Rocksprings in order to shut the door, the plt failed to use the checklist and landed the acft with the gear up. The acft was equipped with an auto gear extender, but because of…NTSB DEN84FA121Accident · Serious injuriesField investigationFinal reportAero Commander 500-B · Miles City, MTThe plt said that when he called on the radio prior to the approach for an altimeter setting the reply was '30.11 or 30.12, something like that.' The acft altimeter was found after the accident set at 30.22 inches of mercury. The visibility was described as 1…NTSB MIA84FA006Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Cornwell, FLThe acft was found with a large amount of burned marijuna onboard & the cargo door open.NTSB LAX83LA189Accident · Serious injuriesLimited investigationFinal reportRockwell A-9B · Marana, AZThe plt was on a flt from quanah, TX to chandler, AZ to deliver the acft for a sale. He had been on the ferry flt for 6 hrs when he landed at Marana, AZ. After refueling, raising the eng cowl, inspecting the eng & wiping off an accumulation of oil, he took…