EP3992947A1 - Système et procédé de dégagement vertical pour une remise des gaz après une panne moteur - Google Patents

Système et procédé de dégagement vertical pour une remise des gaz après une panne moteur Download PDF

Info

Publication number
EP3992947A1
EP3992947A1 EP21204044.8A EP21204044A EP3992947A1 EP 3992947 A1 EP3992947 A1 EP 3992947A1 EP 21204044 A EP21204044 A EP 21204044A EP 3992947 A1 EP3992947 A1 EP 3992947A1
Authority
EP
European Patent Office
Prior art keywords
aircraft
obstacle
status
point
peogap
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP21204044.8A
Other languages
German (de)
English (en)
Inventor
Jaibir SINGH
Shankar Sadasivam
Harishin HS
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Rockwell Collins Inc
Original Assignee
Rockwell Collins Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US17/317,146 external-priority patent/US11822352B2/en
Application filed by Rockwell Collins Inc filed Critical Rockwell Collins Inc
Publication of EP3992947A1 publication Critical patent/EP3992947A1/fr
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
    • G08G5/0047—Navigation or guidance aids for a single aircraft
    • G08G5/0056—Navigation or guidance aids for a single aircraft in an emergency situation, e.g. hijacking
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
    • G08G5/0017—Arrangements for implementing traffic-related aircraft activities, e.g. arrangements for generating, displaying, acquiring or managing traffic information
    • G08G5/0021—Arrangements for implementing traffic-related aircraft activities, e.g. arrangements for generating, displaying, acquiring or managing traffic information located in the aircraft
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
    • G08G5/0073—Surveillance aids
    • G08G5/0086—Surveillance aids for monitoring terrain
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
    • G08G5/0047—Navigation or guidance aids for a single aircraft
    • G08G5/0065—Navigation or guidance aids for a single aircraft for taking-off

