Dynamic approach procedure system

Abstract

The present disclosure relates to a dynamic approach procedure system. A method and apparatus for dynamically updating a customized integrated terminal approach procedure interface based on changing real-time events associated with an aircraft and an airport. A dynamic approach procedure application extracts and analyzes terminal approach data, aircraft data, airport data, and real-time weather data to automatically generate an integrated terminal approach interface. The integrated terminal approach interface presents dynamic digital approach information, including a map interface and a procedure sidebar displaying procedure data related to routes to help a pilot select a route into a destination airport. As conditions change, the terminal approach data displayed in the map and procedure sidebar is updated, and the route recommendations are improved to help the user select a destination airport, route, and related approach procedure.

Description

Technical Field

[0001] This disclosure relates to a dynamic entry procedure system. Background Technology

[0002] Terminal approach boards are static documents that provide terminal approach procedures and other information associated with the airport and / or runway approach used by pilots during landing. Pilots typically carry dozens or even hundreds of these paper terminal approach board documents for use during the selection and planning of the approach.

[0003] In some situations, digital approach boards may be used. While these documents eliminate the need for multiple paper boards, digital boards remain static and cannot reflect updates to procedures, weather changes, or other dynamic conditions. Furthermore, these static boards often include information that pilots do not need, making it more difficult to identify the required information from the approach board. Similarly, if weather or other conditions necessitate changes to in-flight procedures, pilots typically need to manually obtain weather updates and information from static terminal approach boards to update their approach procedures. This process is difficult, time-consuming, and potentially frustrating for users. Summary of the Invention

[0004] The disclosed examples are described in detail below with reference to the accompanying drawings. The following summary is provided to illustrate embodiments disclosed herein. However, this is not intended to limit all examples to any particular configuration or sequence of operations.

[0005] Some aspects and implementations disclosed herein pertain to dynamically presenting customized and integrated terminal approach procedure information within a user interface. One implementation includes multiple data sources providing aircraft data associated with a selected aircraft, airport data associated with at least one airport, and real-time weather data associated with a set of possible routes between the selected departure airport and at least one destination airport. The integrated approach user interface information display is provided via a user interface device associated with a computing device.

[0006] The integrated arrival interface includes a map interface and a program sidebar. The map interface and program sidebar provide integrated terminal arrival data associated with a set of possible routes based on aircraft and airport data. The data displayed in the integrated arrival user interface information display is customized. A recommended set is generated based on an evaluation of the integrated terminal arrival data and real-time weather data updates. The recommended set includes a set of recommended routes selected from the set of possible routes. In response to the generation of the recommended set, the integrated arrival interface information display is updated. This update includes displaying data associated with the recommended route set and removing data from the arrival user interface information display associated with routes excluded from the recommended route set from the map interface and program sidebar.

[0007] The features, functions, and advantages discussed are implemented independently in various embodiments or in combination in other embodiments, further details of which are described below and in the accompanying drawings. Attached Figure Description

[0008] Figure 1 This is a block diagram illustrating a system for generating an integrated entry interface including a map interface and a program sidebar, according to an embodiment.

[0009] Figure 2 This is a block diagram illustrating an integrated entry interface for user use according to an implementation method.

[0010] Figure 3 This is a block diagram illustrating a dynamic arrival procedure application for generating integrated terminal arrival data according to an implementation method.

[0011] Figure 4 This is a block diagram illustrating an integrated entry interface including a map interface and a program sidebar, according to an embodiment.

[0012] Figure 5 This is a block diagram illustrating a user interface display layout for integrating arrival information according to an embodiment.

[0013] Figure 6 This is a block diagram illustrating a program sidebar that includes information associated with the entry procedure, according to an embodiment.

[0014] Figure 7 This is a block diagram illustrating a sidebar with annotations according to an embodiment.

[0015] Figure 8 This is a block diagram illustrating an expandable sidebar according to an implementation method.

[0016] Figure 9 This is a block diagram illustrating an extended sidebar with a selected entrance according to an embodiment.

[0017] Figure 10 This is a block diagram illustrating the approach map workflow according to the implementation method.

[0018] Figure 11 This is a block diagram illustrating an integrated arrival user interface for a dynamic arrival procedure according to an embodiment.

[0019] Figure 12 This is a block diagram illustrating an integrated arrival user interface including an airport pop-up window according to an embodiment.

[0020] Figure 13 This is a block diagram illustrating an integrated approach interface without a landing path according to an implementation method.

[0021] Figure 14 This is a block diagram illustrating an integrated approach interface with user-selected landing routes according to an embodiment.

[0022] Figure 15 This is a block diagram illustrating an integrated approach interface including an approach path associated with a landing route, according to an embodiment.

[0023] Figure 16 This is a block diagram illustrating an integrated entry interface including an extended sidebar according to an embodiment.

[0024] Figure 17 This is a block diagram illustrating an integrated approach interface including a landing route according to an embodiment.

[0025] Figure 18 This is a block diagram illustrating an integrated arrival interface according to an embodiment, including a landing path and annotations associated with the landing path in a sidebar.

[0026] Figure 19 This is a block diagram illustrating an integrated entry interface including an expanded sidebar according to an embodiment.

[0027] Figure 20 This is a block diagram illustrating an integrated arrival interface according to an embodiment, which includes information associated with the arrival procedures selected by the user for entering the destination airport.

[0028] Figure 21 This is a flowchart interface illustrating an implementation of a dynamic entry procedure application according to an embodiment, which uses evaluation and selection data to present to the user within an integrated entry interface.

[0029] Figure 22 This is a flowchart illustrating an implementation of a dynamic entry procedure application that generates a dynamic integrated entry interface according to an implementation method.

[0030] Figure 23 This is a flowchart illustrating an implementation of a dynamic arrival procedure application that updates the integrated arrival interface when changes in weather or other conditions are detected.

[0031] Figure 24 It is a schematic 3D diagram of a specific flight module.

[0032] The corresponding reference characters in the entire attached figure represent the corresponding parts. Detailed Implementation

[0033] Various embodiments will be described in detail with reference to the accompanying drawings. Where possible, the same reference numerals will be used throughout the drawings to refer to the same or similar parts. References made throughout this disclosure to particular embodiments and in connection with embodiments are provided for illustrative purposes only and are not intended to limit all embodiments unless otherwise indicated.

[0034] The foregoing summary of the invention and the following detailed description of certain embodiments will be better understood when read in conjunction with the accompanying drawings. As used herein, an element or step referred to in the singular and preceded by the word "a" or "an" should be understood to not necessarily exclude a plurality of elements or steps. Furthermore, the reference to "an embodiment" is not intended to be construed as excluding the existence of additional embodiments that are also incorporated into the cited features. Moreover, unless expressly stated to the contrary, an embodiment that "comprises" or "has" one or more elements having a particular property may include additional elements that do not have that property.

[0035] Referring to the accompanying drawings, examples of this disclosure enable an integrated arrival interface that provides dynamic digital terminal arrival data integrated into a single interactive information display. In some examples, a dynamic arrival procedure application is provided that automatically evaluates aircraft data, airport data, and real-time weather data, along with the integrated terminal arrival data, to identify possible arrivals at the destination airport. Available arrivals are presented to the user in the integrated arrival interface, which is displayed within the user interface device. By deriving the presentation of terminal procedures directly from the data, this enables improved data maintenance and the elimination of production errors between pre-fabricated interface production. This analysis of real-time data by the dynamic arrival procedure application improves the speed and efficiency of data production and enhances data quality.

