Patent Description:
Modern aircraft navigation displays provide the means to specify and monitor lateral and vertical aircraft profiles using waypoint annotations, and waypoint lists. These display elements not only show spatial locations that will be traversed by an aircraft, but also synthesize crossing constraints or other conditions associated with them.

As a flight progresses, these waypoint lists and waypoint data blocks provide a way for pilots to assess progress relative to an explicitly specified flight plan. When a pilot observes or predicts a discrepancy between aircraft performance and the established plan, the pilot can access a variety of automation and control functions to either modify constraints or manage aircraft trajectory to conform to specified parameters. Unfortunately, many of the functions necessary to adjust these parameters are distributed across the system - imposing workload and introducing the potential for errors of commission and omission when making changes. There is a cost associated with both learnability and training for such UI designs. For example, in current cockpit avionics systems, the flight crew must access important waypoint constraints through a series of menus and dialog windows. Flight Crew can access Vectors, Hold, Cross, and Required Time of Arrival (RTA) dialog windows on a specific waypoint. After constraints are added via one or more of these dialog windows, the flight crew must continually access the dialog windows in the same manner to make changes and/or provide information cues or updates regarding a constraint.

Such systems are known from <CIT> and <CIT>.

Hence, it is desirable to provide systems and methods for setting, editing and accessing status information for a constraint or condition associated with a waypoint or other fix that reduces pilot workload. Furthermore, other desirable features and characteristics of the present invention will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and the foregoing technical field and background.

In aspects of the present disclosure, an aircraft display system for an aircraft according to claim <NUM> and a method of generating a display in an aircraft display system for an aircraft according to claim <NUM> are disclosed.

The present disclosure provides systems and methods including contextually linked direct access to automation functionality. In one example, a constraint or condition can be set for a waypoint/fix by invoking a constraint/condition specific dialog box. An icon is generated including information concerning the set constraint/condition. The icon is tagged to the waypoint/fix. The icon links back to the constraint/condition specific dialog box to allow viewing detailed information and providing quick access to editing the set constraint/condition. Thus, the links invoke dialog boxes relevant to achieve constraints or conditions displayed on navigation displays by means of a single pilot action. In an example, the constraint/condition is Required Time of Arrival (RTA) constraints and the speed management functions necessary to achieve them. Once a constraint is active on a given waypoint, the icon includes contextual symbology conveying specific meaning via color and/or flight-specific data to provide additional information and situational awareness to the flight crew.

In embodiments, the systems and methods allow the crew to quickly, efficiently, and directly manipulate navigational constraints/conditions with a single click or finger press on a waypoint/fix to reduce cognitive load while also reducing the effort required to perform tasks; allowing the crew to focus on more cognitive-intensive tasks which require more focus. The systems and methods greatly simplify common tasks associated with waypoint operations that are performed throughout the flight. The information and controls required to perform tasks associated with aircraft navigation are consequently consolidated and local to the waypoint of interest on the navigation display - instead of the pilot having to memorize and perform a sequence of actions via menus and dialogs to arrive at controls performing the same waypoint operations.

In one exemplary pilot workflow, an RTA constraint is invoked directly on a waypoint by loading a constraint specific dialog box and then the constraint specific dialog box is opened to make edits by clicking on a created icon tagged to the waypoint. The pilot is provided visual indications as to the RTA constraint status in the icon and in the constraint specific dialog box. Assuming that no constraint is active on a waypoint, the pilot accesses contextual menu dialog box on the waypoint and selects "RTA". An RTA dialog box/window is opened and the Pilot selects an "Edit RTA" button. In the edit dialog box, the pilot selects desired constraints and clicks an "Apply" button. The RTA constraint is applied to the waypoint with an icon to denote the constraint. The pilot can click directly on the RTA constraint icon to directly access the RTA dialog box/window to make edits or to remove the constraint. In addition to the RTA constraint, various other constraints/conditions/operations may be applied to a particular waypoint or fix; such as holding pattern, procedure turn, altitude constraint, crossing waypoint constraint (including speed and/or altitude constraints), a speed constraint, etc..

The icon may provide unique visual symbology to denote that a waypoint has a set constraint/condition as well as color coding or other information to denote the current status of the aircraft with respect to meeting the applied constraint. The icon may include unique symbology to denote the type of constraint that has been applied to the waypoint. A waypoint may also contain multiple constraints/conditions. In such cases, a series of icons is displayed with respective color-coding illustrating the current status of the specific constraint/condition of each icon.

