← Back to NASA Technology Projects

Cloud FMS

Completed TRL 3 (started at 3, targeting 6)

Description

We propose to build a Cloud-Based Flight Management System (FMS), whereby safety-critical functions residing on the flight deck are separated from non-safety-critical functions that reside in a cloud-based environment on the ground. This bifurcation of an FMS will open new markets and address use cases such as Urban Air Mobility. An actual network-enabled and modular commercially available FMS will be reconfigured for this project and tested in a simulation and used in flight to assess its ability. Therefore, this project will build an actual example of a Cloud FMS. This proposal follows on a Phase I project in which an approximation of an FMS was used to demonstrate feasibility. Once configured, functions can be added to the Cloud FMS to further enhance NAS safety and improve capacity through computations that are heretofore infeasible with the limited resources of a flight-deck-based FMS. This product will enable Trajectory-Based Operations by sharing aircraft state to a secure cloud environment, enabling accurate trajectory prediction. Additional computations such as wake vortex estimation and ground noise footprint are feasible with Cloud FMS but infeasible with a traditional FMS. UAM and AAM markets will benefit from enhanced (but secure) FMS connectivity. Airline operations centers can improve operating efficiency by incorporating real-time FMS data into its decision making. The implications for NAS operations, new entrants, safety, and capacity of a Cloud FMS is of interest to the NASA ATM-X program, the UTM program, the AAM program, Upper-E investigations, and planning around commercial space launches. We also propose investigating the certification, cybersecurity, and safety aspects of this concept through theoretical computations, fast-time simulation, and flight testing the Cloud FMS concept. Two potential commercial products will emerge, as well as a plethora of future research recommendations and spin-off product ideas. Over the life-cycle of a Flight Management System (FMS), software updates are rolled-out infrequently, as each iteration invokes a costly validation and verification processes. Since software changes are so expensive, major modifications are minimized. Pilots end up flying the same system, decade after decade. To reduce the overall life-cycle costs of FMS while enabling more user-centric experiences, this proposal is to build a Cloud-based FMS example, whereby safety-critical functions reside on the flight deck and are separated from non-safety-critical functions residing in a cloud environment. This bifurcation of functions will enable new markets and address new use cases relying on both airborne and ground-based operator configurations.  For example, this product will enable robust Trajectory-Based Operations by sharing aircraft state in a secure cloud environment.  Additional computations such as wake vortex estimation and ground noise footprint are possible with Cloud FMS but infeasible otherwise, and new entrants will benefit from enhanced FMS connectivity.  Objective 1: Develop a Modular Bifurcated Commercial and UAM FMS Architecture This objective represents the initial steps to remove functionality from the airborne FMS and host it in a cloud-based environment (and potentially use a server/services-based FMS with reduced functionality on the airborne side). The idea is that the architecture should be the same no matter how things are configured or where each of the pieces are hosted.   Objective 2: Study Additional Applications of a Cloud FMS Useful for Diverse NAS Operations To support increasingly diverse NAS operations, two key elements must be addressed: an increase in the capacity of the airspace system, and a method for handing the variance of performance introduced by a plethora of new vehicle types. In this objective we will study the ways in which the cloud-based portion of the bifurcated FMS can help with both of these overarching goals.   Objective 3: Validate the Architecture The objective is to validate the architecture with one or more live flight tests enhanced through ground-based simulations.   Deliverables: Besides quarterly reports and a final report, deliverables include the simulation bench test data and aircraft test data, the Cloud FMS architecture, insights into certification, cybersecurity, and safety when Cloud FMS is deployed.

Benefits

Potential NASA applications include expanding FMS functionality to realize advanced air traffic management algorithms such as robust Trajectory Based Operations. Cloud FMS will provide new ways of managing traffic, thereby allowing novel ATM algorithms unimaginable today, such as time-varying wake vortex spacing, accurate “ghosting” of aircraft from one route to another, real-time noise footprint analysis in the absence of sensor data, and more.  These applications are of interest to ATM-X, UTM, UAM/AAM, “Upper E,” and concept development. This proposed project will produce two viable commercial implementations of the Cloud FMS concept, one targeted for air carriers and the other targeted for the UAM market.  Air carriers can reduce life-cycle costs of FMS and enhance the user experience.  UAM Operators can ensure that the latest version of FMS is installed on all aircraft—assuring a consistent similar-equipped environment.

Details

Technology areaAir Traffic Management and Range Tracking Systems
ProgramSmall Business Innovation Research/Small Business Tech Transfer (SBIR/STTR)
Lead organizationLangley Research Center, Hampton, VA
Start date2021-07-21
End date2025-03-31

Project contacts

Listed on TechPort itself — the most direct way to ask about this specific project.

How to get involved

This is early/mid-stage (TRL 3) — the most realistic path in is NASA SBIR/STTR, which funds small businesses and research institutions to develop technology aligned with NASA's needs (equity-free, phased funding). Check whether a current SBIR/STTR solicitation topic overlaps with this project's technology area, or contact the project directly (above) to ask.

None of these are guaranteed paths for this specific project — TechPort itself doesn't have an "apply" button. Reaching out to the contact(s) above with a specific question is usually the fastest way to find out what's actually open.