As the petitioner states there are many people illegally doing this and that some designs are unsafe with very little testing done to determine what is safe. At this time the requirements for any exemption should be very specific.
A public notice needs to be produced prior to each flight.
The owner of the property needs to sign off that they are the owner of the property and will be responsible for protecting any persons or other persons property.
The operator of the craft needs to sign off that they are have confirmed that they are capable of operating their craft on a prescribe flight plan.
Any owner of property within 500 feet of the proposed flight path needs to be notified by certified mail that the flight will occur and what the flight path will be.
This needs to go through an FAA office so the office can notify the operator if there is a reason the flight cannot be made. This way if their is a protest against the flight going ahead a process is available to protect property rights. For example someone claims that they legally own the land and do not permit the flight.
Anyone can now call the FAA to find out about the legal status of a drone they see flying in an unsafe manner or over their property, including law enforcement agencies.
The FAA can deny flights due to repeat violations or if they have reason to believe the operator is not safe.
The owner and operator are now legally liable if they perjure themselves in signing the application.
With this framework in place the FAA can now require the forms to be filled out and not take a blind eye to these operations.
Once a better system is in place than drones that are certified safe can fly in "public airspace" by certified operators and not be limited to flying over property that owners can control to protect property and individuals on the ground.
This process is similar to other federal permit processes that are setup to protect the public.
Anonymous
This is comment on Notice
Petitions for Exemptions; Summaries of Petitions Received
View Comment
Related Comments
View AllPublic Submission Posted: 02/04/2013 ID: FAA-2012-0897-0014
Feb 03,2013 11:59 PM ET
Public Submission Posted: 02/01/2013 ID: FAA-2012-0897-0013
Feb 03,2013 11:59 PM ET
Public Submission Posted: 01/28/2013 ID: FAA-2012-0897-0007
Feb 03,2013 11:59 PM ET
Public Submission Posted: 02/04/2013 ID: FAA-2012-0897-0015
Feb 03,2013 11:59 PM ET
Public Submission Posted: 01/29/2013 ID: FAA-2012-0897-0009
Feb 03,2013 11:59 PM ET