Avionics Checklist Cross-Checking System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Aircraft checklists often lead to user errors due to unintentional omissions or tasks being performed out of order, increasing cognitive workload, time, and accident risk.

Innovation Solution

A system for automatic cross-checking of avionics electronic checklists that monitors user inputs and sensor data to detect errors, displays error messages, and allows users to correct or override these errors through a graphical user interface, ensuring tasks are performed correctly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users manually perform checklist tasks without automated monitoring, then device complexity is reduced, but user errors increase due to omissions or incorrect task sequencing

Engineering Contradiction:
Improvechecklist task accuracyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system continuously monitors user inputs and automatically compares them against the required checklist sequence, providing real-time feedback through error messages when deviations are detected. This closed-loop feedback mechanism ensures task accuracy without requiring complex manual verification procedures.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The checklist system automatically monitors and validates user actions without requiring a second person or complex external verification. The system serves itself by autonomously detecting errors and guiding users back to the correct procedure, reducing the need for additional monitoring resources.

Inventive Principle:
Principle #25Self-service

2Reliability

If the system provides continuous error monitoring and correction guidance, then user errors are reduced, but cognitive workload increases due to additional system demands on the user

Engineering Contradiction:
Improvetask completion accuracyVSAvoidcognitive workload
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system acts as an intermediary between the checklist procedure and the user, automatically interpreting user actions and comparing them against required steps. This mediator function reduces cognitive workload by handling the complex comparison and error detection logic, presenting users with simple guidance rather than requiring them to mentally track multiple checklist parameters simultaneously.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If the system implements automated error detection and correction, then accident risk is reduced, but time to complete checklists increases due to error handling interactions

Engineering Contradiction:
Improvesafety assuranceVSAvoidchecklist completion time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system pre-defines all valid task sequences and potential error conditions before operation. By having the correct procedure and error responses pre-programmed, the system can quickly compare user actions against predetermined criteria and provide immediate correction guidance, minimizing the time added by error detection and correction interactions.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11535393B2Methods and systems for automatic cross-checking of electronic checklists
Publication Date: 2022.12.27 HONEYWELL INTERNATIONAL INC
  • US11535393B2 patent drawing
  • US11535393B2 patent drawing
  • US11535393B2 patent drawing

AI summary

Disclosed are methods, systems, and non-transitory computer-readable medium for automatic cross-checking of an electronic checklist. One method may include: receiving a first user and/or system input associated with a graphical user interface (GUI) of the electronic checklist; determining whether the first user and/or system input triggers an error; in response to determining that the first user and/or system input triggers the error, displaying an error message on the GUI; receiving a second user and/or system input; determining whether the second user and/or system input resolves the error; and in response to determining the second user and/or system input resolves the error, removing the error message from the GUI.