Weather radar system and method for high altitude crystal warning interface

Abstract

A hazard warning system can be utilized in an aircraft. The hazard warning system can include a processing system for determining a high altitude ice crystal (HAIC) condition and causing a warning of the HAIC condition to be displayed. An avionic display can be used to display the warning of the HAIC condition.

Claims

1. An aircraft hazard warning system, comprising: a processing system configured to detect a high altitude ice crystal (HAIC) or high altitude ice crystal cloud (HAIC.sup.2) condition and cause a warning of the HAIC or HAIC.sup.2 condition to be displayed, wherein the HAIC or HAIC.sup.2 warning is provided on a weather radar display such that weather regions in a same location as the HAIC or HAIC.sup.2 warning are viewable on the weather radar display, the HAIC or HAIC.sup.2 condition being detected using weather radar returns associated with a high altitude region, the weather radar returns being processed to detect the HAIC or HAIC.sup.2 condition, wherein the weather regions are provided as a solid green region for precipitation levels below a first level, a solid yellow region for precipitation levels above the first level below a second level, and a solid red region for precipitation levels above a third level, wherein the HAIC or HAIC.sup.2 warning is displayed as yellow dots or cross sectional lines on a weather region depicted as a solid green region, wherein the processing system detects a high altitude associated threat (HAAT) condition and wherein the weather radar display provides visual indicia according to the following table: TABLE-US-00002 HAIC Con- Weather or HAIC.sup.2 HAAT dition Display Color Condition Condition 1 Solid Red Red Yes Yes 2 Solid Yellow with Red Dots Yellow Yes Yes 3 Solid Green with Red Dots Green Yes Yes 4 Solid Red Red Yes No 5 Solid Yellow Yellow Yes No 6 Solid Green with Yellow Dots Green Yes No 7 Solid Red Red No Yes 8 Solid Yellow with Red Dots Yellow No Yes 9 Solid Green with Red Dots Green No Yes 10 Solid Red Red No No 11 Solid Yellow Yellow No No 12 Solid Green Green No No.

2. The aircraft hazard warning system of claim 1, wherein the warning of the HAIC or HAIC.sup.2 condition is provided as a speckled region, a striped region, or a region with outlined contours.

3. The aircraft warning system of claim 1, wherein the warning of the HAIC or HAIC.sup.2 condition is provided as a speckled region of a color indicating a lower level of hazard.

4. The aircraft warning system of claim 1, wherein the speckled region includes yellow dots.

5. The aircraft warning system of claim 1, wherein the HAAT condition is a lightning or hail condition.

6. The aircraft hazard warning system of claim 1, wherein the high altitude associated threat (HAAT) condition is a lightning condition.

7. The aircraft hazard warning system of claim 6, wherein the warning of the HAAT condition is displayed with a color symbolizing a higher threat level than the warning associated with the HAIC or HAIC.sup.2 condition.

8. The aircraft hazard warning system of claim 1, wherein the warning is displayed using a rectangular shaped region whereby the rectangular shaped region enhances the ability to notice the warning.

9. The aircraft hazard warning system of claim 8, wherein the warning of the HAIC or HAIC.sup.2 condition is provided corresponding to its size and location correlated on the weather radar display.

10. The aircraft hazard warning system of claim 9, wherein dots associated with a HAAT condition at the location overwrite dots associated with the HAIC condition at the location.

11. A method of providing a high altitude associated threat (HAAT) warning and one of at least a high altitude ice crystal (HAIC) or high altitude ice crystal cloud (HAIC.sup.2) warning on an aircraft using an electronic processor, the method comprising: receiving radar reflectivity data and determining at least one of a HAIC or HAIC.sup.2 condition exists; displaying the at least one of the HAIC or HAIC.sup.2 warning of the HAIC or HAIC.sup.2 condition over weather regions on a weather radar display, wherein the weather regions on the weather radar display are viewable when the at least one of the HAIC or HAIC.sup.2 warning is displayed; determining the HAAT condition exists; and displaying the HAAT warning over weather regions on a weather radar display, wherein the weather regions on the weather radar display are viewable when HAAT warning is displayed, and wherein the HAIC or HAIC.sup.2 warning is not viewable at locations where the HAAT warning is displayed, wherein the HAAT warning and HAIC or HAIC warnings are displayed according to the following table: TABLE-US-00003 HAIC Con- Weather or HAIC.sup.2 HAAT dition Display Color Condition Condition 1 Solid Red Red Yes Yes 2 Solid Yellow with Red Dots Yellow Yes Yes 3 Solid Green with Red Dots Green Yes Yes 4 Solid Red Red Yes No 5 Solid Yellow Yellow Yes No 6 Solid Green with Yellow Dots Green Yes No 7 Solid Red Red No Yes 8 Solid Yellow with Red Dots Yellow No Yes 9 Solid Green with Red Dots Green No Yes 10 Solid Red Red No No 11 Solid Yellow Yellow No No 12 Solid Green Green No No.

12. The method of claim 11, wherein the warning of the HAIC condition is provided on a weather radar display.

13. The method of claim 12, wherein the electronic processor is part of an avionic weather radar system.

14. The method of claim 12, wherein the warning of the HAIC condition is provided on a vertical display.

15. The method of claim 14, wherein the warning of the HAIC condition is provided on a plan view display.

16. The method of claim 15, wherein the warning of the HAIC condition is provided as a speckled region on the plan view display and the vertical display.

