NTSB investigations: Piper PA-28RT-201T

7 cases on aircraft the registry lists as Piper PA-28RT-201T, where the first occurrence was “Airframe/component/system failure/malfunction”. 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.

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

19832026

NTSB investigations: Piper PA-28RT-201T per year, 1983–2026: 7 cases
1983	2
1985	1
1988	1
1990	1
2002	1
2006	1

Where

Open the map

Latest cases

Query with SQL

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 ('7102817') 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" = 130)) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

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 ('7102817')
      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\" = 130))
  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 ('7102817')
    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" = 130))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

Run 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 DEN06LA044Accident · No injuriesLimited investigationFinal reportPiper PA-28RT-201T · Parker, COthe improper maintenance procedures resulting in the unseating of the number two main bearing. Contributing factors include the mechanic's improper troubleshooting procedures, and the pilot's improper decision to continue operating the airplane with known…Feb 25, 2006 · N2939V · Substantial damage NTSB DEN03LA014Accident · No injuriesLimited investigationFinal reportPiper PA-28RT · Grand Junction, COthe collapse of the left main landing gear during landing roll resulting in loss of control/ground loop/swerve and subsequent impact with a sign. Contributing factors include, the airplane's total loss of electrical power due to an alternator failure and the…Nov 6, 2002 · N2904C · Substantial damage NTSB FTW90LA162Accident · No injuriesLimited investigationFinal reportPiper PA28-201T · Heber Springs, ARThe pilot's failure to conduct a thorough preflight and his attempt to execute a turn at high speed.Sep 2, 1990 · N2082Y · Substantial damage NTSB LAX88LA213Accident · Minor injuriesLimited investigationFinal reportPiper PA-28RT-201T · Grand Canyon, AZFailure of the an tee fitting, thereby allowing the oil to be pumped overboard causing the engine failure. The failure of the tee fitting was caused by the tie wrap used to secure the line. The tie wrap pulled the oil line and stressed one side of the tee…Jun 5, 1988 · N2131N · Substantial damage NTSB ATL86FLQ03Accident · Minor injuriesFinal reportPiper PA-28RT-201T · Hopkinsvile, KYThe acft had electrical failure during an IFR flt and radio/radar contact was lost. The plt said he was in & out of the clouds during the final stages or the x-country flt. The cloud ceiling was about 800 ft where he finally descended & landed in a soybean…Oct 23, 1985 · N8277Y · Substantial damage NTSB FTW83LA410Accident · No injuriesLimited investigationFinal reportPiper PA-28RT-201T · Lake Charles, LAThe acft collided with trees about 50 ft off the right side of the rwy after the left brake failed during hard brake intermittent applications. Failure to release the right brake in a timely fashion caused the acft to swerve to the rightand off the rwy. The…Aug 27, 1983 · N8448H · Substantial damage NTSB DEN83FA111Accident · No injuriesField investigationFinal reportPiper PA28R-201T · Aurora, COThe plt received a jump start because the battery failed to start the eng. After departure & leveling of at 10,000 ft, he was concerned with the 1 inch of rime ice he had picked up & got an updated wx briefing from flt watch. He asked for & received a…May 13, 1983 · N2943Z · Substantial damage