Skip to main content
Aviation & Regulations

United Crew Reports Possible Drone Strike at 3,000 ft Over San Diego

The crew of United Flight 1980 reported a possible drone strike on approach to San Diego International Airport. Here's what the incident reveals about mixed airspace risk and what every Part 107 operator needs to understand.

Eric By — M.S. Geography (GIS spec.), FAA Part 107
Updated October 25, 2026
United Crew Reports Possible Drone Strike at 3,000 ft Over San Diego

Updated October 2026: We corrected the Class B entry requirement (an airspace authorization, not a waiver), the claim that 400 feet is the floor of controlled airspace, SAN’s Class B floor altitudes, the LAANC providers we named, the recreational-flyer rules, the criminal statute that applies, and the Part 108 status. A later pass reframed the article around a reported, unconfirmed strike and corrected the reported altitudes, the approach phase, the FBI’s statement, the impact research we cited and the civil penalty caps.

On the morning of April 29, 2026, the crew of United Airlines Flight 1980 — a Boeing 737-800 carrying 48 passengers and 6 crew on approach to San Diego International Airport — radioed air traffic control with a report nobody wanted to hear: they believed they had hit a drone on the base leg of the approach.

The pilot described the object as small, red, and shiny. The reported altitude was approximately 3,000 feet.

Three thousand feet. Likely inside Class B airspace. On a commercial airport approach path.

The aircraft landed safely. United’s maintenance team found no damage, and no strike has been confirmed. The FAA is investigating, and FBI San Diego said it was working with law enforcement partners to evaluate the situation. And for anyone who holds a Part 107 certificate and operates near a controlled airport, the incident deserves more than a headline.


The Altitude Problem

FAA regulations under Part 107 limit drone operations to a maximum of 400 feet above ground level, unless the FAA grants a waiver or the drone stays within 400 feet of a structure (14 CFR 107.51). That number isn’t arbitrary — it keeps drones below the altitudes where most manned traffic operates under normal conditions. It is not the floor of controlled airspace, though: the surface areas of Class B, C, and D airspace and Class E surface areas start at the ground, the outer shelves of Class B and C start higher, and other Class E airspace starts at 700 or 1,200 feet AGL.

Three thousand feet is 7.5 times that ceiling.

If a drone was up there, flying it at 3,000 feet on approach to a major commercial airport isn’t a gray area. It’s not a technicality or a misunderstanding of the rules. No Part 107 authorization covers it, in some of the most restricted airspace in the United States.

San Diego International Airport is surrounded by Class B airspace. Class B is the controlled airspace environment built specifically around the country’s busiest commercial airports. Think of it as an inverted wedding cake, with successive layers that extend outward and upward from the airport surface. Within the innermost ring at SAN, Class B airspace begins at the surface. The outer rings have floor altitudes that step up with distance, from 1,800 feet MSL to several thousand feet, all capped at 10,000 feet MSL.

To operate a drone in Class B airspace, you need prior airspace authorization from Air Traffic Control, through LAANC or FAADroneZone (14 CFR 107.41). LAANC never authorizes anything above 400 feet, and climbing higher takes a separate waiver. In practice, the FAA would not approve a drone at 3,000 feet on an airliner approach path.


What Mixed Airspace Actually Looks Like

The aviation industry uses the phrase “mixed airspace” to describe the operating environment where manned and unmanned aircraft share altitude bands — typically the 200–400 foot range where delivery drones, recreational flyers, and low-level manned traffic occasionally intersect. There are decades of research, proposed detect-and-avoid standards, and pending regulatory frameworks built around making that altitude range work safely.

If the crew’s report is accurate, what happened near San Diego International Airport is not mixed airspace in that sense. It would mean an unauthorized drone in manned airspace — a commercial arrival corridor — at airliner altitude.

A Boeing 737-800 maneuvering onto final at 3,000 feet is typically flying faster than its final-approach speed. Even at a final-approach speed of about 140 knots (160 mph), the crew has seconds between visual acquisition of an obstacle and the point of possible impact. On a base leg at 3,000 feet, the crew is heads-down on instruments, monitoring approach briefings, configuring flaps and gear, and confirming callouts with ATC. At those closure rates, visual avoidance of a small object is difficult under the best conditions.

A drone near an approach path is an uncooperative, non-transponder-equipped obstacle. It doesn’t show on TCAS. It doesn’t talk to ATC. It gives no indication of its position to any other aircraft in the area.

The FAA reported that no other nearby pilots confirmed a drone sighting, and ATC alerting produced no additional reports. Which raises the question: was there a drone at all? The investigation is ongoing. United’s maintenance crews found no physical damage on the aircraft. The airline itself stated there is “no indication that the aircraft struck the drone or vice versa.”

What is certain is that the crew believed they hit something at 3,000 feet, described it as a drone, and that report triggered a federal investigation. Whether anything was actually in that airspace is for the investigation to establish.


The Physical Consequences

Drone operators who haven’t thought through the physics of an airborne collision tend to assume size matters in their favor. A small drone versus a large airliner — surely the aircraft wins.

