Regulations & Safety
Near Mid Air Collision Between Delta Jet and B52 Bomber Over North Dakota
Delta Connection jet narrowly avoids mid-air collision with B-52 bomber near Minot ND, exposing military-civilian airspace coordination challenges.
Analysis of the Near Mid-Air Collision Involving a Delta Connection Jet and a B-52 Bomber Over North Dakota
On July 18, 2025, a Delta Connection regional jet narrowly avoided a mid-air collision with a U.S. Air Force B-52 bomber near Minot, North Dakota. The incident, which involved a quick and aggressive maneuver by the commercial pilot, has sparked renewed scrutiny over the coordination between civilian and military aviation operations in shared airspace. The Embraer E175, operated by SkyWest Airlines under the Delta Connection brand, was on final approach to Minot International Airport when it encountered the bomber, prompting evasive action.
This close call underscores persistent gaps in airspace management, especially near joint-use facilities like Minot Air Force Base. The pilot’s post-incident address to passengers, which was recorded and widely shared, brought transparency to a situation typically shrouded in procedural silence. While no injuries occurred, the event has raised questions about radar coverage, aircraft detection systems, and the protocols governing military and civilian flight coordination.
In this article, we explore the incident in detail, contextualize it within broader aviation safety trends, and examine the aircraft, systems, and regulatory frameworks involved. We aim to provide a balanced and factual analysis of what happened, why it matters, and what can be done to prevent similar occurrences in the future.
Detailed Account of the July 18, 2025 Incident
Delta Flight DL3788 departed from Minneapolis-Saint Paul International Airport en route to Minot, North Dakota. As the aircraft approached Minot International Airport, it was vectored by air traffic control for spacing adjustments. However, unknown to the crew, a B-52 bomber from nearby Minot Air Force Base was operating in the same airspace. The bomber was on a training sortie, reportedly performing pattern work near the airport.
At approximately six miles from the runway, the Delta flight crew visually identified the B-52 on a collision course. With no Traffic Collision Avoidance System (TCAS) alert, because the bomber’s transponder was either inactive or incompatible, the pilot had to rely on visual cues. The captain executed a sharp turn to avoid the bomber, which passed close by, alarming passengers who witnessed the event firsthand.
Following the maneuver, the aircraft performed a go-around and landed safely on a subsequent attempt. The pilot then addressed passengers over the intercom, describing the maneuver as “aggressive” and “not normal.” This candid communication was later praised for its transparency, though it also highlighted the lack of awareness between military operations and civilian air traffic control.
“It caught me by surprise, and it’s not normal at all.”, Delta Connection Captain, post-incident address to passengers.
Military and Civilian Airspace Coordination Challenges
Minot International Airport does not have its own terminal radar. Instead, it relies on visual separation procedures and limited data from nearby military radar systems. The ASR-11 radar at Minot Air Force Base theoretically provides surface-level coverage, but civilian air traffic controllers do not have real-time access to its data. Communication between military and civilian controllers is typically conducted via phone, introducing delays and potential for miscommunication.
Joint-use airfields like Minot operate under federal regulations that prioritize military operations, particularly during training exercises. According to 32 CFR §855.20, military aircraft are given precedence unless an emergency is declared. This regulatory framework can result in situations where civilian aircraft are unaware of nearby military traffic, especially if that traffic does not broadcast its position via ADS-B or compatible transponders.
The lack of integration between military and civilian radar, combined with procedural ambiguities, creates a high-risk environment during critical flight phases such as final approach. This incident illustrates the need for more robust coordination mechanisms and technological integration to ensure all aircraft operating in shared airspace are visible to controllers and each other.
Aircraft Capabilities and Limitations
B-52 Stratofortress
The B-52H Stratofortress is a long-range, subsonic strategic bomber with a wingspan of 185 feet and a cruising speed of over 500 mph. It is primarily used for high-altitude bombing missions but also conducts low-altitude training flights. Notably, B-52s are not equipped with TCAS, and often operate with limited or no ADS-B emissions during training to maintain operational security. This makes them difficult to detect by civilian aircraft systems.
Minot Air Force Base hosts 26 B-52s as part of the 5th Bomb Wing. These aircraft frequently perform pattern work and touch-and-go landings in the vicinity of Minot International Airport. The absence of real-time coordination with civilian controllers during these operations can lead to unexpected encounters, as was the case on July 18.
While the B-52’s radar cross-section and size make it visible on primary radar, the lack of transponder-based data means it does not appear on TCAS displays, leading to a reliance on visual detection and controller communication for separation.
Embraer E175
The Embraer E175 is a regional jet used extensively by Delta Connection and other carriers for short-haul routes. It is equipped with TCAS II and ADS-B systems, which provide situational awareness and collision avoidance capabilities. However, these systems depend on other aircraft broadcasting compatible signals.
In this incident, the E175’s systems did not detect the B-52, likely due to the bomber’s lack of a compatible transponder signal. This left the flight crew reliant on visual cues, which are less reliable during high-speed operations. The aircraft’s maneuverability allowed the pilot to perform a sharp turn, avoiding a collision, but the lack of automated warning systems underscores the vulnerability of current detection protocols.
Despite its advanced avionics, the E175’s safety systems were effectively blind to the presence of the B-52, highlighting the need for updated standards that account for military aircraft operating in civilian airspace.
Regulatory and Technological Implications
In recent years, the FAA has implemented several initiatives aimed at improving aviation safety, including the “Back to Basics” campaign, which led to a significant reduction in runway incursions. However, near mid-air collisions (NMACs) remain a concern, particularly in mixed-use airspace. According to FAA data, military-civilian interactions account for a notable portion of NMAC reports, with several incidents involving aircraft operating under different visibility and communication protocols.
The absence of TCAS and ADS-B on military aircraft like the B-52 complicates civilian efforts to maintain safe separation. While operational security is a valid concern, training flights over or near civilian airfields pose a unique risk that may warrant policy changes. One potential solution is the use of non-classified transponders during domestic training missions to ensure visibility to civilian systems.
Additionally, enhancing data-sharing capabilities between military and civilian radar systems could provide controllers with a more complete picture of airspace activity. Automated alerts for military aircraft entering civilian corridors, as suggested by aviation safety reporting systems, could further reduce the risk of conflict.
Conclusion
The near-collision between Delta Flight DL3788 and a B-52 bomber near Minot, North Dakota, serves as a stark reminder of the challenges inherent in shared airspace management. While the pilot’s quick thinking and skilled maneuvering prevented disaster, the systemic issues that allowed the incident to occur remain unresolved. The lack of radar integration, incompatible detection systems, and procedural ambiguities all contributed to the event.
Moving forward, aviation authorities must prioritize the integration of military and civilian systems, update regulatory frameworks, and invest in technologies that enhance situational awareness for all operators. As air traffic continues to grow and military operations evolve, proactive measures are essential to ensure that safety is maintained not by last-minute maneuvers, but by comprehensive planning and coordination.
FAQ
What caused the near-collision between the Delta jet and the B-52?
The near-collision was caused by a lack of real-time coordination between military and civilian air traffic controllers, combined with the B-52’s absence from the Delta jet’s detection systems.
Why didn’t the Delta jet’s TCAS detect the B-52?
The B-52 likely did not have an active transponder compatible with TCAS, making it invisible to the Delta aircraft’s collision avoidance system.
What changes are being proposed to prevent future incidents?
Proposals include enhancing radar data sharing between military and civilian controllers, mandating transponder use during military training flights, and improving communication protocols at joint-use airports.
Sources:
AviationA2Z,
FAA,
Air Force Magazine,
NTSB,
Embraer
Photo Credit: AirNavRadar
Regulations & Safety
Rio de Janeiro Mid-Air Helicopter Collision Kills Six
Two helicopters collided over Rio de Janeiro on June 14, 2026, killing six and triggering an EV battery fire. CENIPA is investigating.
This is a developing story. Information may change as official details are released.
This article summarizes reporting by CNN Brasil.
Six people sustained fatal injuries on June 14, 2026, following a mid-air collision between two helicopters over the West Zone of Rio de Janeiro, Brazil. The deceased include American entertainer Oliver Tree Nickel and five other occupants across both aircraft.
The accident involved a Bell 206B JetRanger III and an Airbus AS350 B2. Following the airborne collision, the wreckage descended into an electric vehicle parking lot, triggering a complex post-crash fire involving multiple lithium-ion vehicle batteries. The Brazilian Aeronautical Accidents Investigation and Prevention Center (CENIPA) has opened an investigation into the sequence of events.
Aircraft and flight details
According to the National Civil Aviation Agency (ANAC), both helicopters maintained regular registration status at the time of the accident. The Bell 206B JetRanger III, registered as PP-MAC, was operated by Turfik Comércio de Frutas Ltda and carried a single occupant. The Airbus AS350 B2, registered as PR-DJJ, carried five occupants.
The Military Fire Department of the State of Rio de Janeiro (CBMERJ) received the initial emergency call at 08:59 local time. The collision occurred over the Recreio dos Bandeirantes neighborhood, specifically near Avenida das Américas.
Ground impact and secondary fire hazards
The wreckage from the mid-air collision impacted a BYD car dealership lot. CNN Brasil reported that the impact and subsequent fuel ignition destroyed approximately 20 electric vehicles parked at the facility.
The presence of electric vehicles introduced severe secondary hazards for first responders. CBMERJ spokesperson Fábio Contreiras detailed the challenges faced by fire crews on the scene.
“The fire in lithium batteries causes very high energy. It is a much more aggressive fire than a common fire,” Contreiras stated.
Victim identification and background
The Civil Police of the State of Rio de Janeiro (PCERJ) officially confirmed the identities of the six victims. In addition to Oliver Tree Nickel, the deceased include Argentine content creator Gaspar Prim Díaz, Argentine video director Lucas Vignale, Brazilian music producer Lucas Brito Chaves, and pilots Alexandre Souza and Charles Marsillac.
Oliver Tree had recently performed in Buenos Aires, Argentina, on June 4, 2026, and in São Paulo, Brazil, on June 6, 2026, as part of an international tour.
Rio de Janeiro Mayor Eduardo Cavaliere addressed the loss of the flight crew in a public statement.
“I knew one of the pilots personally. They were 2 experienced pilots, with many flight hours, with a long career. It was a fatality, a tragedy,” Cavaliere said.
AirPro News analysis
While CENIPA will determine the factors leading to the mid-air collision, the ground phase of this accident highlights an emerging challenge for municipal emergency services. As electric aviation vehicle adoption increases, the probability of aviation accidents intersecting with high-density lithium-ion battery storage also rises. We anticipate that safety regulators and Aircraft Rescue and Firefighting (ARFF) organizations will need to update urban crash response protocols to account for the thermal runaway risks and specialized extinguishing requirements associated with large-scale EV battery fires.
Sources: CNN Brasil
Photo Credit: Ricardo Moraes – Reuters
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
-
Technology & Innovation6 days agoAirbus Vision Landing Application Enables AI Autoland
-
Defense & Military5 days agoBoeing Withdraws T-7A Red Hawk from Navy UJTS Competition
-
Regulations & Safety3 days agoMissouri Skydive Plane Crash Kills 12 at Butler Airport
-
Commercial Aviation5 days agoAirbus A350-1000ULR EASA Certification Campaign Begins
-
Regulations & Safety5 days agoTurkish Airlines 777-300ER Wing Strike at Antalya Airport