Functional Requirements Document for HALE UAS Operations in the NAS - Step 1 - Version 3 - January 2006

Sep 12, 2026

Upload by Oliver

This Functional Requirements Document (FRD) compiles the functional requirements needed to realize the Access 5 Vision for Step 1: routine, safe, and reliable operations of High Altitude, Long Endurance (HALE) Unmanned Aircraft Systems (UAS) in the NAS above FL430. Requirements support FAA and standards organizations in developing minimum policies, procedures, and standards. Functional requirements are derived by decomposing Access 5 CONOPS into Aviate, Navigate, Communicate, and Avoid Hazards, with cross-cutting command/control and contingency management traceability.

LanguageEnglish

CategoryForms

FormatPDF

Pages54

Reading Time19 min

AccessFree to download

EXECUTIVE SUMMARY

1 INTRODUCTION

1.1 PURPOSE AND SCOPE

1.2 ACCESS 5 OVERVIEW

1.3 DOCUMENT ORGANIZATION

2 ACCESS 5 REQUIREMENTS ANALYSIS PROCESS

2.1 REQUIREMENTS ANALYSIS

2.2 REQUIREMENTS PERSPECTIVE

2.3 REQUIREMENTS HIERARCHY

3 HALE UAS DESCRIPTION

3.1 HALE UAS DEFINITION

3.2 ACCESS 5 OPERATIONAL REQUIREMENTS

4 UAS FUNCTIONAL ANALYSIS

Access 5 Project Office NASA P.O. Box 273 Edwards, CA 93523 USA 661-276-2440 661-276-3880 FAX [www.access5.aero](www.access5.aero) COVER SHEET Access 5 Project Deliverable Deliverable Number: SE002 Title: Functional Requirements Document for HALE UAS Operations in the NAS Step 1_v3 Filename: SE002_Functional_Requirements_Document_for_HALE_ UAS_Operations_in_the_NAS_Step_1_v3_FINAL.doc Abstract: The purpose of this Functional Requirements Document (FRD) is to compile the functional requirements needed to achieve the Access 5 Vision of “operating High Altitude, Long Endurance (HALE) Unmanned Aircraft Systems (UAS) routinely, safely, and reliably in the national airspace system (NAS)” for Step 1. These functional requirements could support the development of a minimum set of policies, procedures and standards by the Federal Aviation Administration (FAA) and various standards organizations. It is envisioned that this comprehensive body of work will enable the FAA to establish and approve regulations to govern safe operation of UAS in the NASon a routine or daily "file and fly" basis. The approach used to derive the functional requirements found within this FRD was to decompose the operational requirements and objectives identified within the Access 5 Concept of Operations (CONOPS) into the functions needed to routinely and safely operate a HALE UAS in the NAS. As a result, four major functional areas evolved to enable routine and safe UAS operations for an on-demand basis in the NAS. These four major functions are: Aviate, Navigate, Communicate, and Avoid Hazards. All of the functional requirements within this document can be directly traceable to one of these four major functions. Some functions, however, are traceable to several, or even all, of these four major functions. These cross-cutting functional requirements support the “Command / Control ”function as well as the “Manage Contingencies ”function. The requirements associated to these high-level functions and all of their supporting low-level functions are addressed in subsequent sections of this document. Status: | Access 5-Approved | | --- | | | Limitations on use: This document is an approved Access 5 Project position on the functional requirements for HALE UAS operations in the NAS for Step 1 (operations above FL430). Functional Requirements Document For HALE UAS Operations in the NAS Step 1 Version 3, January 2006 Prepared by: Access 5 Systems Engineering and Integration Team Approved by: Jeffery E. Bauer, NASA Access 5 Project Manager NATIONAL AERONAUTICS AND SPACE ADMINISTRATION David A. Buis, UNITE Industry Director UAV NATIONAL INDUSTRY TEAM 2 The following document was prepared by a collaborative team through the noted work package. This was a funded effort under the Access 5 Project. THIS PAGE INTENTIONALLY LEFT BLANK RECORD OF CHANGES | Revision | Date | Change Description | | --- | --- | --- | | Version 1 | Sept
2003 | Initial release of document. | | Version 2
1st Draft | May
2005 | Made substantial changes to Version 1.
-Defined the approach used to develop the UAS functions,-Established a functional architecture for a UAS,
-Updated the requirements in accordance with the established functional architecture, and
-Incorporated Work Package specific requirements developed for Step 1 | | Version 2
2nd Draft | Sept.
2005 | Refined the May 2005 draft.
-Incorporated numerous changes based on comments received against the May 2005 draft document,
-Added an Executive Summary,
-Added a List of Figures & Tables, References, Acronyms, and Definitions,
-Updated the Operational Requirements Table based upon revised CONOPs,-Added a HALE UAS Description Section,
-Added a Verification/Validation Section,
-Developed and incorporated an Operational/Functional Traceability Matrix, and-Developed and incorporated a requirements traceability wiring diagram for the four high-

FAQs

What is the purpose of this FRD for Access 5 Step 1?

To compile the functional requirements needed to achieve Access 5’s vision for routine, safe, and reliable HALE UAS operations in the NAS for Step 1 (above FL430).

How were the functional requirements derived?

By decomposing the operational requirements and objectives in the Access 5 Concept of Operations (CONOPS) into the functions required to operate a HALE UAS routinely and safely in the NAS.

Which four major functional areas are used to organize the requirements?

Aviate, Navigate, Communicate, and Avoid Hazards; supporting cross-cutting requirements also support command/control and manage contingencies.

Sep 12, 2026

Upload by Oliver