A Boeing 737 carrying nearly 50 passengers nearly collided with an illegal drone hovering thousands of feet above legal limits near San Diego’s airport.
Story Snapshot
- United Flight 1980 pilots spotted a small, shiny red drone at 3,000 feet during descent to San Diego International Airport, far exceeding the 400-foot legal limit.
- Aircraft at 4,000 feet, drone 1,000 feet below; crew reported possible strike but post-flight inspection found no damage.
- FAA investigating; air traffic control alerted other pilots with no further sightings.
- Incident exposes vulnerabilities in controlled airspace near major hubs during critical landing phases.
- Expert warns potential for catastrophic engine failure if collision occurred.
Incident Timeline and Pilot Report
United Airlines Flight 1980 departed San Francisco for San Diego on a Boeing 737 with 48-49 passengers and six crew members.
At 8:20 a.m. on Wednesday, April 30, 2026, pilots prepared for landing at San Diego International Airport.
During descent at approximately 4,000 feet altitude, they sighted a small, shiny red drone about 1,000 feet below, heading west.
The crew immediately radioed air traffic control, describing a possible strike around 3,000 feet on the base leg between waypoints KEEDG and SAIEE.
FAA Response and Air Traffic Control Actions
The Federal Aviation Administration confirmed the crew’s report of the drone sighting. Controllers alerted nearby pilots but received no additional reports.
The Boeing 737 landed safely at Lindbergh Field. Passengers disembarked normally.
United Airlines maintenance teams conducted a thorough inspection and found no damage to the aircraft. FAA launched an investigation into the unauthorized operation in restricted airspace.
Violation of Drone Regulations
Federal rules prohibit recreational drones above 400 feet without FAA authorization and ban them from airport vicinities.
This drone operated at roughly 3,000 feet during a critical approach phase, endangering commercial aviation.
Such violations persist despite repeated FAA reminders. This incident demands stricter enforcement to protect lives; lax oversight invites disaster in busy skies over major cities like San Diego.
San Diego International Airport handles heavy morning traffic as a key West Coast hub. Flight 1980’s encounter occurred amid routine operations, underscoring how rogue drones infiltrate controlled zones.
Pilots followed protocol by reporting instantly. No other aircraft reported issues that day, but the single sighting heightens vigilance for all.
Expert Analysis on Potential Catastrophe
Rich Martin Del, a former Air Force accident investigator, stated the incident could have turned deadly if the drone had hit an engine.
Drone strikes risk catastrophic failure, sucking debris into turbines at high speeds. Stronger penalties and detection tech make sense to safeguard passengers.
United flight from San Francisco to San Diego reports close call with drone just before landing.#Drone #UAV #closecall https://t.co/XksIKQGkjG
— SmartFlight (@SmartFlightInfo) April 30, 2026
Short-term effects include heightened pilot awareness and increased scrutiny of local airspace. In the long term, expect policy pushes for drone bans near airports and for advanced monitoring.
United’s reputation holds steady with a safe outcome. Passengers experienced no harm. Broader aviation demands robust federal action against reckless operators invading public airways.
Sources:
United Airlines pilots report close call with an apparent drone on California flight
United flight from San Francisco to San Diego reports close call with drone just before landing
SFO United pilot reports possible drone strike over San Diego: FAA
United crew reports seeing drone in airspace as plane approached
