The present application is related to U.S. application Ser. No. 13/707,438, filed Dec. 6, 2012 by Fersdahl, et al., U.S. application Ser. No. 13/841,893, filed Mar. 15, 2013 by Finely et al., U.S. application Ser. No. 12/075,103, filed Mar. 7, 2008 by Woodell, et al., and U.S. application Ser. No. 13/717,052, filed Dec. 17, 2012 by Woodell, et al, all assigned to the assignee of the present application and all incorporated herein by reference in their entireties.
The present disclosure relates generally to the field of weather display systems. More particularly, the present disclosure relates to a weather display system and method configured to display weather threats detected by a weather radar system.
Weather display systems are often used to alert operators of vehicles, such as aircraft pilots, of weather hazards in the area near the vehicle. Conventional weather display systems are configured to display weather data in two dimensions and often operate according to ARINC 453 and 708 standards. A horizontal plan view provides an overview of weather patterns near an aircraft mapped onto a horizontal plane. Generally the horizontal plan provides indications of precipitation rates in the vicinity of the aircraft. Red, yellow, and green colors are used to symbolize areas of respective precipitation rates, and black color symbolizes areas of very little or no precipitation. Each color is associated with radar reflectivity range which corresponds to a respective precipitation rate range. Red indicates the highest rates of precipitation while green represents the lowest (non-zero) rates of precipitation. Certain displays can also utilize a magenta color to indicate regions of turbulence.
A vertical profile view can illustrate weather cells along a plane for a particular set of ranges and altitudes and generally uses the red, yellow, green, black and magenta colors described above. Displays with vertical and/or horizontal views have been proposed which include icons for advanced weather threats that are not readily compatible with conventional displays. For example, conventional displays are not configured to easily display new hazards or threats, such as, the threats associated with predictive or inferential weather sensing systems,
Thus, there is a need for a weather information display that provides more information than a conventional display. Further, there is a need for a threat depiction system and method that is compatible with conventional display platforms, such as the A453 and A661 platforms. There is another need for a weather radar system configured to easily display new hazards or threats, such as, those associated with predictive or inferential weather sensing systems using existing display formats and/or standards. There is also a need for an avionic weather radar system for and a method of displaying a core threat, an associated threat, and a predictive overflight threat using symbology compatible with conventional display platforms.
An exemplary embodiment relates to a method of displaying images associated with weather near an aircraft. The method includes sensing a core threat based at least in part on reflectivity data from radar returns of a weather radar system of the aircraft. The method also includes displaying the images of the weather using at least a first color, a second color, and a third color associated with a respective first precipitation rate range, a respective second precipitation rate range, and a respective third precipitation rate range. The first precipitation rate range is less than the second precipitation rate range, and the third precipitation rate range is more than the second precipitation rate range. An area associated with the core threat has the second color when a precipitation rate of the area is within the first precipitation rate range, and the area has the third color when the precipitation rate of the area is within the second precipitation rate range.
Another exemplary embodiment rates to a method of displaying images associated with weather near an aircraft. The method includes sensing an associated threat based at least in part on reflectivity data from radar returns of a weather radar system of the aircraft. The method also includes displaying the images of the weather using at least a first color, a second color and a third color associated with a respective first precipitation rate range, a respective second precipitation rate range, and a respective third precipitation rate range. The first precipitation rate range is less than the second precipitation rate range, and the third precipitation rate range is more than the second precipitation rate range. An area associated with the associated threat is displayed as a speckled area.
Another exemplary embodiment relates to a method of displaying images associated with weather near an aircraft. The method includes sensing a predictive overflight threat based at least in part on reflectivity data from radar returns of a weather radar system of the aircraft. The method also includes displaying the images of the weather using at least a first color, a second color and a third color associated with a respective first precipitation rate range, a respective second precipitation rate range, and a respective third precipitation rate range. The first precipitation rate range is less than the second precipitation rate range, and the third precipitation rate range is more than the second precipitation rate range. An area associated with the predictive overflight threat is displayed as a wedge-shaped bounded region containing the first color, the second color or the third color.
Another embodiment relates to a system comprising an electronic processor configured to provide the images of weather on a display according to any of the methods described above. Another embodiment relates to one or more computer-readable storage media having instructions stored thereon that are executable by one or more processors to execute one or more of the methods described above. Still another exemplary embodiment relates to a system or method which implements two or three of the processes for the depiction of the core threat, the associated threat, or the predictive overflight threat described above.
The disclosure will become more fully understood from the following detailed description, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements, in which:
Before turning to the figures, which illustrate the exemplary embodiments in detail, it should be understood that the application is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology is for the purpose of description only and should not be regarded as limiting. As discussed below, the systems and methods can be utilized in a number of display devices for various types of applications or sensing systems.
Referring generally to the figures, systems and methods for providing visual representations of weather cells in proximity to an aircraft or other vehicle are provided. According to one embodiment, advance weather threats can be displayed. For example, an embodiment of the system and method described herein can advantageously display predictive or inferred threats such as one or more of a core threat, associated threat, or predictive overflight threat. The threats are advantageously depicted using display formats compatible with A453, and A661 avionic display platforms. The display of advanced threats such as one or more of a core threat, associated threat, or predictive overflight threat allows more than conventional rain gage functionality for the display.
In one alternative embodiment, the threats are also displayable on at least one of navigation (NAV) displays, primary flight displays, electronic flight bag displays, tablets such as I-pad computers, synthetic vision system displays, head up displays (HUDs), wearable displays, Google glasses, etc. In addition, the threats can be displayed on ground-based and remote displays by downloading altitude-based weather models to support ground-based weather products or unmanned avionic vehicle (UAV) operations. The threats are displayed to quickly and intuitively provide the user (e.g., the pilot) with a relatively complete view of the weather near the aircraft that the user could not otherwise easily obtain.
Referring generally to
Referring specifically to
Avionics weather radar system 200 includes a weather radar receiver/transmitter 102, a weather radar adjustable antenna 104, a processor 208, and a memory 206 (e.g., a multi-scan, multi-tilt angle memory). System 200 also includes a tilt control 203 for automatically controlling the tilt angle (mechanical or electronic) of the antenna 104; this auto control may include an additional manual control feature as well.
Memory 206 may be capable of storing in a readily addressable and rapidly retrievable manner at least two data sets resulting from two or more antenna sweeps at different angles. Memory 206 can include any type of machine-readable storage device capable of storing radar returns or associated data for analysis/processing by processor 208. In some embodiments, memory 206 can store parameters of a weather model. The data in memory 206 can represent factors for a mathematical relationship defining reflectivity as a function of altitude in one embodiment. The data in memory 206 can be used by weather prediction module 212 to determine weather that should be displayed on display 110. Although a multi-scan, multi-tilt scanning and data sets are described, it should be understood by one of ordinary skill in the art that a single scan of data may also be used in some embodiments. Memory 206 can also be a three dimensional storage buffer for storing weather radar parameters according to X, Y and Z coordinates according to one embodiment. The storage of radar data and the form of the weather data stored therein is not disclosed in a limiting fashion. A variety of storage techniques for weather data can be used without departing from the scope of the invention.
Weather data can be stored in memory 206. The weather data can be based on received horizontal and/or vertical scans. In some embodiments, the data may be stored as a mathematical equation representation of the information. The mathematical equation representation may be a piecewise linear function, piecewise nonlinear function, coefficients of a cubic spline, coefficients of a polynomial function, etc. that represent vertical representations of the weather based on the horizontal scan data and/or horizontal representation of the weather based on the vertical scan data. The function may be an equation based on weather parameters that may be sensor driven, model driven, a merger of sensor and model, etc. Although horizontal scan data is described, alternative embodiments may include X, Y Cartesian coordinates, rho/theta input, latitude and longitude coordinates, altitude, etc. Weather may be estimated for any required point in space with the vertical dimension being the subject of the weather equation.
Display 110 can be part of an avionic multi-function display (MFD) unit in one embodiment. In some embodiments, display 110 may be any of a variety of display types, such as a navigation display, an electronic flight bag, a tablet computing device, a synthetic vision system, a heads up display (HUD), a dedicated weather display, or another type of display system. In some embodiments, display 110 may be a remote display not included within a cockpit of the aircraft, such as a ground-based support display or remote display configured to display information regarding whether near an unmanned aerial vehicle (UAV).
Processor 208 may be included as part of a multi-scan, multi-tilt angle weather radar system and may perform the customary functions performed by a conventional weather radar return processing unit. Processor 208 may also perform several additional operations based upon the additional data and/or instructions provided in memory 206. In general, processor 208 can merge or cross qualify portions, or ranges, of the radar returns of several different antenna sweeps at several different tilt angles, so that a single, relatively clutter-free image may be presented to the pilot based upon the several separate scans. The radar returns may be processed by processor 208 to generate a three-dimensional weather profile of the weather near the aircraft.
System 200 may perform a scanning operation by transmitting at least two beams at different tilt angles. In some embodiments, system 200 may use a global positioning system (GPS), terrain database, or other tool to control the tilt control 203. Data obtained from the radar returns (e.g., reflectivity data) may be stored in memory 206. For example, known ground clutter may be removed from each of the returns using ground clutter suppression techniques.
Referring again to
Some embodiments may use more complex curve fits. Specific curve fits can be utilized depending on geographical location, time of day, time of year, etc. For example, over Europe, a linear curve fit may suffice to determine vertical reflectivity between freezing layer and troposphere height whereas a second order fit may be required over the equatorial Pacific. A tag can be given to each cell denoting the specific order of the data fit and, correspondingly, the method used to obtain vertical data from the stored parameters. As additional data is collected, perhaps through dedicated vertical scans of convective cells, the functions can be updated or increased in complexity in order to improve their accuracy.
This process allows a rapid assessment of vertical cell extent, cell growth, cell tops, etc. with a minimum of data. Rapid assessment may significantly increase the speed of such an assessment in turns or during initial radar power up.
Processor 208 may process weather radar returns to identify or sense the presence of weather in front of or in view of the aircraft. Weather prediction module 212 may utilize the altitude and the range to the weather to generate a vertical profile associated with the weather. Weather prediction module 212 may scan across an array of azimuths to generate a three-dimensional weather profile of the weather near the aircraft, which may be stored for later presentation or immediately presented on display 110. Threats can be displayed on either view 111 or 113 or both view 111 and 113.
In some embodiments, additional visual indicators other than the representation of weather and indications of the core threat, the associated threat or the predictive overflight threat are provided on views 111 or 113. In some embodiments, a range and bearing matrix having range markers indicating distance from a current position of the aircraft and bearing markers indicating azimuths from a current flight path or bearing of the aircraft may be provided and may assist the pilot in cognitive recognition of weather features from the pilot's perspective.
Weather prediction module 212 can determine a core threat or core hazard assessment by inferring the presence of lightning and hail and by measuring reflectivity as a function of altitude within a highly reflective weather region. When lightning, hail or probability of convection within a reflective region is high, weather production module 212 senses a core threat and can adjust the color levels of weather provided on display 110 to represent the core threat or core hazard assessment to the pilot. In one embodiment, weather is displayed in accordance with protocols where red represents a high precipitation rate range (or high radar range of reflectivity), yellow represents a mid precipitation rate range (or mid range of radar reflectivity) and green represents a low precipitation rate range (or low range of radar reflectivity). In addition, magenta can be utilized to indicate turbulence regions. The core threat is shown as an adjusted color level corresponding to a higher precipitation rate in one embodiment.
Accordingly, the adjustment of the color more accurately reflects the environmental conditions that the aircraft will most likely encounter. Regions with lower rain rates that are associated with a core threat (e.g., associated with lightning and hail) are as dangerous as regions of higher rain rates without core threats. Advantageously, the use of existing colors and adjustment thereof for core threat depiction allows conventional display protocols and electronics to be used without major changes to display formats.
Weather prediction module 212 can also provide an associated threat or associated hazard assessment. An associated threat is comprised of both high altitude and low altitude environmental predictions of lightning, hail and/or turbulence. Low altitude threats can be predicted by algorithms that determine when the environment is conducive to produce either cloud-to-cloud or cloud-to-ground lightning. High altitude threats can be predicted by algorithms that determine the presence of tall convective cells that reach high altitudes and bloom outward into familiar anvil shapes of a cumulonimbus cell. The anvil portion of the cell reflects radar energy very poorly but is associated with a number of hazards including lightning, hail and turbulence. By sensing the anvil portion using techniques described in the applications incorporated herein by reference, weather prediction module 212 can determine an area associated with an associated threat. Storm top analysis can be utilized to identify tall convective cells that bloom outward in one embodiment. Using the relationship between temperature and reflectivity can identify associated threats in one embodiment. Higher reflectivities at lower temperatures indicate areas of hazards such as hail in one embodiment.
In one embodiment, an associated threat can be a presence of high altitude ice crystals. Processor 208 and module 212 can use the techniques described in U.S. application Ser. No. 13/841,893 filed Mar. 15, 2013 by Finely et al, incorporated herein by reference to identify regions of high altitude crystal ice.
Processor 208 causes display 110 to display areas associated with an associated threat (e.g., high altitude threat, low altitude threat, ice crystal threat) as uniformly organized speckles of red or yellow color in one embodiment. The speckled pattern can either be bounded or unbounded and can have a variety of shape profiles including rounded or straight edges. The speckles can vary in shape and size based on selected range, determined threat level and spatial extent. For example, if the threat is close, the speckles can be made larger, or if the associated threat is large, the speckles can be made larger. The speckled pattern can be bounded by a color which is not red, or yellow in one embodiment.
Weather prediction module 212 can also sense a predictive overflight threat. A predictive overflight threat is determined when a cell is growing from low altitudes below the aircraft flight altitude. Generally in conventional systems, such low altitude weather is removed from the display when it is far below the aircraft since it is not significant to aircraft operations. However, if such low altitude weather is growing and it is within the flight path of the aircraft, such weather can pose a predictive overflight threat. Weather prediction module 212 can utilize position information, time information and flight path information as well as sensing a growing cell to determine that a growing cell is within the flight path of the aircraft and provide a display icon for the predictive overflight threat in one embodiment.
In one embodiment, a predictive overflight threat display icon can be a boundary containing uniformly organized speckles, (e.g., red or yellow). The boundary can be wedge shaped having two linear segments that diverge from each other and two curvilinear segments connecting the two linear segments in one embodiment. The boundary color can be the same or different as the speckled colors. According to another embodiment, a target-shaped pattern using weather colors can be provided within the wedge-shaped boundary to depict the predictive overflight threat.
With reference to
Processor 208 can provide a mean velocity parameter 260 and a spectral width parameter 262 derived from weather radar returns. Alternatively, other types of velocity parameters can be utilized. In addition, processor 208 can provide a reflectivity parameter 264 and a range parameter 268 to circuit 212. Computed range or range parameter 268 along with scan angle position can be used to plot the position of weather on display 110. Processor 208 can also receive a temperature parameter 66, an azimuth 68, a position 70, a date 72, flight plan 75 and time 74. Alternatively, a separate temperature sensor 66 can be coupled to processor 208. Parameters 260, 262, 264, and 268 can be computed by processor 208 using data stored in memory 206.
Processor 208 can use parameters 260, 262, 264, and 268 to determine hazards. Parameters 260, 262, 264, and 268 can also be used to improve the quality of the weather prediction. For example, if processor 208 determines that the weather includes a convective cell that is growing, that characteristic can be considered when determining the height and/or other characteristic of the weather as discussed above.
With reference to
Processor 208 can receive the radar returns (or signals/data related thereto) directly or through memory 206 at a step 142. Receiver/transmitter circuit 102 can be a single path or can have separate circuits for a receive path and a transmit path. Processor 208 may determine power associated with the radar returns.
Processor 208 processes the weather radar returns to determine the presence of weather and the altitude and range of weather (e.g., based on reflectivity) (144). In one embodiment, the altitude of weather can be determined by comparing power levels of radar returns at different tilt angles.
Weather prediction module 212 can generate a weather profile at a given range and over a defined altitude. Weather prediction module 212 can generate a vertical profile for a given range and azimuth at an altitude or an altitude range for the weather. Module 212 uses inferential detection techniques to determine advanced threats (e.g., core threat, associated threat, or predictive overflight threat) at a step 146. The threats are displayed at a step 160.
With reference to
With reference to
With reference to
With reference to
Weather prediction module 212 can be implemented using hardware, software, or a combination thereof. In one embodiment, module 212 is a software routine that operates within processor 208. Although shown as part of processor 208, module 212 can be a separate circuit or be provided between display 110 and processor 208. According to one embodiment, module 212 can be implemented upon its own processor platform. In some embodiments, weather prediction module 212 determines the range and altitude associated with the sensed weather. The range and altitude may be used so that weather prediction module 212 can generate a vertical profile for sensed weather. One or more vertical profiles may be used to generate a three-dimensional weather profile of weather in proximity to the aircraft for display on display 110.
The disclosure is described above with reference to drawings. These drawings illustrate certain details of specific embodiments that implement the systems and methods and programs of the present disclosure. However, describing the disclosure with drawings should not be construed as imposing on the disclosure any limitations that may be present in the drawings. The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing its operations. The embodiments of the present disclosure may be implemented using an existing computer processor, or by a special purpose computer processor incorporated for this or another purpose or by a hardwired system. No claim element herein is to be construed under the provisions of 35 U.S.C. §112, sixth paragraph, unless the element is expressly recited using the phrase “means for.” Furthermore, no element, component or method step in the present disclosure is intended to be dedicated to the public, regardless of whether the element, component or method step is explicitly recited in the claims.
As noted above, embodiments within the scope of the present disclosure include program products comprising machine-readable storage media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable storage media can be any available media which can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable storage media can comprise RAM, ROM, EPROM, EEPROM, CD ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium (e.g., non-transitory medium) which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable storage media. Machine-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machine to perform a certain function or group of functions.
Embodiments of the disclosure are described in the general context of method steps which may be implemented in one embodiment by a program product including machine-executable instructions, such as program code, for example, in the form of program modules executed by machines in networked environments. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Machine-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.
Embodiments of the present disclosure may be practiced in a networked environment using logical connections to one or more remote computers having processors. Logical connections may include a local area network (LAN) and a wide area network (WAN) that are presented here by way of example and not limitation. Such networking environments are commonplace in office-wide or enterprise-wide computer networks, intranets and the Internet and may use a wide variety of different communication protocols. Those skilled in the art will appreciate that such network computing environments will typically encompass many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, servers, minicomputers, mainframe computers, and the like. Embodiments of the disclosure may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
An exemplary system for implementing the overall system or portions of the disclosure might include a general purpose computing device in the form of a computer, including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit. The system memory may include read only memory (ROM) and random access memory (RAM) or other non-transitory storage medium. The computer may also include a magnetic hard disk drive for reading from and writing to a magnetic hard disk, a magnetic disk drive for reading from or writing to a removable magnetic disk, and an optical disk drive for reading from or writing to a removable optical disk such as a CD ROM or other optical media. The drives and their associated machine-readable media provide nonvolatile storage of machine-executable instructions, data structures, program modules, and other data for the computer.
It should be noted that although the flowcharts provided herein show a specific order of method steps, it is understood that the order of these steps may differ from what is depicted. Also two or more steps may be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. It is understood that all such variations are within the scope of the disclosure. Likewise, software and web implementations of the present disclosure could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various database searching steps, correlation steps, comparison steps and decision steps. It should also be noted that the word “component” as used herein and in the claims is intended to encompass implementations using one or more lines of software code, and/or hardware implementations, and/or equipment for receiving manual inputs.
The foregoing description of embodiments of the disclosure have been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the disclosure. The embodiments were chosen and described in order to explain the principals of the disclosure and its practical application to enable one skilled in the art to utilize the disclosure in various embodiments and with various modifications as are suited to the particular use contemplated.
Number | Name | Date | Kind |
---|---|---|---|
650275 | Reeve | May 1900 | A |
3251057 | Buehler et al. | May 1966 | A |
3359557 | Fow et al. | Dec 1967 | A |
3404396 | Buchler et al. | Oct 1968 | A |
3465339 | Marner | Sep 1969 | A |
3491358 | Hicks | Jan 1970 | A |
3508259 | Andrews | Apr 1970 | A |
3540829 | Collinson et al. | Nov 1970 | A |
3567915 | Altshuler et al. | Mar 1971 | A |
3646555 | Atlas | Feb 1972 | A |
3715748 | Hicks | Feb 1973 | A |
3764719 | Dell | Oct 1973 | A |
3781530 | Britland et al. | Dec 1973 | A |
3781878 | Kirkpatrick | Dec 1973 | A |
3803609 | Lewis et al. | Apr 1974 | A |
3885237 | Kirkpatrick | May 1975 | A |
3943511 | Evans et al. | Mar 1976 | A |
3964064 | Brandao et al. | Jun 1976 | A |
3968490 | Gostin | Jul 1976 | A |
4015257 | Fetter | Mar 1977 | A |
4043194 | Tanner | Aug 1977 | A |
4223309 | Payne | Sep 1980 | A |
4283715 | Choisnet | Aug 1981 | A |
4283725 | Chisholm | Aug 1981 | A |
4318100 | Shimizu et al. | Mar 1982 | A |
4346595 | Frosch et al. | Aug 1982 | A |
4430654 | Kupfer | Feb 1984 | A |
4435707 | Clark | Mar 1984 | A |
4459592 | Long | Jul 1984 | A |
4533915 | Lucchi et al. | Aug 1985 | A |
4555703 | Cantrell | Nov 1985 | A |
4600925 | Alitz et al. | Jul 1986 | A |
4613938 | Hansen et al. | Sep 1986 | A |
4649388 | Atlas | Mar 1987 | A |
4658255 | Nakamura et al. | Apr 1987 | A |
4684950 | Long | Aug 1987 | A |
4742353 | D'Addio et al. | May 1988 | A |
4761650 | Masuda et al. | Aug 1988 | A |
4835536 | Piesinger et al. | May 1989 | A |
RE33152 | Atlas | Jan 1990 | E |
4914444 | Pifer et al. | Apr 1990 | A |
4928131 | Onozawa | May 1990 | A |
4940987 | Frederick | Jul 1990 | A |
5036334 | Henderson et al. | Jul 1991 | A |
5049886 | Seitz et al. | Sep 1991 | A |
5057820 | Markson et al. | Oct 1991 | A |
5077558 | Kuntman | Dec 1991 | A |
5105191 | Keedy | Apr 1992 | A |
5159407 | Churnside et al. | Oct 1992 | A |
5164731 | Borden et al. | Nov 1992 | A |
5173704 | Buehler et al. | Dec 1992 | A |
5177487 | Taylor et al. | Jan 1993 | A |
5198819 | Susnjara | Mar 1993 | A |
5202690 | Frederick | Apr 1993 | A |
5208600 | Rubin | May 1993 | A |
5221924 | Wilson, Jr. | Jun 1993 | A |
5262773 | Gordon | Nov 1993 | A |
5291208 | Young | Mar 1994 | A |
5296865 | Lewis | Mar 1994 | A |
5311183 | Mathews et al. | May 1994 | A |
5311184 | Kuntman | May 1994 | A |
5331330 | Susnjara | Jul 1994 | A |
5396220 | Markson et al. | Mar 1995 | A |
5402116 | Ashley | Mar 1995 | A |
5469168 | Anderson | Nov 1995 | A |
5479173 | Yoshioka et al. | Dec 1995 | A |
5485157 | Long | Jan 1996 | A |
5517193 | Allison et al. | May 1996 | A |
5521603 | Young | May 1996 | A |
5534868 | Gjessing et al. | Jul 1996 | A |
5568151 | Merritt | Oct 1996 | A |
5583972 | Miller | Dec 1996 | A |
5592171 | Jordan | Jan 1997 | A |
5602543 | Prata et al. | Feb 1997 | A |
5615118 | Frank | Mar 1997 | A |
5648782 | Albo et al. | Jul 1997 | A |
5654700 | Prata et al. | Aug 1997 | A |
5657009 | Gordon | Aug 1997 | A |
5686919 | Jordan et al. | Nov 1997 | A |
5726656 | Frankot | Mar 1998 | A |
5757322 | Ray et al. | May 1998 | A |
5771020 | Markson et al. | Jun 1998 | A |
5828332 | Frederick | Oct 1998 | A |
5838239 | Stern et al. | Nov 1998 | A |
5839080 | Muller et al. | Nov 1998 | A |
5907568 | Reitan, Jr. | May 1999 | A |
5920276 | Frederick | Jul 1999 | A |
5945926 | Ammar et al. | Aug 1999 | A |
5973635 | Albo | Oct 1999 | A |
6034760 | Rees | Mar 2000 | A |
6043756 | Bateman et al. | Mar 2000 | A |
6043757 | Patrick | Mar 2000 | A |
6081220 | Fujisaka et al. | Jun 2000 | A |
6138060 | Conner et al. | Oct 2000 | A |
6154151 | McElreath et al. | Nov 2000 | A |
6154169 | Kuntman | Nov 2000 | A |
6177873 | Cragun | Jan 2001 | B1 |
6184816 | Zheng et al. | Feb 2001 | B1 |
6201494 | Kronfeld | Mar 2001 | B1 |
6208284 | Woodell et al. | Mar 2001 | B1 |
6236351 | Conner et al. | May 2001 | B1 |
6240369 | Foust | May 2001 | B1 |
6246367 | Markson et al. | Jun 2001 | B1 |
6281832 | McElreath | Aug 2001 | B1 |
6289277 | Feyereisen et al. | Sep 2001 | B1 |
6297772 | Lewis | Oct 2001 | B1 |
6340946 | Wolfson et al. | Jan 2002 | B1 |
6381538 | Robinson et al. | Apr 2002 | B1 |
6388607 | Woodell | May 2002 | B1 |
6388608 | Woodell et al. | May 2002 | B1 |
RE37725 | Yamada | Jun 2002 | E |
6405134 | Smith et al. | Jun 2002 | B1 |
6424288 | Woodell | Jul 2002 | B1 |
6441773 | Kelly et al. | Aug 2002 | B1 |
6456226 | Zheng et al. | Sep 2002 | B1 |
6480142 | Rubin | Nov 2002 | B1 |
6496252 | Whiteley | Dec 2002 | B1 |
6501392 | Gremmert et al. | Dec 2002 | B2 |
6512476 | Woodell | Jan 2003 | B1 |
6518914 | Peterson et al. | Feb 2003 | B1 |
6549161 | Woodell | Apr 2003 | B1 |
6560538 | Schwinn et al. | May 2003 | B2 |
6563452 | Zheng et al. | May 2003 | B1 |
6577947 | Kronfeld et al. | Jun 2003 | B1 |
6590520 | Steele et al. | Jul 2003 | B1 |
6597305 | Szeto et al. | Jul 2003 | B2 |
6603425 | Woodell | Aug 2003 | B1 |
6606564 | Schwinn et al. | Aug 2003 | B2 |
6614382 | Cannaday et al. | Sep 2003 | B1 |
6650275 | Kelly et al. | Nov 2003 | B1 |
6650972 | Robinson et al. | Nov 2003 | B1 |
6667710 | Cornell et al. | Dec 2003 | B2 |
6670908 | Wilson et al. | Dec 2003 | B2 |
6677886 | Lok | Jan 2004 | B1 |
6683609 | Baron et al. | Jan 2004 | B1 |
6690317 | Szeto et al. | Feb 2004 | B2 |
6703945 | Kuntman et al. | Mar 2004 | B2 |
6720906 | Szeto et al. | Apr 2004 | B2 |
6738010 | Steele et al. | May 2004 | B2 |
6741203 | Woodell | May 2004 | B1 |
6744382 | Lapis et al. | Jun 2004 | B1 |
6771207 | Lang | Aug 2004 | B1 |
6788043 | Murphy et al. | Sep 2004 | B2 |
6791311 | Murphy et al. | Sep 2004 | B2 |
6828922 | Gremmert et al. | Dec 2004 | B1 |
6828923 | Anderson | Dec 2004 | B2 |
6839018 | Szeto et al. | Jan 2005 | B2 |
6850185 | Woodell | Feb 2005 | B1 |
6856908 | Devarasetty et al. | Feb 2005 | B2 |
6879280 | Bull et al. | Apr 2005 | B1 |
6882302 | Woodell et al. | Apr 2005 | B1 |
6917860 | Robinson et al. | Jul 2005 | B1 |
6977608 | Anderson et al. | Dec 2005 | B1 |
7030805 | Ormesher et al. | Apr 2006 | B2 |
7042387 | Ridenour et al. | May 2006 | B2 |
7082382 | Rose et al. | Jul 2006 | B1 |
7109912 | Paramore et al. | Sep 2006 | B1 |
7109913 | Paramore et al. | Sep 2006 | B1 |
7116266 | Vesel et al. | Oct 2006 | B1 |
7129885 | Woodell et al. | Oct 2006 | B1 |
7132974 | Christianson | Nov 2006 | B1 |
7139664 | Kelly et al. | Nov 2006 | B2 |
7145503 | Abramovich et al. | Dec 2006 | B2 |
7161525 | Finley et al. | Jan 2007 | B1 |
7200491 | Rose et al. | Apr 2007 | B1 |
7205928 | Sweet | Apr 2007 | B1 |
7242343 | Woodell | Jul 2007 | B1 |
7259714 | Cataldo | Aug 2007 | B1 |
7292178 | Woodell et al. | Nov 2007 | B1 |
7307576 | Koenigs | Dec 2007 | B1 |
7307577 | Kronfeld et al. | Dec 2007 | B1 |
7307583 | Woodell et al. | Dec 2007 | B1 |
7307586 | Peshlov et al. | Dec 2007 | B2 |
7307756 | Walmsley | Dec 2007 | B2 |
7352317 | Finley et al. | Apr 2008 | B1 |
7352929 | Hagen et al. | Apr 2008 | B2 |
7365674 | Tillotson et al. | Apr 2008 | B2 |
7372394 | Woodell et al. | May 2008 | B1 |
7383131 | Wey et al. | Jun 2008 | B1 |
7391358 | Dupree et al. | Jun 2008 | B2 |
7417579 | Woodell | Aug 2008 | B1 |
7427943 | Kronfeld et al. | Sep 2008 | B1 |
7471995 | Robinson | Dec 2008 | B1 |
7486219 | Woodell et al. | Feb 2009 | B1 |
7486220 | Kronfeld et al. | Feb 2009 | B1 |
7492304 | Woodell et al. | Feb 2009 | B1 |
7492305 | Woodell et al. | Feb 2009 | B1 |
7515087 | Woodell et al. | Apr 2009 | B1 |
7515088 | Woodell et al. | Apr 2009 | B1 |
7528613 | Thompson et al. | May 2009 | B1 |
7541971 | Woodell et al. | Jun 2009 | B1 |
7557735 | Woodell et al. | Jul 2009 | B1 |
7576680 | Woodell | Aug 2009 | B1 |
7581441 | Barny et al. | Sep 2009 | B2 |
7598901 | Tillotson et al. | Oct 2009 | B2 |
7598902 | Woodell et al. | Oct 2009 | B1 |
7633428 | McCusker et al. | Dec 2009 | B1 |
7633431 | Wey et al. | Dec 2009 | B1 |
7656343 | Hagen et al. | Feb 2010 | B1 |
7664601 | Daly, Jr. | Feb 2010 | B2 |
7696921 | Finley et al. | Apr 2010 | B1 |
7714767 | Kronfeld et al. | May 2010 | B1 |
7728758 | Varadarajan et al. | Jun 2010 | B2 |
7733264 | Woodell et al. | Jun 2010 | B1 |
7859448 | Woodell et al. | Dec 2010 | B1 |
7868811 | Woodell et al. | Jan 2011 | B1 |
7917255 | Finley | Mar 2011 | B1 |
7973698 | Woodell et al. | Jul 2011 | B1 |
7982658 | Kauffman et al. | Jul 2011 | B2 |
8022859 | Bunch et al. | Sep 2011 | B2 |
8054214 | Bunch | Nov 2011 | B2 |
8072368 | Woodell | Dec 2011 | B1 |
8081106 | Yannone | Dec 2011 | B2 |
8089391 | Woodell et al. | Jan 2012 | B1 |
8098188 | Costes et al. | Jan 2012 | B2 |
8111186 | Bunch et al. | Feb 2012 | B2 |
8159369 | Koenigs et al. | Apr 2012 | B1 |
8217828 | Kirk | Jul 2012 | B2 |
8228227 | Bunch et al. | Jul 2012 | B2 |
8314730 | Musiak et al. | Nov 2012 | B1 |
8477062 | Kanellis | Jul 2013 | B1 |
8902100 | Woodell et al. | Dec 2014 | B1 |
20020039072 | Gremmert et al. | Apr 2002 | A1 |
20030001770 | Cornell et al. | Jan 2003 | A1 |
20040239550 | Daly, Jr. | Dec 2004 | A1 |
20050049789 | Kelly et al. | Mar 2005 | A1 |
20060036366 | Kelly et al. | Feb 2006 | A1 |
20080158049 | Southard et al. | Jul 2008 | A1 |
20080165051 | Khatwa | Jul 2008 | A1 |
20090177343 | Bunch et al. | Jul 2009 | A1 |
20090219197 | Bunch | Sep 2009 | A1 |
20100019938 | Bunch | Jan 2010 | A1 |
20100042275 | Kirk | Feb 2010 | A1 |
20100103029 | Khatwa et al. | Apr 2010 | A1 |
20100194628 | Christianson et al. | Aug 2010 | A1 |
20100201565 | Khatwa | Aug 2010 | A1 |
20110148694 | Bunch et al. | Jun 2011 | A1 |
20120029786 | Calandra et al. | Feb 2012 | A1 |
20120133551 | Pujol et al. | May 2012 | A1 |
20120139778 | Bunch et al. | Jun 2012 | A1 |
20130226452 | Watts | Aug 2013 | A1 |
20130234884 | Bunch et al. | Sep 2013 | A1 |
20140361923 | Bunch et al. | Dec 2014 | A1 |
Number | Date | Country |
---|---|---|
1 329 738 | Jul 2003 | EP |
2658617 | Aug 1991 | FR |
WO-9807047 | Feb 1998 | WO |
WO-9822834 | May 1998 | WO |
WO-03005060 | Jan 2003 | WO |
WO-2009137158 | Nov 2009 | WO |
Entry |
---|
U.S. Appl. No. 12/075,103, filed Mar. 7, 2008, Woodell et al. |
Advisory Action for U.S. Appl. No. 12/075,103, mail date Feb. 13, 2013, 3 pages. |
Advisory Action for U.S. Appl. No. 12/075,103, mail date Nov. 8, 2010, 3 pages. |
Advisory Action for U.S. Appl. No. 12/075,103, mail date Oct. 15, 2010, 3 pages. |
Bovith et al., Detecting Weather Radar Clutter by Information Fusion with Satellite Images and Numerical Weather Prediction Model Output; Jul. 31-Aug. 4, 2006, 4 pages. |
Burnham et al., Thunderstorm Turbulence and Its Relationship to Weather Radar Echoes, J. Aircraft, Sep.-Oct. 1969, 8 pages. |
Corridor Integrated Weather System (CIWS), www.ll.mit.edu/mission/aviation/faawxsystems/ciws.html, received on Aug. 19, 2009, 3 pages. |
Doviak et al., Doppler Radar and Weather Observations, 1984, 298 pages. |
Dupree et al.,FAA Tactical Weather Forecasting in the United States National Airspace, 29 pages. |
Goodman et al., Lisdad Lightning Observations during the Feb. 22-23, 1998 Central Florida Tornado Outbreak, http:www.srh.noaa.gov/topics/attach/html/ssd98-37.htm, Jun. 1, 1998, 5 pages. |
Hodanish, Integration of Lightning Detection Systems in a Modernized National Weather Service Office, http://www.srh.noaa.gov/mlb/hoepub.html, retrieved on Aug. 6, 2007, 5 pages. |
Honeywell, RDR-4B Forward Looking Windshear Detection/Weather Radar System User's Manual with Radar Operation Guidelines, Jul. 2003, 106 pages. |
Keith, Transport Category Airplane Electronic Display Systems, Jul. 16, 1987, 34 pages. |
Klingle-Wilson et al., Description of Corridor Integrated Weather System (CIWS) Weather Products, Aug. 1, 2005, 120 pages. |
Kuntman et al, Turbulence Detection and Avoidance System, Flight Safety Foundation 53rd International Air Safety Seminar (IASS), Oct. 29, 2000, 13 pages. |
Kuntman, Airborne System to Address Leading Cause of Injuries in Non-Fatal Airline Accidents, ICAO Journal, Mar. 2000, 4 pages. |
Meteorological/KSC/L71557/Lighting Detection and Ranging (LDAR), Jan. 2002, 12 pages. |
Nathanson, Fred E., “Radar and Its Composite Environment,” Radar Design Principles, Signal Processing and the Environment, 1969, McGraw-Hill Book Company, New York et al., 5 pages. |
Notice of Allowance for U.S. Appl. No. 10/631,253, mail date Jul. 28, 2005, 7 pages. |
Notice of Allowance for U.S. Appl. No. 11/256,845, mail date May 27, 2009, 7 pages. |
Notice of Allowance for U.S. Appl. No. 11/370,085, mail date Dec. 30, 2008, 6 pages. |
Notice of Allowance for U.S. Appl. No. 11/402,434, mail date Nov. 4, 2008, 6 pages. |
Notice of Allowance for U.S. Appl. No. 12/474,102, mail date Jan. 20, 2012, 6 pages. |
Office Action for U.S. Appl. No. 11/256,845, mail date Aug. 21, 2007, 4 pages. |
Office Action for U.S. Appl. No. 10/631,253, mail date Jan. 14, 2004, 5 pages. |
Office Action for U.S. Appl. No. 10/631,253, mail date Jun. 30, 2004, 4 pages. |
Office Action for U.S. Appl. No. 11/256,845, mail date Dec. 5, 2006, 5 pages. |
Office Action for U.S. Appl. No. 11/256,845, mail date Jul. 28, 2008, 5 pages. |
Office Action for U.S. Appl. No. 11/256,845, mail date Jun. 22, 2006, 5 pages. |
Office Action for U.S. Appl. No. 11/370,085, mail date Aug. 15, 2007, 10 pages. |
Office Action for U.S. Appl. No. 11/370,085, mail date Dec. 4, 2007, 13 pages. |
Office Action for U.S. Appl. No. 11/370,085, mail date Oct. 9, 2008, 5 pages. |
Office Action for U.S. Appl. No. 11/402,434, mail date Jul. 17, 2008, 5 pages. |
Office Action for U.S. Appl. No. 11/402,434, mail date Mar. 29, 2007, 8 pages. |
Office Action for U.S. Appl. No. 11/402,434, mail date Oct. 26, 2006, 7 pages. |
Office Action for U.S. Appl. No. 11/402,434, mail date Sep. 20, 2007, 7 pages. |
Office Action for U.S. Appl. No. 12/075,103, mail date Feb. 26, 2010, 11 pages. |
Office Action for U.S. Appl. No. 12/075,103, mail date Jul. 29, 2010, 7 pages. |
Office Action for U.S. Appl. No. 12/075,103, mail date Jun. 20, 2012, 5 pages. |
Office Action for U.S. Appl. No. 12/075,103, mail date Nov. 29, 2012, 6 pages. |
Office Action for U.S. Appl. No. 12/474,102, mail date Sep. 7, 2011, 8 pages. |
Office Action for U.S. Appl. No. 13/717,052, mail date Aug. 22, 2013, 15 pages. |
Office Action on U.S. Appl. No. 12/075,103 Dated Jul. 31, 2013, 8 pages. |
Pessi et al., On the Relationship Between Lightning and Convective Rainfall Over the Central Pacific Ocean, date unknown, 9 pages. |
Waldvogel et al., The Kinetic Energy of Hailfalls. Part I: Hailstone Spectra, Journal of Applied Meteorology, Apr. 1978, 8 pages. |
Wilson et al., The Complementary Use of Titan-Derived Radar and Total Lightning Thunderstorm Cells, 10 pages. |
Zipser et al., The Vertical Profile of Radar Reflectivity and Convective Cells: A Strong Indicator of Storm Intensity and Lightning Probability? America Meteorological Society, 1994, 9 pages. |
U.S. Appl. No. 13/841,893, filed Mar. 15, 2013, Rockwell Collins, Inc. |
U.S. Appl. No. 13/919,406, filed Jun. 17, 2013, Rockwell Collins, Inc. |
U.S. Appl. No. 14/086,844, filed Nov. 21, 2013, Rockwell Collins, Inc. |
U.S. Appl. No. 14/206,651, filed Mar. 12, 2014, Rockwell Collins, Inc. |
U.S. Appl. No. 14/207,034, filed Mar. 12, 2014, Rockwell Collins, Inc. |
3-D Weather Hazard and Avoidance System, Honeywell InteVue Brochure dated Nov. 2008, 4 pages. |
Greene et al., Vertically Integrated Liquid Water—A New Analysis Tool, Monthly Weather Review, Jul. 1972, 5 pages. |
Kuntman, Satellite Imagery: Predicting Aviation Weather Hazards, ICAO Journal, Mar. 2000, 4 pps. |
Office Action on U.S. Appl. No. 12/075,103 Dated Apr. 9, 2014, 5 pages. |
Office Action on U.S. Appl. No. 13/246,769 Dated Apr. 21, 2014, 18 pages. |
Office Action on U.S. Appl. No. 13/717,052 Dated Dec. 23, 2013, 7 pages. |
RDR-4B Honeywell User Manual for Forward Looking Windshear Detection/Weather Radar System, Rev. 6, Jul. 2003, 106 pps. |
Robinson et al., En Route Weather Depiction Benefits of the Nexrad Vertically Integrated Liquid Water Product Utilized by the Corridor Integrated Weather System, 10th Conference on Aviation, Range, and Aerospace Meteorology (ARAM), 2002, 4 pages. |
Stormscope Lightning Detection Systems, L3 Avionics Systems, retrieved on Jul. 11, 2011, 6 pages. |
US Office Action on U.S. Appl. No. 13/717,052 Dated Mar. 27, 2014, 6 pages. |
Decision on Appeal for Inter Parties Reexamination Control No. 95/001,860, dated Oct. 17, 2014, 17 pages. |
Final Office Action on U.S. Appl. No. 12,892,663 dated Mar. 7, 2013, 13 pages. |
Final Office Action on U.S. Appl. No. 13/238,606 Dated Apr. 1, 2014, 11 pages. |
Final Office Action on U.S. Appl. No. 13/238,606 Dated Jan. 22, 2015, 6 pages. |
Non-Final Office Action on U.S. Appl. No. 12/892,663 Dated May 29, 2013, 14 pages. |
Non-Final Office Action on U.S. Appl. No. 13/238,606 Dated Jul. 8, 2014, 12 pages. |
Non-Final Office Action on U.S. Appl. No. 13/238,606 Dated Sep. 23, 2013, 15 pages. |
Non-Final Office Action on U.S. Appl. No. 13/717,052 Dated Feb. 11, 2015, 15 pages. |
Notice of Allowance on U.S. Appl. No. 13/246,769 Dated Jan. 8, 2015, 10 pages. |
Notice of Allowance on U.S. Appl. No. 13/707,438 Dated Feb. 25, 2015, 11 pages. |
Office Action for U.S. Appl. No. 12/892,663, mail date Oct. 22, 2012, 12 pages. |
TOA Technology, printed from website: http://www.toasystems.com/technology.html on Dec. 29, 2010, 2 pages. |
Triangulation, from Wikipedia, printed from website: http://en.wikipedia.org/wiki/Triangulation on Dec. 29, 2010, 6 pages. |
U.S. Appl. No. 14/206,239, filed Mar. 12, 2014, Rockwell Collins. |
Final Office Action on U.S. Appl. No. 13/246,769 Dated Sep. 16, 2014, 18 pages. |
Non-Final Office Action on U.S. Appl. No. 13/717,052 Dated Sep. 9, 2014, 8 pages. |
Notice of Allowance on U.S. Appl. No. 12/075,103 Dated Aug. 4, 2014, 10 pages. |
U.S. Appl. No. 13/246,769, filed Sep. 27, 2011, Rockwell Collins. |
Non-Final Office Action on U.S. Appl. No. 14/452,235 Dated Apr. 23, 2015, 9 pages. |
Non-Final Office Action on U.S. Appl. No. 14/681,901 Dated Jun. 17, 2015, 21 pages. |
Non-Final Office Action on U.S. Appl. No. 13/841,893 Dated Jun. 22, 2015, 27 pages. |
Non-Final Office Action on U.S. Appl. No. 13/913,100 Dated May 4, 2015, 25 pages. |
Non-Final Office Action on U.S. Appl. No. 13/238,606 Dated May 27, 2015, 14 pages. |