SYSTEMS AND DEVICES FOR REMOTELY OPERATED UNMANNED AERIAL VEHICLE REPORT-SUPPRESSING LAUNCHER WITH PORTABLE RF TRANSPARENT LAUNCH TUBE

Information

  • Patent Application
  • 20230322407
  • Publication Number
    20230322407
  • Date Filed
    June 15, 2023
    a year ago
  • Date Published
    October 12, 2023
    a year ago
Abstract
An unmanned aerial vehicle (UAV) launch tube that comprises at least one inner layer of prepreg substrate disposed about a right parallelepiped aperture, at least one outer layer of prepreg substrate disposed about the right parallelepiped aperture, and one or more structural panels disposed between the at least one inner layer of prepreg substrate and the at least one outer layer of prepreg substrate. An unmanned aerial vehicle (UAV) launch tube that comprises a tethered sabot configured to engage a UAV within a launcher volume defined by an inner wall, the tethered sabot dimensioned to provide a pressure seal at the inner wall and tethered to the inner wall, and wherein the tethered sabot is hollow having an open end oriented toward a high pressure volume and a tether attached within a hollow of the sabot and attached to the inner wall retaining the high pressure volume or attach to the inner base wall. A system comprising a communication node and a launcher comprising an unmanned aerial vehicle (UAV) in a pre-launch state configured to receive and respond to command inputs from the communication node.
Description
TECHNICAL FIELD

Embodiments include launch tubes and canisters, report-suppressing launch tubes, and sabots for an unmanned aerial vehicle (UAV). Embodiments also pertain to systems comprising one or more UAVs, and to a system comprising a command node and a launcher containing a UAV in a pre-launch state configured to receive command signals from the command node.


BACKGROUND

Typically UAVs are shipped to a launch site in an unassembled state. At the site they are assembled, tested, and then launched. Launching is typically executed by hand, by an elastic tether, a powered wench, from a moving vehicle, or some combination thereof. Such methods can be time consuming and/or cumbersome. Once launched, a UAV may receive uplinks and may be guided by a human-in-the-loop, a human intermittently up-linking course corrections, e.g., via supervisory control, or by a preloaded intercept/strike point in combination with an onboard flight path guidance generator and outputs of inertial sensors and/or from a Global Positioning System (GPS) receiver.


SUMMARY

Embodiments may include articles such as an unmanned aerial vehicle (UAV) launch tube comprising: (a) at least one inner layer of prepreg substrate disposed about a right parallelepiped aperture; (b) at least one outer layer of prepreg substrate disposed about the right parallelepiped aperture; and (c) one or more structural panels disposed between the at least one inner layer of prepreg substrate and the at least one outer layer of prepreg substrate. The at least one inner layer of prepreg substrate may comprise epoxy prepreg Kevlar™ or other light weight composites. The at least one outer layer of prepreg substrate may comprise epoxy prepreg Kevlar™ or other light weight composites. The one or more structural panels may comprise balsawood or a light weight composite. In some embodiments, the one or more structural panels may comprise four structural panels, where each panel comprises a cylindrical segment, and each panel has a planar surface defined by a chord length and a cylindrical height. Each proximate planar surface may be disposed orthogonally relative to one another, each structural panel having a first lateral edge and a second lateral edge perpendicular to the chord length, where the first lateral edge of a first structural panel is proximate to, but not contacting, a first lateral edge of a second structural panel. The second lateral edge of the first structural panel may be proximate to, but not contacting, a first lateral edge of a third structural panel. The first lateral edge of a fourth structural panel may be proximate to, but not contacting, a second lateral edge of a second structural panel. The second lateral edge of the fourth structural panel may be proximate to, but not contacting, a second lateral edge of a third structural panel, where the planar surfaces of each of the four structural panels may be aligned with a launch tube centerline. In addition, each of the four structural panels may be disposed between the inner layer of epoxy prepreg substrate and the outer layer of epoxy prepreg substrate. Embodiments include articles such as an unmanned aerial vehicle (UAV) launch tube configured for report suppression comprising a structural element configured to engage the UAV within a launcher volume defined by an inner wall. The article may be dimensioned to provide a pressure seal at the inner wall and tethered to the inner wall. The structural element may have a hollow, or cavity, having an open end oriented toward a high pressure volume and a tether attached within a hollow or cavity of the article and may be attached to the inner wall retaining the high pressure volume.


