A aviation & planes forum. AviationBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Piloting
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

ID Requirements For Drones Coming Soon



 
 
Thread Tools Display Modes
  #1  
Old October 21st 19, 03:39 PM posted to rec.aviation.piloting
Larry Dighera
external usenet poster
 
Posts: 3,910
Default ID Requirements For Drones Coming Soon

https://www.avweb.com/aviation-news/...s-coming-soon/
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 he https://www.regulations.gov/comment?...2013-0259-2697

https://www.faa.gov/uas/programs_par...AC_Meeting.pdf
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.
10
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
requirements.
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.
11
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
ID?
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
ID
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




https://www.faa.gov/uas/programs_par...ory_committee/

https://www.federalregister.gov/docu...ee-dac-meeting

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.
SUBMIT A FORMAL COMMENT
DOCUMENT DETAILS
Printed version:
PDF
Publication Date:
09/30/2019
Agencies:
Federal Aviation Administration
Dates:
The meeting will be held on Thursday, October 17, 2019, from 9:00 a.m.
to 4:00 p.m. Eastern Time.
Document Type:
Notice
Document Citation:
84 FR 51709
Page:
51709-51710 (2 pages)
Document Number:
2019-21059
DOCUMENT DETAILS
DOCUMENT STATISTICS
Page views:
2,257
as of 10/21/2019 at 8:15 am EDT
DOCUMENT STATISTICS
ENHANCED CONTENT
Regulations.gov Logo
Docket Number:
FAA-2013-0259
Supporting/Related Materials:
Notice of Meeting Graphic June 2016
ENHANCED CONTENT
PUBLISHED DOCUMENT
AGENCY:
Federal Aviation Administration (FAA), U.S. Department of
Transportation (DOT).

ACTION:
Notice of Drone Advisory Committee (DAC) meeting.

SUMMARY:
This notice announces a meeting of the DAC.

DATES:
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.

ADDRESSES:
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 . Copies of the meeting
minutes will be available on the DAC Committee website at
https://www.faa.gov/?uas/?programs_?...y_?committee/?.
A final agenda will be posted on the FAA's Notices of Public Meetings
web page
(https://www.faa.gov/?regulations_?po...making/?npm/?). You
can visit the DAC Committee website at
https://www.faa.gov/?uas/?programs_?...y_?committee/?.

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

SUPPLEMENTARY INFORMATION:
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
following:

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
Adjourn
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
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
Ads
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
NASA: ADS-B Could Allow Drones In NAS Larry Dighera Piloting 2 March 26th 16 12:43 PM
Drones Matt Herron Jr. Soaring 4 February 27th 13 05:29 PM
ADS-B + Drones Craig Funston[_2_] Soaring 0 April 2nd 12 09:40 PM
Drones T8 Soaring 11 February 10th 12 05:30 PM
ww2 training drones tongaloa Home Built 6 September 6th 03 05:55 PM


All times are GMT +1. The time now is 08:54 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright ©2004-2020 AviationBanter.
The comments are property of their posters.