17. An aircraft weather radar system, comprising: a radar antenna for receiving radar returns; and means for determining a high altitude associated threat (HAAT) condition and at least one of a high altitude ice crystal (HAIC) or high altitude ice crystal cloud (HAIC.sup.2) condition and providing a warning of the HAAT condition and at least one of the HAIC or HAIC.sup.2 condition at least partially in response to the radar returns, wherein the means for determining performs one or more of the following to detect the presence: a dual frequency process; a dual polarization process; an ice crystal shape determination process; or a non-coherent integration and turbulence detection process; and means for displaying the at least one of the HAIC or HAIC.sup.2 warning over weather images, the at least one of the HAIC or HAIC.sup.2 warning being visual indicia, wherein the means for displaying provides the HAAT warning and the HAIC or HAIC.sup.2 warning according to the following table: TABLE-US-00004 HAIC Con- Weather or HAIC.sup.2 HAAT dition Display Color Condition Condition 1 Solid Red Red Yes Yes 2 Solid Yellow with Red Dots Yellow Yes Yes 3 Solid Green with Red Dots Green Yes Yes 4 Solid Red Red Yes No 5 Solid Yellow Yellow Yes No 6 Solid Green with Yellow Dots Green Yes No 7 Solid Red Red No Yes 8 Solid Yellow with Red Dots Yellow No Yes 9 Solid Green with Red Dots Green No Yes 10 Solid Red Red No No 11 Solid Yellow Yellow No No 12 Solid Green Green No No.

18. The weather radar system of claim 17 wherein the display means provides the warning of the HAIC condition as a stippled area, striped area or an outline.

19. The aircraft weather radar system of claim 17, wherein the (HAAT) condition is a lightning condition.

20. The aircraft weather radar system of claim 19, wherein the warning of the HAAT condition and the warning of the HAIC condition are provided as speckled regions, wherein the speckled regions have different colors.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) Exemplary embodiments will become more fully understood from the following detailed description, taken in conjunction with the accompanying drawings, wherein like reference numerals refer to like elements, and:

(2) FIG. 1 is a perspective view schematic illustration of an aircraft control center, according to an exemplary embodiment.

(3) FIG. 2 is a side view schematic illustration of the nose of an aircraft including a weather radar system, according to an exemplary embodiment.

(4) FIG. 3 is a general block diagram of a weather radar system including a high altitude ice crystal (HAIC) module, according to an exemplary embodiment.

(5) FIG. 4 is a general block of a horizontal plan view weather display showing a HAIC warning.

(6) FIG. 5 is a schematic illustration of an aviation horizontal plan view weather display showing a HAIC warning, according to an exemplary embodiment.

(7) FIG. 6 is a schematic illustration of an aviation horizontal plan view weather display showing a HAIC warning and a HAAT warning, according to an exemplary embodiment.

(8) FIG. 7 is a schematic illustration of an aviation horizontal plan view weather display showing a HAIC warning and a HAAT warning, according to an exemplary embodiment.

(9) FIG. 8 is a schematic illustration of an aviation vertical view weather display showing a HAIC warning and a HAAT warning, according to an exemplary embodiment.

DETAILED DESCRIPTION

(10) Referring generally to the FIGURES, systems and methods for indicating a weather threat to an aircraft are described, according to an exemplary embodiment. An airborne weather radar system is generally configured to project radar beams and to receive radar returns relating to the projected radar beams. The projected radar beams generally pass through air and reflect off of precipitation (e.g., rain, snow, etc.), other aircraft, and terrain (e.g., a mountain, a building). Using the reflected return data, processing electronics associated with the weather radar system can distinguish between types of precipitation and terrain. Weather radar systems are typically configured to display the precipitation as measured weather threats in green (light rain or precipitation), yellow (moderate rain or precipitation), and red (severe rain or precipitation). While this “rain gauge” provides valuable information to the crew, more specific indicators of weather threats to the aircraft are helpful to the crew. For example, high altitude associated threat (HAAT) and/or high altitude ice crystal (HAIC) threat warnings advantageously allow pilots to avoid regions detrimental to aircraft and their engines.

(11) Referring now to FIG. 1, an illustration of an aircraft control center or cockpit 10 is shown, according to an exemplary embodiment. Aircraft control center 10 includes flight displays 20 which are generally used to increase visual range and to enhance decision-making abilities. In an exemplary embodiment, flight displays 20 may provide an output from a radar system of the aircraft. For example, flight displays 20 may provide a top-down view, a horizontal view, vertical view/perspective or 3 dimensional view, or any other view of weather and/or terrain detected by a radar system on the aircraft. The views of weather may include monochrome or color graphical representations of the weather. Graphical representations of weather may include an indication of altitude of those objects or the altitude relative to the aircraft. Aircraft control center 10 may further include other user interface elements such as an audio device 30 (e.g., speaker, electro-acoustic transducer, etc.) and illuminating or flashing lamps 40. Weather can be displayed as colored regions on the aircraft according to ARINC standards.

(12) In one embodiment, a HAIC and/or HAAT warning can be provided on any of displays 20 as part of a weather radar display. In one embodiment, the HAAT warning is displayed as a red speckled region, and the HAIC warning is displayed as a yellow speckled region. The red speckled region indicates a higher severity of threat for the HAAT warning as compared to the yellow speckled region for the HAIC warning.

(13) Referring to FIG. 2, the front of an aircraft 101 is shown with aircraft control center 10 and nose 100, according to an exemplary embodiment. A radar system 300 (e.g., a weather radar system or other radar system) is generally located within nose 100 of aircraft 101 or within aircraft control center 10 of aircraft 101. According to various exemplary embodiments, radar system 300 may be located on the top of aircraft 101 or on the tail of aircraft 101 instead. Radar system 300 may include or be coupled to an antenna system. A variety of different antennas or radar systems may be used as part of system 300 (e.g., a split aperture antenna, a monopulse antenna, a sequential lobbing antenna, etc.).

