ASTM F3478-20

Standard Practice for Development of a Durability and Reliability Flight Demonstration Program for Low-Risk Unmanned Aircraft Systems (UAS) under FAA Oversight

SIGNIFICANCE AND USE
4.1 Demonstration plans developed in accordance with this practice will include all necessary content and key considerations to support an effective flight demonstration program aimed at approval or certification of UAS by the FAA through D&R demonstration.  
4.2 This practice does not address planning requirements for UAS development testing. It is assumed that a manufacturer has completed all UAS design and development and is preparing demonstration programs to support compliance demonstration on a stable and controlled system configuration. Manufacturers who wish to prepare a detailed design and development program should review Specification F3298 for programmatic examples.  
4.3 This practice is intended to be used on low-risk UAS that meet the following design criteria and operating limitations.  
4.3.1 The UAS has a command and control link that enables the pilot-in-command to take contingency action.  
4.3.2 The unmanned aircraft (UA) has a kinetic energy of ≤25 000 ft-lb calculated in accordance with methods specified within the MOC.  
4.3.3 The UA is operated ≤400 ft above ground level (AGL).  
4.3.4 No operations over open-air assemblies (operations over people are acceptable).  
4.3.5 No flight into known icing.  
4.3.6 Maximum of 20:1 aircraft to pilot ratio.  
4.3.7 The UA is electrically powered (excludes internal combustion engines and fuel cells).
SCOPE
1.1 This standard practice is intended for low-risk UAS seeking type certification by the Federal Aviation Administration (FAA) under 14 CFR Part 21.17(b) in accordance with the FAA durability and reliability (D&R) means of compliance (MOC). The definition of “low-risk UAS” does not necessarily align with other definitions found within corresponding ASTM standards (F3442/F3442M) or other UAS-related standards. For the purposes of this practice, “low-risk” is defined as a UAS operated in accordance with the concept of operations (CONOPs), eligibility criteria, and kinetic energy threshold specified in the G-1 Issue Paper (which will be provided to the applicant by the FAA). See 4.3 for design criteria and operating limitations for low-risk UAS.  
1.2 This standard practice establishes a common methodology and key considerations for the development of minimum flight plans for low-risk UAS that demonstrate aircraft reliability as part of a D&R MOC.  
1.3 The scope of this standard practice encompasses D&R planning, data collection, and reporting.  
1.4 The values stated in SI units are to be regarded as standard. This is not intended to limit the systems of units used for design, development testing, or demonstration testing. However, the units of measurement used on pilot-facing placards and markings and manuals must be the same as those used on the corresponding equipment with recognition that international aviation utilizes feet for altitude and knots for airspeed as operational parameters.  
1.5 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use.  
1.6 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.

General Information

• Status: Published
• Publication Date: 30-Sep-2020
• ICS: 03.220.50 - Air transport
• ICS: 49.020 - Aircraft and space vehicles in general
• Technical Committee: F38 - Unmanned Aircraft Systems
• Drafting Committee: F38.01 - Airworthiness

Relations

