Rotorcraft state control
Summary by NHIP
Constant Thrust Rotor Control
The aircraft controller adjusts rotor drag and efficiency to change state without altering power output. It issues commands to cyclically adjust rotor pitch and tail rotor thrust while maintaining constant thrust and heading during translation or hover.
Claim Score by NHIP
Abstract
A method of rotorcraft state control includes receiving command input indicative of an intended state change in a rotorcraft. The method also includes issuing command output to a rotor actuation system to carry out the intended state change by varying drag and/or efficiency on one or more rotor blades of the rotorcraft. Issuing command output can include issuing a command output to the rotor actuation system to carry out the intended state change by increasing drag at a substantially constant thrust on one or more rotor blades of the rotorcraft.

Term
9.9 yearsleft in the term
Expires 26 August 2036.
- Priority
- Filed
- Granted
- Today
- Expires
14 claims: 1 independent, 13 dependent
- 1Broadest claimClaim Score 67, broad(NHIP)An aircraft comprising a rotor system including blades to provide thrust for the aircraft at a rotor efficiency level;a power system which powers the rotor system at a power output level;and a controller which selectively changes rotor efficiency of the rotor system to change a rotor system state of the aircraft without changing the power output level, wherein the controller issues command output to the rotor system to carry out the intended state change by adjusting drag and/or efficiency at a substantially constant thrust on one or more rotor blades of the rotorcraft.
42 paragraphs in 5 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATION
This application claims the benefit of priority under 35 U.S.C. § 119(e) to U.S. Provisional Application No. 62/210,709, filed Aug. 27, 2015, which is incorporated herein by reference in its entirety.
BACKGROUND OF THE INVENTION
1. Field of the Invention
The present disclosure relates to rotorcraft, and more particularly to systems and methods for controlling rotorcraft.
2. Description of Related Art
Traditional rotorcraft, such as conventional helicopters, use cyclic control of rotor blades to alter the direction of the thrust vector of the rotor blades for maneuvering. For side-to-side motion in a traditional helicopter, for example, the cyclic control of the rotor blades rolls the aircraft slightly toward the direction of side-to-side movement, and when the side-to-side movement is complete, the cyclic control must be used to roll the aircraft in the opposite direction to cancel out the side-to-side motion. Similar techniques can be used for forward and backward motion.
Traditionally, the engine speed and rotation rate of the rotor can remain substantially constant, and ascent and descent are achieved through collective control. Collective control is achieved by altering the pitch of the rotor blades collectively, for example to increase lift for ascent or decrease lift for descent.
Such conventional methods and systems have generally been considered satisfactory for their intended purpose. However, there is still a need in the art for improved systems and methods for controlling rotorcraft. The present disclosure provides a solution for this need.
SUMMARY OF THE INVENTION
A method of rotorcraft state control includes receiving command input indicative of an intended state change in a rotorcraft. The method also includes issuing command output to a rotor actuation system to carry out the intended state change by varying drag and/or efficiency on one or more rotor blades of the rotorcraft. Issuing command output can include issuing a command output to the rotor actuation system to carry out the intended state change by increasing drag at a substantially constant thrust on one or more rotor blades of the rotorcraft.
The intended state change can include a horizontal translation of the rotorcraft, a change in speed of the rotorcraft, or and/or a change in trim attitude of the rotorcraft, and issuing command output can include issuing command output to the rotor actuation system to control rotor drag as a function of azimuthal blade position cyclically to carry out the horizontal translation. Command output can be issued to the rotor actuation system to control rotor pitch cyclically to counter aircraft rotation in any combination of roll and pitch induced by controlling rotor drag and to control tail rotor thrust to counter increased torque on the main rotor due to increased main rotor drag. Countering aircraft rotation can include maintaining substantially constant heading and aircraft attitude in forward or rearward flight while laterally translating to a new track line. It is also contemplated that countering aircraft rotation can include maintaining a substantially constant heading and aircraft attitude while translating to a new position in hover. Receiving command input can include receiving a command to enter drag translation mode prior to receiving command input indicative of an intended state change and issuing command output. It is also contemplated that receiving a command to enter drag translation mode can include selecting whether drag translation mode should be entered based on at least one of pilot input, auto-pilot input, and data regarding aircraft state.
In another aspect, receiving command input can include receiving a command to enter a power delivery response mode prior to receiving command input indicative of an intended state change and issuing command output. The intended state change can include entering a power delivery response mode, and issuing command output can include issuing command output to the rotor actuation system to control rotor drag for an intended power delivery response. The method can include monitoring power demand and rotor speed, wherein issuing command output includes issuing command output to the rotor actuation system to vary rotor drag to maintain substantially constant power output from a power plant powering the rotor blades.
The method can include monitoring frequency and amplitude at which power is being demanded by the rotorcraft by monitoring at least one of power, torque, rotor speed (NR), or power plant state parameters including speed, temperature or amperage; and actively managing fluctuations in power required by issuing command output to a rotor actuation system to vary drag and/or efficiency on one or more rotor blades of the rotorcraft to ensure the power plant can deliver power at the required frequency and/or amplitude. The method can include monitoring ambient conditions, determining whether the rotorcraft is in an ambient condition in which the power plant would have an unsatisfactory power-delivery response, and if so, commanding extra steady state drag and/or reduced rotor system efficiency on the rotor to drive an increase in power required such that a combination of natural power plant power response rate and a rate at which drag power is shed can meet a satisfactory power-delivery response. In another aspect, the method can include monitoring rotorcraft state parameters and a predefined minimum desired power plant state, and commanding an increase of rotor drag and/or reduced rotor system efficiency such that power plant state parameters do not fall below a predefined threshold.
In another aspect, receiving command input can include receiving a command to enter an overspeed protection mode prior to receiving command input indicative of an intended state change and issuing command output. The method can include monitoring at least one of rotor speed, aircraft pitch, and/or control commands and/or rates for cyclic and/or collective, and increasing rotor drag and/or reducing rotor efficiency to prevent rotor overspeed in response to rotor speed approaching overspeed. Issuing command output can include issuing command output to the rotor actuation system to apply differential cyclic to two coaxial, counter-rotating rotor systems in a coaxial rotorcraft
An aircraft includes a rotor system including blades to provide thrust for the aircraft at a rotor efficiency, a power system which powers the rotor system at a power output level, a controller, e.g., a drag controller, which selectively changes a rotor efficiency of the rotor system to change a rotor system state of the aircraft without changing the power output level. The drag controller can include machine readable instructions for carrying out any of the methods and/or modes described above.
These and other features of the systems and methods of the subject disclosure will become more readily apparent to those skilled in the art from the following detailed description of the preferred embodiments taken in conjunction with the drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
So that those skilled in the art to which the subject disclosure appertains will readily understand how to make and use the devices and methods of the subject disclosure without undue experimentation, preferred embodiments thereof will be described in detail herein below with reference to certain figures, wherein:
<figref idref="DRAWINGS">FIG. 1</figref> is a schematic side elevation view of an exemplary embodiment of a rotorcraft constructed in accordance with the present disclosure, showing a drag controller and actuation system;
<figref idref="DRAWINGS">FIG. 2</figref> is a schematic plan view of the rotorcraft of <figref idref="DRAWINGS">FIG. 1</figref>, indicating drag vectors for horizontal translation;
<figref idref="DRAWINGS">FIGS. 3A and 3B</figref> are diagrams for an exemplary embodiment of power delivery response modes for the rotorcraft of <figref idref="DRAWINGS">FIG. 1</figref>;
<figref idref="DRAWINGS">FIG. 4</figref> is a diagram for an exemplary embodiment of an overspeed protection mode for the rotorcraft of <figref idref="DRAWINGS">FIG. 1</figref>;
<figref idref="DRAWINGS">FIG. 5A</figref> is a schematic side elevation view of an exemplary embodiment of a coaxial counter-rotating rotorcraft in accordance with the present disclosure, showing opposed cyclic control of the two counter-rotating main rotors for horizontal control of the rotorcraft; and
<figref idref="DRAWINGS">FIGS. 5B and 5C</figref> are schematic plan views of the lower and upper main rotors of <figref idref="DRAWINGS">FIG. 5A</figref>, respectively, showing the delta drag vectors for horizontal translation of the rotorcraft.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
Reference will now be made to the drawings wherein like reference numerals identify similar structural features or aspects of the subject disclosure. For purposes of explanation and illustration, and not limitation, a partial view of an exemplary embodiment of a rotorcraft in accordance with the disclosure is shown in <figref idref="DRAWINGS">FIG. 1</figref> and is designated generally by reference character <b>100</b>. Other embodiments of rotorcraft in accordance with the disclosure, or aspects thereof, are provided in <figref idref="DRAWINGS">FIGS. 2-5C</figref>, as will be described. The systems and methods described herein can be used to control rotorcraft state by controlling drag on the rotor blades, although it is understood that other mechanisms can be used to create the on blade force differentials.
A method of rotorcraft control includes receiving command input indicative of an intended state change in a rotorcraft <b>100</b>. The command input is indicated schematically in <figref idref="DRAWINGS">FIG. 1</figref> by arrow <b>102</b>, and can be input, e.g., from a pilot, crew member, operator, flight computer, autopilot system, or the like, into drag controller <b>104</b>. Drag controller <b>104</b> issues command output, indicated by arrow <b>106</b> in <figref idref="DRAWINGS">FIG. 1</figref>, to a rotor actuation system <b>108</b> to carry out the intended state change by increasing and/or decreasing drag and/or efficiency on one or more rotor blades <b>110</b> of rotorcraft <b>100</b>. Rotor actuation system <b>108</b> includes actuators for drag system <b>112</b>, and optionally for the main rotor actuators for collective and cyclic control. Drag controller <b>104</b> includes machine readable instructions for carrying out any of the methods and/or modes described herein, and can be incorporated as a module in an engine control unit, flight control computer, or the like, e.g., to coordinate drag control, rotor system control, and power plant control as described in greater detail below.
Drag system <b>112</b> can include any suitable type of control surface or control scheme. It is advantageous for drag system <b>112</b> to controllably impart drag on rotor blades <b>110</b> at a substantially constant thrust. Such drag can be produced, for example if drag system <b>112</b> includes air-brakes, drag surfaces on the rotor blades which increase drag at a relatively constant thrust, spoilers, trim tabs, or the like. Drag system <b>112</b> can advantageously be configured to increase drag while reducing lift, and the drag surfaces can be used in combination with cyclic and collective control of rotor blades <b>110</b> as needed to generate control over drag with a relatively constant level of thrust. It is entirely possible that in certain of the above embodiments of drag system <b>112</b>, increasing drag can increase blade pitching movement at constant thrust. For example, actuation system <b>108</b> can have authority to control cyclic and collective action of rotor blades <b>110</b> and to control tail thrust of tail rotor blades <b>111</b> as well as to control drag system <b>112</b> to implement the modes and methods described herein. By these mechanisms, command output can include issuing a command output to rotor actuation system <b>108</b> to carry out the intended state change by varying drag at a substantially constant main rotor thrust on one or more rotor blades <b>110</b> of rotorcraft <b>100</b>. While described in terms of the drag system <b>112</b> increasing drag, it is understood that the drag system <b>112</b> could also create localized drag reductions as opposed to localized drag increases, such as through selective blowing of air over the blade <b>110</b> whereby the drag increase would be caused by selective reduction of the drag reduction device.
With reference now to <figref idref="DRAWINGS">FIG. 2</figref>, the intended state change can include a horizontal translation of rotorcraft <b>100</b>, and issuing command output, e.g., from drag controller <b>104</b>, can include issuing command output to rotor actuation system <b>108</b> to control rotor drag as a function of azimuthal blade position cyclically to carry out the horizontal translation. The disc in <figref idref="DRAWINGS">FIG. 2</figref> represents rotating blades <b>110</b>, and the large arrows <b>101</b> indicate incremental drag vectors that vary with azimuth due to cyclic control of drag system <b>112</b> on blades <b>110</b>. This increase in rotor drag will result in an increase in main rotor torque which must be counteracted by an incremental tail rotor thrust vector <b>105</b> in order to maintain heading. In this example, the portions or components of the drag vectors <b>101</b> oriented along the axis A in <figref idref="DRAWINGS">FIG. 2</figref> cancel each other out. However, summing the horizontal vector components of the drag vectors <b>101</b> aligned along axis B with incremental tail rotor thrust vector <b>105</b> yields a bulk vector <b>103</b> aligned with axis B in <figref idref="DRAWINGS">FIG. 2</figref>. In other words, the cumulative effect of the drag vectors <b>101</b> and incremental tail rotor thrust <b>105</b> is a net drag vector <b>103</b> as shown in <figref idref="DRAWINGS">FIG. 2</figref>. This bulk vector <b>103</b> represents a force that will tend to translate rotorcraft <b>100</b> along axis B in the direction of bulk vector <b>103</b> in <figref idref="DRAWINGS">FIG. 2</figref>. The sum of drag vectors <b>101</b> will not always need to be selected to align with the incremental tail rotor thrust vector <b>105</b> and the cyclic control of drag system <b>112</b> can thus be varied to generate a net or bulk drag force vector in any direction of the azimuth, so drag controller <b>104</b> can cause horizontal translation of rotorcraft <b>100</b> in any direction from a hover, for example. In level flight, the cyclic control of drag system <b>112</b> can be varied to generate a net side force such that the ground track may be altered. It is also contemplated that the cyclic control of drag system <b>112</b> can be aligned with the longitudinal axis A of the rotorcraft <b>100</b> to enable the rotorcraft <b>100</b> to adjust speed.
Due to the fact that the drag forces acting on drag system <b>112</b> are above the center of gravity of rotorcraft <b>100</b>, some combination of roll and/or pitch may result when the intended state change is a horizontal translation as described above. To counter this, command output can be issued to the rotor actuation system to control rotor pitch cyclically to counter aircraft rotation in any combination of roll and pitch induced by controlling rotor drag. This can allow for maintaining substantially constant attitude and heading in level, climbing, and descending forward or rearward flight while laterally translating to a new track line and/or adjusting speed. It is also contemplated that countering aircraft rotation can include maintaining a substantially constant aircraft attitude while translating in hover, for example for precise maneuvering for external load operations, hoist operations, landing or takeoff, for example. It is also contemplated that the aircraft pitch and roll attitude can be trimmed to a selected value in order to increase or decrease trim pitch and roll attitude to accommodate a given aircraft operational need. For example, roll trim can be decreased in a cross-wind so an external hoist line will not rub up against the airframe while hoisting a load up or down.
Receiving command input can include receiving a command to enter drag translation mode for maneuvering as described above prior to receiving command input indicative of an intended state change and issuing command output. It is also contemplated that receiving a command to enter drag translation mode can include selecting whether drag translation mode should be entered based on at least one of pilot input, crew input, operator input, auto-pilot input, and data regarding aircraft state. For example, a hat button, dials, or the like can be included on the cyclic stick to allow the pilot to input maneuver commands in drag translation mode. In another exemplary embodiment, the cyclic stick can be configured so that small motions near the neutral position are issued as drag translation mode maneuver commands, and large motions and/or motions of the cyclic stick farther from the neutral positions are issued as normal cyclic control commands.
Referring now to <figref idref="DRAWINGS">FIGS. 3A and 3B</figref>, receiving command input can include receiving a command to enter a power delivery response mode prior to receiving command input indicative of an intended state change and issuing command output. The intended state change can include having drag controller <b>104</b> enter a power delivery response mode. In this mode, command output is issued from drag controller <b>104</b> to rotor actuation system <b>108</b> to control rotor drag for an intended power delivery response. This can include monitoring power demand, pilot control inputs, automated control inputs, and/or rotor speed, wherein issuing command output includes issuing command output to rotor actuation system <b>108</b> to vary rotor drag to maintain substantially constant power output from a power plant, e.g., the engine E of rotorcraft <b>100</b>, powering the rotor blades <b>110</b>.
The diagram in <figref idref="DRAWINGS">FIG. 3A</figref> illustrates a power demand curve that varies over time, wherein time extends along the horizontal axis and power is represented along the vertical axis. Since power demand varies over time, the power output of the power plant can be held constant, as indicated by the horizontal line plotted in <figref idref="DRAWINGS">FIG. 3A</figref>, by varying the amount of drag on drag system <b>112</b> collectively, so that at any point in time the power required, represented by arrow <b>114</b>, and the power shed by drag system <b>112</b>, i.e., the managed power losses represented by arrow <b>116</b>, add up to a constant amount of power from the power plant. <figref idref="DRAWINGS">FIG. 3B</figref> shows another example, where power plant power delivery is not constant, but is considerably more constant than power demand.
In the power delivery response mode, drag controller <b>104</b> can monitor frequency and amplitude at which power is being demanded by the rotorcraft by monitoring at least one of power, torque, rotor speed (NR), control inputs, or power plant state parameters including speed, temperature or amperage. Drag controller <b>104</b> can use these monitored parameters for actively managing fluctuations in power required by issuing command output to rotor actuation system <b>108</b> to vary drag on one or more rotor blades <b>110</b> of the rotorcraft to ensure the power plant can deliver power at the required frequency and/or amplitude and/or to reduce the frequency and/or amplitude of power fluctuation demands from the power plant. In this manner, when additional power is required in the power delivery response mode, the drag controller <b>104</b> would decrease the drag which would increase the power available <b>114</b> and decrease the power shed <b>116</b> without changing the demands on the power plant. Conversely, when less power is required in the power delivery response mode, the drag controller <b>104</b> would increase the drag which would decrease the power available <b>114</b> and increase the power shed <b>116</b> without changing the demands on the power plant.
Drag controller <b>104</b> can also monitor ambient conditions, determine whether rotorcraft <b>100</b> is in an ambient condition in which the power plant would have an unsatisfactory power-delivery response, and if so, command extra steady state drag on the rotor to drive an increase in power required such that a combination of natural power plant power response rate and a rate at which drag power is shed together can meet a satisfactory power-delivery response. For example, this can ensure compliance with regulations for minimum power response even outside the envelope that would normally be possible without drag control as set forth herein. In another aspect, the method can include monitoring rotorcraft state parameters and a predefined minimum desired power plant state, and commanding an increase of rotor drag such that power plant state parameters do not fall below a predefined threshold.
Those skilled in the art will readily appreciate that it is not necessary for the power delivery response mode to maintain a strictly constant power level from the power plant. A complimentary filtering can be accomplished by drag controller <b>104</b>, wherein drag controller <b>104</b> manages fluctuations in power required at the high fluctuation rates such that the power plant can manage power required fluctuations at lower fluctuation rates as shown in <figref idref="DRAWINGS">FIG. 3B</figref>. In this manner, when additional power is required in the power delivery response mode, the drag controller <b>104</b> would decrease the drag which would increase the power available <b>114</b> and decrease the power shed <b>116</b> while ensuring that the demands on the power plant are within the power level being delivered at that time. Conversely, when less power is required in the power delivery response mode, the drag controller <b>104</b> would increase the drag which would decrease the power available <b>114</b> and increase the power shed <b>116</b> while ensuring that the demands on the power plant are within the power level being delivered at that time.
Referring now to <figref idref="DRAWINGS">FIG. 4</figref>, drag controller <b>104</b> can receive a command to enter an overspeed protection mode prior to receiving command input, e.g., from a pilot, crew member, operator, autopilot, or the like, indicative of an intended state change. In the overspeed protection mode, controller <b>104</b> monitors rotor speed (NR), and increases rotor drag by commanding rotor actuation system <b>108</b> to collectively control drag system <b>112</b>, to prevent rotor overspeed in response to rotor speed approaching the overspeed threshold. Secondary monitoring of aircraft state such as attitude, pitch/roll rate, speed, as well as control input, and/or control input rate for collective and/or cyclic can also be used, e.g., to refine the command of rotor actuation system <b>108</b>. An example of where this overspeed condition can exist is during autorotation and autorotation flares when the rotor (e.g., the blade <b>110</b>, the rotor system, and transmission elements) is generating power and the rotor may be decoupled from the engine E operating at a speed above the nominal operating speed of the rotorcraft. In <figref idref="DRAWINGS">FIG. 4</figref>, the dashed line <b>118</b> represents a nominal rotor speed (NR), and the dashed line <b>120</b> represents a maximum rotor speed (NR) beyond which an overspeed condition arises. The upper curve <b>122</b> represents a hypothetical rotor speed (NR) as a function of time without drag control, and the lower curve <b>124</b> represents a corresponding hypothetical rotor speed (NR) curve with drag controller <b>104</b> in overspeed protection mode. As shown in <figref idref="DRAWINGS">FIG. 4</figref>, as the rotor speed (NR) approaches the maximum rotor speed (NR), drag is applied by the drag controller <b>104</b> by activating the drag system <b>112</b> to suppress the rotor speed (NR) to not exceed the maximum, and the process is reversed as rotor speed (NR) returns towards nominal.
Referring now to <figref idref="DRAWINGS">FIG. 5A</figref>, drag controller <b>104</b> can be used to control a coaxial rotorcraft <b>500</b> horizontal position in a similar manner as is done for rotorcraft <b>100</b>, e.g., by way of a rotor actuation system connected to control the coaxial rotors; however, the rotor drag control may alternately or additionally be accomplished using differential cyclic in the top and bottom rotors of coaxial rotorcraft <b>500</b>. <figref idref="DRAWINGS">FIG. 5A</figref> presents a side view of a coaxial helicopter with axis A aligned with the longitudinal axis of the coaxial rotorcraft <b>500</b>. The change in out-of plane main rotor thrust on the top and bottom rotors due to application of differential cyclic are shown as main rotor delta thrusts <b>511</b>, <b>521</b>, <b>514</b>, and <b>524</b>. The differential cyclic main rotor delta thrusts are applied in a manner such that the delta thrusts <b>511</b> and <b>521</b> cancel and the delta thrusts <b>514</b> and <b>524</b> cancel each other. As such, the differential cyclic is applied in a manner which results in relatively constant main rotor thrust as well as moment balance in pitch and roll. <figref idref="DRAWINGS">FIG. 5B</figref> presents a top-down schematic view of the drag on the bottom rotor system <b>520</b> rotating counter-clockwise as shown by bottom rotor speed <b>529</b> with a differential cyclic applied with an increased differential blade pitch <b>525</b> applied on the forward portion of the bottom rotor system <b>520</b> and a decreased differential blade pitch <b>522</b> applied on the aft portion of the bottom rotor <b>520</b>. Similarly, <figref idref="DRAWINGS">FIG. 5B</figref> shows a schematic top-down view of the drag on the top rotor system <b>510</b> rotating clockwise as shown by top rotor speed <b>519</b> with a differential cyclic applied with a decreased differential blade pitch <b>515</b> applied on the forward portion of the bottom rotor <b>510</b> and an increased differential blade pitch <b>512</b> applied on the aft portion of the bottom rotor system <b>510</b>.
Following the application of cyclic and resultant forces, it is seen that delta thrust <b>524</b> of <figref idref="DRAWINGS">FIG. 5A</figref> is attained by applying cyclic and increasing blade pitch <b>525</b> on the forward portion of the lower rotor which results in a delta forces <b>526</b> which are aligned opposite to the direction of rotation as shown in <figref idref="DRAWINGS">FIG. 5B</figref>. Similarly, delta thrust <b>521</b> is attained by applying cyclic and decreasing blade pitch <b>522</b> on the aft portion of the lower rotor which results in a decrease in drag as indicated by delta forces <b>523</b> which are aligned with the direction of rotation of bottom rotor system <b>520</b> and which sum with delta forces <b>526</b> to be aligned with axis B as shown in <figref idref="DRAWINGS">FIG. 5B</figref>. Normally, a cyclic force applied as <b>521</b> and <b>524</b> would result in a pitching response of the coaxial rotorcraft <b>500</b>; however, in this configuration, an opposite cyclic force, e.g., a differential cyclic, is applied to the upper rotor such that there is both force and moment balance as described above for rotorcraft <b>500</b>. Continuing the above discussion following the application of cyclic and resultant forces to <figref idref="DRAWINGS">FIG. 5C</figref>, it can be seen that as the upper rotor rotates in the opposite direction as indicated by upper rotor speed <b>519</b>, the application of cyclic to adjust blade pitch change <b>512</b> and <b>515</b> to oppose blade pitch change <b>522</b> and <b>525</b> of <figref idref="DRAWINGS">FIG. 5B</figref>, result in delta drag forces <b>516</b> and <b>513</b> which also sum to be aligned with axis B. Therefore, by applying differential cyclic aligned with axis A, a net drag force may be attained aligned with axis B, and this can be accomplished with or without a drag system <b>112</b> as described above.
As was described for rotorcraft <b>100</b>, axis A is not limited to be aligned with any particular body axis of the coaxial rotorcraft <b>500</b> and was shown as aligned with the longitudinal axis of coaxial rotorcraft <b>500</b> for ease of illustration. As such, applying differential cyclic along any selected axis A may allow the net drag forces along long axis B be used for translation along axis B, speed control along axis B, or coupled with cyclic to trim aircraft attitude in hover, low-speed flight or high-speed flight.
Additionally, when a high power mode is desired such as that described in <figref idref="DRAWINGS">FIGS. 3A and 3B</figref>, coaxial rotorcraft <b>500</b> may apply differential cyclic to reduce rotor efficiency. It is noted that in <figref idref="DRAWINGS">FIGS. 5A-5C</figref> that the differential cyclic is used in a manner which reduces drag on the aft portion of the rotor by reducing blade pitch <b>522</b> while increasing blade pitch <b>525</b> on the forward portion of the rotor. For small applications of cyclic, the net change in power is nominally zero. However, when large applications of cyclic are used, rotor efficiency suffers resulting in an increase in power required at a constant net thrust summing up the individual delta thrust <b>521</b> and delta thrust <b>524</b> for the lower rotor <b>520</b>. Additionally, in the extreme, when large enough cyclic applications are used and the delta thrust <b>521</b> is greater than the thrust generated by the aft portion of the bottom rotor <b>520</b>, then it can be seen that the aft portion of bottom rotor system <b>520</b> generates a downforce which must be overcome by application of additional power. As such, if axis A is aligned with the lateral axis of the coaxial rotorcraft <b>500</b> in level flight (i.e. using differential lateral cyclic), the retreating blades may be forced into a negative thrust state as opposed to a feathered state in order to increase power required. It is also contemplated that a non-optimal condition may be managed with differential cyclic wherein the retreating blade is not feathered to a minimum power state in order to allow reduced efficiency and increased power required. This increased power required from a known minimum power required state may be managed with differential cyclic through drag controller <b>104</b> to attain the benefits discussed above with respect to <figref idref="DRAWINGS">FIG. 3</figref>, but for coaxial rotorcraft <b>500</b> which may or may not be equipped with drag system <b>112</b>.
Additionally, for the purposes of providing overspeed protection as described above with respect to <figref idref="DRAWINGS">FIG. 4</figref> for coaxial rotorcraft <b>500</b>, differential cyclic may be applied to increase power required similar to that which was discussed for the coaxial rotorcraft in relation to <figref idref="DRAWINGS">FIG. 3</figref>, but for the purposes of preventing rotor overspeed as in <figref idref="DRAWINGS">FIG. 4</figref>.
Those skilled in the art will readily appreciate that the modes described herein can be used together or separately. While shown and described in the exemplary context of a rotorcraft <b>100</b> that is a conventional helicopter, those skilled in the art will readily appreciate that the methods and systems described herein can readily be applied to any suitable type of rotorcraft, including rotorcraft with coaxial main rotors, tiltwing rotorcraft, tandem rotorcraft, and the like.
For brevity and clarity, embodiments described herein discussed reducing efficiency. To those skilled in the art, it will be readily appreciated that many of the modes of operation discussed herein may also be accomplished by increasing the rotor system's efficiency. Such increases in efficiency may be achieved via any number of existing rotor technologies including, but not limited to, active rotor control, individual blade control, and blown wing designs. As such, the term “drag translation mode” described herein refers to a translation mode which adjusts the drag and/or efficiency to either up or down as appropriate for aircraft design and desired mode of operation.
Increasing drag to provide the control described herein can potentially reduce efficiency, e.g., increasing fuel consumption. However, advantages provided by the various embodiments can include reduction of engine cycling, prevention of overspeed conditions, improved power response including an expanded flight envelope, and improved maneuvering.
The methods and systems of the present disclosure, as described above and shown in the drawings, provide for rotorcraft control with superior properties as described above. While described in terms of a main rotor blade system for purposes of example, it is understood that aspects can be used in other blade systems, including tail rotors, propulsor rotors, propellers, maritime propellers, wind turbines and the like. While the apparatus and methods of the subject disclosure have been shown and described with reference to preferred embodiments, those skilled in the art will readily appreciate that changes and/or modifications may be made thereto without departing from the scope of the subject disclosure.
Contents5
6 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US12437668B2 | Cited by | United States of America | Search report |
| US2024404424A1 | Cited by | United States of America | Search report |
| EP0631930A1 | Cites | European Patent Office (EPO) | Applicant |
| US2010014981A1 | Cites | United States of America | Search report |
| US2010224720A1 | Cites | United States of America | Search report |
| US2011211959A1 | Cites | United States of America | Search report |
| US2012153073A1 | Cites | United States of America | Search report |
| US2013134256A1 | Cites | United States of America | Search report |
| US2014252158A1 | Cites | United States of America | Search report |
| US3559927A | Cites | United States of America | Applicant |
| US3794273A | Cites | United States of America | Search report |
| US4319722A | Cites | United States of America | Applicant |
| US4585391A | Cites | United States of America | Search report |
| US4786014A | Cites | United States of America | Applicant |
| US4958289A | Cites | United States of America | Search report |
| US5588618A | Cites | United States of America | Search report |
| US5634611A | Cites | United States of America | Search report |
| US5687930A | Cites | United States of America | Applicant |
| US6497385B1 | Cites | United States of America | Search report |
| US7025304B2 | Cites | United States of America | Applicant |
| US8052094B2 | Cites | United States of America | Search report |
| US8790081B1 | Cites | United States of America | Search report |
| US8944365B2 | Cites | United States of America | Search report |
| US8955801B2 | Cites | United States of America | Applicant |
| US9193453B2 | Cites | United States of America | Search report |
| US9604722B1 | Cites | United States of America | Search report |
| US20100014981A1 | Cites | United States of America | Search report |
| US20100224720A1 | Cites | United States of America | Search report |
| US20110211959A1 | Cites | United States of America | Search report |
| US20120153073A1 | Cites | United States of America | Search report |
| US20130134256A1 | Cites | United States of America | Search report |
| US20140252158A1 | Cites | United States of America | Search report |
| EP631930A1 | Cites | European Patent Office (EPO) | Applicant |
2 members in 1 office
Priority claims6
| Document | Office | Kind | Date |
|---|---|---|---|
| 201562210709 | United States of America | P | |
| 201562210709 | United States of America | P | |
| 201615248753 | United States of America | A | |
| 62210709 | – | – | – |
| US201562210709P | – | – | – |
| US201615248753 | – | – | – |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2017190416A1 | United States of America | A1 | |
| US9944388B2This record | United States of America | B2 |
57 transactions on the USPTO file
Allowed without a rejection on record.
- Non-final rejections
- 0
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail First Action Interview Office ActionMFAIA | MFAIA | |
| Pilot-First Action Interview Office Action (FAI Step 2)FAIA | FAIA | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response to PICO-no interviewNPICO | NPICO | |
| Letter Requesting Interview with ExaminerM865 | M865 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Pre-Interview CommunicationMPICO | MPICO | |
| Pre-Interview Communication (FAI Step 1)PICO | PICO | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Email NotificationEML_NTR | EML_NTR | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| PG-Pub Notice of new or Revised projected publication datePG-PB-DT | PG-PB-DT | |
| Sent to Classification ContractorPGPC | PGPC | |
| Receipt of all Acknowledgement LettersL130 | L130 | |
| Receipt of Acknowledgment LetterL197 | L197 | |
| Email NotificationEML_NTR | EML_NTR | |
| Application Is Now CompleteCOMP | COMP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Waiting LR clearancePGPW | PGPW | |
| FITF set to YES - revise initial settingFTFS | FTFS | |
| Referred to Level 2 (LARS) by OIPE CSRL198 | L198 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Entity Status Set To Undiscounted (Initial Default Setting or Status Change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
4 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 09944388
- Publication, DOCDB
- 9944388
- Publication, EPODOC
- US9944388
- Application
- 15248753
- Application, DOCDB
- 201615248753
- Application, EPODOC
- US201615248753
Titles
- English
- Rotorcraft state control
Patent term adjustment
- Net adjustment
- 0 days
Classification
- CPC, 6
- B64C27/57
- B64C27/32
- B64C27/72
- B64C27/82
- B64C2027/7266
- Y02T50/30
- IPC, 3
- B64C27 57
- B64C27 82
- B64C27 32
- USPC, 2
- 244017190
- 001001000