Additional embodiments may include methods and UAV systems comprising: (a) a communications node; and (b) a launcher comprising a UAV configured to receive, in a pre-launch state, command inputs from the communications node. In some embodiments, the UAV in a pre-launch state is further configured to transmit to a communications node UAV status data responsive to a received query signal. In some embodiments, the RF antenna of the UAV is contained within the launcher volume. In some embodiments, the launch propulsion system is configured to receive RF signals.





BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, and in which:



FIG. 1 is a top-side perspective view of an exemplary launch tube embodiment;



FIG. 2 is a bottom-side perspective view of a portion of an exemplary launch tube embodiment;



FIG. 3 is cross-sectional view of an exemplary launch tube embodiment;



FIG. 4 is an exemplary depiction of a launch tube configured as a UAV carrying case embodiment of the present invention;



FIG. 5 is an exemplary depiction of a launch tube configured as a UAV carrying case embodiment of the present invention;



FIG. 6 is an exemplary depiction of a launch tube configured as a UAV carrying case embodiment with support struts and footing deployed;



FIG. 7 is a top-side perspective view of an exemplary tethered sabot embodiment of the present invention;



FIG. 8 is a top view of an exemplary tethered sabot embodiment of the present invention;



FIG. 9 is a cross-sectional view of an exemplary tethered sabot embodiment of the present invention;



FIGS. 10A-10E depict an exemplary UAV launch using a tethered sabot embodiment of the present invention;



FIGS. 11A-11B depict, in a cross-sectional view of the distal end of a lunch tube, an exemplary UAV launch using a tethered sabot embodiment of the present invention;



FIG. 12A is a bottom-side perspective view of an exemplary UAV in a pre-launch state;



FIG. 12B depicts an exemplary UAV with its airfoils deployed and its pusher propeller rotating;



FIG. 13 is a bottom-side perspective view of a portion of an exemplary launch tube embodiment;



FIG. 14 depicts an exemplary functional block diagram of the UAV processing and guidance and control subsystem; and



FIG. 15 is a top-level system architecture of a system embodiment.





DETAILED DESCRIPTION


FIG. 1 is a top-side perspective view of an exemplary launch tube 100 embodiment. The top, or open end 110, of the exemplary launch tube presents a square-shaped aperture having rounded corners. Disposed between an outer layer of prepreg substrate 120 and an inner layer of prepreg substrate 130 are four structural panels 141-144.



FIG. 2 is a bottom-side perspective view of a portion of an exemplary launch tube embodiment 200. The bottom, or closed end 210, of the exemplary launch tube presents an end 220 curved about an axis collinear with a first footing pivot point protrusion 230 where a second footing pivot point protrusion is opposite the first footing pivot point protrusion 230, but not shown in the figure.



FIG. 3 is a cross-sectional view 300 of the exemplary launch tube embodiment of FIG. 1 showing four structural panels 141-144 disposed about a launch tube centerline. A non-cylindrical UAV may be placed and launched from such a volume. Each panel is shown having an outer surface curvature 311 representative of a radius of curvature 322 greater than the distance 323 from the outer surface 350 to the launch tube centerline 360. Each panel 141-144 is shown having a planar inner surface 312 representative of a chord length 313. Accordingly, an end face 314 of each panel 141-144 in the present cross-sectional view is a circular segment. Each panel is shown disposed between an inner layer of prepreg substrate 370 and an outer layer of prepreg substrate 380. The panels are shown disposed apart from one another, with there being space 390 between the lateral edges 318, 319 of the panels. Accordingly, the inner layer of prepreg substrate 370 and the outer layer of prepreg substrate 380 contact one another at the corners 301-304 of the right parallelepiped-shaped volume 305. The outer layer of prepreg substrate 380 defines in cross-sectional view, a substantially ovoid-shaped outside perimeter. In some embodiments the inner layer 370 and outer layer 380 may comprise epoxy prepreg Kevlar™ or a composite material, or combinations of both, and the structural panels may comprise balsawood or a light weight composite material, or combination of both.