Definitions

  • a go around (GA) or missed approach (MA) maneuver may be challenging as pilots may infrequently fly and practice these maneuvers.
  • GA go around
  • MA missed approach
  • a GA requires a power addition, a transition from a descent to a climb, and a level off at lower than normal altitude.
  • ATC air traffic control
  • the pilot is required to fly either a published missed approach procedure or as advised by ATC.
  • each aircraft is certified to be capable of safely flying the published missed approach procedure. Should the aircraft be directed to execute the GA below the published missed approach altitude, there may be questions in the minds of the pilots whether required obstacle clearance (ROC) may be met.
  • ROC obstacle clearance
  • Missed approach procedures may be generally divided into initial, intermediate and final phases.
  • Statutory minimum obstacle clearance requirements begin in the intermediate phase with a 30-meter (98 feet) clearance requirement.
  • the obstacle clearance requirement becomes 50 meters (164 feet).
  • the nominal climb gradient of a missed approach vertical path is 2.5%.
  • compliance with the published missed approach may not be achievable when operating at or near the maximum certificated weight, at high altitudes, with high temperatures and an EO condition.
  • a system onboard an aircraft for engine out (EO) go around (GA) obstacle clearance may comprise a GA selection monitor configured for sensing a pilot section of a GA and an aircraft state monitor configured for monitoring an aircraft state.
  • the system may also include an engine status monitor configured to monitor an engine operating status or an EO status of an engine coupled with the aircraft and a flight deck display available to a pilot.
  • the system may include a controller operatively coupled with each of the GA selection monitor, the aircraft state monitor, the engine status monitor, and the flight deck display and a tangible, non-transitory memory configured to communicate with the controller, the tangible, non-transitory memory including a performance database (DB), a navigation DB, and a terrain DB, the tangible, non-transitory memory having instructions stored therein that, in response to execution by the controller, cause the controller to carry out each function of the system.
  • DB performance database
  • navigation DB navigation DB
  • terrain DB terrain DB
  • the system may function to retrieve, from the navigation DB, a published approach flown by the aircraft, the published approach including a published missed approach point (MAPt), a MAPt altitude mean sea level (MSL), and a published missed approach procedure (MAP) and receive, from one of: the GA selection monitor or the aircraft state monitor, a GA status of the aircraft.
  • the system may also receive, from the engine status monitor, the EO status of the engine and retrieve, from the aircraft state monitor, 1) a GA altitude MSL of the aircraft at the GA status, the GA altitude defined as being below the MAPt altitude and 2) a GA point associated with the GA status.
  • the system may further retrieve, from the terrain DB, an obstacle within an area bound by the MAP and retrieve, from the performance DB, an aircraft performance data associated with the aircraft including a takeoff safety (V2) speed of the aircraft, at the GA status.
  • V2 takeoff safety
  • the system may generate a pseudo engine out go around procedure (PEOGAP) for the aircraft based on the aircraft performance data at the V2 speed, the PEOGAP including a first vertical path from the GA point at the GA altitude to a first obstacle clearance point, the first obstacle clearance point a first height MSL of a first obstacle of the obstacle plus a fixed clearance plus a safety margin, a second vertical path from the first obstacle clearance point to a second obstacle clearance point, the second obstacle clearance point a second height MSL of a second obstacle of the obstacle plus the fixed clearance plus the safety margin, and a third vertical path from the second obstacle clearance point to an anticipation point, the anticipation point having an anticipation altitude which intersects a vertical path within a final portion of the published MAP.
  • the system may then display the PEOGAP to the pilot on the flight deck display.
  • An additional embodiment of the inventive concepts disclosed herein may include a method for engine out (EO) go around (GA) obstacle clearance.
  • the method may include retrieving, from a navigation database (DB), a published approach flown by an aircraft, the published approach including a published missed approach point (MAPt), a MAPt altitude mean sea level (MSL), and a published missed approach procedure (MAP), and receiving, from one of: a GA selection monitor or an aircraft state monitor, a GA status of the aircraft.
  • DB navigation database
  • MAPt published missed approach point
  • MSL mean sea level
  • MAP published missed approach procedure
  • the method may also include receiving, from an engine status monitor, an EO status of an engine coupled with the aircraft and retrieving, from the aircraft state monitor, 1) a GA altitude MSL of the aircraft at the GA status, the GA altitude defined as being below the MAPt altitude and 2) a GA point associated with the GA status.
  • the method may further include retrieving, from a terrain DB, an obstacle within an area bound by the MAP and retrieving, from a performance DB, an aircraft performance data associated with the aircraft including a takeoff safety (V2) speed of the aircraft, at the GA status.
  • the method may include generating a pseudo engine out go around procedure (PEOGAP) for the aircraft based on the aircraft performance data at the V2 speed, the PEOGAP including, a first vertical path from the GA point at the GA altitude to a first obstacle clearance point, the first obstacle clearance point having a first height MSL of a first obstacle of the obstacle plus a fixed clearance plus a safety margin, a second vertical path from the first obstacle clearance point to a second obstacle clearance point, the second obstacle clearance point having a second height MSL of a second obstacle of the obstacle plus the fixed clearance plus the safety margin, and a third vertical path from the second obstacle clearance point to an anticipation point, the anticipation point having an anticipation altitude which intersects a vertical path within a final portion of the published MAP.
  • the method
  • inventive concepts are not limited in their application to the details of construction and the arrangement of the components or steps or methodologies set forth in the following description or illustrated in the drawings.
  • inventive concepts disclosed herein may be practiced without these specific details.
  • well-known features may not be described in detail to avoid unnecessarily complicating the instant disclosure.
  • inventive concepts disclosed herein are capable of other embodiments or of being practiced or carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein is for the purpose of description and should not be regarded as limiting.
  • a letter following a reference numeral is intended to reference an embodiment of the feature or element that may be similar, but not necessarily identical, to a previously described element or feature bearing the same reference numeral (e.g., 1, 1a, 1b).
  • reference numeral e.g. 1, 1a, 1b
  • Such shorthand notations are used for purposes of convenience only, and should not be construed to limit the inventive concepts disclosed herein in any way unless expressly stated to the contrary.
  • approximately 50 may refer to a range of values including plus or minus twenty percent (20%) of the listed value. For example, approximately 50 would equal a range of +/- 20 % of 50 which may include a range from 40 to 60.
  • any reference to "one embodiment,” or “some embodiments” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the inventive concepts disclosed herein.
  • the appearances of the phrase “in some embodiments” in various places in the specification are not necessarily all referring to the same embodiment, and embodiments of the inventive concepts disclosed may include one or more of the features expressly described or inherently present herein, or any combination of sub-combination of two or more such features, along with any other features which may not necessarily be expressly described or inherently present in the instant disclosure.
  • embodiments of the inventive concepts disclosed herein are directed to a system and method onboard an aircraft generates pilot awareness of obstacle clearance during an engine out (EO) go around (GA) situation.
  • the system herein receives inputs from either a pilot selection or aircraft state change indicating a GA below a published missed approach altitude and also receives an input from an engine status monitor indicating an EO situation.
  • the systems herein generate a pseudo engine out go around procedure (PEOGAP) which maintains a minimum separation from all obstacles within an area bound by the published missed approach.
  • PEOGAP pseudo engine out go around procedure
  • FIG 1 A first figure.
  • FIG. 1 a diagram of a system for engine out (EO) go around (GA) obstacle clearance 100 in accordance with an embodiment of the inventive concepts disclosed herein is shown.
  • the system for EO GA obstacle clearance 100 may be incorporated onboard an aircraft to enable system function without an external communication requirement or reception of an external signal.
  • the system for EO GA obstacle clearance 100 may provide function to a manned aircraft as well as an unmanned aircraft.
  • a manned aircraft may be the focus however the inventive concepts disclosed herein may directly apply to an autonomous unmanned aircraft system (UAS) as well.
  • UAS autonomous unmanned aircraft system
  • the system for EO GA obstacle clearance 100 may enable an aircraft during a GA maneuver to fly a lower vertical profile than attempting to rejoin a published missed approach procedure (MAP) vertical profile and safely maintaining a climb gradient in the event of engine failure during the GA. Also, the system may enable safety of the aircraft by flying a lower climb gradient in the event where adherence to a published MAP climb gradient is difficult. This may be due to initiation of GA below a published missed approach point (MAPt) due to various reasons such as canceling a landing clearance, gusting wind or a safety issue with the runway (e.g., men and equipment on the runway, aircraft crossing runway, etc.)
  • the system for EO GA obstacle clearance 100 may improve safety operations at airports and better traffic management due to predictable vertical profiles.
  • the system may allow predictable spacing between aircraft over parallel runways during simultaneous arrival and departure operations and enable a greater margin of safety at airports by avoiding chances of runway incursion and runway excursion due to continuing a landing during an unstabilized approach.
  • a missed approach may be defined as an aircraft executing a published missed approach procedure (MAP) from a published missed approach point (MAPt) at the published missed approach altitude.
  • a GA may be defined as a rejected landing where the aircraft discontinues the landing attempt at an altitude below the published missed approach altitude.
  • a GA may be anywhere below the published missed approach altitude including a few feet below the published missed approach altitude to a few feet above the runway.
  • the system for EO GA obstacle clearance 100 may include a GA selection monitor 130 configured for sensing a pilot section of a GA.
  • the system for EO GA obstacle clearance 100 may declare a GA status should the pilot select a thrust lever sensor by advancing the thrust levers, a GA push button sensor by the pilot actually pressing a GA button, a takeoff go around (TOGA) sensor incorporated within a throttle control, and a flight management system (FMS) interface incorporated to interact with the FMS when the FMS senses a GA.
  • a GA selection monitor 130 configured for sensing a pilot section of a GA.
  • the system for EO GA obstacle clearance 100 may declare a GA status should the pilot select a thrust lever sensor by advancing the thrust levers, a GA push button sensor by the pilot actually pressing a GA button, a takeoff go around (TOGA) sensor incorporated within a throttle control, and a flight management system (FMS) interface incorporated to interact with the FMS when the FMS senses a GA.
  • TOGA takeoff go
  • one specific aircraft may be fitted with a GA button on each of the throttles.
  • the pilot selection of this GA button may be one trigger for the system for EO GA obstacle clearance 100 to declare a GA status.
  • some aircraft may enter a TOGA mode during an approach phase when the thrust levers are advanced to a specific detent.
  • the system for EO GA obstacle clearance 100 may declare the GA status when the TOGA mode is enabled on the aircraft.
  • the system for EO GA obstacle clearance 100 may include an aircraft state monitor 132 configured for monitoring at least one aircraft state.
  • inputs to the aircraft state monitor 132 may include the aircraft state of a position via an inertial system or an inertial system updated by a global navigation satellite system (GNSS) or a stand-alone GNSS position input.
  • GNSS global navigation satellite system
  • a pitot static system may provide an altitude MSL, a rate of climb, a rate of descent, and an airspeed.
  • an altitude above ground level may be provided by a radio altimeter while a groundspeed, an attitude, a power level of the at least one engine, and a heading may be provided by traditional attitude sensors and engine indication and crew alerting system (EICAS) interface elements.
  • EICAS engine indication and crew alerting system
  • the system for EO GA obstacle clearance 100 may include an engine status monitor 140 configured to monitor an engine operating status or an EO status of at least one engine coupled with the aircraft.
  • the engine status monitor 140 may be as simple as a binary monitor to sense of the engine is producing power or not.
  • the engine status monitor 140 may further include an engine speed monitor, an engine fuel flow monitor, and an engine condition and monitoring (ECAM) interface.
  • ECAM engine condition and monitoring
  • the system for EO GA obstacle clearance 100 may also include a flight deck display 150 available to a pilot of the aircraft.
  • the flight deck display 150 may further include a multifunction display (MFD), a heads-up display (HUD), and a helmet mounted display (HMD).
  • the flight deck display 150 may further include a vertical situation display indicating a current MSL altitude of the aircraft and a terrain associated with the MAP.
  • the flight deck display 150 may be sited remotely for a remote pilot to monitor the progress of the flight of the aircraft.
  • a datalink 160 may provide a communications link between the aircraft and the remote pilot for the remote pilot may view a remote version of the flight deck display 150 when located distant from the aircraft.
  • the system for EO GA obstacle clearance 100 may include a controller 110 operatively coupled with each of the GA selection monitor 130, the aircraft state monitor 132, the engine status monitor 140, and the flight deck display 150.
  • the controller 110 may be incorporated within the FMS onboard the aircraft as well as within additional controlling elements of the aircraft systems.
  • a mission computer MC
  • FCC flight control computer
  • the system for EO GA obstacle clearance 100 may further include a tangible, non-transitory memory 120 configured to communicate with the controller 110, the tangible, non-transitory memory including a performance takeoff and landing data (TOLD) database (DB) 122, a navigation DB 124 including runway and approach information, and a terrain DB 126.
  • the tangible, non-transitory memory 120 may have instructions stored therein that, in response to execution by the controller, cause the controller to carry out each step of the system for EO GA obstacle clearance 100.
  • the system for EO GA obstacle clearance 100 may further include an autopilot 152, a flight director 154, and an auto throttle 156 incorporated within a manned aircraft or UAS.
  • the pilot may command the autopilot to control the aircraft or the remote operator may enable the autopilot 152, coupled with the flight director 154 and auto throttle 156, to fly the UAS as directed by the controller 110.
  • the datalink 160 may provide function as above with the remote operator but also provide a communications link to an air traffic control (ATC) to communicate the EO status and GA status to ATC.
  • ATC air traffic control
  • the datalink 160 may function within a controller pilot data link communication (CPDLC) onboard the aircraft and auto communicate the status to ATC.
  • CPDLC controller pilot data link communication
  • the controller 110 may function to retrieve, from the navigation DB 124, a published approach currently being flown by the aircraft, the published approach including the MAPt, a MAPt altitude mean sea level (MSL), and a published MAP. As the pilot may select an approach procedure from the navigation DB 124, the controller 110 may also receive this information in preparation for later function.
  • a published approach currently being flown by the aircraft including the MAPt, a MAPt altitude mean sea level (MSL), and a published MAP.
  • MSL mean sea level
  • the controller 110 may also receive this information in preparation for later function.
  • the published approach procedure may include each of these variables including the published MAP and an area bounded by the MAP 308 ( FIG. 3 ).
  • the MAP may include an initial segment where the aircraft transitions from a descent to a climb, an intermediate segment where the aircraft climbs to remain clear of obstacles, and a final segment where the aircraft is above all obstacles within the area bounded by the MAP 308.
  • the system for EO GA obstacle clearance 100 may provide function during each of these segments enabling pilot awareness of a minimum fly safe climb gradient (MFSCG) associated with the climb out from GA execution to reaching a safe altitude along the published MAP.
  • MFSCG minimum fly safe climb gradient
  • a Logic Flow Diagram 200 may include an EOGA vertical path generator 210.
  • the EOGA vertical path generator may include a speed generator 212, a climb gradients generator 214, an EO vertical path generator 216, and a flight director and auto thrust command generator 218.
  • the performance DB 122, the navigation DB 124 and the terrain DB 126 may be available to the controller 110 for access to the stored data.
  • the performance DB 122 may include each performance aspect of the aircraft. Such exemplary performance characteristics may be stored for the aircraft at specific gross weights, density altitudes, and temperatures. Exemplary characteristics may include a rate of climb with one EO, a takeoff safety (V2) speed at various weights, and rotation rates at a specific vertical speed.
  • V2 takeoff safety
  • the navigation DB 124 may include a plurality of traditional variables included in a DB of flight environments. Specifically, the navigation DB 124 may include the current published instrument approach procedure being flown by the aircraft, the published MAP, the MAPt, the area bounded by the MAP 308, and the MAPt altitude.
  • the terrain DB 126 may include traditional information concerning terrain, obstacles, and threats to aircraft. Of interest here, the controller 110 may retrieve terrain data from the terrain DB 126 bounded by the area of the MAP 308.
  • a TOGA engagement 230 may function to notify the controller 110 of the EO status and the GA status.
  • a manual rotation 232 may function to notify the controller 110 of the EO status and the GA status.
  • a GA initiation 234 may function to notify the controller 110 of the EO status and the GA status.
  • the system for EO GA obstacle clearance 100 may produce a display symbology 250, an autopilot command 252, a flight director command 254, an autothrottle command 256, and a transmission external 260 to the aircraft.
  • the vertical diagram 300 may indicate a published MAPt 390 where an aircraft not in sight of the runway environment must execute a published MAP.
  • the aircraft may be intending to land on a runway 396 having a runway elevation MSL 382.
  • a standard MA climb gradient 394 of 2.5 % may be a statutory climb gradient for an aircraft to fly to remain clear of any obstacle within the MAP.
  • an unknown GA climb gradient 394 may cause uncertainty and lead to further safety of flight issues (e.g., low speed, stall, heading control loss).
  • the GA below the MAPt altitude and an EO status as well may lead to further safety of flight challenges.
  • the vertical diagram 300 may indicate an obstacle 1 302 and an obstacle 2 304 above which the system for EO GA obstacle clearance 100 may direct the aircraft.
  • a final MAP elevation 306 may indicate an altitude of the terrain within the final segment of the published MAP.
  • the controller may function to generate a pseudo engine out go around procedure (PEOGAP) 310 which maintains clearance from each obstacle within the area bounded by the MAP 308.
  • PEOGAP pseudo engine out go around procedure
  • the obstacle 1 302 and obstacle 2 304 may be exemplary obstacles within the area bounded by the MAP 308 wherein additional obstacles may be present and therefore, included within the PEOGAP 310.
  • the PEOGAP 310 may comprise a plurality of segments and begin at a GA point A 320 where the controller 110 senses the GA and EO status, it may flow through a point B 322 above the obstacle 1 302, and a point C 324 above the obstacle 2 304, to an anticipation point (Ap) 326 where the PEOGAP 310 may vertically intersect a published vertical path of the MAP.
  • Each of the points A through Ap may have a position and an associated altitude as determined by the controller 110 either before the GA status or at the time of the GA status.
  • point A 320 may have a GA point A position 340 and a GA point A altitude MSL 360.
  • the point B 322 may include a point B position 342 and a point B altitude MSL 362
  • the point C 324 may include a point C position 344 and a point C altitude MSL 364
  • the Ap 326 may include an Ap position 346 and an Ap altitude 366.
  • all altitudes are reference to sea level 380 in feet MSL.
  • the controller 110 may apply a fixed clearance plus a safety margin to each obstacle to reach the point B and point C altitudes to ensure adequate clearance between the aircraft and each obstacle.
  • the controller 110 may apply the fixed clearance of approximately 35 feet and the safety margin of approximately ten percent (10%) of the height MSL of each obstacle as retrieved from the terrain DB 126.
  • the controller 110 may function to determine a horizontal distance between each point including a distance A-B 350, a distance B-C 352, and a distance C-Ap 354. Also, an altitude difference between each point using simple math.
  • the controller 110 may determine each angle or the PEOGAP 310 from point to point.
  • a plurality of segments may be used in the PEOGAP 310 however, three segments may be exemplary to indicate controller 110 function.
  • a theta 2 ( ⁇ 2) 330 may describe a first climb gradient from the GA point A 320 to the point B 322.
  • a theta 1 ( ⁇ 1) 332 may describe a second segment climb gradient from the point B 322 to the point C 324 and a theta 3 ( ⁇ 3) 334 may indicate the controller 110 calculated climb gradient between the point C 334 and Ap 336.
  • a geometry example 400 may indicate a first segment of the PEOGAP 310.
  • the MAPt altitude MSL 490 is indicated but may not be relevant since the inventive concepts disclosed herein center on altitudes below the MAPt altitude 490 ft MSL.
  • an exemplary field elevation may be 600 feet MSL and the GA is executed at 200 ft AGL (800 ft MSL).
  • An exemplary height of point B 322 may be 3300 ft MSL (obstacle 1 height (e.g., 2965)+ 35 ft + 10%) leading to a climb height from the GA point A 320 to the point B 322 of 1500 ft.
  • the controller 110 may then determine the ⁇ 2 330 of 5.7 degrees requiring an exemplary climb rate of 750 FMP which is understandable to the pilot and FCC.
  • the controller 110 may receive, from either the GA selection monitor 130 or the aircraft state monitor 132, a GA status of the aircraft. In declaring the GA status, the controller 110 may function to create the PEOGAP 310 for the aircraft to safely fly the EO GA path. In additional embodiments, the controller 110 may continuously calculate the PEOGAP 310 in anticipation of the GA status and EO status and store the PEOGAP within the memory 120 before the reception of the GA and EO status of the aircraft.
  • the controller may receive, from the engine status monitor 140, the EO status of one of the aircraft engines and retrieve, from the aircraft state monitor 140, 1) a GA altitude 360 MSL of the aircraft at the GA status.
  • the GA altitude 360 may be defined as being below the MAPt altitude 490.
  • the controller 110 may also retrieve 2) a GA point A 320 associated with the GA status.
  • the controller 110 may retrieve, from the terrain DB 126, at least one obstacle within an area bound by the MAP 308.
  • each obstacle within the area 308 bound by the MAP 392 may be a threat to the aircraft climbing out on a single engine or a loss of an engine.
  • the controller 110 may retrieve, from the performance DB 122, an aircraft performance data associated with the aircraft including a takeoff safety (V2) speed of the aircraft, at the time of the GA status.
  • V2 takeoff safety
  • the controller 110 may generate the PEOGAP 310 for the aircraft based on the aircraft performance data at the V2 speed.
  • the PEOGAP 310 may include a first vertical path from the GA point A 320 at the GA altitude 360 to a first obstacle clearance point B 322, the first obstacle clearance point a first height MSL 362 of a first obstacle 302 plus the fixed clearance plus the safety margin.
  • the PEOGAP 310 may also include a second vertical path from the first obstacle clearance point B 322 to the second obstacle clearance point C 324, the second obstacle clearance point 324 a second height MSL 364 of a second obstacle 304 plus the fixed clearance plus the safety margin.
  • the PEOGAP 310 may further include a third vertical path from the second obstacle clearance point C 324 to the anticipation point 326, the Ap 326 having an anticipation altitude 366 which intersects a vertical path within a final portion of the published MAP 392.
  • the controller 110 may function to display the PEOGAP 310 to the pilot on the flight deck display 150.
  • the flight deck display may be located remotely from the aircraft where the pilot may remotely operate the aircraft.
  • the autopilot 152 may function to command the aircraft to fly the PEOGAP 310 or a flight path above the PEOGAP 310 to the Ap 326.
  • the PEOGAP 310 may be generated based on the V2 speed climb performance.
  • the aircraft may maintain minimum V2 speed until reaching the Ap 326 where, clear of all obstacles and within the final segment of the published MAP 392, the aircraft may change speed to an engine out speed, a GA speed, or engine out climb speed.
  • a multi-function display (MFD) diagram 500 may indicate one exemplary implementation of a pilot display of the PEOGAP 310.
  • the controller 110 may present an Ap symbology 526 associated with a Red Bar 536 indicating a Negative Performance, a Yellow Bar 546 indicating Neutral Performance, and a Green Bar 556 indicating a Positive Performance relative to the PEOGAP 310.
  • the controller 110 may present the red bar 536 to indicate to the pilot an increase in performance is required to remain clear of the upcoming obstacle.
  • a size of the colored status bar may further indicate a magnitude of displacement from the PEOGAP 310.
  • a vertical size of the colored status bar may include a short vertical size indicating positive performance and a long vertical size indicated negative performance, each performance relative to the PEOGAP 310.
  • a short vertical yellow may indicate a slight negative deviation or a slight negative performance while a long vertical yellow may indicate a greater negative deviation.
  • a flight director 154 with command bars 566 may also function within the scope of the incentive concepts herein to display performance data to the pilot.
  • a negative performance may be indicated by command bars 566 above an aircraft diamond symbol while a positive performance may be indicated by the command bars 566 below the aircraft diamond symbol.
  • An MFD trend arrow display 600 may indicate a trend arrow 626 with which some pilots may be familiar.
  • a short trend arrow 626 may indicate a lesser performance while a negative trend arrow 628 pointing below the altitude field (e.g., 710 ft MSL) may indicate a negative performance.
  • a long positive trend arrow 626 may be a graphical representation of the next point along the PEOGAP 310, and a trend arrow indicating a climb performance relative to the PEOGAP 310.
  • a guidance Ap circle 636 displayed in association with a guidance bar 646 may indicate to the pilot an angular representation of where the pilot may need to place a flight path marker 602 to achieve the desired flight path and intersect the Ap 326.
  • a vertical situation display (VSD) 700 may be familiar to some pilots indicating a terrain 710 as well as an aircraft symbol 720 relative to the PEOGAP 310 display.
  • a traffic collision avoidance system (TCAS) display may function to display positive, neutral, and negative trend data including colors red, yellow, and green as pilots may be familiar with a vertical clearance requirement associated with the TCAS display.
  • TCAS traffic collision avoidance system
  • a method flow 800 may include, at a step 802, retrieving, from the navigation database (DB), the published approach flown by the aircraft, the published approach including the published missed approach point (MAPt), the MAPt altitude mean sea level (MSL), and the published missed approach procedure (MAP), and, at a step 804, receiving, from the GA selection monitor or an aircraft state monitor, the GA status of the aircraft.
  • DB navigation database
  • MAPt published missed approach point
  • MSL mean sea level
  • MAP published missed approach procedure
  • the method may include, at a step 806, receiving, from the engine status monitor, an EO status of the engine coupled with the aircraft, and, at a step 808, retrieving, from the aircraft state monitor, 1) the GA altitude MSL of the aircraft at the GA status, the GA altitude defined as being below the MAPt altitude and 2) the GA point associated with the GA status.
  • the method may include, at a step 810, retrieving, from the terrain DB, an obstacle within the area bound by the MAP, and, at a step 812, retrieving, from the performance DB, the aircraft performance data associated with the aircraft including the takeoff safety (V2) speed of the aircraft, at the GA status.
  • V2 takeoff safety
  • the method may include, at a step 814, generating the pseudo engine out go around procedure (PEOGAP) for the aircraft based on the aircraft performance data at the V2 speed, the PEOGAP including the first vertical path from the GA point at the GA altitude to a first obstacle clearance point, the first obstacle clearance point having a first height MSL of the first obstacle of the at least one obstacle plus a fixed clearance plus a safety margin, the second vertical path from the first obstacle clearance point to the second obstacle clearance point, the second obstacle clearance point having the second height MSL of the second obstacle of the at least one obstacle plus the fixed clearance plus the safety margin; and the third vertical path from the second obstacle clearance point to the Ap, the Ap having an anticipation altitude which intersects the vertical path within the final portion of the published MAP.
  • the method may include, at a step 816, displaying the PEOGAP to the pilot on a flight deck display.
  • embodiments of the inventive concepts disclosed herein may provide a novel solution to establish a minimum climb gradient requirement to remain clear of all obstacles during an EO GA.
  • embodiments of the methods according to the inventive concepts disclosed herein may include one or more of the steps described herein. Further, such steps may be carried out in any desired order and two or more of the steps may be carried out simultaneously with one another. Two or more of the steps disclosed herein may be combined in a single step, and in some embodiments, one or more of the steps may be carried out as two or more sub-steps. Further, other steps or sub-steps may be carried in addition to, or as substitutes to one or more of the steps disclosed herein.
  • inventive concepts disclosed herein are well adapted to carry out the objects and to attain the advantages mentioned herein as well as those inherent in the inventive concepts disclosed herein. While presently preferred embodiments of the inventive concepts disclosed herein have been described for purposes of this disclosure, it will be understood that numerous changes may be made which will readily suggest themselves to those skilled in the art and which are accomplished within the broad scope and coverage of the inventive concepts disclosed and claimed herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Business, Economics & Management (AREA)
  • Emergency Management (AREA)
  • Traffic Control Systems (AREA)
