Air Force One dropped as low as 400 feet over the White House on Halloween night, and now a United States senator wants to know exactly who signed off on it.
Quick Take
- Flight-tracking data showed the presidential aircraft making two low passes near the White House and the Washington Monument on October 29.
- Reported altitudes ranged from roughly 375 to 1,000 feet, close to or below the federal 1,000-foot minimum over Washington monuments.
- Reagan National Airport paused flights, causing more than 200 delays, while residents got as little as 15 minutes’ notice.
- Senator Tammy Duckworth, the top Democrat on the Senate’s aviation subcommittee, is demanding a full accounting from the Federal Aviation Administration (FAA).
- The FAA says it coordinated the flyover, and the White House calls it a safe, joyful Halloween moment.
What Flight Data Shows About The Low Passes
Flight-tracking records reviewed by The Washington Post showed the aircraft swooping between about 400 and 1,000 feet during two passes over the White House on October 29. Separate AirNav Radar data put the lowest point near 375 feet, skimming close to the top of the Washington Monument. Either figure puts the aircraft at or below the altitude ceiling federal rules set for flights over the capital’s monuments.
🇺🇸✈️ AIR FORCE ONE gives DC residents one HELL of a Halloween jump scare.
Soaring near roof level, the surprise flyover gave locals an unusually close view right before the White House Halloween party.
Writer: Bri pic.twitter.com/IsXOoCPvHR
— Mario Nawfal (@MarioNawfal) October 29, 2026
Federal aviation rules generally require planes to stay at least 1,000 feet above monuments inside Washington’s tightly controlled airspace. The Federal Aviation Administration (FAA) itself maintains a Special Flight Rules Area around the city specifically because low-altitude flights there carry extra risk and require advance clearance. That backdrop is why the reported altitude numbers immediately raised eyebrows among aviation watchers and lawmakers alike.
An Airport Ground Stop And Startled Neighbors
The flyover did not just rattle windows. Reagan Washington National Airport briefly paused operations to accommodate the presidential aircraft, and The Hill reported the disruption triggered more than 200 flight delays. The FAA confirmed a ground stop occurred at the airport during the event, describing it as a coordinated, if brief, traffic management decision rather than an emergency.
Residents near the White House got little warning before the aircraft roared overhead. Some reports put the heads-up at roughly 15 to 20 minutes before the first pass. The sudden noise sent frightened residents calling 911, according to The Hill, which described people so startled by the low, loud aircraft that they sought help from emergency dispatchers.
Duckworth Demands Specific Answers, Not Just An Apology
Senator Tammy Duckworth, an Illinois Democrat and ranking member of the Senate subcommittee overseeing the FAA, did not just complain about noise. She asked pointed questions: whether the FAA raised objections beforehand, what formal approval process it used, whether it followed standard notification steps, and whether it weighed the impact on passengers and airlines. Those are the kinds of questions a serious oversight body should ask.
Duckworth’s subcommittee role gives her direct standing to request records most Americans never see, including flight authorizations, waivers, and air traffic control logs. Demanding documentation before concluding is exactly how congressional oversight should work, regardless of which party occupies the White House. Everyday travelers who have sat through flight delays deserve to know whether this spectacle followed the same rules that bind every other aircraft in that airspace.
How The FAA And White House Have Responded So Far
An FAA spokesperson told the Daily Beast the flyover was coordinated with the agency ahead of time, pushing back on any suggestion the flight happened without official sign-off. The agency also confirmed the ground stop at Reagan National was arranged to accommodate the event, framing it as a managed operational decision rather than a surprise.
The White House has defended the flyover as both safe and festive. A spokeswoman said the FAA followed all necessary protocols to protect Washington residents, and added that the flight brought joy and excitement to people celebrating Halloween. That statement puts the administration’s account squarely at odds with the alarm described by startled residents and the detailed questions Duckworth is now pressing the FAA to answer on the record.
Context matters here too. Presidential aircraft routinely receive special handling in Washington’s restricted airspace, including temporary traffic changes that can delay other flights. A ground stop alone is not unusual for a presidential movement. The real question Duckworth is asking is narrower and fair: did this particular flight, at this particular altitude, follow the same coordination and notice standards that apply every other time.
Until the FAA releases the underlying authorization records and radar data, the dispute will likely stay where it is now, a credible oversight request meeting a general agency assurance that everything was coordinated. Duckworth has given the FAA a concrete list of questions. How the agency answers them, and whether it releases the paperwork to back up its claim of coordination, will determine whether this becomes a footnote or a genuine accountability moment.
Sources:
thedailybeast.com, thehill.com, people.com, avweb.com, newsobserver.com, sacbee.com, faa.gov
