NTSB investigations: Lycoming 0-540 series, CT
18 cases on aircraft whose registry engine model is Lycoming 0-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
| 1964 | 1 |
|---|---|
| 1967 | 3 |
| 1968 | 1 |
| 1981 | 1 |
| 1983 | 1 |
| 1984 | 1 |
| 1985 | 1 |
| 1989 | 1 |
| 2000 | 1 |
| 2004 | 1 |
| 2005 | 1 |
| 2008 | 1 |
| 2011 | 1 |
| 2012 | 1 |
| 2013 | 1 |
| 2018 | 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 ('41532'))
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 ('41532'))
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 GAA19CA091Accident · No injuriesData collectionFinal reportZlin Z143 · Chester, CTThe pilot's loss of airplane control during the engine start.NTSB ERA13LA408Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-250 · Woodstock, CTThe pilot’s improper preflight inspection, which resulted in fuel exhaustion and a total loss of engine power.NTSB ERA12CA436Accident · No injuriesData collectionFinal reportPiper PA-28-236 · Chester, CTThe pilot’s failure to execute a go-around following an approach that was high and fast, which resulted in a runway overrun.NTSB ERA11FA334Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · Westbrook, CTA total loss of engine power during approach due to inadequate torque on the No. 3 cylinder hold-down nuts.NTSB MIA08CA093Accident · No injuriesData collectionFinal reportPiper PA-28-235 · Ellington, CTThe pilot's failure to perform a go-around when the airplane floated during landing.NTSB IAD05FA068Accident · 2 fatalField investigationFinal reportCessna R182 · New Fairfield, CTFailure of the aluminum-clad, number two connecting rod bearings, which resulted in a total loss of engine power. A factor was the relatively short forced landing area.NTSB IAD04FA025Accident · 2 fatalField investigationFinal reportRobinson R-44 · Killingly, CTThe pilot in command's intentional flight into instrument meteorological flight conditions, and his failure to maintain obstacle clearance which resulted in a controlled descent into trees. Factors included the pilot's inadequate weather evaluation, low cloud…NTSB NYC00LA221Accident · Minor injuriesLimited investigationFinal reportPiper PA28-235 · Chester, CTThe CFI's delayed remedial action.NTSB NYC90FA036Accident · 1 fatalField investigationFinal reportPiper PA-32-260 · Coventry, CTThe non-instrument rated pilot initiating VFR flight into IMC on a dark night which resulted in spatial disorientation and uncontrolled flight into the ground. Contributing factor(s) was: the adverse weather existing at the time of the accident and the…NTSB NYC85LA168Accident · No injuriesLimited investigationFinal reportPiper PA-28-236 · New Milford, CTAccording to the plt, the preflt and runup checks were normal. The plt then applied full pwr for takeoff and rotation was initiated at 60 KTS. After liftoff, the acft appeared to loose pwr and began to yaw to the left. The stall warning horn sounded and the…NTSB NYC85LA036Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Meriden, CTWhile in cruise, plt heard an abnormal sound from the left side of the engine compartment and having had previous problems with the newly-installed engine, elected to make a precautionary landing at a nearby arpt to investigate. Plt stated he landed long and…NTSB NYC84FA053Accident · 2 fatalField investigationFinal reportCessna R182 · Greenwich, CTThe acft collided with trees during an ILS approach to westchester arpt in NY. The weather was IMC and an IFR flt plan was filed. The accident occurred during the 2nd attempt with the 1st ending in a missed approach. It was apparent to thecontroller that the…NTSB NYC81FNE26Accident · No injuriesClosedPiper PA-24 · E.Hartford, CTNTSB NYC68F0446Accident · No injuriesClosedPiper PA-23 · Windsor Lks, CTNTSB NYC68A0050Accident · No injuriesClosedPiper PA-23 · New London, CTNTSB NYC67D0546Accident · No injuriesClosedPiper PA-28 · Hartford, CTNTSB NYC67D0526Accident · No injuriesClosedPiper PA-24 · Madison, CTNTSB UNK64X1565Accident · No injuriesClosedPiper PA24 · Danbury, CT