<FIG> illustrates a flight deck system <NUM> including various display generation and constraint/condition input, depiction and execution feature, in accordance with exemplary embodiments. The system <NUM> is included at least partly in an aircraft <NUM>. System <NUM> includes, inter alia, a processing system <NUM>, a map(s) database <NUM>, flight deck applications <NUM>, display devices <NUM>, user input devices <NUM> and a flight management system (FMS) <NUM> in a flight deck of an aircraft. System <NUM> allows a flight crew member to set a constraint/condition for a waypoint/fix, which causes an icon to be created providing information concerning the constraint/condition and including a one-click/one-tap link to a constraint/condition specific dialog box to display further information on the constraint/condition and including an edit selector button invoking an edit dialog box allowing the constraint/condition to be redefined.

The system <NUM> includes a processing system <NUM> including a processor <NUM>, memory <NUM>, dialog box module <NUM>, map display module <NUM>, icon module <NUM> and FMS interface module <NUM>. In an embodiment, the various modules are implemented by way of computer programming instructions <NUM> stored on memory <NUM> and executed by the processor <NUM>. The memory <NUM> can include one or more computer-readable media, including, but not limited to, non-transitory computer-readable media, RAM, ROM, hard drives, flash drives, or other memory devices.

In embodiments, the map display module <NUM> accesses the map database <NUM>, FMS data from the FMS <NUM> and other data sources (such as a traffic information source, an airport information source, weather information source(s), etc.) to generate a graphical user interface <NUM> including one or more maps as exemplified in <FIG>. The FMS data includes a flight plan defining waypoints/fixes through which the aircraft <NUM> is planned to fly from take-off to destination. In alternative embodiments, another source of flight data could be provided. In one example, the flight information is off-board and is down-linked to the aircraft. The map database <NUM> provides geographical map data and optionally additional map layers such as terrain data. The FMS <NUM> may include a navigation system and a guidance system. An FMS <NUM>, as is generally known, is configured to perform a wide variety of in-flight tasks during operation of an aircraft. These tasks include aircraft navigation and guidance. Although not specifically shown, the FMS <NUM> may additionally include a database with any elements necessary for the operation of the aircraft and the creation and implementation of a flight plan, including waypoints, airports, terrain information and applicable flight rules. Generally, the FMS <NUM> functions to support navigation, flight planning, and other aircraft control functions, as well as provide real-time data and/or information regarding the operational status of the aircraft. The FMS <NUM> may include or otherwise access one or more flight deck applications <NUM> including a weather system, an air traffic management system, a radar system, a traffic avoidance system, an autopilot system, a flight control system, crew alerting systems, electronic checklist systems, an electronic flight bag, and/or other suitable avionics systems.

In embodiments, the dialog box module <NUM> generates a menu dialog box <NUM> as exemplified in <FIG> when a waypoint/fix is selected by a user through the user input device <NUM>. The menu dialog box <NUM> provides a number of selection buttons including buttons for inputting a constraint/condition associated with the selected waypoint/fix. When a constraint/condition button is selected, a constraint/condition specific dialog box <NUM> is opened as exemplified in <FIG>. The constraint/condition specific dialog box <NUM> provides options for setting/editing the constraint/condition. An edit/set dialog box <NUM> is generated to allow a user to enter values for constraints/conditions and to apply those values. The dialog box module <NUM> controls generation of the dialog boxes <NUM>, <NUM>, <NUM>, receipt of user data entry to the dialog boxes <NUM>, <NUM>, <NUM> and output of control information to other modules/applications for responsive actions to the input constraints and conditions.

In embodiments, the icon module <NUM> creates and maintains one or more icons <NUM> representing the constraint/condition. The icons <NUM> provide a shortcut to the constraint/condition specific dialog box <NUM>, as exemplified in <FIG>. The icon <NUM> is provided in the form of a flag icon hanging from the waypoint/fix associated with the constraint/condition in a map part of the graphical user interface <NUM>. The icon <NUM> includes static data such as an indication of the type of constraint/condition that has been set and live data such as an indication of the current status of the constraint/condition with respect to whether the aircraft <NUM> is on target or off target with respect to achieving or meeting the constraint/condition.

In embodiments, the FMS interface module <NUM> receives and sends data items from/to the FMS <NUM> that are required by the other modules <NUM>, <NUM>, <NUM> described above. For example, the FMS interface module <NUM> receives FMS data from the FMS <NUM> for the icon module <NUM> to provide live status information and for the dialog box module <NUM> to provide live status information in the constraint/condition specific dialog box <NUM>. Furthermore, the FMS interface module <NUM> can provide data representing any set constraints/conditions to the FMS <NUM> so that the FMS <NUM> can execute, or aim to execute, the constraint/condition in conjunction with the autopilot system and/or the flight control system of the flight deck applications <NUM> such that the aircraft <NUM> flies, or aims to fly, in compliance with the set constraint/condition.

