A United Airlines Boeing 737 carrying 49 passengers and six crew members reported a close encounter with a drone Wednesday morning while descending toward San Diego International Airport, the latest in a mounting pattern of unauthorized drone activity near commercial flight paths that federal regulators have failed to stop.
The Federal Aviation Administration said Flight 1980, inbound from San Francisco, was at roughly 4,000 feet when the crew told air traffic control they believed they spotted a drone about 1,000 feet below them. The plane landed safely, passengers deplaned without incident, and a United maintenance team inspected the aircraft afterward, CBS News reported.
A United spokesperson told CBS News the airline's maintenance crew found nothing wrong with the jet.
"Our maintenance team found no damage after thoroughly inspecting the aircraft."
But pilot audio obtained by ATC.com paints a tighter picture than the airline's reassurance suggests. One of the pilots radioed controllers with an unmistakable note of concern in the transmission.
"I believe I just saw like a red small object, like about a thousand feet below us to our right."
The accounts diverge on one critical detail: whether the drone actually hit the plane. The FAA's statement and United's spokesperson described a sighting, a close call, not a confirmed impact. Air traffic control audio published by the New York Post, however, captured the pilot saying the aircraft "hit a drone" at about 3,000 feet. The pilot described the object as "so small" and said it appeared "red" and "shiny."
No injuries were reported in either version of events. Whether the object made contact or merely passed close enough to alarm the crew, the incident highlights the same problem: a drone had no business being anywhere near a commercial jet on final approach.
FAA rules require private drones to stay below 400 feet. Flight 1980 was ten times that altitude, well inside controlled airspace reserved for arriving and departing aircraft. The FAA said air traffic control alerted other pilots in the area after receiving the report but got no additional drone sightings in response.
This was not an isolated scare. FAA data shows more than 100 reports of drone sightings near airports every month, most of them filed by pilots. In 2025 alone, more than 1,850 drone sightings around airports were reported to the agency. The numbers keep growing, and the federal response has not kept pace.
Drone operators who fly near airports and aircraft can face criminal charges and jail time. But enforcement is spotty at best, and the FAA has acknowledged no suspect in the San Diego incident. Whether anyone will be identified, let alone prosecuted, remains an open question.
The threat is not theoretical. Last year, a drone collided with a firefighting aircraft during the Palisades Fire, damaging the plane badly enough to ground it. In 2020, a Los Angeles Police Department helicopter struck a drone while responding to a call and was forced into an emergency landing. That case led to the first criminal prosecution in the nation for unsafely operating a drone, a milestone that arrived years after the problem became obvious.
Drones have also posed risks to military aviation. In 2017, a drone collided with an Army Black Hawk helicopter near Staten Island, New York. No one was hurt, but the incident demonstrated how even a small unmanned device can threaten a large rotorcraft in flight.
The San Diego drone scare fits into a wider string of alarming near misses across the country's aviation system. The FAA has faced scrutiny over a near miss at JFK involving two jets that came within 350 feet of each other on approach, raising questions about controller workload and system reliability.
Separately, federal regulators have investigated close calls involving commercial aircraft at airports from coast to coast. A probe into a United Boeing 737 and a Black Hawk helicopter at John Wayne Airport drew attention to the dangers of mixed military and civilian traffic in congested airspace.
Drones add a layer of risk that existing air traffic control infrastructure was never designed to handle. Controllers can alert pilots, but they often cannot see or track small unmanned aircraft on radar. The burden falls almost entirely on flight crews to spot and avoid objects that may be no bigger than a shoebox.
That gap was on full display earlier this year when the FAA temporarily grounded flights at El Paso over a cartel-linked drone incursion, a stark reminder that the drone threat extends well beyond hobbyists who wander into restricted airspace by accident.
The FAA's own public records portal catalogs drone sightings by the thousands, yet the agency has not announced a systematic enforcement strategy that matches the scale of the problem. Criminal prosecution remains the exception, not the rule. The 2020 LAPD helicopter case was the first of its kind, and years later, there is little evidence that the threat of jail time has meaningfully deterred reckless operators.
Meanwhile, the skies over major airports grow more crowded. Commercial air traffic continues to rise. Recreational and commercial drone use is expanding. And the regulatory framework still relies heavily on a 400-foot altitude ceiling that no one can effectively police in real time.
Recent safety breakdowns across the national airspace system, including controller failures and missing transponders flagged by the NTSB after a deadly incident at LaGuardia, only compound the concern. Each new close call is a reminder that the margin for error is razor-thin and shrinking.
The 49 passengers aboard Flight 1980 got home safely. The next planeload may not be so fortunate, and until the FAA treats drone enforcement with the same urgency it brings to other airspace violations, the question is not whether a catastrophic collision will happen, but when.
