Systems and methods for countering an unmanned air vehicle

Information

  • Patent Grant
  • 11161610
  • Patent Number
    11,161,610
  • Date Filed
    Friday, July 26, 2019
    4 years ago
  • Date Issued
    Tuesday, November 2, 2021
    2 years ago
Abstract
Systems and methods for countering an unmanned air vehicle are disclosed. An example method includes detecting a target UAV via a first component of a target acquisition system. The example method further includes, in response to detecting the target UAV, directing, by executing one or more computer-readable instructions of a launch control system in communication with the target acquisition system, an interceptor UAV to launch. The example method further includes, subsequent to the launch, tracking the target UAV via a second component of the target acquisition system, the second component carried by the interceptor UAV. The example method further includes, when the target UAV is within a target range of the interceptor UAV, deploying a disabling element from the interceptor UAV toward the target UAV.
Description
TECHNICAL FIELD

The present disclosure is directed generally to systems and methods for countering an unmanned air vehicle (UAV). In particular embodiments, representative systems and methods include directing an interceptor UAV toward a target UAV to disable the target UAV.


BACKGROUND

Unmanned air vehicles (UAVs) have been used in a wide variety of capacities to provide surveillance and perform other tasks. Some tasks include destroying, disabling or otherwise damaging a target on the ground. Accordingly, a need has arisen for systems to counter such UAVs so as to avoid damage to military and/or civilian installations. The present disclosure is directed to such systems.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is an overall schematic illustration of a counter-UAV system and associated methods.



FIG. 2 is a side view of a representative interceptor UAV configured in accordance with an embodiment of the present disclosure.



FIGS. 3A-3C are front isometric, top plan, and front views, respectively, of a representative interceptor UAV shown in FIG. 2.



FIG. 4 is a partially schematic timeline and illustration of a representative trajectory for a target UAV and associated interceptor UAVs, in accordance with a particular embodiment of the present technology.



FIG. 5 is a table illustrating expected specifications for an interceptor UAV configured in accordance with a particular embodiment of the present technology.



FIG. 6 illustrates a representative disabling system configured in accordance with an embodiment of the present technology.



FIG. 7 illustrates representative subsystems and transport features in accordance with particular embodiments of the present technology.





DETAILED DESCRIPTION

The present disclosure is directed generally to counter-UAV systems and associated methods. A representative counter-UAV system in accordance with a particular embodiment includes an interceptor UAV that is launched toward a detected target UAV. The target UAV is detected, for example, by a ground-based detector, which triggers a launch sequence for the interceptor UAV. The interceptor UAV then flies autonomously to intercept the target UAV. For at least one phase of operation, the interceptor UAV may receive signals from the ground to assist in directing it toward the target. During another phase of operation, the interceptor UAV can operate without such assistance, e.g., as it engages with the target UAV. The interceptor UAV can disable the target UAV, for example, by deploying a net that interferes with the flight of the target UAV and causes the target UAV to strike the ground. In particular embodiments, the interceptor UAV can also return to the ground, but in a controlled manner (so as to be used again), e.g., if it does not successfully engage with and/or disable the target UAV. Further embodiments and specific details of representative systems and methods in accordance with the present technology are described below with reference to FIGS. 1-7.


Many embodiments of the present disclosure described below may take the form of computer- or controller-executable instructions, including routines executed by a programmable computer, controller and/or associated system. Those skilled in the relevant art will appreciate that the disclosure can be practiced on computer systems other than those shown and described below. The technology can be embodied in a special purpose computer or data processor that is specifically programmed, configured or constructed to perform one or more of the computer-executable instructions described below. Accordingly, the terms “computer” and “controller” as generally used herein refer to any suitable data processor and can include Internet appliances and handheld devices, including palmtop computers, wearable computers, cellular or mobile phones, multi-processor systems, processor-based or programmable consumer electronics, network computers, mini-computers and the like. Information handled by these computers and/or controllers can be presented to a user, observer, or other participant via any suitable display medium, such as an LCD screen.


In particular embodiments, aspects of the present technology can be practiced in distributed environments, where tasks or modules are performed by remote processing devices that are linked through a communications network. In distributed computing environments, program modules or subroutines may be located in local and remote memory storage devices. Aspects of the technology described below may be stored or distributed on computer-readable media, including magnetically or optically readable or removable computer disks, as well as distributed electronically over networks. Data structures and transmissions of data particular to aspects of the present technology are also encompassed within the scope of particular embodiments of the present technology.



FIG. 1 illustrates an overall system 100 that includes an interceptor UAV 110 configured to disable or destroy a target UAV 199. The interceptor UAV 110 can include a propulsion system 120, a guidance system 130 (e.g., computer-based or controlled), a communication system 160 (e.g., computer-based or controlled), and an engagement system 140 (e.g., computer-based or controlled). The engagement system 140 is used to engage with and disable the target UAV 199. The overall system 100 can further include a target acquisition system 101 (e.g., computer-based or controlled), which operates in (and/or can otherwise monitor) the airspace in which the target UAV 199 may appear to acquire the target UAV 199, as indicated by arrow E. The target acquisition system 101 further includes one or more first components 101a that are not carried by the interceptor UAV 110, and one or more second components 101b that are carried by the interceptor UAV 110. These components can communicate with each other, as indicated by arrow A. A launch control system 102 communicates with the target acquisition system 101 (as indicated by arrow B) and, based on the information it receives, transmits a signal to a launcher 103 (e.g., computer-based or controlled) (as indicated by arrow C). The launcher 103 launches the interceptor UAV 110, which then flies toward the target UAV 199 and then intercepts and engages with the target UAV 199. The interceptor UAV 110 communicates with a ground station or other controller 106 that provides command and control signals and/or receives data, as indicated by arrow D.


Further details of representative embodiments of the interceptor UAV 110 are described below with reference to FIGS. 2-3C. Further details of a representative sequence of events for intercepting a target UAV are then described below with reference to FIG. 4, and FIGS. 5-7 provide additional details of selected features of the system 100.



