Fatal NTSB investigations: Lycoming TI0-540 series
30 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 | 4 |
|---|---|
| 1983 | 1 |
| 1984 | 4 |
| 1986 | 1 |
| 1987 | 2 |
| 1988 | 1 |
| 1989 | 1 |
| 1991 | 1 |
| 1993 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 1999 | 2 |
| 2000 | 1 |
| 2001 | 2 |
| 2002 | 1 |
| 2003 | 2 |
| 2004 | 2 |
| 2005 | 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.\"highestInjuryLevel\" = 'Fatal'
AND 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."highestInjuryLevel" = 'Fatal'
AND 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 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 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 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 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 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 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 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 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 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 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 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 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 ATL83AA029Accident · 1 fatalFinal reportPiper PA-31-350 · Brevard, NCAfter a missed approach at asheville the flt was cleared to the greenville-spartanburg arpt at greer,SC. Enroute to greer radar contact was lost. In response to a query from atlanta ARTCC the plt verified his position as being on the 235 deg radial of…NTSB MIA83LA012Accident · 2 fatalLimited investigationFinal reportPiper PA-32-300 · Near St. CroixThe non-instrument rated pilot departed st Croix, VI at about 2000 local time on a VFR flight to san juan, PR. The weather was VFR, but it was a dark night. The aircraft failed to arrive at its destination and a search was initiated. About 10 miles northwest…NTSB LAX82FUG17Accident · 1 fatalFinal reportPiper PA-32R-301T · San Gorgonio, CAThe acft crashed into the south face of mount San Gorgonio at approximately 8,300 ft MSL. It appeared the acft was in level flt & at a high speed at impact. Witnesses in the area reported the weather was VFR.NTSB NYC82FA029Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Newburgh, NYAt 2234 the plt was issued a vector to the initial approach fix for the ILS rwy 9 apch. He was also issued the followingwx "...stewart weather thirty minutes ago is estimated one thousand overcast six miles in light rain and haze." At 2238 the plt was advised…