(14) Radar system 300 generally works by sweeping a radar beam horizontally back and forth across the sky. Some embodiments of radar system 300 conduct a first horizontal sweep 104 at tilt angle 1 (108) and a second horizontal sweep 106 at tilt angle 2 (110). Tilt angles 108 and 110 can be with respect to horizontal 112 (e.g., 0 degrees). Radar system 300 can also conduct vertical sweeps to further characterize and identify weather phenomena. Returns from different tilt angles can be electronically merged to form a composite image for display on an electronic display 20 shown, for example, in FIG. 1. Returns can also be processed to, for example, distinguish between terrain and weather, to determine the height of terrain, or to determine the height of weather. Radar system 300 can be a WXR-2100 MultiScan™ radar system or similar system manufactured by Rockwell Collins and configured as described herein. According to other embodiments, radar system 300 may be an RDR-4000 system or similar system manufactured by Honeywell International, Inc. configured as described herein. Radar system 300 may be integrated with other avionic equipment and user interface elements in aircraft control center 10 (e.g., flashing lights 40, displays 20, display elements on a weather radar display, display elements on a terrain display, audio alerting devices 30, navigation systems, TAWs equipment, etc.).

(15) Referring to FIG. 3, a block diagram of radar system 300 embodied as a weather radar system is shown, according to an exemplary embodiment. Weather radar system 300 is shown to include a weather radar antenna 310 connected (e.g., directly, indirectly) to an antenna controller and receiver/transmitter circuit 302. Antenna controller and receiver/transmitter circuit 302 may include any number of mechanical or electrical circuitry components or modules for steering a radar beam. For example, circuit 302 may be configured to mechanically tilt the antenna in a first direction while mechanically rotating the antenna in a second direction. In other embodiments, a radar beam may be electronically swept along a first axis and mechanically swept along a second axis. In yet other embodiments, the radar beam may be entirely electronically steered (e.g., by electronically adjusting the phase of signals provided from adjacent antenna apertures, etc.). Circuit 302 may be configured to conduct the actual signal generation that results in a radar beam being provided from weather radar antenna 310 and to conduct the reception of returns received at radar antenna 310. Radar return data is provided from circuit 302 to processing electronics 304 for processing. For example, processing electronics 304 can be configured to interpret the returns for display on display 20.

(16) Processing electronics 304 can also be configured to provide control signals or control logic to circuit 302. For example, depending on pilot or situational inputs, processing electronics 304 may be configured to cause circuit 302 to change behavior or radar beam patterns. In other words, processing electronics 304 may include the processing logic for operating weather radar system 300. It should be noted that processing electronics 304 may be integrated into radar system 300 or located remotely from radar system 300, for example, in aircraft control center 10.

(17) Processing electronics 304 are further shown as connected to aircraft sensors 314 which may generally include any number of sensors configured to provide data to processing electronics 304. For example, sensors 314 could include temperature sensors, humidity sensors, infrared sensors, altitude sensors, a gyroscope, a global positioning system (GPS), or any other aircraft-mounted sensors that may be used to provide data to processing electronics 304. It should be appreciated that sensors 314 (or any other component shown connected to processing electronics 304) may be indirectly or directly connected to processing electronics 304. Processing electronics 304 are further shown as connected to avionics equipment 312 and include a high altitude ice crystal (HAIC) module 340 and a high altitude associated threat (HAAT) module 334. Modules 340 and 334 advantageously detect and locate HAIC and HAAT conditions and cause display 20 to provide a visual and/or audio warning of such conditions. Modules 334 and 340 process data associated with weather radar reflectivity levels and data from other sensors (e.g., temperature, altitude, etc.) to determine HAIC and HAAT conditions. Avionics equipment 312 can be or include a flight management system, a navigation system, a backup navigation system, or another aircraft system configured to provide inputs to processing electronics 304.

(18) Referring to FIG. 4, a detailed block diagram of processing electronics 304 of FIG. 3 is shown, according to an exemplary embodiment. Processing electronics 304 includes a memory 320 and processor 322. Processor 322 may be or include one or more microprocessors, an application specific integrated circuit (ASIC), a circuit containing one or more processing components, a group of distributed processing components, circuitry for supporting a microprocessor, or other hardware configured for processing. According to an exemplary embodiment, processor 322 is configured to execute computer code stored in memory 320 to complete and facilitate the activities described herein. Memory 320 can be any volatile or non-volatile memory device capable of storing data or computer code relating to the activities described herein. For example, memory 320 is shown to include modules 328-340 which are computer code modules (e.g., executable code, object code, source code, script code, machine code, etc.) configured for execution by processor 322. When executed by processor 322, processing electronics 304 is configured to complete the activities described herein. Processing electronics 304 includes hardware circuitry for supporting the execution of the computer code of modules 328-340. For example, processing electronics 304 includes hardware interfaces (e.g., output 350) for communicating control signals (e.g., analog, digital) from processing electronics 304 to circuit 302 or to display 20. Processing electronics 304 may also include an input 355 for receiving, for example, radar return data from circuit 302, feedback signals from circuit 302 or for receiving data or signals from other systems or devices.