EP21204044.8A 2020-10-26 2021-10-21 Système et procédé de dégagement vertical pour une remise des gaz après une panne moteur Pending EP3992947A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202041046641 2020-10-26
US17/317,146 US11822352B2 (en) 2020-10-26 2021-05-11 Engine out go around vertical clearance system and method

Publications (1)

Publication Number Publication Date
EP3992947A1 true EP3992947A1 (fr) 2022-05-04

Family

ID=78371877

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21204044.8A Pending EP3992947A1 (fr) 2020-10-26 2021-10-21 Système et procédé de dégagement vertical pour une remise des gaz après une panne moteur

Country Status (1)

Country Link
EP (1) EP3992947A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060253232A1 (en) * 2005-03-10 2006-11-09 Naverus, Inc. Method for implementing required navigational performance procedures
US20090030564A1 (en) * 2007-07-26 2009-01-29 Mark Alan Peterson Method and apparatus for managing instrument missed approaches
US20200168104A1 (en) * 2018-11-27 2020-05-28 Honeywell International Inc. Systems and methods for providing deviation assistance on an integrated flight management display

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060253232A1 (en) * 2005-03-10 2006-11-09 Naverus, Inc. Method for implementing required navigational performance procedures
US20090030564A1 (en) * 2007-07-26 2009-01-29 Mark Alan Peterson Method and apparatus for managing instrument missed approaches
US20200168104A1 (en) * 2018-11-27 2020-05-28 Honeywell International Inc. Systems and methods for providing deviation assistance on an integrated flight management display

