[vc_row][vc_column][vc_column_text]The FAA is moving to drastically change the rights and responsibilities of model aircraft pilots by enacting new rules. This may be one of the most important changes in the history of the hobby.<\/p>\n
On December 31, 2019, the FAA published its proposed rule for Remote Identification of Unmanned Aircraft Systems<\/a> in the Federal Register. This proposal outlines a system for drones to broadcast their location, the location of the operator, and other related information. Most drones will be required to adopt this system, and non-compliant aircraft will be significantly limited in their capabilities.[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_single_image image=”5721″ img_size=”full” alignment=”center” onclick=”link_image”][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]FAA Press Release:\u00a0https:\/\/www.faa.gov\/news\/press_releases\/news_story.cfm?newsId=24534<\/a><\/p>\n Overview:\u00a0https:\/\/www.faa.gov\/uas\/research_development\/remote_id\/<\/a><\/p>\n Proposed Rule In Detail:\u00a0https:\/\/www.federalregister.gov\/documents\/2019\/12\/31\/2019-28100\/remote-identification-of-unmanned-aircraft-systems<\/a><\/p>\n Joshua Bardwell’s Interview:\u00a0https:\/\/www.youtube.com\/watch?v=4E1aEym-1cQ<\/a><\/p>\n DJI Article: We Strongly Support Drone Remote ID. But Not Like This<\/a><\/p>\n Pilot Institute:\u00a0Remote ID Response Guide \u2013 How to Submit Your Comment to the FAA<\/a><\/p>\n The point of this article is not to be alarmist; remember that this is a proposal<\/em> and not yet a rule<\/em>. It is open to comment and can be altered and amended.\u00a0 This is a call to action, we, as a community, need to mount a strong response to ensure the FAA hears our voices. The time to act is now, before the end of February 2020.<\/p>\n This article relates only to the proposal from Dec 31, 2019. Readers finding this article after April 2020 should not use this information as reference for the final implemented Remote ID system.<\/em>[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n As proposed, the Remote ID system records the position and identity of a drone in flight and its operator. This data may be broadcast from the drone in real-time, and is saved to a remote server for six months.<\/p>\n Unmanned aircraft fall into three categories: “Standard”, “Limited”, and “without Remote ID”.<\/p>\n Standard-equipped drones communicate their location and their operator’s location continuously in flight. The drone broadcasts this information locally over a radio frequency. If internet is available, the information is also sent to a server. These drones have the least restrictions on what they are allowed to do.<\/p>\n Limited drones require that the control station communicate its location continuously in flight. These must always communicate this information over the internet. They are never allowed to fly more than 400ft from the operator. Drones with Limited Remote ID are designed to automatically enforce the 400ft distance restriction and prevent the drone from taking off if internet is not available.<\/p>\n Drones fabricated non-commercially by an individual may be flown without Remote ID. To qualify, the majority of the drone must be fabricated by that person, not simply assembled from separately purchased parts. Drones without remote ID must only be flown at FAA-approved flying sites and never beyond visual line-of-sight.<\/p>\n The proposal applies to all drones that are required to be registered. Currently, drones are exempt if they are under 250g (.55lbs) and flown only for recreation. However, the requirements for registration could change in the future to include sub-250g craft.[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n Other aspects of the proposal include:<\/p>\n A lot of the proposal lacks specifics, including the method used for collecting the operator’s location and the broadcast frequency and protocol for the messages. The FAA has intentionally left out other information, such as the cost of the remote database service. The FAA intends for 3rd parties to administer this service, similar to what is done now for LAANC<\/a>.<\/p>\n As written, this proposal removes rights to almost all airspace for many existing aircraft.<\/p>\n Some of the effects of this proposal would be:<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_single_image image=”5722″ img_size=”full” add_caption=”yes” alignment=”center” onclick=”link_image”][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n The FAA states that “The remote identification of UAS is necessary to ensure public safety and the safety and efficiency of the airspace of the United States.” The system facilitates “future, more advanced operational capabilities” such as those that allow drones to communicate with each other and with manned aircraft. This could allow drones to operate beyond visual line of sight and provide better information to air traffic controllers.<\/p>\n The FAA believes that enhancing safety, efficiency, and security with this system would serve the public interest. This system would provide data to national security and law enforcement agencies. The FAA states that real-time use of the data could be used to facilitate compliance, enforcement, and educational actions.<\/p>\n Model flying is a safe activity which does not pose significant risk to people or property. Unfortunately, it appears that decades of history were not enough to persuade the authors of the proposal.<\/p>\n Remote ID could actually improve our ability to fly, possibly opening the door to operations beyond visual line of sight\u2014and there is some hope that the FAA wants to make adoption easy. The proposal includes the line “Nothing in this proposal would prevent a person from building a UAS with remote identification for educational or recreational purposes.” Remote ID might not be a great burden to operators if all of the following are true:<\/p>\n It’s important to understand, though, that there are no guarantees<\/strong> and a great many unknowns<\/strong>.<\/p>\n The FAA is pushing hard for all unmanned craft to be Remote ID compliant. Since a great deal of recreational aircraft are fabricated or assembled for non-commercial purposes, recreational users must have a reasonable means to add it to their systems.<\/p>\n Even if the above all work out in our favor, the proposal requires that each aircraft be individually registered with a certificate of compliance filed. For collectors, the registration costs will add up quickly.<\/p>\n While some blogs and vloggers are providing and reacting to incomplete or inaccurate information, this proposal definitely has the potential to destroy recreational aircraft flight as we know it. It’s critically important<\/strong> to respond to the FAA on these matters.[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_single_image image=”5758″ img_size=”full” add_caption=”yes” alignment=”center” onclick=”link_image”][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n The FAA invites comments on this proposal, which can be easily submitted online. The best thing we can each do is submit a reasonable comment.<\/p>\n To make a convincing response, you must be informed on the details of the proposal. It’s best to read the full text<\/a> of the proposal. If not, the FPV Freedom Coalition<\/a> has a FAQ page on Remote ID<\/a> that breaks it down to essentials, and a longer-form Guide to Remote ID<\/a>.<\/p>\n As you develop your comment, consider (comments below do not represent GetFPV’s view):<\/p>\n If you’re looking for more guidance, the AMA has published a template response<\/a>, and the FPVFC has a\u00a0working document with talking points and policy suggestions<\/a>.<\/p>\n Be sure to write your own comment<\/strong> rather than copy and pasting a response you find somewhere. Duplicated responses may not carry as much weight.<\/p>\n Once you’ve written your response, visit the comment page for remote ID<\/a> to submit it. You have until March 2, 2020.<\/p>\n The FAA is about to write some of the most influential rules about model aircraft in the United States. In these 60 days, we have the opportunity to directly contribute to that conversation. We must remind the FAA that we are responsible users of the airspace, that the airspace can be used safely in the future, and that recreational use is at least as valid as any commercial interest. The more of us that respectfully respond, the more seriously we will be taken. On behalf of all racers, freestyle pilots, and all model aircraft enthusiasts: please submit a comment<\/a> on this proposal<\/strong>!<\/p>\n Every comment helps.[\/vc_column_text][\/vc_column][\/vc_row]<\/p>\n","protected":false},"excerpt":{"rendered":" The FAA may drastically change the rights and responsibilities of model aircraft pilots by enacting new rules. This may be one of the most important changes in the history of the hobby.<\/p>\n","protected":false},"author":2,"featured_media":5721,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[138],"tags":[6985,6982,6984,6983],"class_list":["post-5672","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-fpv-news","tag-community","tag-faa","tag-proposal","tag-regulations","infinite-scroll-item","generate-columns","tablet-grid-50","mobile-grid-100","grid-parent","grid-33"],"_links":{"self":[{"href":"https:\/\/www.getfpv.com\/learn\/wp-json\/wp\/v2\/posts\/5672","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.getfpv.com\/learn\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.getfpv.com\/learn\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.getfpv.com\/learn\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.getfpv.com\/learn\/wp-json\/wp\/v2\/comments?post=5672"}],"version-history":[{"count":29,"href":"https:\/\/www.getfpv.com\/learn\/wp-json\/wp\/v2\/posts\/5672\/revisions"}],"predecessor-version":[{"id":5932,"href":"https:\/\/www.getfpv.com\/learn\/wp-json\/wp\/v2\/posts\/5672\/revisions\/5932"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.getfpv.com\/learn\/wp-json\/wp\/v2\/media\/5721"}],"wp:attachment":[{"href":"https:\/\/www.getfpv.com\/learn\/wp-json\/wp\/v2\/media?parent=5672"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.getfpv.com\/learn\/wp-json\/wp\/v2\/categories?post=5672"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.getfpv.com\/learn\/wp-json\/wp\/v2\/tags?post=5672"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What’s Remote ID?<\/h2>\n
Standard Remote ID<\/h3>\n
Limited Remote ID<\/h3>\n
Without Remote ID<\/h3>\n
How will Remote ID be implemented?<\/h2>\n
\n
What are some of the potential impacts of Remote ID to FPV?<\/h2>\n
\n
Why is Remote ID necessary?<\/h2>\n
Is this all overblown?<\/h2>\n
\n
\n
What can we do about it?<\/h2>\n
\n
Submitting your comment<\/h3>\n
Conclusion<\/h2>\n