NTSB investigations: Piper PA-46-310P, TX
7 cases on aircraft the registry lists as Piper PA-46-310P. 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
| 2000 | 1 |
|---|---|
| 2001 | 1 |
| 2005 | 1 |
| 2010 | 1 |
| 2014 | 1 |
| 2020 | 1 |
| 2025 | 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\" = 'TX' AND c.\"eventCountry\" = 'USA'
AND 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'))
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" = 'TX' AND c."eventCountry" = 'USA'
AND 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'))
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 CEN26LA030Accident · No injuriesClass 3 · LimitedPreliminary reportPiper PA-46-310P · El Paso, TXOn October 26, 2025, about 918 mountain daylight time, a Piper PA46-310P, N46CR, was substantially damaged when it was involved in an accident near El Paso, Texas. The pilot and two passengers were not injured. The airplane was operated as a Title 14 Code of…NTSB CEN20LA402Accident · 4 fatalClass 3 · LimitedFinal reportPiper PA46 · Hilltop Lakes, TXThe loss of engine power for reasons that could not be determined and the pilot’s failure to maintain control of the airplane which resulted in an aerodynamic stall and spin. Contributing to the accident was the pilot’s failure to establish and maintain a…NTSB CEN14FA300Accident · 3 fatalField investigationFinal reportPiper PA 46-310P · Lehman, TXThe pilot's improper decision to enter an area of known adverse weather, which resulted in the loss of airplane control. Contributing to the accident was the air traffic controller's failure to provide critical weather information to the pilot to help him…NTSB CEN10CA490Accident · Serious injuriesData collectionFinal reportPiper PA-46-310P · Austin, TXThe pilot's failure to maintain a stabilized approach, which resulted in a loss of control on landing with a tailwind.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 FTW01LA191Accident · 1 fatalLimited investigationFinal reportPiper PA-46-310P · Bulverde, TXthe pilot's failure to obtain airspeed after rotation, which resulted in a stall/mush. Contributing factors were the tailwind condition, high density altitude, and upsloping runway.NTSB FTW00LA057Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Odessa, TXThe separation of the #1 piston pin due to fatigue, which resulted in a total loss of engine power. A factor was the lack of suitable terrain for the forced landing.