12-31-2022, 11:01 PM
https://dspalliance.org/remote-identific...ood-start/
Public availability of PIC location is a huge issue. We’ve all heard multiple stories of first hand accounts of people being threatened, physically attacked, and even shot down by people who were not happy with us flying our drones near them. And that was only if they could find us.
Now imagine if you will (in our best Rod Serling accent) what can happen if someone can simply pull out their phone when they see a drone and know [i]exactly[/i] where we are. It could become a true Twilight Zone situation indeed.
Public knowledge of our location was the number one concern of every drone operator and pilot we talked to. And many of them decided that they would take preemptive measures in order to protect themselves. And that would likely not end well for anyone.
Even after 1000s of comments expressing the very real and dangerous concern over this requirement, the stated reasoning behind keeping that requirement in is weak at best, a direct insult at worst. Straight from the Final Rule preamble:
[i]“Though the FAA acknowledges the concerns expressed by commenters regarding personal safety, the FAA emphasizes that there are rules against interfering with an aircraft. The FAA finds that removal of the proposed requirement is not the appropriate solution, rather community outreach and other precautions are better suited to tackle these issues. Some commenters noted that sharing of the control station location is counter to the current practice of locking aircraft doors; however, the FAA finds that the analogous and appropriate practice would be to operate from a secure or restricted access location as necessary.”[/i]
Yes, there are rules against “[i]interfering with an aircraft”[/i]. Very specific ones in 18 U.S. Code § 32. Including threats with intent. However, even with the myriad of examples available for the FAA, DOJ, and/or the U.S. Attorney’s Office to use, there has yet to be a single example of anyone being cited or prosecuted under this statute. Even the small number sent to the DOJ by the FAA have been ignored. No blood no foul seems to be the standard response.
If the FAA is going to use the existing laws as justification for including that our location in a publicly available packet of information, then they need to use them. And use them immediately, frequently, retroactively if possible, and very, very publicly.
Public availability of PIC location is a huge issue. We’ve all heard multiple stories of first hand accounts of people being threatened, physically attacked, and even shot down by people who were not happy with us flying our drones near them. And that was only if they could find us.
Now imagine if you will (in our best Rod Serling accent) what can happen if someone can simply pull out their phone when they see a drone and know [i]exactly[/i] where we are. It could become a true Twilight Zone situation indeed.
Public knowledge of our location was the number one concern of every drone operator and pilot we talked to. And many of them decided that they would take preemptive measures in order to protect themselves. And that would likely not end well for anyone.
Even after 1000s of comments expressing the very real and dangerous concern over this requirement, the stated reasoning behind keeping that requirement in is weak at best, a direct insult at worst. Straight from the Final Rule preamble:
[i]“Though the FAA acknowledges the concerns expressed by commenters regarding personal safety, the FAA emphasizes that there are rules against interfering with an aircraft. The FAA finds that removal of the proposed requirement is not the appropriate solution, rather community outreach and other precautions are better suited to tackle these issues. Some commenters noted that sharing of the control station location is counter to the current practice of locking aircraft doors; however, the FAA finds that the analogous and appropriate practice would be to operate from a secure or restricted access location as necessary.”[/i]
Yes, there are rules against “[i]interfering with an aircraft”[/i]. Very specific ones in 18 U.S. Code § 32. Including threats with intent. However, even with the myriad of examples available for the FAA, DOJ, and/or the U.S. Attorney’s Office to use, there has yet to be a single example of anyone being cited or prosecuted under this statute. Even the small number sent to the DOJ by the FAA have been ignored. No blood no foul seems to be the standard response.
If the FAA is going to use the existing laws as justification for including that our location in a publicly available packet of information, then they need to use them. And use them immediately, frequently, retroactively if possible, and very, very publicly.