In-Flight and Pre-Flight Detection of Pitot Tube Anomalies

The health and integrity of aircraft sensors and instruments play a critical role in aviation safety. However, inaccurate or false readings from these same sensors/instruments can lead to improper decision-making resulting in serious if not fatal consequences. This proposal offers a research and development (R&D) effort to demonstrate the feasibility of using advanced data analysis techniques to identify failures in pitot tubes resulting from blockage, icing, or moisture. These data analysis techniques will use existing electrical signals of pitot tube sensors that result from measured processes during in-flight conditions and/or induced signals in pre-flight conditions to detect anomalies in the sensor readings. The proposed method for detecting pitot tube anomalies is referred to as the "noise analysis" technique. This technique has been validated and is currently and routinely used by the proposing firm and others for detecting sensing line blockages of pressure transmitters in nuclear power generating stations; a very similar issue to the concern associated with pitot tube blockages. Typically, the output of a sensor that is measuring a process (e.g. air flow) contains two components: a static (DC) component that represents the process parameter, and a dynamic (AC) component. Through the use of the dynamic component of existing electrical signals, the dynamic response of the sensor can be measured in the frequency domain. As the sensor becomes blocked or degraded, changes to the dynamic response can be observed. Specific examples of this are given in the proposal. Another consideration in this proposal is diagnosing pitot tube sensor anomalies in pre-flight conditions. In pre-flight checks, the pitot tubes reside in mild conditions and will not be measuring a turbulent process. As such, a technique is proposed to induce this type of noise on the sensor input and analyze the resultant output using the same noise analysis technique.

The intended end product of a Phase I and Phase II project is the development of hardware and software that can be used for the detection of pitot tube anomalies resulting from blockages either during in-flight or pre-flight conditions. This end product, which would be commercialized by Analysis and Measurement Services in a Phase III effort, could have a large potential use in the commercial, private, and military aircraft industries. For example, the U.S. Air Force could benefit from a commercially available product for this purpose as evidenced by the B-2 bomber crash at Andersen Air Force base in early 2008 due to water contamination in pitot tubes. This crash resulted in an estimated $1.4 billion in property damage. Adapting this technology to the aviation industry, which has never been done, could prove to solve a long standing safety concern associated with aircraft operation.

The intended end product of a Phase I and Phase II project is the development of hardware and software that can be used for the detection of pitot tube anomalies resulting from blockages either during in-flight or pre-flight conditions. The successful completion and commercialization of this project has tremendous potential for responding to current and long-term needs of NASA in the area of instrumentation failure detection, condition monitoring, and autonomous detection of anomalies for airplanes and aerospace vehicles. It would directly serve NASA's research initiatives within the Aviation Safety Program. Adapting this technology to the aviation industry, which has never been done, could prove to solve a long-standing safety concern associated with aircraft operation.

This is early/mid-stage (TRL 4) — 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.