Search NASA⌕ Search

Engineering topics

Trongale, Nicholas A.

Publications and source records attributed to Trongale, Nicholas A..

Cooperative Collision Avoidance Step 1 - Technology Demonstration Flight Test Report. Revision 1

The National Aeronautics and Space Administration (NASA) Access 5 Project Office sponsored a cooperative collision avoidance flight demonstration program for unmanned aircraft systems (UAS). This flight test was accomplished between September 21st and September 27th 2005 from the Mojave Airport, Mojave, California. The objective of these flights was to collect data for the Access 5 Cooperative Collision Avoidance (CCA) Work Package simulation effort, i.e., to gather data under select conditions to allow validation of the CCA simulation. Subsequent simulation to be verified were: Demonstrate the ability to detect cooperative traffic and provide situational awareness to the ROA pilot; Demonstrate the ability to track the detected cooperative traffic and provide position information to the ROA pilot; Demonstrate the ability to determine collision potential with detected cooperative traffic and provide notification to the ROA pilot; Demonstrate that the CCA subsystem provides information in sufficient time for the ROA pilot to initiate an evasive maneuver to avoid collision; Demonstrate an evasive maneuver that avoids collision with the threat aircraft; and lastly, Demonstrate the ability to assess the adequacy of the maneuver and determine that the collision potential has been avoided. The Scaled Composites, LLC Proteus Optionally Piloted Vehicle (OPV) was chosen as the test platform. Proteus was manned by two on-board pilots but was also capable of being controlled from an Air Vehicle Control Station (AVCS) located on the ground. For this demonstration, Proteus was equipped with cooperative collision sensors and the required hardware and software to place the data on the downlink. Prior to the flight phase, a detailed set of flight test scenarios were developed to address the flight test objectives. Two cooperative collision avoidance sensors were utilized for detecting aircraft in the evaluation: Traffic Alert and Collision Avoidance System-II (TCAS-II) and Automatic Dependent Surveillance Broadcast (ADS-B). A single intruder aircraft was used during all the flight testing, a NASA Gulfstream III (G-III). During the course of the testing, six geometrically different near-collision scenarios were evaluated. These six scenarios were each tested using various combinations of sensors and collision avoidance software. Of the 54 planned test points 49 were accomplished successfully. Proteus flew a total of 21.5 hours during the testing and the G-III flew 19.8 hours. The testing fully achieved all flight test objectives. The Flight IPT performed an analysis to determine the accuracy of the simulation model used to predict the location of the host aircraft downstream during an avoidance maneuver. The data collected by this flight program was delivered to the Access 5 Cooperative Collision Avoidance (CCA) Work Package Team who was responsible for reporting on their analysis of this flight data.

Trongale, Nicholas A.↗

Notional Airspace Operations Demonstration Plan

The airspace operations demonstration (AOD) is intended to show that the Access 5 Step 1 functional requirements can be met. The demonstration will occur in two phases. The initial on-range phase will be carried out in restricted airspace to demonstrate the cooperative collision avoidance (CCA) functional requirements and to provide risk-reduction for the AOD by allowing the test team to rehearse some elements of the demonstration mission. The CCA system to be used in these flights is based on Automatic Dependent Surveillance-Broadcast (ADS-B) which is a commercially-available system by which airplanes constantly broadcast their current position and altitude to other aircraft and ground resources over a dedicated radio datalink. The final phase will occur in the national airspace (NAS) and will be the formal demonstration of the remainder of the proposed functional requirements. The general objectives of the AOD are as follows: (1) Demonstrate that the UAS can aviate in the NAS (2) Demonstrate that the UAS can navigate in the NAS (3) Demonstrate that the UAS can communicate with the NAS (4) Demonstrate that the UAS can perform selected collision avoidance functions in the NAS (5) Demonstrate that the UAS can evaluate and avoid weather conflicts in the NAS (6) Demonstrate that the UAS can provide adequate command and control in the NAS In addition to the stated objectives, there are a number of goals for the flight demonstration. The demo can be accomplished successfully without achieving these goals, but these goals are to be used as a guideline for preparing for the mission. The goals are: (1) Mission duration of at least 24 hours (2) Loiter over heavy traffic to evaluate the data block issue identified during the Access 5 Airspace Operations Simulations (3) Document the contingency management process and lessons learned (4) Document the coordination process for Ground Control Stations (GCS) handoff (5) Document lessons learned regarding the process of flying in the NAS Preliminary planning for a notional mission to achieve the objectives and goals has been prepared. The planning is intended to serve as a guide for detailed planning of the AOD.

Trongale, Nicholas A.↗