{"id":15473,"date":"2020-05-12T13:17:11","date_gmt":"2020-05-12T13:17:11","guid":{"rendered":"https:\/\/saj.pachecostudios.com?p=15473"},"modified":"2020-05-12T13:17:12","modified_gmt":"2020-05-12T13:17:12","slug":"u-s-department-of-transportation-announces-technology-partners-for-remote-id-development","status":"publish","type":"post","link":"https:\/\/stateaviationjournal.com\/index.php\/unmanned-systems\/u-s-department-of-transportation-announces-technology-partners-for-remote-id-development\/%20","title":{"rendered":"U.S. Department of Transportation Announces Technology Partners for Remote ID Development"},"content":{"rendered":"\n<p>The U.S. Department of Transportation\u2019s Federal Aviation\nAdministration (FAA) announced the eight companies that will assist the Federal\ngovernment in establishing requirements for future suppliers of Remote\nIdentification (Remote ID). Remote ID will enable Unmanned Aircraft Systems\n(UAS), commonly called drones, to provide identification and location\ninformation while operating in the nation\u2019s airspace.<\/p>\n\n\n\n<p>The FAA selected the following companies to develop\ntechnology requirements for future Remote ID UAS Service Suppliers (USS):\nAirbus, AirMap, Amazon, Intel, One Sky, Skyward, T-Mobile, and Wing. These\ncompanies were selected through a Request for Information process in December\n2018.<\/p>\n\n\n\n<p>\u201cThe FAA will be able to advance the safe integration of\ndrones into our nation\u2019s airspace from these technology companies\u2019 knowledge\nand expertise on remote identification,\u201d said U.S. Transportation Secretary\nElaine L. Chao.<\/p>\n\n\n\n<p>This initial group will support the FAA in developing\ntechnology requirements for other companies to develop applications needed for\nRemote ID. The applications will provide drone identification and location\ninformation to safety and security authorities while in flight.<\/p>\n\n\n\n<p>The technology is being developed simultaneously with the\nproposed Remote ID rule. Application requirements will be announced when the\nfinal rule is published. The FAA will then begin accepting applications for\nentities to become Remote ID suppliers. The FAA will provide updates when other\nentities can apply to become qualified Remote ID USS on FAA.gov.<\/p>\n\n\n\n<p>In a follow-up email, the FAA clarified that the Cohort is\nnot part of the decision-making process for the proposed Remote ID rule final\nrule. The Cohort will help the FAA develop technology requirements for other\ncompanies to develop applications needed for Remote ID. The comment period on\nthe Remote ID Notice of Proposed Rulemaking closed on March 2, 2020, and the\nFAA is reviewing the more than 53,000 comments.<\/p>\n\n\n\n<p>Drones are a fast-growing segment of the transportation\nsector with nearly 1.5 million drones and 160,000 remote pilots now registered\nwith the FAA. The agency\u2019s ability to develop Remote ID technology\nsimultaneously with the rule enables the FAA to continue to build on a UAS\nTraffic Management (UTM) system that has demonstrated global leadership through\nthe small UAS rule and the implementation of the Low Altitude Authorization and\nNotification Capability (LAANC), which automates the application and approval\nprocess for most UAS operators to obtain airspace authorizations.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The U.S. Department of Transportation\u2019s Federal Aviation Administration (FAA) announced the eight companies that will assist the Federal government in establishing requirements for future suppliers of Remote Identification (Remote ID). Remote ID will enable Unmanned Aircraft Systems (UAS), commonly called drones, to provide identification and location information while operating in the nation\u2019s airspace. The FAA [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[127],"tags":[],"class_list":["post-15473","post","type-post","status-publish","format-standard","hentry","category-unmanned-systems"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/stateaviationjournal.com\/index.php\/wp-json\/wp\/v2\/posts\/15473","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/stateaviationjournal.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/stateaviationjournal.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/stateaviationjournal.com\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/stateaviationjournal.com\/index.php\/wp-json\/wp\/v2\/comments?post=15473"}],"version-history":[{"count":1,"href":"https:\/\/stateaviationjournal.com\/index.php\/wp-json\/wp\/v2\/posts\/15473\/revisions"}],"predecessor-version":[{"id":15474,"href":"https:\/\/stateaviationjournal.com\/index.php\/wp-json\/wp\/v2\/posts\/15473\/revisions\/15474"}],"wp:attachment":[{"href":"https:\/\/stateaviationjournal.com\/index.php\/wp-json\/wp\/v2\/media?parent=15473"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/stateaviationjournal.com\/index.php\/wp-json\/wp\/v2\/categories?post=15473"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/stateaviationjournal.com\/index.php\/wp-json\/wp\/v2\/tags?post=15473"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}