FIG. 2 is a partially schematic, partially transparent plan view of a representative interceptor UAV 110 described above with reference to FIG. 1. In a particular aspect of this embodiment, the interceptor UAV 110 includes a flight vehicle 111 which in turn includes a fuselage 112 elongated along a fuselage axis 113. The interceptor UAV 110 includes a propulsion system 120 that can in turn include one or more propellers 121 that provide thrust for the interceptor UAV 110. In a particular embodiment, the propulsion system 120 includes a first propeller 121a and a second propeller 121b. The propellers 121a, 121b can operate in a counter-rotating manner so as to reduce or eliminate twist or torque, which might otherwise be imparted to the interceptor UAV 110 as the propulsion system 120 generates thrust.


In a particular aspect of an embodiment shown in FIG. 2, the propellers 121 can be integrated with the fuselage 112 at some distance along the length of the fuselage 112, rather than at the forward or aft tip of the fuselage 112. For example, as shown in FIG. 2, the first and second propellers 121a, 121b can be positioned along the fuselage axis 113, e.g., about one-third of the distance between the aft end and the forward end of the fuselage 112. In a particular embodiment, the propellers 121a, 121b can also be integrated with one or more other elements of the interceptor UAV 110. For example, the interceptor UAV 110 can include one or more fins 114 (e.g., four) that provide stability for the interceptor UAV 110. Each fin 114 can include a slot 115 that receives the first and second propellers 121a, 121b as the propellers rotate. Accordingly, as the propellers 121a, 121b rotate, they pass sequentially from the slot 115 in one fin 114 to and through the slot 115 in the adjacent fin 114 so as to avoid interfering with the fins 114, while at the same time generating thrust for the interceptor UAV 110.


The propulsion system 120 can further include a power source 123 that provides power to the propellers 121a, 121b. In a particular embodiment, the power source 123 includes an electrical energy storage device, for example, one or more batteries 124. In still a further particular embodiment, the power source 123 includes two batteries: a first battery 124a and a second battery 124b. Each battery 124a, 124b directs electrical current to a corresponding motor 122 (shown as a first motor 122a and a second motor 122b), which rotate the first and second propellers 121a, 121b, respectively. The separate propellers, motors and batteries can provide a measure of redundancy for the interceptor UAV 110. In other embodiments, the propulsion system 120 can include other arrangements, for example, propellers driven by a single motor and/or a single battery, propellers powered by an internal combustion engine, and/or a rocket or other non-propeller system.


The interceptor UAV 110 can also include a vehicle management system (VMS) 165 that oversees, conducts, directs, and/or executes processes, at least some of which are carried out by a variety of systems, subsystems and/or other elements. Representative systems include a guidance system 130 that operates to control and guide the interceptor UAV 110 toward its target. For example, the guidance system 130 can be coupled to one or more control surfaces 131 to steer and maneuver the interceptor UAV 110. The control surfaces 131 can be carried by the fins 114 (as shown in FIG. 2), and/or by the fuselage 112, and/or by other elements/structures of the interceptor UAV 110. In a particular embodiment, the control surfaces 131 are positioned in the prop wash from the propellers 121a, 121b to improve control authority at low airspeeds, e.g., during vertical take-off. The guidance system 130 can also include a navigation system 132 (e.g., an on-board GPS system) that provides information regarding the location of the interceptor UAV 110. The VMS 165 coordinates the operation of the navigation system 132 and the control surfaces 131 to provide for proper guidance of the interceptor UAV 110. The communication system 160 provides for communication with a ground station or other controller, and/or other elements of the overall system 100.


The interceptor UAV 110 can also include an engagement system 140 that is used to engage with the target UAV 199 described above with reference to FIG. 1. In particular, the engagement system 140 can include the airborne component(s) 101b of the target acquisition system described above with reference to FIG. 1. In addition, the engagement system 140 can include a disabling system 150 that disables the target UAV 199 when the interceptor UAV 110 is within a suitable range of the target UAV 199. In a particular embodiment, the disabling system 150 can include a disabling element, e.g., a net that is deployed to entangle the target UAV 199, as will be described further below with reference to FIGS. 4 and 6. The engagement system 140 can include, control, and/or communicate with other aircraft systems (e.g., the guidance system 130) that contribute to providing instructions for guiding the interceptor UAV 110 and/or directing the interceptor UAV 110.



FIGS. 3A-3C illustrate further views of a representative embodiment of the interceptor UAV 110. For example, these Figures illustrate a nose 117 of the flight vehicle 111 that can house the airborne components 101b of the target acquisition system (see FIG. 2). FIGS. 3A-3B also illustrate a tail cone 116 that can house the communication system 160, described above with reference to FIG. 2.



FIG. 4 illustrates a timeline 190 having representative points in time (e.g., T0, T1, T2, etc.) that correspond to representative tasks performed by the system 100, as the interceptor UAV 110 engages the target UAV 199. Below the timeline, FIG. 4 illustrates expected, representative elapsed times in accordance with a particular embodiment, along with representative down-range locations for the incoming target UAV 199. The times and ranges assume the target UAV 199 has a speed of about 90 knots. The characteristics of the interceptor UAV 110 are generally as described above with reference to FIGS. 2-3C, and as described in further detail later with reference to FIG. 5.



FIG. 4 also schematically identifies representative locations of the interceptor UAV 110 and the target UAV 199, with corresponding points in time (boxed) at which these vehicles arrive at the illustrated locations. In a particular embodiment shown in FIG. 4, the overall system 100 deploys up to two interceptor UAVs 110 to disable the incoming target UAV 199. Accordingly, points in time associated with the second interceptor UAV are indicated with a parenthetical “2,” e.g., “T7(2).” In other embodiments, the system can be configured to deploy a single interceptor UAV 110 and in still further embodiments, more than two interceptor UAVs 110.


The representative process shown in FIG. 4 begins at time T0 when the target UAV 199 is first detected by the system 100. In a particular embodiment, the target UAV 199 can be detected by a first detector, e.g., a first radar 104a. In a further aspect of this embodiment, the first radar 104a can be carried by an airborne platform 170. For example, the airborne platform 170 can include an RQ-21A aircraft manufactured by Insitu Inc., a subsidiary of The Boeing Company. In other embodiments, the airborne platform 170 can include other aircraft, and in still further embodiments, the first radar 104a can be carried by platforms other than airborne platforms.


