SFO United pilot reported possible drone strike near San Diego—FAA investigating
possible drone – A United Airlines pilot said he may have hit a drone during landing at San Diego International Airport. The flight landed safely, and the FAA is investigating while United reports no damage found.
A possible drone incident near San Diego is now under federal review after a United Airlines pilot reported the aircraft hit a drone while landing.
The event was tied to United Flight 1980. which was traveling from San Francisco International Airport to San Diego International Airport on Wednesday morning.. According to the FAA investigation. the pilot told air traffic controllers about a suspected “drone” sighting after landing guidance at Lindbergh Field.
Drone at high altitude raises immediate safety questions
The pilot’s report placed the encounter around the aircraft’s base leg approach path. with the description indicating the drone was seen near roughly 3. 000 feet.. The FAA said the sighting occurred at about 4. 000 feet—an altitude that is well above where most recreational and typical commercial drone operations are legally permitted without specific authorization.
That gap matters because drone rules are designed around predictable behavior in shared airspace.. When a report suggests a drone may have been operating at an altitude far higher than allowed. it raises questions about compliance. monitoring. and how quickly authorities can identify the location. operator. and flight path involved.
United says plane inspection found no damage
While the report prompted an FAA response, the flight itself landed safely. United said that a postflight inspection of the Boeing 737 found no damage, offering some reassurance that whatever was reported did not result in a detectable impact significant enough to affect the aircraft’s condition.
Even so, incidents like this rarely hinge on whether damage is visible right away.. Pilots’ observations. radar or tracking limitations. and the difficulty of confirming a small object at specific altitudes can leave investigators with incomplete information—especially when the drone is not recovered or visually confirmed.
For air traffic operations. the FAA said controllers alerted other pilots in the area but did not receive any additional drone reports.. That means the universe of information remained narrow: one pilot’s account. controller communication. and whatever records can be reconstructed from available systems.
Why “possible strike” reports are taken seriously
From a safety perspective, a “possible strike” report forces aviation professionals to treat the event as real until disproven.. A drone—depending on its size. speed. and whether it is in the approach corridor—could pose a risk to an aircraft’s windshield. engine components. or flight control surfaces.
At the same time, drone incidents are notoriously hard to verify.. Air crews often rely on brief visual cues. and smoke or glare. distance. and workload can affect how an object is interpreted.. Investigators therefore focus on matching reported timing and location to flight logs, air traffic communications, and any available tracking information.
There’s also a broader public angle to consider.. When a major airline reports an incident involving small unmanned aircraft, it can quickly escalate public concern about drone safety.. That concern is amplified when reported altitude conflicts with the rules, because it hints at the possibility of unapproved operations.
The human impact: passengers, crews, and communities
Although United’s inspection did not show damage and the aircraft landed safely. the incident would still have affected everyone onboard.. Approach and landing phases are among the most workload-intensive moments for pilots. and any unexpected sighting can change how crews monitor and coordinate with air traffic.
For nearby communities around airports. drone reports also heighten anxiety—especially when people assume unmanned aircraft should be “somewhere else. ” safely out of the way.. In reality. airports are close to populated areas. and drone activity can overlap with routes even when operators believe they are staying within boundaries.
As investigations continue, the practical question for the public will be whether authorities can translate one report into actionable enforcement.. If investigators can identify the drone’s operation or operator. the outcome could feed into broader efforts to deter high-altitude and unauthorized flying.
For the industry, the episode is another reminder that unmanned systems are now part of the everyday risk equation around airports. Even when damage is not found, each report contributes to how airlines, regulators, and local communities think about detection, reporting, and compliance.
Finally. this case may influence how future incidents are handled operationally—how quickly alerts are issued to surrounding traffic. how crews document observations. and how quickly federal investigators can determine whether a “possible hit” was a true impact or a misidentified object.. Either way, it underscores the need for clarity in drone operations in shared airspace—especially near approach paths.