NTSB investigations, 2012
13 cases where NTSB found Recip engine power section.
Cases per year
| 2008 | 18 |
|---|---|
| 2009 | 16 |
| 2010 | 12 |
| 2011 | 7 |
| 2012 | 13 |
| 2013 | 18 |
| 2014 | 9 |
| 2015 | 20 |
| 2016 | 18 |
| 2017 | 11 |
| 2018 | 16 |
| 2019 | 14 |
| 2020 | 12 |
| 2021 | 12 |
| 2022 | 11 |
| 2023 | 14 |
| 2024 | 11 |
| 2025 | 1 |
Where
Latest 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 year(c.\"eventDate\") = 2012
AND c.\"mKey\" IN (SELECT f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f.\"findingCode\", '01058520'))
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 year(c."eventDate") = 2012 AND c."mKey" IN (SELECT f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f."findingCode", '01058520')) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
Run 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 ERA13LA097Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Lock Haven, PAThe reinstallation of improper connecting rods at engine overhaul, which resulted in abnormal wear of the connecting rod bearings; while the bearings did not meet the manufacturer’s specifications, the use of the unapproved connecting rods more likely caused…NTSB WPR13LA052Accident · Minor injuriesLimited investigationFinal reportCessna U206 · Van Nuys, CAA partial loss of engine power during cruise flight due to fatigue fractures of two crankshaft gear teeth from corrosion pitting, which resulted in an off-airport forced landing and collision with obstacles on the ground.NTSB CEN12FA653Accident · No injuriesField investigationFinal reportPiper PA-46-350P · Kiowa, COA catastrophic engine failure due to unrecognized and unrepaired corrosion within the engine, which was consistent with engine operations after an extended period of inactivity.NTSB ERA12LA473Accident · No injuriesLimited investigationFinal reportCirrus Design SR-22 · Pickens, SCA total loss of engine power due to the failure of the crankshaft, which resulted from the application of insufficient torque on the cylinder through-bolts by maintenance personnel.NTSB WPR12LA281Accident · No injuriesLimited investigationFinal reportTecnam P2002 Sierra · Watsonville, CAA partial loss of engine power during initial climb due to the blockage of the carburetor’s main jet by deteriorated float material. Contributing to the accident was an inadequate maintenance inspection by maintenance personnel.NTSB ERA12LA422Accident · Serious injuriesLimited investigationFinal reportMooney M20J · Mc Kinnon, TNThe separation of the piston connecting rod from the crankshaft due to inadequate installation from a mechanic, resulting in a total loss of engine power.NTSB ANC12LA058Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Gustavus, AKThe fatigue failure of the engine crankshaft for reasons that could not be determined during postaccident metallurgical examination.NTSB ERA12LA394Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Ocilla, GAA failure of the No. 2 cylinder connecting rod due to a lack of lubrication, which resulted in a total loss of engine power.NTSB CEN12LA326Accident · Minor injuriesLimited investigationFinal reportMooney M20J · Ozark, ARThe failure of a connecting rod due to oil starvation.NTSB CEN12LA309Accident · Minor injuriesLimited investigationFinal reportQuicksilver Sprint II · Lebanon, ILThe total loss of engine power due to a fatigue failure of the crankshaft, attributed to the relative movement between the crankshaft and flywheel assembly.NTSB ERA12LA274Accident · No injuriesLimited investigationFinal reportCessna 172S · Daytona Beach, FLA total loss of engine power due to a catastrophic engine failure, the origin of which could not be determined during postaccident examination.NTSB ERA12LA267Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Eastover, SCInadequate or loss of through bolt preload tension, which resulted in fretting between the engine halves, the subsequent failure of one cylinder through bolt, the loosening of additional cylinder retaining studs, and the fracture of the crankcase.…NTSB ERA12LA219Accident · No injuriesLimited investigationFinal reportCirrus Design SR22 · Homestead, FLThe inadequate servicing and maintenance of the engine and the airplane owner and maintenance personnel's disregard of the manufacturer's recommended engine overhaul schedule and service bulletins, which resulted in an in-flight internal failure and seizure…