(19) Memory 320 includes a memory buffer 324 for receiving radar return data. The radar return data may be stored in memory buffer 324 until buffer 324 is accessed for data. For example, a core threat module 328, overflight module 330, electrified region module 332, HAAT module 334, display control module 338, HAIC module 340 or another process that utilizes radar return data may access buffer 324. The radar return data stored in memory 320 may be stored according to a variety of schemes or formats. For example, the radar return data may be stored in an x,y or x,y,z format, a heading-up format, a north-up format, a latitude-longitude format, a radial format, or any other suitable format for storing spatial-relative information.

(20) Memory 320 further includes configuration data 326. Configuration data 326 includes data relating to weather radar system 300. For example, configuration data 326 may include beam pattern data which may be data that a beam control module 336 can interpret to determine how to command circuit 302 to sweep a radar beam. For example, configuration data 326 may include information regarding maximum and minimum azimuth angles of horizontal radar beam sweeps, azimuth angles at which to conduct vertical radar beam sweeps, timing information, speed of movement information, and the like. Configuration data 326 may also include data, such as threshold values, model information, look up tables, and the like used by modules 328-340 to identify and assess threats to aircraft 101.

(21) Memory 320 is further shown to include a core threat module 328 which includes logic for using radar returns in memory buffer 324 to make one or more determinations or inferences relating to core threats to aircraft 101. For example, core threat module 328 may use temperature and radar return values at various altitudes to calculate a probability that lightning, hail, and/or strong vertical shearing exists within a weather cell. Core threat module 328 may be configured to compare the probability and/or severity of the core threat to a threshold value stored, for example, in core threat module 328 or configuration data 326. Core threat module 328 may further be configured to output a signal to display control module 338 indicative of the probability of the core threat, of the inferred threat level within the weather cell, or of the inferred threat level within the weather cell being greater than the measured threat due to radar returns from rainfall. The signal may further cause a change in a color on aviation display 20 associated to the threat level to aircraft 101.

(22) Memory 320 is further shown to include an overflight module 330 which includes logic for using radar returns in memory buffer 324 to make one or more determinations or inferences based on weather below aircraft 101. For example, overflight module 330 may be configured to determine the growth rate of a weather cell and/or the change in altitude of an echo top of a weather cell over time. Overflight module 330 may further be configured to calculate a probability that a weather cell will grow into the flight path of aircraft 101. Overflight module 330 may be configured to output a signal to display control module 338 indicating the threat of the growing weather cell in relation to the flight path of aircraft 101. For example, the signal may indicate predicted intersection of the flight path of aircraft 101 and the weather cell, rate of growth of the weather cell, or predicted growth of the weather cell to within a threshold distance of the flight path of aircraft 101. For example, the signal may cause an icon to be displayed on aviation display 20 in a location corresponding to the growing cell, wherein the size of the icon may represent the size, amount, or probability of threat to the aircraft. Overflight module 330 may be configured to inhibit display of weather far below, and thus not a threat to, aircraft 101.

(23) Memory 320 is further shown to include an electrified region module 332 which includes logic for using radar returns in memory buffer 324 to make one or more determinations or inferences regarding potentially electrified regions around the weather cell. For example, electrified region module 332 may be configured to use temperature and reflectivity to determine whether a region around a weather cell is likely to produce lightning. Electrified region module 332 may be configured to determine a probability of aircraft 101 producing a lightning strike if the aircraft flies through a particular region based on the reflectivity around a convective cell near the freezing layer. Electrified region module 332 may further be configured to cause a pattern to be displayed on aviation display 20. For example, electrified region module 332 may be configured to output a signal to display control module 338 indicating the existence, location, and/or severity of risk of the electrified region.

(24) Memory 320 is further shown to include HAAT module 334 which includes logic for using radar returns (e.g., data) in memory buffer 324 to make one or more determinations or inferences regarding high altitude associated threats (e.g., threats related to a blow off or anvil region of a weather cell). HAAT conditions can be associated with high severity threat conditions such as hail, lightning, turbulence, etc. For example, HAAT module 334 may be configured to use wind speed, wind direction, and size of a weather cell to predict the presence of an anvil region downwind of a weather cell that may contain lightning, hail, and/or turbulence. HAAT module 334 may be configured to cause a pattern (e.g., a red speckled region) to be displayed on an aviation display 20. For example, HAAT module 334 and module 338 can be configured to output a signal to display control module 338 indicating the existence, location, and severity or risk of the anvil region. HAAT module 334 can detect a HAAT condition based upon the presence of convective cells reaching high altitudes and having anvil shapes. Such conditions can be sensed using the techniques described in U.S. application Ser. No. 13/919,406 now U.S. Pat. No. 9,244,157 and Ser. No. 13/841,893 now U.S. Pat. No. 9,244,166. Ice crystals may be present in a HAAT region. A HAAT condition generally is a more significant threat than a HAIC condition. HAAT conditions 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 with a highly reflective weather region. High altitude associated 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. 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.

(25) In one embodiment, HAIC module 340 can infer a HAIC condition. In one embodiment, the HAIC condition can be inferred by the following process. If radar system 300 detects temperature anomalies and large areas of weaker reflectivity in the vicinity of a convective core, vertical scans and/or auxiliary horizontal scans can be commanded via module 336 to look for the presence of high water content (high reflectivity) beneath the areas that were depicted as weaker reflectivity (green or black). If such a scenario is identified using the vertical and horizontal beams, the area is tagged as potential for ice crystal icing or a HAIC condition. HAIC module 340 and weather radar system 300 can be configured to use coherent and non-coherent integration processes to detect presence of the HAIC or HAIC.sup.2 condition and its location in one embodiment. Alternatively, module 340 and weather radar system 300 can utilize a dual frequency or dual polarization process. In one embodiment, HAIC or HAIC.sup.2 module receives data associated with weather returns at high altitude and processes the data to determine existence of a HAIC or HAIC.sup.2 condition. The data can be processed by comparing the data to known ice crystal return characteristics to determine a match and therefore a HAIC or HAIC.sup.2 condition. In one embodiment, module 340 senses only one of a HAIC or HAIC.sup.2 condition. As described above, processing electronics 304 uses avionics and radar return information to infer or detect existence of a HAIC or HAIC.sup.2 condition via module 340.

