UAS Data Research

US-Europe TIM on UAS and UAM

William Oehlschlager, FAA ANG-C21

UAS Data Research Efforts• UAS Parameters, Exceedances, Recording Rates

for ASIAS

• UAS Test Data Collection and Analysis

• Affiliated Research Efforts

UAS Parameters, Exceedances, Recording Rates for ASIAS

Purpose• Support aggregation of UAS flight data with commercial,

general aviation and surveillance data, to develop enhanced safety analyses for NAS stakeholders, support UAS integration in the NAS, and support the Unmanned Aircraft Safety Team (UAST).

• This effort will help to develop system requirements for data collection and analytical capabilities needed for processing UAS safety data within ASIAS in order to conduct aggregate safety risk analysis.

4

Projected Benefit of Research• Develop initial supporting infrastructure requirements for

UAS flight data/analysis within ASIAS, to include consideration of system requirements and analytical capabilities

• Operational risk reduction, especially in concert with an SMS or TQM program

• Economic benefits due to reduced accident potential

• Preventative maintenance

• Potential warranty/insurance reductions

• Potential waiver assistance

5

Research Approach• Examine and determine current UAS Flight Data

Monitoring (UFDM) practices

• Describe the safety, productivity and economic benefits of UFDM

• Describe and define parameters, exceedances, and recording rates for UFDM

• Define a data standard for UFDM

• Identify and analyze data types and map them to events

6

7

UAS ASIAS UFDM: What is Flight Data Monitoring (FDM)?• FDM is a set of systems and processes which allows

operators to collect flight data (altitude, location, engine performance, etc.), aggregate the data, analyze the data, and proactively or predictively identify hazards before an accident occurs

• Widely accepted on the manned-side of flying

8

UAS ASIAS Final Report:Findings and Conclusions

• Most UAS platforms have some basic capability of producing and recording flight data

• This flight data would be useful for an ASIAS-FDM initiative, and most likely follow a similar path as General Aviation did with the National General Aviation Flight Information Database (NGAFID)

• Only a minimum number of data parameters are necessary, but most UAS platforms, even small airframes, produce robust data

• The NGAFID, or an NGAFID-like database would work well for a nationwide UFDM rollout

• Next steps should focus on development of this platform and rollout

Several UFDM category examples in report: • Loss of Battery (LOB) – a loss of power due to a complete dissipation

or failure of the onboard battery or batteries• Loss of Command and Control (LOC2) – a loss of signal or transmission

from an associated GCS• Rotor Separation – an occurrence where one or more rotor blades

physically separate from their UAS motor mounts• Loss of Control (LOC) – an inflight condition wherein the UAS becomes

uncontrollable • Hard Landing – a harder than expected contact between the UAS and

surface during a landing maneuver• Collision on Ground – a collision between the UAS and an object or

person on the ground• Collison in Air – a collision between the UAS and another object while

airborne

UAS ASIAS Final Report:Applying ASIAS Methodology

10

UAS ASIAS Final Report:Next Steps

sUAS Mid-Air Collision (MAC) Likelihood

UAS Test Data Collection and Analysis (Phase I)

Purpose• This research is working to enable an enhanced

test data collection framework and safety analysis tool to inform the UAS Integration Research Plan.

• The development of this framework/analysis tool with help users to cross-check needs for UAS data/research with test data stored in the system; as well as determining if the data meets the needs and whether additional data/testing would be required.

12

Projected Benefit of Research• Identify the key test objective types that must be

captured in an ideal UAS risk-based framework

• Identify key test data that must be captured in an integrated safety case framework

• Identifying the data collected by the FAA Test Sites that inform a risk-based framework

• Informing rulemaking and standards

• Better informed decisions based on existing data and identifying data still needed

• Contributing to industry standards

13

Research ApproachThis research will develops a Safety Case Framework as well as develop a custom means of compliance.

• Develop a safety case framework for data collection • Develop a data schema • Evaluate software and hardware requirements• Develop the reporting System and demonstrate the

overarching risk-based framework• Develop Demonstration Reporting System

14

UAS Test Data Collection:Task 1 – Safety Case Framework

15

Courtesy Mark Blanks

UAS Test Data Collection:Task 2 – Data Schema• Test Data Collection and Analysis System (TDCAS)

• Data Collection System (DCS)• Data Analysis System (DAS)

• DCS• CONOPS (1a)

• Metadata• System Information• Aircraft Procedures• Crew Members• Operational Scenario Description• Operational Considerations—Ground Bases• Operational Considerations—Airspace• Meteorological Conditions• Communications• Security

16

