The field relates generally to guided projectiles and, more specifically, to countermeasure systems and methods for use with guided projectiles.
At least some known air-defense systems protect a target, such as a vehicle, a shelter, or a building, by detecting and then intercepting an attacking projectile with a defensive projectile. In such a scenario, the attacking projectile is launched towards an intended target and the defensive projectile is launched towards the attacking projectile. At least some known attacking projectiles may be equipped with a countermeasure system that enables it to attempt to evade the defensive projectile and improve its ability to reach its intended target. Such countermeasure systems include electronic jamming systems, low observability and/or radar avoidance materials, and programming that causes the attacking projectile to perform evasive maneuvers. Such countermeasure systems are typically state-of-the-art, complex, and expensive to implement.
This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the disclosure, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.
One aspect is a guided projectile including a projectile housing, a first sensor, and an air brake detachably coupled to the projectile housing. The air brake is deployable from a flight configuration to a braking configuration. A processor is configured to monitor, based on data received from the first sensor configured to detect approach of an intercepting object, a proximity of the at least one intercepting object relative to the guided projectile, wherein the guided projectile is configured to advance towards a target location on a first target trajectory. The processor is also configured to deploy the air brake to cause the guided projectile to veer from the first target trajectory to establish a separation distance from the at least one intercepting object to evade the at least one intercepting object, and detach the air brake from the guided projectile to enable the guided projectile to advance on a second target trajectory that is offset from the first target trajectory, wherein the first target trajectory and the second target trajectory have the same target location.
Another aspect is a countermeasure system for use with a guided projectile. The countermeasure system includes a first sensor and an air brake detachably coupled to the guided projectile, wherein the air brake is deployable from a flight configuration to a braking configuration. A processor is configured to monitor, based on data received from the first sensor configured to detect approach of an intercepting object, a proximity of the at least one intercepting object relative to the guided projectile, wherein the guided projectile is configured to advance towards a target location on a first target trajectory. The processor is also configured to deploy the air brake to cause the guided projectile to veer from the first target trajectory to establish a separation distance from the at least one intercepting object to evade the at least one intercepting object, and detach the air brake from the guided projectile to enable the guided projectile to advance on a second target trajectory that is offset from the first target trajectory, wherein the first target trajectory and the second target trajectory have the same target location.
Yet another aspect is a method of evading at least one intercepting object. The method includes monitoring, based on data received from a first sensor onboard a guided projectile configured to detect approach of an intercepting object, a proximity of the at least one intercepting object relative to the guided projectile, wherein the guided projectile is configured to advance towards a target location on a first target trajectory. The method also includes deploying an air brake onboard the guided projectile to cause the guided projectile to veer from the first target trajectory to establish a separation distance from the at least one intercepting object to evade the at least one intercepting object, and detaching the air brake from the guided projectile to enable the guided projectile to advance on a second target trajectory that is offset from the first target trajectory. The first target trajectory and the second target trajectory have the same target location.
Various refinements exist of the features noted in relation to the above-mentioned aspects of the present disclosure. Further features may also be incorporated in the above-mentioned aspects of the present disclosure as well. These refinements and additional features may exist individually or in any combination. For instance, various features discussed below in relation to any of the illustrated embodiments of the present disclosure may be incorporated into any of the above-described aspects of the present disclosure, alone or in any combination.
Corresponding reference characters indicate corresponding parts throughout the drawings.
Examples described include countermeasure systems and methods for use with guided projectiles. Example systems and methods include a sensor onboard the guided projectile that is configured to monitor the proximity of incoming an air-defense projectile, and an air brake that is detachably coupled to the guided projectile. When the guided projectile is in flight, the air brake is deployable from a flight configuration to a braking configuration, which causes the guided projectile to rapidly decelerate and lose altitude. This evasive maneuver creates a marked change in the guided projectile's trajectory to avoid the air-defense projectile's intercept trajectory. The air-defense projectile has limited maneuvering capabilities such that, if timed correctly, deployment of the air brake prevents the air-defense projectile from compensating for the rapid deceleration and altitude loss of the guided projectile. Once the guided projectile has passed the lethal kill radius of the air-defense projectile, the air brake may be detached from the guided projectile to cause it to re-accelerate and re-maneuver towards its intended target. Accordingly, the systems and methods described herein provide effective means for countering air-defense systems and increasing the likelihood of a payload reaching its intended target.
As used herein, an element or step recited in the singular and preceded with the word “a” or “an” should be understood as not excluding plural elements or steps, unless such exclusion is explicitly recited. Furthermore, references to “example”, “example implementation” or “one implementation” of the present disclosure are not intended to be interpreted as excluding the existence of additional implementations that also incorporate the recited features.
As will be described in more detail below, operation of guided projectile 100 may be controlled by a controller including a memory 114 and a processor 116, including hardware and software, coupled to memory 114 for executing programmed instructions. Processor 116 may include one or more processing units (e.g., in a multi-core configuration) and/or include a cryptographic accelerator (not shown). Guided projectile 100 is programmable to perform one or more operations described herein by programming memory 114 and/or processor 116. For example, processor 116 may be programmed by encoding an operation as executable instructions and providing the executable instructions in memory 114.
Processor 116 may include, but is not limited to, a general purpose central processing unit (CPU), a microcontroller, a microprocessor, a reduced instruction set computer (RISC) processor, an open media application platform (OMAP), an application specific integrated circuit (ASIC), a programmable logic circuit (PLC), and/or any other circuit or processor capable of executing the functions described herein. The methods described herein may be encoded as executable instructions embodied in a computer-readable medium including, without limitation, a storage device and/or a memory device. Such instructions, when executed by processor 116, cause processor 116 to perform at least a portion of the functions described herein. The above examples are for example purposes only, and thus are not intended to limit in any way the definition and/or meaning of the term processor.
Memory 114 is one or more devices that enable information such as executable instructions and/or other data to be stored and retrieved. Memory 114 may include one or more computer-readable media, such as, without limitation, dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), static random access memory (SRAM), a solid state disk, and/or a hard disk. Memory 114 may be configured to store, without limitation, executable instructions, operating systems, applications, resources, installation scripts and/or any other type of data suitable for use with the methods and systems described herein.
Instructions for operating systems and applications are located in a functional form on non-transitory memory 114 for execution by processor 116 to perform one or more of the processes described herein. These instructions in the different implementations may be embodied on different physical or tangible computer-readable media, such as memory 114 or another memory, such as a computer-readable media (not shown), which may include, without limitation, a flash drive and/or thumb drive. Further, instructions may be located in a functional form on non-transitory computer-readable media, which may include, without limitation, smart-media (SM) memory, compact flash (CF) memory, secure digital (SD) memory, memory stick (MS) memory, multimedia card (MMC) memory, embedded-multimedia card (e-MMC), and micro-drive memory. The computer-readable media may be selectively insertable and/or removable to permit access and/or execution by processor 116. In an alternative implementation, the computer-readable media is not removable.
As illustrated in progression view (1), air fins 122 are positioned against projectile housing 102 when in the flight configuration. Air fins 122 may be retained against projectile housing 102 to reduce drag on guided projectile 100. Air fins 122 are retained with any release mechanism that enables guided projectile 100 to function as described herein. In the example implementation, the release mechanism is a retention band 126 wrapped circumferentially around each air fin 122 and projectile housing 102. As will be described in more detail below, retention band 126 may be severed upon detection of an approaching intercepting object. Severance may be made with a pyrotechnic cutting charge embedded within retention band 126, for example, whose ignition is controlled by processor 116.
Severing retention band 126, or releasing air fins 122 by other means, enables air fins 122 to be deployed to the braking configuration. For example, as illustrated in progression view (2), air fins 122 are rotatable relative to base plate 120 when deployed from the flight configuration. In one implementation, deployment of air fins 122 is initiated with a spring 128 defined at a joint between base plate 120 and each air fin 122. Alternatively, the deployment may be initiated as a result of wind resistance impingement against air fins 122 while guided projectile 100 is in flight.
As illustrated in progression view (3), air fins 122 are fully deployed. When fully deployed, air fins 122 are designed to generate air resistance against guided projectile 100 to cause its rapid deceleration and a loss in altitude. Accordingly, air fins 122 are shaped, and have any orientation relative to guided projectile 100, that enables guided projectile 100 to function as described herein. For example, air fins 122 are sized based on the projectile's mass to create drag capable of generating a large trajectory offset of the incoming projectile to the intercepting projectile lethality zone. Air fins 122 are shaped to maximize drag while providing sufficient structural integrity to survive the opening shock of deployment. In addition, air fins 122 may be oriented at least one of orthogonally or perpendicularly relative to a longitudinal axis 130 (shown in
As illustrated in progression view (4), and as discussed above, air brake 118 is detachably coupled to projectile housing 102. For example, base plate 120 may be coupled to guided projectile 100 with a detachment mechanism 124, such as a pyrotechnic bolt. As will be described in more detail below, activation of detachment mechanism 124 to detach air brake 118, including base plate 120 and air fins 122, from guided projectile 100 is controlled based on a proximity of an intercepting object relative to guided projectile 100.
As shown in the second illustration 144, the processor 116 monitors the first sensor 110 configured for detecting when the intercepting object 132 is within a predetermined proximity, in response to which the processor 116 initiates detachment mechanism to deploy the air brake 118 to cause the guided projectile 100 to rapidly decelerate and veer from the first target trajectory 142 towards an altered trajectory beneath intercepting object 132. As shown in the third illustration 146, intercepting object 132 has a lethal kill radius R. Lethal kill radius R is a distance from intercepting object 132 in which, when a payload onboard intercepting object 132 is detonated, guided projectile 100 will be disabled and/or unable to continue towards target location 138. In the example implementation, upon detecting that the intercepting object 132 is within a predetermined proximity, the air brake 118 is deployed to cause guided projectile 100 to veer from first target trajectory 142 towards an altered trajectory, and the air brake 118 remains deployed for a duration to establish a separation distance from the at least one intercepting object to evade intercepting object 132 and its lethal kill radius R. For example, air brake 118 may remain deployed until a separation distance between the trajectory of the intercepting object 132 and the altered trajectory of the guided projectile 100 is greater than lethal kill radius R. By deploying air brake 118 for a duration until the separation distance is greater than the kill radius R, guided projectile 100 is able to perform an evasive maneuver to bring guided projectile 100 outside a maneuvering radius of intercepting object 132. In other words, the maneuvering radius and/or capabilities of intercepting object 132 are limited in compensating for the rapid deceleration and/or loss in altitude of guided projectile 100 as a result of deployment of air brake 118.
As shown in the fourth illustration 148, air brake 118 may be detached from guided projectile 100 when it is determined intercepting object 132 has been evaded. Detaching air brake 118 from guided projectile 100 causes the air brake 118 to be jettisoned from the guided projectile 100 and enables guided projectile 100 to advance on a second target trajectory 150 that is offset from first target trajectory 142 as a result of the loss in altitude from deployment of air brake 118. In one example, guided projectile 100 is programmed to detach air brake 118 based on time, such as after a predetermined amount of time has elapsed. The predetermined amount of time may be calculated starting from when air fins 122 (shown in
The determination that intercepting object 132 has been evaded, and of when to detach air brake 118, may also be made based on measurements determined by first and/or second sensors 110 and 112. In one example, first sensor 110 continuously monitors the distance between intercepting object 132 and guided projectile 100 as intercepting object 132 approaches guided projectile 100 when on an intercept trajectory, and as intercepting object 132 distances from guided projectile 100 upon performance of the evasive maneuver. Accordingly, air brake 118 may be detached from guided projectile 100 when the distance between guided projectile 100 and intercepting object 132 is greater than a predetermined threshold that is greater than lethal kill radius R. Lethal kill radius R may be determined based on measurements taken by first sensor 110. For example, first sensor 110 may be capable of monitoring the size of an exhaust plume and/or an approaching speed of intercepting object 132 to identify the type and size, and thus the lethal kill radius R, of intercepting object 132. Alternatively, guided projectile 100 may operate based on an estimated size of lethal kill radius R that is pre-programmed into guided projectile 100.
In addition, second sensor 112 monitors at least one of an air speed or an altitude of guided projectile 100 throughout flight and, specifically, while air brake 118 is deployed. In one example, air brake 118 is detached when at least one of the air speed or the altitude is less than a respective minimum threshold. The minimum thresholds may be determined based on the air speed and remaining altitude required for guided projectile 100 to re-accelerate, after air brake 118 is detached, and reach target location 138. In some implementations, this determination of when to detach air brake 118 is a failsafe that overrides all other air brake detachment control programs.
Guided projectile 100 may be programmed to detach air brake 118 based on time and/or based on a proximity of second intercepting object 154 relative to guided projectile. For example, air brake 118 may be detached after the predetermined amount of time discussed above, and an additional amount of time, has elapsed. The additional amount of time may be added when it is determined second intercepting object 154 is present. Alternatively, air brake 118 may be detached from guided projectile 100 when the distance between guided projectile 100 and second intercepting object 154 is greater than a predetermined threshold that is greater than lethal kill radius R, as discussed above.
This written description uses examples to disclose various implementations, including the best mode, and also to enable any person skilled in the art to practice the various implementations, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the disclosure is defined by the claims, and may include other examples that occur to those skilled in the art after reading this specification. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims.
This application claims the benefit of U.S. Provisional Patent Application Ser. No. 63/197,575, filed on Jun. 7, 2021, the entire contents of which are hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
2709054 | Roth | May 1955 | A |
3047259 | Tatnall | Jul 1962 | A |
3228634 | Chakoian | Jan 1966 | A |
4005655 | Kleinschmidt | Feb 1977 | A |
4145917 | Brazhnikov | Mar 1979 | A |
4504031 | Andrews | Mar 1985 | A |
4624424 | Pinson | Nov 1986 | A |
6502785 | Teter | Jan 2003 | B1 |
6666402 | Rupert | Dec 2003 | B2 |
7004424 | Pacchia | Feb 2006 | B1 |
7229048 | August | Jun 2007 | B1 |
7431237 | Mock et al. | Oct 2008 | B1 |
7611095 | Alban, III | Nov 2009 | B1 |
7800032 | Facciano | Sep 2010 | B1 |
8026465 | Fraysse, Jr. | Sep 2011 | B1 |
20010039898 | Bar | Nov 2001 | A1 |
20020088897 | Davis | Jul 2002 | A1 |
20140216290 | Yee et al. | Aug 2014 | A1 |
20170268855 | McAllister et al. | Sep 2017 | A1 |
Number | Date | Country |
---|---|---|
3667226 | Jun 2020 | EP |
WO2008143707 | Nov 2008 | WO |
Number | Date | Country | |
---|---|---|---|
20230045482 A1 | Feb 2023 | US |
Number | Date | Country | |
---|---|---|---|
63197575 | Jun 2021 | US |