(26) In one embodiment, the HAIC and HAIC.sup.2 condition or region shown on the display 20 may be a composite threat display showing on the same display the HAIC and HAIC.sup.2 threats detected by system 300 and the HAIC and HAIC.sup.2 threats detected or inferred by other HAIC detection sources, including other on-board systems (infrared, LIDAR, etc.), or remote systems (e.g., ground-based radar, satellites, etc.). At any given location, the most significant threat from any of the possible sources may be displayed. In one embodiment, HAIC or HAIC.sup.2 module 340 can us an inferential process to detect a HAIC or HAIC.sup.2 condition. In one embodiment, the HAIC or HAIC.sup.2 condition can be inferred by sensing temperature anomalies and reflectivity characteristics associated with core threats. In such a process, if radar system 300 detects temperature anomalies. A temperature anomaly can be a condition where temperature detected by system 300 (e.g., a temperature sensor (e.g., Full Authority Digital Engine Control (FADEC) saturated temperature input) of sensors 314) is different than a predicted (e.g. expected) or baseline atmospheric temperature. The temperature can be a saturated temperature value in one embodiment. The temperature value can be adjusted for heating caused by the movement of aircraft 101 through the atmosphere in one embodiment. The predictive or baseline temperature can be from satellite trip information. A large discrepancy (e.g., 15 degrees or more) between the actual temperature and the predicted temperature at the altitude of the aircraft 101 can indicate a potential icing condition according to one embodiment. In one embodiment, a local temperature reading more than 15 degrees warmer than the expected temperature indicates an anomaly. A low pass filter or averaging technique can be used to prevent a spurious reading from improperly causing a temperature anomaly to be detected.

(27) Weather radar system 300 may optionally receive data from another on-board HAIC detection source (e.g., infrared, LIDAR, etc.) or a remote systems HAIC detection source (e.g., ground-based radar, satellites, etc.) in one embodiment. System 300 identifies convective cells or cores in some embodiments. Convective cores can be identified using cell height, cell growth, and other analysis techniques. Generally, cores in front of or along the flight path of the aircraft are identified for further analysis, according to one embodiment. Cores can be identified using core threat module 328. Cores can be identified by analyzing spectral characteristics in areas of higher reflectivity in one embodiment. In one embodiment, the information can be used to identify cores or increase confidence in the cores identified using radar parameters. System 300 scans the environment and identifies large areas (e.g. more than a square nm, several square nms, ten square nm, etc.) of weaker reflectivity in the vicinity of a convective core. Areas for scanning are chosen based upon a presence of core cells.

(28) In one embodiment, HAIC detection assessment or inference may also be performed by other sensors on board the aircraft (infrared, LIDAR, etc.) or off the aircraft by ground radars or satellites. The HAIC detection assessment or inference information may be optionally input to system 300 for identification of the HAIC or HAIC.sup.2 region in one embodiment. When the HAIC detection assessment or inference information is input into system 300, the scanning region or location of the radar beams may be directed to scan that region and a higher confidence of the HAIC threat can be determined. HAIC and HAIC.sup.2 conditions are caused by strong updrafts that also created turbulence. The Doppler processing of the radar returns or off-aircraft wind information can provide additional information for detection of HAIC and HAIC.sup.2 regions. If a HAIC or HAIC.sup.2 region is detected, it may be qualified by a turbulence (spectral width) or vertical wind speed as qualifier to determine if HAIC or HAIC.sup.2 are present. In one embodiment, vertical scans and/or auxiliary horizontal scans can be commanded via module 336 to look for the presence of high water content (high reflectivity) beneath the areas that were depicted as weaker reflectivity (green or black). If such a scenario is identified using the vertical and horizontal beams, the area is tagged or identified as a potential area for ice crystal icing or a HAIC or HAIC.sup.2 condition by module 340 in one embodiment. The area can be identified on display 20 with a HAIC or HAIC.sup.2 warning. High water content can be identified by using a vertical integrated liquid (VIL) measurement or a reflectivity measurement in one embodiment.

(29) Module 340 includes an inferential detection path which uses a temperature anomaly detector, and a return data analysis module. Module 340 can receive core threat indications from module 328. The temperature anomaly detector compares the sensed outside temperature at or near the altitude of aircraft 101 with the expected temperature at the altitude in accordance with the atmosphere conditions. The expected temperatures can be provided by or derived from data received real time or received during flight preparation. Temperature readings in NEXRAD data can be utilized by the detector for expected temperature values. Once a temperature anomaly is detected, module 340 can provide vertical and horizontal radar returns to an area in the vicinity of a weather cell core as detected by core module 328 according to one embodiment. Various algorithms and techniques can analyze radar returns to determine a HAIC or HAIC.sup.2 condition. In one embodiment, if the return data analyzer determines that a yellow or higher region is directly in front of aircraft 101 when the temperature anomaly detector detects the temperature anomaly, system 300 identifies a HAIC or HAIC.sup.2 condition in front of aircraft 101. Alternatively, module 340 can analyze radar returns for a HAIC or HAIC.sup.2 condition. Beam control module 336 under control of module 340 can have antenna 310 provide beams to the areas in the vicinity of cores found by core threat module 328. When reflectivities from these areas indicate that higher reflectivity is located at a location below the freezing level, module 340 provides an indicator of the presence of a HAIC or HAIC.sup.2 condition in one embodiment. For example, if precipitation rates associated with a red or yellow region are detected below the freezing level, a HAIC or HAIC.sup.2 condition is present.

