United Walks Back San Diego “Drone Strike” After Boeing 737 Inspection Shows No Damage

A United Airlines Boeing 737-800 on final approach to San Diego International Airport reported hitting a drone at roughly 3,000 feet on the morning of April 29, 2026. Hours later, that story had quietly fallen apart.

United Flight 1980, a Boeing 737-800 carrying 48 passengers and six crew members from San Francisco, landed safely just before 8:30 a.m. local time. Maintenance crews found no damage. The Federal Aviation Administration’s own statement said the pilot believed he had seen a drone 1,000 feet below the aircraft, and that air traffic control alerted other inbound flights but received no additional sightings. The FBI’s San Diego field office said it sees no public safety concern.

By Wednesday afternoon, United had revised its initial statement, deleting the word “strike” and saying there was “no indication that the aircraft struck the drone or vice-versa.” The pilot’s airborne description of the object was three words: red, shiny, small. That is most of what is publicly confirmed.

The Audio That Drove the Headlines

The audio recording, captured by the ATC App and widely shared on X, is what put the story everywhere. “We hit a drone. At around probably at around 3000 ft, about,” the pilot tells the ground controller. The dispatcher asks for size, engine count, style. “It was so small. I couldn’t tell. It was red. It was shiny.” That is the entire physical description.

The audio drove the tabloid headlines. The Mirror US ran with “Panic as United Airlines flight strikes drone 3,000 feet over San Diego.” GB News, Hindustan Times, the New York Post and dozens of others followed with similar framing. None of those headlines used the word “possible,” and none reflected the FAA’s narrower account.

United Edited Its Statement Within Hours

The first United statement to NBC 7 San Diego said Flight 1980 “reported a possible drone strike just prior to arriving in San Diego” and that maintenance found no damage. Hours later, United issued a revised statement to the same outlet that deleted the word “strike” and added: “There’s no indication that the aircraft struck the drone or vice-versa.”

The FAA’s own description was tighter still. Spokesman Ian Gregor said the crew “told air traffic control they believed they saw a drone 1,000 feet below them.” Air traffic control alerted other pilots in the area. No one else reported the object.

The aircraft’s tail number is N14219. After landing, the airframe was cleared for service and continued its next scheduled leg to Houston. Airlines do not put aircraft straight back into rotation after a confirmed midair impact at 3,000 feet. The FBI’s San Diego Field Office said in a statement to FOX 5/KUSI that it is “aware of the reports” and that “there are no safety concerns for the public.”

Brendan Schulman’s One-Tweet Reality Check

Brendan Schulman, formerly DJI‘s VP of Policy and now VP of Policy and Government Relations at Boston Dynamics, posted a short reaction on X within hours. Schulman, who is one of the most consistently sober voices on aviation-drone risk, wrote: “Conclusions should await a full investigation, but in the past, reports like these have always turned out to not involve a drone. Balloons are red and shiny, too.”

Schulman is one of the most respected voices in U.S. drone policy. He led DJI’s policy and legal affairs shop for nearly a decade, shaped the industry’s response to Remote ID rulemaking, and has been a steady, careful analyst of drone safety reporting for as long as the modern industry has existed. When he says reports like this have “always” turned out not to be drones, he is speaking from years of working these investigations from the inside.

A Recurring Pattern of “Drones” That Weren’t Drones

The misidentification pattern is now extensive. In December 2024, LaGuardia briefly went into a drone panic over what local pilots immediately recognized as routine landing-queue traffic. The same week, the New Jersey drone sightings generated more than 5,000 reports to federal tip lines. The FBI, DHS, FAA and DOD eventually attributed the bulk of those reports to manned aircraft, planets and stars. Even Jupiter, low and bright that December, got reported as a hovering drone.

In Europe last fall, the pattern repeated. Amsterdam Schiphol shut down for 45 minutes in September 2025 after one pilot reported a drone within 50 meters of an inbound aircraft. Two other pilots described the same object as a balloon. Munich shut down for hours in October on what Germany has so far refused to call confirmed drone activity. A medical helicopter in New Jersey diverted from a transport mission because of “three drones” that TSA documents later identified as three commercial aircraft on approach to Solberg Airport.

Birds, balloons, plastic bags, training aircraft, planets and bright stars get called drones routinely. Trained pilots in cockpits, focused on landing checklists rather than object identification, get it wrong. It is not a slur on pilots. It is a known limitation of the human eye against bright sky at distance.

That does not mean no drone has ever hit a commercial aircraft. The Civil Aviation Authority has counted seven globally confirmed direct in-flight contacts. The rate of confirmed contact is dramatically smaller than the rate of reported contact. That gap is the story.

DroneXL’s Take on Drone Strike

I have been covering drone-versus-aircraft reporting for nine years. The pattern in this story matches almost every previous “drone strike” headline I have written about: a single pilot sighting, no second confirmation, no recovered debris, no aircraft damage, and an airline statement that softens within hours. The Mirror, GB News and the Post wrote the headline that gets clicks. United, the FAA and the FBI are quietly writing a different story.

If physical debris turns up on the airframe, this article needs an update. That is the bar. A red mylar balloon at 3,000 feet over a coastal city in late April is not exotic. Neither is a piece of windblown packaging riding a thermal off the Pacific. Neither is a passing bird that catches sun on its underside.

The legitimate concern about consumer drones at altitude is real. DroneXL has covered actual unauthorized drone activity over San Diego airspace, including SkySafe data showing 34 unauthorized flights in a single month near SAN, with one drone repeatedly climbing to nearly 9,000 feet. That problem deserves attention. Headlines about “drone strikes” that the airline, the FAA and the FBI all decline to confirm undercut that legitimate concern. Every false alarm makes the next real one harder to act on.

Watch the FAA’s published findings on Flight 1980 over the next several weeks. The specific question worth tracking is whether any physical debris is recovered from the airframe inspection or from the approach corridor, and whether a second pilot or radar return ever corroborated the initial report. Schulman’s track record on this kind of question is “always” not a drone. The base rate is on his side.

Sources: NBC 7 San Diego, The Mirror US, AIRLIVE, Brendan Schulman on X.

DroneXL uses automated tools to support research and source retrieval. All reporting and editorial perspectives are by Haye Kesteloo.