The present invention relates to missile launchers, and more particularly to vertical missile launchers.
Modern warships use guided missiles as their principal offensive and defensive weapons. Since a naval engagement may be protracted, a warship must have many missiles available for immediate launch. This need has been addressed by multiple-missile launchers, in which plural launch cells (e.g., eight cells, etc.) are loaded with missiles that can be individually launched.
There is also a need to launch, from a single multiple-missile launcher, missiles of different mission type. This need has been met, for example, by the below-deck, vertical Mk41 and Mk57 missile launchers. These launchers accept canisterized missiles, wherein the missiles in the canister can be one of several types. The canisters are loaded into corresponding canister-holding chambers or cells in the missile launcher. Each canisterized missile has a standardized connector, which is connected within each cell, to a launch sequencer. The launch sequencer is an electronic assembly that identifies the missile within the canister by interrogating a code that is associated with the canister. The launch sequencer also responds to arming and firing signals from a higher level of control by generating a sequence of signals for the identified missile (e.g., firing signals, safe signals, etc.). These signals are transmitted via an umbilical cable to the canister and the missile within it to control launch.
A major road block to providing new munitions capability to naval fleets is the extremely high cost of launcher-related modifications. Specifically, integration of a new munition into an existing main battery launching system typically requires the design and qualification of a new canister for packaging, handling, storing, and transporting the munition. Furthermore, existing main battery host-launcher electronics and software must be appropriately modified to provide power and interfacing to each of the munition rounds in the newly developed canister. Additionally, integrating a new munition typically requires requalifying the gas management system of the launcher for the new munition.
It would therefore be beneficial to develop a way to reduce the cost for integrating new munitions in existing main-battery launchers.
The illustrative embodiment of the present invention is a single-cell, vertical launching system (hereinafter “adaptable launch system” or “ALS”) for new and existing munitions.
In some embodiments, the ALS is used as a standalone launcher. In some other embodiments, the ALS is used as a “guest” launcher in one or more cells of a multi-cell “host” launching system, such as the Mk41 or Mk57 VLS main-battery launchers. In both standalone and guest-launcher applications, the ALS can accommodate either a single munition or a “multi-pack” of smaller munitions in its single launch cell.
It is particularly in its capacity as a guest launcher that the ALS addresses the problems associated with the integration of new munitions into an existing main battery launching system. In this regard, the ALS is not analogous to a canistered round, such would be received in a cell of a Mk41 or Mk57 launcher. Rather, the ALS contains and acts with most of the functionality required for launch. The ALS itself receives one or more canistered munitions in its removable “munitions adapter.” Providing multiple versions of the “munitions adapter” enables the ALS to accommodate different types of munitions. The ALS advantageously uses existing, qualified canisters and munitions without the need for modification. This is done by reutilizing in the ALS, to the extent possible, mechanical and electrical hardware, software, and logistics developed from earlier applications. As a consequence, a one-time modification is required to existing main battery launchers to adapt to the presence of the ALS, establishing the “guest”/“host” launcher functionality. Integration/adaptation specifics pertaining to the munitions are handled within the ALS itself.
In summary, the following features of the ALS contribute to its utility, at least in terms of providing developmental and recurring costs savings:
The adaptable launch system (“ALS”) disclosed herein can be used as a standalone launcher or as a guest launcher in a main battery host system. Since the former application is the far more straightforward application, much of the disclosure below pertains to the integration of the ALS with an existing main-battery launcher.
As depicted in
The MK 41 VLS as MCL 102 is installed below deck, such that only deck and hatch assembly 108 at the top of the module is visible from the deck of a ship. The deck and hatch assembly protects ALS 112 (or missile canisters in a conventional MK 41 VLS) during storage and the hatches open to permit munitions launch. A plenum and uptake structure (not identified in
Electronic equipment 110 monitors and controls various components of MCL 102, distributes power signals originating from outside RMCL 100 to the one or more ALS 112 units, collects control and damage control signals from ALS 112 and transmits them to appropriate authorities, and assists in the launch of munitions from ALS 112 units.
The salient features of ALS 112 depicted in
Enclosure 114 serves as a housing for munitions adaptor 116 and launch control electronics 118. Munitions adapter 116 is specific to the munitions that it carries. Various embodiments of munition adapter 116 are used for missiles, active decoys, and unmanned aerial vehicles (“UAVs”), as described later in conjunction with
The munitions are launched from ALS 112 under the control of their own weapon control system (“WCS”), through an instantiation of launch control electronics 118 that is tailored to that specific munition type. Launch control electronics 118 supplies electrical power to the munitions and manages the launch sequence. In most embodiments, the electrical power distribution subassembly and at least some cabling, all of which are part of the “conceptual” ALS disclosed herein, are not included in ALS 112 proper. Rather, these elements are associated with the host launcher.
Gas and green water management are provided by ALS 112, thereby avoiding the need to modify the management systems of the host launcher. The host hatch system (e.g., deck and hatch assembly 108, etc.) might require modification, as a function of munitions type, to enable venting of exhaust gases under abnormal, inadvertent, or restrained firing events.
ALS 112 is loaded into MCL 102 (when the MCL is as a MK 41 VLS) as follows. ALS 112, with munitions adapter 116 and munitions launch control electronics 118 installed, is transported to dockside in a horizontal orientation. A “tilt fixture” is used to rotate ALS 112 to a vertical orientation. A vertical “strong back” is then attached to ALS 112 and a dockside crane is used to load the ALS(s) into the designated cell(s) of MCL 102 on board a ship.
Personnel then secure ALS 112 into the cell using “dog-downs,” in the same fashion as is done with conventional missile canisters. The umbilical and other required cables are then attached. As part of this initial installation, the MCL's standard hatch is replaced with a hatch that is suitable for the munitions within ALS 112, to the extent that the ALS is loaded with munitions that are not normally fired from a conventional version of the MCL.
ALS 112 is intended as a semi-permanent installation in a cell of MCL 102. Although ALS 112 can be removed or relocated if requirements change, it will typically remain in place and will be reloaded with fresh rounds of munitions as previous rounds are launched or otherwise removed. This is in contrast to conventionally used canisters, which are removed from a launcher such as the MK 41 VLS after the munition formerly stored therein is launched and then replaced with a fresh missile-bearing canister. Again, the ALS is not analogous to a canistered munition.
Referring now to
Shell 220 meets the physical requirements (e.g., size, shape, etc.) of a Mk41 canister. Shell 220 is formed from a composite material that meets appropriate standards (e.g., MIL-STD 2031, DDS 078-1, etc.). Shell 220 is sized to accommodate both the tactical length and strike length launcher applications. For some “stand alone” embodiments of ALS 112, some of launch control electronics 118 are located outside of shell 220 due to size constraints.
Sealing bulkhead 222 (shown in phantom in
ALS 112 does not incorporate a forward fly-through cover nor is it otherwise sealed for transport and storage (since it does not serve as a canister for munitions). In fact, ALS 112 does not contain munitions until they are loaded therein on-board the ship, as described later in this specification. As a consequence, top frame and module seal 232, which are disposed at upper end 228 of enclosure 114, cooperate with deck and hatch assembly 108 of MCL 102 to create a seal to prevent exhaust gases from entering the launcher space of the ship.
Electronics compartment 226 is not sealed. Access to the electronics compartment is provided by electronics access way 230. The electronics access way provides the following three functions when ALS 112 is installed in MCL 102.
Referring now to
Munitions-specific frame assembly 340 receives canistered munitions 344. In this particular embodiment, frame assembly 340 is a quad-pack frame assembly that receives four canistered munitions 344. In the pictured embodiment, the canistered munitions are NULKA active decoys. As previously mentioned, the configuration of munitions-specific frame assembly 340 varies with the particular munitions being used (see, e.g.,
Munitions extension assembly 342 enables ALS 112 to accommodate munitions of different sizes. Specifically, the length of the munitions extension assembly is varied, based on the length of the munitions type being used, to fill any excess length in munitions compartment 224. In most embodiments, the length of any particular munitions extension assembly 342 is not variable; rather, a plurality of different-length munitions extension assemblies are fabricated to accommodate differences in munitions length. The base of munitions extension assembly 342 seals against sealing bulkhead 222 to ensure that electronics compartment 226 is not exposed to exhaust gases that are generated during launch or restrained firing of munitions 344. Munitions extension assembly 342 will be described further in conjunction with
In this embodiment, base 456 receives the bottom of the munitions canisters (not depicted in
Munitions extension assembly 342 serves several purposes in addition to providing ALS 112 with a capability to accommodate munitions of different lengths (as a function of the length of extension member 664). In particular, vertical shock isolators 662 of the munitions extension assembly provides shock protection for the munitions within munition-specific frame assembly 340. Also, various electrical connectors are provided near interface plate 660 and base 666 for creating electrical connection, in conjunction with cables (not shown), between launch control electronics 118 and munitions 344 in frame assembly 340. A seal plate (not depicted) that is positioned between sealing bulkhead 222 and base 666 prevents leakage of exhaust gases and of any green water intrusion due to an open or leaking hatch.
In most embodiments, munitions used in conjunction with ALS 112 have canisters and will use the canister and all-up-round (“AUR”) configuration for transport, storage, and launch capabilities. This eliminates development and recurring costs for integrating canisters into ALS 112. The ALS accepts the AUR; it does not itself function as an AUR.
The following provides an example of a process for loading NULKA all-up-rounds 344A (see, e.g.,
Personnel will disconnect munitions adapter 116 from enclosure 114 and, using a dock-side crane, will partially extract the munitions adapter from ALS 112 that is in a cell of MCL 102. (The munitions adapter is extracted through top 228 (see
After loading is complete, the dock-side crane will lower munitions adapter 116 back into enclosure 114 (which is still in the MCL 102). Personnel reconnect the munitions adapter to enclosure 114 and also connect the munitions adapter to launch control electronics 118.
Returning to the discussion of
Munition specific electronics 348 are typically the same units as would be supplied for a specific munition in an existing launcher. For example, in the case of a NULKA instantiation of launch control electronics 118, munition specific electronics 348 are two MK 174 processor power supplies, as are used for NULKA rounds in the MK 53 DLS deck-mounted, mortar-type countermeasure system. Munition specific electronics 348 provide power, data, and ordnance activation control to the munitions and also perform limited launch control functions.
Launch control module 346 coordinates control/communications between the munition's weapon control system, munition specific electronics 348, and the host launcher (e.g., MK 41, etc.). Launch control module 346 is developed for use with a particular munitions type. It is then re-used for other types of munitions by making suitable software and hardware modifications. The modifications pertain to ALS 112, not the host launcher.
Host/Guest Communications. Communications between host launcher MCL 102 and ALS 112 are described below for the case of a MK 41 VLS as the host launcher and a NULKA instantiation of ALS.
A NULKA MK 24 Decoy Launching Processor communicates directly with launch control module 346, which controls the transfer of existing RS-422 (serial bus) messages between the MK 24 Decoy Launching Processor and processor power supplies 348. Launch control module 346 coordinates hatch operations and launch coordination activities with MCL 102.
The identification code of ALS 112 is communicated to launch sequencer 110 and launch control unit of MCL 102.
Launch Operations. When used as a guest launcher, ALS 112 continues to perform most tasks related to launching its munitions, but it will coordinate with the host—MCL 102—for functionality that is provided by the host. Such functions are those for which ALS 112 utilizes equipment provided by MCL 102 and that involve operational considerations that must be addressed at a higher, host-launcher level. Such functions include, without limitiation:
Inventory Control and Launch Process Initiation. ALS 112 provides an ID to MCL 102 through an umbilical cable. This ID informs the MCL that the particular cell is occupied by ALS 112; it does not specify the munitions type that is contained in the ALS. As a consequence, when MCL 102 is apprised of the presence of ALS 112 in one or more of its cells, the MCL will be required at appropriate times to query ALS 112 for munitions-specific information (e.g., munitions warfare type—AAW, ASW, SUW, others, launch rate deltas, etc.). In some embodiments, this is accomplished via messages between ALS 112 and MCL 102. These messages and related control functionality provides flexibility to handle all future munitions for use with ALS 112, thereby reducing related costs for integrating such munitions.
To initiate the launch process, the weapon control system for the munitions in ALS 112 coordinates selection of the desired cell and (in the case of multiple munitions within the cell) the particular munition within the cell. Although this process is driven by the weapons control system, MCL 102 will typically have other ongoing launch activities that might prevent use of the preferred munitions selection due to commitment of power supplies, etc., or issues associated with disabled equipment, ablative issues, and the like.
Launch Sequencing. Message communications between ALS 112 and MCL 102 is between launch control electronics 118 in the ALS and the launch control unit in MCL 102. Some aspects of the launch sequence will be variable as a function of munitions type. In one category of munitions, the sequence involves the munition's weapon control system, launch control electronics 118, and the munition (for missile preparation and final ignition and egress), but with no coordination with MCL 102 until the end of a subsequence. In another category, it involves processes internal to MCL 102, but with no coordination with ALS 112 until the end of a subsequence. Coordination between MCL 102 and ALS 112 is required only at the completion of each subsequence.
In some embodiments, there are only five such coordination points between ALS 112 and MCL 102. As a consequence, the launch-sequence integration of the ALS with MCL 102 can be a one-time task for all subsequent munitions. The coordination points for any munition to be launched by ALS 112 in a vertical launch system will be:
Some of the munition-specific processes, for example restraint release, are presently done in the host launcher (e.g., Mk41 VLS). But this varies for each munition, which adds to integration costs. By locating these munition-specific functions in ALS 112, the features will become part of the munition-specific instantiation of ALS 112, and will require no further modifications to the host (i.e., MCL 102) following the first instantiation.
It is to be understood that the disclosure teaches just one example of the illustrative embodiment and that many variations of the invention can easily be devised by those skilled in the art after reading this disclosure and that the scope of the present invention is to be determined by the following claims.
This case claims priority of U.S. Provisional Patent Application Ser. No. 60/989,396 filed Nov. 20, 2007 and which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3089389 | Andrews et al. | May 1963 | A |
3106132 | Biermann et al. | Oct 1963 | A |
3110464 | Baratoff et al. | Nov 1963 | A |
3468213 | Hersh et al. | Sep 1969 | A |
4586421 | Hickey et al. | May 1986 | A |
4646617 | Robinson | Mar 1987 | A |
4665792 | Gassler et al. | May 1987 | A |
5327809 | Matteson et al. | Jul 1994 | A |
5742609 | Kondrak et al. | Apr 1998 | A |
6125734 | Yagla | Oct 2000 | A |
6142055 | Borgwarth et al. | Nov 2000 | A |
6230604 | Larson et al. | May 2001 | B1 |
6283005 | Yagla et al. | Sep 2001 | B1 |
6610971 | Crabtree | Aug 2003 | B1 |
20020189432 | Facciano et al. | Dec 2002 | A1 |
20050108917 | Kunstmann | May 2005 | A1 |
20090126556 | Skurdal et al. | May 2009 | A1 |
Entry |
---|
“BAE Systems MK25 Quad Pack”, “http://web.archive.org/web/20071018171337/http://baesystenns.com/ ProductsServices/mk25—quad—pack.html XP002545342”, Oct. 18, 2007, Publisher: BAE Systems. |
Moorhead, Seth B., “The Latest in Ship Weapon Launchers—The Vertical Launching System”, “Naval Engineers Journal XP002048251”, Apr. 1981, pp. 90-96, vol. 93, No. 2, Published in: US. |
Beaufume, Cedric, “PCT Application No. PCT/US2008/084115 International Search Report Oct. 1, 2009”, , Publisher: EPO, Published in: EP. |
Menier, Renan, “PCT Application No. PCT/US2011/047045 International Search Report Nov. 7, 2011”, , Publisher: PCT, Published in: PCT. |
Albuquerque, Savio, “AU Application No. 2008351349 Office Action Feb. 11, 2011”, , Publisher: IPA, Published in: AU. |
Giffo-Schmitt, Beate, “PCT Application No. PCT/US2008/084115 International Preliminary Report on Patentability Jul. 3, 2010”, , Publisher: PCT, Published in: PCT. |
Evans, David J., “GB Application No. 1009887.9 Office Action Mar. 26, 2012”, , Publisher: UK IPO, Published in: GB. |
Number | Date | Country | |
---|---|---|---|
20090126556 A1 | May 2009 | US |
Number | Date | Country | |
---|---|---|---|
60989396 | Nov 2007 | US |