Speed schedule tracking

Abstract

A system and method are provided for continuously monitoring manual flight inputs and updating a flight management system with those manual inputs. The flight management system recalculates and provides predictions based on the manual inputs. The flight management system may continuously monitor certain thresholds. The flight management system utilizes the crew entered speed schedule until a threshold is exceeded. When the flight management system is reengaged, it may utilize the manually entered speeds within the speed schedule for a current phase of the flight. The flight management system may analyze the manual input and corresponding predictions to determine if they are within or conform to certain predefined criteria before using them for automated flight.

Claims

1. A computer apparatus comprising: at least one processor in data communication with a memory storing processor executable code for configuring the at least one processor to: receive a speed schedule; identify a manual speed input; continuously monitor one or more threshold criteria, wherein the one or more threshold criteria comprises at least one of: a threshold deviation between prediction based on the speed schedule and the manual speed input; a threshold time in the manual mode; or a weighted function based on a time in the manual mode and an absolute deviation between the speed schedule and manual speed; when the one of the one or more threshold criteria are met, provide the manual speed input to one or more predictive functions; and update the speed schedule based on the manual speed input meeting one of the one or more threshold criteria in the manual mode; and switch from the manual mode to the automatic mode based on the updated speed schedule.

2. The computer apparatus of claim 1, wherein the at least one processor is further configured to: record predictions based on the speed schedule; record predictions based on the manual speed input; and compare the predictions based on the speed schedule to the predictions based on the manual speed; wherein the at least one of the threshold criteria is the threshold deviation between the predictions based on the speed schedule and the manual speed input.

3. The computer apparatus of claim 1, wherein: the at least one processor is further configured to record a time beginning with receiving the manual speed input; wherein the at least one of the threshold criteria is the threshold time in the manual mode.

4. The computer apparatus of claim 3, wherein the at least one of the threshold criteria is the weighted function based on the time in the manual mode and the absolute deviation between the speed schedule and manual speed such that a greater speed deviation over a short period of time triggers the same threshold criteria as a small speed deviation over a longer period.

5. The computer apparatus of claim 3, wherein the processor is further configured to amend the speed schedule to conform to the manual speed after a predefined time in the manual mode.

6. A method comprising: receiving a speed schedule; identifying a manual speed input; continuously monitoring one or more threshold criteria, wherein the one or more threshold criteria comprises at least one of: a threshold deviation between prediction based on the speed schedule and the manual speed input; a threshold time in the manual mode; or a weighted function based on a time in the manual mode and an absolute deviation between the speed schedule and manual speed; when the one of the one or more threshold criteria are met, providing the manual speed input to one or more predictive functions; and rendering predictions updating the speed schedule based on the manual speed input meeting one of the one or more threshold criteria in the manual mode; and switching from the manual mode to the automatic mode based on the updated speed schedule.

7. The method of claim 6, further comprising: recording predictions based on the speed schedule; recording predictions based on the manual speed input; and comparing the predictions based on the speed schedule to the predictions based on the manual speed, wherein the at least one of the threshold criteria is the threshold deviation between the predictions based on the speed schedule and the manual speed input.

8. The method of claim 6, further comprising recording a time beginning with receiving the manual speed input, wherein the at least one of the threshold criteria is the threshold time in the manual mode.

9. The method of claim 8, wherein the at least one of the threshold criteria is the weighted function based on the time in the manual mode and the absolute deviation between the speed schedule and manual speed such that a greater speed deviation over a short period of time triggers the same threshold criteria as a small speed deviation over a longer period.

10. A flight management system comprising: at least one processor in data communication with a memory storing processor executable code for configuring the at least one processor to: receive a speed schedule; identify a manual speed input; continuously monitor one or more threshold criteria, wherein the one or more threshold criteria comprises at least one of: a threshold deviation between prediction based on the speed schedule and the manual speed input; a threshold time in the manual mode; or a weighted function based on a time in the manual mode and an absolute deviation between the speed schedule and manual speed; when the one of the one or more threshold criteria are met, provide the manual speed input to one or more predictive functions; and update the speed schedule based on the manual speed input meeting one of the one or more threshold criteria in the manual mode; and switch from the manual mode to the automatic mode based on the updated speed schedule.

11. The flight management system of claim 10, wherein the at least one processor is further configured to: record predictions based on the speed schedule; record predictions based on the manual speed input; and compare the predictions based on the speed schedule to the predictions based on the manual speed; wherein the at least one of the threshold criteria is the threshold deviation between the predictions based on the speed schedule and the manual speed input.

12. The flight management system of claim 10, wherein: the at least one processor is further configured to record a time beginning with receiving the manual speed input; wherein the at least one of the threshold criteria is the threshold time in the manual mode.

13. The flight management system of claim 12, wherein the at least one of the threshold criteria is the weighted function based on the time in the manual mode and the absolute deviation between the speed schedule and manual speed such that a greater speed deviation over a short period of time triggers the same threshold criteria as a small speed deviation over a longer period.

