NTSB investigations: Lycoming 0-540 series, NE
4 cases on aircraft whose registry engine model is Lycoming 0-540 series, where the first occurrence was “Loss of engine power”. 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 | 1 |
|---|---|
| 1983 | 1 |
| 1994 | 1 |
| 1997 | 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\" = 'NE' 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')
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\" = 350))
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" = 'NE' 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')
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" = 350))
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 CHI97LA209Accident · No injuriesLimited investigationFinal reportPiper PA-25-235A · O'Neil, NEfuel exhaustion, due to the pilot's improper planning/decision and inadequate fuel consumption calculations. Factors relating to the accident were: the lack of an operable fuel indication system, and the high winds.NTSB CHI94FA263Accident · 2 fatalField investigationFinal reportPiper PA-25 · Decatur, NELoss of engine power for an undetermined reason, and failure of the pilot to maintain adequate airspeed, which resulted in an inadvertent stall.NTSB MKC84LA042Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Schuyler, NEWhile descending toward the planned destination, the eng began running rough & the plt attempted to improve the eng's performance by using carburetor heat. He made a localizer-only apch, but was unable to see the rwy at the min descent alt. A missed apch was…NTSB MKC82DA097Accident · Minor injuriesFinal reportPiper PA-25-235 · Kimball, NEThe aircraft was loaded with 100 gallons of 2-4-D and 40 gallons of fuel. During the preflight run-up check, the pilot noted a mag drop of 225 RPM. He stated that leaning the fuel mixture cleared the excessive decrease in RPM, and he observed 2500 RPM on the…