The system <NUM> includes one or more display devices <NUM> including a navigation display, a primary flight display, an electronic flight bag (EFB), and/or instrument panels. The displays are operable to present the graphical user interface <NUM> exemplified in <FIG>, which includes a lateral profile map and/or a vertical profile map, a depiction of the flight plan including waypoints/fixes and the icon <NUM> describing any set constraints/conditions for a particular waypoint/fix. The dialog boxes <NUM>, <NUM>, <NUM> can be presented as overlays on the lateral or vertical profile map in the graphical user interface <NUM>. At least one of the dialog boxes <NUM>, <NUM>, <NUM> may be integrated into the waypoint list <NUM>. Exemplary graphical user interfaces <NUM> are described below with respect to the figures.

The system <NUM> includes user input devices <NUM> to provide data and command entry modalities. In embodiments, the user input devices <NUM> include one or more of a keyboard (virtual or physical), joystick, multi-way rocker switches, mouse, trackball, touchscreen <NUM>, touch pad, data entry keys, cursor control device <NUM> and/or any other suitable device. The user input devices <NUM> allow the user to enter commands and data into the system <NUM> so as to interact with the flight deck applications <NUM> and the FMS <NUM>. The user input devices <NUM> allow a user to select a waypoint or fix displayed in the graphical user interface <NUM> and to enter selections and data concerning one or constraints/conditions for the selected waypoint/fix via the dialog boxes <NUM>, <NUM>, <NUM>.

<FIG> illustrates an exemplary graphical user interface <NUM> that is at least partly generated by the map display module <NUM>. The graphical user interface <NUM> includes a lateral map <NUM>, a vertical profile display <NUM> and a waypoints list <NUM>. It should be appreciated that a given user may have display settings such that the vertical profile display <NUM> or the waypoints list <NUM> are hidden. The lateral map <NUM> includes a lateral flight plan indication <NUM>, which includes a plurality of lateral waypoint/ fix indicators <NUM>. The lateral waypoints/fix indicators <NUM> are graphical crosses or stars in the present embodiment. A waypoint/fix identifier <NUM> is tagged to each lateral waypoint/fix indicator <NUM> to label the lateral waypoint/fix indicator <NUM> including alphanumeric text (PXR and FOWLE in the present embodiment) representing the geographic location of the waypoint/fix, usually in an abbreviated way. The lateral flight plan indication <NUM> includes a line connecting each lateral waypoint/fix indicator <NUM>. The lateral flight plan indication <NUM> is overlaid on the lateral map <NUM>, which is generated based on map data from the map database <NUM>. In the present embodiment, the map data includes terrain data such that a terrain depiction <NUM> is provided in the lateral map <NUM>. Other map layers are possible including buildings, roads, traffic, airport detailed information, etc. The lateral map <NUM> includes a lateral ownship indicator <NUM> depicting a current position of the aircraft <NUM>. In some embodiments, a cursor <NUM> is provided to allow selection of some graphical elements such as the lateral waypoint/fix indicators <NUM> and the icons <NUM>. The vertical profile display <NUM> includes similar graphical elements including a vertical ownship indicator <NUM> and a vertical flight plan indication <NUM> including vertical waypoint/fix indicators <NUM> and associated icons <NUM>. In the example of <FIG>, the graphical user interface <NUM> includes the waypoints list <NUM> providing more detailed alphanumeric information on upcoming waypoints.

In <FIG>, the graphical user interface <NUM> is shown after a user has called a menu dialog box <NUM> by selection on a lateral or vertical waypoint/fix indicator <NUM>, <NUM> with the user input device <NUM> (e.g. by selection with the cursor control device <NUM> or by touchscreen <NUM> touch selection). The menu dialog box includes a plurality of buttons allowing a user to set a constraint or condition for the selected waypoint/fix, to input a flight operation for the selected waypoint/fix or to retrieve waypoint/fix specific information. The options in the menu dialog box <NUM> apply to the selected waypoint/fix.