[0036] Other examples provide dynamic arrival procedures applications that curate or modify procedure data so that only data relevant to the arrivals available to the user and / or those selected is displayed in the map interface and / or sidebar of the integrated arrivals interface. This provides users with faster and more efficient customization of procedure data, while reducing the size of the terminal procedure dataset once the pre-built interface is removed. This further improves user experience and efficiency through user interface interaction. In some examples, the digital terminal arrival data used by the dynamic arrival procedures application can be automatically updated via application updates or style packages within the data. This eliminates the need to manually edit thousands of static terminal arrival panels.

[0037] In other examples, integrated arrival information displays a rationalized and customized pilot arrival procedure for users during challenging flight phases. The information is easier to use and less prone to errors. This helps users quickly obtain the necessary information. In some examples, the system generates a set of recommendations based on an assessment of integrated terminal arrival data and real-time weather data updates. In some examples, the set of recommendations includes recommended arrivals selected from a set of possible arrivals. This feature allows for quick and efficient selection of the appropriate arrival at the destination airport, improving accuracy and reducing errors.

[0038] In other examples, a program sidebar is provided within the user interface, offering additional information related to the terminal arrival procedures in a linear format. This allows information that would otherwise be scattered throughout the interface to be grouped together linearly or hierarchically, reflecting the order in which users typically process or need the information. This further improves user efficiency and reduces the time users spend obtaining the desired information from the integrated arrival interface.

[0039] Please refer to the attached diagram for more details. Figure 1 An example of a system 100 generating an integrated arrival interface 102 is illustrated, which includes a map 104 and a program sidebar 106. The integrated arrival interface 102 is a digital terminal arrival interface that integrates information from multiple terminal arrival panels into a dynamic and interactive interface that provides customized information associated with individual airports, routes, and terminal arrivals. In this example, the integrated arrival interface includes a map 104 and a program sidebar 106 for organizing and presenting customized and dynamically updated arrival information to the user. It should be understood that different or additional information may be provided.

[0040] exist Figure 1 In the examples, computing device 108 refers to any device that executes computer-executable instructions (e.g., as an application, operating system function, or both) to implement operations and functions associated with computing device 108. In some examples, computing device 108 includes mobile computing devices or any other portable devices. Mobile computing devices include, but are not limited to, mobile phones, laptop computers, tablet computers, computing boards, netbooks, and / or any other type of portable computing device. Computing device 108 may also include less portable devices such as servers, desktop personal computers, kiosks, or desktop devices. Furthermore, computing device 108 may represent a set of processing units or other computing devices.

[0041] In some examples, computing device 108 has at least one processor 110 and memory 112, and also includes a user interface device 114 that presents (e.g., displays) an integrated access interface 102 to a user. Processor 110 includes any number of processing units and is programmed to execute computer-executable instructions, such as, but not limited to, a dynamic access program application 116. The computer-executable instructions are executed by processor 110, by multiple processors within computing device 108, or by a processor external to computing device 108. In some examples, processor 110 is programmed to execute functions such as those shown in the figure (e.g., Figure 21 , Figure 22 and / or Figure 23 The instructions illustrated in ).

