Aircraft Crew Alert Prioritization by Operational Phase

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current aircraft alert systems display alerts in a static order regardless of their urgency, requiring crew members to manually prioritize based on their evaluation, which can lead to confusion and inefficiency.

Innovation Solution

A system that prioritizes alerts based on the operational phase of the aircraft, assigning dynamic alert levels by considering the current flight phase and operational impact, allowing for automated prioritization of alerts in a graphical user interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If alerts are displayed in the order they are generated with the newest alert at the top, then the display is simple and easy to implement, but the crew cannot quickly identify critical alerts requiring immediate attention

Engineering Contradiction:
Improveease of alert identificationVSAvoidalert prioritization system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system dynamically adjusts alert display order based on contextual factors including operational phase, alert severity, and time sensitivity. Instead of a static generation order, the alert list is continuously reorganized to prioritize alerts that require immediate crew attention, making critical information stand out while maintaining system manageability through automated rules.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the display parameter of alerts from a fixed temporal order to a dynamic order based on multiple parameters including operational phase (e.g., takeoff, cruise, landing), alert category, and time sensitivity. This parameter transformation enables the system to present alerts in the most relevant order for the current operational context.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If a static database with pre-defined alert levels is used, then the system is simple and reliable, but the alert levels do not adapt to different operational contexts and may not accurately reflect current urgency

Engineering Contradiction:
Improvealert level adaptability to operational phaseVSAvoidcontextualization system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary contextualization by determining the current operational phase before assigning alert levels. It proactively adjusts alert priorities based on pre-established operational contexts (e.g., treating certain alerts as higher priority during takeoff or landing phases), ensuring that alert levels are appropriately calibrated for the specific operational situation before the crew needs to respond.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system continuously monitors operational phase changes and uses this feedback to dynamically adjust alert priorities. When the operational phase changes (e.g., transitioning from cruise to approach), the system receives feedback about the new context and automatically re-evaluates and reprioritizes alerts to match the current operational requirements.

Inventive Principle:
Principle #23Feedback

3Productivity

If multiple alerts are displayed separately in the list, then each alert is clearly visible and detailed, but the crew must manually evaluate and prioritize among multiple alerts, increasing time to respond

Engineering Contradiction:
Improvecrew response timeVSAvoidmanual alert evaluation requirement
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system performs self-service by automatically evaluating, contextualizing, and prioritizing alerts without requiring manual intervention from the crew. It independently determines operational phase, assigns appropriate alert levels, and organizes the alert list according to priority rules, freeing the crew to focus solely on responding to alerts rather than evaluating their importance.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12406585B2Prioritizing crew alerts
Publication Date: 2025.09.02 THE BOEING CO
  • US12406585B2 patent drawing
  • US12406585B2 patent drawing
  • US12406585B2 patent drawing

AI summary

The present disclosure provides embodiments that include storing an alert database defining a plurality of alert events for a vehicle where the plurality of alert events indicating deviations from a desired operation of the vehicle, detecting an alert event of one of the plurality of alert events by monitoring an output of a sensor in the vehicle, searching the alert database to identify a crew response for the alert event, identifying a current operational phase of the vehicle, contextualizing, based on the current operational phase, the alert event to assign an alert level to the alert event, and outputting, for display, the alert event.