In the example shown in <FIG>, the user has selected the PXR waypoint/fix and the menu dialog box <NUM> is for setting a constraint or condition for the PXR waypoint/fix. The menu dialog box <NUM> appears as an overlay next to the selected waypoint/fix. The plurality of buttons includes a Center Map button <NUM> to center the lateral map <NUM> on the selected waypoint/fix. The plurality of buttons includes a Direct To button <NUM> to instigate a command, executed via the FMS <NUM>, to fly directly to the selected waypoint/fix. The plurality of buttons includes a Direct To Abeam button <NUM>, which instigates a command, executed via the FMS <NUM>, to include a plurality of in-between waypoints between the current location of the aircraft <NUM> and the selected waypoint/fix. The Vertical Direct To button <NUM> allows a user to enter altitude criteria, within operational constraints of the aircraft <NUM>, to which the aircraft <NUM> should ascend or descend by the selected waypoint/fix and to travel to the selected waypoint/fix directly. A constraint/condition specific dialog box <NUM> will be opened in response to selecting the Vertical Direct To button <NUM>, as will be described in the following with respect to <FIG>. The Vectors to Final button <NUM> allows the selected waypoint/fix to be elected as the final waypoint/fix in an instrument approach and causes the aircraft <NUM> to be vectored to the selected waypoint/fix, which will be executed via the FMS <NUM>. The Cross selector button <NUM> allows a user to set altitude and/or speed constraints including at, above, below or between constraints to be set for the selected waypoint/fix. In response to selection of the Cross selector button <NUM>, a constraint/condition specific dialog box <NUM> is opened to replace the menu dialog box <NUM>, as will be described with respect to <FIG>. The plurality of buttons includes an RTA selector button <NUM> that can be selected by a user to input a required time of arrival constraint for the selected waypoint/fix. In response to selection of the RTA selector button <NUM>, a constraint/condition specific dialog box <NUM> is opened, as will be described with respect to <FIG>. The plurality of buttons includes a holding pattern selector button <NUM> allowing a user to select a holding pattern around the selected waypoint/fix. Activation of the holding pattern selector button <NUM> will cause a constraint/condition specific dialog box <NUM> to be opened, as will be described with respect to <FIG>. The plurality of buttons includes a Winds button that provides wind information for the selected waypoint/fix when the button is picked by the user. The Show Info button provides further information on the selected waypoint/fix when the button is activated by the user.

Referring to <FIG>, a constraint/condition specific dialog box <NUM> is illustrated according to one example embodiment. In this example, the constraint/condition is an RTA constraint in response to the RTA selector button <NUM> being selected using the cursor <NUM> in the menu dialog box <NUM>. As such, the constraint/condition specific dialog box <NUM> provides information concerning an RTA constraint in the constraint/condition specific dialog box <NUM>. For other constraints/conditions like holding pattern, crossing constraint, Direct To and Vertical Direct To, other constraint specific information will be included in the dialog box <NUM>. The constraint/condition specific dialog box <NUM> includes a plurality of buttons. The plurality of buttons includes a clear selector button <NUM> for clearing or removing a previously set constraint/condition (e.g. an RTA constraint in this case). The plurality of buttons includes a first edit selector button <NUM> allowing for values of the constraint/condition to be input (as edits to a pre-existing setting or as a new constraint/condition) to an edit/set dialog box <NUM> that will be described with respect to <FIG>. The plurality of buttons (shown as condition/constraint action selectors <NUM>) may include a second edit selector button <NUM> that allows for a subset of the values of the constraint/condition to be input (as edits or new values). In the present case, RTA speeds can be input by pressing the second edit selector button <NUM> wherein the speeds are a subset of speeds and time of arrival entries that can be made by selecting the first edit selector button <NUM>. The provision of a plurality of edit selector buttons <NUM>, <NUM> is an optional feature and just one such button may be provided in a consolidated embodiment.

In the example of <FIG>, an RTA constraint has already been set. In this case, the constraint/condition specific dialog box <NUM> shows information on the pending RTA constraint. The information includes a compliance indicator <NUM> showing the set target RTA (e.g. RTA before <NUM>:<NUM>:<NUM>) and the Expected Time of Arrival (ETA: <NUM>:<NUM>:<NUM>). The ETA value is extracted from values output by the FMS <NUM>. The constraint/condition specific dialog box <NUM> includes further information <NUM> relating to the RTA constraint including RTA speed, earliest ETA and latest ETA as calculated by the FMS <NUM>. It will be appreciated that each specific type of constraint/condition will include its own metrics for the compliance indicator <NUM> and the further information <NUM>. For example, altitude constraints (e.g. crossing constraints or vertical direct to constraints) will have altitude related metrics detailing the set constraints and the current performance with respect to achieving the constraint. The constraint/condition specific dialog box <NUM> further includes a status indicator <NUM> providing a simple indication of whether the set constraint is being achieved or met (e.g. On Target or On Time) as contrasted to the numerical evaluation in the compliance indicator <NUM>.

In cases when a constraint/condition has not yet been set, the constraint/condition specific dialog box <NUM> can have blank values in the status indicator <NUM>, the compliance indicator <NUM> and the further information <NUM> and the condition/constraint action selectors <NUM> can include New or Set buttons rather than edit buttons <NUM>, <NUM>.

