NTSB investigations: Lycoming TI0-540 series, CT
15 cases on aircraft whose registry engine model is Lycoming TI0-540 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 | 1 |
|---|---|
| 1978 | 1 |
| 1979 | 1 |
| 1980 | 2 |
| 1987 | 1 |
| 1989 | 2 |
| 1991 | 1 |
| 1996 | 1 |
| 1999 | 1 |
| 2002 | 1 |
| 2004 | 1 |
| 2007 | 1 |
| 2011 | 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\" = 'CT' 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 ('41533'))
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" = 'CT' 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 ('41533'))
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 ERA11CA365Accident · Serious injuriesData collectionFinal reportPiper PA-32-300 · Bridgeport, CTThe pilot's failure to maintain clearance from a blast fence on final approach to land.NTSB NYC07FA100Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Windham, CTThe pilot's failure to maintain control of the airplane during a go-around.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 IAD03FA024Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Woodbury, CTAn engine fire for undetermined reasons, which resulted in the pilot's loss of control, and the airplane's subsequent impact with terrain.NTSB NYC99LA139Accident · No injuriesLimited investigationFinal reportAero Commander 500S · Windsor Locks, CTHydraulic system contamination which prevented normal landing gear extension. A factor was the misjudged landing flare by the flying pilot.NTSB IAD96LA110Accident · No injuriesLimited investigationFinal reportMooney M20M · Hartford, CTthe pilot's inadequate control of the airplane during the approach to landing/landing roll. A related factor is the pilot's inadequate remedial action (attempted go-around).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 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 NYC89LA169Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Danbury, CTThe pilot's misjudgement of (excessive) airspeed, his failure to attain the proper touchdown point, and failure to make a go-around, while there was sufficient runway remaining. The fence was a related factor.NTSB NYC88LA027Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Windham, CTThe flight departed groton, Connecticut enroute to willimantic, Connecticut in unlimited visibility. However at Windham airport, the runway was partially obscured by patchy fog according to the pilot. The pilot landed long due to carrying additional speed in…NTSB NYC81FAMS1Accident · 4 fatalClosedPiper PA-31 · Bridgeport, CTNTSB NYC80DA074Accident · No injuriesClosedPiper PA-23 · Hartford, CTNTSB NYC80FA009Accident · No injuriesClosedPiper PA-31 · Stamford, CTNTSB NYC78FNE09Accident · No injuriesClosedPiper PA-32 · Meriden, CTNTSB NYC67F0258Accident · No injuriesClosedCessna 172 · Plainville, CT