Aircraft Trajectory Management for Engine Outage Safety
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current aircraft engine outage procedures during take-off are limited, as pilots lack the ability to safely manage trajectories and modify procedures in real-time, with existing systems relying on predefined databases that are not always compatible with varying aeroplane performance levels and weather conditions, leading to potential safety risks and increased workload.
Innovation Solution
A computer-implemented method that receives aeroplane performance levels, flight plans, and weather data to determine safety points and manage Engine Out-SID (EOSID) trajectories, allowing for the creation, selection, and activation of EOSID procedures, even after the point of divergence, and enabling pilots to modify and visualize these trajectories for safe continuation in case of engine failure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If predefined EOSID trajectories are used from navigation databases, then the procedure is automatically proposed, but the pilot cannot modify the procedure in real-time and may be forced to follow incompatible procedures
Solution Approach 1:
The system transforms static predefined trajectories into dynamic, modifiable procedures. The pilot can now adjust trajectory parameters in real-time based on actual aircraft performance and weather conditions, making the procedure adaptive rather than fixed.
Solution Approach 2:
The system allows modification of trajectory parameters such as climb gradient, altitude, and lateral position. The pilot can change these parameters to match current aircraft performance levels and weather conditions, enabling customization of the EOSID procedure.
2Reliability
If EOSID procedures are strictly enforced, then safety is maintained, but the pilot loses flexibility to adapt to varying aircraft performance and weather conditions
Solution Approach 1:
The system incorporates feedback mechanisms where the pilot's modifications are validated against safety criteria. The system provides feedback on whether proposed changes maintain safety requirements while allowing flexibility in trajectory parameters.
Solution Approach 2:
The system enables controlled parameter changes within safety boundaries. The pilot can modify trajectory parameters while the system ensures that safety requirements are maintained, allowing flexibility without compromising reliability.
3Extent of automation
If the point of divergence is used to determine EOSID activation, then the procedure is automatically activated, but the system cannot handle engine outages occurring after the divergence point
Solution Approach 1:
The system maintains continuous monitoring of engine status throughout the entire departure procedure, not just before the divergence point. This continuous monitoring enables automatic activation of EOSID at any stage, ensuring uninterrupted safety coverage.
Solution Approach 2:
The system pre-calculates and prepares EOSID trajectories in advance, storing multiple variant trajectories that can be activated at different stages of the departure procedure, including after the divergence point.
4Adaptability or versatility
If multiple EOSID trajectories are stored in the database, then more options are available, but the database size increases and maintenance becomes more complex
Solution Approach 1:
The system segments the departure procedure into multiple stages and stores corresponding EOSID trajectories for each stage. This segmentation allows selective loading and management of trajectories based on the current phase of flight, reducing overall database complexity.
Solution Approach 2:
The system dynamically selects and loads appropriate EOSID trajectories based on the current aircraft state, weather conditions, and procedure stage. This dynamic approach reduces the need to maintain all possible trajectories in the database simultaneously.
Data Source
AI summary
A method for managing the trajectory of an aircraft implemented by computer comprises the steps consisting of: receiving the aeroplane performance levels, receiving a flight plan, receiving ground relief data, receiving weather data, determining the coordinates of a safety point according to the aeroplane performance levels, the relief data and the weather data, the safety point making it possible to continue the flight according to a predefined SID landing trajectory in case of outage of one or more engines of the aircraft. Developments are described, notably in computation of the spatial coordinates of the safety point, the management of several safety points and/or of EOSID trajectories, the insertion or the activation of an EOSID trajectory including in the absence of engine outage, the management of the Disarm Point flight plan point. System and software aspects are described.