Similar Documents

Publication Publication Date Title
US11699351B2 (en) Flight assistant
US9310222B1 (en) Flight assistant with automatic configuration and landing site selection method and apparatus
US11787560B2 (en) Computer-based systems and methods for facilitating aircraft approach
CN105425813B (zh) 用于规划轨道的实时计算、组合任务的方法及用于管理这样的轨道的系统
US8041504B2 (en) Method and system for display of guidance reference for traffic situational awareness
US20070027588A1 (en) Aircraft flight safety device and method which are intended for an aircraft flying in instrument meteorological conditions and which are used independently of instrument flight infrastructure
US7675461B1 (en) System and method for displaying radar-estimated terrain
US6584382B2 (en) Intuitive vehicle and machine control
US8049644B1 (en) Method for TAWS depiction on SVS perspective displays
EP2267683A2 (fr) Outil automatisé d'aide à la décision pour inciter un pilote de demander un changement de niveau de vol
US20220189316A1 (en) Unmanned aircraft control using ground control station
EP3627475A1 (fr) Procédés et systèmes de gestion d'énergie d'approche stabilisée
US20210350716A1 (en) Detecting and avoiding conflicts between aircraft
US11320842B2 (en) Systems and methods for optimized cruise vertical path
EP3470791B1 (fr) Procédé et système pour fournir une autocorrélation contextuelle d'objets d'affichage de situation verticale à des objets affichés sur une carte latérale basé sur un schéma de priorité
EP3989205A1 (fr) Système et procédé d'atterrissage d'urgence vtol
US11955013B2 (en) Electronic device and method for assisting in the configuration of an aircraft flight, related computer program
US11822352B2 (en) Engine out go around vertical clearance system and method
US11657721B1 (en) Aircraft with flight assistant
EP3992947A1 (fr) Système et procédé de dégagement vertical pour une remise des gaz après une panne moteur
EP4050585A1 (fr) Procédés et systèmes permettant une modélisation efficace de train d'atterrissage pour la gestion d'énergie
US20240177616A1 (en) System and method for enhancing pilot situational awareness for hybrid approach procedure sets
EP4379698A1 (fr) Système et procédé pour améliorer la perception situationnelle de pilote pour des ensembles de procédures d'approche hybride
Ab Wahid Flight guidance along 3D+ T trajectories and space indexed traffic management
EP3929893A1 (fr) Directeur de vol d'urgence

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20221103

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR