The present disclosure relates generally to the field of weather display systems. More particularly, the present disclosure relates to a weather display system configured to display three-dimensional perspective views of weather information generated based on radar returns from 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 only two dimensions. A horizontal plan view provides an overview of weather patterns near an aircraft mapped onto a horizontal plane. Such a horizontal plan view does not provide the pilot with information about how displayed weather cells vary with altitude (e.g., the differences in severity at different altitudes). A vertical profile view illustrates a slice of one or more weather cells along a plane for a particular set of ranges and altitudes. Such a vertical profile view does not provide the pilot with information about the weather to either side of the displayed slice. Both of these two-dimensional views fail to provide information about the weather that the user may find important for operating the vehicle. Thus, there is a need for a weather information display that provides more information than a conventional display with a horizontal profile and a vertical profile.
One embodiment of the disclosure relates to a method of displaying weather data relating to weather near an aircraft. The method comprises generating a three-dimensional weather profile of the weather near the aircraft based at least in part on reflectivity data from radar returns of a weather radar system of the aircraft. Generating the three-dimensional weather profile comprises estimating weather data above a freezing layer height using a function that is based on a rate of reduction in reflectivity above the freezing layer. The method further comprises transmitting weather display data to a display device, the weather display data being configured to cause the display device to display a visual representation of the three-dimensional weather profile.
Another embodiment relates to a system comprising an electronic processor configured to generate a three-dimensional weather profile of the weather near the aircraft based on reflectivity data from radar returns of a weather radar system of the aircraft. The electronic processor is further configured to estimate weather data of the three-dimensional weather profile above a freezing layer height using a function that is based on a rate of reduction in reflectivity above the freezing layer. The electronic processor is further configured to transmit weather display data to a display device, the weather display data being configured to cause the display device to display a visual representation of the three-dimensional weather profile.
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 a method. The method comprises generating a three-dimensional weather profile of the weather near the aircraft based on reflectivity data from radar returns of a weather radar system of the aircraft. Generating the three-dimensional weather profile comprises estimating weather data above a freezing layer height using a function that is based on a rate of reduction in reflectivity above the freezing layer. The method further comprises transmitting weather display data to a display device, the weather display data being configured to cause the display device to display a visual representation of the three-dimensional weather profile.
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 control devices for various types of applications or analyzed systems.
Referring generally to the figures, systems and methods for providing visual representations of weather cells in three dimensions, such as weather cells in proximity to an aircraft or other vehicle, are provided. A three-dimensional weather profile of weather near an aircraft may be constructed by transmitting radar beams from a weather radar system (e.g., using a horizontal and/or vertical scanning pattern) and measuring reflectivity data based on the radar return signals. For portions of weather cells that are positioned above the freezing layer (i.e., a layer of air above which the temperature is below the freezing temperature of water), the data used to construct the three-dimensional weather profile may be approximated based on a function that reflects a rate at which reflectivity drops off above the freezing layer according to one embodiment. A three-dimensional perspective view of the weather profile is generated and provided to a user on a display (e.g., a cockpit weather display). The three-dimensional perspective view of the weather may 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 easily obtain by viewing either a horizontal plan view or a vertical profile view of the weather. In some embodiments, a user input device may be provided that allows the user to rotate the three-dimensional perspective view of the weather in up to all three dimensions. In some embodiments, the user may select a plane within the three-dimensional perspective view that intersects one or more weather cells (e.g., by selecting two points or selecting a line in the three-dimensional perspective view) and a two-dimensional profile view of the weather data associated with the weather cells along the plane may be generated and displayed.
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 vertical 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.
Convective weather has a vertical reflectivity gradient which extends from the ground to a point where the radar can no longer detect echoes from the weather. This gradient may have similar characteristics from weather cell to weather cell. A typical weather cell will have substantial, nearly constant reflectivity between the ground and the height at which the atmospheric moisture begins to freeze.
Above the freezing layer, the reflectivity falls off in a nearly linear manner until the storm generally tops out at the top of the troposphere. Referring now to
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 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. Vertical weather prediction module 212 may utilize the altitude and the range to the weather to generate a vertical profile associated with the weather. Vertical 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.
After vertical weather prediction module 212 generates a three-dimensional weather profile for the weather, processor 208 may transmit data to display 110 that causes display 110 to present a visual representation of the three-dimensional weather profile on a 3D perspective view screen 130. 3D perspective view screen 130 may provide a full representative view of the weather near the aircraft (e.g., in front of the aircraft) in a manner that illustrates information about the weather in three dimensions (e.g., two horizontal dimensions and one vertical dimension). In some embodiments, display 110 may be a two-dimensional display device and 3D perspective view screen 130 may provide an image of the weather that is configured to simulate information about the weather in three dimensions. In some embodiments, display 110 may be a three-dimensional display device. 3D perspective view screen 130 may provide in a single display screen information about how the weather near the aircraft varies across a range of lateral or horizontal coordinates (e.g., across ranges/bearings from the aircraft, across latitude/longitude coordinates, etc.), such as may be obtained from a horizontal plan screen 113, and information about how the weather varies at different altitudes, such as may be obtained from a vertical profile screen 111. This may allow a pilot to make critical decisions about how to navigate the aircraft to avoid weather hazards, such as whether the pilot should navigate the aircraft on a different bearing or move the aircraft to a different altitude, quickly and easily using a single display screen without having to repeatedly switch between a horizontal plan view and vertical profile view to obtain the relevant information. In some embodiments, display 110 may be configured to also allow the user to view a vertical profile screen 111 and/or horizontal plan screen 113 (e.g., separately or simultaneously).
In some embodiments, system 200 may be configured to receive user input from a user input device and modify the displayed representation of the three-dimensional weather profile based on the user input. For example, display 110 may be a touch-sensitive display device with a touch-sensitive display surface through which a user may provide input. In other embodiments, system 200 may additionally or alternatively include other types of input devices, such as a mouse, bezel keys, or other types of separate input devices. Processor 208 may be configured to cause display 110 to rotate the weather image presented on 3D perspective view screen 130 based on the user input in up to three dimensions. For example, if display 110 is a touch-sensitive display device, the user may press and drag a portion of 3D perspective view screen 130 and the image may rotate in a corresponding manner (e.g., if the user drags the image horizontally, the image may rotate in the corresponding direction about a vertical axis, and if the user drags the image diagonally, the image may rotate in the corresponding diagonal direction about multiple axes). The user input device may enable a user to view the weather representation from any height, angle, and/or spatial position, including, but not limited to, a first person view from the perspective of the aircraft along its current flight path. In some embodiments, user input may be used to perform additional or alternative functions, such as zooming in or out of a particular portion of the display weather or displaying textual and/or numerical information about a particular weather cell or portion thereof.
In some embodiments, user input may be used to allow a user to select a two-dimensional cross-section of the weather shown in 3D perspective view screen 130 to be viewed on display 110. For example, if display 110 is a touch-sensitive display device, a user may select a plane that the user wishes to be used in generating the two-dimensional view by, for example, selecting two points on the plane or drawing a line in the desired plane. Processor 208 may be configured to generate a two-dimensional view (e.g., a vertical side profile view) of the weather cell data for the selected plane. In some embodiments, the user may select the plane by selecting an azimuth from the aircraft. In some embodiments, the user may select any plane in 3D perspective view screen 130, including a plane that does not intersect the current position of the aircraft. For example, if the aircraft is approaching a line of cells that are perpendicular to the current flight path of the aircraft (e.g., a squall line), the pilot may select a line that intersects the weather (e.g., a line approximately perpendicular to the flight line of the aircraft). A vertical profile view may then be generated based on the vertical plane associated with the selected line. The generated vertical profile view may allow the pilot to assess which cells have the greatest or least vertical extent.
In some embodiments, additional visual indicators other than the representation of weather may be provided within 3D perspective view screen 130. 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. In some embodiments, visual indicators may be provided to represent whether a cell is growing or decaying in size and/or severity (e.g., an up arrow for a growing cell and a down arrow for a decaying cell). In some embodiments, threat indicators may be provided to warn the user of threats associated with weather cells being approached by the aircraft, such as a predicted overflight condition.
Vertical 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, vertical weather prediction module 212 determines the range and altitude associated with the sensed weather. The range and altitude may be used so that vertical 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.
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 provide a temperature parameter 66, an azimuth 68, a position 70, a date 72, 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 vertical 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.
Display 110 is configured to provide a 3D perspective view of weather radar screen 286 that provides a visual representation of the three-dimensional weather profile constructed by vertical weather prediction module 212. In some embodiments, display 110 may additionally provide a plan view mode weather radar screen 282 and/or a vertical weather prediction mode screen 284. In one embodiment, the pilot can toggle between screens 282, 284, and 286 based upon a manual input. Alternatively, screens 282, 284, and/or 286 can automatically be provided on display 110 when the aircraft is in a particular flight mode, such as a rapid turn.
In some embodiments, processor 208 and/or module 212 may be implemented in software subroutines. The routines can be executed on one or more processors associated with system 200. In one embodiment, system 200 uses a hardware platform of a weather radar system manufactured by Rockwell Collins. However, the embodiments of the present disclosure are not limited to implementation on any particular type of hardware platform.
With reference to
Processor 208 can receive the radar returns (or signals/data related thereto) directly or through memory 206 (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.
Vertical weather prediction module 212 can generate a vertical weather profile at a given range and over a defined altitude (146). Vertical 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. The process may be repeated over an array of azimuth angles to generate a three-dimensional profile of the weather near (e.g., in front of) the aircraft.
Generating a vertical weather profile can include updating coefficients to a function whose inputs are a horizontal location to the weather and whose output is the reflectivity at any given altitude. The functions may be associated with a grid of horizontal location or may be associated with an individual weather feature such as a weather cell. Low altitude reflectivity can be used as a starting point for the estimation of radar reflectivity at an altitude. Low altitude reflectivity can be modified using the function or any other mathematical construct. The functions inputs may include many factors such as geography, atmospheric state, sensed weather feature horizontal or vertical size, sensed weather feature area, results from other sensor systems, time, date, etc.
Image data is provided for eventual conversion to a display signal for display 110 (160). The image data is for providing visual indicia of significant weather.
Referring now to
A weather radar system may be configured to generate a three-dimensional or perspective weather profile based on reflectivity data obtained from radar returns (405). For portions of the weather positioned above a freezing layer, the weather data for the three-dimensional weather profile may be estimated using a function that is based on a slope of a gradient associated with the airspace above the freezing layer (410). The slope may be based on a drop off in the maximum reflectivity of radar returns above the freezing layer. The gradient and the slope of the gradient may vary based on geographic location, time of day, time of year, weather cell characteristics, and/or other factors. The weather radar system may be configured to adjust the estimates for weather cell portions above the freezing level based on such factors. Once the three-dimensional weather profile has been constructed, the weather radar system may be configured to transmit display data to a display device causing the display device to display a visual representation of the three-dimensional weather profile (415). In some embodiments, user input may be received and may be used to rotate the displayed image in up to three dimensions, allowing the user to view a complete representation of the weather near the aircraft in both horizontal and vertical domains. The user input may include an indication that the user wishes to rotate the image and a desired direction of rotation. In various embodiments, the user input may include a hold and drag operation (e.g., a click or tap and drag), input including a magnitude and direction (e.g., a numerical input, such as an absolute magnitude or percentage), etc. For example, if the user taps and drags a point on the image to the right, the display may be configured to rotate the image about a vertical axis in the rightward direction. In another example, if the user taps and drags the point upward, the display may be configured to rotate the image about a horizontal axis in the upward direction. In still further examples, if the user taps and drags the point in a direction other than directly horizontal or vertical, such as diagonally, the image may be rotated along an axis that traverses multiple dimensions of the display coordinates.
Referring now to
When the three-dimensional perspective view of the weather near the aircraft is being displayed, a user may provide input via a user input device (e.g., touch-sensitive display) that represents a selection of a plane that the user wishes to use as the basis for a two-dimensional profile view (505). The plane selection may be provided by the user using any method, such as by selecting two points or drawing a line in the three-dimensional profile view. The weather radar system may be configured to determine the plane (e.g., vertical plane) associated with the user input selection and generate a two-dimensional profile view (e.g., vertical profile view) of the weather data along the selected plane (e.g., a two-dimensional cross section of the weather cells along the selected plane in the range and altitude domains) (510). The generated profile view may be presented to the user on the display device.
Referring now generally to
Image 600 also includes a range and bearing matrix 610 extending from a current position 605 of the aircraft through the weather cells along a current flight plane or altitude plane of the aircraft. Range markers 615 provide an indication of the range or distance from the current aircraft position to various portions of the displayed weather. Bearing markers 620 provide an indication of azimuths from a current bearing or flight path of the aircraft to the different portions of the displayed weather. Range and bearing matrix 610 may assist the pilot in making decision as to whether a flight path of the aircraft should be modified to avoid weather hazards near the aircraft.
Various portions of the weather patterns illustrated in
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 |
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 |
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 |
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 |
6456226 | Zheng et al. | Sep 2002 | B1 |
6480142 | Rubin | Nov 2002 | B1 |
6496252 | Whiteley | Dec 2002 | B1 |
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 |
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 |
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 |
7307756 | Walmsley | Dec 2007 | B2 |
7352317 | Finley et al. | Apr 2008 | B1 |
7352929 | Hagen et al. | Apr 2008 | B2 |
7372394 | Woodell et al. | May 2008 | B1 |
7383131 | Wey et al. | Jun 2008 | B1 |
7417579 | Woodell | Aug 2008 | B1 |
7427943 | Kronfeld et al. | Sep 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 |
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 |
7633431 | Wey et al. | Dec 2009 | B1 |
7696921 | Finley et al. | Apr 2010 | B1 |
7714767 | Kronfeld et al. | May 2010 | B1 |
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 |
8072368 | Woodell | Dec 2011 | B1 |
8089391 | Woodell et al. | Jan 2012 | B1 |
8111186 | Bunch et al. | Feb 2012 | B2 |
8159369 | Koenigs et al. | Apr 2012 | B1 |
8902100 | Woodell et al. | Dec 2014 | B1 |
20030001770 | Cornell et al. | Jan 2003 | A1 |
20050049789 | Kelly et al. | Mar 2005 | A1 |
20060036366 | Kelly et al. | Feb 2006 | A1 |
20110148694 | Bunch et al. | Jun 2011 | A1 |
20120139778 | Bunch et al. | Jun 2012 | A1 |
20130234884 | Bunch et al. | Sep 2013 | 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 |
---|
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 pages. |
RDR-4B Honeywell User Manual for Forward Looking Windshear Detection/Weather Radar System, Rev. 6, Jul. 2003, 106 pages. |
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. |
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.II.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. |
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. |
Kuntman, Airborne System to Address Leading Cause of Injuries in Non-Fatal Airline Accidents, ICAO Journal, Mar. 2000. |
Meteorological/KSC/L71557/Lighting Detection and Ranging (LDAR), Jan. 2002, 12 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. |