The present disclosure relates generally to systems and methods for handling incoming information, including air traffic control clearance information, aboard an aircraft.
Modern aircraft typically receive instructions from air traffic control (ATC) or other control authorities during many phases of flight operations, including outbound taxi maneuvers, take-off, climb-out, cruise, descent, landing and inbound taxi maneuvers. The instructions typically include clearances (for example, clearances to land or ascend to a particular altitude) and/or other requests (for example, to tune the aircraft radio to a particular frequency). The instructions can be immediate or conditional. Immediate instructions are intended to be implemented and complied with immediately. Conditional instructions are not to be implemented until a particular condition is met. For example, some conditional instructions are not to be implemented until a specific time period has elapsed, or until the aircraft has reached a specified ground point or altitude.
Conditional instructions have the advantage of providing the aircraft crew with advance notice of a requested change for the path of the aircraft. However, conditional clearances may also pose problems. For example, the crew may not realize that the clearance is conditional and may accordingly implement the instruction prematurely. In other cases, the crew may lose track of when or where the instruction is to be implemented and may accordingly implement the instruction either prematurely or too late. Still further, some instructions include multiple conditional clearances (e.g., clearances that are to be implemented only after multiple conditions are met, or a series of clearances that are to be implemented sequentially as certain conditions are met). Such instructions can be ambiguous and therefore difficult for the crew to understand. These instructions can also be difficult for the crew to track and implement at the correct time and/or location. Some existing aircraft systems provide a warning to the crew if a particular clearance condition is violated. However, such systems may not address the foregoing problems in the most efficient and effective manner.
The present invention is directed toward systems and methods for handling aircraft information received from an off-board source. A method in accordance with one embodiment of the invention includes receiving from a source off-board an aircraft in instruction for a change in a characteristic of the aircraft during operation. The method can further include automatically determining whether or not at least a portion of the instruction is to be implemented once a condition is met. If at least a portion of the instruction is to be implemented once a condition is met, the method further includes automatically carrying out a first course of action. If implementation of at least a portion of the instruction is not predicated upon fulfilling a condition, the method can include automatically carrying out a second course of action different than the first course of action.
In particular embodiments, carrying out the first course of action can include determining what condition must be met before at least a portion of the instruction is to be implemented, and presenting an indication to an operator of the aircraft before the condition is met, after the condition is met, or both before and after the condition is met. Carrying out the second course of action can include presenting an indication to an operator of the aircraft at least approximately immediately upon determining that the instruction is not to be implemented once a condition is met.
In further embodiments, the instruction can be received from air traffic control and can include a request for changing at least one of a direction, altitude and speed of the aircraft, for example. The instruction can include both conditional and non-conditional portions, or multiple conditions that are to be met sequentially or simultaneously before implementing portions of the instruction.
In still further embodiments, some or all of the foregoing aspects can be carried out by an aircraft system. Accordingly, a system in accordance with one embodiment of the invention can include a receiver portion configured to receive from a source off-board an aircraft an instruction for a change in a characteristic of the aircraft during operation, a discriminator portion configured to automatically determine whether or not the instruction is to be implemented once a condition is met, and a conditional instruction handler configured to automatically carry out a first course of action if the instruction is to be implemented once a condition is met. The system can further include a non-conditional instruction handler configured to automatically carry out a second course of action different than the first course of action if implementation of at least a portion of the instruction is not predicated upon fulfilling a condition.
In yet further embodiments, a computer-implemented method for displaying information corresponding to incoming aircraft operation instructions includes receiving from a source off-board the aircraft an instruction for a change in a characteristic of the aircraft during operation, wherein the instruction is to be implemented once a condition is met. The method can further include displaying at a single display location an at least two-dimensional indication of the location of the aircraft and a location at which the condition is expected to be met. The at least two-dimensional indication can include an indication of the altitude of the aircraft relative to a first axis, and an indication of a distance relative to a second axis transverse to the first axis. The method can further include displaying a textual indication of an upcoming change in a flight path of the aircraft.
The following disclosure describes systems and methods for receiving, displaying and implementing instructions received by an aircraft from an off-board source during flight operations. Certain specific details are set forth in the following description and in
Many embodiments of the invention described below may take the form of computer-executable instructions, including routines executed by a programmable computer (e.g., a flight guidance computer or a computer linked to a flight guidance computer). Those skilled in the relevant art will appreciate that the invention can be practiced on other computer system configurations as well. The invention can be embodied in a special-purpose computer or data processor that is specifically programmed, configured or constructed to perform one or more of the computer-executable instructions described below. Accordingly, the term “computer” as generally used herein refers to any data processor and can include Internet appliances, hand-held devices (including palm-top computers, wearable computers, cellular or mobile phones, multi-processor systems, processor-based or programmable consumer electronics, network computers, minicomputers and the like).
The invention can also be practiced in distributed computing environments, where tasks or modules are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules or subroutines may be located in both local and remote memory storage devices. Aspects of the invention described below may be stored or distributed on computer-readable media, including magnetic or optically readable or removable computer disks, as well as distributed electronically over networks. Data structures and transmissions of data particular to aspects of the invention are also encompassed within the scope of the invention.
The flight guidance computer 110 can be linked to one or more aircraft control systems 101, shown in
The flight guidance computer 110 can include a memory and a processor and can be linked to the display devices 111, I/O devices 113 and/or other computers of the system 100. The I/O devices 113 and the display devices 111 are housed in a flight deck 140 of the aircraft 102 for access by the pilot or other operator. When the instructions 121 are not received by the instruction handler automatically (e.g., via a data link), the operator can provide instructions to the instruction handler 120 via the I/O devices 113. Further details of the instruction handler 120 and associated methods for its operation are described below.
The discriminator portion 223 can identify whether the instructions 121 are to be implemented immediately or after a condition has been met. If the instructions 121 are to be implemented immediately, control can pass to a non-conditional instruction handler 225. If the instructions 121 are to be implemented only when a condition is first met, control can pass to a conditional instruction handler 224. The conditional instruction handler 224 and the non-conditional instruction handier 225 can each handle instructions in a different manner to provide the operator with more accurate information and/or to reduce the likelihood for mis-implementing the instructions. Both the conditional instruction handler 224 and the non-conditional instruction handler 225 can direct displays and indications and/or annunciations to the operator via a displays and indications director 226, and can implement the instructions via an instruction implementor 227. Further details of particular methods by which the instruction handler 120 operates are described below with reference to
In process portion 380, the process 300 includes receiving instructions corresponding to a requested change in an aircraft characteristic. If the operator rejects the instructions (process portion 381) control returns to step 380. If not, control advances to process portion 382, where it is determined whether or not the operator has accepted the instructions. If the operator accepts the instructions, an indication of receipt can optionally be displayed (process portion 383) and/or transmitted to the source of the instructions (e.g., ATC).
In process portion 384, the nature of the instruction (e.g., whether it is conditional or non-conditional) is determined. If the instruction includes both conditional and non-conditional aspects, each aspect can be handled separately, as described below with reference to
The process 300 can then include determining whether or not the aircraft is within a particular margin of meeting the condition (process portion 386). If the aircraft is within the margin, the system 100 can generate an indication or annunciation (process portion 387). For example, if the instruction is to be implemented at a target altitude, the indication can be generated when the aircraft is within a predetermined margin (e.g., 1,000 feet) of the target altitude. If the instruction is to be implemented at a target time, the indication can be displayed when the aircraft is within a predetermined margin (e.g., two minutes) of the target time. If the instruction is to be implemented when the aircraft reaches a target location, the indication can be generated when the aircraft is within a predetermined range (e.g., two nautical miles) of the target location. If the instruction is not a conditional instruction, the non-conditional instruction handler 225 can also direct the generation of an indication immediately or nearly immediately (process portion 392). Accordingly, the operator will receive an indication (a) immediately if the instruction is non-conditional, and (b) prior to meeting a target condition if the instruction is conditional. If the instruction includes more than one condition, portions of the process 300 (e.g., portions 385–391) can be repeated for each condition. Further details of instructions having multiple conditions are described below with reference to
From this point, conditional and non-conditional instructions can be handled in generally the same manner. Accordingly, in process portion 393, the instruction is implemented, either automatically or with operator input 389. The entire process 300 can then be repeated for each newly received instruction before ending (process portion 394).
Tables 1–3 illustrate exemplary conditional instructions that can be implemented with the systems and methods described above. Each instruction can include a condition portion corresponding to a condition that must be met before a directive portion is implemented. The directive portions of each instruction are indicated in capital letters, with the condition and target indicated in lower case letters. Referring first to Table 1, the instructions can include instructions to change a course, altitude or speed of the aircraft at a selected position or time. As shown in Tables 2 and 3, the instructions can also include requests to change other characteristics or settings of the aircraft. For example, in Table 2, the instruction can include a directive to contact or monitor a particular facility (e.g., ATC facility) or radio frequency at a particular location or time. As shown in Table 3, the instruction can include a request for a report, for example, a request to report the distance to a particular position at a particular time. Table 3 also illustrates conditional instructions that require reporting when a particular position or altitude is attained. In other embodiments, the instructions can have different forms (e.g., multiple conditions, as described below with reference to
The flight instruments 447 can include primary flight displays (PFDs) 445 that provide the operators with actual flight parameter information, and multifunction displays 439, which can in turn include navigation displays 448 that display navigational information. The flight instruments 447 can further include a mode control panel (MCP) 450 having input devices 451 for receiving inputs from the operators, and a plurality of displays 452 for providing flight control information to the operators. The operators can select the type of information displayed on at least some of the displays by manipulating a display select panel 449. Control display units (CDUs) 416 positioned on the control pedestal 446 provide an interface to a flight management computer (FMC) 413. The CDUs 416 include a flight plan list display 414 for displaying information corresponding to upcoming segments of the aircraft flight plan. The flight plan list can also be displayed at one of the MFDs 439 in addition to or in lieu of being displayed at the CDUs 416. The CDUs 416 also include input devices 415 (e.g., alphanumeric keys) that allow the operators to enter information corresponding to the segments. The operators can also enter inputs for the instruction handler 120 described above at the CDUs 416, the MFDs 439 and/or other devices, e.g., the PFDs 445.
The operator can make a selection (e.g., by mouse clicking on one of the input selectors 561) to accept, load or reject the instruction 521. The conditional instruction handler 224 receives the instruction once it has been accepted, and, optionally, displays the instruction in a graphical manner on one or more visual displays 511 (two are shown in
The mode control panel 650 can include an autoflight portion 658a, a communications portion 658b, and a flight instruments portion 658c. The autoflight portion 658a can include a speed portion 654a (displaying information relating to aircraft speed), a lateral control portion 654b (displaying information relating to the lateral control of the aircraft), and a vertical control portion 654c (displaying information relating to the vertical control of the aircraft). Each portion 654a–654c can include an active display 656 (shown as active displays 656a–656c) and a preview display 655 (shown as preview displays 655a–655c). The active displays 656 indicate the targets to which the aircraft is currently being controlled, and the preview displays 655 can display an upcoming instruction (e.g., a clearance). Accordingly, the conditional instruction handler 224 can display a clearance limit (e.g., 33,000 feet as shown in
In the embodiments described above, each conditional instruction includes a single condition which, when met, can trigger an indication corresponding to the implementation of a single directive. In other embodiments, the instructions can include more than one condition. For example, as shown in
The non-conditional instruction handler 225 and/or the conditional instruction handler 224 can also process instructions that have both non-conditional and conditional aspects in a manner that removes ambiguity from the instruction. For example, an existing instruction might include:
On the other hand, if the speed increase is to be implemented concurrently with the climb, the instruction can read:
One feature of systems in accordance with embodiments described above is that they can distinguish between instructions for a change in a condition of the aircraft (e.g., a flight path direction or change in altitude) that is to be implemented (a) immediately or (b) when a particular condition is met. Accordingly, the system can handle such instructions in different manners to provide the pilot with appropriate notice before and/or when the instruction is to be implemented. An advantage of this feature is that it can be clearer to the operator when the instruction should be implemented and, for automatically implemented instructions, can provide clearer advance notice as to what the instruction will entail.
Another feature of embodiments of systems described above is that they can process instructions that include multiple conditions. Accordingly, such systems can reduce operator confusion which may result when it is unclear whether a given instruction or portion of an instruction is to be implemented immediately and another portion to be implemented conditionally.
Still another feature of systems described above is that they can display in a two-dimensional fashion (e.g., either on a horizontal or vertical display) the location at which the condition is expected to be met. This feature provides the operator with additional advance warning of what action the aircraft will take upon meeting a condition, and how close the aircraft is to meeting the condition.
From the foregoing, it will be appreciated that specific embodiments of the invention have been described herein for purposes of illustration, but that various modifications may be made without deviating from the spirit and scope of the invention. For example, while some of the embodiments described above include particular combinations of features, other embodiments include other combinations of features. Instructions received via a data link or other off-board communication link can be processed automatically in a manner generally similar to that described in co-pending U.S. application Ser. No. 10/798,588, entitled “Methods and Systems for Automatically Displaying Information, Including Air Traffic Control Instructions,” filed concurrently herewith and incorporated herein in its entirety by reference. Accordingly, the invention is not limited except as by the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
3191147 | Majendie | Jun 1965 | A |
4196474 | Buchanan et al. | Apr 1980 | A |
4212064 | Forsythe | Jul 1980 | A |
4247843 | Miller | Jan 1981 | A |
4274096 | Dennnison | Jun 1981 | A |
4325123 | Graham | Apr 1982 | A |
4631678 | Angermuller et al. | Dec 1986 | A |
4792906 | King | Dec 1988 | A |
4860007 | Konicke | Aug 1989 | A |
4899284 | Lewis | Feb 1990 | A |
5050081 | Abbott | Sep 1991 | A |
5070458 | Gilmore et al. | Dec 1991 | A |
5329277 | Dougan et al. | Jul 1994 | A |
5337982 | Sherry | Aug 1994 | A |
5420582 | Kubbat | May 1995 | A |
5454074 | Hartel | Sep 1995 | A |
5499025 | Middleton et al. | Mar 1996 | A |
5668542 | Wright | Sep 1997 | A |
5715163 | Bang | Feb 1998 | A |
5739769 | Vladimir | Apr 1998 | A |
5844503 | Riley et al. | Dec 1998 | A |
5875998 | Gleine | Mar 1999 | A |
5940013 | Vladimir et al. | Aug 1999 | A |
5978715 | Briffe | Nov 1999 | A |
6057786 | Briffe | May 2000 | A |
6085129 | Schardt | Jul 2000 | A |
6098014 | Kranz | Aug 2000 | A |
6112141 | Briffe | Aug 2000 | A |
6118385 | Leard | Sep 2000 | A |
6188937 | Sherry | Feb 2001 | B1 |
6246320 | Monroe | Jun 2001 | B1 |
6262720 | Jeffrey | Jul 2001 | B1 |
6278913 | Jiang | Aug 2001 | B1 |
6313759 | Musland-Sipper | Nov 2001 | B1 |
6314366 | Farmakis et al. | Nov 2001 | B1 |
6346892 | DeMers et al. | Feb 2002 | B1 |
6362750 | Castor | Mar 2002 | B1 |
6381519 | Snyder | Apr 2002 | B1 |
6389333 | Hansman | May 2002 | B1 |
6443399 | Yount et al. | Sep 2002 | B1 |
6542796 | Gibbs et al. | Apr 2003 | B1 |
6556902 | Ng Ing | Apr 2003 | B2 |
6633810 | Qureshi et al. | Oct 2003 | B1 |
6636786 | Partel | Oct 2003 | B2 |
6697718 | Le Draoullec et al. | Feb 2004 | B2 |
6720891 | Chen et al. | Apr 2004 | B2 |
6745113 | Griffin | Jun 2004 | B2 |
6753891 | Chohan et al. | Jun 2004 | B1 |
20020016654 | Ing et al. | Feb 2002 | A1 |
20020033837 | Munro | Mar 2002 | A1 |
20030058134 | Sherry | Mar 2003 | A1 |
20030132860 | Feyereisen | Jul 2003 | A1 |
20030229426 | Griffin | Dec 2003 | A1 |
20040059474 | Boorman | Mar 2004 | A1 |
20040183697 | Rogers et al. | Sep 2004 | A1 |
20040254691 | Subelet | Dec 2004 | A1 |
20060004496 | Tucker et al. | Jan 2006 | A1 |
Number | Date | Country |
---|---|---|
3315386 | Oct 1984 | DE |
0 286 120 | Oct 1988 | EP |
0 370 640 | May 1990 | EP |
0 489 521 | Jun 1992 | EP |
2817831 | Jun 2002 | FR |
2848306 | Jun 2004 | FR |
888136 | Jan 1962 | GB |
WO-0224530 | Mar 2002 | WO |
WO-04027732 | Apr 2004 | WO |
Number | Date | Country | |
---|---|---|---|
20050203676 A1 | Sep 2005 | US |