[0042] The computing device 108 also includes one or more computer-readable media, such as memory 112. Memory 112 includes any number of media associated with or accessible by the computing device 108. In some examples, memory 112 is internal to the computing device 108 (e.g., Figure 1 (As shown). In other examples, memory 112 is external to the computing device (not shown) or both (not shown). Memory 112 may include read-only memory and / or memory wired to the analog computing device.

[0043] Memory 112 stores data, such as dynamic arrival application 116 that processes dynamic terminal arrival data 132, as described in more detail herein. Generally, one or more applications run while being executed by processor 110 to perform functions on computing device 108. Applications may communicate with corresponding applications or services (e.g., network services accessible via a network). In one example, the application represents a downloaded client-side application corresponding to a server-side service executed in the cloud.

[0044] In one example, the dynamic approach procedure application 116 is a software component used to generate an integrated approach interface 102 within a user interface device 114 for pilots or other users to view and use. In some examples, the dynamic approach procedure application 116 accesses a collection 118 of one or more data sources to obtain information for generating and / or updating the integrated approach interface 102. In this way, the system 100 utilizes existing information sources to obtain relevant information associated with terminal approach procedures and integrates that information into the integrated approach interface 102.

[0045] The data source set 118 can include any type of data source, such as databases, cloud storage, streaming data sources, sensor devices, networked devices, and / or any other source. Data obtained from the data sources may include, but is not limited to, weather data 120, approach data 122, airport data 124, and / or aircraft-related data (e.g., but not limited to...). Figure 18 The aircraft 1801 shown in the figure has data 126. The database may include any type of data storage, such as, but not limited to, a remote database accessible via a network, and a local database 138 associated with computing device 108.

[0046] In some examples, database 138 is a database on a data storage device. The data storage device may include one or more different types of data storage devices, such as one or more spinning disk drives, one or more solid-state drives (SSDs), and / or any other type of data storage device. In some non-limiting examples, the data storage device includes a redundant array of independent disks (RAID). In other examples, the data storage device includes a remote data storage device, a data storage unit in a remote data center, or a cloud storage unit.

[0047] In one example, weather data 120 includes real-time weather data obtained from a source such as Automatic Dependent Surveillance-Broadcast (ADS-B). Approach panel data 122 is data previously provided within multiple terminal approach panels, eliminating the need for users to manually obtain or extract panel data from various terminal approach panels. Terminal approach panel data is added to the integrated approach interface 102. System 100 eliminates the need for precomposed terminal approach panels. System 100 does not rely on static approach panels shown on a map, but instead dynamically presents information currently obtained from static panels within the interface.

[0048] Airport data 124 describes the runways and landing procedures of multiple airports. In some examples, airport data 124 includes data describing the available airport facilities at the departure airport and / or the destination airport selected by the user.

[0049] Aircraft data 126 is data that identifies and / or describes the aircraft selected by the user. Aircraft data 126 may include data describing the aircraft type, aircraft equipment, aircraft speed, and / or any other aircraft data. Aircraft data 126 may be obtained from: user-provided data; data obtained from a database; data obtained in real time from sensors such as fuel sensors or airspeed indicators; and other data sources.

[0050] Data collected from the data source is integrated into a map 104 and / or a program sidebar 106 presented to the user within the user interface. In this way, system 100 provides terminal arrival data associated with a set of possible flight paths, which integrates relevant portions of aircraft data, airport data, terminal arrival board data, weather data, and / or any other data related to selecting an arrival procedure at a given destination airport. The data displayed within the integrated arrival interface 102 is customized for the selected aircraft, destination airport, and real-time weather data associated with the departure airport and / or weather associated with the destination airport.

[0051] In other examples, the dynamic approach procedure application 116 generates a set of recommendations. Recommendations may include one or more destination airports, one or more recommended routes selected from possible routes, one or more recommended arrivals at the selected destination airport, or any other recommendations. Recommendations are generated based on an evaluation of integrated terminal arrival data, user-provided flight plans 134, real-time weather data updates, and / or any other user-provided data.

[0052] The dynamic terminal arrival data 132 output to the user within the integrated arrival interface 102 is updated in real time to reflect changes to flight plans due to weather changes, missed arrivals, or other events. In some examples, map 104 displays all possible routes to the destination airport. When the user selects a route, map 104 is updated to highlight the selected route in the map view using map 104.

[0053] In other examples, if the system recommends a set of routes, the integrated arrival interface is updated to include information associated with the recommended routes, while information associated with non-recommended routes is removed from map 104 (map view) and / or program sidebar 106. In this way, the interface remains uncluttered with information that users might hardly notice or find useless. Streamlining information presentation allows users to obtain the information they need more quickly and easily.

[0054] The sensor devices in the data source set 118 may include any type of sensor used to dynamically generate aircraft-related data (such as, but not limited to, aircraft data 126). For example, but not limited to, sensor devices may include gyroscopes, accelerometers, magnetometers, Global Positioning Satellite (GPS) systems, barometers, proximity sensors, ambient light sensors, or any other type of sensor device used to measure motion, position, movement, orientation, etc.

[0055] In some examples, dynamic approach applications use sensor data to determine the orientation of the computing device. If the device is turned or rotated, making the interface displayed on the user interface unreadable, the application will reorient itself to make the interface readable and correctly oriented for the user.

[0056] In one example, the dynamic entry procedure application 116 is implemented on a local physical computing device. However, in some non-limiting examples, the dynamic entry procedure application 116 is implemented on a cloud server. The cloud server obtains data from a collection of data sources and generates an integrated entry interface 102, which is transmitted to the computing device 108 via a network. The cloud server is a logical server that provides services to the computing device or other clients. The cloud server is hosted and / or delivered via a network. In some non-limiting examples, the cloud server is associated with one or more physical servers in one or more data centers. In other examples, the cloud server is associated with a distributed server network.

[0057] In some examples, computing device 108 may optionally include communication interface device 128. Communication interface device 128 includes a network interface card and / or computer-executable instructions (e.g., a driver) for operating the network interface card. Communication between computing device 108 and data source set 118 can be conducted, wholly or partially, using any protocol or mechanism via any wired or wireless connection. In some examples, communication interface device 128 may operate using short-range communication technologies, such as by using near-field communication (NFC) tags. In other examples, communication interface device 128 enables computing device 108 to receive real-time data 130 from data source set 118, such as weather updates or any other type of data.

[0058] Figure 1 The computing device 108 shown is depicted as a stand-alone computing device. However, in other examples, the computing device may be a hardwired or mounted device on an aircraft, for example... Figure 18 The aircraft 1801 is illustrated in the example. The aircraft can be implemented as an aircraft, helicopter, or other transport vehicle. In some other examples, the computing device 108 can be a portable user device carried or used on the aircraft. In still other examples, the computing device 108 can be a computing device installed within the aircraft that is removable rather than hardwired to the aircraft. However, the examples are not limited to aircraft (e.g., below). Figure 24 The computing device used on the aircraft shown in the figure.

[0059] In other examples, System 100 automatically provides pilots and other users with dynamic terminal approach information, taking into account aircraft and aircraft equipment type, aircraft speed, available airport facilities, and weather (and / or other information). The system provides approach information directly on the interface using a symbology system, including a map interface and / or sidebar for navigation. In various examples, the approach information is dynamically and in real-time updated based on changing weather conditions, user approach selections, etc.

[0060] Figure 2 An integrated arrival interface 102 presented within a user interface device 114 is illustrated for use by user 208. In this non-limiting example, the integrated arrival interface 102 presents customized, dynamic terminal arrival data to user 208 in the form of a combination of a map 104 and a program sidebar 106. Map 104 provides a representation of areas within the vicinity of one or more airports. The areas shown on the map can be determined based on a user-configurable radius "N" from the airport. In other examples, the areas depicted on map 104 may include a user-selected number "N" square miles around one or more airports, or any other area.

[0061] The area depicted on map 104 includes overlay map 202. Overlay map 202 is a set of symbols representing one or more possible routes to the selected airport. Overlay map 202 may also include, for example, but not limited to, symbols representing other approach information for one or more possible approaches, such as, but not limited to, runway identifiers, waypoints, approach speeds, and location points.

[0062] The program sidebar 106 presents customized program information to the user 208 in a linear format. In some examples, the linear format provides information in a condensed form, excluding information unrelated to the user's selected aircraft, airport, and / or route. In other words, any terminal arrival procedure information unrelated to the user's flight plan and currently selected route is removed from the display within the integrated arrival interface 102 to streamline the presentation of information to the user. This improves the efficiency with which the user can identify relevant information that may be most beneficial to the user at the moment the information is displayed.

[0063] In other examples, the integrated arrival interface 102 updates dynamically in response to user selection 206. User selection 206 may include, for example, the user's selection of a destination airport, the user's selection of a route from two or more possible routes to the destination airport, the user's selection of an arrival airport, etc. With each user selection received, the system updates the information displayed in the integrated arrival interface to highlight the selected route, display information associated with the selected airport and arrival, and remove information associated with unselected routes, arrival airports, or airports from the display. This real-time updating ensures that the most relevant and useful information is presented to the user at any given time for evaluation and utilization during flight or pre-flight planning.

[0064] In other examples, the system evaluates information about the aircraft and current weather conditions, combining it with information from the approach interface to assimilate the data and make recommendations to the user regarding approach and route selection. This helps the user choose the correct procedure for the aircraft and conditions. Integrated information is provided in the combination of map 104 and sidebar 106, enabling approach information and a dynamically updated scrollable list. In some examples, system 100 presents customized information, both in text form in the sidebar and graphically within the map, based on the path being evaluated. This improves the user's ability to quickly and easily digest information.

[0065] Figure 3 An example of a dynamic approach procedure application 116 is illustrated, which is configured to generate integrated terminal approach data displayed within an integrated approach interface. In this non-limiting example, the dynamic approach procedure application 116 includes an approach interface generator 302. The approach interface generator 302 is a software component that analyzes and integrates terminal approach data, as well as aircraft data, airport data, and other dynamic data, to generate an integrated approach interface 102. The integrated approach interface 102 provides approach data associated with multiple airports, routes, approaches, and other data in an integrated manner, making all the information that pilots expect or need available within a single source, namely the integrated approach interface 102.

[0066] The dynamic update component 306 (e.g., a software component) receives real-time updates 308, such as weather updates and other dynamic data describing constantly changing conditions within and around the airport, which may require updating the integrated arrival interface 102. The dynamic update component 306 updates the information displayed within the integrated arrival interface to reflect changes in weather, flight routes, or arrival conditions, which may make the information available or unavailable due to changes, etc.

[0067] Similarly, if a user selects a route from a set of two or more possible routes to the destination airport, the integrated arrival interface is updated by the dynamic update component 306 to highlight information associated with the user's selection and remove any data that becomes irrelevant to the given user selection.

[0068] The route evaluation component 312 (e.g., a software component) identifies all routes 314 leading to the selected destination airport 316. Possible routes are displayed to the user within the integrated approach interface 102. In some examples, the dynamic approach application 116 applies one or more parameters 318 to the terminal approach data to identify possible routes from the user's departure airport to their destination airport. For example, the parameters might specify that if the data indicates the runway is closed due to icing weather conditions, the route will be removed from the list of possible routes available to the user.

[0069] In other examples, the dynamic arrival procedure application 116 includes a recommendation generator 320. In one example, the recommendation generator 320 is a software component that optionally generates one or more recommendations for the user. In this non-limiting example, the recommendation generator 320 generates a set 322 of one or more recommended routes to the selected destination airport. In this example, the integrated arrival interface can be updated to provide route information for the recommended routes, while removing information associated with unrecommended routes from the map and / or sidebar.

[0070] In other examples, the recommendation generator 320 may recommend arrivals 324 and / or one or more procedures 326 associated with one or more airports. The recommendations can be displayed to the user via a map interface or via a sidebar. In some examples, the displayed terminal procedure information supports the pilot's workflow.

[0071] Figure 4 An integrated arrival interface 102, including a map interface 402 and a program sidebar 106, is schematically illustrated. The map interface 402 provides a user interface including a map 104 with an overlay map 404 that presents arrival procedure data to the user. In some examples, the overlay map 404 includes route identifiers, waypoint identifiers, and other symbols that provide arrival procedure data to the user.

[0072] Map 104 may optionally include a set of markers 408 to identify approach procedure-related data to the user. The set of markers 408 may include markers such as, but not limited to, approach speed markers, speed limit markers, minimum altitude markers, maximum altitude markers, initial approach positioning (IAF), final approach positioning (FAF), altitude limits at different positioning points, missed approach markers, etc.

[0073] In other examples, the procedure sidebar 106 includes terminal arrival procedure information arranged in a linear, hierarchical format. However, the examples are not limited to a hierarchical format. In other examples, the arrival procedure information may be presented in any other format within the procedure sidebar 106.

[0074] Figure 5 A user interface display layout 500 integrating an arrival interface is schematically illustrated. User interface display layout 500 is an example of a layout for presenting customized terminal arrival information within a user interface device for user use. In this example, user interface display layout 500 includes a toolbar 502. Toolbar 502 optionally includes one or more controls for selecting display options within the user interface. For example, toolbar 502 may include options for selecting flight plan data to display, program data to display, etc.

[0075] Dynamic map 504 is a map display used to illustrate the procedures described in sidebar 506. Other example map displays present route information, airport locations, waypoints, or other approach-related data.

[0076] Sidebar 506 presents procedure information in a line chart view. In this example, sidebar 506 includes a procedure title identifying the procedure, briefing information, secondary information and buttons for frequently used actions, flight path information, the selected minimum altitude, and visibility. Sidebar 506 includes selectable options, such as allowing the pilot to select different minimum values ​​by selecting different minimum values ​​(e.g., tapping the touchscreen allows the pilot to select different minimum values). In some examples, sidebar 506 may also optionally include buttons for missed approach procedures and / or less frequently used functions. Less frequently used functions may include changing the selected procedure or other procedures.

[0077] In some examples, the user-selected approach route to the destination airport is shown on map 104, and sidebar 506 includes additional information about the route, such as missed approach information. If the pilot descends to the minimum altitude of the selected approach procedure but does not see the runway, the pilot must return and try again. In this case, map 104 is dynamically updated to automatically show the missed approach route overlaid on map 104. This helps the pilot react seamlessly to constantly changing conditions during flight.

[0078] Figure 6 A program sidebar 600, including information associated with the entry procedure, is illustrated schematically. In this non-limiting example, the program sidebar 600 includes information presented in a hierarchical, top-down line table view 602.

[0079] In some examples, layout 606 includes briefing information 608 associated with the selected procedure. Note 610 describes various aspects of the procedure and additional information applicable to procedures represented in terminal approach charts or sidebars. Route data 612 includes information associated with the procedure, such as, but not limited to, IAF, FAF, minimum altitude, maximum altitude, and / or speed limits. Other information may be displayed. In other examples, the procedure sidebar 600 includes missed approach information 614 (e.g., missed approach procedure) that may be provided, for example, in the event of a missed approach attempt.

[0080] Figure 7 Example 700 shows a sidebar 700 with comment 704. Sidebar 700 is a program sidebar, such as, but not limited to, others. Figure 1 Sidebar 106. Procedure title 708 indicates Instrument Landing System (ILS) 11. Note 704 contains additional information about the procedure. Sidebar 700 in this example also includes flight path data 706 associated with the procedure.

[0081] Figure 8 An expandable side lever 800 is illustrated. Side lever 800 is a programmable side lever, such as, but not limited to, others. Figure 1 Side bar 106. Side bar 800 in this example can be expanded to provide additional details about the procedure. In this example, additional details include missed approach procedures 802 (e.g., step-by-step procedures including text and graphics). Other options are available, such as adding procedures, activating certain routes (vectors), changing approaches, changing IAFs, etc.

[0082] Figure 9 An example is shown with an extended sidebar 900 that displays the selected entry information. Sidebar 900 is a program sidebar, such as, but not limited to, [other types]. Figure 1 Sidebar 900 is shown as 106. In this example, sidebar 900 can be expanded (e.g., to provide an expanded display or user interface) to accommodate additional information associated with the selected approach. In this example, program title 902 indicates instrument landing. The expanded sidebar 900 includes notes 904 (e.g., a section with notes for the approach) and information on the flight path 906 (e.g., flight path information in a line-style format including text and graphics).

[0083] Now will describe Figures 10 to 20 These diagrams illustrate different display and user interface configurations, such as at different stages before or during flight. More specifically, Figure 10 This example illustrates the approach map workflow flight plan presented within sidebar 1000. Sidebar 1000 is a program sidebar, including, but not limited to, [examples of other programs]. Figure 1Sidebar 106 in this example. Sidebar 1000 displays possible routes 1002 associated with flight plan 1004. The user can select a route from the set of possible routes using a toolbar. That is, an interactive map is displayed, which allows for dynamic selection and updating of possible routes 1002 associated with flight plan 1004. It should be noted that display properties such as brightness and scale can be adjusted as desired or needed. Different displays and user interfaces described herein can be customized.

[0084] Figure 11 An integrated entry interface 1100 for dynamic entry procedures is illustrated. The integrated entry interface 1100 is a digital entry interface, such as, but not limited to, [other types]. Figure 1 The integrated entry interface 102 is shown in this non-limiting example. The integrated entry interface 102 includes a toolbar 1102, a map 1104, and a sidebar 1106. In other examples, a toolbar with selectable labels may optionally be provided. In this example, the label of map 1108 is selected to trigger the display of map 1104. The user can select a panel 1110 label to trigger the display of program data within a different panel interface instead of the map interface, such as... Figure 11 As shown, the board interface presents arrival information in different formats, such as the terminal arrival board type format. However, the example is not limited to providing a board interface. In other examples, a board interface may not be provided. Other optional tabs may also be provided within the interface.

[0085] Figure 12 An integrated arrival interface 1200, including an airport pop-up window, is illustrated. The integrated arrival interface 1200 is a digital arrival interface, such as, but not limited to, those shown below. Figure 1 The integrated arrival interface 102 is shown in the example. In this non-limiting example, the user can open (e.g., select on the user interface) the program sidebar 1202 of the flight plan for an airport by clicking a program button or clicking the dashed line that completes the route from the departure point to the destination airport. It should be noted that "tapping" refers to the user making a selection by touching the user interface (e.g., on a touchscreen display). However, other input devices and apparatuses are also conceivable, including other touchable and non-touchable inputs. The program sidebar 1202 for any airport can be selected (e.g., opened) by clicking a program button in the airport pop-up window 1204 (e.g., an overlaid information box).

[0086] Figure 13 An example of an integrated approach interface 1300 without a landing path is shown. The integrated approach interface 1300 is a digital approach interface, such as, but not limited to, [other types of interfaces]. Figure 1The integrated arrival interface 102 is shown in this example. In this non-limiting example, the user has not yet selected or landed a route. Therefore, route-related information is not displayed in the sidebar. Users can create routes in the flight plan to enable the navigation advisor and / or populate the sidebar with route-related program information. As described herein, the selection process and display of this information are dynamically updated and may include automatic modification in some examples.

[0087] Figure 14 An integrated approach interface 1400 with user-selected landing routes is illustrated. The integrated approach interface 1400 is a digital approach interface, such as, but not limited to, [other types]. Figure 1 The integrated arrival interface 102 includes a map 1402 and a line-style sidebar 1404. In this example, a list within the sidebar 1404 is presented to the user to begin procedural selection of departure, arrival, arrival, and entry into the destination airport.

[0088] Figure 15 An integrated approach interface 1500, including an approach path associated with the landing configuration, is illustrated. The integrated approach interface 1500 is a digital approach interface, such as, but not limited to, [other types of interfaces]. Figure 1 The integrated approach interface 102 is shown in this example. In this non-limiting example, the approach selected by the user is represented as an overlay map on map 1502. This overlay map shows various possible approach paths for aircraft flying into the selected airport. Approaches with up-to-date weather information associated with the airport and / or the surrounding area are also listed in the sidebar 1504 to help the user decide which approach to choose. That is, as described herein, relevant weather information is displayed and dynamically updated.

[0089] In this example, the minimum altitude for the approach is highlighted to indicate that the current ceiling is too low for a flight approach. For example, the approach is highlighted with a color, such as red. However, the example is not limited to red. In other examples, the approach can be highlighted with yellow, orange, or any other color. In still other examples, the approach information in sidebar 1504 can be highlighted using underlines, bold text, all capital letters, or any other method of highlighting. In yet another example, the user selects the approach from sidebar 1504 or directly from map 1502.

[0090] Figure 16 An integrated entry interface 1600, including an extended sidebar 1602, is illustrated. The integrated entry interface 1600 is a digital entry interface, such as, but not limited to, those described above. Figure 1The integrated entry interface 102 is shown in the example. This non-limiting example illustrates the integrated entry interface 1600 during the intermediate stage when the user selects an entry from multiple possible entries listed in the sidebar 1602. That is, the entry selected by the user is incomplete at this stage.

[0091] Figure 17 An integrated approach interface including landing paths is illustrated. The integrated approach interface 1700 is a digital approach interface, such as, but not limited to, [other types of interfaces]. Figure 1 The integrated arrival interface 1700 shows the intermediate stages of the procedure selection, allowing users to zoom in on the final arrival feeder route via map 1702 or sidebar 1704. In other words, the integrated arrival interface 1700 includes more focused information in its display.

[0092] Figure 18 An integrated approach interface 1800 is illustrated, including a landing path and a note 1802 in a sidebar associated with the landing path. The integrated approach interface 1800 is a digital approach interface, such as, but not limited to, [other types]. Figure 1 The integrated approach interface 102 is used in this example. In this non-limiting example, the Instrument Landing System (ILS11) enters the selected airport (KPWM) and lands with an initial approach positioning (ENE). Only the minimum altitude and annotations for this specific approach are displayed, significantly reducing clutter within the integrated approach interface 1800 compared to a prefabricated (static) terminal approach panel. That is, a more readable and understandable user interface and display are provided. In some examples, the type, amount, and granularity of information are user-selectable and / or can be automatically populated and modified by the user.

[0093] Figure 19 An integrated arrival interface 1900, including an expanded sidebar 1902, is illustrated. The expanded sidebar 1902 displays information associated with the selected arrival at the destination airport. The integrated arrival interface 1900 is a digital arrival interface, such as, but not limited to, [other types]. Figure 1 The integrated entry interface 102 is shown in this example. In this example, the expanded sidebar 1902 provides additional information while still maintaining a simplified and less cluttered view.

[0094] Figure 20 An integrated arrival interface 2000 is illustrated, which includes information associated with the arrival procedures selected by the user for entering the destination airport. The integrated arrival interface 2000 is a digital arrival interface, such as, but not limited to, [other types]. Figure 1The integrated arrival interface 102 is shown in this example. In this example, sidebar 2002 includes several departure, arrival, arrival, and destination airport traffic patterns. In the example scenario, a user flying to the destination airport can click a program button on the integrated arrival interface to select an arrival from a list of all possible arrivals to the destination airport. The system combines terminal arrival interface data with arrival paths overlaid or superimposed on the terminal arrival interface data. The user selects a process and adds it to the flight path. Arrivals can be selected from the map view or from sidebar 2002.

[0095] In other examples, the system allows users to select an approach for a runway. The system applies filters to narrow down the minimum values ​​required for their flight approach. This reduces the number of possible approaches to evaluate. For example, a set of fifteen possible approaches can be filtered down to four. It should be understood that the filtering attributes and criteria can be modified or adjusted by the user, for example, based on flight conditions.

[0096] In other examples, the integrated approach interface 2000 is updated during flight based on dynamic weather data received during the flight. That is, the received weather information is used to update the displayed information. In one example, the NOTAM (Notice to Airmen) is also updated to display pilot-defined information. Specifically, the update displays defined, required, or expected information that warns the pilot of external factors.

[0097] Figure 21 This is a flowchart illustrating an implementation of a dynamic entry procedure application that evaluates and assimilates data to be presented to the user within an integrated entry interface. In one implementation, Figure 21 The operation shown is performed at least in part by one or more processors (e.g., but not limited to) Figure 1 The processor 110 in the middle executes instructions to perform this.

[0098] In operation 2102, the user selects the departure airport and destination airport via the dynamic approach procedure application interface (e.g., using dynamic approach procedure application 116). In operation 2104, the dynamic approach procedure application receives the procedure type selected by the user, including the departure airport, arrival airport (destination), and approach. It should be noted that other user selections related to the flight plan (e.g., other pre-flight information) can be made and received.

[0099] Once an approach type is selected, in operation 2106, the dynamic approach application 116 evaluates the efficiency of each approach path, which can be based on several different factors. For example, in operation 2108, the dynamic approach application 116 evaluates the flight conditions (e.g., thunderstorms) along the selected approach path. In operation 2110, the dynamic approach application uses a dynamic map to present the assimilated approach information in a linear sequence, as described in more detail herein.

[0100] In operation 2112, the dynamic approach procedure application 116 checks the current maximum flight limits and visibility (e.g., determines maximum flight limits and visibility information along the approach path). In operation 2114, the applicability of minimum maximum flight limits and visibility for each approach is assessed (e.g., feasibility, availability, etc. are evaluated). In operation 2116, the dynamic approach procedure application 116 assesses minimum weather conditions for individuals and / or companies. For example, information and requirements specific to a particular company owning the aircraft may be assessed to determine compliance.

[0101] In operation 2118, the dynamic approach procedure application 116 evaluates the preferred landing orientation based on wind direction (e.g., available landing orientation options). In operation 2120, it evaluates the runway length (e.g., different available runway lengths at the destination airport). In operation 2128, it checks the airport lighting status (e.g., current and future lighting conditions at the destination airport). In operation 2122, the dynamic approach procedure application 116 evaluates the Notifications of the Airline Operators (NOTAMs) affecting the airport and approach. In operation 2124, the dynamic approach procedure application 116 considers the aircraft approach speed (e.g., identifying available approach speeds, minimum approach speeds, and / or maximum approach speeds). In operation 2126, it checks available navigation equipment (e.g., identifying flight navigation equipment available at the destination airport). In operation 2110, this assimilated approach information is presented in the integrated approach interface. That is, this information can be displayed in one or more user interfaces, as described herein (see, for example...). Figures 10 to 20 ).