14. The flight management system of claim 12, wherein the processor is further configured to amend the speed schedule to conform to the manual speed after a predefined time in the manual mode.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The numerous advantages of the embodiments of the inventive concepts disclosed herein may be better understood by those skilled in the art by reference to the accompanying figures in which:

(2) FIG. 1 shows a block diagram of a system suitable for implementing an exemplary embodiment;

(3) FIG. 2A shows a flight management system interface useful for implementing an exemplary embodiment;

(4) FIG. 2B shows a flight management system interface useful for implementing an exemplary embodiment;

(5) FIG. 3 shows a flowchart of a method according to an exemplary embodiment;

DETAILED DESCRIPTION

(6) Before explaining various embodiments of the inventive concepts disclosed herein in detail, it is to be understood that the inventive concepts are not limited in their application to the arrangement of the components or steps or methodologies set forth in the following description or illustrated in the drawings. In the following detailed description of embodiments of the instant inventive concepts, numerous specific details are set forth in order to provide a more thorough understanding of the inventive concepts. However, it will be apparent to one of ordinary skill in the art having the benefit of the instant disclosure that the inventive concepts disclosed herein may be practiced without these specific details. In other instances, well-known features may not be described in detail to avoid unnecessarily complicating the instant disclosure. The inventive concepts disclosed herein are capable of other embodiments or of being practiced or carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein is for the purpose of description and should not be regarded as limiting.

(7) As used herein a letter following a reference numeral is intended to reference an embodiment of a feature or element that may be similar, but not necessarily identical, to a previously described element or feature bearing the same reference numeral (e.g., 1, 1a, 1b). Such shorthand notations are used for purposes of convenience only, and should not be construed to limit the inventive concepts disclosed herein in any way unless expressly stated to the contrary.

(8) Further, unless expressly stated to the contrary, or refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by anyone of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).

(9) In addition, use of a or an are employed to describe elements and components of embodiments of the instant inventive concepts. This is done merely for convenience and to give a general sense of the inventive concepts, and a and an are intended to include one or at least one and the singular also includes the plural unless it is obvious that it is meant otherwise.

(10) Also, while various components may be depicted as being connected directly, direct connection is not a requirement. Components may be in data communication with intervening components that are not illustrated or described.

(11) Finally, as used herein any reference to one embodiment, or some embodiments means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the inventive concepts disclosed herein. The appearances of the phrase in at least one embodiment in the specification does not necessarily refer to the same embodiment. Embodiments of the inventive concepts disclosed may include one or more of the features expressly described or inherently present herein, or any combination or sub-combination of two or more such features.

(12) Broadly, embodiments of the inventive concepts disclosed herein are directed to a system and method for continuously monitoring manual flight inputs and updating a flight management system with those manual inputs. The flight management system recalculates and provides predictions based on the manual inputs. The flight management system may continuously monitor certain thresholds. The flight management system utilizes the crew entered speed schedule until a threshold is exceeded. When the flight management system is reengaged, it may utilize the manually entered speeds within the speed schedule for a current phase of the flight. The flight management system may analyze the manual input and corresponding predictions to determine if they are within or conform to certain predefined criteria before using them for automated flight.

(13) Referring to FIG. 1, a block diagram of a system suitable for implementing an exemplary embodiment is shown. The system includes a processor 100, a memory 102 for storing processor executable code, and a display 104 in data communication with the processor 100. The system, which may be embodied in a flight management system, may be in an automatic mode wherein the processor 100 produces predictions base on a crew supplied speed schedule, or in a manual mode wherein the processor 100 produces predictions based on an instantaneous manual speed input. Such predictions may include time, fuel, and distance predictions.

(14) In at least one embodiment, the processor 100 receives a crew supplied speed schedule corresponding to certain flight phases and produces and renders predictions on the display 104 (as in FIGS. 2A-2B). Existing systems, when placed in the manual mode, continue to produce predictions based on the speed schedule. A processor 100 according to an exemplary embodiment determines when the system is in a manual mode (either directly via a user interface input, crew entry of a manual speed input, signal from a separate avionics component via a data connection element 108, a deviation from the speed schedule as identified via a separate avionics component, etc.).

(15) When the processor 100 determines that the system has entered the manual mode, the processor 100 may begin monitoring certain threshold criteria. While no threshold criteria are exceeded, the processor 100 may continue to render predictions based on the speed schedule with the expectation that the manual deviation from the speed schedule will be short lived, deviations minimal, and that it would be confusing to supply long term predictions based on short term speed changes.

