Jim_R
En-Route
- Joined
- Feb 17, 2010
- Messages
- 2,568
- Display Name
- Jim
It doesn't sound to me like drones, per se, were the issue. It sounds more to me like the FAA wanted more time to understand/approve the use of whatever anti-drone countermeasures Ft. Bliss was intending to deploy. Ft. Bliss said, "Nah, we're not going to wait." If the FAA wasn't sure the countermeasures wouldn't endanger civilian air traffic in the area, they may have felt compelled to close the airspace in an abundance of caution.A spat between FAA, DOD sort of puts FAA in a no win position. I dont know who's drone, or what was being used to find and disable it. If a medium size drone goes thru a RR commercial engine on short final for ELP there is going to be hell to pay at FAA hdqtrs. Not saying specifically I support the shutdown, but not sure what alternatives there were if the ATC had intel about drones in the zone.
It could also have been an overblown pi$$ing match between two gov't entities.
But given the "recent" collision between the helicopter and airliner in D.C., maybe the FAA reasonably decided that an airspace shutdown was the lesser evil compared to the possibility of another DoW/civilian catastrophe. I dunno.