At time T1, a second detector, e.g., a second radar 104b, assumes responsibility for tracking the target UAV 199. In a particular embodiment, the second radar 104b can include a ground-based radar and in other embodiments, the second radar 104b can have other locations. In any of these embodiments, information received from the second radar 104b is used to perform tracking tasks. For example, at time T2, the azimuth, elevation, and range of the target UAV 199 are calculated using information from the second radar 104b, and the track of the target UAV 199 is established. At time T3, the system 100 calculates an intercept track for the interceptor UAV 110. This information is then used to direct a launcher 103 to launch a first interceptor UAV 110 at time T4. In a particular embodiment, the launch is vertical, e.g., from a canister or other suitable launch device. In addition, at time T3, an additional tracking system, e.g., a ground-based optics system 105, begins identifying and tracking the target UAV 199. The ground-based optics system 105 remains actively engaged with the target UAV 199 throughout the rest of the process.


At time T5, the interceptor UAV 110 continues its upward and down-range trajectory. At time T6, the interceptor UAV 110 transitions to an intercept vector. In a particular embodiment, the interceptor UAV 110 achieves a speed of 100 KTAS, and transitions to a target acquisition mode.


At time T7, a second interceptor UAV 110 is launched (e.g., for systems 100 that include the capability for deploying multiple interceptor UAVs 110 toward a single target), typically before the first UAV 110 has disabled (or attempted to disable) the target UAV 199. The instructions given to the second interceptor UAV 110 and the actions taken by the second interceptor UAV 110 parallel those discussed above and further below with reference to the initial interceptor UAV 110. In FIG. 4, selected times associated with the second interceptor UAV 110 are indicated with a parenthetical “2.” Accordingly, “T7(2)” indicates the launch of the second interceptor UAV 110.


At time T8, the initial interceptor UAV 110 acquires the target UAV 199 using the second target acquisition system 101b carried by the interceptor UAV 110. For example, the second target acquisition system 101b can include an airborne optics system. The second target acquisition system 101b can remain active for the rest of the mission of the initial interceptor UAV 110.


Once the second target acquisition system 101b has acquired the target, the process can include comparing the image(s) obtained from the second target acquisition system 101b with the image(s) obtained from the ground-based optics system 105 and/or other elements of the first target acquisition system 101a. This process can be performed to confirm that the target acquired by the interceptor UAV 110 matches the target identified by the ground-based or other target acquisition systems. The comparison process can be carried out by a human operator in particular embodiments, and can be automated in other embodiments.


At time T9, an engagement decision is made. In some embodiments, human operators or other suitable personnel make the decision, and in other embodiments, the decision can be automated. In any of these embodiments, the decision can be made based on the comparison process described above, and/or other information received from the second target acquisition system 101b (carried by the first interceptor UAV 110) and/or other information received from the first target acquisition system 101a and/or other assets or subsystems. Once the decision is made, the first interceptor UAV 110 receives instructions to either continue with the intercept track, or abort the intercept track and return to ground. If the decision is made to abort the intercept track, the first interceptor UAV 110 returns to its base (or another suitable landing site) and lands, for example, with a controlled descent into an airbag, or via another suitable procedure.


If the decision is made to continue with the intercept track, then at time T10, the first interceptor UAV 110 executes a terminal maneuver. In a particular embodiment, the interceptor UAV achieves a velocity of 150 KTAS for this portion of the mission. In cases for which the interceptor UAV 110 includes an outward-deploying net, the track toward the target UAV 199 can be head-on to increase the likelihood for a successful engagement. The terminal maneuver can include deploying the disabling system 150 (e.g., deploying a net 151 and associated weights 152) that make contact with, tangle with, and/or otherwise disable the target UAV 199. In one aspect of this embodiment, the net 151 deploys generally outwardly to entangle the oncoming target UAV 199. In a further aspect of this embodiment, the net's outward deployment direction (rather than a forward deployment direction) reduces the likelihood that the net 151 will interfere with the nose-mounted second target acquisition system 101b. In other embodiments, the second target acquisition system 101b can be expended during the disabling process. In such cases, the interceptor UAV 110 can use other systems to perform a controlled landing, or can itself be expended.


During the disabling process, the net 151 can tangle with or otherwise become caught in the propeller(s), fuselage, lifting surfaces and/or other elements of the target UAV 199, so as to interfere with and disable the controlled flight of the target UAV 199. The net 151 can remain attached to the interceptor UAV 110 after it is deployed, so that both the first interceptor UAV 110 and the entangled target UAV 199 fall to the ground. In other embodiments, the net 151 can be released by the first interceptor UAV 110, in which case, the target UAV 199 can fall to the ground, and the first interceptor UAV 110 can return to ground in accordance with a controlled process (e.g., a normal landing), similar to or identical to the process described above in which the interceptor UAV 110 lands if a decision is made to abort the intercept mission.


If the first interceptor UAV 110 is successful, then at time T11, the intercept process is complete, and at time T12, the system 100 confirms the success of the intercept, e.g., from the ground-based optics system 105 and/or another sensor. The second interceptor UAV 110 then lands in a controlled manner.


If the terminal maneuver and intercept processes carried out by the first interceptor UAV 110 are not successful (e.g., if the first interceptor UAV 110 did not or did not sufficiently disable the target UAV 199), and if the first interceptor UAV 110 is still flyable, then the first interceptor UAV 110 returns to its base. For example, if the interceptor UAV releases the net 151 as part of the disabling process, and does not strike the target UAV 199 as part of the engagement maneuver, then the interceptor UAV 110 can redirect its flight path to land. If the net 151 remains attached to the interceptor UAV 110 during a normal disabling process, and the disabling process is not successful, the interceptor UAV 110 can jettison the net 151 before landing. In one aspect of such an embodiment, the net 151 can be deployed from the tail of the interceptor UAV 110 rather than the nose, to avoid interfering with the propellers of the interceptor UAV 110.


If the first interceptor UAV 110 is unsuccessful, then the second interceptor UAV 110 continues to carry out the mission. For example, at time T12, the second interceptor UAV 110 can acquire the target UAV 199. At time T13, the second interceptor UAV 110 can be directed to either complete the engagement process or return to base, and at time T14, the second interceptor UAV 110 can execute the terminal engagement process. At time T15, the second interceptor UAV 110 intercepts the target UAV 199, and at time T16, the system 100 confirms a successful intercept by the second interceptor UAV 110.



