Connect with us

Regulations & Safety

NTSB Preliminary Report on Fatal Pelegrin Tarragon Crash in Arizona

The NTSB released a preliminary report on the fatal crash of an experimental Pelegrin Tarragon aircraft in Arizona, with investigation ongoing.

Published

on

This article is based on an official preliminary report from the National Transportation Safety Board (NTSB) and public FAA registry data.

NTSB Issues Preliminary Findings on Fatal Experimental Aircraft Crash in Arizona

The National Transportation Safety Board (NTSB) has released its preliminary report regarding the fatal accident involving an experimental amateur-built Pelegrin Tarragon aircraft in Arizona. The crash, which occurred on February 6, 2026, resulted in the death of the pilot and injuries to a surviving passenger.

According to the NTSB’s findings released on February 18, 2026, the aircraft, registered as N35RR, was destroyed after impacting terrain in a remote desert environment near Shawmut, Arizona. The accident site is located near a railroad siding southeast of Gila Bend in Maricopa County. Investigators confirmed that the flight was operating under Part 91 general aviation rules as a personal flight at the time of the incident.

The release of this preliminary document marks the first official step in an investigation that is expected to continue for at least a year. While the report establishes the factual circumstances gathered at the scene, the NTSB emphasizes that it does not yet determine the probable cause of the tragedy.

Crash Timeline and Site Details

The accident occurred at approximately 19:30 (7:30 PM) local time on Friday, February 6. The NTSB report indicates that the aircraft was navigating the Gila Bend area when the crash sequence initiated. Visual Meteorological Conditions (VMC) prevailed at the time, suggesting that weather may not have been a primary restricting factor, though specific visibility and wind data will likely be analyzed further in the full factual report.

The crash site in Shawmut is characterized by flat, open desert terrain often utilized for general aviation transit. However, the area presents significant challenges for emergency landings due to uneven ground and scrub brush. The aircraft reportedly sustained substantial damage upon impact.

“Preliminary data suggests the aircraft impacted terrain in a remote desert environment. The specific sequence of events leading to the impact is currently under investigation.”

— National Transportation Safety Board (NTSB) Preliminary Report

Investigative Focus

Federal investigators are currently examining several critical components of the wreckage. The NTSB has stated that the investigation will focus on the airframe, the flight controls, and the Rotax 915 iS engine (approximately 141 hp) to rule out or identify any pre-impact mechanical anomalies. Additionally, investigators noted that the statement from the surviving passenger will be a “critical component” of the ongoing inquiry.

Advertisement

Aircraft and Pilot Background

The aircraft involved was a Pelegrin Tarragon, a high-performance tandem-seat ultralight originally designed in Latvia. Known for its carbon-fiber construction and speed capabilities of up to 190 knots, the aircraft is often registered in the United States under the Experimental Amateur-Built category. This classification typically requires the owner to participate significantly in the aircraft’s construction.

According to FAA registry records cited in the report context, the aircraft (N35RR) was registered to Red Baron Snoop Dog LLC based in Lewes, Delaware. The airworthiness certificate was issued in August 2022, listing Robert G. Elves as the manufacturer.

Pilot Profile

The pilot, identified as Dr. Robert G. Elves, was the sole fatality in the accident. Background information included in the report context describes Elves as a retired U.S. Air Force officer and chemist. He was a recognized member of the aviation community and a member of the Aircraft Owners and Pilots Association (AOPA). Elves was also known for advocating safety measures, specifically the use of helmets in general aviation cockpits.

AirPro News Analysis: The Path to a Final Report

The release of a preliminary report is a standard procedure for the NTSB, typically occurring within two weeks of an accident. It serves to inform the public and the aviation industry of the basic facts established on-site. However, stakeholders should note that the investigation is far from complete.

The next major milestone will be the release of the Factual Report, which usually arrives several months later. This document will provide a deep dive into pilot logs, maintenance records, and toxicology results, offering a comprehensive view of the human and mechanical factors involved. The final determination of probable cause is generally not released until the Final Report is completed, a process the NTSB estimates will take between 12 and 24 months.

As the investigation progresses, the NTSB will post publicly available factual data, including photos and witness statements, to its Docket Management System.


Sources

Photo Credit: NTSB

Continue Reading
Advertisement
Click to comment

Leave a Reply

Regulations & Safety

NTSB Preliminary Report on Fatal Carbon Cub Crash in Idaho

The NTSB released a preliminary report on the fatal CubCrafters Carbon Cub crash in Idaho involving a wire strike and two fatalities.

Published

on

This article is based on the preliminary report released by the National Transportation Safety Board (NTSB) and official statements from CubCrafters.