FIG. 4 is an exemplary depiction of a launch tube configured as a UAV carrying case 400 embodiment. A footing 410 is shown rotatably attached to the launch tube 405 via a footing pivot point protrusion 230. A first strut or leg 420 is shown rotatably attached to the launch tube 405 proximate to the top 110 of the launch tube. A second strut or leg is disposed opposite the first strut and is not shown in this figure. A cap 430 is shown covering the otherwise open end of the launch tube and is shown restrained by a circumferential strap 431.



FIG. 5 is an exemplary depiction of a launch tube configured as a UAV carrying case embodiment in a partially deployed state. That is, the cap 430 is shown removed, exposing the open end of the launch tube that may have an optional membrane seal 540 as shown. The seal 540 may be a frangible film applied to repel sand, soil, moisture, and/or grit from entering the launch tube during pre-launch preparations. The footing 410 is shown partially rotated away from the launch tube and the first strut or leg 420 is shown partially rotated into a support position.



FIG. 6 is an exemplary depiction of a launch tube 600 configured as a UAV carrying case embodiment with support struts 420 and footing 410 deployed. The use of the term “tube” is done so with the intent to indicate a volume from which a UAV may be launched and not to limit the shape of the volume to a cylindrical tube. The angle 610 of the pair of struts or pair of legs may be adjusted to accommodate a desired launch angle 601 relative to local level 602. Likewise, the angle 620 between the launch tube and the footing may be adjusted to accommodate the desired launch angle 601. In some embodiments, the pair of struts or pair of legs 420 may comprise segments of differing diameters allowing for a telescoping of the distal segment 422 into and out of the proximal segment 421. In these embodiments, the overall length of the legs may be adjusted, either to accommodate uneven local terrain, and to accommodate a desired launch angle 601, or both. The footing 410 may be sized to receive the down force from a boot and/or a mass to further enhance the stiction between the lower surface of the footing and the local ground surface 602. The top of the launch tube 630 may include a frangible membrane to protect the internal launcher volume from grit, sand, moisture and the effects of weather. Once the launcher is positioned on a surface, the launcher 600 may be remotely controlled for purposes of uploading mission information to the UAV while the UAV is in a pre-launch state and for purposes of receiving UAV status information.


Embodiments include an unmanned aerial vehicle (UAV) launch tube that may comprise a tethered sabot configured to engage a UAV within a launcher volume defined by an inner wall, the tethered sabot dimensioned to provide a pressure seal at the inner wall, and tethered to the inner wall. In some embodiments, the tethered sabot may be hollow having an open end oriented toward a high pressure volume and a tether attached within a hollow of the sabot and attached to the inner wall retaining the high pressure volume.


For a launcher having a right parallelepiped aperture, an exemplary tethered sabot 700 embodiment as depicted in FIG. 7 may be used. The sabot may be made of carbon fiber, e.g., a prepreg carbon fiber shaped over a form and cured to yield a hollow article, open at one end. The sabot may have a channel 710 for receiving a pusher propeller assembly of a UAV. The sabot may also have a depression 720 for receiving gas outside of the volume provided by the hollow. The sabot is shown depicting an end portion 730 of a structural element that may span the width of the sabot to provide for a structural attachment for a tether. A portion of a tether 740 is shown extending from the hollow of the sabot.



FIG. 8 is a top view of an exemplary tethered sabot 700 embodiment. The structural element 810 may be a rod, and may span the width of the sabot 700. A loop portion 820 of the tether may engage the structural element 810. The tether 740 may be silicone prepreg, braided Kevlar™ where an end of the tether 740 may be tucked within the braiding of the tether 740 after looping the structural element 810 and further cured.



