The present disclosure relates, in general, to aircraft configured to convert between thrust-borne lift in a VTOL orientation and wing-borne lift in a biplane orientation and, in particular, to aircraft configured to autonomously transport and deploy a payload to a desired location.
It is often desirable to deploy a payload such as food, water, medicine or other supplies to a remote, distant, dangerous or otherwise inaccessible location during military operations, disaster relief, humanitarian efforts or other missions. Fixed wing aircraft are capable of delivering a payload over a long range in a short time. It has been found, however, that a majority of the locations requiring such payload deployment lack suitable conditions for landing a fixed wing aircraft. To overcome this runway requirement, attempts have been made to use fixed wing aircraft in airdrop operations in which a payload is released during flight for drop to the ground with or without the aid of a parachute. It has been found, however, that high altitude airdrops require significant preplanning and lack suitable precision for certain payload deployments rendering such operations ineffective.
Helicopters are highly versatile for use in congested, isolated or remote areas where fixed wing aircraft may be unable to take off or land. In addition, helicopters are able to execute payload deployment operations in stationary flight over a desired location. For example, payload deployment may be accomplished using a hoist or winch assembly that is operable to raise and/or lower the payload while the helicopter remains in a stable hover. It has been found, however, that helicopters lack the desired speed and range necessary for certain payload deployment operations. In addition, particularly for smaller aircraft, it has been found that aircraft mounted hoist assemblies have a significant weight penalty. Further, both fixed wing aircraft and helicopters typically require a pilot that may be put in harm's way during some payload deployment operations. Accordingly, a need has arisen for improved aircraft and aircraft systems operable to autonomously transport and deploy a payload to a desired location.
In a first aspect, the present disclosure is directed to an aircraft operable to transition between thrust-borne lift in a VTOL orientation and wing-borne lift in a biplane orientation. The aircraft has an airframe that includes first and second wings with first and second pylons coupled therebetween. A distributed thrust array is coupled to the airframe. The thrust array includes a plurality of propulsion assemblies coupled to the first wing and a plurality of propulsion assemblies coupled to the second wing. A cargo pod is coupled between the first and second pylons. The cargo pod is rotatable between a loading configuration substantially perpendicular to the wings and a transportation and deployment configuration substantially parallel to the wings. A flight control system is configured to independently control each of the propulsion assemblies and to autonomously deploy a payload from the cargo pod at a desired location. In the loading configuration, the cargo pod is adapted to receive the payload through a substantially horizontally oriented front opening. In the transportation and deployment configuration, the cargo pod is adapted to deploy the payload through a substantially horizontally oriented aft opening.
In certain embodiments, the cargo pod may have an aerodynamic outer shape. In some embodiments, the cargo pod may be a cargo enclosure having a front hatch operable to cover and uncover the front opening and an aft hatch operable to cover and uncover the aft opening. In certain embodiments, the cargo pod may be an open air cargo pod wherein the front opening and the aft opening remain uncovered. In some embodiments, the front opening and the aft opening may be substantially normal to one another. In certain embodiments, the front opening and the aft opening may intersect. In some embodiments, the cargo pod may include a payload support assembly that secures the payload in the cargo pod for transportation. For example, such a payload support assembly may include a lock system, a gate system and/or a variable payload cavity configurable based upon the size of the payload.
In certain embodiments, the cargo pod may include a payload deployment assembly configured to release the payload from the cargo pod responsive to the flight control system. For example, the payload deployment assembly may include a rail system, a cable system such as a retractable cable system or an expendable cable system, a payload self-orienting system and/or a gate system. In some embodiments, the flight control system may be configured to autonomously deploy the payload from the cargo pod at the desired location when the aircraft is positioned on a surface in a tailsitter orientation.
In a second aspect, the present disclosure is directed to an aircraft operable to transition between thrust-borne lift in a VTOL orientation and wing-borne lift in a biplane orientation. The aircraft has an airframe that includes first and second wings with first and second pylons coupled therebetween. A distributed thrust array is coupled to the airframe. The thrust array includes a plurality of propulsion assemblies coupled to the first wing and a plurality of propulsion assemblies coupled to the second wing. A cargo pod is coupled between the first and second pylons. The cargo pod is rotatable between a loading configuration substantially perpendicular to the wings and a transportation and deployment configuration substantially parallel to the wings. A flight control system is configured to independently control each of the propulsion assemblies and to autonomously deploy a payload from the cargo pod at a desired location. The cargo pod has a payload support assembly and a payload deployment assembly. The payload support assembly includes a lock system configured to the secure the payload in the cargo pod. The payload deployment assembly includes a cable system configured to release the payload from the cargo pod responsive to the flight control system.
In a third aspect, the present disclosure is directed to an aircraft operable to transition between thrust-borne lift in a VTOL orientation and wing-borne lift in a biplane orientation. The aircraft has an airframe that includes first and second wings with first and second pylons coupled therebetween. A distributed thrust array is coupled to the airframe. The thrust array includes a plurality of propulsion assemblies coupled to the first wing and a plurality of propulsion assemblies coupled to the second wing. A cargo pod is coupled between the first and second pylons. The cargo pod is rotatable between a loading configuration substantially perpendicular to the wings and a transportation and deployment configuration substantially parallel to the wings. A flight control system is configured to independently control each of the propulsion assemblies and to autonomously deploy a payload from the cargo pod at a desired location. The cargo pod has a payload support assembly and a payload deployment assembly. The payload support assembly includes a variable payload cavity configurable based upon the size of the payload and configured to the secure the payload in the cargo pod. The payload deployment assembly includes a gate system configured to release the payload from the cargo pod responsive to the flight control system.
For a more complete understanding of the features and advantages of the present disclosure, reference is now made to the detailed description along with the accompanying figures in which corresponding numerals in the different figures refer to corresponding parts and in which:
While the making and using of various embodiments of the present disclosure are discussed in detail below, it should be appreciated that the present disclosure provides many applicable inventive concepts, which can be embodied in a wide variety of specific contexts. The specific embodiments discussed herein are merely illustrative and do not delimit the scope of the present disclosure. In the interest of clarity, not all features of an actual implementation may be described in the present disclosure. It will of course be appreciated that in the development of any such actual embodiment, numerous implementation-specific decisions must be made to achieve the developer's specific goals, such as compliance with system-related and business-related constraints, which will vary from one implementation to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming but would be a routine undertaking for those of ordinary skill in the art having the benefit of this disclosure.
In the specification, reference may be made to the spatial relationships between various components and to the spatial orientation of various aspects of components as the devices are depicted in the attached drawings. However, as will be recognized by those skilled in the art after a complete reading of the present disclosure, the devices, members, apparatuses, and the like described herein may be positioned in any desired orientation. Thus, the use of terms such as “above,” “below,” “upper,” “lower” or other like terms to describe a spatial relationship between various components or to describe the spatial orientation of aspects of such components should be understood to describe a relative relationship between the components or a spatial orientation of aspects of such components, respectively, as the device described herein may be oriented in any desired direction. As used herein, the term “coupled” may include direct or indirect coupling by any means, including moving and/or non-moving mechanical connections.
Referring to
In the illustrated embodiment, aircraft 10 has an airframe 12 including wings 14, 16 each having an airfoil cross-section that generates lift responsive to the forward airspeed of aircraft 10. Wings 14, 16 may be formed as single members or may be formed from multiple wing sections. The outer skins for wings 14, 16 are preferably formed from high strength and lightweight materials such as fiberglass, carbon, plastic, metal or other suitable material or combination of materials. As best seen in
Aircraft 10 includes a cargo pod 22 that is coupled between pylons 18, 20. As discussed herein, cargo pod 22 is rotatable between a loading configuration in which cargo pod 22 is substantially perpendicular to wings 14, 16 and a transportation and deployment configuration in which cargo pod 22 is substantially parallel to wings 14, 16, as discussed herein. Cargo pod 22 has an aerodynamic shape with a forward end 22a and an aft end 22b with a cargo pod chord length extending therebetween, two sides 22c, 22d with a cargo pod span length extending therebetween and a front 22e and back 22f with a cargo pod thickness extending therebetween. The aerodynamic shape of cargo pod 22 is configured to minimize drag during high speed forward flight. Cargo pod 22 is preferably formed from high strength and lightweight materials such as fiberglass, carbon, plastic, metal or other suitable material or combination of materials. In the illustrated embodiment, cargo pod 22 is rotatably coupled to pylon 18 at side 22c and is rotatably coupled to pylon 20 at side 22d. As best seen in
One or more of cargo pod 22, wings 14, 16 and/or pylons 18, 20 may contain flight control systems, energy sources, communication lines and other desired systems. For example, as best seen in
One or more of cargo pod 22, wings 14, 16 and/or pylons 18, 20 may contain one or more of electrical power sources depicted as a plurality of batteries 32 in pylon 20, as best seen in
Cargo pod 22, wings 14, 16 and/or pylons 18, 20 also contain a communication network that enables flight control system 30 to communicate with the distributed thrust array of aircraft 10. In the illustrated embodiment, aircraft 10 has a two-dimensional distributed thrust array that is coupled to airframe 12. As used herein, the term “two-dimensional thrust array” refers to a plurality of thrust generating elements that occupy a two-dimensional space in the form of a plane. A minimum of three thrust generating elements is required to form a “two-dimensional thrust array.” A single aircraft may have more than one “two-dimensional thrust array” if multiple groups of at least three thrust generating elements each occupy separate two-dimensional spaces thus forming separate planes. As used herein, the term “distributed thrust array” refers to the use of multiple thrust generating elements each producing a portion of the total thrust output. The use of a “distributed thrust array” provides redundancy to the thrust generation capabilities of the aircraft including fault tolerance in the event of the loss of one of the thrust generating elements. A “distributed thrust array” can be used in conjunction with a “distributed power system” in which power to each of the thrust generating elements is supplied by a local power system instead of a centralized power source. For example, in a “distributed thrust array” having a plurality of propulsion assemblies acting as the thrust generating elements, a “distributed power system” may include individual battery elements housed within the nacelle of each propulsion assembly.
The two-dimensional distributed thrust array of aircraft 10 includes a plurality of propulsion assemblies, individually denoted as 34a, 34b, 34c, 34d and collectively referred to as propulsion assemblies 34. In the illustrated embodiment, propulsion assemblies 34a, 34b are coupled at the wingtips of wing 14 and propulsion assemblies 34c, 34d are coupled at the wingtips of wing 16. By positioning propulsion assemblies 34a, 34b, 34c, 34d at the wingtip of wings 14, 16, the thrust and torque generating elements are positioned at the maximum outboard distance from the center of gravity of aircraft 10 located, for example, at the intersection of axes 10a, 10b, 10c. The outboard locations of propulsion assemblies 34 provide dynamic stability to aircraft 10 in hover and a high dynamic response in the VTOL orientation of aircraft 10 enabling efficient and effective pitch, yaw and roll control by changing the thrust, thrust vector and/or torque output of certain propulsion assemblies 34 relative to other propulsion assemblies 34.
Even though the illustrated embodiment depicts four propulsion assemblies, the distributed thrust array of aircraft 10 could have other numbers of propulsion assemblies both greater than or less than four. Also, even though the illustrated embodiment depicts propulsion assemblies 34 in a wingtip mounted configuration, the distributed thrust array of aircraft 10 could have propulsion assemblies coupled to the wings in other configurations such as a mid-span configuration. Further, even though the illustrated embodiment depicts propulsion assemblies 34 in a mid-wing configuration, the distributed thrust array of aircraft 10 could have propulsion assemblies coupled to the wings in a low wing configuration, a high wing configuration or any combination or permutations thereof. In the illustrated embodiment, propulsion assemblies 34 are variable speed propulsion assemblies having fixed pitch rotor blades and thrust vectoring capability. Depending upon the implementation, propulsion assemblies 34 may have longitudinal thrust vectoring capability, lateral thrust vectoring capability or omnidirectional thrust vectoring capability. In other embodiments, propulsion assemblies 34 may be single speed propulsion assemblies, may have variable pitch rotor blades and/or may be non-thrust vectoring propulsion assemblies.
Propulsion assemblies 34 may be independently attachable to and detachable from airframe 12 and may be standardized and/or interchangeable units and preferably line replaceable units providing easy installation and removal from airframe 12. The use of line replaceable propulsion units is beneficial in maintenance situations if a fault is discovered with one of the propulsion assemblies. In this case, the faulty propulsion assembly 34 can be decoupled from airframe 12 by simple operations and another propulsion assembly 34 can then be attached to airframe 12. In other embodiments, propulsion assemblies 34 may be permanently coupled to wings 14, 16.
Referring to
Flight control system 30 communicates via a wired communications network within airframe 12 with electronics nodes 36d of propulsion assemblies 34. Flight control system 30 receives sensor data from sensors 36e and sends flight command information to the electronics nodes 36d such that each propulsion assembly 34 may be individually and independently controlled and operated. For example, flight control system 30 is operable to individually and independently control the speed and the thrust vector of each propulsion system 36f. Flight control system 30 may autonomously control some or all aspects of flight operation for aircraft 10. Flight control system 30 is also operable to communicate with remote systems, such as a ground station via a wireless communications protocol. The remote system may be operable to receive flight data from and provide commands to flight control system 30 to enable remote flight control over some or all aspects of flight operation for aircraft 10. The autonomous and/or remote operation of aircraft 10 enables aircraft 10 to transport and deploy payload 24 to a desired location.
Aircraft 10 has a damping landing gear system that includes landing gear assembly 38a coupled to a lower or aft end of propulsion assembly 34a, landing gear assembly 38b coupled to a lower or aft end of propulsion assembly 34b, landing gear assembly 38c coupled to a lower or aft end of propulsion assembly 34c and landing gear assembly 38d coupled to a lower or aft end of propulsion assembly 34d. In the illustrated embodiment, each landing gear assembly 38 including a spring housing forming a spring chamber with a spring disposed therein and a plunger slidably coupled to the spring housing and movable between a compressed position and an extended position. The spring biases the plunger into the extended position during flight and the landing force compresses the plunger into the compressed position against the bias of the spring, thereby absorbing at least a portion of the landing force. In addition, the spring biasing force acting on the plunger when aircraft 10 is positioned on a landing surface generates a push-off effect to aid during takeoff maneuvers. In other embodiments, the landing gear assemblies may be passively operated pneumatic landing struts or actively operated telescoping landing struts. In still other embodiments, the landing gear assemblies may include wheels that enable aircraft 10 to taxi and perform other ground maneuvers. In such embodiments, the landing gear assemblies may provide a passive brake system or may include active brakes such as an electromechanical braking system or a manual braking system to facilitate parking during ground operations.
Referring additionally to
As best seen in
After vertical ascent to the desired elevation, aircraft 10 may begin the transition from thrust-borne lift to wing-borne lift. As best seen from the progression of
As best seen in
As aircraft 10 approaches the desired location, aircraft 10 may begin its transition from wing-borne lift to thrust-borne lift. As best seen from the progression of
Referring next to
Propulsion assembly 102b includes an electronics node 104b depicted as including controllers, sensors and one or more batteries. Propulsion assembly 102b also includes a propulsion system 106b and a two-axis gimbal 108b operated by one or more actuators 110b. Propulsion assembly 102c includes an electronics node 104c depicted as including controllers, sensors and one or more batteries. Propulsion assembly 102c also includes a propulsion system 106c and a two-axis gimbal 108c operated by one or more actuators 110c. Propulsion assembly 102d includes an electronics node 104d depicted as including controllers, sensors and one or more batteries. Propulsion assembly 102d also includes a propulsion system 106d and a two-axis gimbal 108d operated by one or more actuators 110d. A flight control system 112 is operably associated with each of propulsion assemblies 102a, 102b, 102c, 102d and is linked to the electronic nodes 104a, 104b, 104c, 104d by a fly-by-wire communications network depicted as arrows 114a, 114b, 114c, 114d. Flight control system 112 receives sensor data from and sends commands to propulsion assemblies 102a, 102b, 102c, 102d to enable flight control system 112 to independently control each of propulsion assemblies 102a, 102b, 102c, 102d, as discussed herein.
Referring additionally to
In the illustrated embodiment, flight control system 112 includes a command module 132 and a monitoring module 134. It is to be understood by those skilled in the art that these and other modules executed by flight control system 112 may be implemented in a variety of forms including hardware, software, firmware, special purpose processors and combinations thereof. Flight control system 112 receives input from a variety of sources including internal sources such as sensors 136, controllers/actuators 138, propulsion assemblies 102a, 102b, 102c, 102d and payload deployment assembly 144 as well as external sources such as remote system 124, global positioning system satellites or other location positioning systems and the like.
During the various operating modes of aircraft 100 including the vertical takeoff and landing flight mode, the hover flight mode, the forward flight mode and transitions therebetween, command module 132 provides commands to controllers/actuators 138. These commands enable independent operation of each propulsion assembly 102a, 102b, 102c, 102d including rotor speed, thrust vector and the like. Flight control system 112 receives feedback from controllers/actuators 138 and each propulsion assembly 102a, 102b, 102c, 102d. This feedback is processes by monitoring module 134 that can supply correction data and other information to command module 132 and/or controllers/actuators 138. Sensors 136, such as an attitude and heading reference system (AHRS) with solid-state or microelectromechanical systems (MEMS) gyroscopes, accelerometers and magnetometers as well as other sensors including positioning sensors, speed sensors, environmental sensors, fuel sensors, temperature sensors, location sensors and the like also provide information to flight control system 112 to further enhance autonomous control capabilities. Upon landing at the desired location, flight control system 112 is configured to cause payload deployment assembly 144 to deploy the payload from the cargo pod, as discussed herein.
Some or all of the autonomous control capability of flight control system 112 can be augmented or supplanted by remote flight control from, for example, remote system 124. Remote system 124 may include one or computing systems that may be implemented on general-purpose computers, special purpose computers or other machines with memory and processing capability. The computing systems may be microprocessor-based systems operable to execute program code in the form of machine-executable instructions. In addition, the computing systems may be connected to other computer systems via a proprietary encrypted network, a public encrypted network, the Internet or other suitable communication network that may include both wired and wireless connections. Remote system 124 communicates with flight control system 112 via a communication link 130 that may include both wired and wireless connections.
While operating remote control application 128, remote system 124 is configured to display information relating to one or more aircraft of the present disclosure on one or more flight data display devices 140. Display devices 140 may be configured in any suitable form, including, for example, liquid crystal displays, light emitting diode displays or any suitable type of display. Remote system 124 may also include audio output and input devices such as a microphone, speakers and/or an audio port allowing an operator to communicate with other operators or a base station. The display device 140 may also serve as a remote input device 142 if a touch screen display implementation is used, however, other remote input devices, such as a keyboard or joystick, may alternatively be used to allow an operator to provide control commands to an aircraft being operated responsive to remote control.
Referring additionally to
Cargo pod 22 includes a payload support assembly depicted as including a rail system 54 having oppositely disposed rails on the interior of sides 22c, 22d of cargo pod 22. In the illustrated embodiment, payload 24 includes a pair of opposite disposed detent assemblies 24a that are configured to snap into rail system 54, as best seen in
Once payload 24 is secured within cargo pod 22, cargo pod 22 may be rotated relative to pylons 18, 20 from the loading configuration to the transportation and deployment configuration wherein cargo pod 22 is oriented substantially parallel to wings 14, 16 and pylons 18, 20 such that the aft end 22b including an aft opening 22h are substantially horizontally oriented, as best seen in
As discussed herein, aircraft 10 may autonomously fly to and land in a tailsitter orientation at the desired location for payload deployment responsive to commands from flight control system 30. Once aircraft 10 has landed at the desired location, payload 24 may be released from the locking system of cargo pod 22 such as by releasing detent assemblies 24a from within the notches in rail system 54. Thereafter, cable system 56 may guild or control the descent of payload 24 down rail system 54, as best seen in
Payload 24 may now be placed on the ground in the desired orientation, as best seen in
For example, referring now to
As best seen in
Referring again to
As discussed herein, aircraft 10 may autonomously fly to and land in a tailsitter orientation at the desired location for payload deployment responsive to commands from flight control system 30. Once aircraft 10 has landed at the desired location, payload 202 may be released from cargo pod 200 by autonomously or manually actuating gate system 206, as best seen in
Referring now to
Cargo pod 300 includes a suitable payload support assembly to secure payload 304 in cargo pod 300 for transportation thereof. Once payload 304 is secured within cargo pod 300, front hatch 302 is closed to cover front opening 300g and is secured in the close position with a quarter turn latch mechanism 306, as best seen in
As discussed herein, aircraft 10 may autonomously fly to and land in a tailsitter orientation at the desired location for payload deployment responsive to commands from flight control system 30. Once aircraft 10 has landed at the desired location, payload 304 may be released from the cargo pod 300. This may be accomplished by opening an aft hatch depicted as clamshell doors 308 to expose aft opening 300h. Thereafter, cable system 56 may be used to control the descent of payload 304 to the ground, as discussed herein and as best seen in
The foregoing description of embodiments of the disclosure has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the disclosure. The embodiments were chosen and described in order to explain the principals of the disclosure and its practical application to enable one skilled in the art to utilize the disclosure in various embodiments and with various modifications as are suited to the particular use contemplated. Other substitutions, modifications, changes and omissions may be made in the design, operating conditions and arrangement of the embodiments without departing from the scope of the present disclosure. Such modifications and combinations of the illustrative embodiments as well as other embodiments will be apparent to persons skilled in the art upon reference to the description. It is, therefore, intended that the appended claims encompass any such modifications or embodiments.
Number | Name | Date | Kind |
---|---|---|---|
1655113 | Nikola | Jan 1928 | A |
2601090 | James | Jun 1952 | A |
2655997 | Peterson | Oct 1953 | A |
2688843 | Pitt | Sep 1954 | A |
2759691 | Weaver | Aug 1956 | A |
3002712 | Sterling | Oct 1961 | A |
3081964 | Quenzler | Mar 1963 | A |
3181810 | Olson | May 1965 | A |
3259343 | Roppel | Jul 1966 | A |
3289980 | Gardner | Dec 1966 | A |
3350035 | Schlieben | Oct 1967 | A |
3371891 | Brader, Sr. | Mar 1968 | A |
3592412 | Glatfelter | Jul 1971 | A |
3618875 | Kappus | Nov 1971 | A |
3783618 | Kawamura | Jan 1974 | A |
3916588 | Magill | Nov 1975 | A |
4243358 | Carlock et al. | Jan 1981 | A |
4458864 | Colombo et al. | Jul 1984 | A |
4571157 | Eickmann | Feb 1986 | A |
4596368 | Schmittle | Jun 1986 | A |
4613098 | Eickmann | Sep 1986 | A |
4741672 | Breuner | May 1988 | A |
4771967 | Geldbaugh | Sep 1988 | A |
4913377 | Eickmann | Apr 1990 | A |
4925131 | Eickmann | May 1990 | A |
5131605 | Kress | Jul 1992 | A |
5188512 | Thornton | Feb 1993 | A |
5592894 | Johnson | Jan 1997 | A |
5842667 | Jones | Dec 1998 | A |
6086015 | MacCready | Jul 2000 | A |
6170778 | Cycon et al. | Jan 2001 | B1 |
6260793 | Balayn et al. | Jul 2001 | B1 |
6270038 | Cycon et al. | Aug 2001 | B1 |
6402088 | Syrovy et al. | Jun 2002 | B1 |
6655631 | Austen-Brown | Dec 2003 | B2 |
6845939 | Baldwin | Jan 2005 | B1 |
6886776 | Wagner et al. | May 2005 | B2 |
6892980 | Kawai | May 2005 | B2 |
7059562 | Baldwin | Jun 2006 | B2 |
7150429 | Kusic | Dec 2006 | B2 |
7210654 | Cox et al. | May 2007 | B1 |
7465236 | Wagels | Dec 2008 | B2 |
7472863 | Pak | Jan 2009 | B2 |
7555893 | Okai et al. | Jul 2009 | B2 |
7984684 | Hinderks | Jul 2011 | B2 |
8152096 | Smith | Apr 2012 | B2 |
8393564 | Kroo | Mar 2013 | B2 |
8505846 | Sanders | Aug 2013 | B1 |
8602348 | Bryant | Dec 2013 | B2 |
8646720 | Shaw | Feb 2014 | B2 |
8733690 | Bevirt et al. | May 2014 | B2 |
8800912 | Oliver | Aug 2014 | B2 |
8820672 | Erben et al. | Sep 2014 | B2 |
8833692 | Yoeli | Sep 2014 | B2 |
8909391 | Peeters et al. | Dec 2014 | B1 |
8948935 | Peeters et al. | Feb 2015 | B1 |
9022312 | Kosheleff | May 2015 | B2 |
9045226 | Piasecki et al. | Jun 2015 | B2 |
9087451 | Jarrell | Jul 2015 | B1 |
9108744 | Takeuchi | Aug 2015 | B2 |
9109575 | Weddendorf et al. | Aug 2015 | B2 |
9120560 | Armer et al. | Sep 2015 | B1 |
9127908 | Miralles | Sep 2015 | B2 |
9162753 | Panto et al. | Oct 2015 | B1 |
9187174 | Shaw | Nov 2015 | B2 |
9193460 | Laudrain | Nov 2015 | B2 |
9221538 | Takahashi et al. | Dec 2015 | B2 |
9242714 | Wang et al. | Jan 2016 | B2 |
9254916 | Yang | Feb 2016 | B2 |
9284049 | Wang et al. | Mar 2016 | B1 |
9321530 | Wang et al. | Apr 2016 | B2 |
9376208 | Gentry | Jun 2016 | B1 |
9388794 | Weddendorf et al. | Jul 2016 | B2 |
9403593 | Downey et al. | Aug 2016 | B2 |
9440736 | Bitar | Sep 2016 | B2 |
9463875 | Abuelsaad et al. | Oct 2016 | B2 |
9493225 | Wang et al. | Nov 2016 | B2 |
9610817 | Piasecki et al. | Apr 2017 | B1 |
9643720 | Hesselbarth | May 2017 | B2 |
9694908 | Razroev | Jul 2017 | B2 |
9694911 | Bevirt et al. | Jul 2017 | B2 |
9714087 | Matsuda | Jul 2017 | B2 |
9798322 | Bachrach et al. | Oct 2017 | B2 |
9800091 | Nugent, Jr. et al. | Oct 2017 | B2 |
9821909 | Moshe | Nov 2017 | B2 |
9963228 | McCullough et al. | May 2018 | B2 |
9994313 | Claridge et al. | Jun 2018 | B2 |
10011351 | McCullough et al. | Jul 2018 | B2 |
10086931 | Reichert | Oct 2018 | B2 |
10124890 | Sada-Salinas et al. | Nov 2018 | B2 |
10183746 | McCullough et al. | Jan 2019 | B2 |
10214285 | McCullough | Feb 2019 | B2 |
10220944 | McCullough et al. | Mar 2019 | B2 |
10227133 | McCullough et al. | Mar 2019 | B2 |
10232950 | McCullough | Mar 2019 | B2 |
10266266 | Sopper et al. | Apr 2019 | B2 |
10301016 | Bondarev | May 2019 | B1 |
10322799 | McCullough et al. | Jun 2019 | B2 |
10597164 | Oldroyd | Mar 2020 | B2 |
10650342 | Shucker et al. | May 2020 | B2 |
10661892 | McCullough | May 2020 | B2 |
10870485 | Reichert | Dec 2020 | B2 |
10946982 | Carthew et al. | Mar 2021 | B2 |
11111010 | Bernard | Sep 2021 | B2 |
20020100834 | Baldwin | Aug 2002 | A1 |
20020100835 | Kusic | Aug 2002 | A1 |
20030062443 | Wagner et al. | Apr 2003 | A1 |
20040245374 | Morgan | Dec 2004 | A1 |
20060091258 | Chiu et al. | May 2006 | A1 |
20060266881 | Hughey | Nov 2006 | A1 |
20070212224 | Podgurski | Sep 2007 | A1 |
20070221780 | Builta | Sep 2007 | A1 |
20090008499 | Shaw | Jan 2009 | A1 |
20100147993 | Annati et al. | Jun 2010 | A1 |
20100193644 | Karem | Aug 2010 | A1 |
20100295321 | Bevirt | Nov 2010 | A1 |
20110001001 | Bryant | Jan 2011 | A1 |
20110042508 | Bevirt | Feb 2011 | A1 |
20110042509 | Bevirt et al. | Feb 2011 | A1 |
20110057453 | Roberts | Mar 2011 | A1 |
20110121570 | Bevirt et al. | May 2011 | A1 |
20110315806 | Piasecki et al. | Dec 2011 | A1 |
20120209456 | Harmon et al. | Aug 2012 | A1 |
20120234968 | Smith | Sep 2012 | A1 |
20130020429 | Kroo | Jan 2013 | A1 |
20130175404 | Shefer | Jul 2013 | A1 |
20130341458 | Sutton et al. | Dec 2013 | A1 |
20140018979 | Goossen et al. | Jan 2014 | A1 |
20140097290 | Leng | Apr 2014 | A1 |
20140339372 | Dekel et al. | Nov 2014 | A1 |
20150012154 | Senkel et al. | Jan 2015 | A1 |
20150014475 | Taylor et al. | Jan 2015 | A1 |
20150136897 | Seibel et al. | May 2015 | A1 |
20150284079 | Matsuda | Oct 2015 | A1 |
20150285165 | Steinwandel et al. | Oct 2015 | A1 |
20160068265 | Hoareau et al. | Mar 2016 | A1 |
20160180717 | Ubhi et al. | Jun 2016 | A1 |
20160214712 | Fisher et al. | Jul 2016 | A1 |
20170008627 | Soto et al. | Jan 2017 | A1 |
20170021924 | Kubik et al. | Jan 2017 | A1 |
20170066531 | McAdoo | Mar 2017 | A1 |
20170097644 | Fegely et al. | Apr 2017 | A1 |
20170144746 | Schank et al. | May 2017 | A1 |
20170158312 | Alber et al. | Jun 2017 | A1 |
20170174342 | Huang | Jun 2017 | A1 |
20170203843 | Chan | Jul 2017 | A1 |
20170240274 | Regev | Aug 2017 | A1 |
20170297699 | Alber et al. | Oct 2017 | A1 |
20170327219 | Alber | Nov 2017 | A1 |
20170334557 | Alber et al. | Nov 2017 | A1 |
20180002011 | McCullough | Jan 2018 | A1 |
20180002012 | McCullough et al. | Jan 2018 | A1 |
20180002013 | McCullough et al. | Jan 2018 | A1 |
20180002014 | McCullough et al. | Jan 2018 | A1 |
20180002015 | McCullough et al. | Jan 2018 | A1 |
20180002016 | McCullough et al. | Jan 2018 | A1 |
20180002026 | Oldroyd | Jan 2018 | A1 |
20180002027 | McCullough et al. | Jan 2018 | A1 |
20180022467 | Alber | Jan 2018 | A1 |
20180044011 | Reichert | Feb 2018 | A1 |
20180244377 | Chan | Aug 2018 | A1 |
20180244383 | Valente et al. | Aug 2018 | A1 |
20180257761 | Oldroyd et al. | Sep 2018 | A1 |
20180265193 | Gibboney et al. | Sep 2018 | A1 |
20180273160 | Baldwin et al. | Sep 2018 | A1 |
20180281943 | McCullough | Oct 2018 | A1 |
20180327092 | Deng et al. | Nov 2018 | A1 |
20180362158 | Zhang et al. | Dec 2018 | A1 |
20190031331 | McCullough et al. | Jan 2019 | A1 |
20190031334 | McCullough et al. | Jan 2019 | A1 |
20190031335 | McCullough et al. | Jan 2019 | A1 |
20190031336 | McCullough et al. | Jan 2019 | A1 |
20190031337 | McCullough et al. | Jan 2019 | A1 |
20190031338 | McCullough et al. | Jan 2019 | A1 |
20190031339 | McCullough et al. | Jan 2019 | A1 |
20190031361 | McCullough et al. | Jan 2019 | A1 |
20190144108 | McCullough et al. | May 2019 | A1 |
20190263516 | McCullough et al. | Aug 2019 | A1 |
20190389573 | Kahou et al. | Dec 2019 | A1 |
Number | Date | Country |
---|---|---|
105539833 | May 2016 | CN |
2977865 | Jan 2013 | FR |
587388 | Apr 1947 | GB |
618475 | Feb 1949 | GB |
654089 | Jun 1951 | GB |
2001074659 | Oct 2001 | WO |
2005039973 | May 2005 | WO |
2014067563 | May 2014 | WO |
Entry |
---|
Air Launched Unmanned Disaster Relief Delivery Vehicle, 33rd Annual AHS Student Design Competition, University of Maryland, Undated but admitted prior art. |
Bell and NASA Partner for UAV Development; Transportup.com; Sep. 9, 2018. |
Bell APT—Automatic Pod Transport; SUASNEWS.com; Dec. 6, 2017. |
Bell Autonomous Pod Transport; MONCH.com; May 2, 2018. |
Wolfe, Frank; Bell Moving to Scale Up Antonymous Delivery Drones for US Military; Rotor & Wing International; Sep. 27, 2018. |