More news on this day
Flights into and out of San Diego International Airport faced hours of disruption on Friday, September 4, after drone activity near the airfield and a high-altitude weather balloon prompted a ground stop and widespread delays at the height of Labor Day weekend travel.
Get the latest news straight to your inbox!

Ground stop halts operations at busy holiday peak
Publicly available flight-tracking data and passenger accounts indicate that departures and arrivals at San Diego International Airport were halted for more than an hour on Friday afternoon following reports of drones operating close to the airfield. The disruption unfolded as the airport was handling heavy Labor Day weekend traffic, amplifying the impact on already congested schedules.
Flight tracking platforms showed large numbers of aircraft holding in stacks offshore or diverting to other airports while the stoppage was in effect, with some passengers reporting holds of 30 minutes or longer before their aircraft were cleared to approach San Diego. Others described extended gate holds and deplaning after duty-time limits were reached for flight crews waiting out the airspace restrictions.
According to online aviation forums and delay dashboards, San Diego ranked among the most affected airports in the United States on Friday, with average arrival delays climbing well beyond an hour for flights from across the continental United States and Canada once operations resumed.
The Federal Aviation Administration’s public traffic management advisories for San Diego showed an ongoing ground delay program following the initial ground stop, reflecting the need to meter inbound traffic while the airport worked through a growing backlog of flights.
Confusion over high-altitude weather balloon
Complicating the situation, travelers and local residents also reported seeing a high-altitude balloon over the region around the same time as the drone-related stoppage. Initial social media posts suggested the balloon might be responsible for the halt in flights, but subsequent discussion among aviation enthusiasts pointed to the devices as separate events.
Comments shared by local observers indicated that the balloon was operating above 50,000 feet with a transponder and an approved flight plan, characteristics more typical of a research or weather platform than a rogue object. By contrast, the drones reported in the San Diego flight path were described as low-altitude devices operating much closer to airport infrastructure and traffic patterns.
Later local media coverage referenced both the drones and the balloon as being under review in connection with the day’s disruptions, but the emerging consensus in public reporting has been that the balloon’s high operating altitude placed it well above normal arrival and departure corridors at San Diego International Airport.
The parallel sightings nevertheless contributed to confusion among passengers following events from terminals and smartphones, underscoring how quickly unverified information can circulate when flight operations suddenly pause.
Reports describe drones near control tower and departure paths
Multiple passenger accounts posted to airline and regional discussion boards described at least one drone hovering near the airport’s control tower, with some users relaying pilot announcements that a drone had been observed roughly 20 to 25 feet above the facility. Others referenced a second drone reported by a departing crew, suggesting there may have been more than one device operating near the airport’s critical flight paths.
Posts from travelers arriving and departing San Diego on Friday afternoon pointed to a complete stop in takeoffs, followed by an extended period of limited operations as air traffic control worked to re-sequence backed-up flights. Some flights were reportedly diverted to larger hubs such as Los Angeles while the situation unfolded, with connections and evening departures affected hours after the initial reports of drone activity.
The scale of the disruption highlighted the vulnerability of a single-runway airport like San Diego to even brief interruptions. With all commercial traffic funneled through one strip and steep approaches constrained by nearby terrain and urban development, any extended pause in movements can quickly produce long lines of inbound and outbound aircraft.
Historical operational guidance and irregular-operations plans for San Diego emphasize the need to manage tarmac delays and passenger surges during unexpected events, and Friday’s drone-related stoppage offered a real-time stress test of those procedures at one of the region’s most important transportation hubs.
Drone rules under renewed scrutiny in the San Diego region
The incident is already feeding into a wider public conversation about drone safety around critical infrastructure in Southern California. Recent advisories from federal and local agencies have repeatedly highlighted strict no-fly zones for unmanned aircraft near airports, stadiums and large public events in the San Diego area, noting that violations can trigger law enforcement investigations and significant penalties.
Local emergency planning documents and county regulations also set additional limits on recreational and commercial drone use near sensitive operations, including temporary airspace restrictions during emergencies. These frameworks are designed to keep low-flying devices away from flight paths and emergency aircraft, and to give authorities options to restrict airspace swiftly when hazards are detected.
Despite those rules, Friday’s disruptions show how relatively small unmanned devices can still intrude into critical airspace in ways that force conservative responses from air traffic managers. Even when no collision occurs, standard practice is to suspend operations until conflicting traffic is no longer present, which in turn can strand thousands of travelers and ripple across the wider network.
The scale of the delays following the San Diego ground stop is likely to intensify debate over enforcement tools, detection technology and possible geofencing requirements that could further reduce the risk of unauthorized drone flights near busy commercial airports.
Passengers face missed connections and extended travel days
As operations gradually resumed Friday evening, the focus for many travelers shifted from the cause of the disruption to its practical consequences. Online posts from those affected described missed connections, late-night arrivals and rebooked itineraries, with some travelers stranded at outstations after their crews timed out waiting for clearance into San Diego.
Data from airline status pages and tracking platforms showed delays stretching from relatively short holds to extreme cases lasting several hours, reflecting a typical pattern after a sudden shutdown at a major airport. Once operations restart, controllers must sequence both delayed flights and newly scheduled services, often leading to rolling disruptions well beyond the initial event window.
San Diego’s role as a gateway to popular West Coast and Hawaiian destinations meant that the timing of the ground stop on the eve of a holiday weekend was particularly challenging. Travelers bound for onward connections or cruises reported having to scramble for alternative plans as arrival times slipped later into the night.
Airport operations guidance for irregular events emphasizes communication between airlines and passengers about evolving delay forecasts, and public-facing advisories encouraged travelers to monitor carrier apps and websites closely as the San Diego system worked through the backlog.
https://www.readers.id/en/san-diego-airport-flight-delays-drone
https://www.fly.faa.gov/fly/flyfaa/flyfaaindex?ARPT=SAN&p=1
https://www.san.org/airport-authority-guidelines-operations/
https://www.reddit.com/r/sandiego/comments/1w7i418/san_ground_stop_for_drone_activity/