FIG. 9 is a cross-sectional view of the sabot 700 taken from the top view of FIG. 8 depicting the tether 740 engaging the structural element 810 within the hollow 910 of the sabot 700.



FIG. 10A illustrates a cross-sectional view of a loaded launcher 1010, such as the launcher depicted in FIGS. 1 and 2; loaded with a UAV 1020 such as the UAV depicted in FIG. 3. In this example, the launcher 1010 is shown having an optional frangible seal 1030. Two gas-generating canisters 1041, 1042 are shown disposed within the aft volume 1001 of the launcher 1010. An exemplary tethered sabot 1050 is shown disposed between the gas-generating canisters 1041, 1042 and the UAV 1020.



FIG. 10B illustrates, in the cross-sectional view of FIG. 10A, a first gas-generating canister 1041 increasing the pressure—as depicted by the smoke cloud 1002—within the volume 1001 between the inner aft wall 1011 of the launcher 1010 and the sabot 1050. The tether 1060 may be attached to the inner base wall 1013 via a tether reel or winding element 1014. Relative to FIG. 10A, the sabot 1050 is shown displaced along the launch tube—in this example a right parallelepiped volume—and moving with it the UAV 1020. The UAV is shown breaking the frangible seal 1030 and beginning to exit the launcher 1010.



FIG. 10C illustrates, in the cross-sectional view of FIG. 10A, the second gas-generating canister 1042 increasing, or sustaining, the pressure (as depicted by the second smoke cloud 1003) within the volume between the inner aft wall 1012 of the launcher 1010 and the sabot 1050. The sabot 1050 is shown displaced further along the launch tube, the tether 1060 is shown in a payout length, and, moved with the sabot 1050, the UAV 1020 is shown substantially outside of the launcher.



FIG. 10D illustrates, in the cross-sectional view of FIG. 10A, the sabot 1050 fully displaced within the launch tube, constrained from further travel by the tether 1060, and retaining the gas within the launcher volume.



FIG. 10E illustrates, in the cross-sectional view of FIG. 10A, the sabot 1050 fully displaced within the launch tube, constrained from further travel by the tether 1060, and retaining the gas within the launcher volume and allowing the seeping 1090 of gas from the launcher volume into the surrounding atmosphere.



FIG. 11A depicts, a cross-sectional view of the distal, an unsealed, end of a lunch tube 1100, as the sabot 1050 approaches full payout as depicted in FIG. 10D. In some embodiments using hot or warm gas generators, the sabot 1050 travels approximately no further than the location depicted in FIG. 11A, and a seepage of gas to atmosphere is around the sabot as the sabot may shrink in a cooling cycle from having been heated by the gas. In some embodiments using warm or cool gas generators, the sabot 1050 may travel to partially extend from the rim 1120 of the launcher (FIG. 11B) where gas may seep 1110 from the side depression 720 once the sabot lip 701 has cleared the launcher rim 1120. By retaining the sabot 1050 via the tether 1060, the launcher retains, for a brief period, a substantial portion of the pressure waves, i.e., the report, and heat produced by rapid gas generation. Post-launch, the launcher diffuses the pressure from the launcher via seepage about the sabot 1050.


In some embodiments, the sabot 1050 may expand out to contact the inner wall or walls of the launcher due to the pressure exerted on the interior of the sabot 1050 by the gas from the gas generators. This expansion can cause, or at least facilitate, the formation of a seal between the sabot 1050 and the inner wall or walls and in doing so prevent or limit the passage of gas around the sabot 1050 during its movement along the tube. In certain embodiments, the sabot may be configured to form gaps between the sabot and the inner wall or inner walls of the launcher. The size of such gaps may be set to provide a desired amount of gas leakage. In some embodiments, the sabot 1050 may be sized to allow enough gas leakage to prevent the launcher from becoming too hot from containing the launch gases such that the structural integrity of the launcher is compromised or breached. Accordingly, sabot 1050 embodiments may be sized to limit gas leakage to limit the sound propagation of the sonic waves generated during the launch process.