[0102] It should be understood that additional or different information can be used by the methods described above, where the dynamic entry procedure applies evaluation and assimilation of data to present it to the user within the integrated entry interface. That is, different relevant information can be used to automatically generate the integrated entry interface, as described herein.

[0103] Figure 22 This illustrates the flow interface of method 220 for generating a dynamically integrated entry interface (e.g., via dynamic entry procedure application 116). In one embodiment, Figure 22 The illustrated operations are performed at least in part by one or more processors (e.g., but not limited to) Figure 1 The processor 110 in the middle executes instructions to perform this.

[0104] In operation 2202, aircraft data, airport data, and real-time weather data are obtained from multiple data sources. That is, flight plan information that can be used and assimilated by this disclosure is obtained (e.g., automatically obtained from external sources, pilot input, etc.). In operation 2204, an integrated arrival interface including a map interface and a sidebar is provided. For example, as described herein, a simplified user interface including a map and a sidebar is generated, which is easier to interpret or understand. In operation 2206, the data is evaluated (e.g., flight plan information is analyzed based on flight requirements, aircraft requirements, company requirements, etc.). In operation 2208, it is determined whether to make a recommendation (e.g., whether to present one or more flight plan options to the user). If so, a set of recommendations is generated in operation 2210 (e.g., tiered options for flight plans are presented to the pilot). Then, in operation 2212, the integrated arrival interface is updated, for example, based on the recommendations. In some examples, the pilot can accept or reject the recommendations.