NTSB Releases Preliminary Findings on Fatal Carbon Cub Crash in Idaho

The National Transportation Safety Board (NTSB) has released its preliminary report regarding the fatal aviation accident that occurred on January 27, 2026, near Montour, Idaho. The crash of the CubCrafters CCX-1865 Carbon Cub, registered as N126C, resulted in the deaths of two individuals, including a prominent local meteorologist. The report confirms that the aircraft collided with power lines while operating in the rugged terrain of the Payette River’s Black Canyon.

According to the NTSB’s findings, the flight was part of a “Media Evaluation Program” conducted by the aircraft manufacturer, CubCrafters. The program, which allowed media figures to evaluate aircraft for content creation, has been suspended following the tragedy. Investigators have recovered data recording devices, including GoPro cameras, which may provide critical insight into the final moments of the flight.

Accident Sequence and Site Details

The preliminary report outlines the specific timeline and trajectory of the accident. On the morning of January 27, the aircraft was operating under Part 91 general aviation rules in Gem County, Idaho. The flight took place in the Black Canyon area, a region known for its scenic river views but also for the hazards presented by its complex terrain.

Wire Strike and Impact

Investigators determined that the accident sequence began at approximately 10:58 AM MST. The aircraft struck a set of power lines spanning the Payette River. The collision severed the lines, causing a significant power outage that affected an estimated 7,000 customers in Gem County and Garden Valley. Following the wire strike, the aircraft impacted the frozen surface of the river, coming to rest in the water and ice.

Wreckage Recovery

The wreckage was located within the icy river. During the recovery process, investigators secured GoPro cameras from the crash site. The NTSB has indicated that these devices could yield high-definition video evidence regarding the cockpit environment and flight parameters leading up to the collision.

Aircraft and Operational Context

The aircraft involved was a CubCrafters CCX-1865 Carbon Cub FX, a modern Short Takeoff and Landing (STOL) aircraft designed specifically for backcountry operations. The specific airframe, N126C, was owned by the manufacturer, CubCrafters, and had been loaned to the pilot for review purposes.

Media Evaluation Program Suspended

The flight was conducted under the auspices of CubCrafters’ “Media Evaluation Program.” This initiative provided aircraft to select aviation journalists and influencers for independent review. Following the accident, CubCrafters announced a temporary suspension of the program to review safety protocols. In a statement, the company expressed deep sadness regarding the loss of life and emphasized its cooperation with the NTSB and Federal Aviation Administration (FAA).

Advertisement

Victim Profiles

The crash claimed the lives of two experienced members of the aviation community.

Roland Steadham, 67, was identified as the pilot. Steadham was a well-known figure in Boise, Idaho, serving as the Chief Meteorologist for KBOI-TV (CBS 2). Beyond his broadcasting career, Steadham was a veteran aviator with over 3,000 flight hours. He held a commercial pilot certificate and possessed experience in a variety of aircraft, including gliders and jets.

Dallin Laufenberg was identified as the passenger. Reports suggest Laufenberg was an active member of the local aviation community, with some sources linking him to operations at Nampa Airport, though the NTSB report focuses primarily on the factual circumstances of the crash rather than biographical details.

AirPro News Analysis

The preliminary details of this accident highlight the persistent danger of wire strikes in low-level backcountry flying. River canyons often present a “terrain trap” where power lines are strung across gaps, becoming nearly invisible against complex backgrounds like running water, rocks, or snow. While the Carbon Cub is a highly capable STOL aircraft designed for this environment, the visibility of obstacles remains a critical human factor challenge. The recovery of onboard video will likely be pivotal in determining whether the wires were marked or if environmental conditions contributed to the pilot’s inability to see the obstruction in time.

Investigation Timeline

The current document released by the NTSB is a preliminary report, which contains factual information gathered at the scene but does not determine a probable cause. The investigation will proceed through several phases:

  • Factual Report: Expected in 12 to 18 months, this report will provide detailed technical analyses of the airframe, engine, pilot medical records, and weather data.
  • Final Report: This document will officially determine the probable cause of the accident and may include safety recommendations to prevent similar occurrences.

Frequently Asked Questions

What is a Preliminary Report?
An NTSB preliminary report is an initial document released shortly after an accident. It establishes the basic facts, such as time, location, and aircraft type, but does not analyze the cause or assign blame.

What is the Carbon Cub FX?
The Carbon Cub FX is a high-performance, lightweight aircraft modernized from the classic Piper Cub design. It is widely used for backcountry and off-airport operations due to its ability to take off and land in very short distances.

