Regulations & Safety
NTSB Reports Weather Balloon Collision with United Airlines Flight 1093
NTSB identifies a WindBorne Systems weather balloon as the object that struck United Airlines Flight 1093, ensuring a safe emergency landing.
NTSB Preliminary Report: United Airlines Flight 1093 Incident Analysis
On November 20, 2025, the National Transportation Safety Board (NTSB) released its preliminary report regarding a significant mid-air incident that occurred roughly one month prior. The investigation, filed under ID DCA26LA012, addresses the events of October 16, 2025, when a United Airlines Boeing 737-8 (MAX 8) collided with an unidentified object while cruising at high altitude. For weeks, industry observers and the public speculated on the nature of the object, with theories ranging from space debris to meteors. The release of this report provides the first official clarity on the matter.
The incident involved United Airlines Flight 1093, which was operating a scheduled domestic passenger flight from Denver International Airport (DEN) to Los Angeles International Airport (LAX). While flying over Utah, the aircraft suffered substantial damage to the flight deck windshield, forcing an emergency diversion. The release of the preliminary report marks a critical step in understanding how high-altitude airspace is managed and the potential risks posed by unmanned free balloons.
We have analyzed the NTSB’s findings to break down the sequence of events, the identification of the object involved, and the structural performance of the aircraft during the emergency. This report relies strictly on the factual data provided by the NTSB and the investigative research desk to offer a comprehensive overview of the event.
Sequence of Events and Flight Operations
On the morning of October 16, 2025, United Airlines Flight 1093 departed Denver with 134 passengers and 6 crew members on board. The flight proceeded normally during its initial climb and established a cruise altitude of approximately 36,000 feet (FL360). At this altitude, the aircraft was traveling at a groundspeed of roughly 395 knots. The skies near Moab, Utah, appeared clear, and operations were standard until approximately 06:44 MDT.
The Collision and Immediate Aftermath
According to the preliminary report, the situation changed instantly when the captain observed an object positioned immediately ahead of the aircraft. Due to the high closure rate typical of jet travel at cruising speeds, there was little time to react. Moments later, the object struck the first officer’s forward windshield. The force of the impact was significant enough to shatter the outer pane of the multilayered window structure.
The collision resulted in glass debris entering the cockpit environment. The captain sustained minor injuries, specifically cuts and bruises to his right arm, caused by the fragmented glass. Despite the breach of the outer pane, the aircraft’s pressurization system remained stable, a testament to the fail-safe design of modern aircraft windshields. Following the impact, the first officer assumed control of the aircraft, as the crew initiated emergency protocols.
The flight crew declared an emergency and executed the necessary checklists to ensure the safety of the passengers and the aircraft. They made the decision to divert to Salt Lake City International Airport (SLC). The descent and approach were conducted without further incident, and the aircraft landed safely on runway 16L. Following the landing, the plane was able to taxi to the gate under its own power, avoiding the need for a tow and allowing passengers to deplane safely.
“The object has been identified as a lost weather balloon operated by WindBorne Systems.”
Investigation Findings: Object Identification
The primary focus of the NTSB investigation was to positively identify the object that struck Flight 1093. Initial public speculation had suggested the possibility of space debris or a natural phenomenon, given the altitude of 36,000 feet. However, forensic analysis and flight tracking data have ruled out these theories. Investigators successfully traced the object to a Global Sounding Balloon operated by WindBorne Systems.
Trajectory and Tracking Data
The investigation revealed that the balloon in question had been launched the previous day from Spokane, Washington. WindBorne Systems, the operator, reported that they had lost communication with one of their balloons in the exact vicinity and timeframe of the collision. The last data transmission received from the balloon indicated it was at an altitude of 35,936 feet as it traversed Utah airspace.
The geometry of the collision highlights the challenges of detecting small, unmanned objects at high speeds. Flight data indicates that the United Airlines Boeing 737-8 was traveling southwest. Conversely, the balloon’s last reported track suggests it was drifting in a direction nearly opposite to the aircraft’s flight path. This head-on or near-head-on trajectory created a high-speed closure rate, intensifying the force of the impact upon collision.
WindBorne Systems describes their equipment as lightweight, unmanned free balloons. These devices typically consist of a thin-film envelope, avionics for data collection, and a low-density ballast system. While they are engineered to minimize impact forces, essentially designed to be fragile, the physics of a collision at jet cruise speeds can still result in significant kinetic energy transfer, as evidenced by the damage to the aircraft.
Structural Analysis and Safety Context
A critical component of the NTSB’s preliminary report focuses on the damage sustained by the Boeing 737-8 and the engineering standards that prevented a more catastrophic outcome. The windshield of a 737-8 is a complex, multilayered structure designed specifically to maintain cabin pressure and structural integrity even in the event that an outer pane fails.
Windshield Integrity and Certification
The aircraft’s windshield is certified to withstand significant impacts, including a four-pound bird strike. In this incident, the outer pane shattered, but the inner layers held, preventing rapid decompression. The damaged windshield has since been removed from the airframe and transported to the NTSB Materials Laboratory for a detailed microscopic examination. This analysis will help engineers understand the precise mechanics of the failure and verify that the materials performed as intended under the stress of the collision.
This incident has prompted a review of safety protocols regarding high-altitude balloon operations. While the investigation is ongoing, reports indicate that United Airlines and the Federal Aviation Administration (FAA) are reviewing the event to determine if operational changes are required. There are reports that immediate adjustments were made to minimize time spent at specific altitudes in affected areas, though these operational changes will likely be refined as the final report is completed.
Conclusion
The NTSB preliminary report on United Airlines Flight 1093 provides a factual resolution to the mystery of the October 16 incident. By identifying the object as a WindBorne Systems weather balloon, the investigation shifts focus from speculation to the practical management of shared airspace. The successful diversion and safe landing underscore the resilience of modern aircraft design and the professionalism of the flight crew under pressure.
As the investigation continues, the NTSB will analyze data from the cockpit voice recorder (CVR) and flight data recorder (FDR). A final report, which will include the probable cause and official safety recommendations, is expected to take between 12 and 24 months to complete. We will continue to monitor these developments as they provide vital insights for future aviation safety standards.
FAQ
Question: What object hit United Airlines Flight 1093?
Answer: The NTSB identified the object as a lost weather balloon operated by WindBorne Systems.
Question: Were there any injuries reported?
Answer: The captain sustained minor injuries, including cuts and bruises, from glass debris. No passengers or other crew members were injured.
Question: Did the cabin lose pressure during the incident?
Answer: No. Although the outer pane of the windshield shattered, the inner layers remained intact, and cabin pressurization remained stable throughout the diversion.
Sources
Photo Credit: NTSB
Regulations & Safety
NTSB: Thermal Plugs Caused AA Flight 3023 Tire Failure
NTSB determines melted thermal relief plugs caused tire failure on American Airlines 737-8 at Denver, triggering emergency evacuation.
The National Transportation Safety Board (NTSB) has determined that melted thermal relief plugs caused the left main landing gear tires to fail on an American Airlines Boeing 737-8 during a July 2025 takeoff roll at Denver International Airport (DEN), prompting a high-speed rejected takeoff and emergency evacuation.
The final aviation investigation report, published on August 26, 2026, officially closes the inquiry into American Airlines Flight 3023. The document details the mechanical sequence that led to the tire failure while highlighting significant passenger noncompliance during the subsequent evacuation, as travelers ignored crew commands and retrieved carry-on baggage.
Mechanical sequence and rejected takeoff
The incident occurred on July 26, 2025, involving a Boeing 737-8, registration N306SW, equipped with CFM International LEAP-1B28 engines. According to the NTSB, the flight experienced an approximate 25-minute delay while awaiting departure at runway 34L.
During the subsequent takeoff roll, as the aircraft reached an indicated airspeed between 90 and 100 knots, the captain reported hearing a loud pop accompanied by a noticeable bump. The flight crew initiated a rejected takeoff at speeds above 80 knots.
The NTSB determined the probable cause of the incident was the melting of thermal relief plugs in the left main landing gear. This melting released tire pressure and caused the tires and wheels to fail during the takeoff roll. The agency noted that this failure resulted in abnormal airplane handling characteristics, which prompted the flight crew to reject the takeoff. Debris from the fractured wheels caused minor damage to the aircraft, including a three-inch dent on the lower skin of the left wing.
Emergency evacuation and passenger behavior
Following the rejected takeoff, the flight crew initially instructed the cabin to remain seated. Between 30 and 45 seconds later, after identifying smoke and fire originating from the left main landing gear, the crew ordered an emergency evacuation.
The aircraft carried 175 occupants, comprising 169 passengers and six crew members. The NTSB final report confirms that zero injuries occurred during the event. This official casualty figure supersedes preliminary media reports from July 2025 that had indicated minor injuries and hospital evaluations.
The investigation report draws specific attention to passenger behavior during the emergency egress. The NTSB stated that the cabin crew described the evacuation as rapid but hindered by significant passenger confusion and noncompliance. Despite flight attendants repeatedly commanding passengers to leave their belongings behind, multiple individuals retrieved their carry-on baggage. The NTSB concluded that this noncompliance directly slowed the flow of egress from the aircraft.
AirPro News analysis
The NTSB findings regarding American Airlines Flight 3023 add to a well-documented and growing safety concern within the commercial aviation sector. Passenger retrieval of carry-on baggage during emergency evacuations is a recurring issue that compromises the 90-second evacuation standard mandated by the Federal Aviation Administration (FAA).
When passengers stop to open overhead bins and carry luggage down escape slides, they not only slow the egress rate for those behind them but also introduce the risk of puncturing the evacuation slides or injuring fellow passengers. We continue to see official accident reports cite passenger noncompliance as a negative factor in evacuation efficiency. This recurring behavioral pattern has prompted safety advocates and lawmakers to question whether current FAA evacuation certification tests, which rely on compliant participants, accurately reflect real-world human behavior during an emergency.
Sources: National Transportation Safety Board
Photo Credit: National Transportation Safety Board
Regulations & Safety
Marine One Loss of Separation at DCA: NTSB Preliminary Report
NTSB cites radio line-of-sight failure after Marine One and Envoy Air E-170 came within 0.82 NM at Reagan National.
This is a developing story. Information may change as official details are released.
This is original reporting and analysis by AirPro News.
A loss of separation occurred on August 4, 2026, between a Sikorsky VH-3D operating as Marine One and an Envoy Air Embraer E-170 departing Ronald Reagan Washington National Airport (DCA). The incident took place approximately two miles north of the airport at 14:34 EDT and prompted an immediate Federal Aviation Administration (FAA) relocation of radio equipment after investigators identified a communication failure.
According to a preliminary report released on August 27, 2026, by the National Transportation Safety Board (NTSB), air traffic controllers at DCA did not receive a required three-minute pre-departure warning from the helicopter. The event triggered a review of strict Safety protocols implemented following a fatal midair collision in the same airspace in January 2025.
Incident timeline and separation data
The loss of separation occurred when Marine One departed The Ellipse simultaneously with Envoy Air flight 3742 departing runway 1 at DCA. Preliminary FAA estimates indicate the aircraft came within 0.82 nautical miles (NM) laterally and 700 feet vertically. The NTSB is currently analyzing surveillance data to establish the exact closest point of approach.
President Donald Trump was on board the Sikorsky VH-3D at the time of the incident. In a statement provided to CBS News, White House spokesman Kush Desai confirmed the President was never in danger.
Marine One flights are piloted by the finest aviators in the world, and the White House maintains the utmost confidence in these patriots and other security officials who are responsible for ensuring the President’s safety.
No injuries were reported among the occupants of either aircraft, and both flights continued to their respective destinations without further incident.
Communication failure and FAA response
The NTSB preliminary report points to inadequate radio line-of-sight coverage between The Ellipse and the DCA tower as the primary factor in the missed pre-departure warning. A DCA tower controller reported that the transmission attempt from the helicopter was “broken and unreadable,” according to CBS News.
Following the August 4 incident, FAA technicians evaluated the infrastructure and confirmed the line-of-sight deficiency. To resolve the issue, the agency relocated the helicopter-control radio equipment to the top of the DCA control tower. Subsequent communication checks were successful.
CBS News also reported that recent construction at the White House may have contributed to the radio line-of-sight degradation, though the NTSB has not yet issued a final determination on the cause.
Regulatory context and prior airspace changes
The airspace surrounding DCA operates under highly specific procedural rules designed to deconflict fixed-wing airline traffic from frequent VIP helicopter movements. These procedures were significantly tightened following a fatal midair collision on January 29, 2025, involving an airliner and an Army Black Hawk helicopter near the airport.
Following the 2025 accident, regulators instituted a requirement for a ground stop at DCA anytime a Helicopters passes on a conflicting route. The failure of the three-minute warning on August 4 prevented controllers from initiating this required ground stop for the Envoy Air departure.
Air traffic controllers and Marine One pilots had previously met on July 28, 2026, exactly one week prior to the incident, to discuss ongoing communication challenges in the sector.
AirPro News analysis
The August 4 loss of separation highlights the fragility of procedural deconfliction in the Washington, D.C. airspace. While the FAA characterized the event as a momentary loss of separation, the failure of a critical communication link reveals a single point of failure in the safety protocols established after the 2025 collision. We note that the rapid relocation of the radio equipment by the FAA demonstrates an acknowledgment of the infrastructure gap. As the NTSB continues its Investigation, we will monitor the docket for potential systemic recommendations regarding how VIP helicopter movements integrate with high-volume Commercial-Aircraft traffic at DCA, particularly concerning redundant communication systems.
Sources: National Transportation Safety Board
Photo Credit: National Transportation Safety Board
Regulations & Safety
FAA Moves to Fire Two LaGuardia Controllers After Fatal Collision
FAA initiates termination proceedings against two LaGuardia controllers for early shift departures on the night of the March 22, 2026 runway collision.
This is a developing story. Information may change as official details are released.
This article summarizes reporting by Reuters by David Shepardson and Doyinsola Oladipo.
The FAA has initiated termination proceedings against two air traffic controllers accused of leaving their shifts early on the night of a fatal runway collision at LaGuardia Airport (LGA) in March 2026. The agency is classifying the unauthorized early departures as timecard fraud amid a broader national crackdown on the practice.
The disciplinary action follows the March 22, 2026, accident in which Air Canada Express Flight 8646, operated by Jazz Aviation LP, collided with an aircraft rescue firefighting (ARFF) vehicle while landing on Runway 4. According to Reuters, the two controllers allegedly departed the facility approximately one hour before their scheduled shifts ended, a practice colloquially known as an “early shove.”
Disciplinary actions and union response
The FAA stated its commitment to holding employees accountable, emphasizing that it will not compromise the safety or efficiency of the national airspace system. U.S. Secretary of Transportation Sean Duffy condemned the practice, stating that while most controllers complete their full shifts, the department will not tolerate fraud from individuals who unfairly burden their colleagues and impact the airspace.
The National Air Traffic Controllers Association (NATCA) confirmed it is actively discussing the allegations with FAA leadership. The union indicated that these internal discussions are the appropriate forum for addressing the matter. Reuters reports that the FAA is currently conducting a nationwide enforcement effort targeting employees who leave on break at the end of their shifts and fail to return.
The March 22 collision and investigation
The NTSB continues to investigate the March 22 collision under investigation ID DCA26MA161. The official cause of the accident remains undetermined. The aircraft involved was an MHI RJ Aviation CRJ-900, and the ground equipment was an Oshkosh Striker 1500 ARFF vehicle.
Official NTSB figures confirm that 76 people were on board the aircraft, including 72 passengers, two flight attendants, and two pilots. The captain and first officer sustained fatal injuries. Thirty-nine individuals were transported to local hospitals, with six reported to have serious injuries.
It remains unverified whether the controllers’ early departure directly influenced the events leading to the collision. Speaking in March 2026, NTSB Chair Jennifer Homendy noted that operating with two controllers in the tower cab during a midnight shift is common practice across the national airspace system, suggesting the facility may have been operating at standard staffing levels at the time of the accident.
Regulatory response to surface safety
Following the LaGuardia accident, the FAA accelerated initiatives to improve surface visibility at airports. On May 13, 2026, the agency announced a $16.5 million investment to equip all airport vehicles with transponders.
These vehicle movement area transponders (VMATs) are designed to provide ATC with better situational awareness of ground equipment operating on runways and taxiways.
AirPro News analysis
We note that the FAA’s decision to pursue termination for timecard fraud rather than operational errors highlights a strict administrative approach to facility management. By focusing on the unauthorized absence, the agency addresses the “early shove” culture directly without preempting the NTSB’s ongoing safety investigation into the collision’s root causes. The distinction between administrative violations and operational fault will likely remain a focal point as NATCA engages with FAA leadership.
Photo Credit: Mike Segar – Reuters
-
Technology & Innovation7 days agoSkyband Systems M100 LRU Validates GNSS Jamming Protection
-
MRO & Manufacturing6 days agoBoeing SPEEA Engineers Reject Contract, Authorize Strike
-
Military Technology6 days agoSaab Unveils A3-001 Supersonic Stealth Drone Concept
-
Business Aviation6 days agoFTAI Aviation Closes $2B Warehouse Financing for 2026 SPV
-
Business Aviation6 days agoSyberJet SJ30-2 Sets Transcontinental Speed Record