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 transport and deploy one or more unmanned aircraft vehicles to extend the range of such unmanned aircraft vehicles.
Unmanned aerial vehicles (UAVs), also known as unmanned aerial systems (UASs) or drones, are self-powered aircraft that do not carry a human operator, uses aerodynamic forces to provide vehicle lift, are autonomously and/or remotely operated, may be expendable or recoverable and may carry lethal or nonlethal payloads. UAVs are commonly used in military, commercial, scientific, recreational and other applications. For example, military applications include intelligence, surveillance, reconnaissance and attack missions. Civil applications include aerial photography, search and rescue missions, inspection of utility lines and pipelines, humanitarian aid including delivering food, medicine and other supplies to inaccessible regions, environment monitoring, border patrol missions, cargo transportation, forest fire detection and monitoring, accident investigation and crowd monitoring, to name a few. Certain UAVs have been networked together such that they are capable of cooperating with one another and exhibiting swarm behavior. Such swarm UAVs have the ability to dynamically adapt responsive to changing conditions or parameters including the ability for group coordination, distributed control, distributed tactical group planning, distributed tactical group goals, distributed strategic group goals and/or fully autonomous swarming. It has been found, however, that due to the size of certain UAVs, their flight range is limited. Accordingly, a need has arisen for transportation and deployment systems that can extend the range of such UAVs.
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 including first and second wings with first and second pylons coupled therebetween. A distributed thrust array is coupled to the airframe including a plurality of propulsion assemblies coupled to the first wing and a plurality of propulsion assemblies coupled to the second wing. A UAV carrier assembly is coupled between the first and second pylons. The UAV carrier assembly has a plurality of UAV stations each configured to selectively transport and release a UAV. A flight control system is configured to control each of the propulsion assemblies and launch each of the UAVs during flight.
In certain embodiments, the plurality of UAV stations may be vertically stacked when the aircraft is in the biplane orientation. In some embodiments, the plurality of UAV stations may be at least two UAV stations, at least three UAV stations, at least six UAV stations or more. In certain embodiments, each of the UAV stations is configured to provide a mechanical coupling with a respective one of the UAVs, a magnetic coupling with a respective one of the UAVs, an electrical coupling with a respective one of the UAVs, a power communication coupling with a respective one of the UAVs and/or a data communication coupling with a respective one of the UAVs. In some embodiments, the flight control system may be configured to sequentially launch each of the UAVs. In other embodiments, the flight control system may be configured to simultaneously launch each of the UAVs.
In certain embodiments, the flight control system may be configured to launch each of the UAVs when the aircraft is in the biplane orientation. In other embodiments, the flight control system may be configured to launch each of the UAVs when the aircraft is in the VTOL orientation. In some embodiments, each of the UAVs may be released aftward from the aircraft. In other embodiments, each of the UAVs may be released forward from the aircraft. In certain embodiments, the UAV carrier assembly may include a substantially horizontal cross member coupled between the first and second pylons, a first beam extending substantially vertically upward from the cross member and a second beam extending substantially vertically downward from the cross member when the aircraft is in the biplane orientation. In such embodiments, the first and second beams may be aft swept beams. In some embodiments, the UAV carrier assembly may be a tube launcher. In certain embodiments, the UAV carrier assembly may be configured for UAV recovery during flight.
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 including first and second wings with first and second pylons coupled therebetween. A distributed thrust array is coupled to the airframe including a plurality of propulsion assemblies coupled to the first wing and a plurality of propulsion assemblies coupled to the second wing. A UAV carrier assembly is coupled between the first and second pylons. The UAV carrier assembly has a plurality of UAV stations each configured to selectively transport and release a UAV. A flight control system is configured to control each of the propulsion assemblies and launch each of the UAVs during flight. In addition, the flight control system is configured to sequentially launch each of the UAVs when the aircraft is in the biplane orientation with each of the UAVs released aftward from the aircraft.
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 an UAV carrier assembly 22 that is coupled between pylons 18, 20. UAV carrier assembly 22 is 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
Referring additional to
In its flight configuration, UAV 24 has a two-dimensional distributed thrust array including four propulsion assemblies 28a, 28b, 28c, 28d that are independently operated and controlled by the flight control system of UAV 24. Propulsion assemblies 28a, 28b are coupled to distal ends of a motor mount 28e and propulsion assemblies 28c, 28d are coupled to distal ends of a motor mount 28f. In the illustrated embodiment, motor mounts 28e, 28f are rotatably coupled to the leading edge of the flying wing to enable UAV 24 to transition between the flight configuration depicted in
Referring again to
One or more of wings 14, 16 and/or pylons 18, 20 may contain one or more electrical power sources depicted as a plurality of batteries 32 in pylon 20, as best seen in
Wings 14, 16, pylons 18, 20 and/or UAV carrier assembly 22 may contain a communication network that enables flight control system 30 to communicate with the distributed thrust array of aircraft 10 and UAVs 24. 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 UAVs 24 to a desired location.
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
When aircraft 10 reaches the desired release location for UAVs 24, flight control system 30 provides the launch commands for the UAV carrier assembly to release UAVs 24. Depending upon the type of coupling between the UAV carrier assembly and UAVs 24, the launch commands may result in a mechanical actuation that allows UAVs 24 to separate from the UAV carrier assembly. Alternatively, the launch commands may unenergized electromagnets that enable UAVs 24 to separate from the UAV carrier assembly. In one implementation, flight control system 30 provides launch commands to sequentially release UAVs 24. As best seen from the progression of
As aircraft 10 approaches the desired landing site, aircraft 10 may begin its transition from wing-borne lift to thrust-borne lift. As best seen from the progression of
Even though aircraft 10 has been depicted and described as launching UAVs 24 in a particular sequence, it should be understood by those having ordinary skill in the art that aircraft 10 could launch UAVs 24 in any sequence. In addition, even though aircraft 10 has been depicted and described as sequentially launching UAVs 24, it should be understood by those having ordinary skill in the art that aircraft 10 could alternatively launch UAVs 24a, 24b, 24c simultaneously, as best seen from the progression of
Referring next to
Referring additionally to
In the illustrated embodiment, flight control system 108 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 108 may be implemented in a variety of forms including hardware, software, firmware, special purpose processors and combinations thereof. Flight control system 108 receives input from a variety of sources including internal sources such as sensors 136, controllers/actuators 138, propulsion assemblies 102a, 102b, 102c, 102d, UAV carrier assembly 112 and UAVs 114a, 114b, 114c 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 and independent launch of each UAV 114a, 114b, 114c. Flight control system 108 receives feedback from controllers/actuators 138, propulsion assemblies 102a, 102b, 102c, 102d and UAVs 114a, 114b, 114c. 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 108 to further enhance autonomous control capabilities.
Some or all of the autonomous control capability of flight control system 108 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 108 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. In some implementation, remote control application 128 may be used to provide mission parameters to UAVs 114a, 114b, 114c and remote input device 142 may be used to provide launch commands to sequentially or simultaneously release UAVs 114a, 114b, 114c at the desired location.
Even though the aircraft of the present disclosure have been described and depicted as including a UAV carrier assembly that is configured to receive, secure, transport and deploy three UAVs, it should be understood by those having ordinary skill in the art that an aircraft of the present disclosure could receive, secure, transport and deploy any number of UAVs both less than or greater than three. For example,
In another example,
UAV 324 may be a multirole aircraft having a digital flight control and navigation system and the ability for swarm networking and cooperation. UAV 324 may have a sensor system that includes a sensor array having one or more of an optical camera, a thermal camera, an infrared camera, a video camera, an intelligence, surveillance and reconnaissance module and/or other desired sensors. As best seen from the progression of
Referring next to
Referring next to
Referring next to
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 |
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 |
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 |
10124890 | Sada-Salinas et al. | Nov 2018 | B2 |
10183746 | McCullough et al. | Jan 2019 | B2 |
10214285 | McCullough et al. | Feb 2019 | B2 |
10220944 | McCullough et al. | Mar 2019 | B2 |
10227133 | McCullough et al. | Mar 2019 | B2 |
10232950 | McCullough et al. | Mar 2019 | B2 |
10301016 | Bondarev et al. | May 2019 | B1 |
10315761 | McCullough et al. | Jun 2019 | B2 |
10322799 | McCullough et al. | Jun 2019 | B2 |
10329014 | McCullough et al. | Jun 2019 | B2 |
10343773 | McCullough et al. | Jul 2019 | B1 |
10351232 | McCullough et al. | Jul 2019 | B2 |
10442522 | Oldroyd et al. | Oct 2019 | B2 |
10457390 | McCullough et al. | Oct 2019 | B2 |
10501193 | Oldroyd et al. | Dec 2019 | B2 |
10583921 | McCullough et al. | Mar 2020 | B1 |
10597164 | Oldroyd et al. | Mar 2020 | B2 |
10604249 | McCullough et al. | Mar 2020 | B2 |
10611477 | McCullough et al. | Apr 2020 | B1 |
10618646 | McCullough et al. | Apr 2020 | B2 |
10618647 | McCullough et al. | Apr 2020 | B2 |
10625853 | McCullough et al. | Apr 2020 | B2 |
10633087 | McCullough et al. | Apr 2020 | B2 |
10633088 | McCullough et al. | Apr 2020 | B2 |
10661892 | McCullough et al. | May 2020 | B2 |
10737765 | Oldroyd et al. | Aug 2020 | B2 |
10737778 | Oldroyd et al. | Aug 2020 | B2 |
10752350 | McCullough et al. | Aug 2020 | B2 |
10870487 | McCullough et al. | Dec 2020 | B2 |
10913541 | Oldroyd et al. | Feb 2021 | B2 |
10981661 | Oldroyd et al. | Apr 2021 | B2 |
11027837 | McCullough et al. | Jun 2021 | B2 |
11084579 | Ivans et al. | Aug 2021 | B2 |
11091257 | McCullough et al. | Aug 2021 | B2 |
11104446 | McCullough et al. | Aug 2021 | B2 |
11111010 | Bernard | Sep 2021 | B2 |
11319064 | Wittmaak, Jr. | May 2022 | B1 |
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 |
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 et al. | 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 et al. | Jan 2018 | A1 |
20180002027 | McCullough et al. | Jan 2018 | A1 |
20180022467 | Alber | Jan 2018 | A1 |
20180044011 | Reichert | Feb 2018 | A1 |
20180118336 | Drennan | May 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 |
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. |
Duffy, et al., The LIFT! Project—Modular, Electric Vertical Lift System with Ground Power Tether, AHS 71st Annual Forum, Virginia Beach, Virginia, May 2015. |
Kang, et al., Gap and Stagger Effects on Biplanes with End Plates, 47th AIAA Aerospace Sciences Meeting Including The New Horizons Forum and Aerospace Exposition, Orlando, Florida, Jan. 2009. |
Munk, General Biplane Theory, National Advisory Committee for Aeronautics, Unknown Date. |
Wolfe, Frank; Bell Moving to Scale Up Antonymous Delivery Drones for US Military; Rotor & Wing International; Sep. 27, 2018. |