NTSB investigations: Piper PA-31T2
7 cases on aircraft the registry lists as Piper PA-31T2. 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 |
|---|---|
| 1984 | 1 |
| 1989 | 1 |
| 1990 | 1 |
| 2001 | 1 |
| 2009 | 1 |
| 2026 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103127'))
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 ('7103127'))
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 ERA27LA016Accident · No injuriesLimited investigationInvestigation openPiper PA-31T2 · Dayton, OHNTSB CEN10FA063Accident · 1 fatalField investigationFinal reportPiper PA-31T2 · Harrison, MIA loss of aircraft control for undetermined reasons.NTSB MIA01FA152Accident · 5 fatalField investigationFinal reportPiper PA-31-T2 · Jackson, TNThe pilot's shutting down the left engine following loss of control of the left propeller resulting in an in-flight loss of control of the airplane due to the windmilling propeller. Factors in the accident were the failure of the propeller control bracket…NTSB CHI91FA035Accident · 1 fatalField investigationFinal reportPiper PA-31T2 · Des Moines, IAThe pilot's improper emergency procedures by not feathering the left engine after it lost power and/or was shut down, and his failure to keep the aircraft at or above the minimum control airspeed (VMC), which resulted in a loss of aircraft control. A factor…NTSB DEN89FA217Accident · 3 fatalField investigationFinal reportPiper PA-31T2 · Louisville, COFailure of the pilot to maintain adequate airspeed, while maneuvering for spacing in the traffic pattern, which resulted in an inadvertent stall at low altitude.NTSB ATL84FA222Accident · No injuriesField investigationFinal reportPiper PA-32R-300 · Rock Hill, SCThe acft was destroyed in a post flt fire after a forced landing at night in a private yard. The engine had surged and lost power during the descent through 4500 ft prior to landing. The acft had been written up for sluggishness and lack of response to…NTSB ATL82FA055Accident · 8 fatalField investigationFinal reportPiper PA-31T2 · Springfield, KYThe flt was cleared to maintain 3,000 ft MSL until over the arpt, then cruise. The plt had previously stated that he could see the lights on the ground & that he was 15 mi from the arpt. At 2013 the plt stated "we oughta be able to cancel here." The acft…