FIG. 5 is a table illustrating representative specifications for an interceptor UAV 110 configured in accordance with a particular embodiment of the present technology. FIG. 5 includes representative values for gross take-off weight (GTOW), payload, fuel (e.g., battery size and type), mission radius, endurance, speeds, ceiling, engine specification, wingspan, and recovery footprint (e.g., the size of an airbag used to recover the interceptor UAV 110). It is expected that an interceptor UAV 110 with the characteristics identified in FIG. 5 can successfully intercept and disable a wide range of incoming target UAVs 199, e.g., ranging in size from micro-UAVs and quad-copters up to Tier II tactical UAS vehicles. Such UAVs are expected to be successfully intercepted and disabled at altitudes ranging from 0-5000 feet AGL.



FIG. 6 illustrates a representative disabling system 150 configured in accordance with a particular embodiment of the disclosed technology. The system 150 can include a net gun 153, such as are commercially available for capturing wild animals. The net gun 153 can include a propellant 154 (e.g., a conventional CO2 cartridge) which directs a net 151 in a laterally outward direction. The weights 152 spread the net 151 out as it deploys. The disabling system 150 can have multiple modes, e.g., an inactive mode, an armed mode and a deployed mode. In other embodiments, the disabling system 150 can include other elements. For example, the disabling system 150 can include projectile, explosive, and/or energy-based components (e.g., lasers and/or high-powered RF generators).



FIG. 7 is a partially schematic illustration of particular components of the overall system 100 and containers in which the components can be transported. For example, FIG. 7 illustrates a representative land-based optics system 105, a pair of antenna interface terminals 108 (for communication with the interceptor UAVs), and a ground-based radar and support system 104b. FIG. 7 also illustrates a representative command, control and data system 106, for example, an ICOMC2 system available from Insitu Inc. The system 106 can include two operator work stations, one for each of the interceptor UAVs 110 that can be deployed against a single target UAV 199. The foregoing elements can be transported in first containers 107a (e.g., six such containers) and second containers 107b can be used to carry miscellaneous components and other components not specifically shown in FIG. 7, including the vehicle itself, launch systems, recovery systems, and storage and health systems. These containers are specifically designed to be readily transported and handled manually or with automated equipment.


One feature of several of the embodiments described above is that the system 100 can include the capability for the interceptor UAV 110 to be recovered and reused, for example, if it has not successfully engaged with an incoming target. This feature can be advantageous because it reduces the cost of operating the system 100 in the event that a particular interceptor UAV 110 is unable to successfully engage with the target. This feature can also reduce or eliminate the likelihood for collateral damage.


Another feature of at least some of the foregoing embodiments is that the overall system 100 can deploy multiple interceptor UAVs 110 against a single incoming target UAV 199. This ability to provide redundant and/or multiple counter-measures against the target UAV 199, thus improving the likelihood for disabling the target UAV 199. For example, this arrangement can provide a “second chance” in the event that an initial interceptor UAV is unsuccessful in its attempt to disable the incoming target UAV 199. The overall result of the foregoing features is that the system 100 can be robust and low cost, compared with other conventional systems.


Still another feature of at least some of the embodiments described above is that the interceptor UAV 110 can include counter-rotating propellers located along the length of the UAV and/or integrated with the fin structure of the UAV. An advantage of this configuration is that it can provide a compact, efficient, propeller-based interceptor function, suitable for intercepting vehicles having relatively low airspeeds, without the complexity, expense, and/or handling complications presented by more complex rocket-based or gas turbine-based systems. In addition, this configuration is expected to be highly maneuverable, which can in turn increase the likelihood of a successful engagement. For example, the highly maneuverable configuration can allow the interceptor UAV 110 to account for evasive maneuvers performed by the target UAV 199, and/or can allow the interceptor UAV 110 to re-engage with the target UAV 199 if its initial engagement is unsuccessful.


From the foregoing, it will be appreciated that specific embodiments of the disclosed technology have been described herein for purposes of illustration, but that various modifications may be made without deviating from the technology. For example, while certain embodiments of the system were described above in the context of an interceptor UAV that deploys a net to engage and disable a target UAV, in other embodiments, the interceptor UAV can include other disabling systems. Such disabling systems can include the nose or other portion of the interceptor UAV 110 in an embodiment for which the interceptor UAV strikes the target UAV 199 in order to disable it. The first and second detectors described above in the context of radars 104a, 104b can have other configurations (e.g., IR or optical detectors) in other embodiments. Representative embodiments of the interceptor UAV 110 are shown as having a missile-type silhouette, with a generally round, cylindrical shape. In other embodiments, the interceptor UAV fuselage can have other shapes, and/or the flight vehicle 111 can have other suitable overall configurations. The flight vehicle 111 can have four fins arranged in a cruciform shape in some embodiments, and can have other arrangements and/or numbers of fins (e.g., three) in other embodiments. The flight vehicle 111 can launch vertically and land horizontally onto an airbag in some embodiments, and can launch and/or land in other manners in other embodiments. “Disabling” the target UAV can include causing the target UAV to deviate from its flight path sufficiently to reduce or eliminate the threat provided by the target UAV. This can include causing the target UAV to crash, arresting the target UAV, disrupting the target UAV and/or diverting the target UAV from its intended target or other target of value. The engagement system and/or the disabling system can be designed into the flight vehicle prior to manufacture, and/or can be configured to retrofit an existing flight vehicle.


Certain aspects of the technology described in the context of particular embodiments may be combined or eliminated in other embodiments. For example, while certain embodiments were described above in the context of a system that deploys multiple interceptor UAVs toward a single target UAV, other systems may be configured to deploy only a single interceptor UAV against any single incoming target UAV. Certain aspects of the overall system may be combined and/or segregated, depending upon the particular embodiment. For example, the launch control system can be integrated with one or more portions of the target acquisition system. The multiple radars (or other detectors) can be combined into a single detector. Furthermore, while advantages associated with certain embodiments of the disclosed technology have been described in the context of those embodiments, other embodiments may also exhibit such advantages, and not all embodiments need necessarily exhibit such advantages to fall within the scope of the present technology. Accordingly, the present disclosure and associated technology can encompass other embodiments not expressly shown or described herein.

