The present disclosure relates, in general, to aircraft operable to transition between thrust-borne flight and wing-borne flight and, in particular, to aircraft having a distributed thrust array including a plurality of propulsion assemblies each having a gimbal mounted propulsion system operable for thrust vectoring.
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 having redundant directional control. The aircraft has an airframe with a two-dimensional distributed thrust array attached thereto. The thrust array includes a plurality of propulsion assemblies each of which is independently controlled by a flight control system. Each propulsion assembly includes a housing having a gimbal coupled thereto that is operable to tilt about first and second axes. First and second actuators are operable to tilt the gimbal respectively about the first and second axes. A propulsion system is coupled to and is operable to tilt with the gimbal. The propulsion system includes an electric motor having an output drive and a rotor assembly having a plurality of rotor blades. The rotor assembly is rotatable with the output drive of the electric motor in a rotational plane to generate thrust having a thrust vector. Responsive to a thrust vector error of a first propulsion assembly, the flight control system commands at least a second propulsion assembly, that is symmetrically disposed relative to the first propulsion assembly, to counteract the thrust vector error, thereby providing redundant directional control for the aircraft.
In certain embodiments, the flight control system may be a redundant flight control system or a triply redundant flight control system. In some embodiments, the commands of the flight control system to the second propulsion assembly may include tilting the second propulsion assembly about the first axis, tilting the second propulsion assembly about the second axis, changing the operating speed of the rotor assembly of the second propulsion assembly and combinations thereof. In certain embodiments, responsive to the thrust vector error of the first propulsion assembly, the flight control system may command at least two other propulsion assemblies to counteract the thrust vector error, thereby providing redundant directional control for the aircraft.
In some embodiments, when the thrust vector error of the first propulsion assembly is a static actuator fault causing the propulsion system of the first propulsion assembly to cease tilting about one axis, the flight control system may command the second propulsion assembly to counteract the single-axis static actuator fault. In certain embodiments, when the thrust vector error of the first propulsion assembly is a static actuator fault causing the propulsion system of the first propulsion assembly to cease tilting about both axes, the flight control system may command the second propulsion assembly to counteract the two-axis static actuator fault. In some embodiments, when the thrust vector error of the first propulsion assembly is a dynamic actuator fault causing the propulsion system of the first propulsion assembly to tilt uncontrolled about one axis, the flight control system may command the second propulsion assembly to counteract the single-axis dynamic actuator fault. In certain embodiments, when the thrust vector error of the first propulsion assembly is a dynamic actuator fault causing the propulsion system of the first propulsion assembly to tilt uncontrolled about both axes, the flight control system may command the second propulsion assembly to counteract the two-axis dynamic actuator fault.
In some embodiments, responsive to the thrust vector error of the first propulsion assembly, the flight control system may command the aircraft to land at a predetermined location, to perform an emergency landing, to continue a current mission, to adjust a center of mass of a payload relative to the airframe, to initiate a jettison sequence or some combination thereof. In certain embodiments, the aircraft may include at least four propulsion assemblies forming the two-dimensional thrust array. In some embodiments, the aircraft may have a thrust-borne flight mode and a wing-borne flight mode. In certain embodiments, the airframe may include first and second wings having at least first and second pylons extending therebetween and having a plurality of tail members extending therefrom, each tail member having a control surface. In some embodiments, the aircraft may include a pod assembly coupled to the airframe.
In a second aspect, the present disclosure is directed to an aircraft having a thrust-borne flight mode and a wing-borne flight mode. The aircraft includes an airframe having first and second wings with at least first and second pylons extending therebetween and with a plurality of tail members extending therefrom. A pod assembly is coupled to the airframe between the first and second pylons. A two-dimensional distributed thrust array is attached to the airframe. The thrust array includes at least four line replaceable propulsion units each of which is independently controlled by a flight control system. Each propulsion unit includes a housing with and a gimbal coupled thereto that is operable to tilt about first and second axes. First and second actuators are operable to tilt the gimbal respectively about the first and second axes. A propulsion system is coupled to and is operable to tilt with the gimbal. The propulsion system includes an electric motor having an output drive and a rotor assembly having a plurality of rotor blades. The rotor assembly is rotatable with the output drive of the electric motor in a rotational plane to generate thrust having a thrust vector. Responsive to a thrust vector error of a first propulsion assembly, the flight control system commands at least a second propulsion assembly, that is symmetrically disposed relative to the first propulsion assembly, to counteract the thrust vector error, thereby providing redundant directional control for 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
Extending generally perpendicularly between wings 14a, 14b are two truss structures depicted as pylons 16a, 16b. In other embodiments, more than two pylons may be present. Pylons 16a, 16b are preferably formed from high strength and lightweight materials such as fiberglass, carbon, plastic, metal or other suitable material or combination of materials. Wings 14a, 14b and pylons 16a, 16b may be coupled together at the respective intersections using mechanical connections such as bolts, screws, rivets, adhesives and/or other suitable joining technique. Extending generally perpendicularly from wings 14a, 14b are landing gear depicted as tail members 18a, 18b, 18c, 18d that enable aircraft 10 to operate as a tailsitting aircraft. In the illustrated embodiment, tail members 18a, 18b, 18c, 18d are fixed landing struts. In other embodiments, tail members 18a, 18b, 18c, 18d may include passively operated pneumatic landing struts or actively operated telescoping landing struts with or without wheels for ground maneuvers. Tail members 18a, 18b, 18c, 18d each include a control surface 20a, 20b, 20c, 20d, respectively, that may be passive or active aerosurfaces that serve as vertical stabilizers and/or elevators during wing-borne flight and serve to enhance hover stability during thrust-borne flight.
Wings 14a, 14b and pylons 16a, 16b preferably include central passageways operable to contain flight control systems, energy sources, communication lines and other desired systems. For example, as best seen in
In the illustrated embodiment, wings 14a, 14b and/or pylons 16a, 16b may contain one or more of electrical power sources depicted as batteries 22 in wing 14a, as best seen in
In the illustrated embodiment, the distributed thrust array includes four propulsion assemblies 26a, 26b, 26c, 26d that are independently operated and controlled by flight control system 32. It should be noted, however, that the distributed thrust array of the present disclosure could have any number of independent propulsion assemblies including six, eight, twelve, sixteen or other number of independent propulsion assemblies. Propulsion assemblies 26a, 26b, 26c, 26d are independently attachable to and detachable from airframe 12. For example, propulsion assemblies 26a, 26b, 26c, 26d are preferably standardized and interchangeable units that are most preferably line replaceable propulsion units enabling easy installation and removal from airframe 12. Propulsion assemblies 26a, 26b, 26c, 26d may be coupled to wings 14a, 14b using quick connect and disconnect couplings techniques including bolts, pins, cables or other suitable coupling techniques. In addition, the use of line replaceable propulsion units is beneficial in maintenance situations if a fault is discovered with one of the propulsion units. In this case, the faulty propulsion unit can be decoupled from airframe 12 by simple operations and another propulsion unit can then be attached to airframe 12. In other embodiments, propulsion assemblies 26a, 26b, 26c, 26d may be permanently coupled to wings 14a, 14b by riveting, bonding and/or other suitable technique.
As illustrated, propulsion assemblies 26a, 26b, 26c, 26d are coupled to the outboard ends of wings 14a, 14b. In other embodiments, propulsion assemblies 26a, 26b, 26c, 26d could have other configurations including close coupled configurations, high wing configurations, low wing configurations or other suitable configuration. In the illustrated embodiment, the four independently operating propulsion assemblies 26a, 26b, 26c, 26d form a two-dimensional thrust array with each of the propulsion assemblies having a symmetrically disposed propulsion assembly. For example, propulsion assemblies 26a, 26c are symmetrically disposed propulsion assemblies and propulsion assemblies 26b, 26d are symmetrically disposed propulsion assemblies. It should be noted, however, that a two-dimensional thrust array of the present disclosure could have any number of independent propulsion assemblies including six, eight, twelve, sixteen or other number of independent propulsion assemblies that form the two-dimensional thrust array with each of the propulsion assemblies having a symmetrically disposed propulsion assembly.
In the illustrated embodiment, each propulsion assembly 26a, 26b, 26c, 26d includes a housing 28a, 28b, 28c, 28d, that contains components such as an electric motor, a gimbal, one or more actuators and an electronics node including, for example, batteries, controllers, sensors and other desired electronic equipment. Only electric motors 30a, 30b and electronics nodes 32a, 32b are visible in
Flight control system 32 communicates via communications network 24 with the electronics nodes of each propulsion assembly 26a, 26b, 26c, 26d, such as electronics node 32a of propulsion assembly 26a and electronics node 32b of propulsion assembly 26b. Flight control system 32 receives sensor data from and sends flight command information to the electronics nodes of each propulsion assembly 26a, 26b, 26c, 26d such that each propulsion assembly 26a, 26b, 26c, 26d may be individually and independently controlled and operated. For example, flight control system 32 is operable to individually and independently control the operating speed and thrust vector of each propulsion assembly 26a, 26b, 26c, 26d. Flight control system 32 may autonomously control some or all aspects of flight operation for aircraft 10. Flight control system 32 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 32 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 logistic operations for both military and commercial applications.
Each propulsion assembly 26a, 26b, 26c, 26d includes a rotor assembly 34a, 34b, 34c, 34d. Each rotor assembly 34a, 34b, 34c, 34d is directly or indirectly coupled to an output drive of a respective electrical motor 30a, 30b, 30c, 30d that rotates the rotor assembly 34a, 34b, 34c, 34d in a rotational plane to generate thrust for aircraft 10. In the illustrated embodiment, rotor assemblies 34a, 34b, 34c, 34d each include three rotor blades having a fixed pitch. In other embodiments, the rotor assemblies could have other numbers of rotor blades both less than and greater than three. Alternatively or additionally, the rotor assemblies could have variable pitch rotor blades with collective and/or cyclic pitch control. Each electrical motor 30a, 30b, 30c, 30d is paired with a rotor assembly 34a, 34b, 34c, 34d, for example electrical motor 30a and rotor assembly 34a, to form a propulsion system 36a, 36b, 36c, 36d. As described herein, each propulsion system 36a, 36b, 36c, 36d may have a single-axis or a two-axis tilting degree of freedom relative to housings 28a, 28b, 28c, 28d and thus airframe 12 such that propulsion systems 36a, 36b, 36c, 36d are operable for thrust vectoring. 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 not have a tilting degree of freedom in which case, propulsion systems 36a, 36b, 36c, 36d may not be capable of thrust vectoring. As such, aircraft 10 may have no thrust vectoring capabilities, single-axis thrust vectoring capabilities or two-axis thrust vectoring capabilities associated with each propulsion assembly 26a, 26b, 26c, 26d.
Aircraft 10 may operate as a transport aircraft for a pod assembly 50 that is fixed to or selectively attachable to and detachable from airframe 12. In the illustrated embodiment, pylons 16a, 16b include receiving assemblies for coupling with pod assembly 50. The connection between pylons 16a, 16b and pod assembly 50 may be a fixed connection that secures pod assembly 50 in a single location relative to airframe 12. Alternatively, pod assembly 50 may be allowed to rotate and/or translate relative to airframe 12 during ground and/or flight operations. For example, it may be desirable to have pod assembly 50 low to the ground for loading and unloading cargo but more distant from the ground for takeoff and landing. As another example, it may be desirable to change the center of mass of pod assembly 50 relative to airframe 12 during certain flight conditions such as moving the center of mass of pod assembly 50 forward relative to airframe 12 during high speed wing-borne flight. Similarly, it may be desirable to lowering the center of mass of pod assembly 50 relative to airframe 12 during hover in the event of a partial or total failure of one of the propulsion assemblies. As illustrated, pod assembly 50 may be selectively coupled to and decoupled from airframe 12 to enable sequential pickup, transportation and delivery of multiple pod assemblies 50 to and from multiple locations.
Airframe 12 preferably has remote release capabilities of pod assembly 50. For example, this feature allows airframe 12 to drop pod assembly 50 at a desire location following transportation. In addition, this feature allows airframe 12 to jettison pod assembly 50 during flight, for example, in the event of an emergency situation such as a propulsion assembly or other system of aircraft 10 becoming compromised. One or more communication channels may be established between pod assembly 50 and airframe 12 when pod assembly 50 is attached therewith. A quick disconnect harness may be coupled between pod assembly 50 and airframe 12 such that flight control system 32 may send commands to pod assembly 50 to perform functions. For example, flight control system 32 may operate doors of pod assembly 50 between open and closed positions to enable loading and unloading of a payload to be transported within pod assembly 50.
Referring additionally to
As best seen in
Alternatively or additional, flight control system 32 may utilize differential thrust vectoring of propulsion systems 36a, 36b, 36c, 36d for stabilizing aircraft 10 and for providing yaw authority. This may be achieved by differential longitudinal thrust vectoring of two symmetrically disposed propulsion systems such as propulsion systems 36a, 36c. This may also be achieved by differential thrust vectoring of all propulsion systems 36a, 36b, 36c, 36d by suitably clocking the thrust vectors at approximately 90 degrees from one another. Alternatively or additional, flight control system 32 may utilize differential control surface maneuvers of control surfaces 20a, 20b, 20c, 20d for stabilizing aircraft 10 and for providing yaw authority. This may be achieved by differential longitudinal control surface maneuvers of two symmetrically disposed control surfaces such as control surfaces 20a, 20c.
In embodiments of aircraft 10 having two-axis thrust vectoring capabilities associated with each propulsion assembly 26a, 26b, 26c, 26d, aircraft 10 has redundant direction control during hover which serves as a safety feature in the event of a partial or complete failure in one propulsion assembly. As discussed herein, flight control system 32 is operable to send commands to a symmetrically disposed propulsion assembly to counteract a thrust vector error in the compromised propulsion assembly. Alternatively or additional, flight control system 32 is operable to send commands to any one or all of the other propulsion assemblies to counteract a thrust vector error in the compromised propulsion assembly. This feature improves the overall safety of aircraft 10 and provides redundant direction control to aircraft 10.
After vertical assent to the desired elevation, aircraft 10 may begin the transition from thrust-borne flight to wing-borne flight. As best seen from the progression of
As best seen in
As aircraft 10 approaches its destination, aircraft 10 may begin its transition from wing-borne flight to thrust-borne flight. As best seen from the progression of
Referring next to
For example, as best seen in
The longitudinal thrust vectoring operation will now be described with reference to an exemplary propulsion assembly 102, depicted as a line replaceable propulsion unit, in
As best seen in the comparison of
As best seen in
The lateral thrust vectoring operation will now be described with reference to propulsion assembly 102 in
Using both the longitudinal and lateral control authority provided by collective thrust vectoring of propulsion assemblies 102a, 102b, 102c, 102d, provides omnidirectional horizontal control authority for aircraft 100. For example, as best seen in
The diagonal thrust vectoring operation will now be described with reference to propulsion assembly 102 in
In addition to collective thrust vectoring of propulsion assemblies 102a, 102b, 102c, 102d, aircraft 100 is also operable to engage in differential thrust vectoring of propulsion assemblies 102a, 102b, 102c, 102d. For example, as best seen in
As discussed herein, outer gimbal member 128 is pivotally coupled to housing 126 and is operable to tilt about the first axis and inner gimbal member 130 is pivotally coupled to outer gimbal member 128 and is operable to tilt about the second axis that is orthogonal to the first axis. In the illustrated embodiment, in order to minimize the energy required to tilt propulsion system 112 relative to housing 126 to change the thrust vector direction of propulsion assembly 102, the first and second axes pass through propulsion system 112. The precise location of the intersection of the axes through propulsion system 112 may be determined based on factors including the mass of propulsion system 112, the size and shape of propulsion system 112, the desired rotational velocity of propulsion system 112 during thrust vectoring and other factors that should be understood by those having ordinary skill in the art. In one implementation, the first and second axes may pass through the center of mass of propulsion system 112. Alternatively, it may be desirable to have the first and second axes pass through a location near the center of mass of propulsion system 112 such as within a predetermined distance from the center of mass of propulsion system 112. The predetermined distance may be selected based upon criteria such as a defined volume surrounding the center of mass that contains a predetermined portion of the total mass of propulsion system 112. For example, the first and second axes may pass through a location within a volume centered at the center of mass of propulsion system 112 that contains no more than ten percent of the mass of propulsion system 112. Such a volume may be expressed, for example, as being within one centimeter, one inch or other predetermined distance from the center of mass of propulsion system 112.
Due to dynamic effects caused by the rotation of the rotor assembly and the lift generated by the rotor assembly during flight operations, such as during thrust-borne flight operations, the center of mass in hover of propulsion system 112 may not coincide with the actual center of mass of propulsion system 112. To compensate for the dynamic effects, the first and second axes may pass through the center of mass in hover of propulsion system 112. Alternatively, it may be desirable to have the first and second axes pass through a location near the center of mass in hover of propulsion system 112 such as within a predetermined distance from the center of mass in hover of propulsion system 112. In one example, it may be desirable to have the first and second axes pass through a location between the center of mass of propulsion system 112 and the center of mass in hover of propulsion system 112.
Referring now to
Referring specifically to
Referring specifically to
Referring specifically to
Referring specifically to
In addition to performing autonomous corrective actions to counteract a thrust vector error, flight control system 114 may autonomously command aircraft 100 to perform other flight maneuvers. Depending upon the type of fault and the magnitude of the thrust vector error caused by the fault, flight control system 114 may command aircraft 100 to return to a maintenance center or other predetermined location. Under other fault situations, flight control system 114 may command aircraft 100 to initiate a jettison sequence of the pod assembly or other payload and/or perform an emergency landing. If the fault is not critical and/or is suitably overcome by the corrective actions described herein, flight control system 114 may command aircraft 100 to continue the current mission. In this case, flight control system 114 may command aircraft 100 to adjust the center of mass of the pod assembly or other payload relative to the airframe such as lowering the elevation of the pod assembly relative to the airframe as this may improve hover stability.
Referring next to
For example, as best seen in
The longitudinal thrust vectoring operation will now be described with reference to an exemplary propulsion assembly 202, depicted as a line replaceable propulsion unit, in
As best seen in the comparison of
In the illustrated embodiment, the single gimbal axis is located below propulsion system 212. In other single gimbal axis embodiments and similar to propulsion assembly 102 of
In addition to collective thrust vectoring of propulsion assemblies 202a, 202b, 202c, 202d, aircraft 200 is also operable to engage in differential longitudinal thrust vectoring of propulsion assemblies 202a, 202b, 202c, 202d. For example, as best seen in
Referring to
If aircraft 10 utilizes embodiments of propulsion assembly 302 with no thrust vectoring, aircraft 10 has two independent yaw authority mechanisms in hover. In one approach, differential speed control is used to change the relative rotor speeds of the rotor assemblies rotating clockwise compared to the rotor assemblies rotating counterclockwise causing a torque imbalance in aircraft 10, which provides yaw authority. This operation may be represented by the tail section configuration in
If aircraft 10 utilizes embodiments of propulsion assembly 302 having single-axis or two-axis thrust vectoring, aircraft 10 has three independent yaw authority mechanisms in hover. In one approach, differential speed control is used to change the relative rotor speeds of the rotor assemblies rotating clockwise compared to the rotor assemblies rotating counterclockwise causing a torque imbalance in aircraft 10, which provides yaw authority. This operation may be represented by the tail section configuration in
In addition, an aircraft 10 having thrust vectoring propulsion assemblies 302 may use a combination of differential speed control, differential longitudinal control surface maneuvers and differential thrust vectoring to provide yaw authority. For example, aircraft 10 could utilize differential speed control in combination with differential longitudinal control surface maneuvers, which may be represented by the tail section configuration 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.
The present application is a continuation of co-pending application Ser. No. 15/972,431 filed May 7, 2018, which claims the benefit of U.S. Provisional Application No. 62/594,424, filed Dec. 4, 2017 and which is a continuation-in-part of application Ser. No. 15/606,242 filed May 26, 2017, which is a continuation-in-part of application Ser. No. 15/200,163 filed Jul. 1, 2016, the entire contents of each is hereby incorporated by reference.
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 |
10322799 | McCullough et al. | Jun 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 |
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 |
20170338710 | Liu | 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 |
20180244377 | Chan | Aug 2018 | A1 |
20180244383 | Valente et al. | Aug 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. |
Number | Date | Country | |
---|---|---|---|
20200231297 A1 | Jul 2020 | US |
Number | Date | Country | |
---|---|---|---|
62594424 | Dec 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15972431 | May 2018 | US |
Child | 16790676 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15606242 | May 2017 | US |
Child | 15972431 | US | |
Parent | 15200163 | Jul 2016 | US |
Child | 15606242 | US |