Full Breakdown
United Airlines Flight 1980 Reports Possible Drone Strike on Approach to San Diego International Airport
4/30/2026, 5:58:39 AM
Flight 1980’s Drone Encounter Over San Diego
On 29 April 2026, United Airlines Flight 1980, a Boeing 737-800 departing San Francisco International at 6:53 a.m., reported a possible drone strike while on the base leg of its approach to San Diego International Airport (SAN) at roughly 3,000 feet. The aircraft, carrying 48 passengers and six crew members, landed safely at 8:28 a.m. and continued to Houston after a routine post-flight inspection found no damage.
Background: Drone Regulations and Airspace Restrictions
Federal Aviation Administration (FAA) rules prohibit unmanned aircraft from operating above 400 feet above ground level unless a specific waiver is granted. Drones are also barred from restricted airspace surrounding major airports. Violations can result in civil penalties up to $75,000 per incident and possible criminal prosecution.
Timeline of the Incident
- 6:53 a.m.: Flight 1980 departs SFO.
- 8:20 a.m.: Pilot radios Southern California Terminal Radar Approach Control (SoCal TRACON) to inquire about nearby drones; controller replies “not that I’m aware.”
- 8:28 a.m.: Pilot reports “We hit a drone at around 3,000 feet” while on the base leg.
- 8:30 a.m.: Aircraft lands safely; passengers deplane.
- 10:16 a.m.: Flight departs SAN for Houston.
- Later that day: United and the FAA issue statements; FAA opens an investigation.
Data Summary
- Aircraft: Boeing 737-800 (United Flight 1980).
- Passengers: 48 (one source cites 49).
- Reported altitude of encounter: pilot ? 3,000 ft; FAA ? 4,000 ft.
- Drone description: small, red, shiny.
- Legal altitude limit for drones: 400 ft (without waiver).
- FAA receives > 100 drone-sighting reports near airports each month.
Why It Matters
A drone at 3,000 feet lies within the final-approach corridor where pilots have limited reaction time. Unlike bird strikes, a drone’s metal components and lithium-ion batteries can cause engine ingestion, structural damage, or fire. The incident underscores gaps in detection, enforcement, and the potential need for mandatory transponders on unmanned aircraft.
Official Statements & Responses
- United Airlines: “United Flight 1980 reported a possible drone strike just prior to arriving in San Diego. The flight landed safely, and customers deplaned normally at the gate. Our maintenance team found no damage after thoroughly inspecting the aircraft.”
- FAA: “The agency is aware of the report and is investigating. While approaching San Diego International Airport at about 4,000 feet altitude, the crew told air traffic control they believed they saw a drone 1,000 feet below them. Air traffic control alerted other pilots but did not receive any additional drone-sighting reports.”
Criticism & Opposition
Aviation safety expert Capt. Robert Katz warned that the incident was “extremely reckless, careless and irresponsible of the drone operator because that drone could have been sucked into an engine of that airplane and that would have really been a problem.” Drone operator Brady Spear noted that recent removal of geo-fencing allowed the aircraft to fly higher than permitted, adding, “the fact that this drone operator was at 3,000 ft was pretty scary.”
Conflicting Reports & Gaps
- Altitude: Pilot cited ? 3,000 ft; FAA documentation cites ? 4,000 ft.
- Collision vs. Sighting: Pilot said “We hit a drone,” while FAA language states the crew “believed they saw a drone.”
- Passenger Count: Most sources list 48 passengers; one source reports 49.
- Physical Evidence: No damage was observed; no drone debris recovered.
Verbatim Quotes
- “we hit a drone at around 3,000 feet.” — United pilot, Flight 1980
- “It was so small I couldn’t tell,” — United pilot, Flight 1980
- “I believe I just saw like a red small object, like about a thousand feet below us to our right,” — United pilot, Flight 1980
- “It is extremely reckless, careless and irresponsible of the drone operator, because that drone could have been sucked into an engine of that airplane and that would have really been a problem.” — Capt. Robert Katz, commercial pilot
- “In the areas that's not restricted, you're still limited to 400 ft. So the fact that this drone operator was at 3000 ft was pretty scary,” — Brady Spear, drone operator
What’s Next
The FAA’s investigation will determine whether a drone violated airspace and whether a collision occurred. Findings may prompt stricter enforcement of altitude waivers, mandatory remote-identification transponders for drones, and revised penalties for illegal operations near busy airports. United Airlines has indicated it will cooperate fully and continue heightened monitoring of its fleet’s approach corridors.