[0105] Figure 23 The process interface of method 2300 is to update the integrated arrival interface when changes in weather or other conditions are detected (e.g., via dynamic arrival procedure application 116). Figure 23 The operations illustrated in the example are performed at least in part by one or more processors (e.g., but not limited to...). Figure 1 The processor 110 in the middle executes instructions to perform this.

[0106] In operation 2302, an integrated arrival interface is generated. For example, as described herein, one or more displays or user interfaces are generated. In operation 2304, it is determined whether a user selection has been made (e.g., whether user input corresponding to the displayed options, features, etc. has been received). If yes, the integrated arrival interface is updated in operation 2306 (e.g., the displayed information is updated). Thereafter, or if no user selection has been made, it is determined in operation 2308 whether the conditions have changed, for example, based on information received automatically or manually (e.g., weather or airport information, whether flight, landing, or other conditions have changed (because a flight plan has been generated)). If yes, the integrated arrival interface is updated in operation 2310, for example, updating map information (e.g., overlay map information) and / or sidebar information (including the order or configuration of displayed information). Thereafter, or if the conditions have not changed, it is determined in operation 2312 whether to continue. If yes, operations 2304 to 2312 are performed iteratively until it is determined in operation 2312 that no further continuation is possible. If no, method 2300 ends.

[0107] Now for reference Figure 24A more specific diagram is depicted of a flight device 2401 in which an embodiment of the present disclosure is advantageously employed. In this example, the flight device 2401 includes a fuselage 2403 and a plurality of systems 2404 and an interior 2406. Embodiments of the plurality of systems 1804 include one or more of a propulsion system 2408, an electrical system 2410, a hydraulic system 2412, and an environmental system 2414. This system may be implemented in an aircraft navigation system or on a portable computing device used by a pilot within the aircraft. Other systems (not shown) are also included as candidate systems. Although an aerospace example is shown, different advantageous embodiments are also applicable to other industries, such as the automotive industry, etc.

