Military personnel may be faced with numerous types of threats from hostile parties. Rocket-propelled grenades (RPGs) are often a weapon of choice for hostile parties. RPGs typically consist of a rocket with a warhead attached and may be launched from a handheld launcher. RPGs may be effective against armored vehicles, helicopters, and structures. The relatively low cost, portability, and lethality of the weapon makes RPGs a formidable threat to friendly forces.
One method for guarding against these types of threats is to attempt to destroy an incoming RPG with an explosive force and/or fragments from a defensive rocket or weapon. These types of defensive weapons are designed to intercept the incoming RPG and destroy the rocket via impact, explosion, or fragments or other debris from exploding the defensive weapon in close proximity to the RPG. Similarly, existing solutions include utilizing fixed barriers or rapidly deployable barriers to fixed structures or vehicles in an effort to contact and prematurely detonate the incoming RPG prior to contact with the intended target. One drawback to these types of defensive weapons and fixed barrier solutions is that the explosions and resulting shrapnel from these weapons or from the exploding RPG have the potential to damage friendly structures, vehicles, or to injure friendly personnel or innocent bystanders.
Another existing solution to an RPG attack includes utilizing a projectile or other countermeasure to dud the warhead by crushing the nose cone of the incoming RPG to short out the fuse coupled to the warhead. This method may be effective against dated RPGs that rely on the nose cone to supply electrical current to the fuse of the weapon. However, more recent RPGs utilize insulated electrical wires that prevent this type of electrical short when the nose cone is crushed or damaged.
Other solutions attempt to catch or detonate an incoming RPG utilizing a structure that is attached or otherwise fixed to a defensive projectile. For example, a rigid or semi-rigid barrier may be deployed from a forward portion of a countermeasure rocket to engage an incoming RPG. However, because of the nature of these barriers and because of the attachment location on the forward portion of the rocket, these countermeasure systems may be destabilizing to the rocket at deployment. To overcome the stability issues the size, weight, and corresponding cost and complexity of these systems may be significant.
Similarly, other countermeasure rockets may tow a barrier behind the intercepting rocket in order to engage the incoming RPG. However, towing barriers behind a rocket creates an inordinate amount of drag that slows the rocket, potentially preventing interception of the incoming RPG at a safe distance from the aircraft, vehicle, or structure being protected. This towed configuration additionally requires a larger rocket motor, which may increase the size, cost, and complexity of the countermeasures system. Additionally, there may be a potential for the exhaust gases from the countermeasure rocket to burn through a portion of the towed barrier, reducing the effectiveness of the system.
It is with respect to these considerations and others that the disclosure made herein is presented.
It should be appreciated that this Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to be used to limit the scope of the claimed subject matter.
Systems and methods described herein provide for the effective protection of a vehicle or other platform from an incoming RPG or similar threat. Utilizing the concepts described herein, an incoming threat can be detected and an interceptor vehicle launched to intercept the incoming threat at a safe distance from the vehicle or platform being protected. The interceptor vehicle deploys a detachable net or similarly expanding countermeasure to intercept and capture the incoming RPG or threat prior to impact with the vehicle.
According to one aspect of the disclosure provided herein, a countermeasure system may include an interceptor vehicle having a propulsion system and a countermeasure compartment. The interceptor vehicle may be launched from a countermeasure launcher on or near the vehicle or other asset being protected. The countermeasure system may further include a countermeasure configured to be stowed within and launched from the countermeasure compartment of the interceptor vehicle. The countermeasure may include a flexible receiving body that expands when deployed for capturing the incoming threat.
According to another aspect, a method for neutralizing an incoming threat is provided. The method may include detecting the incoming threat approaching the vehicle or other asset to be protected and launching an interceptor vehicle to intercept the incoming threat. A countermeasure may be deployed from the interceptor vehicle. A flexible receiving body of the countermeasure may expand in the path of the incoming threat to capture and neutralize the threat.
According to another aspect, a countermeasure system may include a countermeasure launcher, an interceptor vehicle, and a countermeasure. The countermeasure may include a flexible receiving body with a number of deployment mechanisms attached around the perimeter of the flexible receiving body. The interceptor vehicle may include a propulsion system with an exhaust nozzle, and a countermeasure compartment around the exhaust nozzle for stowing the countermeasure. A number of detachable panels may be positioned around the countermeasure compartment to encompass the countermeasure within prior to deployment of the countermeasure. An electronics system of the interceptor vehicle may be configured to release the detachable panels to deploy the countermeasure. The countermeasure system may further include a threat detection and launch system in communication with the electronics system of the interceptor vehicle. The threat detection and launch system may be operative to detect the incoming threat, launch the interceptor vehicle, guide the interceptor vehicle to the incoming threat, and provide instructions for deployment of the countermeasure.
The features, functions, and advantages that have been discussed can be achieved independently in various embodiments of the present disclosure or may be combined in yet other embodiments, further details of which can be seen with reference to the following description and drawings.
The present disclosure is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
The following detailed description is directed to systems and methods for detecting and neutralizing an incoming threat such as a rocket-propelled grenade (RPG). As discussed briefly above, RPGs typically consist of a rocket with a warhead attached and may be launched from a handheld launcher. Due to the low cost, portability, and lethality of the weapon, RPGs are a threat to friendly forces in structures and vehicles. Existing solutions may detonate the incoming RPGs, creating further risk of collateral damage, or require relatively large and complex intercept rockets due to the drag created by the attached countermeasure.
However, utilizing the concepts and technologies described herein, helicopters, ground-based vehicles, structures, and any other friendly asset may be protected with a system that detects an incoming RPG and launches an interceptor vehicle on a trajectory or flight path that passes in close proximity to the incoming threat. At a designed location with respect to the incoming RPG, the interceptor vehicle deploys a countermeasure from the interceptor vehicle. The interceptor vehicle continues past the incoming RPG, while the deployed countermeasure expands outward into the path of the RPG. The RPG flies into the deployed countermeasure. The opposing momentums of the RPG and the countermeasure, as well as the additional drag of the countermeasure encompassing the RPG, causes the incoming RPG to miss the target and typically fall harmlessly to the ground short of the intended target or to veer off of the intended flight path.
In the following detailed description, references are made to the accompanying drawings that form a part hereof, and which are shown by way of illustration, specific embodiments, or examples. Referring now to the drawings, in which like numerals represent like elements through the several figures, a countermeasure system and method will be described.
Additionally, although the various figures and corresponding disclosure describe the countermeasure system as being installed on a vehicle 100, such as the helicopter depicted in
As shown in
According to one embodiment, the RPG 102 may partially penetrate a mesh material of the countermeasure 110, but without traversing completely through the countermeasure 110, effectively slowing the RPG 102 or altering the course of the RPG 102, preventing the RPG 102 from reaching the vehicle 100 without detonating its warhead. According to another embodiment, the RPG 102 may be detonated by the impact with the countermeasure 110, but at a sufficient distance from the vehicle 100 so as to prevent damage to the vehicle 100 and associated personnel. Throughout this disclosure, the countermeasure system is described as a “projectile-deployed countermeasure system.” It should be understood that this label is used to convey that the countermeasure 110 described herein is stowed within, and deployed from, a projectile (interceptor vehicle 108) launched from a launcher.
Turning to
The countermeasure system 200 also includes a threat detection and launch control system 202 that is used to detect an incoming threat 102, to select the appropriate countermeasure launcher 104 for neutralizing the threat, and to launch one or more interceptor vehicle 108. According to one embodiment, the threat detection and launch control system 202 includes a detection system 204 and a controller 206.
The detection system 204 may include any radar system, lidar system, optical or acoustic-based sensors, electro-optical and/or infrared systems, and/or any technology suitable for detecting the presence of an object approaching the vehicle 100. According to one embodiment, the detection system 204 includes a millimeter wave and/or microwave wide field of view (FOV) radar system. According to one embodiment, the radar system for use with aircraft such as the helicopter or vehicle 100 may have a 180-degree FOV capability. According to another embodiment, the radar system for use with ground-based vehicles or structures may have a 120-degree FOV capability. The radar system may utilize any number of antennas located at any suitable location on the vehicle 100 or other structure. According to various embodiments, the detection system 204 incorporates existing radar and threat detection systems currently employed in existing helicopters or other vehicles 100.
It should also be appreciated that the threat detection and launch control system 202 may include a manual launch mechanism such as a button or switch (not shown) that enables an operator to manually launch one or more interceptor vehicles 108 prior to or without threat detection from the detection system 204. According to this embodiment, should the interceptor vehicle 108 be guided, the controller 206 may guide the interceptor vehicle 108 to the incoming RPG 102 when acquired by radar or may be manually guided to the threat by the operator. With an unguided interceptor vehicle 108, the operator may manually deploy the countermeasure 110 when desired via a corresponding button or switch (not shown) that activates a deployment signal sent to the interceptor vehicle 108.
The controller 206 may be any computer hardware and/or software containing computer executed instructions for receiving threat detection data from the detection system 204 and, in response, selecting the appropriate countermeasure launchers 104 and corresponding interceptor vehicles 108 for neutralizing the incoming threat 102. The controller 206 is operative to determine and provide a firing solution to the electronics systems 210A-210N (collectively referred to as 210) of the appropriate interceptor vehicles 108. The firing solution may include guidance data for directing the interceptor vehicle 108 to the target and countermeasure deployment information that provides instructions as to when the countermeasure 110 is to be deployed or released from the interceptor vehicle 108.
It should be appreciated that the concepts described herein may not only be used to launch a protective interceptor vehicle 108 from the vehicle 100 that is being targeted by the incoming RPG 102, but also to launch an interceptor vehicle 108 from a vehicle 100 to intercept an RPG 102 that is targeting another vehicle 100, structure, or other target. In these implementations, the guidance data from the firing solution may include instructions for the interceptor vehicle 108 to perform a turn or heading change to provide proper alignment of the countermeasure 110 with the RPG 102 when deployed from the interceptor vehicle 108.
According to one embodiment, the countermeasure deployment information may instruct the electronics systems 210 of the corresponding interceptor vehicle 108 to deploy the countermeasure 110 after a determined number of rotations of the interceptor vehicle 108 after launch. According to an alternative embodiment, the instructions may trigger deployment of the countermeasure 110 after a determined time lapse after launch.
According to yet another alternative embodiment, the instructions may be provided by the controller or may be pre-stored on computer-readable storage media onboard the interceptor and may instruct the electronics systems 210 to deploy the countermeasure 110 within a determined distance from the protected asset or a determined proximity to the RPG 102. The determined distance may correspond to a distance from the vehicle 100 or other protected asset in which the detonation of an incoming RPG 102 or other threat would not cause any damage, taking into account any applicable variables such as flight characteristics of the incoming RPG 102, interceptor vehicle 108, and vehicle 100; deployment characteristics of the interceptor vehicle 108 and corresponding countermeasure 110; as well as typical explosive characteristics and damage radius predictions associated with a detonation of the incoming RPG.
The proximity of the interceptor vehicle 108 to the incoming RPG 102 may be detected by an onboard proximity sensor on the interceptor vehicle 108 or other conventional radar or suitable detection system. Alternatively, the proximity of the interceptor vehicle 108 to the RPG 102 may be determined from the detection system 204 associated with the vehicle 100 and transmitted to the interceptor vehicle 108 before or after launch of the interceptor vehicle 108. According to various embodiments, the threat detection and launch control system 202 may instruct the electronics systems 210 of the interceptor vehicle 108 to deploy the countermeasure 110 at a time or distance determined according to the speed of the incoming RPG 102. The countermeasure 110 deployment may be triggered according to the number of revolutions of the interceptor vehicle 108 or according to a time delay based on the speed of the incoming RPG 102 and corresponding distance from the vehicle 100.
As mentioned above, each countermeasure launcher 104 may be loaded with any number of interceptor vehicles 108A-108N. According to one embodiment, the interceptor vehicles 108A-108N may include corresponding countermeasures 110A-110N, propulsion systems 208A-208N (collectively referred to as 208), and electronic systems 210A-210N. Turning now to
The propulsion system 208 may include components for propelling the interceptor vehicle 108 from the countermeasure launcher 104 to the RPG 102. As seen in
According to various embodiments, the countermeasure 110 may be stowed in a countermeasure compartment 311 at a rear portion 309 of the interceptor vehicle 108 surrounding the exhaust nozzle 304. The countermeasure compartment 311 may be bordered on the outside by one or more detachable panels 307 and on the inside by the exhaust nozzle 304 or associated components. The countermeasure 110 may be wrapped, folded, or otherwise configured to stow within the countermeasure compartment 311 under one or more detachable panels 307 surrounding the rear portion 309 of the interceptor vehicle 108. Although the countermeasure compartment 311 is shown and described as being positioned at the rear portion 309 of the interceptor vehicle, it should be appreciated that the countermeasure compartment 311 may be positioned at a middle or forward portion of the interceptor vehicle without departing from the scope of this disclosure.
When the electronics systems 210 trigger the deployment of the countermeasure 110, the detachable panels 307 are ejected via electro-mechanical, explosive, or other means. With the detachable panels ejected, the countermeasure 110 is free to deploy as described in greater detail below. It should be appreciated that the precise dimensions and other parameters of the interceptor vehicle 108 may be dependent upon the characteristics of the desired countermeasure 110 and the speed and distance at which the interceptor vehicle 108 is to deliver and deploy the countermeasure 110, among other design criteria.
Alternatively, a rear portion of the stabilizing fins 402 may extend rearward over the stowed countermeasure 110, but with the rear portion of the stabilizing fins remaining unattached to the interceptor vehicle 108 so as to prevent interference with the countermeasure 110 deployment. It should be appreciated that the precise shape, dimensions, number, and placement of the stabilizing fins 402 may vary according to the particular application and are not limited to those shown in
While the shape of the countermeasure 110 as viewed in the deployed configuration from the top is shown in
As seen in
As stated above, there are numerous types of deployment mechanisms 306 contemplated by this disclosure. Various example deployment mechanisms 306A-306D are shown in
The deployment mechanism 306A may include a weight or weighted element that is attached either directly or via a tether to the flexible receiving body 502. With this implementation, any number of deployment mechanisms 306A may be attached to the corners or periphery of the flexible receiving body 502. These weights may be shaped or contoured to facilitate stowage around the exhaust nozzle 304 of the interceptor vehicle 108. The precise size and weight of the deployment mechanisms 306A (as well as all other deployment mechanisms 306) may be minimized to values that allow for rapid expansion after deployment of the countermeasure 110, while minimizing the stowage space and corresponding payload weight of the interceptor vehicle 108.
The deployment mechanism 306B may be similar to deployment mechanism 306A. However, the deployment mechanism 306B illustrates how attachment to multiple corners or locations on the periphery of the flexible receiving body 502 is possible. Additionally, it is contemplated that the deployment mechanism 306B may include the detachment panel 307. In this embodiment, the detachment panels 307 on the interceptor vehicle 108 may be tethered or otherwise attached to locations around the perimeter of the flexible receiving body 502 of the countermeasure 110. In this manner, when the detachment panels 307 are ejected, wind resistance and/or the weight of the panels coupled with centrifugal force causes the detachment panels 307 to move outward, expanding the flexible receiving body 502 into the fully deployed configuration.
The deployment mechanism 306C utilizes multiple weights of any number, shape, and size attached directly to multiple locations around the perimeter of the flexible receiving body 502. In this embodiment, numerous smaller weights as compared to those discussed above with respect to deployment mechanism 306A are contemplated and are coupled directly to the edge of the countermeasure 110.
The deployment mechanism 306D utilizes small parachutes or other high drag devices attached at multiple locations around the perimeter of the flexible receiving body 502. These small parachutes inflate when exposed to the ambient airflow and operate to pull the countermeasure 110 into the deployed configuration. This particular deployment mechanism 306D may be particular useful if used with the interceptor vehicle 108 having stabilizing fins 402 rather than rotational stabilizing flight. It should be appreciated that any of these and other deployment mechanisms 306A-306D may be used alone or in combination with one another depending on the particular implementation. A benefit of using drag enhancements such as the parachutes described above is that they continue to act on the RPG 102 until its forward motion stops. After capturing the RPG 102, the small parachutes or other drag enhancements continue to assist in slowing the RPG 102 until impact well short of the intended target.
Turning to
From operation 602, the routine 600 continues to operation 604, where the interceptor vehicle 108 is loaded into the countermeasure launcher 104. At operation 606, an RPG 102 or other incoming threat is detected. The detection may occur with the detection system 204, such as a radar system, or may be a visual detection from an occupant of the vehicle 100. At operation 706, the controller 206 determines the applicable approach zone of the incoming threat 102.
The routine 600 continues from operation 606 to operation 608, where a firing solution is calculated by the controller 206. The firing solution may be calculated using any amount and type of data corresponding to the incoming RPG 102. Examples include but are not limited to the size, type, position, velocity, vector, acceleration, time to impact, or any other applicable or desirable data associated with the RPG 102 or other incoming threat. The firing solution is used to launch the interceptor vehicle 108 at operation 610. At operation 612, the electronics systems 210, either autonomously after receiving the firing solution from the controller 206 pre-launch or upon receiving real-time instructions from the controller 206 during threat intercept, triggers the ejection of the detachable panels 307 and subsequent deployment of the countermeasure 110 at the determined time and location. The deployment of the countermeasure 110 results in the capture of the RPG 102 and the routine 600 ends.
For illustrative purposes only, an example scenario will now be described to show how a countermeasure system 200 described herein might be employed to detect and neutralize an incoming threat as illustrated in
According to this example, as shown in
The subject matter described above is provided by way of illustration only and should not be construed as limiting. Various modifications and changes may be made to the subject matter described herein without following the example embodiments and applications illustrated and described, and without departing from the true spirit and scope of the present invention, which is set forth in the following claims.
This application claims the benefit of U.S. Provisional Application No. 61/671,297 filed Jul. 13, 2012 entitled “Projectile-Deployed Countermeasure System,” which is expressly incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
2251918 | Dawson | Aug 1941 | A |
3568191 | Hiester et al. | Mar 1971 | A |
4231311 | Longerich | Nov 1980 | A |
4492166 | Purcell | Jan 1985 | A |
4912869 | Govett | Apr 1990 | A |
5750918 | Mangolds et al. | May 1998 | A |
5898125 | Mangolds et al. | Apr 1999 | A |
5988036 | Mangolds et al. | Nov 1999 | A |
6430108 | Pignol et al. | Aug 2002 | B1 |
6626077 | Gilbert | Sep 2003 | B1 |
6957602 | Koenig et al. | Oct 2005 | B1 |
7066427 | Chang | Jun 2006 | B2 |
7190304 | Carlson | Mar 2007 | B1 |
7202809 | Schade et al. | Apr 2007 | B1 |
7328644 | Vickroy | Feb 2008 | B2 |
7398617 | Mattox | Jul 2008 | B2 |
7412916 | Lloyd | Aug 2008 | B2 |
7786417 | Sells, II | Aug 2010 | B2 |
8122810 | Glasson | Feb 2012 | B2 |
8205537 | Dupont | Jun 2012 | B1 |
8399816 | Glasson | Mar 2013 | B2 |
20020134365 | Gray | Sep 2002 | A1 |
20060169832 | Glasson | Aug 2006 | A1 |
20070169616 | Vickroy | Jul 2007 | A1 |
20070261542 | Chang et al. | Nov 2007 | A1 |
20100307328 | Hoadley et al. | Dec 2010 | A1 |
20120210851 | Glasson | Aug 2012 | A1 |
20140033907 | Martinez et al. | Feb 2014 | A1 |
Number | Date | Country |
---|---|---|
2172853 | Mar 1985 | GB |
Entry |
---|
GB Combined Search and Examination Report dated May 18, 2012 in GB Application No. GB1201328.0. |
Non-Final Office Action dated Jan. 10, 2013 in U.S. Appl. No. 13/016,608. |
Shenzhen Xinyi Technology Co., Ltd., “Air-charged Catching Net,” [http://www.ecplaza.net/trade-leads-seller/aircharged-catching-net--6447638.html] Accessed Jun. 20, 2012. |
CoolestGadgets, “Shooting Net for Catching Thieves,” [http://www.coolest-gadgets.com/20080402/shooting-net-for-catching-thieves/] Accessed Jun. 20, 2012. |
Instructables, “Build a Net Gun,” [http://www.instructables.com/id/Build-A-Net-Gun/] Accessed Jun. 20, 2012. |
Tactical Life, “Net Gun,” [http://www.tactical-life.com/online/special-weapons/net-gun/] Accessed Jun. 20, 2012. |
Number | Date | Country | |
---|---|---|---|
20140216290 A1 | Aug 2014 | US |
Number | Date | Country | |
---|---|---|---|
61671297 | Jul 2012 | US |