The FBI’s Washington Field Office is asking the public to identify the people it says flew a drone in restricted airspace next to Ronald Reagan Washington National Airport (DCA). The bureau says they were observed flying it on or about October 29 at the Washington Sailing Marina on Daingerfield Island in Alexandria, Virginia, directly south of the airport.
The “Seeking Information” bulletin went up on Monday, November 16, with four night-time photos. Local stations WJLA and NBC4 Washington describe three men. The FBI gives no names, ages or descriptions, and it has announced no charges.
The possible violations on the bulletin include the same federal drone law a Charlotte pilot pleaded guilty under in September, plus a second statute that only applies around places like Washington. The bulletin says the flight “impacted airport operations.” It does not say how.
The FBI Bulletin Names Three Statutes But Not What Happened At DCA
The FBI bulletin lists three possible federal violations: reckless interference with an occupied aircraft and flying inside a runway exclusion zone, both under 18 U.S.C. § 39B, and violating national defense airspace under 49 U.S.C. § 46307. Each carries a fine, up to one year in prison, or both.
The bulletin says those penalties come on top of civil fines. It gives no time of day, no drone make or model, and no account of whether a flight was delayed, held or sent around. WJLA and NBC4 Washington both reported that the FBI gave no details on the impact.

The first offense is the heaviest to prove. Section 39B(a)(2) requires that the drone recklessly interfered with an aircraft carrying people, in a way that posed an imminent safety hazard to them. The runway exclusion zone offense needs no aircraft at all, only a knowing flight inside the zone without authorization.
The airspace statute got tougher last year. Congress amended § 46307 in December 2025, and a second conviction now carries up to five years.
Katie Inman, a transportation attorney who has worked at both the FAA and the NTSB, told NBC4: “My goodness, you can get the book thrown at you.”
Tips go to 1-800-CALL-FBI, the Washington Field Office at (202) 278-2000, or tips.fbi.gov.
The Marina Sits Three-Quarters Of A Mile From Two DCA Runway Ends
The Washington Sailing Marina sits about three-quarters of a mile (1.2 km) south of the ends of Runways 1 and 4 at Reagan National, by DroneXL’s measurement from published runway coordinates. That puts it at the edge of the runway exclusion zones Congress drew around both.

A runway exclusion zone reaches 1 statute mile (1.6 km) past each end of an active runway and a quarter mile (0.4 km) to either side of its centerline. The middle of the marina is about three-tenths of a mile off both centerlines, so it sits just outside the strips. A drone launched from the shoreline would not have to go far to be inside one. The FBI has not said where the drone allegedly flew or how high.
A flight there would not need to enter a runway zone to be illegal. The Washington, D.C. Special Flight Rules Area is centered on Reagan National itself, and the FAA says flying a drone inside the area’s 15-mile inner ring is prohibited without specific FAA authorization. The agency calls it national defense airspace, the term § 46307 uses. Near most other airports a pilot can request approval through LAANC. Inside the inner ring the FAA requires a TSA/FAA waiver.
A Drone Report Stopped DCA Flights For 20 Minutes Six Weeks Earlier
Flights at Reagan National stopped for about 20 minutes on the night of September 16, 2026, after two pilots reported a drone over the active runway, the FAA told CNN. Airport workers searched and never found it. The FBI bulletin does not connect that night to the marina.
One of the two pilots was flying an American Airlines regional jet landing from Tulsa, according to CNN’s report, which quoted tower audio. The FAA said local and federal authorities were notified.
DCA has little room for surprises. Sixty-seven people died in January 2025 when an Army Black Hawk collided with an American Airlines regional jet on approach there. In March 2025, Secret Service counter-drone equipment near the airport set off false collision alerts in airline cockpits, which DroneXL covered when two House Democrats demanded answers.
DroneXL’s Take
I have argued for leniency in thin cases this year, like the Houston church videographer who flew for two minutes near a World Cup fan-festival site three days before the city’s first match. If the FBI’s account holds, a drone flown from a marina three-quarters of a mile from DCA’s runways is not a thin case. The airport’s control tower is the backdrop from that marina, and Washington has been the most restricted airspace in the country for more than twenty years. Don’t fly there. If you are one of the people in those photos, call a lawyer and then the tip line before a neighbor does.
The FBI owes the public more than one sentence, though. It has put the faces of uncharged people on its Seeking Information page, local stations have aired them, and it has said only that the flight “impacted” operations. That could mean a go-around with a full jet or a controller’s phone call, and those are very different cases. My read is that the runway scare six weeks earlier made this one a priority. The bureau should say what happened on October 29.
Sources: FBI, FBI Washington Field Office on X, NBC4 Washington, WJLA, CNN, FAA, 18 U.S.C. § 39B, 49 U.S.C. § 46307
DroneXL uses automated tools to support research and source retrieval. All reporting and editorial perspectives are by Haye Kesteloo. Read our editorial standards.