(30) HAIC or HAIC.sup.2 module 340 can directly detect a HAIC or HAIC.sup.2 condition using a combination of coherent and non-coherent integration path. The path receives a series of inphase I signals associated with an IQ demodulated signal from radar returns and a series of quadrature phase Q signals associated with the IQ data from radar returns from coherent integrators respectively. The one integrator provides a value I.sub.K according to the equation Σ.sub.k=1.sup.N.sup.PI.sub.k in one embodiment. Another integrator provides the value Q.sub.K according to the equation Σ.sub.k=1.sup.N.sup.PQ.sub.k in one embodiment. N.sub.P is the number of pulses in the coherent integrator, and these coherent sums are updated at a rate R.sub.PRF/N.sub.P where R.sub.PRF is the pulse repetition frequency. In one embodiment, system 300 provides multiple rapid pulses on target. An amplitude detector determines the amplitude associated with each combination of I.sub.K and OK according to the equation Z.sub.K=I.sub.K.sup.2+Q.sub.K.sup.2 in one embodiment. I.sub.K and Q.sub.K represent voltage values at the output of the coherent integrators 602 and 604 associated with return data. These sums can be implemented with a Fourier transform that also will provide Doppler information. The detector can be any monotonic function of the input I.sub.K.sup.2+Q.sub.K.sup.2, e.g., a logarithm or a square root. A non-coherent integrator non-coherently sums the values of Z according to the equation ζ=Σ.sub.K=1.sup.N.sup.DZ.sub.K N.sub.D is the number of dwells over which non-coherent integration is performed, and the update rate of ζ is R.sub.PRF/(N.sub.PN.sub.D). Non-coherent integration after the amplitude detector is less efficient than coherent integration, but does not require signal coherence from dwell to dwell (both in phase and amplitude). A detector determines if the value from the integrator is greater than a threshold value T. If so, the data is further processed to determine if a HAIC or HAIC.sup.2 condition is detected.

(31) Various algorithms or techniques can be utilized to discriminate a HAIC or HAIC.sup.2 condition from the radar return data. Module 340 can compare the characteristics of the radar data to known ice crystal reflectivity characteristics to determine a HAIC or HAIC.sup.2 condition. For example, a HAIC.sup.2 condition can be determined when reflectivity levels are above a level zero or nominal level and less than a level associated with liquid precipitation. According to another example, the algorithm can utilize temperature and reflectivity to determine the presence of a HAIC or HAIC.sup.2 condition. According to another embodiment, a HAIC or HAIC.sup.2 condition can be determined if the appropriate reflectivity level is provided across a significant area (e.g., many range bins). According to yet another embodiment, temperature, combined with reflectivity level or area and reflectivity level can be utilized to determine the presence of a HAIC or HAIC.sup.2 condition. In another embodiment, the radar returns are processed to determine whether the radar returns indicate spherical targets which are more likely water or non-spherical targets which are more likely ice crystals. In one embodiment, if the temperature is below temperature threshold (e.g. −20 degrees Celsius), the reflectivity level is consistent with ice crystal levels and the altitude is above a threshold (e.g. 10,000 feet), a HAIC or HAIC.sup.2 condition is detected. In one embodiment, modern fuzzy logic techniques can be utilized to detect and discriminate HAIC.sup.2 conditions. The reflectivity characteristics of known HAIC and HAIC.sup.2 can be stored and used for comparisons. In one embodiment, HAIC and HAIC.sup.2 can be stored with respect to particular locations or locations types (e.g., continental, maritime, etc.) and/or seasons and the comparisons can be made with consideration of location and/or season. If the detector detects that the value from the non-coherent integrator is less than the value T, a HAIC or HAIC.sup.2 condition is not detected. The value T represents a threshold power value for a HAIC or HAIC.sup.2 evaluation. Evaluation can be performed by analyzer 612 to identify regions of HAIC or HAIC.sup.2 conditions in one embodiment. A qualifier 614 can use detection of turbulence to qualify the regions of HAIC or HAIC.sup.2 conditions in one embodiment. Doppler processing or off-aircraft wind information can be used to qualify the regions in one embodiment. Advantageously, module 340 allows ice crystals to be detected across a longer distance.

(32) The module 340 advantageously serves to coherently integrate the pulses within a dwell using the integrators and non-coherently integrating the energy from each dwell using the amplitude detector and the non-coherent integrator. The combination of coherent and non-coherent integration allows for HAIC or HAIC.sup.2 decorrelation over the integration period in one embodiment. Integration is done over time scales shorter than the radar scan time in one embodiment. The path advantageously increases detection range to a point where discrimination and avoidance of HAIC regions are feasible for aircraft 101. Advantageously, the path can use the same pulses as used for X band weather radar to avoid disruption of other radar-sensing operations in one embodiment. Although the integration period degrades angular resolution of the data, it is an acceptable tradeoff to determine HAIC or HAIC.sup.2 conditions.

