SEARCH · Search NASA
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Topics discussed include: Aeronautics Research Mission Directorate Integrated Systems Research Program (ISRP) and UAS Integration in the NAS Project; UAS Integration into the NAS Project; Separation Assurance and Collision Avoidance; Pilot Aircraft Interface Objectives/Rationale; Communication; Certification; and Integrated Tests and Evaluations.
UAS Integration in the NAS Project Overview.
UAS Integration in the NAS Project overview with details from each of the subprojects. Subprojects include: Communications, Certification, Integrated Test and Evaluation, Human Systems Integration, and Separation Assurance/Sense and Avoid Interoperability.
NASA's UAS Integration in the NAS project, has partnered with Rockwell Collins to develop a concept Control and Non-Payload Communication system prototype radio, operating on recently allocated UAS frequency spectrum bands. The prototype radio will be used to validate initial proposed performance requirements for UAS control communications. This presentation will give an overview of the current status of the design, development, and flight test planning for this prototype radio.
The current Global Hawk flight rules would probably not have been effective in the single event of greatest concern (the Emily encounter). The cloud top had not reached 50,000 ft until minutes before the encounter. The TOT and lightning data would not have been available until near the overflight time since this was a rapidly growing cell. This case would have required a last‐minute diversion when lightning became frequent. Avoiding such a cell probably requires continual monitoring of the forward camera and storm scope, whether or not cloud tops have been exceeding specific limits. However, the current overflight rules as strictly interpreted would have prohibited significant fractions of the successful Global Hawk overpasses of Karl and Matthew that proved not to be hazardous. Many other high altitude aircraft (ER‐2 and Global Hawk) flights in NASA tropical cyclone field programs have successfully overflown deep convective clouds without incident.The convective cell that caused serious concern about the safety of the ER‐2 in Emily was especially strong for a tropical cyclone environment, probably as strong or stronger than any that was overflown by the ER‐2 in 20 previous flights over tropical cyclones. Specifically, what made that cell a safety concern was the magnitude of the vertical velocity of the updraft, at least 20 m/s (4000 ft/minute) at the time the ER‐2 overflew it. Such a strong updraft can generate strong gravity waves at and above the tropopause, posing a potential danger to aircraft far above the maximum altitude of the updraft itself or its associated cloud top. Indeed, the ER‐2 was probably at least 9000 ft above that cloud top. Cloud‐top height, by itself, is not an especially good indicator of the intensity of convection and the likelihood of turbulence. Nor is overflying high cloud tops (i.e. > 50,000 ft) of particular concern unless there is other evidence of very strong convective updrafts beneath those tops in the path of the aircraft. center dot Lightning, especially lightning with a high flash rate, is well correlated with convective intensity. Lightning with a minimal flash rate (say 1‐3 flashes per minute) is indicative of updraft speeds of about 10 m/s in the mixed phase region where charge is being separated, generally at altitudes about 20‐25 kft in a hurricane. That is still stronger than typical updrafts (more like 5 m/s). An unresolved issue is whether there is a high and instantaneous correlation between vertical velocity in the middle troposphere (necessary for lightning generation) and near cloud top (more direct concern for overflights).
No abstract available
The primary activity for the UAS-NAS Human Systems Integration (HSI) sub-project in Phase 1 was support of RTCA Special Committee 228 Minimum Operational Performance Standards (MOPS). We provide data on the effect of various Detect and Avoid (DAA) display features with respect to pilot performance of the remain well clear function in order to determine the minimum requirements for DAA displays.
The Phase 1 DAA Minimum Operational Performance Standards (MOPS) provided requirements for two classes of DAA equipment: equipment Class 1 contains the basic DAA equipment required to assist a pilot in remaining well clear, while equipment Class 2 integrates the Traffic Alert and Collision Avoidance (TCAS) II system. Thus, the Class 1 system provides RWC functionality only, while the Class 2 system is intended to provide both RWC and Collision Avoidance (CA) functionality, in compliance with the Minimum Aviation System Performance (MASPS) for the Interoperability of Airborne Collision Avoidance Systems. The FAAs TCAS Program Office is currently developing Airborne Collision Avoidance System X (ACAS X) to support the objectives of the Federal Aviation Administrations (FAA) Next Generation Air Transportation System Program (NextGen). ACAS X has a suite of variants with a common underlying design that are intended to be optimized for their intended airframes and operations. ACAS Xu being is designed for UAS and allows for new surveillance technologies and tailored logic for platforms with different performance characteristics. In addition to Collision Avoidance (CA) alerting and guidance, ACAS Xu is being tuned to provide RWC alerting and guidance in compliance with the SC 228 DAA MOPS. With a single logic performing both RWC and CA functions, ACAS Xu will provide industry with an integrated DAA solution that addresses many of the interoperability shortcomings of Phase I systems. While the MOPS for ACAS Xu will specify an integrated DAA system, it will need to show compliance with the RWC alerting thresholds and alerting requirements defined in the DAA Phase 2 MOPS. Further, some functional components of the ACAS Xu system such as the remote pilots displayed guidance might be mostly references to the corresponding requirements in the DAA MOPS. To provide a seamless, integrated, RWC-CA system to assist the pilot in remaining well clear and avoiding collisions, several issues need to be addressed within the Phase 2 SC-228 DAA efforts. Interoperability of the RWC and CA alerting and guidance, and ensuring pilot comprehension, compliance and performance, will be a primary research area.
This presentation is a review of detect and avoid (DAA) research conducted over the last five years in support of RTCCA SC 228.
This presentation is an overview of the UAS-NAS Project and how flight testing is used to collect data to provide inputs in validating the RTCA MOPS.
This presentation is a high level overview of the flight testing that took place in 2015 for the UAS-NAS project. All topics in the presentation discussed at a high level and no technical details are provided.
No abstract available
No abstract available
This presentation is a high level overview for the UAS community of current operations.
This Phase 2 Project Plan includes the overview and detailed information regarding the areas of Command and Control, Detect and Integrated Test and Evaluation.
This presentation was presented to the Integrated Aviation Systems Program at the FY17 Annual Review of the UAS-NAS project. The presentation captures the overview of the work completed by the UAS-NAS project and its subprojects.
The UAS-NAS Project hosted a Systems Integration Operationalization (SIO) Industry Day for the SIO Request for Information (RFI) on November 30, 2017 in San Diego, California. This presentation is being presented to the same group as a follow up regarding the progress that the UAS-NAS project has made on the SIO RFI. The presentation will be virtual with a teleconference