Claims
  • 1. A method, comprising: detecting a target UAV via a first component of a target acquisition system;in response to detecting the target UAV, directing, by executing one or more computer-readable instructions of a launch control system in communication with the target acquisition system, an interceptor UAV to launch, the interceptor UAV having a propeller-based propulsion system configured to provide thrust for the interceptor UAV;subsequent to the launch, tracking the target UAV via a second component of the target acquisition system, the second component carried by the interceptor UAV;when the target UAV is within a target range of the interceptor UAV, deploying a disabling element from the interceptor UAV toward the target UAV;determining whether deploying the disabling element successfully disabled the target UAV; andin response to determining that deploying the disabling element did not successfully disable the target UAV, directing, by executing one or more computer-readable instructions of a guidance system carried by the interceptor UAV, the interceptor UAV to land via the propeller-based propulsion system.
  • 2. The method of claim 1, wherein the disabling element is a net configured to disable the target UAV in response to the net contacting the target UAV.
  • 3. The method of claim 2, wherein deploying the disabling element includes releasing the net from the interceptor UAV.
  • 4. The method of claim 2, wherein deploying the disabling element includes maintaining an attachment between the net and the interceptor UAV such that the net is not released from the interceptor UAV.
  • 5. The method of claim 1, further comprising propelling the interceptor UAV to travel along an intercept track determined for the interceptor UAV, the propelling including: rotating a first propeller of the propeller-based propulsion system of the interceptor UAV in a first direction; androtating a second propeller of the propeller-based propulsion system of the interceptor UAV in a second direction opposite the first direction.
  • 6. The method of claim 1, wherein the first component of the target acquisition system is a ground-based component.
  • 7. The method of claim 1, wherein the first component of the target acquisition system is an airborne component carried by an aircraft other than the interceptor UAV.
  • 8. A method, comprising: detecting a target UAV via a first component of a target acquisition system;in response to detecting the target UAV, directing, by executing one or more computer-readable instructions of a launch control system in communication with the target acquisition system, an interceptor UAV to launch;determining, by executing one or more computer-readable instructions of an engagement system carried by the interceptor UAV and in communication with the target acquisition system, whether to engage the interceptor UAV with the target UAV;in response to determining not to engage the interceptor UAV with the target UAV, directing, by executing one or more computer-readable instructions of a guidance system carried by the interceptor UAV, the interceptor UAV to land; andin response to determining to engage the interceptor UAV with the target UAV: tracking the target UAV via a second component of the target acquisition system,the second component carried by the interceptor UAV; and when the target UAV is within a target range of the interceptor UAV, deploying a disabling element from the interceptor UAV toward the target UAV.
  • 9. The method of claim 8, further comprising: determining whether deploying the disabling element successfully disabled the target UAV; andin response to determining that deploying the disabling element did not successfully disable the target UAV, directing, by executing one or more computer-readable instructions of the guidance system carried by the interceptor UAV, the interceptor UAV to land.
  • 10. The method of claim 8, wherein determining whether to engage the interceptor UAV with the target UAV includes: comparing a ground-based image obtained from the target acquisition system with an interceptor-UAV-based image obtained from the target acquisition system to render an engagement decision; andcommunicating the engagement decision to the engagement system carried by the interceptor UAV to cause the engagement system to determine, based on the engagement decision, whether to engage the interceptor UAV with the target UAV.
  • 11. The method of claim 8, further comprising propelling the interceptor UAV to travel along an intercept track determined for the interceptor UAV, the propelling including: rotating a first propeller of the interceptor UAV in a first direction; androtating a second propeller of the interceptor UAV in a second direction opposite the first direction.
  • 12. The method of claim 8, wherein the first component of the target acquisition system is a ground-based component.
  • 13. The method of claim 8, wherein the first component of the target acquisition system is an airborne component carried by an aircraft other than the interceptor UAV.
  • 14. A method, comprising: detecting a target UAV via a first component of a target acquisition system;in response to detecting the target UAV, directing, by executing one or more computer-readable instructions of a launch control system in communication with the target acquisition system, an interceptor UAV to launch;determining, by executing one or more computer-readable instructions of an engagement system carried by the interceptor UAV and in communication with the target acquisition system, whether to engage the interceptor UAV with the target UAV; andin response to determining not to engage the interceptor UAV with the target UAV, directing, by executing one or more computer-readable instructions of a guidance system carried by the interceptor UAV, the interceptor UAV to land.
  • 15. The method of claim 14, further comprising, in response to determining to engage the interceptor UAV with the target UAV: tracking the target UAV via a second component of the target acquisition system, the second component carried by the interceptor UAV; andwhen the target UAV is within a target range of the interceptor UAV, deploying a disabling element from the interceptor UAV toward the target UAV.
  • 16. The method of claim 15, further comprising: determining whether deploying the disabling element successfully disabled the target UAV; andin response to determining that deploying the disabling element did not successfully disable the target UAV, directing, by executing one or more computer-readable instructions of the guidance system carried by the interceptor UAV, the interceptor UAV to land.
  • 17. The method of claim 14, wherein determining whether to engage the interceptor UAV with the target UAV includes: comparing a ground-based image obtained from the target acquisition system with an interceptor-UAV-based image obtained from the target acquisition system to render an engagement decision; andcommunicating the engagement decision to the engagement system carried by the interceptor UAV to cause the engagement system to determine, based on the engagement decision, whether to engage the interceptor UAV with the target UAV.
  • 18. The method of claim 14, further comprising propelling the interceptor UAV to travel along an intercept track determined for the interceptor UAV, the propelling including: rotating a first propeller of the interceptor UAV in a first direction; androtating a second propeller of the interceptor UAV in a second direction opposite the first direction.
  • 19. A method, comprising: detecting a target UAV via a first component of a target acquisition system;in response to detecting the target UAV, directing, by executing one or more computer-readable instructions of a launch control system in communication with the target acquisition system, an interceptor UAV to launch;determining, by executing one or more computer-readable instructions of an engagement system carried by the interceptor UAV and in communication with the target acquisition system, whether to engage the interceptor UAV with the target UAV, the determining including: comparing a ground-based image obtained from the target acquisition system with an interceptor-UAV-based image obtained from the target acquisition system to render an engagement decision; andcommunicating the engagement decision to the engagement system carried by the interceptor UAV to cause the engagement system to determine, based on the engagement decision, whether to engage the interceptor UAV with the target UAV; andin response to determining to engage the interceptor UAV with the target UAV: tracking the target UAV via a second component of the target acquisition system, the second component carried by the interceptor UAV; andwhen the target UAV is within a target range of the interceptor UAV, deploying a disabling element from the interceptor UAV toward the target UAV.
  • 20. The method of claim 19, further comprising, in response to determining not to engage the interceptor UAV with the target UAV, directing, by executing one or more computer-readable instructions of a guidance system carried by the interceptor UAV, the interceptor UAV to land.
