(no title)
noelsusman | 18 days ago
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.
HillRat|18 days ago
mrandish|18 days ago
This is the first explanation I've seen that fits the odd facts perfectly. This is the kind of thing that happens when two regional bureaucracies collide. The FAA has long-standing mechanisms for coordinating military use of airspace with commercial and civilian flight operations.
But instead of the usual DEA border interdiction, the administration is now tasking the military to drive this. Military commanders on a new high-priority mission to intercept drones which can attempt to cross the border anytime and anywhere realized coordinating with the FAA would require committing to active corridors and time windows in advance, limiting their mission success and resisted. The FAA realized that could lead to lots of last minute airspace restrictions, flight cancellations and increased risk of a mistake resulting in downing a civilian flight.
The regional FAA administrators responsible for flight safety around El Paso decided to escalate the dispute by simply shutting down all civilian flights, knowing that would get immediate national attention. It was an extreme action but one that's within their purview if they can't guarantee the safety of the airspace. I'm sure they expected it would put political pressure on the military to limit operations and it worked. In a sense, it also helps the military commanders because being ordered to accept FAA operational limitations gives them cover if it reduces their mission effectiveness below what they'd promised. That's probably why the military wouldn't agree on their own without it being ordered from above. They're the ones responsible for deploying expensive new anti-drone tech in field ops for the first time. Future budgets and careers are on the line.
HillRat|18 days ago
sh34r|18 days ago
prpl|18 days ago
It sounds like the DOD was being unusually indifferent to the concerns, and after deadly prior mishaps, the FAA has to be particularly careful here.
cornellwright|18 days ago
downrightmike|18 days ago
gzread|18 days ago
[deleted]
Hikikomori|18 days ago
nkrisc|18 days ago
hshdhdhj4444|18 days ago
Indeterminate end dates are not a new problem.
indoordin0saur|18 days ago
noelsusman|18 days ago
stefan_|18 days ago
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."
unknown|18 days ago
[deleted]
knowitnone3|18 days ago
[deleted]