Pilots on two separate aircraft reported spotting what appeared to be a drone near a runway at Reagan National Airport on Wednesday night, prompting the FAA to pause departures for roughly 20 minutes in the most restricted airspace in the country.
The pilot of American Eagle Flight 5128 radioed air traffic controllers around 8 p.m. after seeing an object fly past during final approach. A Vista America pilot on a nearby runway backed up the report moments later, telling controllers the light looked like it could be a drone. The FAA halted outbound flights and notified local and federal authorities.
The incident raises a blunt question: if a drone, whether hobbyist, commercial, or something worse, can operate freely over a runway minutes from the U.S. Capitol and the Pentagon, what exactly is the multi-layered security apparatus around Washington, D.C., doing about it?
The American Eagle pilot's description was specific but cautious. ABC News reported the pilot's words to controllers:
"We saw like a drone or something that went flying by, probably halfway down the runway on final."
The Vista America pilot, operating on a nearby runway, offered a similar account:
"I saw a light that I thought might have been a drone too."
Neither pilot claimed certainty. Both used hedged language, "like a drone or something," "might have been a drone." That ambiguity matters. It is still unclear whether a drone was physically located or recovered in the area after the reports. No arrests, fines, or criminal charges have been announced.
The FAA confirmed the sequence in a statement to ABC News, saying it "briefly paused departures at Ronald Reagan Washington National Airport for about 20 minutes after two flight crews reported seeing a drone near Runway 19." The agency said local and federal authorities were notified.
Reagan National sits inside the most restricted airspace in the United States. Federal regulations require special FAA authorization for any drone to fly there. GPS-based geofencing technology built into commercially sold drones is designed to prevent them from even lifting off in the D.C. zone. If a drone operator attempts to launch inside the restricted area, the propellers should not spin.
That means any drone operating over a Reagan National runway either carried special authorization, which no agency has claimed, or had its geofencing tampered with. Neither the FAA nor the FBI addressed that point directly.
Operating a drone in restricted airspace without authorization is a federal offense. Violators face fines and criminal charges, including possible jail time.
The FBI's statement to ABC News was a textbook non-answer. The bureau declined to comment on the specific incident and instead offered a general description of its mission:
"While we do not have a comment on specific incidents, the FBI works with our federal and local law enforcement partners to detect, track, and investigate illegal drone activity that could potentially threaten aviation safety, critical infrastructure, or public safety. Anyone who observes unsafe or improper use of a drone should report it to the FBI tipline at 1-800-CALL-FBI or tips.fbi.gov."
Detect, track, and investigate. Those are the FBI's own words. Yet no one has confirmed whether the object was actually a drone, who was operating it, or how it penetrated airspace that is supposed to be physically impossible for consumer drones to enter.
The FAA receives more than 100 reports of drone sightings near airports each month. That figure, reported by ABC News, suggests the Reagan National incident is not an isolated event but part of a persistent pattern that federal agencies have yet to solve.
Each report represents a potential collision between a small unmanned aircraft and a commercial jet carrying dozens or hundreds of passengers. A drone strike on an engine during takeoff or landing, the phases of flight with the least margin for error, could be catastrophic.
Reagan National handles heavy commercial traffic daily, and its flight paths run directly over densely populated areas of Arlington, Virginia, and Washington, D.C. The stakes of a drone incursion there are not theoretical.
The list of unknowns from Wednesday night is long. Was the object confirmed as a drone, or could it have been something else? If it was a drone, how did it bypass geofencing? Was it commercially manufactured or custom-built? Did any federal counter-drone system detect it independently of the pilot reports? Were arrivals also paused, or only departures? The FAA's statement mentioned only departures.
No agency has answered any of these questions publicly. The FAA issued a brief confirmation. The FBI issued a form letter. Local authorities have not been identified by name.
Taxpayers fund a sprawling security infrastructure around the nation's capital, restricted airspace designations, geofencing mandates, federal law enforcement coordination, and criminal penalties on the books. When two airline pilots can spot a suspected drone over a runway and the best the government can offer is a tip line, the system is not working the way Americans were told it would.
