• ID Requirements For Drones Coming Soon

    From Larry Dighera@21:1/5 to All on Mon Oct 21 07:39:46 2019
    ID Requirements For Drones Coming Soon
    Russ Niles
    October 20, 20192

    A critical step in the integration of unmanned aircraft into the
    National Airspace System is scheduled for Dec. 20 as the FAA releases
    its Notice of Proposed Rulemaking on remote identification
    requirements for drones. The agency will require that all drones emit
    some kind of signal giving aircraft and ownership information and
    that’s considered fundamental to all the other rulemaking that will
    follow. The agency doesn’t expect to make a decision on remote ID
    requirements for at least two years after the publication of the NPRM.
    “There’s probably no schedule that we could ever show that would be
    fast enough [for implementation of remote ID],” Jay Merkle, director
    of the FAA’s UAS integration office, is quoted by Avionics
    International as saying at the Drone Advisory Committee meeting
    earlier this month.

    Remote ID is considered essential by the FAA for beyond visual line of
    sight (BVLOS) operations and law enforcement wants to be able to
    identify reckless or unlawful operators. Just how those signals are
    transmitted and collected is the main technical issue and so far
    Bluetooth, Wi-Fi and dedicated networks have been proposed. Industry
    groups are naturally pulling for the most cost-effective solutions and
    there is still plenty of discussion on what information such “digital
    license plates” should provide. -------------------------------------------------------

    Comment here: https://www.regulations.gov/comment?D=FAA-2013-0259-2697

    Drone Advisory Committee Tasking 1: Remote Identification
    Equipage Subgroup
    Equipage Subgroup Scope
    In the absence of Remote ID of UAS and in consideration of security
    partners’ concerns regarding
    operations over people and other waivered operations under Part 107 in
    the intervening period, the
    FAA tasked the DAC to develop recommendations on: What voluntary
    equipage of remote identification
    technologies by UAS manufacturers or operators could occur in the
    short-term prior to a Final Rule for
    remote identification.
    The Equipage Subgroup was formed to provide recommendations to the FAA
    DAC with team members
    experience from municipalities, UAS operators, industry and public organizations. Members of the
    Subgroup had representatives from: Airmap, Ariascend, AT&T, DJI,
    FPVFC, Intel, National League of
    Cities, NUAIR, Verizon/Skyward, and Wing. Several members also
    participated or led the ASTM
    Committee F38 on Unmanned Aircraft Systems which proved essential to
    the recommendations.
    Voluntary Remote ID Equipage Recommendations
    The entire Task 1 group unanimously agreed to recommend the ASTM
    Remote ID (RID) standard to the
    DAC as the equipage basis for the voluntary program. The RID standard
    has a scope that includes
    various means to perform Remote ID.
    The standard is intended to be a world-wide adaptable standard.
    Therefore, it is expected that a
    regulator would add a regulatory “overlay” and Minimal Operational
    Performance Standard (MOPS) on
    top of the ASTM standard as part of regulatory implementation. As with
    other ASTM references by the
    FAA, this overlay may specify requirements for certain fields and may
    override other standard
    As such, the equipage workgroup, agreed on an “initial MOPS” for the
    volunteer program as a
    recommended starting place for the FAA.
    Minimum Operational Performance Standard (MOPS) for Voluntary
    Participation Program:
    • To participate in the voluntary Remote ID Program, the UAS must
    perform Remote ID according
    to the ASTM Standard using any one of the following methods outlined
    in the standard:
    o Broadcast: Bluetooth 4 or 5
    o Broadcast: Wi-Fi
    o Network
    ? Through a connected UAS, or,
    ? Non-Equipped Network Participant
    • The method used must function in the area of operation.
    • Participants must support all required fields in the ASTM standard.
    Optional fields may be used
    at participant’s discretion.
    Drone Advisory Committee Tasking 1: Remote Identification
    Incentives Subgroup
    Incentive Subgroup Scope
    In the absence of Remote ID of UAS and in consideration of security
    partners’ concerns regarding
    operations over people and other waivered operations under Part 107 in
    the intervening period, the
    FAA tasked the DAC to develop recommendations on: What types of
    incentives, if any, could be provided
    by the FAA for operators who voluntarily use UAS equipped with Remote
    The Incentives Subgroup was formed to answer this question and provide
    the FAA incentivization
    concepts that would promote voluntary Remote ID equipage. This
    subgroup was composed of
    representatives from: Wing, PrecisionHawk, Rhode Island State
    Representative, TriVector Services &
    ASTM, Airmap, DJI, New York City Fire Department, Skyward, Intel,
    National League of Cities, Air Line
    Pilots Association, Alliance for Drone Innovation, Wiley Rein LLP,
    National Press Photographers
    Association, Boeing, Amazon, Fort Wayne Court System, Fort Wayne
    Police Department, A-Cam Aerials,
    Aircraft Owners and Pilots Association, Flyte, and the Dallas Police Department. It is an assumption of
    this subgroup that safety cases may need to be developed for some of
    these proposals.
    Voluntary Remote ID Equipage Incentives Recommendations
    Ease of compliance
    • The cost and ease of compliance should be kept at a reasonable level
    such that commercial and
    recreational operators see that the benefits outweigh the cost of
    adopting Remote ID
    Incentives Provided by FAA
    Contract Preference
    • The FAA and other government agencies procuring contracts for UAS
    services or systems should
    give preferential treatment to operators or systems that have Remote
    Waiver Application Preference
    • The FAA should prioritize Part 107 waiver applications from
    operators who have Remote ID and
    provide accelerated processing of their applications
    Satisfy a Component of Waiver, Exemption, or Application Requirement
    • Remote ID should help mitigate the security concerns surrounding
    anonymous flying for
    operations over people or beyond visual line of sight waivers
    • Night operations should be facilitated through a blanket waiver when
    the operator has Remote
    ID and operates consistent with the “Operation of Small Unmanned
    Aircraft Systems Over
    People” proposed rule requirements that relate t



    Drone Advisory Committee (DAC); Meeting
    A Notice by the Federal Aviation Administration on 09/30/2019

    Comments on this document are being accepted at Regulations.gov.
    Printed version:
    Publication Date:
    Federal Aviation Administration
    The meeting will be held on Thursday, October 17, 2019, from 9:00 a.m.
    to 4:00 p.m. Eastern Time.
    Document Type:
    Document Citation:
    84 FR 51709
    51709-51710 (2 pages)
    Document Number:
    Page views:
    as of 10/21/2019 at 8:15 am EDT
    Regulations.gov Logo
    Docket Number:
    Supporting/Related Materials:
    Notice of Meeting Graphic June 2016
    Federal Aviation Administration (FAA), U.S. Department of
    Transportation (DOT).

    Notice of Drone Advisory Committee (DAC) meeting.

    This notice announces a meeting of the DAC.

    The meeting will be held on Thursday, October 17, 2019, from 9:00 a.m.
    to 4:00 p.m. Eastern Time.

    Requests to attend the meeting must be received by October 10, 2019.

    Requests for accommodations to a disability must be received by
    Thursday, October 10, 2019.

    Requests to submit written materials to be reviewed during the meeting
    must be received no later than Thursday, October 10, 2019.

    The meeting will be held at the National Transportation Safety Board
    Boardroom and Conference Center located at 420 10th Street SW,
    Washington, DC 20594. Members of the public who wish to attend, must
    register by emailing DACmeetingRSVP@faa.gov. Copies of the meeting
    minutes will be available on the DAC Committee website at https://www.faa.gov/?uas/?programs_?partnerships/?drone_?advisory_?committee/?. A final agenda will be posted on the FAA's Notices of Public Meetings
    web page
    (https://www.faa.gov/?regulations_?policies/?rulemaking/?npm/?). You
    can visit the DAC Committee website at https://www.faa.gov/?uas/?programs_?partnerships/?drone_?advisory_?committee/?.

    For questions about the DAC, please visit https://www.faa.gov/?uas/?programs_?partnerships/?drone_?advisory_?committee/? or contact Jessica Orquina, Senior Communications Specialist,
    Executive Office, UAS Integration Office, at jessica.a.orquina@faa.gov
    or 202-267-7493. Any other committee-related request should be sent to
    the person listed in this section.

    I. Background
    The DAC was created under the Federal Advisory Committee Act (FACA),
    in accordance with Title 5 of the United States Code (5 U.S.C. App. 2)
    to provide the FAA with advice on key UAS integration issues by
    helping to identify challenges and prioritize improvements.

    II. Agenda
    The agenda will likely include, but may not be limited to, the

    Official Statement of the Designated Federal Officer
    Approval of the Agenda and Minutes
    Opening Remarks
    FAA Update
    Industry-Led Technical Topics
    New Business/Agenda Topics
    Closing Remarks
    III. Public Participation
    The meeting will be open to the public on a first-come, first served
    basis, as space is limited. Registration is required for this meeting;
    members of the public may register at DACmeetingRSVP@faa.gov until
    October 10, 2019. Please provide the following information: Full legal
    name, country of citizenship, and name of Start Printed Page 51710your
    industry association, or applicable affiliation. If you are attending
    as a public citizen, please indicate so.

    The U.S. Department of Transportation is committed to providing equal
    access to this meeting for all participants. If you need alternative
    formats or services because of a disability, such as sign language, interpretation, or other ancillary aids, please contact the person
    listed under the heading FOR FURTHER INFORMATION CONTACT. Sign and
    oral interpretation, as well as a listening device, can be made
    available if requested by October 10, 2019.

    The public may present written statements to the committee at any
    time. Written statements submitted by October 10, 2019, will be
    provided to the DAC members before the meeting. The FAA is not
    accepting oral presentations at this meeting due to time constraints.

    Issued in Washington, DC, on September 23, 2019.

    Erik W. Amend,

    Manager, Executive Office, AUS-10, FAA UAS Integration Office.

    [FR Doc. 2019-21059 Filed 9-27-19; 8:45 am]

    BILLING CODE 4910-13-P

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)