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.
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.
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.
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.”
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. 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.
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.
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.
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. Question: What object hit United Airlines Flight 1093? Question: Were there any injuries reported? Question: Did the cabin lose pressure during the incident?
NTSB Preliminary Report: United Airlines Flight 1093 Incident Analysis
Sequence of Events and Flight Operations
The Collision and Immediate Aftermath
Investigation Findings: Object Identification
Trajectory and Tracking Data
Structural Analysis and Safety Context
Windshield Integrity and Certification
Conclusion
FAQ
Answer: The NTSB identified the object as a lost weather balloon operated by WindBorne Systems.
Answer: The captain sustained minor injuries, including cuts and bruises, from glass debris. No passengers or other crew members were injured.
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
FAA Suspends Visual Separation Between Airplanes and Helicopters in Busy Airspace
FAA mandates radar separation for airplanes and helicopters in Class B, C, and TRSA airspace to improve safety after 2025 mid-air collision.
This article is based on an official press release from the Federal Aviation Administration.
The Federal Aviation Administration (FAA) and U.S. Transportation Secretary Sean P. Duffy have announced a sweeping new safety protocol aimed at preventing mid-air collisions between airplanes and helicopters. The new measure, issued as a general notice (GENOT), officially suspends the use of visual separation between these aircraft types in busy airspace sectors.
According to the FAA’s press release, air traffic controllers will now be required to use radar to actively manage and separate airplanes and helicopters at specific lateral or vertical distances. The rule applies to Class B and Class C airspace, as well as Terminal Radar Service Areas (TRSA), where helicopters frequently cross arrival and departure paths.
This regulatory shift follows a year-long review by the FAA’s safety team, which utilized artificial intelligence tools to analyze cross-traffic data and incident reports nationwide. The review was prompted by a tragic mid-air collision near Ronald Reagan Washington National Airport (DCA) in early 2025.
Historically, visual separation allowed air traffic controllers to advise pilots of nearby traffic, shifting the responsibility to the flight crews to remain visually clear of other aircraft. However, the FAA’s recent data analysis concluded that this “see and avoid” method is no longer a sufficient safety mitigation tool in high-traffic areas.
FAA Administrator Bryan Bedford emphasized the need for proactive risk mitigation in the agency’s official statement.
“Following the mid-air collision near Ronald Reagan Washington National Airport (DCA), we looked at similar operations across the national airspace. We identified an overreliance on pilot ‘see and avoid’ operations that contribute to safety events involving helicopters and airplanes,” Bedford said.
The agency highlighted two recent near-miss incidents that underscored the urgency of the new mandate. On February 27, 2026, American Airlines Flight 1657 on final approach to San Antonio International Airport was forced into a converging course with a police helicopter, which had to make an evasive left-hand turn. Just days later, on March 2, 2026, a Beechcraft 99 landing at Hollywood Burbank Airport experienced a similar conflict with a helicopter that required an evasive right-hand turn.
The suspension of visual separation is expected to have immediate operational impacts on both helicopter operators and commercial airlines. The FAA noted that helicopter pilots, who are accustomed to receiving immediate approval to transit through certain busy areas, may now face routing adjustments or delays while controllers establish safe radar separation. Furthermore, the new protocol includes provisions for urgent missions. When helicopter pilots conducting medical or law enforcement operations request clearance through heavy-traffic zones, commercial airline operations may experience disruptions to accommodate these priority flights.
U.S. Transportation Secretary Sean P. Duffy framed the changes as part of a broader, ongoing effort to reform airspace safety following the DCA tragedy a year ago.
“The tragedy over the Potomac one year ago revealed a startling truth: years of warning signs were missed, and the FAA needed dire reform,” Duffy stated in the release. “Using innovative data analysis, the safety team at the FAA has identified the need for enhanced protocols at all airports across the National Airspace System.”
We note that the FAA’s decision to suspend visual separation in Class B, Class C, and TRSA airspace represents a significant operational shift for air traffic control. By mandating radar separation for mixed airplane and helicopter traffic, the agency is prioritizing absolute spatial deconfliction over the efficiency previously afforded by visual flight rules in terminal areas. While this will undoubtedly enhance safety margins and reduce the risk of mid-air collisions, it is likely to increase the workload for air traffic controllers and introduce new complexities in managing arrival and departure flows at the nation’s busiest airports. The reliance on AI tools to evaluate these high-volume areas suggests a modernization of the FAA’s approach to airspace risk management, moving from reactive measures to data-driven, proactive policymaking.
Visual separation is an air traffic control procedure where controllers advise pilots of nearby aircraft and allow the pilots to maintain safe distances visually, rather than relying on standard radar separation distances.
According to the FAA, the suspension of visual separation between airplanes and helicopters applies to Class B and Class C airspace, as well as Terminal Radar Service Areas (TRSA).
Yes. The FAA has indicated that airline operations may face disruptions or delays when urgent medical or law enforcement helicopters require priority clearance through heavy-traffic areas under the new radar separation rules.
Sources: Federal Aviation Administration
Moving Away from “See and Avoid”
Operational Impacts and Priority Clearances
AirPro News analysis
Frequently Asked Questions
What is visual separation?
Where does the new FAA rule apply?
Will this affect commercial airline flights?
Photo Credit: FAA
Regulations & Safety
Virgin Australia Flight Emergency Due to Vape Battery Fire in Cabin
Virgin Australia flight VA328 made an emergency landing at Melbourne after a vape’s lithium-ion battery caught fire, with no injuries reported.
A Virgin Australia flight from Brisbane to Melbourne was forced to declare a mid-air emergency on Sunday, March 15, 2026, after a passenger’s vape device caught fire in the cabin. According to reporting by ABC News, the incident prompted an immediate and large-scale response on the ground.
“A Virgin Australia flight makes an emergency landing at Melbourne Airport after a vape caught fire onboard,” reported ABC News.
Flight VA328, operated by a Boeing 737-800, was on its descent when the lithium-ion battery inside the e-cigarette experienced a thermal runaway. The swift actions of the cabin crew, who utilized a fire-proof containment bag, prevented any injuries or structural damage to the aircraft.
The event highlights the ongoing and severe risks associated with lithium-ion batteries in aviation, reinforcing why global aviation regulators mandate that such devices remain strictly in the passenger cabin rather than the cargo hold.
As the Boeing 737-800 (registration VH-YFU) neared Melbourne, flight attendants noticed smoke, a hissing noise, and small flames coming from a passenger’s vape. According to incident reports, the crew immediately followed standard operating procedures for onboard battery fires.
They successfully isolated the burning device and secured it inside a specialized fire-proof containment bag. To provide the cabin crew with the necessary time to manage the hazard safely, the flight deck executed a missed approach before continuing their final descent.
During the incident, the pilots transmitted a “PAN” call to air traffic control. This internationally recognized urgency signal indicates a serious situation requiring priority handling, though it falls short of a “Mayday” life-threatening emergency. The transmission ensured that ground control was fully aware of the unfolding situation and could prepare accordingly.
Upon receiving the PAN call, air traffic controllers at Melbourne Airport placed several other arriving flights into holding patterns. This air traffic management decision ensured Flight VA328 had immediate and priority clearance to land without delay. Simultaneously, a massive precautionary response was activated on the ground. More than 17 emergency vehicles, including fire engines, ambulances, and airport response units, were deployed and positioned along the runway on standby.
The aircraft touched down safely between 4:20 p.m. and 4:45 p.m. AEDT. Aviation Rescue Firefighters met the plane on the tarmac, escorted it to the gate, and boarded to safely remove the damaged e-cigarette. Passengers disembarked normally without requiring any medical assistance.
Vape devices are powered by lithium-ion batteries, which can enter a state of “thermal runaway” if damaged, short-circuited, or faulty. This uncontrollable chain reaction produces intense heat, toxic smoke, and flames.
Aviation safety regulators worldwide require that vapes and power banks be carried exclusively in the passenger cabin as carry-on baggage. This rule exists so that if a fire occurs, the crew can detect and extinguish it immediately, a scenario that could be catastrophic if it occurred undetected in the cargo hold.
Virgin Australia strictly prohibits the use or charging of vapes and power banks during flights. Furthermore, vaping on an aircraft is a federal offense under Australian law. Accidental fires caused by negligence, such as the improper packing of a battery, can trigger investigations by the Civil Aviation Safety Authority (CASA), potentially resulting in substantial fines for the offending passenger.
We observe that this incident is part of a growing industry concern regarding personal electronic devices. In July 2025, Virgin Australia experienced a similar scare when a passenger’s power bank ignited in an overhead locker on a flight from Sydney to Hobart, prompting major Australian carriers to introduce stricter guidelines.
The successful resolution of Flight VA328 demonstrates that current aviation safety protocols are highly effective when executed properly. The mandate to keep battery-operated devices in the cabin, combined with the availability of fire-proof containment bags, worked exactly as intended to avert a potential disaster. However, it also underscores the critical need for continued passenger education regarding the safe transport of lithium-ion batteries, as many travelers remain unaware of the severe risks these everyday items pose at altitude.
Vapes and power banks must be kept in carry-on baggage so that if a battery malfunctions and catches fire, cabin crew can immediately detect and extinguish it. If these devices were placed in checked luggage, a fire in the cargo hold could go unnoticed until it becomes uncontrollable. No injuries were reported among the passengers or crew. The cabin crew successfully contained the fire, and the aircraft sustained no structural damage.
No. Virgin Australia, along with all other major airlines, strictly prohibits the use or charging of vapes during flights. Vaping on an aircraft is a federal offense in Australia and can lead to severe penalties.
The In-Flight Emergency and Crew Response
Smoke in the Cabin
Declaring a PAN Call
Ground Coordination and Safe Landing
Priority Clearance at Melbourne Airport
Post-Landing Procedures
Aviation Rules and Lithium-Ion Risks
The Danger of Thermal Runaway
Airline Policies and Legal Implications
AirPro News analysis
Frequently Asked Questions
Why are vapes allowed on planes if they are a fire risk?
Was anyone injured on Virgin Australia Flight VA328?
Can you use a vape on a commercial flight?
Sources
Photo Credit: Virgin Australia
Regulations & Safety
NTSB Preliminary Report on 2026 Deerfield Cessna Crash
The NTSB preliminary report details a 1976 Cessna crash near Deerfield, Illinois, highlighting severe weather and erratic flight path factors.
This article is based on an official preliminary report from the National Transportation Safety Board (NTSB), supplemented by third-party reporting and aviation data.
On Wednesday, March 4, 2026, a 1976 Cessna T210M Turbo Centurion crashed into a residential neighborhood in an unincorporated area of Lake County near Deerfield, Illinois. The sole occupant and pilot, 75-year-old Chester Wojnicki, was killed upon impact. Miraculously, despite the aircraft striking a densely populated townhome complex, there were no injuries reported on the ground.
The National Transportation Safety Board (NTSB) has released its preliminary report regarding the incident. The ongoing investigation is currently focusing on severe weather conditions, erratic flight tracking data, and the potential for spatial disorientation during the aircraft’s final approach to Chicago Executive Airport.
We are reviewing the NTSB’s initial findings, alongside flight tracking data and local emergency response reports, to understand the sequence of events that led to this tragic aviation accident.
According to the NTSB preliminary data and flight tracking information from Global ADS-B Exchange, the flight departed from Dane County Regional Airport in Madison, Wisconsin, at 8:49 p.m. CST. The intended destination was Chicago Executive Airport in Wheeling, Illinois.
Weather conditions were rapidly deteriorating as the aircraft neared its destination. METAR data recorded heavy fog, low clouds, and poor visibility in the area. A weather report issued just 10 minutes after the 9:45 p.m. crash indicated a vertical visibility of only 200 feet and a ground visibility of half a statute mile.
The NTSB’s preliminary findings highlight an erratic flight path during the pilot’s attempted GPS approach to Runway 16. ADS-B data shows the aircraft was consistently flying below the approach’s minimum required altitudes, beginning from the initial approach fix.
Furthermore, the aircraft deviated left and right of the designated course prior to impacting the terrain. Air traffic control (ATC) audio suggests the pilot may have experienced confusion regarding his altitude and proximity to the ground in the final minutes of the flight. The control tower lost contact with the aircraft shortly before the crash, and no distress signals or Mayday calls were reported. The aircraft impacted the ground 2.6 nautical miles northwest of the destination runway, on the 800 block of Swallow Street. Witnesses reported hearing the plane strike the tops of trees before crashing into the backyard of the townhome complex.
During the crash, the plane clipped a roofline and severed two Nicor gas meters, embedding its propeller into the side of a home. First responders from the Lincolnshire-Riverwoods Fire Protection District and local utility crews quickly secured the area, containing a minor gas leak and preventing any post-crash fire. All townhomes remained habitable following the incident.
The Lake County Coroner’s Office confirmed that the pilot, Chester Wojnicki of Mount Prospect, Illinois, died from blunt force injuries sustained in the crash. Wojnicki was a highly experienced aviator and served as the president of the American Polish Aero Club Chicago (APA).
The local aviation community remembers him as a generous and mechanically skilled individual who owned a local electrical and heating repair business. Neighbors in the townhome complex expressed profound relief that the crash did not result in a larger catastrophe. Speaking to CBS News, one local resident highlighted the miraculous outcome for the neighborhood:
“For 50 years, planes have been flying over this area… it’s very, very fortunate that the lord was watching over us last night.”
While the NTSB preliminary report provides raw data and factual observations from the crash site, a final probable cause report will likely take 12 to 24 months to be published.
Based on the preliminary data, aviation safety experts, including analysts at the AOPA Air Safety Institute, suggest that spatial disorientation is a highly probable factor in this accident. Spatial disorientation occurs when a pilot loses their sense of direction, altitude, or airspeed. This physiological condition is frequently exacerbated by night flying in heavy fog and zero-visibility environments.
The combination of a 200-foot ceiling, a high-workload instrument approach, and potential confusion during ATC advisories creates a scenario where even veteran pilots can become disoriented. The absence of a Mayday call further supports the theory that the pilot may not have realized the severity of the altitude deviation until the final seconds of the flight. We will continue to monitor the NTSB’s ongoing investigation for further official updates and safety recommendations.
When did the Deerfield plane crash occur? What type of aircraft was involved? Were there any injuries on the ground?
Flight Details and Deteriorating Weather
Erratic Approach and ATC Communication
Ground Impact and Community Response
Remembering the Pilot
Investigating the Probable Cause
AirPro News analysis
Frequently Asked Questions
The crash occurred on Wednesday, March 4, 2026, at approximately 9:45 p.m. CST.
The aircraft was a single-engine 1976 Cessna T210M Turbo Centurion.
No. Despite crashing into a residential townhome complex and severing two gas meters, there were no ground injuries and no post-crash fires.
Sources
Photo Credit: Paul Valade – Daily Herald
-
Defense & Military4 days agoUSAF Awards Boeing $2.33B Contract for E-7A Wedgetail Development
-
MRO & Manufacturing5 days agoÖAMTC and Airbus Sign Long-Term Contract for H135 H140 H145 Helicopters
-
Airlines Strategy5 days agoSpirit Airlines Files Restructuring Plan to Exit Chapter 11 by Summer 2026
-
Aircraft Orders & Deliveries6 days agoDe Havilland Delivers First Refurbished Dash 8-400 to ANA Group
-
Defense & Military4 days agoAirbus and Kratos to Deliver Uncrewed Combat Aircraft to Germany by 2029