A NORAD fighter jet deployed flares and escorted a plane out of restricted airspace over Camp David on Saturday morning, the second such intercept during Trump's presidency, raising fresh questions about how private pilots keep blundering into presidential no-fly zones.
President Donald Trump was at the Maryland retreat when an unidentified aircraft flew into the permanent no-fly zone surrounding Camp David near Thurmont, prompting NORAD to scramble an F-16, Fox News reported. The fighter jet dispensed flares, a standard but aggressive measure meant to grab a non-responsive pilot's attention, and then escorted the aircraft safely out of the area.
Trump had arrived at Camp David on Friday evening aboard Marine One. The airspace violation occurred the following morning. NORAD, the joint U.S.-Canadian command responsible for defending North American airspace, confirmed the intercept through both the Defense Visual Information Distribution Service and a post from First Air Force on X.
First Air Force, which operates under NORAD, posted a blunt advisory on X directed at general aviation pilots:
"Pilots! @NORADCommand fighter aircraft intercepted an aircraft violating restricted airspace over Thurmont, MD, resulting in flares being deployed. Make sure to check NOTAMs before takeoff to ensure you have current information about TFRs in your area. Stay Safe, Fly Informed!"
NOTAMs, Notices to Air Missions, are the standard alerts the Federal Aviation Administration publishes to warn pilots about temporary flight restrictions, or TFRs, including those triggered whenever the president travels. Camp David carries a permanent no-fly zone under normal circumstances. When the president is on site, additional restrictions tighten the perimeter further.
The DVIDS release spelled out what intercepted pilots are supposed to do: tune immediately to emergency radio frequency 121.5 or 243.0, reverse course, and await further instructions. That the F-16 had to fire flares suggests the pilot either failed to monitor those frequencies or did not respond quickly enough for NORAD's comfort.
Saturday's incident was not the first time a private aircraft wandered into restricted airspace over Camp David while Trump was staying there. A plane was intercepted over the retreat in June under similar circumstances, and the pilot was safely escorted away. Neither the identity of Saturday's pilot nor the type of aircraft involved has been disclosed.
No injuries, damage, or arrests were reported in connection with the latest intercept. Whether the pilot faces FAA enforcement action or other regulatory consequences remains unclear.
Presidential airspace violations by small-plane pilots are not uncommon, and most turn out to be careless rather than malicious. But each one forces a live military response, armed fighter jets closing on civilian aircraft at high speed, and every second of delay in identifying the threat raises the stakes for the Secret Service detail protecting the commander in chief.
NORAD handled Saturday's breach by the book: intercept, flares, escort, all-clear. The system worked. But the fact that it had to work twice over the same location in a matter of months suggests that checking a NOTAM before takeoff is a step too many pilots skip, and that a polite post on X may not be a sufficient deterrent.
When an F-16 has to light up flares over the president's weekend retreat, the public deserves to know who was flying that plane and why they were there. Until the FAA or NORAD releases those details, the incident sits in a familiar and uncomfortable category: a near-miss that ended well, with no visible accountability to discourage the next one.