Is the investigation complete?
No. The investigation is ongoing. A full determination of probable cause typically takes more than a year to complete.

Sources: NTSB Preliminary Report, CubCrafters Official Statement, KBOI-TV (CBS 2), Gem County Sheriff’s Office

Advertisement

Photo Credit: CubCrafters

Continue Reading

Regulations & Safety

Delta Flight Returns to Houston After Passenger Disturbance and Assault

Delta flight from Houston returned due to a passenger disturbance involving an attempted cockpit breach and assault. FAA to investigate.

Published

on

This article summarizes reporting by Houston Public Media and Adam Zuvanich.

Delta Flight Returns to Houston Following Passenger Disturbance and Reported Assault

A Delta Air Lines flight departing from William P. Hobby Airports (HOU) in Houston was forced to make an emergency return early Wednesday morning, February 18, 2026, following a significant passenger disturbance. While initial reports from the flight deck indicated a potential attempt to breach the cockpit, the airline has since clarified the nature of the security threat.

According to reporting by Houston Public Media, the incident occurred shortly after takeoff on Delta Flight 2557, a Boeing 717 service bound for Atlanta. The aircraft, carrying 85 passengers and five crew members, returned safely to Houston approximately 15 minutes after departure.

Incident Timeline and Police Response

Data from FlightAware indicates that the flight departed HOU at approximately 5:25 a.m. local time. Within minutes of becoming airborne, the flight crew declared an emergency. The Houston Police Department (HPD) confirmed to local reporters that they received a call at 5:38 a.m. regarding a disturbance on board.

Upon the aircraft’s return to Hobby Airport at roughly 5:40 a.m., law enforcement officers met the plane at Gate 32. HPD officers subsequently detained a male suspect. Footage and witness accounts suggest the individual was led off the aircraft in handcuffs. The flight eventually re-departed for Hartsfield-Jackson Atlanta International Airport (ATL) approximately 90 minutes after the security event.

Discrepancy in “Cockpit Breach” Accounts

A notable divergence has emerged between the immediate operational communications from the pilots and the subsequent corporate statement released by Delta Air Lines regarding the severity of the threat to the flight deck.

According to audio recordings from Broadcastify, reviewed by AirPro News, the pilot explicitly informed air traffic control of the situation in real-time:

“We had a passenger get up and try to access the cockpit.”

, Pilot transmission, Delta Flight 2557 (via Broadcastify)

Advertisement

This radio message aligns with the initial statement provided by an HPD spokesperson, who noted the call was received because “someone tried to breach a cockpit.”

However, in a later statement, Delta Air Lines provided a nuanced clarification, emphasizing that the physical security of the flight deck was not compromised. The airline stated:

The customer “approached crew members and other passengers but did not make contact with or attempt to access the flight deck.”

, Delta Air Lines Official Statement

AirPro News Analysis

The difference between a pilot reporting an attempt to “access the cockpit” and a corporate statement denying an “attempt to access” often comes down to technical definitions. In post-9/11 aviation security, any aggressive movement toward the front galley while the aircraft is in flight is treated by the flight crew as an imminent threat to the cockpit, triggering immediate diversion protocols. Delta’s corporate clarification likely relies on the fact that the passenger did not physically touch or manipulate the reinforced cockpit door, despite moving aggressively in that direction.

Reports of Physical Assault

Beyond the security concerns regarding the flight deck, verified reports confirm that physical violence occurred in the cabin. During the exchange with air traffic control, the pilot requested paramedics meet the aircraft, stating that the suspect “did assault another passenger.”

Additional reporting by FOX 5 Atlanta included a witness account from a male passenger who stated he was punched by the suspect. The suspect’s identity has not been released, though unverified reports suggest the incident may have involved a mental health crisis.

Regulatory Context and Statistics

The Federal Aviation Administration (FAA) has confirmed it will investigate the incident. This event adds to the growing list of unruly passenger reports in 2026. According to FAA data cited in the research report:

  • 2025 Total: The agency recorded 1,621 unruly passenger incidents.
  • 2026 Year-to-Date: There have been approximately 126 reported incidents as of mid-February.

Delta Air Lines reiterated its stance on such disturbances in their statement to the press:

“The safety of our customers and crew is paramount, and Delta has zero tolerance for unruly behavior.”

, Delta Air Lines

Advertisement

The airline apologized to customers for the delay, and the flight completed its journey to Atlanta later that morning without further incident.

Sources

Photo Credit: AirNav Radar

Continue Reading

Regulations & Safety

FAA Mandates Merit-Based Pilot Hiring in New Operations Specification

