Runway Condition Validation via Aircraft Deceleration Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems fail to provide accurate real-time runway condition validation and reassessment, leading to runway excursion events due to subjective reporting and inaccuracies in runway condition codes, which affect aircraft braking performance and safety.
Innovation Solution
A computer-implemented method and system that identifies runway segments, receives and compares reported and actual deceleration data from recently landed aircraft to validate and reassess runway condition codes and braking actions, transmitting validated data to approaching aircraft and airport controllers for optimal braking pressure application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If subjective runway condition reporting is used, then reporting simplicity is improved, but measurement precision deteriorates
Solution Approach 1:
The patent replaces the subjective human judgment system with an automated electronic system that collects objective deceleration data from aircraft sensors. The system processes actual deceleration measurements and compares them against expected values to generate validated runway condition codes, eliminating reliance on pilot subjectivity while maintaining ease of data collection through existing aircraft instrumentation.
Solution Approach 2:
The system implements feedback by continuously collecting deceleration data from landing aircraft, comparing actual performance against expected performance based on reported conditions, and using the validation results to confirm or correct runway condition codes. This closed-loop feedback mechanism ensures ongoing accuracy of runway condition information.
2Device complexity
If runway condition code is reported for entire runway, then reporting complexity is reduced, but measurement precision deteriorates
Solution Approach 1:
The patent divides the runway into multiple segments and validates the deceleration profile for each segment individually. By comparing actual deceleration data against expected deceleration for each specific segment, the system can identify localized variations in runway conditions (such as contaminated areas or surface irregularities) that would be averaged out in a whole-runway assessment.
3Measurement precision
If friction measurement equipment is used by airport controller, then objective assessment is improved, but reliability deteriorates due to equipment inaccuracy and condition changes
Solution Approach 1:
The system continuously validates runway condition information by collecting fresh deceleration data from each landing aircraft and comparing it against expected performance. This ongoing validation process detects changes in runway conditions in real-time, allowing the system to update or correct condition codes when contaminants accumulate or conditions deteriorate between manual assessments.
Solution Approach 2:
The system uses the aircraft's own deceleration performance as the measurement tool, eliminating reliance on external friction measurement equipment. Each aircraft serves as its own sensor by providing deceleration data that directly reflects the actual braking conditions on the runway, ensuring continuous and accurate condition assessment without equipment maintenance issues.
4Ease of operation
If PIREP is not mandatory, then pilot workload is reduced, but loss of information increases
Solution Approach 1:
The patent replaces the voluntary pilot reporting system with automated data collection from aircraft sensors. The system directly extracts deceleration profile information from the aircraft's flight data recorder or inertial measurement unit, eliminating the need for pilot input while ensuring complete and accurate data capture for every landing.
Data Source
AI summary
Computer-implemented methods for validating a real-time condition of a landing field using aircraft data. One method comprises identifying a plurality of segments of the runway based on a configurable parameter; receiving input data of at least one of a reported runway condition code and a reported braking action of a recently landed aircraft; receiving actual data of an actual runway deceleration profile from the recently landed aircraft for each identified segment of the runway; creating expected data of an expected runway deceleration profile based on the received input data and the received actual data; comparing the received actual data with the created expected data to validate and/or reassess the input data; and transmitting the validated and/or reassessed data to at least one of other approaching aircraft and an airport controller.