The aviation industry stopped thinking in those terms after the first serious drone ingestion studies. Even a hovering 2-pound quadcopter meets a 160-mph aircraft at a closing speed of 160 mph. That kinetic energy is substantial — and it’s delivered by a rigid object with lithium-polymer batteries, hard motor mounts, and a plastic airframe that does not compress or dissipate energy the way a bird does. A bird, given the same mass and speed, compresses. A drone does not.

In 2018, the University of Dayton Research Institute fired a 2.1-pound DJI Phantom 2 into the wing of a Mooney M20 at 238 mph. The drone tore open the leading edge and damaged the main spar, which a gel bird of the same weight did not do. Engines are no safer: in the FAA-sponsored ASSURE Task A43 test, a DJI Phantom 3 ingested into a CFM56-7B, the engine on the 737 Next Generation, caused material loss and cracking across multiple fan blades. And a transport-category windshield only has to withstand a 4-pound bird at the airplane’s design cruise speed at sea level (14 CFR 25.775(b)). It was not designed around a rigid quadcopter.

United’s 737 landed without damage. That is the outcome everyone needed. It is not the outcome guaranteed by physics if the contact had been with an engine inlet or the windshield at a slightly different angle.


Criminal and Civil Exposure

The FAA is investigating. The FBI San Diego Field Office said it is working with law enforcement partners to evaluate the situation, noting reports of an alleged drone approximately 12 miles from San Diego International Airport.

Federal criminal liability for a drone that interferes with an airliner falls under 18 U.S.C. § 39B, which provides for fines and imprisonment up to one year for knowingly or recklessly interfering with an occupied aircraft in a way that poses an imminent safety hazard. If someone is seriously injured or killed, the exposure rises to 10 years or more.

On the civil side, the FAA says fines can reach $75,000 per violation, but under 49 U.S.C. 46301 that cap applies to companies other than small businesses. An individual or small business faces up to $17,062 per violation, or $1,875 for an individual serving as an airman (14 CFR 13.301), and each flight can count as a separate violation. If the drone was operated by a Part 107 holder — which would mean they likely flew without authorization in Class B airspace, exceeded maximum altitude by 650%, and operated in an airport arrival corridor — you’re looking at multiple overlapping violations.

If you operate commercially and your drone is involved in an incident like this, your Part 107 certificate is likely gone, your equipment is evidence, your identity is traceable through Remote ID, and federal prosecutors have a clear statutory path to criminal charges.


What Responsible Part 107 Operators Do

None of this is directed at operators doing the work correctly. If you’re reading AeroCartwright, you probably already know how to pull up a sectional chart, request LAANC authorization, and understand what a Class B Mode C veil means.

But incidents like San Diego are useful pressure tests for your own pre-flight habits. Walk through it:

Before any flight within 30 miles of a commercial airport:

  • Open a sectional chart and identify the airspace class at your planned altitude — not just at ground level.
  • Request LAANC authorization before wheels-up through an FAA-approved provider (Aloft, Airspace Link, or AutoPylot, among others on the FAA’s current list). LAANC approval is not a formality; it’s your legal authorization to enter controlled airspace.
  • Understand that LAANC provides clearance at specific altitudes. An approval for 200 feet does not authorize you to climb to 400 feet, and LAANC never authorizes anything above 400 feet.
  • Know the Class B floor altitudes for your position. SAN’s Class B structure has floors at 1,800 feet MSL, 2,000 feet MSL, and higher depending on distance from the airport. At 3 miles from the threshold, you are likely inside a surface-level area.

If you haven’t read You Are a Professional Pilot. Act Like One., it’s worth your time. The core point: when the FAA issued your Part 107 certificate, they added you to the same airman database as airline captains. That’s not a metaphor about attitude. It’s a statement about legal standing and regulatory expectation.

The drone that allegedly struck United 1980 may have been operated by someone who never thought of themselves as a pilot at all. That is exactly the problem.


What Comes Next

The FAA investigation will determine whether contact actually occurred. Remote ID data — if the drone was registered and broadcasting — could identify the operator. If not, physical evidence from the aircraft or ground-level camera footage in the approach corridor may help. FBI San Diego has said only that it is working with law enforcement partners to evaluate the situation.

For the broader industry, this incident lands at an awkward moment. The FAA’s proposed Part 108 BVLOS rule would let approved operators fly routine beyond-visual-line-of-sight missions without case-by-case waivers — but the final rule has been under White House review since July 10, 2026 and had not been published as of late October 2026. The regulatory argument for expanded drone access depends on an operating culture of discipline and compliance. Every unauthorized flight at 3,000 feet over a commercial airport makes that regulatory argument harder to sustain.

The people who fly responsibly — who check the sectional, request LAANC, stay within authorization — are the ones who ultimately carry the reputational cost of incidents like this one.


The FAA investigation into United Flight 1980 is ongoing. Details may change as findings are released.

Eric

Written by Eric

M.S. Geography (GIS specialization) from St. Cloud State University, FAA Part 107. Pacific Northwest-based; active public-sector Blue UAS operator. Geospatial background covering spatial data, remote sensing, and coordinate systems — applied to drone mapping workflows and deliverables.

About Eric →