• Refers: ASTM F3060-20 - Standard Terminology for Aircraft
• Effective Date: 01-Jan-2020
• Refers: ASTM F2909-19 - Standard Specification for Continued Airworthiness of Lightweight Unmanned Aircraft Systems
• Effective Date: 01-Sep-2019
• Refers: ASTM F3298-19 - Standard Specification for Design, Construction, and Verification of Lightweight Unmanned Aircraft Systems (UAS)
• Effective Date: 01-Feb-2019
• Refers: ASTM F3298-18 - Standard Specification for Design, Construction, and Verification of Fixed-Wing Unmanned Aircraft Systems (UAS)
• Effective Date: 01-May-2018
• Refers: ASTM F3060-16a - Standard Terminology for Aircraft
• Effective Date: 01-Nov-2016
• Refers: ASTM F3060-16 - Standard Terminology for Aircraft
• Effective Date: 01-Apr-2016
• Refers: ASTM F2908-16 - Standard Specification for Aircraft Flight Manual (AFM) for a Small Unmanned Aircraft System (sUAS)
• Effective Date: 15-Feb-2016
• Refers: ASTM F3060-15b - Standard Terminology for Aircraft
• Effective Date: 15-Sep-2015
• Refers: ASTM F3060-15a - Standard Terminology for Aircraft
• Effective Date: 01-May-2015
• Refers: ASTM F3060-15 - Standard Terminology for Aircraft
• Effective Date: 01-Mar-2015
• Refers: ASTM F3060-14 - Standard Terminology for Aircraft
• Effective Date: 01-Dec-2014
• Refers: ASTM F2909-14 - Standard Practice for Maintenance and Continued Airworthiness of Small Unmanned Aircraft Systems (sUAS)
• Effective Date: 15-Jan-2014
• Refers: ASTM F2908-14 - Standard Specification for Aircraft Flight Manual (AFM) for a Small Unmanned Aircraft System (sUAS)
• Effective Date: 15-Jan-2014

Overview

ASTM F3478-20 sets forth a standard practice for the development of a durability and reliability (D&R) flight demonstration program tailored for low-risk unmanned aircraft systems (UAS) seeking type certification under Federal Aviation Administration (FAA) oversight. The standard supports applicants by providing a structured methodology to plan, execute, and document flight demonstrations as part of the FAA's D&R means of compliance (MOC). It is intended for use once UAS design and development are complete, and does not address requirements for initial UAS development testing. The ultimate goal is to facilitate FAA approval or certification by proving aircraft reliability in operational environments.

Key Topics

• Applicability to Low-Risk UAS: The standard defines "low-risk" for the purposes of D&R MOC as UAS operated within specified concept of operations (CONOPs), eligibility criteria, and kinetic energy limits set by the FAA (≤25,000 ft-lb kinetic energy, ≤400 ft AGL, electrically powered).
• Demonstration Program Structure: Guidance covers all phases-from demonstration planning, instrumentation, and data collection to analysis and reporting.
• Documentation Requirements: A minimum of three demonstration articles must be documented, with detailed records on conformity, operating conditions, environmental data, system performance, and outcomes.
• Operational Safety and Limitations: Outlines how to document and validate safe, reliable UAS operation within permissible limits (altitude, airspace, flight over people, icing, aircraft-to-pilot ratios).
• FAA Compliance: Procedures align with FAA regulations under 14 CFR Part 21.17(b) and associated FAA documents, ensuring that test plans and final reports meet regulatory expectations.

Applications

ASTM F3478-20 is a practical resource for:

• UAS Manufacturers: Those preparing to seek FAA certification for low-risk electrically powered UAS, needing to build a compliant test case to demonstrate reliability and durability.
• Aerospace Certification Teams: Streamlining the preparation of demonstration programs, ensuring performance data supports type approval under FAA oversight.
• Test Planners and Technical Writers: Creating documentation such as demonstration plans, data collection forms, and final reports according to recognized best practices.
• Operators Requiring Certification: Providing clear criteria for operational environments, system performance, maintenance, and safety evaluations.
• Regulators and Auditors: Reference for verifying that submitted UAS flight demonstration documentation aligns with both ASTM and FAA expectations.

By following the prescribed methodology, stakeholders can develop robust demonstration programs that:

• Prove stable configuration and conformity to design,
• Collect and analyze comprehensive data (including environmental and performance metrics),
• Validate fail-safe and contingency actions,
• Clearly define demonstration limitations and conditions,
• Support objective, evidence-based final reporting for certification.

Related Standards

The practice references and aligns with several ASTM and FAA standards, including:

• ASTM F2908: Unmanned Aircraft Flight Manual Specification
• ASTM F2909: Specification for Continued Airworthiness of Lightweight UAS
• ASTM F3060 / F3341: Terminologies for Aircraft and Unmanned Aircraft Systems
• ASTM F3298: Guidance on Design, Construction, and Verification of Lightweight UAS
• ASTM F3442/F3442M: Detect and Avoid System Performance Requirements
• FAA Order 8110.54A: Instructions for Continued Airworthiness
• FAA D&R Means of Compliance (MOC): FAA official guidance for durability and reliability testing

