Piper PA-32 Accidents: What Families and Survivors Need to Know

Which PA-32 Model Was Involved, and Why It Matters to Your Questions

If you are reading an NTSB report about a PA-32, the first thing to know is that the name covers several related airplanes, not one. The NTSB identifies each accident airplane by its exact model number. The records on this page name the PA-32-260, the PA-32-300 and the PA-32R-300, and the dataset behind this page also includes the PA-32-301. The model number tells an investigator, and later a court, which airplane design is involved.

The NTSB's final report on one PA-32-300, accident ERA26LA336, lists the airplane's year of manufacture as 1966, its engines as "1 Reciprocating," its landing gear type as tricycle, its seats as 6 and its certified maximum gross weight as 3,400 pounds. It also records an annual inspection on January 1, 2026. Those details describe that one airplane. Other PA-32s differ by model and year.

How the airplane was being flown matters as much as which model it was. Several records here list "Part 91: General aviation - Personal," and one lists "Part 91: General aviation - Business." Part 91 refers to the general set of federal operating rules for flights like these. A charter flight, in which a company carries passengers for hire, is commonly called a Part 135 operation. Flight schools operate under their own federal requirements.

For you, the type of operation is more than a label. It affects which federal rules applied and who had duties to the people on board: a private owner-pilot, a charter company, a flight school or a maintenance shop. Knowing the model and the flight's purpose is often where an early conversation with an attorney begins. State injury and product-liability law is a separate layer, explained below.

What Recent NTSB Records Show About PA-32 Accidents, and What an Open Report Means for Your Family

The five records below come from the NTSB's own accident dataset, listed newest first. They are a sample this site selected, not an NTSB count. Records from California are not included on this national page. None of these records says anyone was at fault, and none should be read as proof of a defect or of anyone's negligence.

• ERA26LA336: September 9, 2026, West Kingston, Rhode Island. The aircraft was a Piper PA-32-300, and the highest injury recorded was none. The NTSB published the Aviation Investigation Final Report - Accident Number: ERA26LA336. It records the defining event as a "Runway excursion" and states this probable cause: "The pilot's failure to bring the airplane to a stop on the available runway, which resulted in a runway excursion." The report also states that the pilot reported no preaccident mechanical malfunctions or failures, and that a postaccident examination found no discrepancies in the flaps or brakes.
• ERA26LA322: August 21, 2026, Thomaston, Georgia. The aircraft was a Piper PA-32R-300, and the highest injury recorded was none. The NTSB's Aviation Investigation Notification - Accident Number: ERA26LA322 states that this is a Class 4 investigation. It says "a preliminary report will not be issued but a final report will be released at the conclusion of the investigation." The investigation is open.
• ERA26LA296: the dataset entry lists a Piper PA32, with the highest injury recorded as serious. The entry does not state a date or place, and this page links no NTSB report for it, so nothing further is said about it here.
• ANC26LA080: August 6, 2026, Pinetown, North Carolina. The aircraft was a Piper PA-32-260, and the highest injury recorded was minor. The Aviation Investigation Preliminary Report - Accident Number: ANC26LA080 states that the private pilot and two passengers had minor injuries. According to the pilot's account, the engine had a total loss of power in cruise flight, followed by a forced landing in a wooded area. The report marks itself "preliminary and subject to change," and the investigation is open.
• CEN26LA202: May 22, 2026, Comanche, Texas. The aircraft was a Piper PA-32R-300, and the highest injury recorded was none. The Aviation Investigation Preliminary Report - Accident Number: CEN26LA202 recounts a reduction and then a total loss of engine power after takeoff, followed by a forced landing in a field. It states that the wreckage was recovered for an examination still to be conducted. The investigation is open.

These reports come in three kinds. A preliminary report is an early factual summary issued while the investigation is still open. An investigation notification is a short early notice; in ERA26LA322, it is the only document the NTSB will release before its final report. A final report closes the investigation and gives the NTSB's analysis and probable cause.

As of October 17, 2026, the NTSB's dataset did not carry a probable-cause statement for any of these five events. ERA26LA336 is the one exception in practice: its final report, quoted above, does state a probable cause. For the other four, the NTSB has not stated a cause, and this page names none.

If your family's accident is still open, the official explanation may not exist yet, and an early report can change. Knowing which kind of report you are holding helps set expectations about what it can tell you now.

Waiting on the NTSB: What Its Investigation Can and Cannot Tell Your Family

The National Transportation Safety Board (NTSB) is, in its own words, "an independent federal agency charged by Congress with investigating every civil aviation accident in the United States." Its reports explain that it determines "the probable causes of the accidents and events we investigate" and issues safety recommendations. The reports also say the agency offers "information and other assistance to family members and survivors for each accident or event we investigate."

A probable cause is the NTSB's official statement of what it determined led to an accident, and it appears in the final report. For a family waiting on answers, that statement carries real weight as the federal government's considered explanation. But it is not a court's finding of legal fault. The NTSB's reports state that the agency "does not assign fault or blame," and they quote its regulation that investigations "are not conducted for the purpose of determining the rights or liabilities of any person."

