This application is a U.S. National Phase application of PCT Application No. PCT/US2008/077613 filed on Sep. 25, 2008.
The present application relates to aircraft instrumentation, and more particularly to graphical munitions release symbology.
Aircrew on attack runs must manage significant information over a short timescale. Munitions released from an aircraft must be released within a particular munition release envelope to maximize effective deployment. Textual data and inhibits are typically provided to determine whether the munitions may be released given the munition type, target location and current aircraft parameters. The data may in some cases be difficult for the aircrew to readily interpret during an attack run.
A method for displaying a munition release envelope according to an exemplary aspect of the present application includes displaying a geometric munition release area with respect to an altitude scale and an airspeed scale and displaying a current aircraft state relative the geometric munition release area.
A module for displaying a munition release envelope according to an exemplary aspect of the present application includes a module for munition release in communication with a display system to display a geometric munition release area with respect to an altitude scale and an airspeed scale and to display a current aircraft state relative to the geometric munition release area.
A flight display for an aircraft according to an exemplary aspect of the present application includes a geometric munition release area with respect to an altitude scale and an airspeed scale and a current aircraft state indicator positioned relative to said geometric munition release area.
Various features will become apparent to those skilled in the art from the following detailed description of the disclosed non-limiting embodiment. The drawings that accompany the detailed description can be briefly described as follows:
The aircraft 10 may carry munitions 20 such as torpedoes, sonobuoys, depth charges, mines, missiles and other devices which must be released within a particular munition release envelope. The munition release envelope typically differs dependent upon munition type and aircraft flight condition.
Referring to
The flight computer 30 includes or communicates with a multiple of modules such as a module 34 for munition release. It should be understood by those skilled in the art with the benefit of this disclosure that although the module 34 is illustrated as in communication with a mission computer within the aircraft avionics system 22, the functions provided thereby may be enacted in dedicated hardware circuitry or programmed software routines capable of execution in any of the systems disclosed as blocks. The flight computer 30 communicates with other avionics systems and modules such as mission computers, FADECs, active inceptor systems and the display system 32. It should be understood that the term “module” as utilized herein may be dedicated or multi-functional hardware or software within the flight computer 30, a stand-alone module as illustrated in the disclosed non-limiting embodiment, or other system that utilizes data and control algorithms for operation of various systems and subsystems. The various systems and subsystems may include, for example, flight control systems, weapons systems, mission computers, air data computers, engine systems, sensor systems, collision and avoidance systems, as well as other types of systems currently installed or planned for future aircraft applications.
The module 34 for munition release may include a processor 34A, a memory 34B, and an interface 34C. The processor 34A may be a custom made or commercially available power PC type processor, a central processing unit, a processor among several processors associated with the flight computer 30, a semiconductor based microprocessor in the form of a microchip or chip set or generally any device for executing software instructions such as software stored in memory 34B to provide the desired performance characteristics. The memory 34B can include any one or combination of volatile memory elements, for example, random access memory such as RAM, DRAM, SRAM, SDRAM, VRAM, etc. and/or nonvolatile memory elements, for example, ROM, hard drive, tape, CD-ROM, etc. Moreover, the memory may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory 34B can also have a distributed architecture, where various components are situated remotely from one another, but can be accessed by the processor 34A. The interface 34C communicates with the display system 32 and the flight computer 30 through the data bus 31 to control aircraft systems and display information received from other avionics systems.
The module 34 for munition release may obtain aircraft dynamic state, ambient conditions as well as other data from the flight computer 30 for display on the display system 32. The module 34 for munitions release stores data and control algorithms such as a munition release envelope algorithm 36 in the memory device 34B or other computer readable medium for operation of the processor 34A. The stored data and control algorithms are the scheme by which decisions are made to perform operations disclosed herein. The algorithm 36 may be defined by software in the memory 34B. When in operation, the processor 34A may be configured to execute the algorithm 36 stored within the memory 34B and to generally control operations pursuant to the software.
The module 34 for munition release performs the munition release envelope algorithm 36. The functions of the algorithm 36 are schematically disclosed in terms of a functional block diagram format (
Referring to
Referring to
The munition release symbology 40 is generally displayed in either a forward flight mode (
In the forward flight mode (
If the aircraft indicator 50 is positioned within the geometric munition release area 44, the munition is within the munition release envelope such that immediate release is available to the aircrew. The geometric munition release area 44 may also be color coded—for example green—to further communicate that immediate release is available to the aircrew.
Referring to
The algorithm 36 also operates to display what corrective flight action is most efficient such as a change in altitude or a change in airspeed to correct the flight condition inhibits. In this non-limiting embodiment, it is more efficient to reduce altitude. The reduction in altitude may be indicated by relative color coding of the airspeed scale 46 and the altitude scale 48. The altitude scale 48 may be color coded to indicate out of limits—for example red—while the airspeed scale 46 may be color coded to indicate in limits—for example white—to thereby readily suggest the most efficient corrective flight actions to the aircrew. In one non-limiting embodiment, the munition release symbology 40 may be displayed in accords with the following table:
It should be understood that other symbology such as arrows may alternatively or additionally be provided to further direct flight which corrects, inhibits, and indicate other conditions.
In the hover flight mode, the geometric munition release area 44 is generally rectilinear in shape but otherwise operates as described above to indicate that immediate release is available (
It should be understood that like reference numerals identify corresponding or similar elements throughout the several drawings. It should also be understood that although a particular component arrangement is disclosed in the illustrated embodiment, other arrangements will benefit herefrom.
Although particular step sequences are shown, described, and claimed, it should be understood that steps may be performed in any order, separated or combined unless otherwise indicated and will still benefit from the present invention.
The foregoing description is exemplary rather than defined by the limitations within. Various non-limiting embodiments are disclosed herein, however, one of ordinary skill in the art would recognize that various modifications and variations in light of the above teachings will fall within the scope of the appended claims. It is therefore to be understood that within the scope of the appended claims, the invention may be practiced other than as specifically described. For that reason the appended claims should be studied to determine true scope and content.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US2008/077613 | 9/25/2008 | WO | 00 | 3/18/2011 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2010/036254 | 4/1/2010 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
3558865 | Berndt et al. | Jan 1971 | A |
3736411 | Berndt | May 1973 | A |
3793481 | Ripley et al. | Feb 1974 | A |
3880043 | Cox et al. | Apr 1975 | A |
3883091 | Schaefer | May 1975 | A |
4478581 | Goda | Oct 1984 | A |
4679751 | Peterson | Jul 1987 | A |
4715417 | Coloney | Dec 1987 | A |
5136951 | Herrlinger | Aug 1992 | A |
5200606 | Krasutsky et al. | Apr 1993 | A |
5224109 | Krasutsky et al. | Jun 1993 | A |
5285461 | Krasutsky et al. | Feb 1994 | A |
5331881 | Fowler et al. | Jul 1994 | A |
5351597 | Holmstrom et al. | Oct 1994 | A |
5369589 | Steiner | Nov 1994 | A |
5379966 | Simeone et al. | Jan 1995 | A |
5435503 | Johnson, Jr. et al. | Jul 1995 | A |
5465212 | Fowler et al. | Nov 1995 | A |
5586219 | Yufik | Dec 1996 | A |
5601255 | Romer et al. | Feb 1997 | A |
5838262 | Kershner et al. | Nov 1998 | A |
5855339 | Mead et al. | Jan 1999 | A |
5893085 | Phillips et al. | Apr 1999 | A |
5898483 | Flowers | Apr 1999 | A |
6024326 | Godfrey et al. | Feb 2000 | A |
6056237 | Woodland | May 2000 | A |
6061068 | Hoffman, II et al. | May 2000 | A |
6176167 | Sanderson | Jan 2001 | B1 |
6196496 | Moskovitz et al. | Mar 2001 | B1 |
6250197 | Sanderson | Jun 2001 | B1 |
6254394 | Draper et al. | Jul 2001 | B1 |
6286410 | Leibolt | Sep 2001 | B1 |
6349898 | Leonard et al. | Feb 2002 | B1 |
6453790 | Cesulka et al. | Sep 2002 | B1 |
6460445 | Young et al. | Oct 2002 | B1 |
6571155 | Carriker et al. | May 2003 | B2 |
6672534 | Harding et al. | Jan 2004 | B2 |
6687186 | Fields | Feb 2004 | B1 |
6718862 | Sanderson | Apr 2004 | B1 |
6779430 | Sanderson | Aug 2004 | B1 |
6789455 | Sanderson | Sep 2004 | B1 |
6802238 | Sanderson | Oct 2004 | B1 |
6802239 | Sanderson | Oct 2004 | B1 |
6885313 | Selk, II et al. | Apr 2005 | B2 |
6961070 | Madison et al. | Nov 2005 | B1 |
6997097 | Harding | Feb 2006 | B2 |
7047861 | Solomon | May 2006 | B2 |
7093802 | Pitzer et al. | Aug 2006 | B2 |
7121183 | Waid et al. | Oct 2006 | B2 |
7203577 | Gunn et al. | Apr 2007 | B2 |
7210392 | Greene et al. | May 2007 | B2 |
7236861 | Paradis et al. | Jun 2007 | B2 |
7262395 | Bilyk et al. | Aug 2007 | B2 |
Number | Date | Country |
---|---|---|
0282394 | Jan 1988 | EP |
Entry |
---|
Search Report and Written Opinion mailed on Nov. 6, 2009 for PCT/US 2008/077613. |
Northrop Grumman, MH-60R/MH60S, All-Glass Cockpit Smart MFD, Navigations Systems, pp. 1 & 2. |
Number | Date | Country | |
---|---|---|---|
20110169666 A1 | Jul 2011 | US |