FIG. 12A depicts, in a bottom-side perspective view, an exemplary UAV in a pre-launch state 1200, i.e., with its wing 1210 and tail surfaces 1220 folded beneath the fuselage of the vehicle. Also shown is a propeller hub 1230 about which a propeller may be rotatably mounted. The air vehicle may include a radio frequency (RF) antenna 1231 conformal with or extending from the vehicle. Whether the tube volume is a right cylinder, a right parallelepiped, or some other shape, the cross-section or cross-sections of the UAV may be insufficient to maintain an air-tight fit between the vehicle and the inner walls of the launcher. Accordingly, for launches based on gas pressure, a sabot may be disposed between the gas source and the UAV. FIG. 12B depicts an exemplary UAV in a launched state 1201 with its airfoils 1210, 1220 deployed and its pusher propeller 1232 rotating.



FIG. 13 is a side elevational view of the air vehicle 1300 embodiment loaded into a forward portion of a launcher 1310. The aft portion of the launcher 1320 is shown having a pair of gas-generating canisters 1331, 1332 and may include an RF antenna 1333 and receiver unit 1334, and a power source 1336, such as a battery for powering the launcher. In some embodiments the power source 1336 can also power the UAV 1300 while it is in the launcher 1310, allowing for maximum battery life for the UAV's battery after leaving the launcher 1310. Balsawood and epoxy prepreg Kelvar™ are examples of structural elements having high RF permeability. Accordingly, RF antenna and receiver elements of the UAV and/or RF antenna and receiver elements of the launch propulsion unit may receive RF commands from a command node with negligible signal attenuation due to the launcher structure.



FIG. 14 depicts an exemplary functional block diagram of the UAV processing and guidance and control subsystem 1400 where the guidance sensor 1414 provides information about the external environment pertaining to seeking processing of a seeker processing 1420. A guidance sensor 1414, and more generally, a guidance sensor suite, may include a passive and/or active radar subsystem, an infrared detection subsystem, an infrared imaging subsystem, a visible light imaging subsystem such as a video camera-based subsystem, an ultraviolet light detection subsystem, and combinations thereof. The seeker processing 1420 may include both image processing and target tracking processing, and target designation or re-designation input 1421 that may be received from an uplink receiver 1435 and/or as an output of a guidance process 1430. The image processing and/or target tracking information 1422 may be transmitted via a downlink transmitter 1423, which may be a part of an uplink/downlink transceiver. The guidance processor 1430, in executing instructions for guidance processing, may take in the target information 1424 from the seeker processing 1420, and UAV flight status information such as position, velocity and attitude from the GPS receiver 1431, and gyroscopes and accelerometers 1432, if any. Once in flight, the guidance processor 1430, to receive reconnaissance waypoints and/or surveillance optimizing trajectories, may reference a memory store 1433. For system embodiments, the guidance process 1430 may receive, by way of an external data port 1434, e.g., during a pre-launch phase, or by way of an uplink receiver 1435, e.g., during a post-launch phase, receive and/or upload reconnaissance waypoints and/or surveillance optimizing trajectories. The guidance processor 1430, as part of executing instructions for determining flight path, a trajectory, or a course steering angle and direction, may reference the waypoint and/or surveillance optimizing trajectory information, particularly when not in a terminal homing mode. The guidance processor 1430 may receive a command via an uplink receiver 1435 to set an initial post-launch mode or flight plan. The uplink receiver 1435 may receive commands, target data, and or flight plan information from a communications node while the UAV is in a pre-launch state.


An example of a terminal homing mode may be proportional navigation with a gravity bias for strike sub-modes of the terminal homing mode, and an acceleration bias for aerial intercept sub-modes of the terminal homing mode. The guidance processing 1430 and autopilot processing 1440 may execute instructions to effect a bank-to-turn guidance, for example, in an elevon embodiment, to redirect the air vehicle by re-orienting its velocity vector. For example, one or more control surfaces may be re-oriented via one or more control surface actuators 1450 causing forces and torques to reorient the air vehicle and the portion of its linear acceleration that is orthogonal to its velocity vector. The portion of the linear acceleration of the air vehicle that is along the velocity vector is greatly affected by aerodynamic drag, and the linear acceleration may be increased via a motor processor 1460 and a propeller motor 1470. For embodiments with full three-axis control, additional control topologies may be implemented including skid-to-turn and other proportion-integral-differential guidance and control processing architectures as well. The seeker processing 1420, guidance processing 1430, motor processing 1460, and/or autopilot processing 1440 may be executed by a single microprocessor having addressable memory and/or the processing may be distributed to two or more microprocessors in distributed communication, e.g., via a data bus.