[0108] Although combined Figure 1 The computing device 108 described herein is illustrated, but the examples of this disclosure can be implemented using many other general-purpose or special-purpose computing system environments, configurations, or devices. Implementations of well-known computing systems, environments, and / or configurations suitable for use with aspects of this disclosure include, but are not limited to, smartphones, mobile tablets, mobile computing devices, personal computers, server computers, handheld computers, handheld or laptop devices, multiprocessor systems, game consoles, microprocessor-based systems, set-top boxes, programmable consumer electronics, mobile phones, mobile computing and / or wearable or accessory form factors (e.g., watches, glasses, headphones, or earphones) communication devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the systems or devices described above, VR devices, holographic devices, etc. Such systems or devices accept input from users in any manner, including from input devices such as keyboards or pointing devices, via gesture input, proximity input (e.g., by hovering), and / or via voice input.

[0109] Embodiments of this disclosure are described in the general context of computer-executable instructions (e.g., program modules) that execute in software, firmware, hardware, or a combination thereof on one or more computers or other devices. In one example, the computer-executable instructions are organized into one or more computer-executable components or modules. Typically, program modules include, but are not limited to, routines, programs, objects, components, and data structures that perform a particular task or implement a particular abstract data type. In one example, aspects of this disclosure are implemented with any number and organization of such components or modules. For example, aspects of this disclosure are not limited to specific computer-executable instructions or specific components or modules illustrated in the figures and described herein. Other examples of this disclosure include different computer-executable instructions or components having more or fewer functions than those illustrated and described herein. In embodiments involving general-purpose computers, aspects of this disclosure transform a general-purpose computer into a special-purpose computing device when configured to execute the instructions described herein.

[0110] By way of example and not limitation, computer-readable media include computer storage media and communication media. Computer storage media include volatile and non-volatile memory, removable memory, and non-removable memory implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules, etc. Computer storage media are tangible and mutually exclusive with communication media. Computer storage media are implemented in hardware and do not include carrier waves and propagating signals. Computer storage media used for the purposes of this disclosure are not signals themselves. In one example, computer storage media include hard disks, flash drives, solid-state memory, phase-change random access memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other storage technologies, optical disc read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, cassette tape, magnetic tape, disk storage or other magnetic storage devices, or any other non-transmission medium used to store information for access by a computing device. In contrast, communication media typically implement computer-readable instructions, data structures, program modules, etc., in modulated data signals such as carrier waves or other transmission mechanisms, and include any information transmission medium.

[0111] As described above, program code instructions can be stored in memory and executed by processing circuitry programmed thereon to implement the functions of the systems, subsystems, tools, and their corresponding elements described herein. It should be understood that any suitable program code instructions can be loaded from a computer-readable storage medium onto a computer or other programmable device to produce a particular machine, such that the particular machine becomes a means for implementing the functions specified herein. These program code instructions can also be stored in a computer-readable storage medium that can direct a computer, processing circuitry, or other programmable device to operate in a particular manner, thereby producing a particular machine or article of art. Instructions stored in a computer-readable storage medium can produce an article of art, wherein the article of art becomes a means for implementing the functions described herein. Program code instructions can be retrieved from a computer-readable storage medium and loaded into a computer, processing circuitry, or other programmable device to configure the computer, processing circuitry, or other programmable device to perform operations to be performed on or by the computer, processing circuitry, or other programmable device.

[0112] The retrieval, loading, and execution of program code instructions can be performed sequentially, such that one instruction is retrieved, loaded, and executed at a time. In some example implementations, retrieval, loading, and / or execution can be performed in parallel, such that multiple instructions are retrieved, loaded, and / or executed together. The execution of program code instructions can produce computer-implemented processes, such that the instructions, executed by a computer, processing circuitry, or other programmable device, provide operations for implementing the functions described herein.

[0113] The processing circuitry executes instructions or stores instructions in a computer-readable storage medium to support a combination of operations for performing a specified function. It will also be understood that one or more functions and combinations of functions can be implemented by a computer system and / or processing circuitry based on dedicated hardware, or a combination of dedicated hardware and program code instructions, to perform the specified function.

[0114] The following paragraphs describe other aspects of this disclosure. In some embodiments, the paragraphs described below may be further combined in any sub-combination without departing from the scope of this disclosure.

[0115] Clause 1. A system for providing a dynamically integrated terminal arrival procedure interface, the system comprising:

[0116] A set of data sources that provides aircraft data associated with the selected aircraft, airport data associated with at least one airport, and real-time weather data associated with a set of possible routes between the selected departure airport and at least one destination airport.

[0117] A computing device, the computing device including a computer-readable medium storing instructions that, when executed by a processor, are operated to:

[0118] Based on the aircraft data and the airport data, an integrated arrival interface is provided via a user interface device. The integrated arrival interface includes a map interface and a program sidebar. The map interface and the program sidebar provide integrated terminal arrival data associated with the set of possible routes. The data displayed in the integrated arrival interface is customized for the selected aircraft, the at least one destination airport, and the real-time weather data associated with the at least one destination airport.