UAS Test Data Collection:Task 2 – Data Schema (cont.)

• ORA (1b)• Metadata• Air Risk• Ground Risk

• Unmitigated Risk Identification• Mitigated Risk Identification• Prioritization of Risks• Data Characteristics

17

UAS Test Data Collection:Task 2 – Data Schema (cont.)

Test Planning (2a)• Metadata• Narrative Format

• Test Requirements• Data Requirements• Require Resources• Test Execution• Deliverables

18

UAS Test Data Collection:Task 2 – Data Schema (cont.)

Test Data/Reports (2b)• Metadata• Narrative Format

• Test Execution• Test Data• Test Articles• Results

19

UAS Test Data Collection:Task 2 – Data Schema (cont.)

Safety Case Compilation (3)• Metadata• Narrative Format

• Safety Case Elements

20

UAS Test Data Collection:Key Findings

• Data Schema• Data need vs burden• Quantitative vs. qualitative

• Test Data• Not operational data• Different requirements

• Other Items• Clear connection from ORA to testing critical• Best practices important

21

22

UAS Test Data Collection:Next Steps

• UAS Test Data and Analysis Phase II

• UAS Safety Case Development, Process Improvement, and Data Collection

Ongoing ASSURE Projects• A18 – Small UAS Detect and Avoid Requirements Necessary for

Limited Beyond Visual Line of Sight (BVLOS) Operations• Purpose: Inform FAA regulations & industry standards for BLVOS

DAA minimum performance standards and methods of certification• Final Report: Winter 2020/21

• A19 – UAS Test Data Collection and Analysis• Purpose: Develop safety-case framework and associated data

schema to include:• Development of software & hardware requirements• Development of demonstration system and associated training materials

• Final Report: Summer 2020

• A22 – eCommerce, Emerging UAS Network and Implications on NAS Integration

• Purpose: Inform FAA risk-and-hazard analysis of potential nationwide commercial UAS delivery network

• Final Report: Fall 2021

Ongoing ASSURE Projects (cont.)• A21 – Integrating Expanded and Non-Segregated UAS Operations into the NAS: Impact

on Traffic Trends and Safety• Purpose: to develop a quantitative framework for risk-based decision making and waiver

approvals, that includes:• Descriptive analysis of current sUAS Ops• Predictive analysis of future sUAS demand• Sensitivity analysis to increase opportunity for de minimus risk approach to applications

• Final Report: Fall 2021

• A24 – UAS Safety Case Development, Process Improvement and Data Collection• Purpose: Implement the safety-case framework developed in A19 through:

• Development of Test Data Collection & Analysis System• Exercise system using advanced UAS Ops (BVLOS, Ops Over People, Automation…)• Build linkage to industry consensus standards, other rulemaking, & FAA SMS• Validate system using Ops Over People Part 107 Waiver

• Final Report: Winter/Spring 2022

• A25 – Develop Risk-Based Training and Standards for Waiver Review and Issuance• Purpose: to provide standardized risk-based process for assessing operational risk when

reviewing & approving 14 CFR Part 107 waiver applications.• Final Report: Winter/Spring 2022

Upcoming ASSURE ProjectsA23 – Validation of Low-Altitude Detect and Avoid Standards

• Purpose: Develop & validate alternative means of compliance for certification of DAA systems

• Anticipated Award: Fall 2020

A31 – Safety Risks and Mitigations for UAS Operations On and Around Airports

• Purpose: Analyze safety & risk of UAS ops on the ground at airports• Anticipated Award: Fall 2020

A36 – Urban Air Mobility: Safety Standards, Aircraft Certification and Impact on Market Feasibility and Growth Potentials

• Purpose: Inform the FAA of the challenges and needs for safe integration of UAM

• UAM Market Potential• Airworthiness regulations and their applicability to UAM aircraft certification• Evaluation of UAM integration and impact on ATC and NAS Operations

• Anticipated Award: Fall 2020

Upcoming ASSURE Projects (cont.)A44 – Mitigating GPS and ADS-B risks for UAS

• Purpose: Assess the safety & security risks of unvalidated GPS & ADS-B-In data supporting UAS operations

• Anticipated Award: Early 2021

A45 – Shielded UAS Operations: Detect and Avoid (DAA)• Purpose: Identify risks & recommend solutions to the FAA that enable

shielded UAS ops• Anticipated Award: Early 2021

A47 – A47 - Small UAS (sUAS) Mid-Air Collision (MAC) Likelihood • Purpose: Analyze both collision severity & collision likelihood to assess

risks of MAC• Anticipated Award: Early 2021