(33) Memory 320 is further shown to include HAIC module 340 which includes logic for using radar returns in memory buffer 324 to make one or more determinations or inferences regarding threats related to a HAIC condition. Module 340 can be combined with module 338, be a hard wired ASIC, or programmable logic circuit in one embodiment. HAIC module 340 and weather radar system 300 can be configured to use coherent and non-coherent integration processes discussed in related U.S. application Ser. No. 14/206,239 (047141-0977) incorporated herein by reference to detect presence of the HAIC condition and its location in one embodiment. Alternatively, module 340 and weather radar system 300 can utilize a dual frequency or dual polarization process discussed in related U.S. patent application Ser. No. 14/206,651 (047141-0979) incorporated herein by reference in one embodiment. In one embodiment, HAIC module receives data associated with weather returns at high altitude and processes the data to determine existence of a HAIC condition. The data can be processed by comparing the data to known ice crystal return characteristics to determine a match and therefore a HAIC condition.

(34) HAIC module 340 and module 338 can be configured to cause a pattern (e.g., a yellow speckled region) to be displayed on an aviation display 20 in one embodiment. HAIC module 340 is configured to output a signal or data to display control module 338 indicating the existence, location, and severity or risk of the HAIC condition or region in one embodiment. Module 338 can cause the appropriate video signal to be provided to display 20.

(35) Memory 320 is further shown to include a beam control module 336. Beam control module 336 may be an algorithm for commanding circuit 302 to sweep a radar beam. Beam control module 336 may be used, for example, to send one or more analog or digital control signals to circuit 302. The control signals may be, for example, an instruction to move the antenna mechanically, an instruction to conduct an electronic beam sweep in a certain way, an instruction to move the radar beam to the left by five degrees, etc. Beam control module 336 may be configured to control timing of the beam sweeps or movements relative to aircraft speed, flight path information, transmission or reception characteristics from weather radar system 300 or otherwise. Beam control module 336 may receive data from configuration data 326 for configuring the movement of the radar beam.

(36) Memory 320 is further shown to include a display control module 338 which includes logic for displaying weather information on aviation display 20. For example, display control module 338 may be configured to display radar return information received from memory buffer 324 and to determine a gain level or other display setting for display of an inferred threat to aircraft 101 on a weather radar display. Display control module 338 may be configured to receive signals relating to threats to aircraft 101 from core threat module 328, overflight module 330, electrified region module 332, HAAT 334, and HAIC module 340. Display control module 338 may further be configured to cause, in response to one or more signals received from threat modules 328-334 and 340 and threshold values from configuration data 326, a change in color of a portion of an image on aviation display 20, a pattern (e.g., a speckled region) to be overlaid on an image on aviation display 20, and an icon to be shown on aviation display 20. Display control module 338 may be configured to cause a change in size, location, shape, or color of the colored regions, patterns, symbols, and/or icons in response to updated signals received from modules 328-336 and 340.

(37) Processing electronics 304 may be configured to use none, some, or all of the threat modules 328-334 and 340 described above. For example, processing electronics 304 may have an automatic mode, in which weather radar antenna 310 is automatically controlled (e.g., direction, gain, etc.) and core threat module 328, overflight module 330, electrified region module 332, HAAT module 334 and HAIC module 340 are all processing information looking for inferred threats. Processing electronics 304 can have a manual mode, in which one or more of core threat module 328, overflight module 330, electrified region module 332, HAAT module 334 and HAIC module 340 are disabled, for example, for diagnostic purposes.

(38) Referring now to FIG. 5, a schematic illustration of aviation display 20 showing a weather radar display 500 including precipitative (or weather) regions 502, 504, and 506 corresponding to radar returns according to an exemplary embodiment. Processing electronics 304 may be configured to cause aviation display 20 to show measured threats to aircraft 101 using symbology, icons, or text. In FIG. 5, light rain is shown as a slanted down right to left cross hatched area region (e.g., region 502), which is often indicated with a green color on display 20. A moderate rain is shown as a slanted down left to right cross hatched region (e.g., region 504) in FIG. 5 often colored yellow on display 20 to indicate caution to the crew. Solid black regions (e.g., region 506) in FIG. 5 correspond to heavy rain, and are usually colored red on display 20 to indicate warning to the crew. The area outside of regions 502, 504, and 506 can have a black color on display 20 to indicate a very low or zero precipitation rate in one embodiment. Region 502, 504, and 506 can be shown in accordance with Federal Aviation Administration (FAA) standards.

(39) Generally, a crew flies through green regions 502, always avoids red regions 506, and uses their best judgment on yellow regions 504. In the example shown, a crew heading to the right of the aircraft's track on display 500 may decide to bank right and fly through regions 502 rather than climbing or banking left to avoid the weather cell (region 506) directly in front of aircraft 101 and region 503 which represents a HAIC condition.

(40) As described above, processing electronics 304 uses avionics and radar return information to infer or detect existence of a HAIC condition via module 340. The HAIC condition can be symbolized as a stippled region 503 on display 20. Region 503 can be stippled using yellow dots to signify caution. Alternatively, cross hatching or other dot colors can be utilized to show region 503. Region 503 can have a border 513 in yellow or other color or no border at all.

(41) A caution level coloring for region 503 is chosen because icing threats generally require an exposure time in the region of HAIC conditions. Applicants believe that an exposure time associated a 50-100 nautical miles (nm) of travel can expose aircraft 101 to detrimental icing.

(42) With reference to FIG. 6, processing electronics 304 uses avionics and radar return information to infer or detect HAAT condition indicated by region 512 as well as HAIC conditions indicated by regions 503 on a display 550 similar to display 500. Display 550 also includes regions 502, 504, and 506. In one embodiment, region 512 is shown as a stippled area with red dots or dots of other color indicating a hazardous area. Alternatively, cross hatched areas can be utilized for area or region 512. A border similar to border 513 can be provided for region 512 having a matching color to the dots in the stippled area. In one embodiment, region 512 does not have a border. Precipitation levels of weather can be shown beneath regions 503 and 512 (e.g., regions 503 and 512 can be overlaid on other weather regions showing the underlying weather beneath the speckled areas). Region 512 can be inferred as a HAAT region on a downwind side of a high altitude, high conductivity cell.