---

Keywords: ASTM F3478-20, UAS Flight Demonstration, Durability and Reliability, FAA Oversight, Low Risk UAS, Type Certification, Unmanned Aircraft Systems, Flight Test Standards, UAS Documentation, Compliance Demonstration, Aerospace Certification

By adhering to ASTM F3478-20, UAS stakeholders can streamline the path to FAA type certification, reduce regulatory risk, and ensure consistent, reliable performance in real-world operations.

Standards Content (Sample)

This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the
Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.
Designation: F3478 − 20
Standard Practice for
Development of a Durability and Reliability Flight
Demonstration Program for Low-Risk Unmanned Aircraft
Systems (UAS) under FAA Oversight
This standard is issued under the fixed designation F3478; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (´) indicates an editorial change since the last revision or reapproval.
1. Scope 1.6 This international standard was developed in accor-
dance with internationally recognized principles on standard-
1.1 This standard practice is intended for low-risk UAS
ization established in the Decision on Principles for the
seeking type certification by the Federal Aviation Administra-
Development of International Standards, Guides and Recom-
tion (FAA) under 14 CFR Part 21.17(b) in accordance with the
mendations issued by the World Trade Organization Technical
FAA durability and reliability (D&R) means of compliance
Barriers to Trade (TBT) Committee.
(MOC).The definition of “low-risk UAS” does not necessarily
align with other definitions found within correspondingASTM
2. Referenced Documents
standards (F3442/F3442M) or other UAS-related standards.
2.1 ASTM Standards:
For the purposes of this practice, “low-risk” is defined as a
F2908 Specification for Unmanned Aircraft Flight Manual
UAS operated in accordance with the concept of operations
(UFM) for an Unmanned Aircraft System (UAS)
(CONOPs), eligibility criteria, and kinetic energy threshold
F2909 Specification for Continued Airworthiness of Light-
specified in the G-1 Issue Paper (which will be provided to the
weight Unmanned Aircraft Systems
applicantbytheFAA).See4.3fordesigncriteriaandoperating
F3060 Terminology for Aircraft
limitations for low-risk UAS.
F3298 Specification for Design, Construction, and Verifica-
1.2 This standard practice establishes a common methodol-
tion of Lightweight Unmanned Aircraft Systems (UAS)
ogy and key considerations for the development of minimum
F3341/F3341M Terminology for Unmanned Aircraft Sys-
flight plans for low-risk UAS that demonstrate aircraft reliabil-
tems
ity as part of a D&R MOC.
F3442/F3442M Specification for Detect and Avoid System
1.3 The scope of this standard practice encompasses D&R Performance Requirements
planning, data collection, and reporting.
2.2 FAA Documents:
FAAD&RMOC dated2020-02-28(AvailablefromtheFAA
1.4 The values stated in SI units are to be regarded as
to D&R applicants)
standard.This is not intended to limit the systems of units used
FAA Order 8110.54A Instructions for Continued Airworthi-
for design, development testing, or demonstration testing.
ness Responsibilities, Requirements, and Contents
However, the units of measurement used on pilot-facing
placards and markings and manuals must be the same as those
3. Terminology
used on the corresponding equipment with recognition that
international aviation utilizes feet for altitude and knots for 3.1 Definitions—See Terminology F3341/F3341M and Ter-
airspeed as operational parameters. minology F3060 for more definitions and abbreviations.
3.2 Definitions of Terms Specific to This Standard:
1.5 This standard does not purport to address all of the
3.2.1 low-risk UA, n—an unmanned aircraft with a kinetic
safety concerns, if any, associated with its use. It is the
energy of ≤25 000 ft-lb. This includes everything that is on
responsibility of the user of this standard to establish appro-
board or otherwise attached to the aircraft at maximum gross
priate safety, health, and environmental practices and deter-
weight.
mine the applicability of regulatory limitations prior to use.
For referenced ASTM standards, visit the ASTM website, www.astm.org, or
This practice is under the jurisdiction ofASTM Committee F38 on Unmanned contact ASTM Customer Service at [e-mail]. For Annual Book of ASTM
Aircraft Systems and is the direct responsibility of Subcommittee F38.01 on Standards volume information, refer to the standard’s Document Summary page on
Airworthiness. the ASTM website.
Current edition approved Oct. 1, 2020. Published November 2020. DOI: Available from Federal Aviation Administration (FAA), 800 Independence
10.1520/F3478-20. Ave., SW, Washington, DC 20591, http://www.faa.gov.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States
F3478 − 20
3.2.1.1 Discussion—The definition of “low-risk” is unique 5.4 A released and controlled UFM developed in accor-
to the D&R MOC and not intended to be used outside of this dance with Specification F2908 shall be available. The UFM
context. defines operations procedures, operations checklists, and oper-
ating limitations of the UAS. The demonstration operations
3.2.2 manual control, n—a mode of real-time control of an
shall follow the UFM in order to prove it is sufficient for a
unmanned aircraft where the remote pilot initiates changes and
qualified user to safely operate the system.
manipulates the flight controls using the UAS interface.
5.5 Areleased and controlled ICAdeveloped in accordance
3.3 Abbreviations and Acronyms:
with Specification F2909 and FAA Order 8110.54A shall be
3.3.1 CS—control station
available to maintain the UAS in a condition for safe operation
3.3.2 D&R—durability and reliability
during demonstration. ICAare commonly included as part of a
3.3.3 ICA—instructions for continued airworthiness
UMM that defines maintenance procedures, inspection
checklists, and life limits of components within the UAS.Any
3.3.4 RSSI—received signal strength indicator
maintenance,repairs,oralterationoperationscompletedduring
3.3.5 UFM—UAS flight manual
D&R demonstrations shall be in accordance with the ICA and
3.3.6 UMM—UAS maintenance manual
UMM in order to prove it is sufficient for a qualified user to
safely maintain the system.
4. Significance and Use
5.6 Demonstration Program Documentation General Re-
4.1 Demonstration plans developed in accordance with this
quirements:
practice will include all necessary content and key consider-
5.6.1 A demonstration program shall involve the develop-
ations to support an effective flight demonstration program
ment of at least three documents:
aimed at approval or certification of UAS by the FAAthrough
5.6.1.1 Demonstration Plan.
D&R demonstration.
5.6.1.2 Data Collection; Minimum Demonstration Card In-
formation.
4.2 Thispracticedoesnotaddressplanningrequirementsfor
5.6.1.3 Demonstration Program Final Report.
UAS development testing. It is assumed that a manufacturer
5.6.2 The documentation shall be structured to include the
has completed all UAS design and development and is prepar-
sections and items given in Section 6. Plans shall include the
ing demonstration programs to support compliance demonstra-
content of 6.1, data collection shall include the content of 6.2,
tion on a stable and controlled system configuration. Manufac-
and reports shall include the content of 6.3.
turers who wish to prepare a detailed design and development
5.6.2.1 The sequencing of sections may be adjusted, as
program should review Specification F3298 for programmatic
needed, for documentation efficiency and flow.
examples.
5.6.2.2 Additional sections also may be included, or sec-
4.3 This practice is intended to be used on low-risk UAS
tions may be combined, as needed.
that meet the following design criteria and operating limita-
5.6.2.3 Minor adjustments to the section titles are accept-
tions.
able to accommodate language and localization concerns and
4.3.1 The UAS has a command and control link that enables
company best practices.
the pilot-in-command to take contingency action.
5.6.3 The documentation content shall be developed in
4.3.2 The unmanned aircraft (UA) has a kinetic energy of
accordancewiththerequirements,recommendations,andguid-
≤25 000 ft-lb calculated in accordance with methods specified
ance of subsequent sections of this practice having the same
within the MOC.
titles as given in Section 6.
4.3.3 The UA is operated ≤400 ft above ground level
(AGL).
6. Documentation Structure
4.3.4 No operations over open-air assemblies (operations
6.1 Demonstration Plan (Section 8).
over people are acceptable).
6.1.1 Front Matter (Section 7).
4.3.5 No flight into known icing.
6.1.2 Demonstration Setup (8.1).
4.3.6 Maximum of 20:1 aircraft to pilot ratio.
6.1.3 Data Collection and Storage (8.2).
4.3.7 The UA is electrically powered (excludes internal
6.1.3.1 Demonstration Specific Hardware, Software, and
combustion engines and fuel cells).
Demonstration Equipment.
6.1.4 Instrumentation (8.3).
5. Demonstration Prerequisites
6.1.5 Data Analysis (8.4).
5.1 The system shall be under configuration control with
6.1.6 Demonstration Evaluation Criteria (8.5).
established change management processes and a stable and
6.1.7 Demonstration Limitations (8.6).
released system configuration, inclusive of hardware and
6.1.8 Demonstration Environment (8.7).
software.
6.1.9 Demonstration Resources (8.8).
5.2 Each demonstration article shall conform to the con-
6.1.10 Demonstration Hazard Analysis (8.9).
trolled system configuration(s).
6.1.11 Demonstration Cases (8.10).
6.1.12 Demonstration Matrix (8.11).
5.3 A minimum of three demonstration articles (UA) shall
be utilized for the D&R demonstration. 6.1.13 Demonstration Procedures (8.12).
F3478 − 20
6.2 DataCollection;MinimumDemonstrationDataContent 7.6.3 Describe the conformity status of the demonstration
6.2.1 Front Matter (Section 7). articles and include a reference to (or embed) a statement of
conformity signed by an authorized company official. High-
6.2.2 Flight Demonstration Parameters (9.1).
lightanydeviationsfromfullconformitytotheintendeddesign
6.2.3 Environmental Data Content (9.2).
definition and the substantiation for the acceptability of each
6.2.4 System Performance Data Content (in accordance
deviation.
with Demonstration) (9.3).
7.6.4 Identify the airworthiness of the demonstration ar-
6.2.5 Demonstration Card Review (9.4).
ticles and under what operating rules the demonstrations are
6.3 Demonstration Program Final Reporting (Section 10).
conducted; for example, Experimental R&D, Part 107 waivers,
6.3.1 Front Matter (Section 7).
etc.
6.3.2 Overall Demonstration Results (10.2.2)
7.6.5 Describe in the planning the methodology utilized to
6.3.3 General Objectives (10.2.3).
ensure that the UAS will maintain a static configuration
6.3.4 Specific Objectives (10.2.4)
throughout the demonstration process. Describe in the report-
6.3.4.1 D&R Demonstration (10.2.4.1)
ing how the UAS did maintain a static configuration through-
6.3.4.2 Likely Failure Demonstrations (10.2.4.2).
out the demonstration process.
6.3.5 Final Data Products (and data reduction processing
8. Demonstration Planning
methodology) (10.2.5).
6.3.6 Documentation of Resulting Changes (10.2.6).
8.1 Demonstration Setup—Each unique demonstration type
6.3.7 References (10.2.7). shall have a demonstration setup description that addresses the
6.3.7.1 UFM. following aspects:
6.3.7.2 Maintenance Manual. 8.1.1 Equipment to be used.
6.3.7.3 Data Collection Forms. 8.1.2 Flight mission.
8.1.3 Airspace and environment.
8.1.4 Overall approach description.
7. Front Matter
8.1.5 Flight envelope.
7.1 Title Page:
8.2 Data Collection and Storage:
7.1.1 This provides identification and tracking of the docu-
8.2.1 Demonstration Specific Hardware, Software, and
ment and includes the following information:
Demonstration Equipment:
7.1.1.1 Documentation Title—This should be updated to
8.2.1.1 Identify any unique hardware, software, or equip-
reflect whether this is a Planning Document, Data Collection,
ment that is included in the demonstration or used by the UAS
or Final Report.
that differs from the released system configuration.
7.1.1.2 Document unique identification number
8.2.1.2 Include an assessment of these items and rationale
7.1.1.3 Revision designation
for why the demonstration is still valid with their inclusion.
7.1.1.4 Release date
8.2.2 Describe how data will be collected, tagged,
7.1.1.5 Release authority
organized, recorded, formatted, transferred, and stored.
7.2 Record of Revisions—This subsection provides a listing
8.2.3 Establish media requirements for data collection, and
of the document revision history and a brief synopsis of the
review adequacy of media for type, amount, size, duration,
changes.
bandwidth, etc. of data to be collected and stored.
8.2.4 Describe media requirements in terms resources (what
7.3 Purpose—Thepurposeisabriefdescriptionoftheintent
kindofsystem,recorder,station,monitor),datacollected(what
of the documentation. It should include the UAS model
kind of data, what parameters), and data/media quantity and
identification and a high-level description of the requirements
type (file size, storage media, etc.).
that the document that follows is intending to satisfy.
8.2.5 Environmental data should be gathered in accordance
7.4 External References—External references should be in-
with Appendix X3.
cluded to identify any plans, regulations, configuration
8.2.6 Other sections of this practice may specify additional
information, or other relevant documents affecting or refer-
data collection requirements.
enced by the document.
8.3 Instrumentation:
7.5 General—Include an introduction and any information
8.3.1 Describe all instrumentation that is being utilized for
to appropriately set the context for the document.
data collection purposes that will support compliance determi-
7.6 Demonstration Articles and Conformity: nation.
7.6.1 Identify the demonstration articles and their released
8.3.2 List the parameters to be collected and recorded.
configuration. Generally, this is done by reference to a released Describe the parameter name, number, location, range, units,
product structure or parts list that provides the product defini-
resolution, accuracy, sample rate, and any other relevant
tion. remarks, in accordance with Appendix X3.
7.6.2 Identify the quantity of demonstration articles being 8.3.3 Consideration should be given to the instrument
utilized by serial number. The minimum acceptable quantity is accuracy, tolerances, and any calibrations to be performed to
three, in accordance with 5.3. ensure adequate and reliable data.
F3478 − 20
8.4 Data Analysis: mishapplans.D&Rdemonstrationismeanttodemonstratethat
8.4.1 Describe the data analysis methodology, procedures, the range of proposed operations within the published limits/
calculations, and algorithms that will be used to show if envelope can be conducted safely and reliably.
demonstration program objectives have been met.
8.10 Demonstration Cases:
8.4.2 Refer to FAA D&R MOC measures of performance
8.10.1 Demonstration cases define specific flight conditions
(MOPs) where appropriate when discussing how each MOP
that the UAS may experience in service. A “flight” is defined
will be determined or demonstrated.
by the length of time in which the UA is airborne. A
8.5 Demonstration Evaluation Criteria: “demonstration” also may include operations before and after
8.5.1 D&R Demonstration—The FAA dictates a successful the flight. Each demonstration case should be tracked by a
demonstration when there were no failures or degradations that designator, such as “DC123,” that can be referenced in
resulted in a UA loss of flight, loss of control, loss of demonstration cards, data collection, and reports to demon-
containment (appreciable flight path or operational area strate compliance. A set of demonstration cases for all of the
excursion), or emergency landing outside the operator’s des- MOC requirements is provided in Annex A1 – Annex A3.
ignated recovery zone. 8.10.2 The mission details should be documented in a set of
8.5.2 Likely Failure and Specific Demonstrations—The flightdemonstrationcards.Flightdemonstrationcardsoutlinea
FAA dictates a successful demonstration when there were no
specific sequence of events in a logical, efficient, and safe
failures that resulted in a loss of control or a loss of contain- manner in which to conduct the demonstration.
ment.
8.10.3 Demonstrations shall track the duration that the UA
8.5.3 All anomalous occurrences and in-flight failures shall is airborne, to include start and end times.
be documented.
8.10.4 Demonstrations shall track when D&R operations
8.5.4 The documentation of anomalous occurrences and are being conducted, to include start and end times.
in-flight failures should utilize the form template in Appendix
8.10.5 Each demonstration card should be kept clear,
X4, or the applicant’s equivalent method. concise, and understandable so as not to cause confusion
during the mission. The individuals conducting the demonstra-
8.6 Demonstration Limitations:
tion should, while using the demonstration cards, be able to
8.6.1 Define all applicable demonstration limitations as
direct the progression of the mission and ensure that all
appropriate to the demonstration conditions. Do not simply
associated demonstration team members remain aligned
include flight manual or other published limitations contained
through each step. Review of the final approved demonstration
elsewhere. Pertinent limitations may relate to the system under
cards should occur at a pre-mission brief.
demonstration, demonstration instrumentation, demonstration
8.10.6 Demonstration case definitions may consider system
facilities, demonstration vehicles, or weather.
configurations as well as operational scenarios.
8.6.2 Demonstration limitations should discuss the differ-
8.10.7 Operational scenarios shall demonstrate different
ences between the actual executed demonstration and an ideal
capabilities and considerations for the system based upon
or perfect demonstration.
operational use; for example, if a system is intended to deliver
8.7 Demonstration Environment:
packages, the demonstration program must demonstrate this
8.7.1 Briefly describe the location(s), time(s) of day,
use case.
weather, and radio frequency conditions required for the
8.10.8 Some demonstration cases in AnnexA1 – AnnexA3
demonstrations.
are specific to representative operations and are a guide as to
8.7.2 Describe the operating area and how the aircraft will
which are appropriate. See, for example, Table 1.
be maintained within the established operating area during
8.10.9 In addition, these operational scenarios should be
launch, mission flight, and recovery operations.
considered (as applicable):
8.8 Demonstration Resources: 8.10.9.1 Control Limits—Exercise max control limits.
8.8.1 List all resources required to conduct the mission (for 8.10.9.2 Delivery—Cargo release, where applicable.
example, aircraft, ranges, hardware, software, facilities, 8.10.9.3 Obstacle Avoidance—Towers, long linear infra-
personnel, etc.). structure.
8.8.2 List all resources required to transmit, record, or 8.10.9.4 Airspace—Geofence walls, ceiling, and floor.
display demonstration data. 8.10.9.5 Altitude Hold—AGL, MSL, etc.
8.8.3 Indicate that the operation of the UAS will be per- 8.10.9.6 Off-Nominal—Lost link.
formed by a remote pilot in command (RPIC) and indicate any
8.11 Demonstration Matrix:
supporting crewmembers.
8.11.1 The demonstration matrix summarizes the demon-
8.9 Demonstration Hazard Analysis: stration cases that will be flown, and any parameters and
8.9.1 Proper planning is an important element of keeping resources surrounding those demonstration cases. For D&R
hazards within acceptable limits. demonstrations, one parameter that shall be included is a
8.9.2 Describe all appropriate safety requirements, reviews, measure of time required or a mission duration required.
and documentation. Specific safety considerations should be 8.11.2 The demonstration matrix is best presented in a
included as appropriate, such as configuration restrictions, tabular format with columnar headings of specific information
performance restrictions, airspace restrictions, C2 restrictions, pertinent to the demonstration. Example demonstration matri-
RF restrictions, risk assessments, mitigating conditions, and ces are included in Appendix X6.
F3478 − 20
TABLE 1 Sample Representative Demonstrations
Sample Demonstration Case Designators
Operation Sample Characteristic Task Element Sample Representative Demonstration
(see Annex A1)
Delivery Carrying and dropping cargo Demonstrate ability to quickly drop cargo if it DC2, DC12, DC32
interferes with safe operations
Multivehicle Aircraft:pilot ratio of >1 Demonstrate both a nominal mission with full DC10, DC21
specified aircraft:pilot ratio and a failure injection
scenario at full specified aircraft:pilot ratio where
pilot in command (PIC) is required to take over
manual control of one aircraft while at least one
other enters an automated fail-safe mode
Beyond visual line of Transfer of aircraft from one CS and PIC Demonstrate handoff from one CS to another DC31
sight (BVLOS) to another without loss or duplication of control
8.12 Demonstration Procedures: 9.1.1.7 Maximum terrain height in demonstration area if
8.12.1 Pre-Demonstration Briefing/Demonstration Readi- altitude not listed in AGL.
ness Review—Describe who will attend and what will be 9.1.1.8 Any other maneuver parameter and associated tol-
addressed. Typical topics are demonstration system checkout, erance needed.
instrumentation checkout, ground station checkout, 9.1.1.9 Maneuver recovery procedure(s) that include(s) ap-
configuration, demonstration review, schedule, coordination, plicable tolerances.
security, safety, success criteria, go/no-go criteria, real-time 9.1.1.10 Data acquisition system settings.
data requirements, and reporting data requirements. 9.1.1.11 Go or no-go criteria.
8.12.2 Demonstration Execution—Identify positions to be 9.1.1.12 Demonstration card number.
manned and the use of demonstration information sheets or 9.1.2 See Appendix X1 – Appendix X5 for examples of
demonstration cards. Detailed demonstration execution proce- flight demonstration card formats.
dures shall be documented for each flight demonstration
9.2 Environmental Data Content:
objective, if demonstration information sheets or cards will not
9.2.1 Sources of weather information shall be from the U.S.
be used.
National Weather Service, or a source approved by the U.S.
8.12.3 Demonstration Documentation—Develop a method
National Weather Service; for example, Automated Surface
to document whether demonstration outcomes meet the criteria
Observing Systems (ASOS), Automated Weather Observing
for a successful demonstration in accordance with the D&R
System (AWOS), or international equivalents. If such a report
MOC.
is not available, weather information based on that pilot’s own
8.12.4 In-Process Review—The applicant shall plan to re-
observations should be used.
view demonstration data at regular cadence during the demon-
9.2.2 Visibility—Measure the prevailing visibility deter-
stration program to ensure that demonstration objectives have
mined in statute miles or fractions thereof from the RPIC’s
been met. If demonstration program objectives have not been
usual point of observation. Describe how it was measured and
met, the applicant shall review the demonstration program and
the values. Manually derived visibility shall be evaluated as
propose adjustments to meet specified objectives.
frequently as practicable. If the prevailing visibility rapidly
8.12.5 Reviewandadjustdemonstrationcardsasrequiredto
increases and decreases by ⁄2 statute mile or more, during the
meet stated demonstration objectives and introduce new cards
timeoftheobservation,andtheprevailingvisibilityislessthan
as necessary.
three statute miles, the visibility is considered to be variable.
8.12.6 Review environmental data against demonstration
The minimum and maximum visibility values observed shall
objectives and proposed operating limits.
be reported in the remarks section.
9.2.3 Winds—Recordthedirectionandspeedofthewindsat
9. Data Collection; Minimum Demonstration Data
takeoff, winds aloft during cruise from an acceptable weather
Content
source as specified in 9.2.1, and at landing. Describe how it
9.1 Flight Demonstration Parameters:
was measured and the values (that is, from true or magnetic
9.1.1 If flight demonstration cards are used, they should
north and knots or miles per hour). Units shall be consistently
contain the following minimum information, as applicable:
used and clearly marked.
9.1.1.1 Aircraft configuration with weight and center of
9.2.4 Day/Night—Record the time of day and calculate
gravity (CG), as applicable.
sunrise, sunset, and civil/nautical twilight using an almanac
9.1.1.2 Aircraft operating limits critical to the demonstra-
such as this one provided by the FAA.
tion point.
9.2.5 Sky Cover/Clouds—Record the cloud base and total
9.1.1.3 Demonstration limits.
amount of coverage in meteorological aerodrome reports
9.1.1.4 Initial conditions for start of demonstration.
(M
...