FIG. 15 is a top-level system architecture of a system 1500 embodiment. Ground vehicles 1501, aircraft 1502, spacecraft 1503, airborne surveillance or airborne communication nodes 1504, or ground, human-portable, communication nodes 1505 may transmit command signals via an RF link 1511-1515 to a launcher 1520 embodiment, that may be, for example, the embodiment depicted in FIG. 13. In some embodiments, the UAV, in a pre-launch state, may output along an RF link 1511-1515 to a requesting node 1501-1505, status information, e.g., battery levels, and the results of self-diagnostics. Launcher embodiments provide for a self-contained RF node via the UAV contained in the launcher. For example, the UAV may be placed in a standby mode, and remain responsive to a received RF signal that may command a full power-up, and thereafter the UAV in the launcher may be ready to be committed to launch—e.g., by an RF command of an offsite command node. The self-contained launcher-UAV may be deployed and left at a prospective launch site for a protracted period of time, and thereafter may be powered up and launched responsive to one or more command signals from an offsite or otherwise remotecommand node.


It is contemplated that various combinations and/or sub-combinations of the specific features and aspects of the above embodiments may be made and still fall within the scope of the invention. Accordingly, it should be understood that various features and aspects of the disclosed embodiments may be combined with or substituted for one another in order to form varying modes of the disclosed invention. Further it is intended that the scope of the present invention herein disclosed by way of examples should not be limited by the particular disclosed embodiments described above.

