Abstract:
A system includes a memory device, and a processor coupled to the memory device. The processor is configured to receive, in a first time interval, from a first component a signal indicating an altitude of the aircraft, from a second component a signal indicating a first heading of the aircraft, and from a third component a signal indicating a first position of the aircraft. The processor is further configured to receive, in a second time interval later than the first time interval, and from the second and third components, signals respectively indicating a second heading and second position of the aircraft. The processor does not receive a signal from the first component in the second time interval. The processor is further configured to determine an estimated altitude of the aircraft and a geometric altitude of the aircraft.

Description:
BACKGROUND OF THE INVENTION 
       [0001]    The leading cause of worldwide aviation fatalities comes from inadvertently flying a perfectly operating aircraft into ground or water. This type of accident is referred to as Controlled Flight into Terrain (CFIT). Common causes of CFIT accidents are due to loss of radio altimeter altitude input to the enhanced ground proximity warning system (EGPWS). Altitude information from the radio altimeter (RA) is one of the critical inputs to derive the geometric altitude for EGPWS. An approach to calculation of geometric altitude is described in commonly owned U.S. Pat. No. 6,216,064. 
         [0002]    Geometric Altitude uses an improved pressure altitude calculation, GPS Altitude, Radio Altitude, and Terrain and Runway elevation data to reduce or eliminate errors potentially induced in Corrected Barometric Altitude by temperature extremes, non-standard altitude conditions, and altimeter mis-sets. The final Geometric Altitude is computed by combining the three computed component altitudes with optional Corrected Barometric altitude. The weighting of each altitude in the final solution is based on the corresponding estimated (vertical figure of merit) VFOM. The blending algorithm gives the most weight to altitudes with a higher estimated accuracy, reducing the effect of less accurate altitudes on the final computed altitude. Each component altitude is also checked for reasonableness using a window monitor computed from GPS Altitude and GPS VFOM. Altitudes that are invalid, not available, or fall outside the reasonableness window are not included in the final blended altitude. 
         [0003]    Radio Altitude Calibrated Altitude is a calibration of Non-Standard Altitude during approach using an altitude derived from radio altitude (height above terrain) and the terrain elevation data stored in the EGPWS terrain database. This calibration is performed during the approach phase of flight when the aircraft is within a minimum distance and elevation of any runway. Once a correction factor is determined, it is applied to Non-Standard Altitude (or Standard Altitude) until the aircraft lands. 
         [0004]    In the event of RA failure, or failure of any other instrument providing altitude information, the determination of geometric altitude is severely compromised. 
       SUMMARY OF THE INVENTION 
       [0005]    In an embodiment, a system includes a memory device, and a processor coupled to the memory device. The processor is configured to receive, in a first time interval, from a first component a signal indicating an altitude of the aircraft, from a second component a signal indicating a first heading of the aircraft, and from a third component a signal indicating a first position of the aircraft. The processor is further configured to receive, in a second time interval later than the first time interval, and from the second and third components, signals respectively indicating a second heading and second position of the aircraft. The processor does not receive a signal from the first component in the second time interval. The processor is further configured to determine an estimated altitude of the aircraft and a geometric altitude of the aircraft. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0006]    Preferred and alternative embodiments of the present invention are described in detail below with reference to the following drawings. 
           [0007]      FIG. 1  illustrates elements of an exemplary system formed in accordance with an embodiment of the present invention; 
           [0008]      FIGS. 2-4  illustrate a process according to an embodiment of the invention; 
           [0009]      FIG. 5  conceptually illustrates the functionality of a memory device according to an embodiment; and 
           [0010]      FIGS. 6-9  illustrate altitude prediction according to an embodiment. 
       
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT 
       [0011]    An embodiment of the invention is directed towards prediction of the aircraft altitude in the event of failure of RA, or loss of altitude information from any other sensor, serving as input to calculate the Geometric Altitude for EGPWS using the blending algorithm and continue providing this information to EGPWS until VFR (visual flight rules) condition is reached during the approach phase and until the operational range limit of the RA during climb-out phases of flight is reached. 
         [0012]    An embodiment of the invention is directed towards an Altitude Prediction approach for estimating and predicting the aircraft altitude to the TA&amp;D function of the EGPWS by maintaining the integrity of the existing blending algorithm to calculate the Geometric Altitude for the EGPWS. Unlike conventional approaches, an embodiment accrues and stores the predicted altitude information. This altitude data is ‘volumetric’ or ‘three-dimensional,’ because it is built from and constantly updated by systematic calculation of predicted height information in the area in front of the airplane over the flight path angle. 
         [0013]    An embodiment of the invention computationally “builds” the equivalent of a cuboid in space in front of the airplane. The present position of the aircraft is stored in a 3-D buffer, so that this information can be used to calculate the predicted position over a range of two voxels, for example, apart along the flight path angle. The predicted positions/altitude information are stored in the 3-D buffer continuously. In the event of system failure of Radio Altimeter or any other sensor input to the blending algorithm, the information is extracted from this buffer and replenished as an input to computation of RA Calibrated Altitude, or similar corresponding input. The altitude information stored in the buffer is not only extracted and provided to EGPWS but also may be used to calculate the subsequent altitude information/aircraft position with respect to the cells in the buffer based on the flight path angle with a high degree of accuracy. During the critical approach phase this information continues to be provided to the EGPWS until the Decision height or conditions for a VFR approach is reached. 
         [0014]    An embodiment of the invention can be yet another mode of EGPWS. For example, the activation of this mode can be based on the RA failure (or any other sensor failure). The EGPWS can indicate this failure with the usual RED indicator lamp. There could be the sounding of a caution alarm as “Radio Altimeter failure” (or any other corresponding sensor failure) so that the pilot remains in auto-pilot mode or can stay on the flight plan course with as little deviation as possible. Such would result in accurate prediction of RA information from the 3-D Buffer prediction approach discussed herein. However, if there is still a deviation in the flight course from the stored flight plan, the heading information from an inertial navigation system (INS) could be used, as well. 
         [0015]    Embodiments of the invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer and/or by computer-readable media on which such instructions or modules can be stored. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices. 
         [0016]    According to one or more embodiments, the combination of software or computer-executable instructions with a computer-readable medium results in the creation of a machine or apparatus. Similarly, the execution of software or computer-executable instructions by a processing device results in the creation of a machine or apparatus, which may be distinguishable from the processing device, itself, according to an embodiment. 
         [0017]    Correspondingly, it is to be understood that a computer-readable medium is transformed by storing software or computer-executable instructions thereon. Likewise, a processing device is transformed in the course of executing software or computer-executable instructions. Additionally, it is to be understood that a first set of data input to a processing device during, or otherwise in association with, the execution of software or computer-executable instructions by the processing device is transformed into a second set of data as a consequence of such execution. This second data set may subsequently be stored, displayed, or otherwise communicated. Such transformation, alluded to in each of the above examples, may be a consequence of, or otherwise involve, the physical alteration of portions of a computer-readable medium. Such transformation, alluded to in each of the above examples, may also be a consequence of, or otherwise involve, the physical alteration of, for example, the states of registers and/or counters associated with a processing device during execution of software or computer-executable instructions by the processing device. 
         [0018]      FIG. 1  illustrates an example of a suitable operating environment in which the invention may be implemented. The operating environment is only one example of a suitable operating environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. The operating environment may include or be a component of a three-dimensional buffer processing system, such as the RDR-4000 weather radar system manufactured by Honeywell®, including its volumetric buffer technology. Other well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. 
         [0019]    The operating environment illustrated in  FIG. 1  typically includes at least some form of computer readable media. Computer readable media can be any available media that can be accessed by one or more components of such operating environment. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by one or more components of such operating environment. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer readable media. 
         [0020]      FIG. 1  illustrates a system  500  that includes a processing device, such as an EGPWS  510 , which in turn includes a database  520 , an alerting algorithm component  522 , and a maneuvering algorithm component  524 . EGPWS  510  may include or be otherwise coupled to a 3-D buffer memory device  511 . The database  520  includes geographic locations and horizontal and vertical extents of local protected airspace. The EGPWS  510  interfaces with airplane systems  530 ,  532  and  534  to provide knowledge of the airplane position (latitude, longitude, altitude), horizontal velocity, vertical velocity (or flight path angle) and track angle. The system  532  may include, for example, a radio altimeter (not shown). Additionally, if guidance commands are desired, knowledge of airplane pitch attitude, roll attitude and heading may be required. 
         [0021]    The alerting algorithm component  522  determines if the airplane is predicted to encroach on any protected airspace volume. The EGPWS  510  includes an aural message generator that provides audible information to the pilot after the alerting algorithm component  522  determined that there is imminent conflict with a protected airspace. The maneuvering algorithm component  524  generates guidance commands for output to the pilot or an automatic flight control system  540  for avoiding the protected airspace. 
         [0022]      FIG. 5  illustrates conceptually the functionality of the memory device  511  according to an embodiment. A 3-D memory (volumetric elevation buffer) is constructed in which memory is allocated in the form of cells  550 , also called “voxels,” in logical 3-dimensional x, y and z planes, thereby enabling performance of a “look-ahead algorithm” by EGPWS  510  during take-off/approach. The 3-D buffer  511  allocates memory in a manner that conceptually forms a cuboid  555  in front of the aircraft constructed of the cube-shaped voxels  550 . At any point of time, the aircraft position may be considered to be at the first cell along the x plane and at corresponding positional co-ordinates in the y and z planes. The y and z positions may be according to the information received from EGPWS  510 . 
         [0023]    Each voxel  550  is a perfect cube. The x and y planes are 128 voxels  550  in length, in an embodiment, although more or fewer such voxels may be used, as appropriate. The division of 64 feet, in an embodiment, by 128 voxels provides a voxel size of 0.5 feet in the x and y planes. Consequently, each voxel  550  is 0.5 feet in length in the z plane. In the illustrated embodiment, 128 layers of voxels  550  are included in the z plane. As discussed in further detail below, this 3-dimensional cuboid  555  is continuously logically “moved” correspondingly to movement of the aircraft. 
         [0024]    The dimensions of the voxels  550  can be altered as per the size of the cell of the digital terrain elevation database stored in EGPWS, provided sufficient accuracy as that of RA is still achieved. 
         [0025]      FIGS. 2-4  illustrate a process  200  according to an embodiment of the invention. The process  200  is illustrated as a set of operations shown as discrete blocks. The process  200  may be implemented in any suitable hardware, software, firmware, or combination thereof. The order in which the operations are described is not to be necessarily construed as a limitation. 
         [0026]    Referring to  FIG. 2 , at a block  210 , radio altimeter calibrated altitude data is received and/or generated by EGPWS  510 . As will be discussed in further detail, if the RA is functioning, this data will be based on data received from the RA. Otherwise, such data will be based on data generated by EGPWS  510  using the 3-D buffer  511 . 
         [0027]    At a block  220 , EGPWS  510  receives heading information, including ascent/descent angle, from system  534 . As above alluded to, if the aircraft is on the flight plan course, data from a flight management system (FMS) may be used. Otherwise, the heading information supplied by an INS may be used. 
         [0028]    At a block  230 , EGPWS  510  receives aircraft position data, including aircraft longitude/latitude, from system  530 . 
         [0029]    At a block  240 , the data received in blocks  210 - 230  is used to initialize or update, as appropriate, a reference point defining the current position of the aircraft relative to previously determined aircraft positions and predicted aircraft positions as stored in the 3-D buffer  511 . 
         [0030]    As discussed above, the cuboid  555  generated by buffer  511  is considered to be dynamically moving along with the motion of the aircraft at all times in accordance with motion-compensation techniques. To perform motion compensation accurately, the total aircraft displacement from a chosen frame of reference should be tracked constantly, including during turn-around times. The inputs to aircraft position integration may be heading (radians), drift angle (radians), delta time to the last reported aircraft position (seconds), ground speed (meters/second), and data indicating previous aircraft position (reference point). 
         [0031]    Aircraft position integration may be initialized by “marking” the position of the aircraft by initializing an object called a reference point. Reference points accumulate as the aircraft moves from the position at which the reference points were initialized. Reference points track Δx displacement (left/right), Δy displacement (forward/rear), and record the aircraft heading (radians) at the time of initialization. The output of the aircraft position integration may be Δx—relative displacement of aircraft (left/right), Δy—relative displacement of aircraft (forward/back), Δh—relative difference in heading (radians), and an updated reference point containing the updated Δx and Δy. 
         [0032]    Referring now to  FIG. 3 , at a block  250 , EGPWS  510  calculates predicted heights of the aircraft along predetermined incremental distances along the current flight path and populates cells of the 3-D buffer  511  with the predicted heights. 
         [0033]    For example, Y1, Y2, Y3, Y4, Y5 may represent successive predicted positions of the aircraft populating corresponding alternate cells (e.g., 2 voxels away from a prior estimated position) of the cuboid  555 . These predicted heights may be calculated using the current position “X” determined with reference to the cuboid  555 . The following equations provide a first estimated height “Y1,” a second estimated height “Y2,” etc. Note that these predicted heights may be a function of Δx, Δy and Δh as determined using the above-described motion-compensation techniques: 
         [0000]        Y 1 =X± ( Z±Δy ) tan ({acute over (α)}±Δ h ),
 
         [0000]        Y 2 =Y 1±( Z±Δy ) tan ({acute over (α)}±Δ h ),
 
         [0000]        Y 3 =Y 2±( Z±Δy ) tan ({acute over (α)}±Δ h ),
 
         [0000]        Y 4 =Y 3±( Z±Δy ) tan ({acute over (α)}±Δ h ),
 
         [0000]        Y 5= Y 4±( Z±Δy ) tan ({acute over (α)}±Δ h ),
 
         [0034]    where, Z is the distance, in an embodiment, two cells away from the current aircraft position along the flight path angle {acute over (α)}. 
         [0035]      FIG. 6  graphically illustrates components involved in these calculations.  FIG. 7  illustrates altitude prediction, according to an embodiment, as a consequence of a level aircraft flight path and as may be arranged in layers of the cuboid  555 .  FIG. 8  illustrates altitude prediction, according to an embodiment, as a consequence of an ascending aircraft flight path and as may be arranged in layers of the cuboid  555 .  FIG. 9  illustrates altitude prediction, according to an embodiment, as a consequence of a descending aircraft flight path and as may be arranged in layers of the cuboid  555 . 
         [0036]    At a block  260 , EGPWS  510  determines whether data is available from the RA (or other applicable altitude sensor). If such data is available, then the process  200  moves to block  290 . Otherwise, the process moves to block  270 . 
         [0037]    At block  270 , EGPWS  510  determines predicted radio altitude calibrated altitudes (RACAs) for use in determining predicted geometric altitudes of the aircraft. The RACAs may be determined by correlating the GPS position of the aircraft with the predicted heights stored in 3-D buffer  511 , accessing terrain elevation data stored in the Terrain Database and correlated with the GPS position, and adding the terrain elevation data to the stored predicted heights. 
         [0038]    Referring now to  FIG. 4 , at a block  280 , EGPWS  510  uses the RACAs to determine predicted geometric altitudes of the aircraft. 
         [0039]    At block  290 , EGPWS  510  determines whether the aircraft is in the approach/landing phase of flight. If the aircraft is in the approach/landing phase of flight, then the process  200  moves to block  300 . Otherwise, the process  200  moves back to block  210 . 
         [0040]    At block  300 , EGPWS  510  determines whether the most-extended predicted height (e.g., Y5) is associated with a voxel of a layer in the 3-D buffer  511  corresponding to a decision height for VFR conditions. If so, then the process  200  ends. Otherwise, the process  200  moves back to block  210 . 
         [0041]    While a preferred embodiment of the invention has been illustrated and described, as noted above, many changes can be made without departing from the spirit and scope of the invention. Accordingly, the scope of the invention is not limited by the disclosure of the preferred embodiment. Instead, the invention should be determined entirely by reference to the claims that follow.