Referring to the exemplary embodiment of <FIG>, the edit/set dialog box <NUM> is opened in response to a user selecting the first edit selector button <NUM> or a new constraint/condition setting button using the user input device <NUM>. The edit/select dialog box is constraint/condition specific. In the case of a crossing constraint, speed or altitude values may be input along with before, at, after or between type values being selected so that the crossing constraint for the selected waypoint/fix can be submitted to the FMS <NUM>. In the case of a holding pattern condition, preprogrammed holding pattern values (altitude, position, speed, etc.) may be entered or manual entries describing the holding pattern may be entered (altitude, position, speed, etc.). In the case of a speed constraint, a speed value may be entered along with a requirement for the aircraft speed to be less than, greater than, at or between input speed values. In the case of a procedural turn condition, preprogrammed procedural turn values (altitude, position, speed, etc.) may be entered or manual entries describing the procedural turn may be entered (altitude, position, speed, etc.). Altitude or speed and/or time of arrival constraints or procedural operations can be defined in the edit/set dialog box <NUM> for a specific condition/constraint selected in the menu dialog box and for a specific waypoint/fix selected in the lateral map <NUM> or the vertical profile display <NUM>.

In the example embodiment of <FIG>, an RTA constraint is being edited or set in the edit/set dialog box <NUM>. The edit/set dialog box includes an RTA before/after/at selector <NUM> allowing selection of whether the aircraft <NUM> should arrive at the waypoint/fix temporally before, after or at a time entered in the RTA time selector <NUM>. The RTA time selector <NUM> may allow the time to be entered in hours, minutes and optionally also seconds. An RTA tolerance selector <NUM> allows a tolerance range to be entered, which in the example of <FIG> is set as <NUM> seconds plus or minus the RTA entered in the RTA time selector <NUM>. The edit/set dialog box may include FMS information <NUM> indicating minimum and maximum ETAs based on operational capabilities of the aircraft <NUM> and an expected ETA based on a current prediction from the FMS <NUM>. The edit/set dialog box <NUM> includes an apply button <NUM> such that the entered values for the constraint/condition (irrespective of the constraint/condition type) are submitted to the FMS <NUM> for execution. Further, a cancel button <NUM> may be included to cancel any entries made and abort the process.

In the example of <FIG>, the constraint/condition entered into the edit/set dialog box <NUM> has been applied by the apply button <NUM> and submitted to the FMS <NUM>. In response to the submission of the constraint/condition, the icon module <NUM> generates an icon <NUM> that at least partly describes the constraint/condition. The icon <NUM> is connected to the waypoint/fix identifier <NUM> for the waypoint to which the constraint/condition has been applied. The icon <NUM> is included in the lateral map <NUM> and/or the vertical profile display <NUM>. The icon <NUM> identifies, in connection with the waypoint/fix identifier <NUM>, that a constraint/condition has been applied, the type of constraint/condition (e.g. a procedural turn, a holding pattern, a crossing constraint of any kind (e.g. speed and/or type), an RTA constraint) in a way differentiable from other types of constraint/condition, a numerical value of the constraint/condition where applicable (e.g. time, speed or altitude) and a type of the value (e.g. before, after, at, less than, greater than or between). In the RTA constraint example of <FIG>, the icon <NUM> includes a constraint/condition identifier <NUM> including alphanumeric text specifying RTA as the constraint. Further, the constraint/condition detail indicator <NUM> is included in the icon <NUM> to specify the time value of the RTA constraint of <NUM>:<NUM> and a location of a square bracket relative to the time value indicates the value type, namely left side bracket ('[') means before, right side bracket (']') means after and brackets ('[]') on each side means at. Other symbols could be used to indicate the value type of before, after or at. The icon <NUM> includes a constraint/condition type indicator <NUM> that can be one of a variety of symbols to indicate the type of constraint/condition. In the present case, the symbol is a clock to indicate an RTA constraint. The constraint/condition type indicator <NUM> may be color coded based on the status of the constraint/condition according to data provided by the FMS <NUM>. Specifically, different colors can be used depending on whether the aircraft <NUM> is on target or off target with respect to the constraint/condition.

In accordance with embodiments of the present disclosure, the icon <NUM> embodies a shortcut such that when the icon <NUM> is selected, the constraint/condition specific dialog box <NUM> is opened directly without having to re-select the waypoint/fix indicator <NUM>, <NUM> and to make selections in the menu dialog box <NUM>, as illustrated in <FIG>. In this way, the detailed information concerning the constraint/condition embodied by the icon <NUM> (which resulted in the icon <NUM> being created) is displayed by the constraint/condition specific dialog box <NUM>. Further, an option to edit the constraint/condition by selecting the edit button <NUM>, <NUM> is presented to the user.

