NTSB investigations: Piper PA-24-250
18 cases on aircraft the registry lists as Piper PA-24-250, where the first occurrence was “Loss of engine power(total) - mech failure/malf”. 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
| 1985 | 2 |
|---|---|
| 1987 | 2 |
| 1988 | 3 |
| 1989 | 2 |
| 1990 | 2 |
| 1991 | 1 |
| 1993 | 1 |
| 1994 | 1 |
| 2002 | 1 |
| 2005 | 1 |
| 2006 | 2 |
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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102404')
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\" = 351))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102404')
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" = 351))
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 CHI07IA017Incident · No injuriesIncident investigationFinal reportPiper PA-24-250 · Sherman, ILThe loose connecting rod bolt due to a loss of torque and subsequent failure of the connecting rod during cruise flight.NTSB NYC07LA001Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Hammonton, NJDisplacement of the idler gear assembly, which resulted in a loss of camshaft timing, and a subsequent engine failure. Contributing to the accident was the swampy terrain condition.NTSB LAX06LA044Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-250 · Tucson, AZthe separation of the mixture cable at the carburetor control arm, which resulted in a loss of power, and maintenance personnel's inadequate inspection of the airplane during the last annual inspection.NTSB LAX02LA065Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Oceano, CAA loss of engine power due to the separation of the mixture control cable from the mixture control arm of the carburetor. The mixture cable separation was due to maintenance personnel's failure to secure the mixture control cable away from the nose landing…NTSB NYC94LA174Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-250 · North Anson, MEthe inadequately installed cylinder mounting stud nuts, by the engine overhaul facility, which resulted in the separation of the number two cylinder and the subsequent forced landing.NTSB SEA93LA089Accident · No injuriesLimited investigationFinal reportPiper PA-24 · Casper, WYFuel exhaustion, and the pilot in command's poor inflight decision. Factors include an inadequate preflight by the pilot in command.NTSB SEA91FA076Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · Chehalis, WAA loss of engine power due to an improper overhaul.NTSB ATL91LA007Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Savannah, GATotal failure of a connecting rod cap bolt which resulted in a total loss of power.NTSB FTW90LA135Accident · No injuriesLimited investigationFinal reportPiper PA-24 · West Fork, ARThe catastrophic failure of the engine.NTSB MIA89LA242Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-250 · Perry, FLFuel starvation due to wear and restricted movement of the carburetor float, which resulted in loss of engine power. Soft terrain in the emergency landing area contributed to overload failure of the nose gear.NTSB CHI89LA087Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Waunakee, WISlippage of a bearing, which resulted in blockage of the lubrication system, and subsequent failure of a connecting rod.NTSB ATL89LA044Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Ft Mill, SCTwo days before the acdnt, the plt had fueled the acft to capacity & flown it a short distance to his house at a pvt airstrip. After the flt, he noticed fuel on the tops of both wings, aft of the fuel filler caps. He was aware that fuel had leaked from the…NTSB LAX88LA267Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Chico, CADuring a cross country flight, the pilot noted a loss of oil pressure. Shortly after, the pilot heard a loud bang and the engine lost power. A forced landing was made short of the airport where the airplane collided with the terrain during the landing roll.…NTSB CHI88DEX01Accident · 1 fatalFinal reportPiper PA-24-250 · Salem, INN6478P crashed during a forced landing near the Salem, IN, airport. The aircraft had experienced an engine failure due to failure of the number 5 connecting rod cap bolt. The aircraft struck a tree during the approach and crashed 100 yards north of the runway.NTSB ATL88FA040Accident · Serious injuriesField investigationFinal reportPiper PA-24-250 · Lewisburg, KYThe pilot experienced a loss of engine power at 5500 feet. He was not able to start the engine after completing an emergency procedure. The pilot established an approach to a landing area, and stalled the aircraft on short final. The aircraft moved about 30…NTSB MIA87LA104Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Navarre, FLShortly after take off with the fuel selector positioned to the rt tank, at an alt of aprx 250 feet, the eng quit. The plt force landed the acft in an inter coastal waterway with the landing gear extended. Insp of the acft revealed that the eng quit due to…NTSB LAX86LA068Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-250 · Canoga Park, CAWhile the plt was cruisin in his own acft, an eng oil leak developed, oil pressure decreased & eng power was lost, the plt attempted to make an emergency ldg on a city street, on approach the acft collided with power lines & a fence, & the acft came to rest…NTSB FTW86FPA04Accident · No injuriesFinal reportPiper PA-24-250 · Terrell, TXThe acft traveled through a barbed wire fence during a forced landing short of rwy 35 at Terrell arpt. When aprx 1 mile from the arpt, the eng quit. The plt was unable to move the fuel selector, however, by applying a full rich mixture and turning on the…