alt Hacker NewsDoesn't really pass the sniff test. Why would you need a 10 day closure to deal with a drone incursion?
I'm guessing DoD and the FAA were squabbling over a test the military wanted to run, and it didn't go up the chain fast enough to get resolved before testing was scheduled to begin.
Edit: Here's the actual notice from the FAA[1]. Note that it was issued at 0332 UTC, but the restrictions weren't scheduled to go into place until 0630 UTC. Either the FAA is clairvoyant, or Sean Duffy is lying.
Replies
Charitably guessing that if they don't know how long they'll need to keep airspace closed then you give yourself plenty of time and rescind early if necessary, as opposed to continually issuing extensions which could cause confusion.
Was it meant to be "up to 10 days" rather than 10 days? If the drones are no longer flying over the airport it makes sense they'd open it back up.
Ding ding. Always assume weaponized incompetence in this administration:
https://www.cbsnews.com/news/airspace-closure-followed-spat-...
> FAA Administrator Bryan Bedford on Tuesday night decided to close the airspace — without alerting White House, Pentagon or Homeland Security officials, sources said.
In the meantime, the politician responsible of course made up a quick lie and yall ran with it, fantasizing about cartel MANPADs:
> Transportation Secretary Sean Duffy said in a statement, "The FAA and DOW acted swiftly to address a cartel drone incursion."
[dead]
Recent updates say this was a unilateral call by FAA because DOD was refusing to coordinate with them for creating safety corridors for DOD drones and/or HEW usage. Issues came to a head after DOD shot down a highly threatening mylar party balloon, which FAA evidently considered to be a somewhat reckless use of military weaponry in a US city's airspace.