Embodiments of the subject matter described herein relate generally to avionics systems such as cockpit flight display systems. More particularly, embodiments of the subject matter described herein relate to a system and method for displaying symbology on a cockpit display that relates to an In-Trail Procedure (ITP).
An in-trail procedure (ITP) is a protocol followed by an aircraft that desires to change its current flight level to a new flight level by descending or climbing in front of or behind one or more potentially blocking aircraft flying at an intervening flight level. In accordance with ITP criteria, certain conditions must be satisfied before the flight crew member issues a request for clearance to proceed with the flight level change. Whether or not the conditions are satisfied will depend on a number of dynamically changing factors associated with the host aircraft and other aircraft, such as the current geographic position of the aircraft, the current speed of the aircraft, the current heading of the aircraft, the desired new flight level, and the current flight level.
Modern flight deck instrumentation might include a traffic display that provides a two-dimensional representation of a host aircraft and neighboring aircraft. Such display systems typically provide a number of parameters and visual indicators that enable a pilot to form a quick mental picture of the vertical situation of the host aircraft. For example, such a system might include displays of an aircraft symbol, the aircraft altitude, the vertical flight plan, and terrain. In this manner, a member of the aircraft flight crew can obtain information related to the vertical situation of the aircraft relative to other aircraft with a simple glance at the display system.
Such a system could be used to identify the vertical position of potentially blocking aircraft for purposes of an ITP. However, it is possible that at the moment when the pilot views the ITP display, (1) an intermediate flight level is blocked by traffic that does not meet the ITP distance/speed criteria or (2) the desired flight level is not available because traffic is present with which the host aircraft cannot maintain the standard separation when it climbs to the desired flight level, notwithstanding that at a later time, the opportunity for the ITP transition might exist. It may be necessary for the pilot to repeatedly scan the ITP display in order to detect an opportunity for an ITP transition because the display does not provide any information regarding when an opportunity for a transition to the desired flight level will arise. Thus, the pilot's work load is increased.
Considering the foregoing, it would be desirable to provide a system and method for providing a graphical/textual indication on an ITP display that is representative of the time when an opportunity for an ITP maneuver will be available.
In accordance with the forgoing, there is provided a method for displaying ITP opportunities on an onboard display device of a host aircraft flying at a first flight level. The method comprises obtaining flight status data of the host aircraft and at least a first neighboring aircraft flying at a second flight level, processing the flight status data of the host aircraft and the neighboring aircraft to determine a first predicted time within which an ITP transition through the second flight level to a desired flight level can be made, rendering on the onboard display device a graphical representation of the host aircraft and the neighboring aircraft, and rendering the first predicted time on the onboard display device.
There is also provided a method for predicting ITP opportunities for a host aircraft desiring to transition from a first flight level to a second flight level, wherein neighboring aircraft occupy flight levels between the first and second flight levels. The method comprises predicting a set of optimum flight level availability times, predicting a set of intermediate flight level availability times, predicting a time-set of ITP opportunities, and rendering on a display device symbology visually representative of the ITP opportunities.
An onboard flight display system, deployed on a host aircraft, for displaying ITP opportunities while flying at a first flight level, is also provided. The system comprises an on-board display device and a processor operatively coupled to the display device and configured to (1) process flight status data of the host aircraft and at least one neighboring aircraft flying at a second flight level, (2) determine a predicted time within which the host aircraft can perform an ITP transition through the second flight level to a third flight level, and (3) render the predicted time on the display device.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
A more complete understanding of the subject matter may be derived by referring to the detailed description and claims when considered in conjunction with the following figures, wherein like reference numbers refer to similar elements throughout the figures.
The following detailed description is merely illustrative in nature and is not intended to limit the embodiments of the subject matter or the application and uses of such embodiments. As used herein, the word “exemplary” means “serving as an example, instance, or illustration.” Any implementation described herein as exemplary is not necessarily to be construed as preferred or advantageous over other implementations. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the following detailed description.
Techniques and technologies may be described herein in terms of functional and/or logical block components, and with reference to symbolic representations of operations, processing tasks, and functions that may be performed by various computing components or devices. Such operations, tasks, and functions are sometimes referred to as being computer-executed, computerized, software-implemented, or computer-implemented. In practice, one or more processor devices can carry out the described operations, tasks, and functions by manipulating electrical signals representing data bits at memory locations in the system memory, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to the data bits. It should be appreciated that the various block components shown in the figures may be realized by any number of hardware, software, and/or firmware components configured to perform the specified functions. For example, an embodiment of a system or a component may employ various integrated circuit components, e.g., memory elements, digital signal processing elements, logic elements, look-up tables, or the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices.
For the sake of brevity, conventional techniques related to graphics and image processing, navigation, flight planning, aircraft controls, aircraft data communication systems, and other functional aspects of certain systems and subsystems (and the individual operating components thereof) may not be described in detail herein. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in an embodiment of the subject matter.
Although not always required, the techniques and technologies described here are suitable for use by aircraft using an ITP in an oceanic (or other) track system. For example, the techniques and technologies presented here could be used in connection with the ITP as defined and explained in the Safety, Performance and Interoperability Requirements Document for the In-Trail Procedure in Oceanic Airspace (ATSA-ITP) Application, RTCA/DO-312, Jun. 19, 2008. For ease of understanding and clarity, the following description employs terminology that is consistent with that used in the RTCA/DO-312 document. Moreover, the relevant portions of the RTCA/DO-312 document are incorporated by reference herein.
The RTCA/DO-312 document specifies that an in-trail procedure is a procedure that is employed by an aircraft that desires to change its flight level to a new flight level by climbing or descending in front or behind one or two, or between two same tracks, potentially blocking aircraft which are at an intervening flight level. A potentially blocking aircraft is an aircraft at an intervening flight level whose ADS-B data is available to the aircraft wishing to conduct an ITP maneuver. The host aircraft and any neighboring aircraft of interest (i.e., a potentially blocking aircraft) must be same track aircraft in order for an ITP flight level change to be requested. In this regard, “same track” means same direction tracks and intersecting tracks (or portions thereof) the angular difference of which is less than 45 degrees or more than 315 degrees. As an example,
As stated above, ITP is a protocol that can be followed when an aircraft seeks to change its flight level to a new flight level in the presence of potentially blocking aircraft located at an intervening flight level. For example,
RTCA/DO-312 defines reference aircraft as one or two similar track, potentially blocking aircraft no more than: 3,000 feet above or below the initial flight level, if vertical separation is 1,000 feet; or 2,000 feet above or below the initial flight level, if the vertical separation minima is 2,000 feet; with qualified ADS-B data that meets ITP speed/distance criteria and that will be identified to ATC by the ITP aircraft as part of the ITP clearance request. At least one of two ITP speed/distance criteria must be met: (1) if the ITP distance to a reference aircraft 136 is greater than or equal to 15 nautical miles, then the groundspeed differential between the two aircraft must be less than or equal to 20 knots; or (2) if the ITP distance to a reference aircraft 136 is greater than or equal to 20 nautical miles, then the groundspeed differential between the two aircraft must be less than or equal to 30 knots.
The ITP distance represents one appropriate measure of distance between the host aircraft and a nearby reference aircraft and potentially blocking, same track aircraft, which may be in front of or behind the host aircraft. Depending upon the particular embodiment, other distance metrics, distance measures, or relative spacing metrics could be used. For instance, the system could contemplate linear distance, time, aircraft acceleration, relative speed, closing rate, and/or other measureable or computable values that are dependent on the current geographic position, speed, acceleration, heading, attitude, or other operating status of the aircraft. The RTCA/DO-312 document defines the ITP distance as the distance between reference or potentially blocking aircraft and the ITP aircraft as defined by the difference in distance to a common point along each aircraft's track. In this regard,
As another example,
The systems and methods presented herein can be utilized to predict and display opportunities for ITP transitions. It is also contemplated that the proposed systems and methods will determine and display the time when a desired flight level and intermediate flight levels will become available.
In a first scenario, it is contemplated that a Flight Management System (FMS) will predict the optimum climb/descent altitudes. These are provided to a traffic computer or ITP display that determines the ITP transition possibilities for the predicted altitude based on received ADS-B IN data. The traffic computer, in turn, predicts different time sets and the corresponding candidate reference aircraft for the flight level changes proposed by the FMS. This prediction includes a consideration of the host aircraft's ground speed to predict the ITP transition times, which are displayed on the ITP display as will be shown and described hereinafter.
In a second scenario, it is contemplated that a pilot selects a desired flight level change using the ITP display. The traffic computer then predicts a set of ITP opportunities available for transition to the desired flight level, which are displayed on the ITP display as in the first scenario.
In both scenarios, the traffic computer considers (1) all traffic present at the desired flight level and the closing or separating ground speed of the traffic intruders with respect to the host aircraft, and (2) the intent of the traffic from the traffic's ADS-B OUT transmissions; e.g. when the traffic is planning to change flight level and/or transition from the host aircraft's desired flight level. The traffic computer determines the time when an intermediate flight level will become available for transition. It considers the present position and ground speed difference of aircraft present in the intermediate flight level and determines when not more than two aircraft will be sufficiently separated to meet the criteria to be considered candidate reference aircraft. The traffic computer also validates that all other aircraft present in the intermediate flight level meet standard separation criteria with the host aircraft.
Thus, it is contemplated that the system and methods provided herein will determine, for each ITP opportunity: (1) a desired flight level, (2) the desired flight level availability time determined in accordance with the requirement of providing required standard separation with aircraft at the desired flight level, (3) the availability time of intermediate flight levels, (4) a maximum of two candidate reference aircraft with which the host aircraft can conduct an ITP transition for that flight level at the available time, and (5) the time duration of the ITP opportunity consisting of an ITP Start Time and an ITP End Time in minutes and seconds from the current time or in Greenwich Mean Time (Zulu Time). The time when the host aircraft can request an ITP transition and the candidate reference aircraft will be displayed.
The above described displays can be generated using a suitably configured onboard system, such as a flight deck display system. More preferably, the display can be generated by the traffic computer that may receive data from the Flight Management System (FMS). In this regard,
The processor 202 may be implemented or realized with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination designed to perform the functions described here. A processor device may be realized as a microprocessor, a controller, a microcontroller, or a state machine. Moreover, a processor device may be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration. As described in more detail below, the processor 202 obtains and processes current flight status data (of the host aircraft and one or more candidate reference aircraft and other neighboring aircraft) to determine ITP transition opportunities and to control the rendering of the ITP display in an appropriate manner.
The memory 204 may be realized as RAM memory, flash memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, the memory 204 can be coupled to the processor 202 such that the processor 202 can read information from, and write information to, the memory 204. In the alternative, the memory 204 may be integral to the processor 202. As an example, the processor 202 and the memory 204 may reside in an ASIC. In practice, a functional or logical module/component of the display system 200 might be realized using program code that is maintained in the memory 204. For example, the graphics system 208, the data communication module 212, or the datalink subsystem 214 may have associated software program components that are stored in the memory 204. Moreover, the memory 204 can be used to store data utilized to support the operation of the display system 200, as will become apparent from the following description.
In an exemplary embodiment, the display element 206 is coupled to the graphics system 208. The graphics system 208 is coupled to the processor 202 such that the processor 202 and the graphics system 208 cooperate to display, render, or otherwise convey one or more graphical representations, synthetic displays, graphical icons, visual symbology, or images associated with operation of the host aircraft on the display element 206, as described in greater detail below. An embodiment of the display system 200 may utilize existing graphics processing techniques and technologies in conjunction with the graphics system 208. For example, the graphics system 208 may be suitably configured to support well known graphics technologies such as, without limitation, VGA, SVGA, UVGA, or the like.
In an exemplary embodiment, the display element 206 is realized as an electronic display configured to graphically display flight information or other data associated with operation of the host aircraft under control of the graphics system 208. In practice, the processor 202 and/or the graphics system 208 produces image rendering display commands that are received by the display element 206 for purposes of rendering the display. The display element 206 is usually located within a cockpit of the host aircraft. It will be appreciated that although
The illustrated embodiment of the display system 200 includes a user interface 210, which is suitably configured to receive input from a user (e.g., a pilot) or other crew member and, in response to the user input, supply appropriate command signals to the processor 202. The user interface 210 may be any one, or any combination, of various known user interface devices or technologies, including, but not limited to: a touchscreen, a cursor control device such as a mouse, a trackball, or joystick; a keyboard; buttons; switches; or knobs. Moreover, the user interface 210 may cooperate with the display element 206 and the graphics system 208 to provide a graphical user interface. Thus, a user can manipulate the user interface 210 by moving a cursor symbol rendered on the display element 206, and the user may use a keyboard to, among other things, input textual data. For example, the user could manipulate the user interface 210 to enter a desired or requested new flight level into the display system 200.
In an exemplary embodiment, the data communication module 212 is suitably configured to support data communication between the host aircraft and one or more remote systems. More specifically, the data communication module 212 is used to receive current flight status data 222 of other aircraft that are near the host aircraft. In particular embodiments, the data communication module 212 is implemented as an aircraft-to-aircraft data communication module that receives flight status data from an aircraft other than the host aircraft. For example, the data communication module 212 may be configured for compatibility with Automatic Dependent Surveillance-Broadcast (ADS-B) technology, with Traffic and Collision Avoidance System (TCAS) technology, and/or with similar technologies.
The flight status data 222 may include, without limitation: airspeed data; fuel consumption; groundspeed data; altitude data; attitude data, including pitch data and roll data; yaw data; geographic position data, such as GPS data; time/date information; heading information; weather information; flight path data; track data; radar altitude data; geometric altitude data; wind speed data; wind direction data; etc. The display system 200 is suitably designed to process the flight status data 222 in the manner described in more detail herein. In particular, the display system 200 can use the flight status data 222 when rendering the ITP display.
The data link subsystem 214 enables the host aircraft to communicate with Air Traffic Control (ATC). In this regard, the data link subsystem 214 may be used to provide ATC data to the host aircraft and/or to send information from the host aircraft to ATC, preferably in compliance with known standards and specifications. Using the data link subsystem 214, the host aircraft can send ITP requests to ground based ATC stations and equipment. In turn, the host aircraft can receive ITP clearance or authorization from ATC (when appropriate) such that the pilot can initiate the requested flight level change.
In operation, the display system 200 is also configured to process the current flight status data for the host aircraft. In this regard, the sources of flight status data 216 generate, measure, and/or provide different types of data related to the operational status of the host aircraft, the environment in which the host aircraft is operating, flight parameters, and the like. In practice, the sources of flight status data 216 may be realized using line replaceable units (LRUs), transducers, accelerometers, instruments, sensors, and other well-known devices. The data provided by the sources of flight status data 216 may include, without limitation: airspeed data; groundspeed data; altitude data; attitude data, including pitch data and roll data; yaw data; geographic position data, such as GPS data; time/date information; heading information; weather information; flight path data; track data; radar altitude data; geometric altitude data; wind speed data; wind direction data; fuel consumption, etc. The display system 200 is suitably designed to process data obtained from the sources of flight status data 216 in the manner described in more detail herein. In particular, the display system 200 can use the flight status data of the host aircraft when rendering the ITP display.
As previously stated, in a first scenario the FMS provides the optimum altitude considering aircraft performance and weather conditions, and in a second scenario, the pilot selects the optimum altitude. In both scenarios, the ITP prediction algorithm, discussed herein below, is utilized. In an embodiment, the pilot's flight level selection takes priority over the FMS.
Flight Management System 201 is a specialized computer that automates a variety of in-flight tasks such as in-flight management of the flight plan. Using various sensors, the FMS determines the aircrafts position and guides the aircraft along its flight plan using its navigation database. Traffic Computer 203 processes surveillance data using ADS-B reports from the ADS-B receive function, and performs application specific processing. Surveillance reports, tasks, and any application specific information, e.g., alerts or guidance cues, are output to the traffic display function.
As stated previously, FMS 201 is integrated with the traffic computer 203 (
Referring now to
A “PREVIOUS” scroll button 320 and a “NEXT” scroll button 322 are also provided in the event that multiple ITP opportunities are available. These scroll buttons permit a pilot to review successive ITP opportunities in ascending order from the current start time. Each time the next ITP Opportunity is selected for review, the candidate reference aircraft for that set is shown on the ITP display. After the pilot initiates an ITP procedure (i.e. selects one of the ITP opportunity sets and sends an ITP request to Air Traffic Control (ATC)), the ITP prediction symbology is removed from the display. If only a single opportunity can be calculated, the NEXT and PREVIOUS buttons will be disabled or removed. Finally, referring again to
In the case when the FMS cannot predict the optimum altitude or the FMS predicted optimum altitude is not supplied to the traffic computer, a pilot selected flight level is treated as the desired flight level for which the ITP opportunities are calculated as described above.
In practice, process 600 can be performed in a virtually continuous manner at a relatively high refresh rate such that the display will be updated in real-time or substantially real time in a dynamic manner. This particular embodiment of process 600 begins (STEP 602) by obtaining data of the type described in conjunction with
Process 600 may be performed in connection with an ITP routine, during which the pilot or other flight crew member desires to change the altitude (flight level) of the host aircraft. Accordingly, process 600 may acquire a requested or optimum new flight level that is different than the current flight level of the host aircraft. This may be associated with user manipulation of a user interface element, e.g., manual entry of the new flight level. In a preferred embodiment, one or more ITP transitions may be predicted by ITP prediction algorithm.
The particular embodiment of the process 600 begins (STEP 600) by obtaining current flight status data of the host aircraft (STEP 602). Flight status data of one or more other aircraft proximate the host aircraft is also obtained (STEP 604). In addition to the flight status data of the host and neighboring aircraft, the processed data may include the respective flight levels of host and neighboring aircraft and the flight level of the requested new flight level. The ITP opportunity times may be based on some or all of this data. For example, the opportunity times may be determined by processing the data from the host aircraft, neighboring aircraft, candidate reference aircraft, and the desired flight level.
As stated previously, the FMS may determine the optimum flight level or the pilot may select a desired flight level. In either case, the remainder of the process is the same. Thus, method 600 continues by detecting the occurrence of either the FMS determining an optimum flight level (STEP 606) or the pilot requesting a desired flight level (STEP 608). A technique such as that referred to in STEP 606 is described in U.S. Pat. No. 5,574,647 entitled “Apparatus and Method for Computing Wind-Sensitive Optimum Altitude Steps in a Flight Management System” issued Nov. 12, 1996 and assigned to the assignee of the present invention. The pilot has priority regarding whether the FMS or the pilot selects the flight level.
In either event, the processor 202 (
Next, processor 202 or traffic computer 203 evaluates and predicts the set of intermediate flight level availability times Tint (TintFL1, Ref1, Ref2) . . . (TintFLn, Refx, Refy) (STEP 612). Each intermediate flight level availability time consists of a start time and end time determined using ITP distance speed criteria for at most two potentially blocking aircraft. Optionally, the intermediate flight availability start times are displayed.
Processor 202 or traffic computer 203, as the case may be, next predicts a time set for ITP opportunities. T1, Ref1, Ref2 . . . Tn, Refx, Refy using the ToptFL and TintFL time sets determined in STEP 610 and STEP 612 (STEP 614). This may be accomplished as follows. First, the desired flight level availability is determined. Next, the intermediate flight level availability times are determined for each intermediate flight level. There can be one or multiple flight levels and one or more availability times for each flight level. The ITP opportunity start time is the time when the desired flight level is not blocked and the intermediate flight levels are non-blocking The ITP end time is the time when the desired flight level becomes blocked or any one of the intermediate flight levels becomes blocking The ITP opportunity time is the time set consisting of the ITP opportunity start time and the ITP opportunity end time. These steps may be repeated to obtain the next ITP opportunity time.
To determine intermediate flight level availability times, it is first necessary to identify candidate reference aircraft by first identifying a maximum of two aircraft in intervening aircraft which take minimum time to satisfy ITP distance/speed criteria and consider them as candidate reference aircraft. If an intervening flight level contains only one candidate reference aircraft and no other aircraft, then the intermediate level availability start time is the time the candidate reference aircraft meets ITP distance/speed criteria. If an intermediate flight level contains two candidate reference aircraft and no other aircraft, then the intermediate flight level availability start time is the time both candidate reference aircraft meet the ITP distance/speed criteria. If an intervening flight level contains one or both candidate reference aircraft and one or more potentially blocking aircraft, then the intermediate flight level availability start time is the is the time when the candidate reference aircraft meet the ITP distance/speed criteria and the other potentially blocking aircraft meet standard separation.
If an intervening flight level contains only one candidate reference aircraft and no other aircraft, then the intermediate level availability end time is the time the candidate reference aircraft fails to meet ITP distance/speed criteria. If an intermediate flight level contains two candidate reference aircraft and no other aircraft, then the intermediate flight level availability end time is the time when any candidate reference aircraft fails to meet the ITP distance/speed criteria. If an intervening flight level contains one or both candidate reference aircraft and one or more potentially blocking aircraft, then the intermediate flight level availability end time is the is the time when any one of the candidate reference aircraft fails to meet the ITP distance/speed criteria and any one of the other potentially blocking aircraft fails to meet standard separation. Finally, the time set of ITP opportunities is displayed on display element 206 or ITP display 205, as the case may be, with possible candidate reference aircraft (STEP 616).
If no ITP opportunities can be determined because either the desired flight level or any one of the intermediate flight levels is always blocked, the ITP opportunity time can be displayed in a manner that is visually representative of the fact that an ITP transition is not possible; e.g. FL 123/NO ITP. If all traffic at the intermediate flight levels is separated as per standard longitudinal separation from the ownship and the desired flight level is not blocked, then the ITP opportunity time may be displayed in a manner to reflect that an ITP maneuver is not required; e.g. FL 123/STANDARD CLIMB/DESCENT.
Thus, there has been provided a system and method for providing a graphical/textual indication on a cockpit display that is representative of the time when an opportunity for an ITP maneuver will be available.
While at least one exemplary embodiment has been presented in the foregoing detailed description, it should be appreciated that a vast number of variations exist. For example, the techniques and methodologies presented here could also be deployed as part of a fully automated guidance system to allow the flight crew to monitor and visualize the execution of automated maneuvers. It should also be appreciated that the exemplary embodiment or embodiments described herein are not intended to limit the scope, applicability, or configuration of the claimed subject matter in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing the described embodiment or embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the scope defined by the claims, which includes known equivalents and foreseeable equivalents at the time of filing this patent application.
Number | Name | Date | Kind |
---|---|---|---|
3875379 | Vietor | Apr 1975 | A |
5077673 | Brodegard et al. | Dec 1991 | A |
5574647 | Liden | Nov 1996 | A |
5957412 | Saint Upery et al. | Sep 1999 | A |
6085145 | Taka et al. | Jul 2000 | A |
6127944 | Daly et al. | Oct 2000 | A |
6148259 | Hagelauer | Nov 2000 | A |
6433729 | Staggs | Aug 2002 | B1 |
6690298 | Barber et al. | Feb 2004 | B1 |
6696980 | Langner et al. | Feb 2004 | B1 |
6711479 | Staggs | Mar 2004 | B1 |
6720891 | Chen et al. | Apr 2004 | B2 |
6799114 | Etnyre | Sep 2004 | B2 |
6816780 | Naimer et al. | Nov 2004 | B2 |
6828921 | Brown et al. | Dec 2004 | B2 |
6839018 | Szeto et al. | Jan 2005 | B2 |
6876906 | Zellers et al. | Apr 2005 | B1 |
6946976 | Langner et al. | Sep 2005 | B1 |
6963291 | Holforty et al. | Nov 2005 | B2 |
7103455 | Subelet | Sep 2006 | B2 |
7148816 | Carrico | Dec 2006 | B1 |
7366591 | Hartmann et al. | Apr 2008 | B2 |
7367526 | Baudry | May 2008 | B2 |
7375678 | Feyereisen et al. | May 2008 | B2 |
7386373 | Chen et al. | Jun 2008 | B1 |
7403843 | Gremmert | Jul 2008 | B2 |
7453375 | Chamas et al. | Nov 2008 | B2 |
7471995 | Robinson | Dec 2008 | B1 |
7570178 | Whalen et al. | Aug 2009 | B1 |
7650232 | Paielli | Jan 2010 | B1 |
7746343 | Charaniya et al. | Jun 2010 | B1 |
7747382 | Small et al. | Jun 2010 | B2 |
7877197 | Lewis et al. | Jan 2011 | B2 |
7961135 | Smith et al. | Jun 2011 | B2 |
7965223 | McCusker | Jun 2011 | B1 |
8271152 | Singer et al. | Sep 2012 | B2 |
8403259 | Charuel et al. | Mar 2013 | B2 |
20020075171 | Kuntman et al. | Jun 2002 | A1 |
20020089432 | Staggs et al. | Jul 2002 | A1 |
20020133294 | Farmakis et al. | Sep 2002 | A1 |
20030016158 | Stayton et al. | Jan 2003 | A1 |
20030102987 | Walter | Jun 2003 | A1 |
20060065779 | McCoskey et al. | Mar 2006 | A1 |
20060290562 | Ehresman | Dec 2006 | A1 |
20080065312 | Coulmeau et al. | Mar 2008 | A1 |
20080109163 | Stone et al. | May 2008 | A1 |
20080120032 | Brandao et al. | May 2008 | A1 |
20080266054 | Crank | Oct 2008 | A1 |
20080288164 | Lewis et al. | Nov 2008 | A1 |
20080309518 | Aung | Dec 2008 | A1 |
20090024311 | Hess | Jan 2009 | A1 |
20090088972 | Bushnell | Apr 2009 | A1 |
20090231163 | He | Sep 2009 | A1 |
20090267800 | Hammack et al. | Oct 2009 | A1 |
20100023187 | Gannon et al. | Jan 2010 | A1 |
20100070180 | Ridenour | Mar 2010 | A1 |
20100131121 | Gerlock | May 2010 | A1 |
20100152932 | Das | Jun 2010 | A1 |
20100286900 | Depape et al. | Nov 2010 | A1 |
20100292871 | Schultz et al. | Nov 2010 | A1 |
20100305783 | Tucker et al. | Dec 2010 | A1 |
20100332054 | Brandao et al. | Dec 2010 | A1 |
20110006918 | Shafaat et al. | Jan 2011 | A1 |
20110066360 | Haissig | Mar 2011 | A1 |
20110066362 | He | Mar 2011 | A1 |
20110118981 | Chamlou | May 2011 | A1 |
20110144833 | Tjorhom et al. | Jun 2011 | A1 |
20110187588 | Khatwa et al. | Aug 2011 | A1 |
20110224847 | Singer et al. | Sep 2011 | A1 |
20110231096 | Ridenour, II | Sep 2011 | A1 |
20110270472 | Shafaat et al. | Nov 2011 | A1 |
20110270473 | Reynolds et al. | Nov 2011 | A1 |
20110276198 | Khatwa et al. | Nov 2011 | A1 |
20110282568 | Khatwa et al. | Nov 2011 | A1 |
20110316857 | Pepitone et al. | Dec 2011 | A1 |
20130057414 | Nutaro et al. | Mar 2013 | A1 |
20130131888 | Nutaro et al. | May 2013 | A1 |
Number | Date | Country |
---|---|---|
1752739 | Feb 2007 | EP |
1752739 | Jan 2008 | EP |
1947624 | Jul 2008 | EP |
2071542 | Jun 2009 | EP |
2345872 | Jul 2011 | EP |
2388759 | Nov 2011 | EP |
2898675 | Mar 2006 | FR |
2910124 | Dec 2006 | FR |
Entry |
---|
Chartrand, R. C. et al.; Operational Improvements From Using the In-Trail Procedure in the North Atlantic Organized Track System, Oct. 2009. |
Murdoch, J. L. et al.; Enhanced Oceanic Operations Human-In-The-Loop In-Trail Procedure Validation Simulation Study, NASA/TP-2008-215313, Jun. 2008. |
Jones, K.M.; ADS-B In-Trail Procedures, Overview of Research Results; National Aeronautics and Space Administration; Presented to the ASAS TN2 Workshop, Sep. 2007. |
Alam, S, et al.; An Assessment of BADA Fuel Flow Methodologies for In-Trail Procedure Evaluation; Defence & Security Applications Research Centre, University of New South Wales, Australian Defence Force Academy, Canberra, Australia. |
Munoz, C.A. et al.; In-Trail Procedure (ITP) Algorithm Design; National Institute of Aerospace; Hampton, VA. |
Richards, W.R. et al.; New Air Traffic Surveillance Technology; www.boeing.com/commercial/aeromagazine. |
EP Examination Report for EP 11 154 857.4, dated Aug. 30, 2013. |
EP Search Report for Application No. 13 155 828.0 dated Nov. 19, 2013. |
USPTO Office Action for U.S. Appl. No. 13/407,475; notification date Nov. 21, 2012. |
EP Search Report, EP11 154 857.4, dated Apr. 11, 2012. |
EP Examination Report for EP 11 154 857.4, dated May 22, 2012. |
Haissig C. M. et al. “Using TCAS Surveillance to Enable Legacy ADS-B Transponder Use for In-trail Procedures” Digital Avionics Systems Conference (DASC), IEEE/AIAA 31st; published by IEEE on Oct. 14, 2012; pp. 5D5-1. |
“Getting to Grips with Surveillance”—Airbus; retrieved from the Internet on Nov. 20, 2013, URL: URL:http://www.cockpitseeker.com/wp-content/uploads/A320/pdf/data/gettingToGripsSurveillanceIssue1.pdf. |
EP Search Report for Application No. EP 13 150 717.0 dated Dec. 3, 2013. |
RTCA, Inc.; Safety, Performance and Interoperability Requirements Document for the In-Trail Procedure in Oceanic Airspace (ATSA-ITP) Application; RTCA/DO-312, Jun. 19, 2008. |
USPTO Office Action for U.S. Appl. No. 12/563,691; notification date Dec. 9, 2011. |
USPTO Final Office Action for U.S. Appl. No. 12/563,691; notification date Mar. 30, 2012. |
USPTO Final Office Action for U.S. Appl. No. 13/407,475; notification date Feb. 6, 2013. |
EP Search Report dated May 6, 2013 for application No. EP 11 154 900.2. |
USPTO Office Action for U.S. Appl. No. 12/774,513; Notification date May 2, 2012. |
USPTO Final Office Action for U.S. Appl. No. 12/774,513; notification date Aug. 30, 2012. |
Chartrand et al.; Operational Improvements form the In-Trail Procedure in the North Atlantic Organized Track System; American Institure of Aeronautics and Astronautics. |
Federal Aviation Administration; NextGen Operator and Airport Enablers; Supplement to NextGen Investment for Operators and Airports, FAA's NextGen Implementation Plan, Mar. 2011. |
USPTO Office Action for U.S. Appl. No. 12/721,146; Notification Date Jan. 9, 2012. |
USPTO Office Action for U.S. Appl. No. 13/463,657 dated Jun. 4, 2013. |
Koeners, J.; deVries, M.; Delft University of Technology, Delft, The Netherlands; Conflict Resolution Support for Air Traffic Control Based on Solution Spaces: Design and Implementation; 2008 IEEE. |
EP Search Report, EP 10 166 821.8, dated Apr. 21, 2011. |
EP Communication for EP 10 166 821.8 dated May 23, 2011. |
USPTO Notice of Allowance for U.S. Appl. No. 12/721,146; notification date Jun. 7, 2012. |
EP Search Report for Application No. 13 157 907.0 dated Feb. 4, 2014. |
EP Examination Report for Application No. 13 157 907.0 dated Feb. 13, 2014. |
USPTO Notice of Allowance for U.S. Appl. No. 12/774,513; notification date Dec. 11, 2012. |
Number | Date | Country | |
---|---|---|---|
20130245927 A1 | Sep 2013 | US |