CROSS-REFERENCE TO RELATED APPLICATION

This application arises from a division of U.S. patent application Ser. No. 14/801,479, filed Jul. 16, 2015, which claims priority to U.S. Provisional Application No. 62/030,024, filed on Jul. 28, 2014. The entirety of U.S. patent application Ser. No. 14/801,479 and U.S. Provisional Application No. 62/030,024 are hereby incorporated herein by reference.

US Referenced Citations (268)
Number Name Date Kind
965881 Draper Aug 1910 A
968339 Geraldson Aug 1910 A
975953 Hourwich Nov 1910 A
1144505 Steffan Jun 1915 A
1164967 Thorp Dec 1915 A
1317631 Kinser Sep 1919 A
1383595 Black Jul 1921 A
1384036 Anderson Jul 1921 A
1428163 Harriss Sep 1922 A
1499472 Pratt Jul 1924 A
1530010 Neilson Mar 1925 A
1532736 Dodds Apr 1925 A
1556348 Ray et al. Oct 1925 A
1624188 Simon Apr 1927 A
RE16613 Moody et al. May 1927 E
1634964 Steinmetz Jul 1927 A
1680473 Parker Aug 1928 A
1686298 Uhl Oct 1928 A
1712164 Peppin May 1929 A
1716670 Sperry Jun 1929 A
1731091 Belleville Oct 1929 A
1737483 Verret Nov 1929 A
1738261 Perkins Dec 1929 A
1748663 Tucker Feb 1930 A
1749769 Johnson Mar 1930 A
1756747 Holland Apr 1930 A
1777167 Forbes Sep 1930 A
1816976 Kirkham Aug 1931 A
1825578 Cernuda Sep 1931 A
1836010 Audrain Dec 1931 A
1842432 Stanton Jan 1932 A
1869506 Richardson Aug 1932 A
1892357 Moe Dec 1932 A
1909445 Ahola May 1933 A
1912723 Perkins Jun 1933 A
1925212 Steiber Sep 1933 A
1940030 Steiber Dec 1933 A
1960264 Heinkel May 1934 A
2211089 Berlin Aug 1940 A
2286381 Rubissow Jun 1942 A
2296988 Endter Sep 1942 A
2333559 Grady et al. Nov 1943 A
2342773 Wellman Feb 1944 A
2347561 Howard et al. Apr 1944 A
2360220 Goldman Oct 1944 A
2364527 Haygood Dec 1944 A
2365778 Schwab Dec 1944 A
2365827 Liebert Dec 1944 A
2380702 Persons Jul 1945 A
2390754 Valdene Dec 1945 A
2401853 Bailey Jun 1946 A
2435197 Brodie Feb 1948 A
2436240 Wiertz Feb 1948 A
2447945 Knowler Aug 1948 A
2448209 Boyer et al. Aug 1948 A
2465936 Schultz Mar 1949 A
2488050 Brodie Nov 1949 A
2488051 Brodie Nov 1949 A
2515205 Fieux Jul 1950 A
2526348 Gouge Oct 1950 A
2669403 McKay nee Milligan Feb 1954 A
2671938 Roberts Mar 1954 A
2735391 Buschers Feb 1956 A
2787185 Rea et al. Apr 1957 A
2814453 Trimble, Jr. et al. Nov 1957 A
2843342 Ward Jul 1958 A
2844340 Daniels et al. Jul 1958 A
2908240 Hodge Oct 1959 A
2919871 Sorensen Jan 1960 A
2933183 Koelsch Apr 1960 A
2937827 Duce May 1960 A
2954946 O'Neil et al. Oct 1960 A
3069118 Bernard Dec 1962 A
RE25406 Byrne et al. Jun 1963 E
3163380 Brodie Dec 1964 A
3268090 Wirkkala Aug 1966 A
3411398 Blakeley et al. Nov 1968 A
3454244 Walander Jul 1969 A
3468500 Carlsson Sep 1969 A
3484061 Niemkiewicz Dec 1969 A
3512447 Vaughn May 1970 A
3516626 Strance et al. Jun 1970 A
3589651 Niemkiewicz Jun 1971 A
3657956 Bradley et al. Apr 1972 A
3672214 Yasuda Jun 1972 A
3684219 King Aug 1972 A
3708200 Richards Jan 1973 A
3765625 Myhr et al. Oct 1973 A
3771484 Schott et al. Nov 1973 A
3827660 Doolittle Aug 1974 A
3939988 Wellman Feb 1976 A
3943657 Leckie Mar 1976 A
3980259 Greenhalgh et al. Sep 1976 A
4037807 Johnston et al. Jul 1977 A
4067139 Pinkerton et al. Jan 1978 A
4079901 Mayhew et al. Mar 1978 A
4143840 Bernard et al. Mar 1979 A
4147317 Mayhew et al. Apr 1979 A
4149840 Tippmann Apr 1979 A
D256816 McMahon et al. Sep 1980 S
4236686 Barthelme et al. Dec 1980 A
4238093 Siegel et al. Dec 1980 A
4267987 McDonnell May 1981 A
4279195 Miller Jul 1981 A
4296894 Schnäbele et al. Oct 1981 A
4296898 Watson Oct 1981 A
4311290 Koper Jan 1982 A
4372016 LaViolette et al. Feb 1983 A
4408737 Schwaerzler Oct 1983 A
4410151 Höppner et al. Oct 1983 A
4457479 Daude Jul 1984 A
4471923 Höppner et al. Sep 1984 A
4523729 Frick Jun 1985 A
4566658 DiGiovanniantonio et al. Jan 1986 A
4645142 Soelter Feb 1987 A
4653706 Ragiab Mar 1987 A
4678143 Griffin Jul 1987 A
4730793 Thurber, Jr. et al. Mar 1988 A
4753400 Reuter et al. Jun 1988 A
4790497 Yoffe Dec 1988 A
4809933 Buzby et al. Mar 1989 A
4842222 Baird Jun 1989 A
4909458 Martin Mar 1990 A
4979701 Colarik et al. Dec 1990 A
4991739 Levasseur Feb 1991 A
5007875 Dasa Apr 1991 A
5039034 Burgess et al. Aug 1991 A
5042750 Winter Aug 1991 A
5054717 Taylor Oct 1991 A
5060888 Vezain et al. Oct 1991 A
5109788 Heinzmann May 1992 A
5119935 Stump et al. Jun 1992 A
5145129 Gebhard Sep 1992 A
5176339 Schmidt Jan 1993 A
5222694 Smoot Jun 1993 A
5253605 Collins Oct 1993 A
5253606 Ortelli Oct 1993 A
5259574 Carrot Nov 1993 A
5378851 Brooke et al. Jan 1995 A
5390550 Miller Feb 1995 A
5407153 Kirk et al. Apr 1995 A
5509624 Takahashi Apr 1996 A
5583311 Rieger Dec 1996 A
5603592 Sadri et al. Feb 1997 A
5655944 Fusselman Aug 1997 A
5687930 Wagner et al. Nov 1997 A
5762456 Aasgaard Jun 1998 A
5816761 Cassatt et al. Oct 1998 A
5906336 Eckstein May 1999 A
5913479 Westwood, III Jun 1999 A
6161797 Kirk et al. Dec 2000 A
6237875 Menne et al. May 2001 B1
6264140 McGeer et al. Jul 2001 B1
6343768 Muldoon Feb 2002 B1
6370455 Larson et al. Apr 2002 B1
6371410 Cairo-Iocco et al. Apr 2002 B1
6416019 Hilliard et al. Jul 2002 B1
6442460 Larson et al. Aug 2002 B1
6457673 Miller Oct 2002 B1
6478650 Tsai Nov 2002 B1
6626077 Gilbert Sep 2003 B1
6695255 Husain Feb 2004 B1
6758440 Repp et al. Jul 2004 B1
6772488 Jensen et al. Aug 2004 B1
6835045 Barbee et al. Dec 2004 B1
6874729 McDonnell Apr 2005 B1
6925690 Sievers Aug 2005 B2
7059564 Dennis Jun 2006 B2
7066430 Dennis et al. Jun 2006 B2
7090166 Dennis et al. Aug 2006 B2
7114680 Dennis Oct 2006 B2
7121507 Dennis et al. Oct 2006 B2
7128294 Roeseler et al. Oct 2006 B2
7140575 McGeer et al. Nov 2006 B2
7143974 Roeseler et al. Dec 2006 B2
7152827 McGeer Dec 2006 B2
7155322 Nakahara et al. Dec 2006 B2
7165745 McGeer et al. Jan 2007 B2
7175135 Dennis et al. Feb 2007 B2
7219856 Watts et al. May 2007 B2
7259357 Walker Aug 2007 B2
7264204 Portmann Sep 2007 B1
7410125 Steele Aug 2008 B2
7422178 DeLaune Sep 2008 B2
7472461 Anstee Jan 2009 B2
7510145 Snediker Mar 2009 B2
7578467 Goodrich Aug 2009 B2
7686247 Monson et al. Mar 2010 B1
7740210 Pilon et al. Jun 2010 B2
7748661 Harris et al. Jul 2010 B2
7798445 Heppe et al. Sep 2010 B2
7806366 Jackson Oct 2010 B2
8016073 Petzl et al. Sep 2011 B2
8028952 Urnes, Sr. Oct 2011 B2
8038090 Wilson et al. Oct 2011 B2
8063347 Urbano Nov 2011 B1
8136766 Dennis Mar 2012 B2
8172177 Lovell et al. May 2012 B2
8205537 Dupont Jun 2012 B1
8313057 Rednikov Nov 2012 B2
8348714 Newton et al. Jan 2013 B2
8387540 Merems Mar 2013 B2
8683770 diGirolamo et al. Apr 2014 B2
8820698 Balfour et al. Sep 2014 B2
8944373 Dickson et al. Feb 2015 B2
8950124 Wellershoff Feb 2015 B2
9085362 Kilian et al. Jul 2015 B1
9266610 Knapp et al. Feb 2016 B2
9340301 Dickson et al. May 2016 B2
9359075 von Flotow et al. Jun 2016 B1
9932110 McNally Apr 2018 B2
20020011223 Zauner et al. Jan 2002 A1
20020049447 Li Apr 2002 A1
20020100838 McGeer et al. Aug 2002 A1
20030116107 Laimbock Jun 2003 A1
20030122384 Swanson et al. Jul 2003 A1
20030202861 Nelson et al. Oct 2003 A1
20030222173 McGeer et al. Dec 2003 A1
20040129833 Perlo et al. Jul 2004 A1
20050132923 Lloyd Jun 2005 A1
20050187677 Walker Aug 2005 A1
20060006281 Sirkis Jan 2006 A1
20060091258 Chiu et al. May 2006 A1
20060102783 Dennis et al. May 2006 A1
20060249623 Steele Nov 2006 A1
20060271251 Hopkins Nov 2006 A1
20070023582 Steele et al. Feb 2007 A1
20070051849 Watts et al. Mar 2007 A1
20070158498 Snediker Jul 2007 A1
20070169616 Vickroy Jul 2007 A1
20070200027 Johnson Aug 2007 A1
20070261542 Chang et al. Nov 2007 A1
20080156932 McGeer et al. Jul 2008 A1
20080191091 Hoisington et al. Aug 2008 A1
20090114761 Sells, II May 2009 A1
20090191019 Billings Jul 2009 A1
20090194638 Dennis Aug 2009 A1
20090224097 Kariv Sep 2009 A1
20090236470 Goossen et al. Sep 2009 A1
20090294584 Lovell et al. Dec 2009 A1
20100181424 Goossen et al. Jul 2010 A1
20100237183 Wilson et al. Sep 2010 A1
20100243799 Al-Qaffas Sep 2010 A1
20100318475 Abrahamson Dec 2010 A1
20110226889 Rovinsky Sep 2011 A1
20120210853 Abershitz et al. Aug 2012 A1
20120210904 Merems Aug 2012 A1
20120223182 Gilchrist, III et al. Sep 2012 A1
20130082137 Gundlach et al. Apr 2013 A1
20140216290 Yee Aug 2014 A1
20140231575 Shand Aug 2014 A1
20150129716 Yoffe May 2015 A1
20150166177 Bernhardt Jun 2015 A1
20160023760 Goodrich Jan 2016 A1
20160114906 McGeer et al. Apr 2016 A1
20160137311 Peverill et al. May 2016 A1
20160144980 Kunz et al. May 2016 A1
20160152339 von Flotow et al. Jun 2016 A1
20160264259 Dickson et al. Sep 2016 A1
20160320165 Rovinsky Nov 2016 A1
20160327945 Davidson Nov 2016 A1
20160375981 McDonnell Dec 2016 A1
20170225784 Hayes et al. Aug 2017 A1
20170369185 Grubb Dec 2017 A1
20180094908 Down et al. Apr 2018 A1
20180162528 McGrew et al. Jun 2018 A1
20190003511 Leon et al. Jan 2019 A1
20190006749 Mack et al. Jan 2019 A1
Foreign Referenced Citations (25)
Number Date Country
1032645 May 1989 CN
101549754 Oct 2009 CN
102384702 Mar 2012 CN
4301671 Jul 1993 DE
19602703 Feb 1997 DE
102010010508 Sep 2011 DE
0742366 Sep 1998 EP
854371 Apr 1940 FR
1445153 Aug 1976 GB
2080216 Feb 1982 GB
2093414 Sep 1982 GB
2150895 Jul 1985 GB
2219777 Dec 1989 GB
2231011 Nov 1990 GB
76726 Jan 1991 IL
07304498 Nov 1995 JP
H07304498 Nov 1995 JP
2008540217 Nov 2008 JP
2016215874 Dec 2016 JP
0075014 Dec 2000 WO
0107318 Feb 2001 WO
2008015663 Feb 2008 WO
2011066400 Jun 2011 WO
2012047677 Apr 2012 WO
2014080386 May 2014 WO
Non-Patent Literature Citations (20)
Entry
European Patent Office, “Extended European Search Report,” issued in connection with European Patent Application No. 20203534.1 dated Feb. 8, 2021, 9 pages.
European Patent Office, “Communication pursuant to Article 94(3) EPC,” issued in connection with European Patent Application No. 1517837530, dated Jun. 19, 2018, 5 pages.
“Ames Builds Advanced Yawed-Wing RPV,” Aviation Week and Space Technology, Jan. 22, 1973, 2 pages.
Robinson, “Dynamic Analysis of a Carousel Remotely Piloted Vehicle Recovery System,” 1977, Naval Post-Graduate School Master's Thesis No. ADA052401, 70 pages.
Whitmore, “Development of a Closed-Loop Strap Down Attitude System for an Ultrahigh Altitude Flight Experiment,” Jan. 1997, NASA Technical Memorandum 4775, 31 pages.
Dorr, “The XF-85 Goblin,” https://www.defensemedianetwork.com/stories/the-sf-85-goblin-the-parasite-fighter-that-didnt-work/, DefenseMediaNetwork, Sep. 11, 2014, 5 pages.
Gross, “Investigation of Lift, Drag, and Aeordynamic Pitching Moment During In-Flight Recovery of a Remotely Piloted Vehicle,” Air Force Institute of Technology, NTIS, Sep. 1973, 99 pages.
Phillips, “Alternate Aquila Recovery System Demonstration Recovery System Flight Test,” Final Report, Jan. 19, 20177, 67 pages.
Plane Talk, The Newsletter of the War Eagles Air Museum, www.war-eagles-air-museum.com, vol. 25, No. 1, First Quarter Jan.-Mar. 2012, 8 pages.
Dickard, “Mini-RPV Recover System Conceptual Study,” Contract DA4J02-76-C-0048, Report No. USAAMRDL-TR077-24, 321 pages. (Uploaded in 2 parts).
Hunton et al., “An Investigation of the McDonnell XP-85 Airplane in the Ames 40 by 80 Foot Wind Tunnel—Force and Moment Tests,” NACA Research Memorandum for the Air Material Command, U.S. Air Force, National Advisory Committee for Aeronautics, Sep. 27, 1948, 155 pages. (Uploaded in 2 parts).
European Patent Office, “Extended European Search Report,” issued in connection with European Patent Application No. 15178375.0, dated Jan. 7, 2016, 8 pages.
Galinski et al., “Results of the Gust Resistant MAV Programme,” 28th International Congress of the Aeronautical Sciences, 2012, 10 pages.
State of Israel Patent Office, “Notification of Defects in Patent Application,” issued in connection with Israel Patent Application No. 240141, dated May 23, 2019, 8 pages.
China National Intellectual Property Administration, “Notification of Second Office Action,” issued in connection with Chinese Patent Application No. 201410446066.8, dated May 13, 2019, 8 pages.
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 14/801,479, dated Jul. 10, 2019, 10 pages.
United States Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” issued in connection with U.S. Appl. No. 14/801,479, dated May 9, 2019, 22 pages.
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 14/801,479, dated Nov. 2, 2018, 57 pages.
United States Patent and Trademark Office, “Requirement for Restriction and/or Election.” issued in connection with U.S. Appl. No. 14/801,479, dated May 23, 2018, 13 pages.
National Intellectual Property Administration, PRC, “Notification of Third Office Action,” issued in connection with Chinese Patent Application No. 2015104460668, dated Aug. 13, 2019, 5 pages.
Related Publications (1)
Number Date Country
20200102075 A1 Apr 2020 US
Provisional Applications (1)
Number Date Country
62030024 Jul 2014 US
Divisions (1)
Number Date Country
Parent 14801479 Jul 2015 US
Child 16523755 US