NTSB investigations: Lycoming TI0-540 series, SD
17 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
| 1969 | 1 |
|---|---|
| 1972 | 1 |
| 1976 | 1 |
| 1977 | 1 |
| 1979 | 1 |
| 1982 | 2 |
| 1986 | 1 |
| 1993 | 1 |
| 1998 | 1 |
| 2006 | 1 |
| 2014 | 2 |
| 2017 | 1 |
| 2022 | 2 |
| 2023 | 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\" = 'SD' 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" = 'SD' 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 CEN24LA020Accident · 1 fatalClass 3 · LimitedFinal reportPiper PA 46-350P · Pierre, SDThe total loss of engine power due to fuel starvation as a result of the pilot’s improper configuration of the automatic fuel transfer system. Contributing to the accident was the pilot’s failure to adequately monitor the header tank’s fuel quantity.NTSB CEN22LA313Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-24-260 · Rapid City, SDA total loss of engine power for reasons that could not be determined because the airplane was unavailable for examination.NTSB CEN22LA257Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-32R-300 · Gettysburg, SDAn inadvertent hard landing by the pilot.NTSB GAA18CA094Accident · No injuriesData collectionFinal reportPiper PA32 · Spearfish, SDThe pilot’s inadvertent landing in snow adjacent to the snow-covered runway resulting in a collision with runway signs.NTSB CEN15CA006Accident · Minor injuriesData collectionFinal reportPiper PA 31-350 · Glenham, SDThe pilot's improper fuel management, which resulted in losses of power on both engines due to fuel exhaustion.NTSB CEN14FA224Accident · 4 fatalField investigationFinal reportPiper PA 32R-300 · Highmore, SDThe pilot's decision to continue the flight into known deteriorating weather conditions at a low altitude and his subsequent failure to remain clear of an unlit wind turbine. Contributing to the accident was the inoperative obstruction light on the wind…NTSB CHI06FA067Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Pierre, SDThe loss of engine power during takeoff-initial climb due to the pilot's failure to correctly position the fuel selector, which resulted in fuel starvation and a forced landing.NTSB CHI98LA219Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Mobridge, SDThe pilot's failure to maintain clearance from the power lines. Factors associated with the accident were the power lines, and the separation of the vertical stabilizer and rudder which resulted in the pilot's inability to maintain directional control of the…NTSB CHI94LA056Accident · 1 fatalLimited investigationFinal reportPiper PA-24-250 · Mcintosh, SDwas continued VFR flight into IMC and the failure to maintain clearance with the terrain. Factors associated with this accident were an inaccurate weather evaluation by the pilot, snow and the rising terrain.NTSB DEN86FTK02Accident · No injuriesFinal reportAero Commander Callair A-9B · Dell Rapids, SDThe plt stated that during the takeoff roll, he lost rudder effectiveness after accelerating to about 60 KTS. He applied brakes to stop, but the acft veered off the left side of the rwy & struck a fence. No preimpact part failure or malfunction was reported.…NTSB DEN82FTK04Accident · No injuriesFinal reportCallair A-9B · Sioux Falls, SDThe eng quit & the plt landed in an adjacent field after first hitting a wooded fence. An inspectin of the bendix fuel servo unit, model PSA-10ED-1, revealed that the fuel diaphragm stem, pn 2539806, had failed.NTSB DEN82FA034Accident · No injuriesField investigationFinal reportPiper PA-23 · Mitchell, SDAs the pilot approached sioux falls he received information that it was below minimums, so he started to divert. As he passed over sioux falls he could see Mitchell, SD, which appeared to be clear, therefore, he elected to land there. It continued to look…NTSB MKC79FTK09Accident · No injuriesClosedPiper PA-24 · Pierre, SDNTSB MKC77DTK26Accident · No injuriesClosedPiper PA-24 · Philip, SDNTSB MKC77FTK02Accident · No injuriesClosedPiper PA-32 · Dell Rapids, SDNTSB MKC72DTK26Accident · No injuriesClosedPiper PA-31 · Brookings, SDNTSB MKC69F0469Accident · Serious injuriesClosedCallair A-9B · Miller, SD