(16) When the processor 100 determines that one of the threshold criteria has been exceeded, the processor 100 may begin rendering predictions based on the manual speed instead of the speed schedule with the expectation that the manually input speed will be longer than minimal in duration, and will result in prediction deviations substantial enough to warrant crew attention. In at least one embodiment, threshold criteria may include an absolute time while in the manual mode (i.e., after ten minutes in the manual mode, the processor 100 may switch to predictions based on the manual speed input), a percentage time (i.e., after five percent of the flight phase is spend in the manual mode), or the like. Alternatively, or in addition, the threshold criteria may comprise threshold deviations; for example, the processor 100 may begin producing predictions based on the manual speed input when the system enters the manual mode, and compare predictions based on the manual speed to the predictions based on the speed schedule. When the predictions based on the manual speed deviate from the predictions based on the speed schedule by more than a threshold amount, the processor 100 may begin rendering the predictions based on the manual speed. In at least one embodiment, the threshold criteria may comprise a weighted function of several data points; for example, the processor 100 may execute a function based on the time in the manual mode and the absolute deviation between the speed schedule and manual speed such that a greater speed deviation over a short period of time triggers the same threshold criteria as a small speed deviation over a longer period of time.

(17) In at least one embodiment, where the processor 100 produces and monitors predictions based on the manual speed even while still in the automatic mode, the processor 100 may determine if those predictions exceed some safety threshold (i.e., fuel usage or the like). The threshold criteria may comprise anticipated violations of those safety thresholds.

(18) In at least one embodiment, the processor 100 may amend the speed schedule, or offer the crew the option to amend the speed schedule based on some threshold criteria, for example after some threshold time in the manual mode, to simplify crew operations. While in the manual mode, the processor 100 may monitor a set of criteria and offer a new soft selection, or trigger the FMS to offer a soft selection, to allow the crew to pull the manual speed into the speed schedule when the crew deems it time to do so.

(19) Referring to FIGS. 2A-2B, a flight management system interface useful for implementing an exemplary embodiment are shown. In one example, an initial speed schedule (as in FIG. 2A) defines speeds and altitudes for various phases of a flight and a cruise phase speed 200 of 300 knots or 0.85 mach. The speed schedule is basis for certain predictions 202. At some point, air traffic control may instruct the crew to fly at 270 knots instead of 300 knots for traffic reasons. In at least one embodiment, the crew may switch to a manual mode 204 and begin flying at 270 knots. The FMS may retain the existing speed schedule in a memory and switch current speed 208 to 270 knots. Speeds for the current flight phase 206 are updated to reflect the current speed 208, and new predictions 210 are generated.

(20) At some future time, air traffic control may instruct the crew to return to the original flight plan, and the crew may switch from the manual mode to an automatic mode. The original speed schedule is resumed and the FMS produces speed schedule-based predictions.

(21) Alternatively, the crew may elect to retain the manual speed as an updated entry in the speed schedule for the duration of the flight/phase. In the present example, the FMS would the current speed 208 at 270 knots and produce predictions on the route page. Performance predictions continue to predict the future state of the aircraft based on the current set of inputs, with the prior manual speed as the FMS planned speed while in the automatic mode.

(22) Referring to FIG. 3, a flowchart of a method according to an exemplary embodiment is shown. A flight management system receives 300 a speed schedule and produces 302 predictions (i.e., fuel, time, and distance predictions) based on that speed schedule. The flight management system may then identify 304 that the corresponding aircraft has entered a manual speed mode. In at least one embodiment, the flight management system may receive a user input placing the aircraft in the manual mode; alternatively, the flight management system may identify a manual speed input has been entered.

(23) After determining that the aircraft has entered the manual speed mode, the flight management system continuously monitors 306 certain threshold criteria including, but not limited to, a time in manual speed mode, a percentage of the total flight phase spend in manual mode, or an absolute deviation between the manual speed and the speed schedule. In addition, the flight management system may compare predictions based on the manual speed input to predictions based on the speed schedule; the threshold criteria may be based on a deviation identified by the comparison.

(24) In at least one embodiment, when one or more threshold criteria are exceeded, the flight management system may utilize 308 the manual speed input to make and display new predictions to the flight crew. In at least one embodiment, if the flight management system is maintained in the manual mode for some extended threshold time, the flight management system may update 310 the speed schedule to the manual speed input, or offer the crew the option to do so.

(25) At any time, the flight management system may be returned 312 to an automatic mode and generate predictions based on the speed schedule.

(26) It is believed that the inventive concepts disclosed herein and many of their attendant advantages will be understood by the foregoing description of embodiments of the inventive concepts, and it will be apparent that various changes may be made in the form, construction, and arrangement of the components thereof without departing from the broad scope of the inventive concepts disclosed herein or without sacrificing all of their material advantages; and individual features from various embodiments may be combined to arrive at other embodiments. The forms herein before described being merely explanatory embodiments thereof, it is the intention of the following claims to encompass and include such changes. Furthermore, any of the features disclosed in relation to any of the individual embodiments may be incorporated into any other embodiment.