Claims
  • 1. A method comprising: receiving, by a receiver disposed within a launcher, wireless communication via one or more radio-frequency (RF) signals received wirelessly through a launcher wall of the launcher, wherein the launcher wall comprises an RF permeable material; andcommanding, by the launcher, an unmanned aerial vehicle (UAV) disposed within the launcher to enter a standby mode while remaining responsive to received RF signal commands for a full power-up.
  • 2. The method of claim 1, wherein the command the enter the standby mode provides a self-contained launcher-UAV configured to be deployed and left at a prospective launch site for a protracted period of time.
  • 3. The method of claim 1, wherein the UAV is configured to be powered up and launched responsive to one or more command signals from an offsite node.
  • 4. The method of claim 3, further comprising: transmitting, by a transmitter disposed within the launcher, wireless communication via one or more RF signals, based on the offsite node requesting status information while in a pre-launch state, wherein the status information is associated with the UAV.
  • 5. The method of claim 1, wherein the wireless communication via one or more RF signals is transmitted from at least one of: a ground vehicle, an aircraft, a spacecraft, an airborne surveillance node, an airborne communication node, and a ground communication node.
  • 6. The method of claim 1, wherein the received one or more RF signals are received by an RF antenna disposed within the launcher.
  • 7. The method of claim 1, further comprising: transmitting, by an external communications node, the one or more RF signals received by the receiver disposed within the launcher.
  • 8. The method of claim 1, wherein the one or more RF signals received by the receiver comprise at least one of: a reconnaissance waypoint information, a surveillance optimizing trajectory information, a target data, and a flight plan information.
  • 9. The method of claim 1, wherein the received RF signal commands for a full power-up configures the UAV in the launcher to be ready to be committed to launch.
  • 10. The method of claim 1, further comprising: generating gas by one or more gas generating canisters during a launch of the UAV disposed within the launcher; andretaining the generated gas within the launcher after the launch of the UAV.
  • 11. A system comprising: a launcher having a launcher wall, the launcher wall having radio-frequency (RF) permeability;an unmanned aerial vehicle (UAV) disposed within the launcher; anda receiver disposed within the launcher, the receiver receiving wireless communication via one or more RF signals received wirelessly through the launcher wall.
  • 12. The system of claim 11, wherein the launcher provides a self-contained launcher-UAV configured to be deployed and left at a prospective launch site for a protracted period of time.
  • 13. The system of claim 11, wherein the UAV commands a full power-up responsive to the received wireless communication.
  • 14. The system of claim 13, wherein the UAV commits to a launch responsive to the received wireless communication.
  • 15. The system of claim 11, wherein the wireless communication via one or more RF signals is transmitted from at least one of: a ground vehicle, an aircraft, a spacecraft, an airborne surveillance node, an airborne communication node, and a ground communication node.
  • 16. The system of claim 11 further comprising: a transmitter disposed within the launcher, the transmitter transmitting wireless communication via one or more RF signals transmitted wirelessly through the launcher wall.
  • 17. The system of claim 11, wherein the receiver further comprises an RF antenna disposed within the launcher.
  • 18. The system of claim 11, wherein the receiver is in communication with an external communications node, in a pre-launch state, to wirelessly receive one or more RF signals from the external communications node.
  • 19. The system of claim 11, wherein the received one or more RF signals comprise at least one of: a reconnaissance waypoint information, a surveillance optimizing trajectory information, a target data, and a flight plan information.
  • 20. The system of claim 11, wherein the launcher further comprises: a membrane seal disposed over an open end of the launcher preventing outside elements from entering the launcher prior to launch; andone or more gas generating canisters disposed within the launcher, wherein the one or more gas generating canisters generate gas during a launch of the UAV disposed within the launcher, and wherein the generated gas is retained within the launcher after the launch of the UAV.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of patent application Ser. No. 17/728,603, filed Apr. 25, 2022, which is a continuation of patent application Ser. No. 16/920,578, filed Jul. 3, 2020, which issued as U.S. Pat. No. 11,319,087 on May 3, 2022, which is a continuation of patent application Ser. No. 16/574,344, filed Sep. 18, 2019, which issued as U.S. Pat. No. 10,703,506 on Jul. 7, 2020, which is a continuation of patent application Ser. No. 16/137,196 filed Sep. 20, 2018, which issued as U.S. Pat. No. 10,450,089 on Oct. 22, 2019, which is a continuation of patent application Ser. No. 14/887,675 filed Oct. 20, 2015, which issued as U.S. Pat. No. 10,124,909 on Nov. 13, 2018, which is a continuation of patent application Ser. No. 13/234,044, filed Sep. 15, 2011, which issued as U.S. Pat. No. 9,187,184 on Nov. 17, 2015, which is a continuation of patent application Ser. No. 13/229,377, filed Sep. 9, 2011, which issued as U.S. Pat. No. 8,505,430 on Aug. 13, 2013, which is a continuation of International Application No. PCT/US2010/048313, filed Sep. 9, 2010, which claims priority to and the benefit of U.S. Provisional Patent Application Ser. No. 61/240,996 filed Sep. 9, 2009, U.S. Provisional Patent Application Ser. No. 61/240,987 filed Sep. 9, 2009, and U.S. Provisional Patent Application Ser. No. 61/241,001 filed Sep. 9, 2009, all of which are hereby incorporated herein by reference in their entirety for all purposes.

Provisional Applications (3)
Number Date Country
61241001 Sep 2009 US
61240987 Sep 2009 US
61240996 Sep 2009 US
Continuations (8)
Number Date Country
Parent 17728603 Apr 2022 US
Child 18210418 US
Parent 16920578 Jul 2020 US
Child 17728603 US
Parent 16574344 Sep 2019 US
Child 16920578 US
Parent 16137196 Sep 2018 US
Child 16574344 US
Parent 14887675 Oct 2015 US
Child 16137196 US
Parent 13234044 Sep 2011 US
Child 14887675 US
Parent 13229377 Sep 2011 US
Child 13234044 US
Parent PCT/US2010/048313 Sep 2010 US
Child 13229377 US