Exemplary icons <NUM> for the RTA constraint in different situations are provided in <FIG>. In <FIG>, the icon <NUM> shows that an RTA constraint has been at least partly set up but has not yet been applied by submission to the FMS <NUM>. In this instance, the constraint/condition type indicator <NUM> (which is a clock symbol in the present example) is generated and displayed but no time values are displayed. Further, a color coding specific to the status of no constraint having been applied is used to display the constraint/condition type indicator <NUM> in the form of a color coded status indicator <NUM>. In <FIG>, the situation has changed to the RTA constraint having been applied but the current status of the RTA constraint has not yet been established by the FMS <NUM>. The constraint/condition detail indicator <NUM> is added to the icon <NUM>, which presents the time value of the RTA constraint in a time indicator <NUM> (<NUM>:<NUM>) and the type of the time value constraint, namely in the form of a before/at/after indicator <NUM> indicating a before RTA constraint using '[' in this example. Further, the constraint/condition detail indicator <NUM> has a different color coding from that of <FIG> to convey that the RTA constraint has been applied. In the example of <FIG>, the FMS <NUM> has returned data indicating that the aircraft <NUM> is on target to arrive at the waypoint/fix in compliance with the RTA constraint. In this case, the constraint/condition detail indicator <NUM> is color coded to indicate an on-target status in the form of a color coded status indicator <NUM>. In <FIG>, the color coded status indicator <NUM> is a yet different color to indicate that the aircraft <NUM> is not predicted by the FMS <NUM> to comply with the RTA constraint. Exemplary colors for the color coded status indicator <NUM> are white for no RTA constraint applied, magenta for an RTA constraint applied, green for RTA constraint applied and compliance therewith is predicted and yellow for lack of compliance with the RTA constraint being predicted. In <FIG>, the aircraft <NUM> is predicted by the FMS <NUM> to arrive early for an after RTA constraint, which results in a lack of compliance color coded status indicator <NUM>. Further, the icon <NUM> includes a condition/constraint first status detail indicator in the form of an early message (or other indication of type of lack of compliance) and a condition/constraint second detail status indicator <NUM> quantifying the lack of compliance (e.g. <NUM> seconds early). In <FIG>, the aircraft <NUM> is predicted to be late for before RTA constraint, resulting in a lack of compliance color coded status indicator <NUM>, a late message for the condition/constraint first detail indicator <NUM> and a time quantification of how late the aircraft <NUM> is predicted to be in the condition/constraint second status detail indicator <NUM>.

In the exemplary embodiment of <FIG>, the icon <NUM> is depicted in the case of a hold constraint. In <FIG>, a hold constraint has been at least partly input but not yet applied to the FMS <NUM>. The icon <NUM> includes the constraint/condition type indicator <NUM> includes a symbol representing a holding pattern. In the example provided, the symbol is a loop with arrows showing a direction (clockwise or anticlockwise) of the holding pattern. The constraint/condition type indicator <NUM> is color coded in the form of a color coded status indicator <NUM> so as to differentiate the following statuses: no hold constraint applied (<FIG>), hold constraint applied and no compliance status information yet determined by the FMS <NUM> (<FIG>), hold constraint applied and the aircraft <NUM> is on target with respect to following the defined holding pattern (<FIG>) and hold constraint applied and the aircraft <NUM> is off target with respect to following the defined holding pattern (<FIG>). The respective colors can be white, magenta, green and yellow in one embodiment. It should be appreciated that further details of the off target status could be provided in the icon <NUM> similar to the first and second detail indicators described with respect to <FIG> for the RTA constraint. The further details could be provided by the FMS <NUM> comparing position of the aircraft <NUM> with the target position of the holding pattern. Not only could an off target or on target message be provided in a condition/constraint status first detail indicator but also a quantification of the off target status (e.g. in distance units) in a condition/constraint status second detail indicator.

In the exemplary embodiment of <FIG>, the icon <NUM> is depicted in the case of a crossing constraint. In <FIG>, a crossing constraint has been at least partly input but not yet applied to the FMS <NUM>. The icon <NUM> includes the constraint/condition type indicator <NUM> including a symbol representing a crossing constraint. In the example provided, the symbol is an outer circle with a square disposed inside with the corners of the square aligned to compass reference directions North, South, East and West. The constraint/condition type indicator <NUM> is color coded in the form of a color coded status indicator <NUM> so as to differentiate the following statuses: no cross constraint applied (<FIG>), hold constraint applied and no compliance status information yet determined by the FMS <NUM> (<FIG>), hold constraint applied and the aircraft <NUM> is on target with respect to complying with the defined crossing constraint (<FIG>) and hold constraint applied and the aircraft <NUM> is off target with respect to following the defined crossing constraint (<FIG>). The respective colors can be white, magenta, green and yellow in one embodiment. In <FIG>, the icon <NUM> may include a constraint/condition detail indicator annunciating the target speed and/or altitude of the crossing constraint and also whether the crossing constraint is a less than, greater than, at or between value. Not only could an off target or on target message be provided in a condition/constraint status first detail indicator but also a quantification of the off target status (e.g. in altitude or speed units) in a condition/constraint status second detail indicator.

