Robinson R22 Helicopter Crashes: What Happened and What It Means for You

What the Robinson R22 Is and Who Operates It

The R22 is a helicopter built by Robinson Helicopter Company, the manufacturer name the National Transportation Safety Board uses in its records. The National Transportation Safety Board (NTSB) is the independent federal agency that investigates civil aviation accidents in the United States. In its final report on one Missouri accident, the NTSB describes "a Robinson Helicopter Company (RHC) R22 Beta II helicopter."

The NTSB's records list the aircraft under several model names, including the R22 Beta, the R22 Beta II and the R22 Mariner. One record lists two seats, skid landing gear and a certified maximum gross weight of 1,370 pounds. The recorded years of manufacture include 1994 and 2006, so aircraft of quite different ages are still flying.

The records also show how these helicopters were being used. Two state that the flight was conducted under "Part 91: General aviation - Instructional." Another lists "Part 91: General aviation - Other work use." Part 91 is the federal rule set for general aviation flights. Several records describe a flight instructor and a student pilot on board.

For someone who was injured, these details are where the question of responsibility begins: who was flying, who owned and maintained the aircraft, and under which rules the flight operated. A training flight at a flight school raises different questions than a privately owned helicopter flown by its owner. For a student or instructor on the flight, the useful details are the model and year of the aircraft, who operated the flight, and whether it was listed as instructional. An attorney can help sort out which of those facts bear on a claim. For a broader comparison of operation types, see the site's page on small plane crashes.

Nothing on this page states or suggests that the manufacturer, or any operator, caused an injury or did anything wrong.

Recent NTSB Accident Records for the Robinson R22

The five records below are the newest United States R22 records the site drew from the NTSB's accident dataset. That count of five is the site's own selection, not an NTSB statistic. Each report is linked by its own title.

Two terms help when reading them. A probable cause is the NTSB's formal statement of the cause or causes of an accident, issued in its final report. A preliminary report is an early factual summary released while the investigation is still under way.

On September 3, 2026, an R22 Beta was involved in an accident in McMinnville, Tennessee. The Aviation Investigation Final Report - Accident Number: ERA26LA327 records a hard landing, substantial damage and injuries of "1 Serious, 1 None." The dataset extract the site read on October 17, 2026 listed the highest injury as Minor and did not carry a probable-cause statement. The final report itself states the probable cause as "The flight instructor's delayed remedial action during a practice autorotation, which resulted in a hard landing."

On August 24, 2026, an R22 Beta was involved in an accident in Milton, Florida. The Aviation Investigation Final Report - Accident Number: ERA26LA313 records loss of control in flight and "2 Minor" injuries. The dataset extract carried no probable-cause statement. The final report states the cause as "The flight instructor's failure to maintain control of the helicopter during a low hover over a grass area, which resulted in left skid contact with the ground and a dynamic rollover to the left."

On August 15, 2026, an R22 Beta was involved in an accident in Miramar, Florida. The Aviation Investigation Final Report - Accident Number: ERA26LA304 records a dynamic rollover and "2 None" for injuries. The dataset extract carried no probable-cause statement. The final report states the cause as "The flight instructor's failure to maintain control of the helicopter during a hover, which resulted in the left skid contacting ground and a subsequent dynamic rollover."

On July 14, 2026, an R22 was involved in an accident in Monroe, North Carolina. The Aviation Investigation Notification - Accident Number: ERA26LA274 records an instructional flight, substantial damage and "2 None" for injuries. This investigation is open. The notification states, "This information is preliminary and subject to change," and says a final report "will be released at the conclusion of the investigation." No cause has been stated.

On October 21, 2025, an R22 was involved in an accident in Springfield, Missouri. The Aviation Investigation Final Report - Accident Number: CEN26LA027 states that the flight instructor and the pilot receiving instruction "both sustained serious injuries." The report gives the probable cause as "The pilot's failure to maintain directional control and the flight instructor's lack of proper remedial action during the practice autorotation that resulted in the helicopter impacting terrain." It adds, "Contributing to the accident was the presence of the gusting wind condition and the presence of speed shear."

These are the NTSB's words, not a finding of legal fault. 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."

In practical terms, a probable-cause line naming an instructor or pilot does not settle who is legally responsible, and an open investigation with no stated cause does not end the legal questions either. For anyone whose accident appears in these records, two details are worth noting: whether the report is final or preliminary, and what it lists for injuries, since the dataset and the final report can differ.

