The present disclosure relates, in general, to aircraft operable to transition between thrust-borne lift in a VTOL orientation and wing-borne lift in a biplane orientation and, in particular, to logistics support aircraft having a cargo delivery flight configuration and a minimal drag flight configuration.
Fixed-wing aircraft, such as airplanes, are capable of flight using wings that generate lift responsive to the forward airspeed of the aircraft, which is generated by thrust from one or more jet engines or propellers. The wings generally have an airfoil cross section that deflects air downward as the aircraft moves forward, generating the lift force to support the airplane in flight. Fixed-wing aircraft, however, typically require a runway that is hundreds or thousands of feet long for takeoff and landing. Unlike fixed-wing aircraft, vertical takeoff and landing (VTOL) aircraft do not require runways. Instead, VTOL aircraft are capable of taking off, hovering and landing vertically. One example of VTOL aircraft is a helicopter which is a rotorcraft having one or more rotors that provide lift and thrust to the aircraft. The rotors not only enable hovering and vertical takeoff and landing, but also enable, forward, backward and lateral flight. These attributes make helicopters highly versatile for use in congested, isolated or remote areas where fixed-wing aircraft may be unable to takeoff and land. Helicopters, however, typically lack the forward airspeed of fixed-wing aircraft.
A tiltrotor aircraft is another example of a VTOL aircraft. Tiltrotor aircraft generate lift and propulsion using proprotors that are typically coupled to nacelles mounted near the ends of a fixed wing. The nacelles rotate relative to the fixed wing such that the proprotors have a generally horizontal plane of rotation for vertical takeoff, hovering and landing and a generally vertical plane of rotation for forward flight, wherein the fixed wing provides lift and the proprotors provide forward thrust. In this manner, tiltrotor aircraft combine the vertical lift capability of a helicopter with the speed and range of fixed-wing aircraft. Tiltrotor aircraft, however, typically suffer from downwash inefficiencies during vertical takeoff and landing due to interference caused by the fixed wing. A further example of a VTOL aircraft is a tiltwing aircraft that features a rotatable wing that is generally horizontal for forward flight and rotates to a generally vertical orientation for vertical takeoff and landing. Propellers are coupled to the rotating wing to provide the required vertical thrust for takeoff and landing and the required forward thrust to generate lift from the wing during forward flight. The tiltwing design enables the slipstream from the propellers to strike the wing on its smallest dimension, thus improving vertical thrust efficiency as compared to tiltrotor aircraft. Tiltwing aircraft, however, are more difficult to control during hover as the vertically tilted wing provides a large surface area for crosswinds typically requiring tiltwing aircraft to have either cyclic rotor control or an additional thrust station to generate a moment.
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 includes an airframe having first and second wings with first and second pylons extending therebetween forming a central region. A two-dimensional distributed thrust array is attached 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 flight control system is coupled to the airframe and is operable to independently control each of the propulsion assemblies. A nose cone is selectively coupled to the airframe such that the nose cone extends between the first and second wings and between first and second pylons. An afterbody is selectively coupled to the airframe such that the afterbody extends between the first and second wings and between first and second pylons. In a cargo delivery flight configuration, the nose cone and the afterbody are coupled to the airframe to form a cargo enclosure with an aerodynamic outer shape. In a minimal drag flight configuration, the nose cone and the afterbody are not coupled to the airframe such that air passes through the central region during flight.
In certain embodiments, in the biplane orientation, the first wing may be an upper wing having a dihedral configuration and the second wing may be a lower wing having an anhedral configuration. In some embodiments, the central region may form a rectangle having a major dimension extending between the first and second wings and a minor dimension extending between first and second pylons, wherein the major dimension is greater than the minor dimension. In such embodiments, the major dimension may be between about two times and about four times greater than the minor dimension, the major dimension may be between about two times and about three times greater than the minor dimension or the major dimension may be about two and half times greater than the minor dimension. In certain embodiments, each of the propulsion assemblies may be outboard of the central region. In some embodiments, each of the propulsion assemblies may include a variable speed electric motor and a rotor assembly. In certain embodiments, each of the propulsion assemblies may be a thrust vectoring propulsion assembly such as a longitudinal thrust vectoring propulsion assembly or an omnidirectional thrust vectoring propulsion assembly.
In some embodiments, each of the propulsion assemblies may include a tail assembly with at least one aerosurface. In certain embodiments, two propulsion assemblies may be coupled to the first wing and two propulsion assemblies may be coupled to the second wing. In some embodiments, the nose cone may include a leading edge fairing that is slidably receivable on the airframe. In certain embodiments, the afterbody may include a trailing edge fairing that is slidably receivable on the airframe. In such embodiments, the trailing edge fairing may include first and second trailing edge members that are rotatable relative to the first and second pylons, respectively, such that the first and second trailing edge members have open and closed positions.
In a second aspect, the present disclosure is directed to a method of operating an aircraft. The method includes providing an airframe having first and second wings with first and second pylons extending therebetween forming a central region, a plurality of propulsion assemblies coupled to the first wing, a plurality of propulsion assemblies coupled to the second wing and a flight control system operable to independently control each of the propulsion assemblies; forming a cargo enclosure having an aerodynamic outer shape by attaching a nose cone to the airframe such that the nose cone extends between the first and second wings and between first and second pylons and by attaching an afterbody to the airframe such that the afterbody extends between the first and second wings and between first and second pylons; disposing cargo within the cargo enclosure; transporting the cargo by air from a first location to a second location including transitioning the aircraft between thrust-borne lift in a VTOL orientation and wing-borne lift in a biplane orientation; removing the cargo from the cargo enclosure at the second location; detaching the nose cone and the afterbody from the airframe forming a minimal drag flight configuration in which air passes through the central region during flight; and returning the aircraft by air from the second location to the first location in the minimal drag flight configuration including transitioning the aircraft between thrust-borne lift in the VTOL orientation and wing-borne lift in the biplane orientation.
The method may also include transitioning the aircraft between the VTOL orientation wherein the first wing is forward of the cargo enclosure and the second wing is aft of the cargo enclosure and the biplane orientation wherein the first wing is below the cargo enclosure and the second wing is above the cargo enclosure; operating the aircraft responsive to autonomous flight control; operating the aircraft responsive to remote flight control; operating the aircraft responsive to a combination of remote flight control and autonomous flight control and/or attaching the nose cone to the airframe by slidably receiving a leading edge fairing on the airframe; attaching the afterbody to the airframe by slidably receiving a trailing edge fairing on the airframe; detaching the nose cone from the airframe by slidably removing the leading edge fairing from the airframe; and detaching the afterbody from the airframe by slidably removing the trailing edge fairing from the airframe.
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 includes 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
Wings 14, 16 and pylons 18, 20 preferably include internal passageways operable to contain flight control systems, energy sources, communication lines and other desired systems. For example, as best seen in
Wings 14, 16 and pylons 18, 20 may contain one or more of electrical power sources depicted as one or more batteries 22a in pylon 20, as best seen in
The two-dimensional distributed thrust array of aircraft 10 includes a plurality of propulsion assemblies, individually and collectively denoted as 24. In the illustrated embodiment, two propulsion assemblies 24 are coupled to wing 14 and two propulsion assemblies 24 are coupled to wing 16 such that each propulsion assembly 24 is outboard of the central region of airframe 12. In other embodiments, aircraft 10 could have other numbers of propulsion assemblies both greater than or less than four in other configurations. In the illustrated embodiment, propulsion assemblies 24 are variable speed propulsion assemblies having fixed pitch rotor blades and thrust vectoring capability. Depending upon the implementation, propulsion assemblies 24 may have longitudinal thrust vectoring capability, lateral thrust vectoring capability or omnidirectional thrust vectoring capability. In other embodiments, propulsion assemblies 24 may be single speed propulsion assemblies, may have variable pitch rotor blades and/or may be non thrust vectoring propulsion assemblies.
In the illustrated embodiment, propulsion assemblies 24 are coupled to the outboard ends of wings 14, 16 in a midwing configuration. In other embodiments, propulsion assemblies 24 could be coupled to wings 14, 16 at midspan, in a high wing configuation and/or in a low wing configuation or various combination or permutations thereof. Propulsion assemblies 24 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 24 can be decoupled from airframe 12 by simple operations and another propulsion assembly 24 can then be attached to airframe 12. In other embodiments, propulsion assemblies 24 may be permanently coupled to wings 14, 16 by riveting, bonding, welding, bolting and/or other suitable technique.
As best seen in
Flight control system 22 communicates via the wired communications network of airframe 12 with the electronics nodes 24e of the propulsion assemblies 24. Flight control system 22 receives sensor data from and sends flight command information to the electronics nodes 24e such that each propulsion assembly 24 may be individually and independently controlled and operated. For example, flight control system 22 is operable to individually and independently control the speed and the thrust vector of each propulsion assembly 24. Flight control system 22 may autonomously control some or all aspects of flight operation for aircraft 10. Flight control system 22 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 22 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 perform unmanned logistics operations for both military and commercial applications.
Each propulsion assembly 24 includes a rotor assembly 24i that is coupled to an output drive of a respective electrical motor 24h that rotates the rotor assembly 24i in a rotational plane to generate thrust for aircraft 10. In the illustrated embodiment, rotor assemblies 24i each include four rotor blades having a fixed pitch. In other embodiments, the rotor assemblies could have other numbers of rotor blades including rotor assemblies having less than or more than four rotor blades. Alternatively or additionally, the rotor assemblies could have variable pitch rotor blades with collective and/or cyclic pitch control. Each electrical motor 24h is paired with a rotor assembly 24i to form a propulsion system 24f. In the illustrated embodiment, each propulsion system 24f has a two-axis tilting degree of freedom relative to nacelle 24a provided by gimbal 24g such that propulsion assemblies 24 are omnidirectional thrust vectoring propulsion assemblies. In the illustrated embodiment, the maximum angle of the thrust vector may preferably be between about 10 degrees and about 30 degrees, may more preferably be between about 15 degrees and about 25 degrees and may most preferably be about 20 degrees. Notably, using a 20-degree thrust vector yields a lateral component of thrust that is about 34 percent of total thrust. In other embodiments, the propulsion systems may have a single-axis tilting degree of freedom in which case, the propulsion assemblies could act as longitudinal and/or lateral thrust vectoring propulsion assemblies.
In one non-limiting example, aircraft 10 may operate as a logistics support aircraft. As best seen in
In the illustrated implementation, cargo 26 is depicted as a single package carried within cargo enclosure 30. In other implementation, cargo 26 may be composed of any number of packages or other items that can be carried within cargo enclosure 30. Preferably, cargo 26 is fixably coupled within cargo enclosure 30 by suitable means to prevent relative movement therebetween, thus protecting cargo 26 from damage and maintaining a stable center of mass for aircraft 10. In addition, cargo 26 may be insertable into and removable from cargo enclosure 30 to enable sequential cargo pickup, transportation and delivery operations to and from multiple locations. Alternatively or additionally, cargo 26, nose cone 30a and afterbody 30b may be removed from airframe 12, as best seen in
Aircraft 10 and cargo enclosure 30 preferably have remote release capabilities of cargo 26. For example, this feature allows airframe 12 to deliver cargo 26 to a desired location following transportation without the requirement for landing. In this case, afterbody 30b preferably includes a pair of trailing edge members depicted as rotatable doors that operate in a clamshell manner relative to pylons 18, 20 responsive to instructions received from flight control system 22. For example, as best seen in
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
Continuing with the flight scenario illustrated in
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
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 described herein as including an electric motor and a rotor assembly. In the illustrated embodiment, propulsion assembly 102b includes 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 described herein as including an electric motor and a rotor assembly. In the illustrated embodiment, propulsion assembly 102c includes 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 described herein as including an electric motor and a rotor assembly. In the illustrated embodiment, propulsion assembly 102d includes 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 communicably linked to the electronic nodes 104a, 104b, 104c, 104d thereof by a communications network depicted as arrows 114a, 114b, 114c, 114d between flight control system 112 and propulsion assemblies 102a, 102b, 102c, 102d. 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
Flight control system 112 preferably includes a non-transitory computer readable storage medium including a set of computer instructions executable by a processor. Flight control system 112 may be a triply redundant system implemented on one or more general-purpose computers, special purpose computers or other machines with memory and processing capability. For example, flight control system 112 may include one or more memory storage modules including, but is not limited to, internal storage memory such as random access memory, non-volatile memory such as read only memory, removable memory such as magnetic storage memory, optical storage, solid-state storage memory or other suitable memory storage entity. Flight control system 112 may be a microprocessor-based system operable to execute program code in the form of machine-executable instructions. In addition, flight control system 112 may be selectively connectable 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.
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 138 and propulsion assemblies 102a, 102b, 102c, 102d and external sources such as remote system 124 as well as global positioning system satellites or other location positioning systems and the like. For example, as discussed herein, flight control system 112 may receive a flight plan for a mission from remote system 124. Thereafter, flight control system 112 may be operable to autonomously control all aspects of flight of an aircraft of the present disclosure.
For example, during the various operating modes of aircraft 100 including vertical takeoff and landing flight mode, hover flight mode, forward flight mode and transitions therebetween, command module 132 provides commands to controllers 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 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 138. Sensors 136, such as positioning sensors, attitude 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.
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. For example, the computing systems may include one or more memory storage modules including, but is not limited to, internal storage memory such as random access memory, non-volatile memory such as read only memory, removable memory such as magnetic storage memory, optical storage memory, solid-state storage memory or other suitable memory storage entity. 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. The communication network may be a local area network, a wide area network, the Internet, or any other type of network that couples a plurality of computers to enable various modes of communication via network messages using as suitable communication techniques, such as transmission control protocol/internet protocol, file transfer protocol, hypertext transfer protocol, internet protocol security protocol, point-to-point tunneling protocol, secure sockets layer protocol or other suitable protocol. 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.
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.
The present application is a continuation-in-part of application Ser. No. 16/246,474 filed Jan. 12, 2019, which is a continuation of application Ser. No. 15/200,197 filed Jul. 1, 2016, now U.S. Pat. No. 10,220,944, the entire contents of each is hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
1655113 | Nikola | Jan 1928 | 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 |
4458864 | Colombo et al. | Jul 1984 | A |
4571157 | Eickmann | Feb 1986 | A |
4596368 | Schmittle | Jun 1986 | A |
4613098 | Eickmann | Sep 1986 | A |
4771967 | Geldbaugh | Sep 1988 | A |
4913377 | Eickmann | Apr 1990 | A |
5131605 | Kress | Jul 1992 | 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 |
7367528 | Allison, Sr. | May 2008 | B2 |
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 |
8505846 | Sanders | Aug 2013 | B1 |
8602348 | Bryant | Dec 2013 | 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 |
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 |
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 |
20060108477 | Helou | May 2006 | A1 |
20060266881 | Hughey | Nov 2006 | A1 |
20070221780 | Builta | Sep 2007 | A1 |
20090008499 | Shaw | Jan 2009 | A1 |
20100147993 | Annati et al. | Jun 2010 | A1 |
20100295321 | Bevirt | Nov 2010 | 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 |
20140018979 | Goossen et al. | Jan 2014 | A1 |
20140217230 | Helou | Aug 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 |
20170021924 | Kubik et al. | Jan 2017 | A1 |
20170066531 | McAdoo | Mar 2017 | A1 |
20170097644 | Fegely et al. | Apr 2017 | A1 |
20170158312 | Alber et al. | 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 |
20180002013 | McCullough et al. | Jan 2018 | A1 |
20180002026 | Oldroyd et al. | Jan 2018 | A1 |
20180244383 | Valente et al. | Aug 2018 | A1 |
20180265193 | Gibboney et al. | Sep 2018 | A1 |
20200023829 | Hefner | Jan 2020 | A1 |
Number | Date | Country |
---|---|---|
105539833 | May 2016 | CN |
2977865 | Jan 2013 | FR |
2001074659 | Oct 2001 | WO |
2005039973 | May 2005 | WO |
2014067563 | May 2014 | WO |
WO-2015135951 | Sep 2015 | WO |
WO-2018200879 | Nov 2018 | WO |
Entry |
---|
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. |
Air Launched Unmanned Disaster Relief Delivery Vehicle, 33rd Annual AHS Student Design Competition, University of Maryland, Undated but admitted prior art. |
European Search Report; Application No. 20166807.6; European Patent Office; dated Oct. 9, 2020. |
Number | Date | Country | |
---|---|---|---|
20200062384 A1 | Feb 2020 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15200197 | Jul 2016 | US |
Child | 16246474 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16246474 | Jan 2019 | US |
Child | 16427311 | US |