In the exemplary embodiment of <FIG>, the icon <NUM> is depicted in the case of a speed constraint. In <FIG>, a speed constraint has been at least partly input but not yet applied to the FMS <NUM>. The icon <NUM> includes the constraint/condition type indicator <NUM> including a symbol representing a speed constraint. In the example provided, the symbol is an arrow having a speed value disposed therein. A direction of the arrow indicates whether a greater than or less than speed constraint is applied. The constraint/condition type indicator <NUM> is color coded in the form of a color coded status indicator <NUM> so as to differentiate the following statuses: no speed constraint applied (<FIG>), speed constraint applied and no compliance status information yet determined by the FMS <NUM> (<FIG>), speed constraint applied and the aircraft <NUM> is on target with respect to complying with the defined speed constraint (<FIG>) and speed constraint applied and the aircraft <NUM> is off target with respect to following the defined speed constraint (<FIG>). In <FIG>, the icon <NUM> may include a constraint/condition detail indicator annunciating the target speed value of the speed constraint and also whether the speed constraint is a less than, greater than, at or between value. Such a constraint/condition detail indicator may be provided in place of the directionality of the arrow and the target speed value being located therein. Not only could an off target or on target message be provided in a condition/constraint status first detail indicator but also a quantification of the off target status (e.g. in speed units of how far off target the aircraft <NUM> is predicted to be according to data provided by the FMS <NUM>) in a condition/constraint status second detail indicator.

In the exemplary embodiment of <FIG>, the icon <NUM> is depicted in the case of a procedural turn condition. In <FIG>, a procedural turn has been at least partly input (e.g. by manual entry of waypoints about the procedural turn or by loading a preprogrammed procedural turn) but not yet applied to the FMS <NUM>. The icon <NUM> includes the constraint/condition type indicator <NUM> including a symbol representing a procedural turn. In the example provided, the symbol is a tear shaped loop having arrows in a direction (e.g. clockwise or anticlockwise) of the procedural turn. The constraint/condition type indicator <NUM> is color coded in the form of a color coded status indicator <NUM> so as to differentiate the following statuses: no procedural turn condition applied (<FIG>), procedural turn condition applied and no compliance status information yet determined by the FMS <NUM> (<FIG>), procedural turn condition applied and the aircraft <NUM> is on target with respect to complying with the defined procedural turn (<FIG>) and hold constraint applied and the aircraft <NUM> is off target with respect to following the defined procedural turn (<FIG>). Not only could an off target or on target message be provided in a condition/constraint status first detail indicator but also a quantification of the off target status (e.g. in units of distance determined by the FMS <NUM> comparing the aircraft position and the defined procedural turn) in a condition/constraint status second detail indicator.

In the embodiment of <FIG>, multiple different constraints/conditions have been applied to one waypoint/fix indicated by the lateral waypoint/fix indicator <NUM>. As each constraint/condition is added, a new icon is added to the plurality of constraint/condition icons <NUM>. The icons <NUM> are concatenated to each other to form a single block including a series of icons <NUM> extending horizontally (or vertically in alternative embodiments), with each icon optionally being divided from an adjacent icon by a graphical vertical wall. Each icon of the plurality of icons <NUM> link to a different constraint/condition specific dialog box <NUM>. In the exemplary embodiment, the plurality of icons is generated based, respectively, on an applied RTA constraint, an applied speed constraint and an applied altitude constraint. It should be appreciated that less or more constraints could be applied to the waypoint/fix, which would result in less or more corresponding icons. Further, different constraint/conditions could be applied as compared to the illustrated example. Each of the plurality icons <NUM> respectively includes a constraint/condition type identifier. The first constraint/condition type identifier <NUM> includes a clock symbol to identify the RTA type constraint. The second constraint/condition type identifier <NUM> includes an arrow symbol to indicate the speed type constraint. The third constraint/condition type identifier includes an aircraft symbol to identify an altitude type constraint. As has been described heretofore, other symbols for identifying each different constraint type could be used. For the altitude type constraint, the third constraint/condition type identifier includes an underline, an overline or both to differentiate whether the altitude constraint is a below, above or at type altitude constraint. The icon for the altitude constraint may include an altitude value of the altitude constraint and may include status information such as an on target or off target message based on a prediction from the FMS <NUM> and a quantification of how off target the aircraft is predicted to be.