Federal law keeps the investigation and a lawsuit apart in a second way. Under 49 U.S.C. § 1154(b), "No part of a report of the Board, related to an accident or an investigation of an accident, may be admitted into evidence or used in a civil action for damages resulting from a matter mentioned in the report." The ERA26LA336 final report repeats this rule. It adds that "a factual report that may be admissible" under the same section is available. In plain terms, the NTSB separates its analysis and probable cause from the underlying factual material it gathered. That factual report can matter because, unlike the NTSB's conclusions, the NTSB itself describes it as possibly usable in a civil case, so it may be one of the few parts of the federal file a court can consider.

For a family, the result is two parallel tracks. The NTSB works toward a safety finding on its own timeline, which may run long after the accident. A civil case, if there is one, has to prove its facts through its own evidence, and that track does not wait for the NTSB to finish. All four linked records here note that "the NTSB did not travel to the scene of this accident," which is one more reason other records can carry weight. Each investigation's status can be followed on the NTSB's public data site. Similar records for other aircraft appear on this site's page on Beechcraft Bonanza accidents.

Who May Be Responsible When a PA-32 Goes Down

If you were hurt, or your family lost someone, responsibility is not decided by the fact of the crash. It is decided by legal standards applied to the facts. Two frameworks come up most often.

The first is negligence. A negligence claim on your behalf would have to show four things: that someone owed the people on board a duty of care; that they fell short of what a reasonably careful person would do; that this shortfall caused the harm; and that there were real damages, such as injury or death. A gap in any one element can affect the whole claim. The second framework is product liability, which asks whether a product, such as an airplane or one of its parts, had a defect and whether that defect caused the harm. A defect may be in the design, in how one unit was made, or in the warnings and instructions that came with it.

Several kinds of parties may have their roles examined, depending on what happened:

• A pilot is generally expected to operate the airplane with reasonable care and to follow the federal operating rules for the flight.
• An aircraft owner may have duties about who flies the airplane and how it is kept up.
• A charter operator generally works under stricter federal operating rules than a private flight.
• A maintenance provider is expected to inspect and repair to required standards.
• A manufacturer of the airplane or a component is the focus of product-liability questions about design, manufacture and warnings.

Federal aviation regulations set minimum standards for operators and maintenance. Whether anyone met them, and whether that mattered, depends on the facts. Nothing on this page suggests that any pilot, owner, operator, maintenance provider or manufacturer was at fault in any accident listed here. What is at stake for you is which of these parties' roles can be examined at all, since that shapes who a claim could involve. A case evaluation is a conversation with our attorney about what happened and which framework may apply. This site's aviation accident lawyer page explains the federal and state layers more broadly.

Why Limitation Periods and Fault Rules Differ Across States, and Why Your State Matters

Most claims after a PA-32 accident are decided under state law, and the state rules are not uniform. A limitation period, also called a statute of limitations, is the deadline for filing a civil claim. A claim filed after the deadline can generally be barred, however strong it might otherwise be. Each state sets its own period, when the clock starts and what exceptions apply. For a family, that means the timing question can matter as much as the facts of the flight.

Fault rules differ too, and they can change what an injured person may recover. In a state that uses comparative fault, if you were found partly at fault, your share would reduce what you may recover rather than end the claim, though some states cut off recovery past a set share. In the few places that keep the older contributory-fault rule, any fault by the injured person can bar recovery entirely.

Wrongful death is a claim brought after someone dies because of another's wrongful act or neglect. Each state's wrongful-death rules decide who may bring the claim, what losses the law may allow and how long the family has. Damages rules, meaning the categories of loss the law may recognize, such as medical expenses, lost earnings and pain and suffering, also vary.

For a family, the first question is often not what happened in the air but which state's law governs and when its deadline began to run. If the wrong state's rules were assumed, a family could misjudge both its deadline and how fault is weighed. An accident's location, where people live and where the aircraft was based can all bear on that. Texas is one example with its own rules, covered on this site's Texas aviation accident lawyer page. Which state's law applies and when a deadline runs is one of the first things you can talk through with our attorney in a case evaluation.

Records That Can Help Tell Your Family's Side After a PA-32 Accident

The NTSB's file is only part of the record. Because federal law keeps its reports out of a damages case, other records tend to carry more of the weight. For you, that means the papers and images families hold may end up being some of the most useful evidence of what happened, the airplane's condition and what the people on board lost.

If you were hurt, the records that usually matter include medical records describing the injuries and treatment. Survivors and families also often keep photos and video from the scene or of the airplane, incident reports and official reports, and the names and contact details of people who saw what happened. The airplane's maintenance logs and inspection records come up often, because they show its history; the ERA26LA336 final report, for instance, records the date and type of the last inspection.

The NTSB and the FAA keep their own records of an accident and an aircraft, and two of the linked reports list FAA participants in the investigation. Some of what matters, such as the agency findings and the wreckage, rests with others. A conversation with an attorney can help sort out which records are within a family's reach and which are not. Comparable records for another aircraft type appear on this site's page on Cessna 208 Caravan accidents.