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.

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.
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
Regulations & Safety
Missouri Skydive Plane Crash Kills 12 at Butler Airport
A Pacific Aerospace 750XL crashed after takeoff from Butler Memorial Airport on June 14, 2026, killing a pilot and 11 skydivers.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by CBS News, The Washington Post, SFGATE, KEYT, and Fox 10 Phoenix.
A Pacific Aerospace 750XL operated by Skydive Kansas City crashed shortly after takeoff from Butler Memorial Airport (BUM) on June 14, 2026, resulting in 12 fatalities.
The Missouri State Highway Patrol confirmed that the pilot and 11 skydivers died when the single-engine turboprop impacted a field adjacent to the airport and caught fire. The NTSB and the FAA have deployed investigators to the site, located approximately 65 miles south of Kansas City.
Accident sequence and emergency response
The aircraft departed BUM at approximately 11:20 a.m. local time. According to preliminary reports cited by SFGATE, the aircraft made a left turn shortly after takeoff. Emergency responders received a 911 call around 11:30 a.m. reporting that the aircraft had crashed into a field approximately 300 yards from the runway and was engulfed in flames.
Dennis Jacobs, acting airport manager and Bates County Emergency Management Agency director, told reporters that the aircraft appeared to lose power before stalling and impacting the ground nose first. The NTSB has not yet verified this sequence of events, and the official cause of the accident remains under investigation.
The Missouri State Highway Patrol, alongside the Butler Police Department and Bates County Sheriff’s Office, secured the scene. A statement from the highway patrol confirmed that all 12 occupants perished in the crash. The identities of the victims are being withheld pending family notification.
Aircraft and operator background
The aircraft involved was a Pacific Aerospace 750XL manufactured in 2010. The 750XL is a single-engine turboprop frequently utilized in commercial skydiving operations due to its climb rate and payload capacity. The flight was operated by Skydive Kansas City, a commercial skydiving center based at BUM.
This accident follows a previous skydiving-related aviation occurrence near the same airport. On May 25, 2024, a Cessna U206C experienced an in-flight emergency near BUM. In that incident, the pilot and six skydivers successfully evacuated the aircraft via parachute before it crashed into a hayfield, resulting in no fatalities.
AirPro News analysis
We note that the NTSB investigation will likely focus on engine performance, weight and balance, and environmental factors at the time of departure. The Pacific Aerospace 750XL is a specialized utility aircraft, and investigators will examine maintenance records and the operator’s procedures as part of their standard protocol. Until the NTSB releases its preliminary report, usually within 30 days, any statements regarding a loss of power remain unconfirmed eyewitness observations.
Sources: CBS News
Photo Credit: NZAero
Regulations & Safety
FAA Investigates Southwest Airlines Near Miss at Nashville
Two Southwest Boeing 737s came within 500 vertical feet near Nashville on April 18, 2026, after an ATC error during a go-around.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by CNN, Fox News, and The Washington Post.
Two Southwest Airlines (WN) Boeing 737 aircraft passed within 500 vertical feet of each other near Nashville International Airport (BNA) on April 18, 2026, after air traffic control instructions placed an aborting arrival into the path of a departing flight.
The incident, which occurred at approximately 5:30 p.m. local time, prompted both flight crews to execute evasive maneuvers following onboard Traffic Collision Avoidance System (TCAS) alerts. The Federal Aviation Administration (FAA) has launched an investigation into the airspace separation loss, which highlights ongoing scrutiny over air traffic control protocols and collision avoidance effectiveness.
Sequence of events and evasive maneuvers
According to statements provided to CNN and Fox News, Southwest Airlines Flight 507 was arriving from Myrtle Beach, South Carolina, when the flight crew initiated a precautionary go-around due to gusty wind conditions at BNA. During this maneuver, air traffic controllers instructed the crew to turn right.
The FAA confirmed in a statement that these instructions placed Flight 507 directly into the departure path of Southwest Airlines Flight 1152, which was taking off from a parallel runway bound for Knoxville, Tennessee. As the aircraft converged, TCAS resolution advisories activated in both cockpits. Flight tracking data from Flightradar24 indicates the two Boeing 737s came within 500 vertical feet of one another before the crews successfully altered their trajectories.
Both aircraft continued to safe landings without further incident. Flight 507 completed its arrival into Nashville on a subsequent approach, while Flight 1152 proceeded to its destination in Knoxville.
Regulatory investigation and safety context
The FAA is currently investigating the circumstances that led to the loss of separation. Southwest Airlines issued a statement emphasizing that the pilots of Flight 507 were complying with air traffic control directives when the conflict occurred, and that the crews responded professionally to the onboard traffic alerts to maintain safety.
The Nashville incident occurs against a backdrop of heightened national attention on mid-air collision risks. The Washington Post notes that aviation safety systems have faced intense public and regulatory scrutiny following a January 29, 2025, collision between an American Airlines aircraft and a military helicopter near Washington, D.C., which resulted in 67 fatalities. While the circumstances of the two events differ, the 2025 accident has amplified focus on the reliability of TCAS and air traffic control coordination in congested airspace.
AirPro News analysis
The activation of TCAS resolution advisories in this incident demonstrates the critical role of automated safety nets when procedural separation fails. While the FAA investigation will ultimately determine the root cause of the controller instructions, the event underscores the vulnerability of the go-around phase. Go-arounds are dynamic maneuvers that rapidly alter an aircraft’s energy state and expected flight path. These maneuvers require immediate and precise coordination between the flight deck and air traffic control, particularly when parallel runway operations are active.
Sources: CNN (via KESQ)
Photo Credit: Flightradar24 – Google Earth via CNN Newsource
Regulations & Safety
FAA Investigates Southwest Airlines Ground Collision at PVD
Two Southwest Boeing 737s collided during pushback at Rhode Island T.F. Green Airport on June 11, 2026. FAA investigation opened.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by WPRI, NBC 10, Daily Voice, and CBS News Baltimore.
The Federal Aviation Administration (FAA) has opened an investigation after two Southwest Airlines Boeing 737 aircraft collided during pushback at Rhode Island T.F. Green International Airport (PVD) late on June 11, 2026.
The ground collision resulted in no reported injuries but forced the cancellation of both flights and the grounding of the involved aircraft for mandatory safety inspections. According to reporting by the Daily Voice and NBC 10, the incident highlights ongoing operational challenges on airport ramps, occurring just weeks after a similar event involving the same carrier at another East Coast facility.
Details of the ground collision
At approximately 10:45 p.m. local time, Southwest Airlines Flight 3515, bound for Ronald Reagan Washington National Airport (DCA), was pushing back from its gate. During the maneuver, the aircraft’s wing made contact with the tail of Southwest Airlines Flight 3409, which was scheduled to depart for Chicago Midway International Airport (MDW).
Both aircraft returned to their respective gates following the contact, allowing passengers to deplane normally. Southwest Airlines confirmed that no injuries occurred among passengers or crew members. The carrier subsequently canceled both flights and reaccommodated the affected travelers.
“Southwest Airlines is aware of an incident involving two of our aircraft at Rhode Island T. F. Green International Airport. We are investigating further and will be thoroughly inspecting the two aircraft,”
the airline stated in remarks provided to local media, adding that safety remains its highest priority.
Local media outlets, including NBC 10, reported passenger accounts suggesting that Flight 3515 continued to move briefly after the initial impact. These accounts claim passengers verbally alerted the flight crew to the collision. Neither Southwest Airlines nor the FAA has officially verified these specific passenger narratives, and the official sequence of events remains under investigation.
Regulatory response and recent precedent
The FAA confirmed on June 12, 2026, that it is investigating the circumstances surrounding the collision. Ground operations during pushback rely heavily on coordination between flight crews and ground personnel, particularly in ramp areas where air traffic controllers do not maintain direct communication with the aircraft.
This event follows a comparable occurrence on May 4, 2026, at Baltimore/Washington International Thurgood Marshall Airport (BWI). In that instance, two Southwest Airlines Boeing 737s clipped wings during pushback operations. The FAA investigated the BWI incident, noting the specific communication dynamics between ground crews and the flight deck in non-controlled ramp sectors.
AirPro News analysis
We note that while ground collisions during pushback rarely pose a severe threat to passenger safety, they represent a significant operational and financial burden for carriers. Ramp incidents require immediate grounding of the involved airframes, triggering mandatory structural inspections and potential repairs. The recurrence of pushback-related contact within a single airline’s network over a short period may prompt internal reviews of ground handling procedures, wingwalker positioning, and ramp communication protocols. Until the FAA concludes its investigation, the specific cause of the PVD collision remains undetermined.
Sources: WPRI
Photo Credit: Zachary Reis
-
Technology & Innovation4 days agoAirbus Vision Landing Application Enables AI Autoland
-
Defense & Military3 days agoBoeing Withdraws T-7A Red Hawk from Navy UJTS Competition
-
Training & Certification5 days agoAirbus Overhauls Pilot Training With VR and CBTA Standards
-
Commercial Aviation3 days agoAirbus A350-1000ULR EASA Certification Campaign Begins
-
Regulations & Safety3 days agoTurkish Airlines 777-300ER Wing Strike at Antalya Airport
