Future Opportunities for Aero Supply Chain
Manufacturers in Michigan to enter the aerospace manufacturing and supply chain ecosystem. How they can support U.S. competitiveness in the aerospace industry.
Aerospace Supply Chain↗
SEARCH · Search NASA
Results for “sUAS Manufacturing”
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.
A Grounded Theory of UAS Reported Accidents
Context: The manufacture and operation of sUAS are not as regulated as today’s commercial operation, and their widespread use introduces new risks and hazards to the general public. Aim: Our intent is to understand the various processes that prevent or portend sUAS incidents or accidents and the influence that pilots’ expectations and training have on these processes. Method: We use classic grounded theory on sUAS reported accidents (and incidents). Results: We identified three categories, Control Interference, Reviewing and Reporting, which describe various processes surrounding UAS accidents based on the dataset analyzed. Conclusion: The use of grounded theory can offer a different perspective in the analysis of UAS accidents. In addition, the traceability between data sources and the method results facilitate result validation, and navigation. While the results are preliminary, the concepts can be expanded through the use of other accident datasets or used as basis for UAS accident surveys.
Carlos Paradis↗
A Grounded Theory of UAS Reported Accidents
Context: The manufacture and operation of sUAS are not as regulated as today’s commercial operation, and their widespread use introduces new risks and hazards to the general public. Aim: Our intent is to understand the various processes that prevent or portend sUAS incidents or accidents and the influence that pilots’ expectations and training have on these processes. Method: We use classic grounded theory on sUAS reported accidents (and incidents). Results: We identified three categories, Control Interference, Reviewing and Reporting, which describe various processes surrounding UAS accidents based on the dataset analyzed. Conclusion: The use of grounded theory can offer a different perspective in the analysis of UAS accidents. In addition, the traceability between data sources and the method results facilitate result validation, and navigation. While the results are preliminary, the concepts can be expanded through the use of other accident datasets or used as basis for UAS accident surveys.
Carlos Paradis↗
Deploying a Route Optimization EFB Application for Commercial Airline Operational Trials
The Traffic Aware Planner (TAP), developed for NASA Langley Research Center to support the Traffic Aware Strategic Aircrew Requests (TASAR) project, is a flight-efficiency software application developed for an Electronic Flight Bag (EFB). Tested in two flight trials and planned for operational testing by two commercial airlines, TAP is a real-time trajectory optimization application that leverages connectivity with onboard avionics and broadband Internet sources to compute and recommend route modifications to flight crews to improve fuel and time performance. The application utilizes a wide range of data, including Automatic Dependent Surveillance Broadcast (ADS-B) traffic, Flight Management System (FMS) guidance and intent, on-board sensors, published winds and weather, and Special Use Airspace (SUA) schedules. This paper discusses the challenges of developing and deploying TAP to various EFB platforms, our solutions to some of these challenges, and lessons learned, to assist commercial software developers and hardware manufacturers in their efforts to implement and extend TAP functionality in their environments. EFB applications (such as TAP) typically access avionics data via an ARINC 834 Simple Text Avionics Protocol (STAP) server hosted by an Aircraft Interface Device (AID) or other installed hardware. While the protocol is standardized, the data sources, content, and transmission rates can vary from aircraft to aircraft. Additionally, the method of communicating with the AID may vary depending on EFB hardware and/or the availability of onboard networking services, such as Ethernet, WIFI, Bluetooth, or other mechanisms. EFBs with portable and installed components can be implemented using a variety of operating systems, and cockpits are increasingly incorporating tablet-based technologies, further expanding the number of platforms the application may need to support. Supporting multiple EFB platforms, AIDs, avionics datasets, and user interfaces presents a challenge for software developers and the management of their code baselines. Maintaining multiple baselines to support all deployment targets can be extremely cumbersome and expensive. Certification also needs to be considered when developing the application. Regardless of whether the software is itself destined to be certified, data requirements in support of the application and user interface elements may introduce certification requirements for EFB manufacturers and the airlines. The example of TAP, the challenges faced, solutions implemented, and lessons learned will give EFB application and hardware developers insight into future potential requirements in deploying TAP or similar flight-deck EFB applications.
Roscoe, David A.↗
Gap Analysis of UAS Manuals and Hazards
Emerging aviation includes the use of small Unmanned Aerial Systems (UAS) in novel operations. The manufacture and operation of these small UAS are not as regulated as today’s commercial operation, and their widespread use introduces new risks and hazards to the general public. Today, there are case-by-case approvals for sUAS operations, particularly for emergency response operations in which the potential benefits to use of sUAS is perceived to outweigh potential risks. We analyze operational approvals, procedures, and concepts of operation to identify and categorize the risks and hazards that applicants and approvers are already considering, and also identify barriers and mitigations that the operators have already put in place. This analysis may help lead to routine checklists that standardize safety analysis and lead to more routine operations.
grounded theory↗
xTM - ATM Coordination - Knowledge Elicitation Results: xTM Operational Domain
Crown Consulting Inc. has been tasked by NASA to elicit information from operators, vehicle manufacturers, and service suppliers on the expected xTM-ATC coordination. For this presentation, first, an introduction for the task and the process is discussed. The second part of the presentation will go through the results which are broken up into the participant company types that we interviewed to elicit feedback on the issues / barriers associated with the introduction of new vehicles and their system (called xTM) into the National Airspace System. The company types are HAPS (Balloons/HALE), sUAS, Large UAS, UAM, Supersonics, and Supporting Technology Providers.
xTM-ATM coordination↗