NTSB investigations: Piper PA-46-310P
9 cases on aircraft the registry lists as Piper PA-46-310P, 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
| 1994 | 1 |
|---|---|
| 2000 | 2 |
| 2001 | 1 |
| 2002 | 2 |
| 2005 | 2 |
| 2006 | 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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7104605', '7104611', '7104624')
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 ('7104605', '7104611', '7104624')
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 CHI07LA018Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Chester, ILThe fatigue failure of the turbocharger shroud which resulted in oil starvation to the engine. A factor was the muddy field.NTSB DFW05FA241Accident · 2 fatalField investigationFinal reportPiper PA-46-310P · Houston, TXThe pilot's improper in-flight decision to maneuver back to the departure airport following a loss of engine power on initial climb. Contributing factors were the loss of engine power for undetermined reasons, and the dark night conditions.NTSB CHI05FA162Accident · 1 fatalField investigationFinal reportPiper PA-46-310P · Grand Rapids, MNAn observed loss of engine power due to the bound/jammed turbocharger wastegate during takeoff, the pilot not maintaining airplane control, and the stall he inadvertently encountered. A factor was the maintenance personnel not replacing the turbocharger…NTSB MIA02FA113Accident · 3 fatalField investigationFinal reportPiper PA-46-310P · Naples, FLThe pilot's failure to maintain airspeed above the stall speed while maneuvering to land after the engine ceased operating for undetermined reasons, which resulted in a stall/spin, an uncontrolled descent, and an impact with the ground.NTSB CHI02LA100Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Hastings, MNThe engine failure due to oil starvation as a result of the fatigue fracture of the number 6 piston. Additional factors were the unsuitable terrain for landing encountered by the pilot, and the inadequate piston design by the manufacturer.NTSB CHI01LA271Accident · Minor injuriesLimited investigationFinal reportPiper PA-46-310P · Milwaukee, WIthe rich fuel mixture and the unsuitable landing area encountered by the pilot. Contributing factors were the high output of the fuel pump and the low altitude.NTSB ATL00LA084Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Vero Beach, FLThe pilot's inability to control the aircraft after landing due to a loss of engine power and landing gear failure for undetermined reasons. A factor in the severity of the accident was the impact with the airport marker lights.NTSB FTW00LA067Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Corning, ARThe loss of engine power for an undetermined reason. A factor was the dark night light condition.NTSB FTW94LA146Accident · Minor injuriesLimited investigationFinal reportPiper PA-46-310P · High Island 334A total loss of engine power with the cause undetermined. A factor was the lack of suitable terrain for the forced landing.