[0119] A recommendation set is generated based on an evaluation of the integrated terminal arrival data and real-time weather data updates. This recommendation set includes a set of recommended routes selected from the set of possible routes.

[0120] In response to generating the recommended set, the integrated entry interface is updated, wherein the update includes displaying data associated with the recommended route set and removing data associated with routes excluded from the recommended route set from the map interface and the program sidebar.

[0121] Clause 2. The system according to Clause 1, wherein the instructions are further operated to:

[0122] In response to receiving a route selected by the user from the recommended route set, the integrated terminal arrival data displayed in the integrated arrival interface is updated to remove data associated with unselected routes in the recommended route set.

[0123] Clause 3. The system according to Clause 1 or 2, wherein the instructions are further operated to:

[0124] In response to receiving a route selected by the user from a set of possible routes associated with the destination airport, the selected route is highlighted in the map interface.

[0125] Clause 4. The system according to any one of Clauses 1 to 3, wherein the instructions are further operated to:

[0126] The online table view provides terminal arrival procedure data associated with the user-selected arrival in the procedure sidebar, wherein the data is selected to remove unnecessary terminal procedure data that is irrelevant to the user-selected arrival from the view.

[0127] Clause 5. The system according to any one of Clauses 1 to 4, wherein the instructions are further operated to:

[0128] The terminal arrival procedure data associated with the user-selected arrival is presented in a hierarchical, top-down format in the program sidebar. The terminal arrival procedure data includes briefing information, custom annotations, flight route data, and missed arrival data.

[0129] Clause 6. The system according to any one of Clauses 1 to 5, wherein the instructions are further operated to:

[0130] The terminal procedure information is displayed, which allows pilots to dynamically evaluate and select terminal procedures during pre-flight planning and in-flight procedures.

[0131] Clause 7. The system according to any one of Clauses 1 to 6, wherein the instructions are further operated to:

[0132] A set of markers is overlaid on the map within the map interface, the set of markers including at least one of initial approach positioning, final approach positioning, minimum altitude, maximum altitude, and speed limit.

[0133] Clause 8. A method for dynamically integrating a terminal arrival procedure interface, the method comprising the following steps:

[0134] Obtain aircraft data associated with the selected aircraft, airport data associated with at least one airport, and real-time weather data associated with a set of possible routes between the selected departure airport and at least one destination airport from multiple data sources.

[0135] Based on the aircraft data and the airport data, an integrated arrival interface is provided via a user interface device. The integrated arrival interface includes a map interface and a program sidebar. The map interface and the program sidebar provide integrated terminal arrival data associated with the set of possible routes. The data displayed in the integrated arrival interface is customized for the selected aircraft, the at least one destination airport, and the real-time weather data associated with the at least one destination airport.

[0136] A recommendation set is generated based on an evaluation of the integrated terminal arrival data and real-time weather data updates. This recommendation set includes a set of recommended routes selected from the set of possible routes.

[0137] In response to generating the recommended set, the integrated entry interface is updated, wherein the update includes displaying data associated with the recommended route set and removing data associated with routes excluded from the recommended route set from the map interface and the program sidebar.

[0138] Clause 9. The method described in Clause 8 further comprises the following steps:

[0139] In response to receiving a route selected by the user from the recommended route set, the integrated terminal arrival data displayed in the integrated arrival interface is updated to remove data associated with unselected routes in the recommended route set.

[0140] Clause 10. The method described according to Clause 8 or 9 further comprises the following steps:

[0141] In response to receiving a route selected by the user from a set of possible routes associated with the destination airport, the selected route is highlighted in the map interface.

[0142] Clause 11. The method according to any one of Clauses 8 to 10, the method further comprising the following steps:

[0143] The online table view provides terminal arrival procedure data associated with the user-selected arrival in the procedure sidebar, wherein the data is selected to remove unnecessary terminal procedure data that is irrelevant to the user-selected arrival from the view.

[0144] Clause 12. The method according to any one of Clauses 8 to 11, further comprising the following steps:

[0145] The terminal arrival procedure data associated with the user-selected arrival is presented in a hierarchical, top-down format in the program sidebar. The terminal arrival procedure data includes briefing information, custom annotations, flight route data, and missed arrival data.

[0146] Clause 13. The method according to any one of Clauses 8 to 12, further comprising the following steps:

[0147] The terminal procedure information is displayed, which allows pilots to dynamically evaluate and select terminal procedures during pre-flight planning and in-flight procedures.

[0148] Clause 14. The method according to any one of Clauses 8 to 13, further comprising the following steps:

[0149] A set of markers is overlaid on the map within the map interface, the set of markers including at least one of initial approach positioning, final approach positioning, minimum altitude, maximum altitude, and speed limit.

[0150] Clause 15. A computer program product comprising a computer-usable medium having computer-readable program code embodied therein, the computer-readable program code being adapted to be executed to implement a method for providing a dynamically integrated terminal arrival procedure interface, the method comprising the steps of:

[0151] Obtain aircraft data associated with the selected aircraft, airport data associated with at least one airport, and real-time weather data associated with a set of possible routes between the selected departure airport and at least one destination airport from multiple data sources.

[0152] Based on the aircraft data and the airport data, an integrated arrival interface is provided via a user interface device. The integrated arrival interface includes a map interface and a program sidebar. The map interface and the program sidebar provide integrated terminal arrival data associated with the set of possible routes. The data displayed in the integrated arrival interface is customized for the selected aircraft, the at least one destination airport, and the real-time weather data associated with the at least one destination airport.

[0153] A recommendation set is generated based on an evaluation of the integrated terminal arrival data and real-time weather data updates. This recommendation set includes a set of recommended routes selected from the set of possible routes.

[0154] In response to generating the recommended set, the integrated entry interface is updated, wherein the update includes displaying data associated with the recommended route set and removing data associated with routes excluded from the recommended route set from the map interface and the program sidebar.

[0155] Clause 16. The computer program product as described in Clause 15, further comprising:

[0156] In response to receiving a user's selection of a route from the recommended route set, the integrated terminal arrival data displayed in the integrated arrival interface is updated to remove data associated with unselected routes in the recommended route set.

[0157] Clause 17. The computer program product according to Clause 15 or 16, further comprising:

[0158] In response to receiving a user's selection of a route from a set of possible routes associated with the destination airport, the selected route is highlighted in the map interface.

[0159] Clause 18. The computer program product according to any one of Clauses 15 to 17, wherein the computer program product further comprises:

[0160] The online table view provides terminal arrival procedure data associated with the user-selected arrival in the procedure sidebar, wherein the data is selected to remove unnecessary terminal procedure data that is irrelevant to the user-selected arrival from the view.

[0161] Clause 19. The computer program product according to any one of Clauses 15 to 18, wherein the computer program product further comprises:

[0162] The terminal arrival procedure data associated with the user-selected arrival is presented in a hierarchical, top-down format in the program sidebar. The terminal arrival procedure data includes briefing information, custom annotations, flight route data, and missed arrival data.

[0163] Clause 20. The computer program product according to any one of Clauses 15 to 19, wherein the computer program product further comprises:

[0164] The terminal procedure information is displayed, which allows pilots to dynamically evaluate and select terminal procedures during pre-flight planning and in-flight procedures.

[0165] The embodiments disclosed herein are described in the general context of computer code or machine-usable instructions, including computer-executable instructions (e.g., program components) that are executed by a computer or other machine (e.g., a personal data assistant or other handheld device). Typically, a program component, including routines, programs, objects, parts, data structures, etc., refers to code that performs a specific task or implements a specific abstract data type. The disclosed embodiments are practiced in a variety of system configurations, including personal computers, laptops, smartphones, mobile tablets, handheld devices, consumer electronics, professional computing devices, etc. The disclosed embodiments are also implemented in distributed computing environments, where tasks are performed by remote processing devices linked via a communication network.

