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.
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.
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.
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.
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.
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.
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). 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.
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.
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:
What is a Preliminary Report? What is the Carbon Cub FX? Is the investigation complete? Sources: NTSB Preliminary Report, CubCrafters Official Statement, KBOI-TV (CBS 2), Gem County Sheriff’s Office
NTSB Releases Preliminary Findings on Fatal Carbon Cub Crash in Idaho
Accident Sequence and Site Details
Wire Strike and Impact
Wreckage Recovery
Aircraft and Operational Context
Media Evaluation Program Suspended
Victim Profiles
AirPro News Analysis
Investigation Timeline
Frequently Asked Questions
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.
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.
No. The investigation is ongoing. A full determination of probable cause typically takes more than a year to complete.
Photo Credit: CubCrafters
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.
This article summarizes reporting by Houston Public Media and Adam Zuvanich.
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.
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.
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)
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
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.
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.
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:
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
The airline apologized to customers for the delay, and the flight completed its journey to Atlanta later that morning without further incident.
Delta Flight Returns to Houston Following Passenger Disturbance and Reported Assault
Incident Timeline and Police Response
Discrepancy in “Cockpit Breach” Accounts
AirPro News Analysis
Reports of Physical Assault
Regulatory Context and Statistics
Sources
Photo Credit: AirNav Radar
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.
This article is based on an official press release from the FAA.
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.
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
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. 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
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.
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.
What is an Operations Specification (OpSpec)? Does this ban diversity in hiring? What happens if an airline does not comply?
Transportation Secretary Duffy Announces Mandate for Merit-Based Pilot Hiring, Targets DEI Initiatives
New “Operations Specification” Mandate
Enforcement and Compliance
Shift in Federal Aviation Policy
AirPro News analysis
Frequently Asked Questions
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.
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.
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
Regulations & Safety
NTSB Report Blames FAA Airspace Failures for Deadly Potomac Midair Collision
The NTSB final report identifies FAA airspace design flaws and lack of collision avoidance tech as causes of the 67-fatality Potomac midair collision near DCA.
This article is based on an official report and press materials from the National Transportation Safety Board (NTSB).
The National Transportation Safety Board (NTSB) has issued its final report on the catastrophic midair collision between a Bombardier CRJ700 and a U.S. Army Sikorsky UH-60 Black Hawk over the Potomac River. In findings released on January 27, 2026, the Board determined that the accident, which claimed 67 lives on January 29, 2025, was driven primarily by “deep underlying systemic failures” within the Federal Aviation Administration’s (FAA) airspace design rather than simple pilot error.
The collision, which occurred approximately 0.5 miles southeast of Ronald Reagan Washington National Airport (DCA), resulted in the deaths of all 64 passengers and crew aboard American Airlines Flight 5342 (operated by PSA Airlines) and the three crew members of the Army Helicopters. It stands as the deadliest U.S. commercial aviation disaster since 2001, ending a 16-year safety streak for U.S. passenger airlines.
According to the NTSB’s Investigation (DCA25MA108), the probable cause was the FAA’s failure to separate helicopter routes from commercial approach paths, compounded by an overreliance on “see and avoid” visual separation protocols in a complex, high-traffic environment.
The NTSB report identifies the proximity of “Route 4”, a published helicopter route along the Potomac River, to the active approach path for Runway 33 at DCA as the critical flaw. Investigators found that the FAA had placed these routes without sufficient vertical or lateral separation, creating a hazard that went unmitigated despite previous safety recommendations.
At the time of the accident, air traffic control relied on pilots to visually identify and avoid other aircraft. However, the NTSB concluded that this method was inadequate for the conditions present on the night of the crash. Cockpit simulations conducted during the investigation revealed that the Black Hawk’s position lights were “barely visible” to the CRJ700 crew against the bright backdrop of Washington, D.C., city lights until mere seconds before impact.
“This complex and comprehensive one-year investigation identified serious and long-standing safety gaps in the airspace over our nation’s capital. Sadly, the conditions for this tragedy were in place long before the night of Jan. 29.”
, Jennifer Homendy, NTSB Chair
While the primary blame was placed on airspace design, the NTSB identified several contributing factors related to equipment and military oversight. The investigation found that the Black Hawk crew likely believed they were complying with the route’s 200-foot altitude ceiling. However, due to allowable equipment tolerances and airflow disruption caused by wing-mounted stores, the helicopter was actually flying at approximately 300 feet, 100 feet higher than the crew’s instruments indicated. This deviation placed the helicopter directly into the descent path of the incoming commercial jet.
The report highlighted a critical lack of collision avoidance technology on both aircraft:
NTSB simulations indicated that if the CRJ700 had been equipped with functioning ADS-B In technology, the crew could have received an alert 59 seconds before the collision, potentially allowing enough time to take evasive action.
One of the most startling revelations in the final report is the frequency of similar conflicts in the airspace surrounding DCA. The investigation uncovered that between October 2021 and December 2024, there were 15,214 occurrences where an airplane and a helicopter were separated by less than one nautical mile laterally and 400 feet vertically.
NTSB Board Member Michael Graham described the accident as the result of a “multitude of errors,” noting that the sheer volume of near-miss data suggests a failure by organizations to foster robust safety cultures that would have identified the risk earlier.
The revelation of over 15,000 proximity events in just three years raises serious questions about the efficacy of voluntary reporting systems and the FAA’s internal review processes. While the “see and avoid” concept is a cornerstone of VFR (Visual Flight Rules) flight, applying it as a primary separation tool in one of the nation’s most restricted and congested airspaces appears, in hindsight, to be a calculated risk that failed.
This report will likely force a paradigm shift in how mixed-use airspace is managed near major metropolitan airports. The days of relying on visual separation for military and general aviation traffic operating underneath heavy commercial corridors may be ending, replaced by rigid positive control and mandatory electronic conspicuity.
In response to the tragedy, the NTSB has issued 50 new safety recommendations aimed at preventing a recurrence. Key directives include:
Following the accident, the FAA temporarily closed Route 4. The NTSB’s findings effectively recommend that this closure be made permanent or that the route undergo a drastic redesign to eliminate the conflict with commercial traffic.
Sources: NTSB Final Report (AIR-26-02), NTSB Investigation Page (DCA25MA108)
NTSB Final Report: Systemic Airspace Failures Caused Fatal Potomac Midair Collision
Probable Cause: Airspace Design and Regulatory Oversight
The Failure of Visual Separation
Contributing Factors: Technology and Equipment Gaps
Altimeter Discrepancies
Missing Safety Technology
A History of Near Misses
AirPro News Analysis
Recommendations and Path Forward
Sources
Photo Credit: NTSB
-
Regulations & Safety6 days agoFour Killed in Tennessee-Registered Plane Crash Near Steamboat Springs
-
Regulations & Safety5 days agoJet2 Flight Diverts to Brussels After Violent Midair Altercation
-
Business Aviation7 days agoBombardier Exceeds 2025 Targets and Projects $10B Revenue in 2026
-
Technology & Innovation5 days agoHorizon Aircraft Partners with North Aircraft for Cavorite X7 Wing Production
-
Regulations & Safety2 days agoNTSB Report Blames FAA Airspace Failures for Deadly Potomac Midair Collision