(43) In an alternative embodiment, the speckles of regions 503 and 512 are the same color. However, speckles for region 512 have a larger size to signify a HAAT condition as opposed to smaller speckles for a HAIC condition in one embodiment. In an alternative embodiment, a checkered pattern can be utilized for regions 503 and 512. With reference to FIGS. 5 and 6, regions 503 and 512 are shown on a radial-by-radial basis or cell-by-cell basis.

(44) With reference to FIG. 7, a region 702 indicating a HAIC condition is shown as a rectangular region correlated to its location on a display 700. As shown in FIG. 7, a region 704 associated with a HAAT condition is provided with a region 702 on display 700 in one embodiment. Speckles or dots of red in region 704 are aligned with and overwrite the speckles or dots of yellow in region 702 in one embodiment. The use of the rectangular shapes for regions 702 and 704 makes it easier to notice such regions. Precipitation levels of region 506 are viewable through regions 702 and 704 in one embodiment.

(45) With reference to FIG. 8, displays 500, 550, and 700 can be utilized in conjunction with the display 600 of FIG. 8. Alternatively, FIG. 8 can be utilized by itself. Display 600 is a vertical display having altitude on an Y axis 601 and range on a X axis 602. Region 604 of weather does not include a region for HAIC condition or a region for a HAAT condition. However, region 606 of weather includes a region 608 corresponding to a HAIC condition and a region 610 indicating a HAAT condition. Vertical display 600 allows the pilot to view the altitude necessary to clear HAAT conditions and HAIC conditions. In the example of FIG. 8, display 600 is not correlated to displays 500, 550 or 700. However, display 600 can be correlated with displays 500, 550, or 700 according to vertical weather display operation with plan view displays.

(46) In one embodiment, the density of speckles on any of displays 500, 550, 600 or 700 can have a density corresponding to the level of threat of the HAIC condition. Higher density of ice can correspond to higher density dots in regions 502 or 702 in one embodiment. Larger sizes of ice can correspond to higher density dots or speckles in regions 502 or 702 in one embodiment. The level of threat associated with HAAT conditions can be similarly displayed. Modules 334 and 340 can determine the level of threat. In one embodiment, the size of speckles on any of displays 500, 550, 600 or 700 can correspond to the level of threat of the HAIC condition.

(47) In one embodiment, module 338 provides an overwriting scheme when weather regions and HAIC and HAAT conditions occur in the same area. Table 1 below provides an exemplary scheme.

(48) TABLE-US-00001 TABLE 1 Weather HAIC HAAT Condition Display Color Condition Condition 1 Solid Red Red Yes Yes 2 Solid Yellow with Red Dots Yellow Yes Yes 3 Solid Green with Red Dots Green Yes Yes 4 Solid Red Red Yes No 5 Solid Yellow Yellow Yes No 6 Solid Green with Yellow Green Yes No Dots 7 Solid Red Red No Yes 8 Solid Yellow with Red Dots Yellow No Yes 9 Solid Green with Red Dots Green No Yes 10 Solid Red Red No No 11 Solid Yellow Yellow No No 12 Solid Green Green No No

(49) In certain embodiments, condition 5 can be displayed using an indication similar to region 702 of the HAIC condition such as showing the region in a rectangular form. Alternatively, a cross hatching can be utilized to indicate the HAIC condition in a yellow weather region. Alternatively, a text or other symbol can be used.

(50) Similarly, crosshatching, text, rectangular regions, (e.g., region 704), etc. can be used for conditions 1 and 7 when a HAAT condition is at a red weather region. In one embodiment, a rectangular region can be used for conditions 1-7 to show the presence of a HAAT condition or a HAIC condition.

(51) The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements may be reversed or otherwise varied and the nature or number of discrete elements or positions may be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps may be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.

(52) According to various exemplary embodiments, electronics 304 may be embodied as hardware and/or software. In exemplary embodiments where the processes are embodied as software, the processes may be executed as computer code on any processing or hardware architecture (e.g., a computing platform that can receive reflectivity data from a weather radar system) or in any weather radar system such as the WXR-2100 system available from Rockwell Collins, Inc. or an RDR-400 system available from Honeywell, Inc. The processes can be performed separately, simultaneously, sequentially or independently with respect to each other.

(53) While the detailed drawings, specific examples, detailed algorithms and particular configurations given describe preferred and exemplary embodiments, they serve the purpose of illustration only. The inventions disclosed are not limited to the specific forms and equations shown. For example, the methods may be performed in any of a variety of sequence of steps or according to any of a variety of mathematical formulas. The hardware and software configurations shown and described may differ depending on the chosen performance characteristics and physical characteristics of the weather radar and processing devices. For example, the type of system components and their interconnections may differ. The systems and methods depicted and described are not limited to the precise details and conditions disclosed. The flow charts show preferred exemplary operations only. The specific data types and operations are shown in a non-limiting fashion. Furthermore, other substitutions, modifications, changes, and omissions may be made in the design, operating conditions, and arrangement of the exemplary embodiments without departing from the scope of the invention as expressed in the appended claims.

(54) Some embodiments within the scope of the present disclosure may 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 include RAM, ROM, EPROM, EEPROM, CD ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other 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 include, 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. Machine or computer-readable storage media, as referenced herein, do not include transitory media (i.e., signals in space).