<FIG> depicts a flow chart of a method <NUM>, in accordance with the present disclosure. The method is performed through the processing system <NUM>, specifically the dialog box module <NUM>, the map display module <NUM>, the icon module <NUM> and the FMS interface module <NUM> thereof being executed by the processor <NUM>. Method <NUM> will be described with reference to <FIG>. The method <NUM> begins assuming that the graphical user interface <NUM> is generated and displayed including a lateral or vertical flight plan indication <NUM>, <NUM> including a plurality of waypoints/fixes labelled with lateral or vertical waypoint/fix indicators <NUM>, <NUM> and associated waypoint/fix identifiers <NUM>.

In step <NUM>, a waypoint/fix is selected by a user through the user input device <NUM>. In response, the menu dialog box <NUM> is generated and displayed in step <NUM> presenting a plurality of buttons embodying actions that can be performed with respect to the selected waypoint/fix. In step <NUM>, a selection of one of the constraint/conditions selector buttons is received such as the RTA selector button <NUM>, the holding pattern selector button <NUM>, the cross selector button <NUM>, etc. In response, the constraint/condition specific dialog box <NUM> is generated and displayed in step <NUM>. The constraint/condition specific dialog box <NUM> includes at least one edit selector button <NUM>, <NUM> to allow a user to set a new constraint/condition for the selected waypoint/fix or to edit an existing constraint/condition of the selected waypoint/fix. In step <NUM>, the edit/set dialog box <NUM> is opened in response to the user selection in step <NUM> and values defining a constraint/condition are edited or set. The constraint/condition definition can include entry of speed, position (e.g. altitude) and/or time values and optionally also whether the requirement is less than, greater than, at, before, after or between. In step <NUM>, the user selects to apply the constraint/condition defined in step <NUM>, which is consequently submitted to the FMS <NUM> for execution using a flight deck application <NUM> for controlling flight of the aircraft <NUM>.

In step <NUM>, the icon <NUM> is generated and displayed and tagged to the waypoint/fix identifier <NUM>. The icon <NUM> identifies the existence of the condition/constraint, the type of the constraint/condition through the constraint/condition type indicator <NUM> including differentiating symbology and provides details concerning the defined constraint/condition through the constraint/condition detail indicator <NUM>. The details can include an abbreviation of the defined values from step <NUM> such as a numerical representation of time, speed and/or position and the type of target value such as less than, greater than, at, before, after or between. Further, the icon <NUM> can receive data from the FMS <NUM> or other flight data source and provide a status message denoting whether the constraint/condition is on target or off target to being achieved and optionally also a quantification of how far off target the aircraft <NUM> is predicted to be at the selected waypoint/fix. In step <NUM>, icon <NUM> can be selected to provide a shortcut to the constraint/condition specific dialog box <NUM> providing more detailed information on the defined constraint/condition and the performance of the aircraft <NUM> relative to the constraint/condition and including at least one edit button <NUM>, <NUM> for commencing a process to redefine the constraint/condition.

Claim 1:
An aircraft display system for an aircraft, comprising:
a display device;
a processor in operable communication with the display device, the processor configured to execute program instructions, wherein the program instructions are configured to cause the processor to:
receive flight data from a Flight Management System (FMS) or other flight data source;
generate, based on the flight data, a map display including a depiction of a flight path and a plurality of waypoints or other fixes;
receive (<NUM>), via a user interface device, a user selection of one of the waypoints or other fixes
characterised in that the processor is further caused to;
generate and display (<NUM>) a menu dialog box (<NUM>);
receive (<NUM>), via the user interface device, a user selection of a constraint/condition the user selection of the constraint/condition comprising at least one of a Requested Time of Arrival (RTA) constraint, a holding pattern condition, a procedure turn condition, an altitude constraint, a crossing constraint or a speed constraint;
generate and display (<NUM>) a constraint/condition specific dialog box (<NUM>) containing an edit button (<NUM>);
in response to selection of the edit button (<NUM>), generate an edit/set dialog box (<NUM>) to receive (<NUM>) at least one value for the user selected constraint or condition for the selected one of the waypoints or fixes;
apply (<NUM>) the at least one value for the constraint or condition to the selected one of the waypoints or fixes via the FMS or other flight data source;
generate (<NUM>) the map display including the depiction of the flight path and the plurality of waypoints or fixes and an icon tagged to the selected one of the waypoints or fixes, wherein the icon denotes an existence of the constraint or condition and a type of the constraint or condition; and
in response to the user selecting (<NUM>) the icon using the user interface device, generate the constraint/condition specific dialog box providing further information (<NUM>) on the constraint or condition.