Why the NTSB Investigation Doesn't Decide Your Case

The NTSB's purpose explains why its conclusions stand apart from a lawsuit. Each final report above describes the investigation as fact-finding: "The NTSB does not assign fault or blame for an accident or incident." It quotes its regulation, which says investigations "are not conducted for the purpose of determining the rights or liabilities of any person."

The reports show what that fact-finding covers: the pilot's flight time and most recent flight review; the aircraft's registration, model, year of manufacture, and the date and type of its last inspection; and the weather, departure point and damage. One Florida record, for example, lists an annual inspection on June 29, 2026. Three records include an instructor's own statement. In the McMinnville report, the instructor reported "no preimpact mechanical malfunctions or failures of the helicopter that would have precluded normal operation."

The Federal Aviation Administration (FAA) has a separate role. The FAA issues pilot and other aviation certificates. The NTSB describes itself as the appellate authority for FAA certificate enforcement actions. In the Monroe notification, the participants include the FAA's local Flight Standards District Office in Charlotte.

Each final report also points to an investigation docket and notes that "A factual report that may be admissible under 49 United States Code section 1154(b) is available." The NTSB's final report and the evidence in a civil case are two different records. A civil case relies on its own evidence, such as logbooks, inspection records, training records, witness accounts, photos and the aircraft itself.

For an injured student, an instructor or a family, the stakes are plain: because the NTSB's report cannot be used in a civil damages case, the logbooks, maintenance and training records gathered for the case may carry its evidentiary weight. Questions a person in this position may weigh include who holds those records, whether the aircraft has been preserved, and what the docket contains. An attorney can help sort out which records exist and how they may be obtained.

Who May Be Responsible When an R22 Crash Causes Injury

Responsibility in civil law turns on legal elements, and an accident alone does not establish any of them. Two frameworks come up most often.

The first is negligence, which asks four questions. Did someone owe a duty to act with reasonable care? Did they breach that duty by falling short of it? Did that breach cause the harm (causation)? And did real losses result (damages)?

The second is product liability, the body of law that applies when the question is whether something about the helicopter itself played a role. It asks whether a product had a defect and whether that defect caused the injury. The crash on its own does not prove a defect; a product claim depends on evidence about the specific aircraft or part involved.

Depending on the facts, the people and companies whose roles may come into question include the operator who ran the flight, a flight school and its instructors, a company that maintained the aircraft, and the manufacturer of the aircraft or a component. This is a list of roles, not a statement about any particular company; whether anyone is responsible depends on what happened and what the evidence shows. The site's page on pilot error explains why an investigative label is not the same as a court's decision.

When a crash takes a life, the claim is often a wrongful death action, a lawsuit brought on behalf of the family or estate of a person who died because of another's wrongful act. Who may bring it, and what it may cover, is set by state law. The site's page on aviation wrongful death covers that path.

State law governs most of these questions. Limitation periods, comparative fault rules and damages rules differ from state to state, and no one state's rule applies everywhere. Federal aviation rules and state injury law operate as separate layers, and how they interact depends on the facts and the courts involved. The site's aviation accident lawyer guide explains those layers in more depth.

What Your Attorney Has to Prove in an R22 Claim

In an R22 case, a negligence claim has to connect specific conduct to the injury, such as how a flight was supervised, how the aircraft was maintained or how a flight was planned. Each of the four elements described above must be shown with evidence.

A product claim usually takes one of three forms, depending on what is claimed to have gone wrong. A manufacturing defect claim says a particular unit or part did not match its intended design. A design defect claim says the design itself is unreasonably dangerous. A failure-to-warn claim says the instructions or warnings were inadequate. Each requires proof that the claimed defect caused the harm.

Because § 1154(b) keeps Board reports out of a civil action for damages resulting from a matter mentioned in the report, the NTSB's conclusion, whatever it says, does not decide the claim. Each side builds its own evidence. Injured people and families often keep medical records, photos and video, flight-school paperwork and enrollment documents, and the names of people who saw the flight.

If the elements are proven, the damages the law may allow include medical expenses, lost earnings, and pain and suffering. In a death case, they include the wrongful-death damages that state law names. Which categories apply, and whether any limits exist, depends on the state and the facts.

For anyone working out how these elements line up with a particular flight, a conversation can cover the NTSB record, the aircraft's history and the injuries involved. A case evaluation is available to talk it through.