NTSB investigations: Piper PA-32-300
22 cases on aircraft the registry lists as Piper PA-32-300, 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 |
| 1984 | 1 |
| 1985 | 2 |
| 1987 | 1 |
| 1988 | 3 |
| 1989 | 1 |
| 1994 | 3 |
| 1997 | 1 |
| 1999 | 2 |
| 2000 | 1 |
| 2001 | 2 |
| 2002 | 1 |
| 2005 | 2 |
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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103212')
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103212')
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 ATL06LA027Accident · No injuriesLimited investigationFinal reportPiper PA32-300 · Maiden, NCThe total loss of engine power due to the failure of the No. 5 main bearing due to overheating for undetermined reasons.NTSB ATL05LA049Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Concord, NCThe loss of engine power due to the failure of the fuel pump which resulted in fuel starvation.NTSB ATL02FA057Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Hamilton, GAThe loss of engine power for undetermined reasons.NTSB NYC01LA154Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Watch Hill, RILoss of engine power for undetermined reason.NTSB ANC01LA083Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Eek, AKA malfunction of the engine fuel control due to an improper overhaul by other maintenance personnel, and subsequent loss of engine power during cruise flight. A factor in the accident was unsuitable terrain for a forced landing.NTSB FTW00LA059Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Sweeney, TXThe pilot's excessive flare resulting in a hard landing. Factors were the loss of engine power for undetermined reasons, the power lines on final approach and the dark night conditions.NTSB ATL99LA088Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Dickson, TNThe loss of engine power due to undetermined reasons. A factor was uneven terrain.NTSB MIA99LA103Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Mt. Vernon, GAThe pilot's improper flare that resulted in a hard landing in an open field. A factor was the high output flow of the fuel injector servo that resulted in a loss of engine power and the forced landing.NTSB FTW97LA284Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Pine Bluff, ARloss of engine power for undetermined reason(s). The lack of suitable terrain for a forced landing was a related factor.NTSB CHI94LA265Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-300 · Richmond, MOa loss of engine power due to fuel starvation, reason undetermined.NTSB CHI94LA255Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Marshalltown, IAA partial loss of engine power for undetermined reasons.NTSB MIA94LA066Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Tamarac, FLThe loss of engine power for undetermined causes.NTSB NYC89FAMS2Accident · 1 fatalMissing aircraftFinal reportPiper PA-32-300 · Missing (Atlantic Ocean)Loss of engine power for an unknown reason.NTSB NYC89LA016Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Easton, PALanding short of the runway due to a power loss of unknown reason(s).NTSB MIA88LA259Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300E · San Juan, PRWhile on a business flt shortly after departure while climbing to cruise, the plt reported that the eng quit. The acft was ditched & has not been recovered therefore no determination could be made as to the reason for the reported loss of eng power. The plt…NTSB MIA88LA149Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Monticello, FLThe plt stated that while enroute to st. petersburg, and in the vicinity of montecello FL, he began to experience severe engine vibrations and a loss of power. He then selected a field to land in & on his apch, the acft struck some trees, sheared off the…NTSB LAX87LA182Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Lincoln, CAThe aircraft collided with a ditch after a loss of pwr during t/o climb at aprx 350 to 400 ft AGL. The plt described the loss of pwr as 'like taking the throttle and pulling off in a rapid motion.' He noticed during his preflt check that the fuel in the right…NTSB NYC85LA216Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Provincetown, MAPlt experience eng pwr loss during tke climb at a height of about 350 ft. the plt headed toward a beach and ditched about 50 yards offshore in order to avoid crowd. The acft submerged underwater afterwards. Examination of the acft disclosed leadlike…NTSB LAX85LA143Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Hayward, CAWhile the instructor plt (CFI) & student were practicing landings, the eng lost power during the initial climb of the 4th touch-&-go at aprx 30 to 40 ft AGL. The CFI took control of the acft & attempted to land on the remaining rwy. However, the acft…NTSB SEA84LA229Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Kelso, WAClimbing through 4,000 ft the engine failed. Emergency procedures resulted in a momentary restoration of power prior to the forced landing. During final approach the left wing struck a tree. The right main landing gear collapsed during the landing roll.…NTSB ANC83FA037Accident · Minor injuriesField investigationFinal reportPiper PA-32-300 · Kasilof, AKThe plt reported that as the acft begun to climb after takeoff, the engine lost power momentarily & the RPM dropped from 2650 to 2500. He started to abort the takeoff, and commented to the passengers, 'we're going to have to put her down.' At about the time…NTSB SEA82DA104Accident · Minor injuriesFinal reportPiper PA-32-300 · 51 Nm Ese Yakut, AKThe pilot reported that during departure, he proceeded east along the alsek river and along the south side of the alsek glacier while climbing to 6200 ft. he then decided that the intended route was closed due to low clouds and he initiated a turn to reverse…