[0166] When describing elements of this disclosure or embodiments thereof, the articles “a,” “an,” “the,” and “described” are intended to indicate the presence of one or more elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be other elements besides those listed. The term “implementation” is intended to mean “example.” The phrase “one or more of the following: A, B, and C” means “at least one of A and / or at least one of B and / or at least one of C.”

[0167] Although the subject matter has been described in language specific to structural features and / or methodological actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims.

[0168] It should be understood that the above benefits and advantages may relate to one implementation or multiple implementations. Implementations are not limited to those that solve any or all of the described problems or those that have any or all of the described benefits and advantages. It will be further understood that reference to "a" means one or more of these items.

[0169] The term "comprising" is used in this specification to mean including the features or actions that follow, but does not exclude the presence of one or more additional features or actions.

[0170] In some examples, the operations illustrated in the figures can be implemented as software instructions encoded on a computer-readable medium, in hardware programmed or designed to perform the operations, or both. For example, aspects of this disclosure can be implemented as a system-on-a-chip or other circuitry comprising multiple interconnected conductive elements.

[0171] Unless otherwise stated, the order in which operations are performed or executed in the examples of this disclosure illustrated and described herein is not essential. That is, operations may be performed in any order unless otherwise stated, and the examples of this disclosure may include operations with or without additions to those disclosed herein. For example, it is conceivable that a particular operation may be performed before, simultaneously with, or after another operation, which is within the scope of this disclosure.

[0172] When describing elements of this disclosure or embodiments thereof, the articles “a,” “an,” “the,” and “the” are intended to indicate the presence of one or more elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be other elements besides those listed. The term “exemplary” is intended to mean “example.” The phrase “one or more of the following: A, B, and C” means “at least one of A and / or at least one of B and / or at least one of C.”

[0173] Having described aspects of this disclosure in detail, it will be apparent that modifications and variations are possible without departing from the scope of the aspects of this disclosure as defined in the appended claims. Since various changes can be made to the above-described structures, products, and methods without departing from the scope of the aspects of this disclosure, all subject matter contained in the foregoing description and shown in the accompanying drawings should be interpreted as illustrative and not restrictive.

[0174] It should be understood that the above description is intended to be illustrative and not restrictive. As an example, the above embodiments (and / or aspects thereof) may be used in combination with each other. Furthermore, many modifications can be practiced to adapt particular situations or materials to the teachings of various embodiments of this disclosure without departing from the scope of this disclosure. While the dimensions and types of materials described herein are intended to define parameters of various embodiments of this disclosure, these embodiments are by no means restrictive and are exemplary embodiments. Many other embodiments will be apparent to those skilled in the art upon review of the above description. Therefore, the scope of the various embodiments of this disclosure should be determined by reference to the appended claims and the full scope of their equivalents. Furthermore, terms such as “first,” “second,” and “third” are used merely as labels and are not intended to impose numerical requirements on their objects.

Claims

1. A system for generating a terminal arrival procedure interface, the system comprising: Multiple data sources provide aircraft data associated with the selected aircraft, airport data associated with at least one airport, and real-time weather data associated with a set of possible routes between the selected departure airport and at least one destination airport. A computing device, the computing device including a computer-readable medium storing instructions that, when executed by a processor, are operable to: Based on the aircraft data, the real-time weather data, and the airport data, an integrated arrival interface is provided via a user interface device. The integrated arrival interface includes a map interface and a program sidebar. The map interface and the program sidebar include integrated terminal arrival data associated with the set of possible routes. The data displayed in the integrated arrival interface is customized for the selected aircraft, the at least one destination airport, and the real-time weather data associated with the at least one destination airport. A recommendation set is generated based on an evaluation of the integrated terminal arrival data and real-time weather data updates. The recommendation set includes a set of recommended routes selected from the set of possible routes. In response to generating the recommended route set, the integrated entry interface is updated, wherein the update includes displaying data associated with the recommended route set and removing data associated with routes excluded from the recommended route set from the map interface and the program sidebar; and The online table view provides terminal arrival procedure data associated with the user-selected arrival in the procedure sidebar, wherein the data is assimilated to remove unnecessary terminal procedure data that is irrelevant to the user-selected arrival from the view.

2. The system of claim 1, wherein, The computing device is also configured to: In response to receiving a user's selection of a route from the recommended route set, the integrated terminal arrival data displayed in the integrated arrival interface is updated to remove data associated with unselected routes in the recommended route set.

3. The system according to claim 1, wherein, The computing device is also configured to: In response to receiving a user's selection of a route from a set of possible routes associated with the destination airport, the selected route is highlighted in the map interface.

4. The system according to claim 1, wherein, The computing device is also configured to: The terminal arrival procedure data associated with the user-selected arrival is presented in a hierarchical, top-down format in the program sidebar. The terminal arrival procedure data includes one or more of the following: briefing information, custom notes, flight route data, and missed arrival data.

5. The system according to claim 1, wherein, The computing device is also configured to: Terminal procedure information is displayed within the user interface, which allows pilots to dynamically evaluate and select terminal procedures during pre-flight planning and in-flight procedures.

6. The system according to claim 1, wherein, The computing device is also configured to: A set of markers is overlaid on the map within the map interface, the set of markers including at least one of initial approach positioning, final approach positioning, minimum altitude, maximum altitude, and speed limit.

7. A computerized method for generating a dynamically integrated terminal arrival procedure interface, the computerized method comprising the following steps: Obtain aircraft data associated with the selected aircraft, airport data associated with at least one airport, and real-time weather data associated with a set of possible routes between the selected departure airport and at least one destination airport from multiple data sources. Based on the aircraft data and the airport data, an integrated arrival interface is provided via a user interface device. The integrated arrival interface includes a map interface and a program sidebar. The map interface and the program sidebar include integrated terminal arrival data associated with the set of possible routes. The data displayed in the integrated arrival interface is customized for the selected aircraft, the at least one destination airport, and the real-time weather data associated with the at least one destination airport. A recommendation set is generated based on an evaluation of the integrated terminal arrival data and real-time weather data updates. The recommendation set includes a set of recommended routes selected from the set of possible routes. In response to generating the recommended route set, the integrated entry interface is updated, wherein the update includes displaying data associated with the recommended route set and removing data associated with routes excluded from the recommended route set from the map interface and the program sidebar; and The online table view provides terminal arrival procedure data associated with the user-selected arrival in the procedure sidebar, wherein the data is assimilated to remove unnecessary terminal procedure data that is irrelevant to the user-selected arrival from the view.

8. The computerized method according to claim 7, further comprising the following steps: In response to receiving a user's selection of a route from the recommended route set, the integrated terminal arrival data displayed in the integrated arrival interface is updated to remove data associated with unselected routes in the recommended route set.

9. The computerized method according to claim 8, further comprising the following steps: In response to receiving a user's selection of a route from a set of possible routes associated with the destination airport, the selected route is highlighted in the map interface; The terminal arrival procedure data associated with the user-selected arrival is presented in a hierarchical, top-down format in the program sidebar. The terminal arrival procedure data includes one or more of the following: briefing information, custom notes, flight route data, and missed arrival data. The user interface displays terminal procedure information that allows pilots to dynamically evaluate and select terminal procedures during pre-flight planning and in-flight procedures; and A set of markers is overlaid on the map within the map interface, the set of markers including at least one of initial approach positioning, final approach positioning, minimum altitude, maximum altitude, and speed limit.

Images