The FAA issues a mandatory directive requiring U.S. airlines to adopt merit-based pilot hiring and end race or gender-based recruitment programs.

Published

on

This article is based on an official press release from the FAA.

Transportation Secretary Duffy Announces Mandate for Merit-Based Pilot Hiring, Targets DEI Initiatives

U.S. Transportation Secretary Sean P. Duffy has announced a significant shift in federal aviation policy, directing the Federal Aviation Administration (FAA) to issue a new mandatory “Operations Specification” (OpSpec) for all commercial airlines. The directive requires carriers to formally commit to merit-based hiring practices for pilots and certify the termination of recruitment programs based on race or gender.

The announcement, released through the FAA newsroom, frames the initiative as a measure to “purge DEI from our skies” and restore a focus on technical qualifications. According to the Department of Transportation (DOT), the move aligns with President Trump’s Executive Order on Ending Illegal Discrimination and Restoring Merit-Based Opportunity.

This policy marks a sharp departure from the previous administration’s approach, with Secretary Duffy explicitly criticizing prior directives as “absurd” and emphasizing that safety must remain the sole priority in aviation recruitment.

New “Operations Specification” Mandate

Under the new FAA directive, all U.S. commercial carriers must adopt the updated OpSpec, which legally obligates them to certify that their pilot hiring processes are exclusively merit-based. The FAA stated that failure to comply with this certification could subject airlines to federal investigation.

In the official release, Secretary Duffy emphasized the administration’s stance that demographic factors should play no role in the cockpit.

“When families board their aircraft, they should fly with confidence knowing the pilot behind the controls is the best of the best. The American people don’t care what their pilot looks like or their gender, they just care that they are most qualified man or woman for the job.”

, U.S. Transportation Secretary Sean P. Duffy

Enforcement and Compliance

The FAA has indicated that the new OpSpec is a “commonsense measure” designed to increase transparency between passengers and airlines. While the agency acknowledged that it has already raised performance standards and dismantled internal Diversity, Equity, and Inclusion (DEI) offices, the new mandate extends these requirements directly to private carriers.

Advertisement

FAA Administrator Bryan Bedford supported the Secretary’s position, stating that the agency’s primary focus remains the safety of the traveling public.

“It is a bare minimum expectation for airlines to hire the most qualified individual when making someone responsible for hundreds of lives at a time. Someone’s race, sex, or creed, has nothing to do with their ability to fly and land aircraft safely.”

, FAA Administrator Bryan Bedford

Shift in Federal Aviation Policy

The directive is part of a broader effort by the DOT to roll back policies established during the Biden-Buttigieg era. The press release explicitly mentioned the reversal of directives that “wasted time renaming cockpits to flight decks,” signaling a return to traditional aviation terminology and a rejection of language changes viewed by the current administration as ideological.

According to the FAA statement, the agency is acting on “allegations of airlines hiring based on race and sex,” though specific carriers were not named in the release. The mandate aims to ensure that technical knowledge, cognitive skills, and piloting experience are the only metrics used in hiring decisions.

AirPro News analysis

This new OpSpec represents a significant regulatory pivot for the U.S. aviation industry. By formalizing “merit-based” hiring into a mandatory Operations Specification, the FAA is moving the issue from political rhetoric to regulatory enforcement. Airlines, which operate under strict FAA certification rules, will likely need to review their internal HR policies to ensure they can sign the required certification without legal exposure.

While major U.S. airlines have historically maintained that safety is their top priority, many had also publicly embraced diversity initiatives in recent years to broaden their pilot pipelines. The new directive may force a restructuring of these programs to avoid the threat of federal investigation. It remains to be seen how the FAA will define “merit” in a legal context if an airline’s hiring practices are challenged, or how this mandate will interact with existing equal opportunity employment laws.

Frequently Asked Questions

What is an Operations Specification (OpSpec)?
An OpSpec is a legal document issued by the FAA to an airline that outlines the specific authorizations, limitations, and procedures under which the airline must operate. It is legally binding.

Does this ban diversity in hiring?
The directive requires hiring to be “exclusively merit-based” and demands certification that race or sex-based hiring practices are terminated. It frames DEI initiatives as contrary to merit-based principles.

Advertisement

What happens if an airline does not comply?
According to the press release, failure to certify compliance with the new mandate will subject the airline to a federal investigation.

Sources

Photo Credit: Pilot Headquarters

Continue Reading
Every coffee directly supports the work behind the headlines.

Support AirPro News!

Advertisement

Follow Us

newsletter

Latest

Categories

Tags

Every coffee directly supports the work behind the headlines.

Support AirPro News!

Popular News