Patent Description:
A rotorcraft may include one or more rotor systems including one or more main rotor systems. A main rotor system generates aerodynamic lift to support the weight of the rotorcraft in flight and thrust to move the rotorcraft in forward flight. Another example of a rotorcraft rotor system is a tail rotor system. A tail rotor system may generate thrust in the same direction as the main rotor system's rotation to counter the torque effect created by the main rotor system. For smooth and efficient flight in a rotorcraft, a pilot balances the engine power, main rotor collective thrust, main rotor cyclic thrust and the tail rotor thrust, and a control system may assist the pilot in stabilizing the rotorcraft and reducing pilot workload.

<CIT> discloses a method and apparatus for tactile cueing of aircraft controls. The apparatus of the present invention warns pilots of approaching limits on certain aircraft performance parameters. The most common warnings are for rotor speed exceeding a moving limit. The present invention uses tactile cueing through the collective stick. Tactile cueing means that the pilot does not need to scan the instruments to ascertain proximity to the aforementioned limits. Instead, the pilot can operate the aircraft within proper limits by touch, while maintaining situational awareness outside of the cockpit. The method and apparatus of the present invention provides customary friction resistance up to a limit position that is continuously updated. According to the present invention, continued motion of the collective (<NUM>) in a direction beyond that limit position results in a breakout force and an increasing resistive force.

<CIT> discloses a method and apparatus for a split detent tactile cueing control system comprising an inceptor, a position sensor, vehicle sensors, and a flight control computer. The inceptor can be moved into different positions measured by a position sensor. The vehicle sensors generate signals in response to detecting parameters about a vehicle during a flight. The flight control computer is coupled to the inceptor and the vehicle sensors. The flight control computer is capable of generating actuation signals used to generate tactile cues to generate a flight path hold detent and an altitude hold detent within the plurality of positions using a force feel profile and the parameters. An extension of a latch force from the flight path hold detent to the altitude hold detent is present during changes in vehicle direction. Series actuator compensation allows increased split detent separation with insignificant command overshoot.

<CIT> discloses a flight control system having a control law, the control law operable to generate a modified pitch command, the modified pitch command representing a greater amount of collective pitch compared to an amount of collective pitch generated by a first pitch command, the modified pitch command being generated because a vertical descent speed of the rotorcraft at a given forward airspeed is greater than a threshold. A method of avoiding entry into an undesired vertical descent speed region during operation of a rotorcraft, including measuring a forward airspeed; evaluating a vertical descent of the rotorcraft; and generating a modified collective pitch command in respond to a first collective pitch command having a collective pitch value that would cause the rotorcraft to experience a vertical descent rate greater than a threshold value at the forward airspeed of the rotorcraft.

The scope of the invention is set out in the appended independent claims. The dependent claims provide optional features.

An embodiment flight control computer (FCC) for a rotorcraft is defined in appended claim <NUM>.

An embodiment method for operating a rotorcraft is defined in appended claim <NUM>.

Illustrative embodiments of the system and method of the present disclosure are described below. In the interest of clarity, all features of an actual implementation may not be described in this specification. It will of course be appreciated that in the development of any such actual embodiment, numerous implementation-specific decisions may 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 should be appreciated that such a development effort might be complex and time-consuming but would nevertheless be a routine undertaking for those of ordinary skill in the art having the benefit of this disclosure.

Reference may be made herein 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, etc. 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.

The increasing use of rotorcraft, in particular, for commercial and industrial applications, has led to the development of larger more complex rotorcraft. However, as rotorcraft become larger and more complex, the differences between flying rotorcraft and fixed wing aircraft has become more pronounced. Since rotorcraft use one or more main rotors to simultaneously provide lift, control attitude, control altitude, and provide lateral or positional movement, different flight parameters and controls are tightly coupled to each other, as the aerodynamic characteristics of the main rotors affect each control and movement axis. For example, the flight characteristics of a rotorcraft at cruising speed or high speed may be significantly different than the flight characteristics at hover or at relatively low speeds. Additionally, different flight control inputs for different axes on the main rotor, such as cyclic inputs or collective inputs, affect other flight controls or flight characteristics of the rotorcraft. For example, pitching the nose of a rotorcraft forward to increase forward speed will generally cause the rotorcraft to lose altitude. In such a situation, the collective may be increased to maintain level flight, but the increase in collective requires increased power at the main rotor which, in turn, requires additional anti-torque force from the tail rotor. This is in contrast to fixed wing systems where the control inputs are less closely tied to each other and flight characteristics in different speed regimes are more closely related to each other.

Recently, fly-by-wire (FBW) systems have been introduced in rotorcraft to assist pilots in stably flying the rotorcraft and to reduce workload on the pilots. The FBW system may provide different control characteristics or responses for cyclic, pedal or collective control input in the different flight regimes, and may provide stability assistance or enhancement by decoupling physical flight characteristics so that a pilot is relieved from needing to compensate for some flight commands issued to the rotorcraft. FBW systems may be implemented in one or more flight control computers (FCCs) disposed between the pilot controls and flight control systems, providing corrections to flight controls that assist in operating the rotorcraft more efficiently or that put the rotorcraft into a stable flight mode while still allowing the pilot to override the FBW control inputs. The FBW systems in a rotorcraft may, for example, automatically adjust power output by the engine to match a collective control input, apply collective or power correction during a cyclic control input, provide automation of one or more flight control procedures provide for default or suggested control positioning, or the like.

FBW systems for rotorcraft must provide stable flight characteristics for FBW controlled flight parameters while permitting the pilot to override or work with any suggested flight parameters suggested by the FBW system. Additionally, in providing enhanced control and automated functionality for rotorcraft flight, the FBW must maintain an intuitive and easy to use flight control system for the pilot. Thus, the FBW system adjusts the pilot flight controls so that the controls are in a position associated with the relevant flight parameter. For example, the FBW system may adjust the collective stick to provide suggested or FBW controlled flight parameters, and which reflect a collective or power setting. Thus, when the pilot releases the collective stick and the FBW provides collective control commands, the collective stick is positioned intuitively in relation to the actual power or collective setting so that, when the pilot grasps the collective stick to retake control, the control stick is positioned where the pilot expects the stick to be positioned for the actual collective setting of the main rotor. Similarly, the FBW system use the cyclic stick to, for example, adjust for turbulence, drift or other disturbance to the flight path, and may move the cyclic stick as the FBW system compensates the cyclic control. Thus, when the pilot grasps the cyclic stick to take control of flight from the FBW system, the cyclic stick is positioned to reflect the actual cyclic settings.

Embodiments of the system presented herein are directed to providing a rotor overspeed protection function using a tactile cue through the pilot controls of a rotorcraft. In some embodiments, the FBW system measures the revolutions per minute (RPM) of the main rotor, and if the main rotor is in or approaching an overspeed condition, drives a collective stick of the rotorcraft to increase the collective and reduce the rotor RPM. The drive provides a force felt by the pilot in the collective stick so the pilot is cued to the rotor overspeed condition. The FBW system attempts to keep the main rotor speed or RPM substantially constant, or within a threshold related to the target RPM.

The FBW system attempts to drive the collective stick to a position that would create a stable flight position and maintain the main rotor speed within a desired threshold. In an embodiment, in the case of an RPM or overspeed condition, the FBW provides a reverse tactile cue to alert the pilot of the overspeed condition. A force cue driving the collective stick upwards to increase the collective angle of the main rotor blades may be used, and may be a soft stop that the pilot can push downward through. The pilot may override the drive of the collective stick, but will feel the force driving the collective. In some embodiments, the tactile cue for rotor overspeed protection is a continuously variable tactile feedback. Thus, the pilot may be cued to the rotor overspeed condition without requiring that the pilot monitor instruments in the cockpit.

A rotor overspeed condition is associated with the rotor RPM increasing by, for example, the pilot quickly lowering the collective or pitching the rotorcraft up rapidly. FBW systems, particularly when combined with a flexing rotor system, allow for lighter main rotor blades with less mass than, for example, blades of an articulated rotor. The lighter blades have less inertia than heavier blades, and are more easily accelerated by external forces. For example, when a pilot rapidly pitches the nose of the rotorcraft up during forward flight at low collective setting, the increased pitch of the rotorcraft causes increased airflow through the main rotor, rapidly increasing the speed or RPM of the main rotor. Overspeeding the rotor, or permitting the rotor to turn faster that the engine is driving the rotor, may cause damage to the main rotor drive system, and the overspeed protection acts as a tactile warning that the RPM is approaching a structural limit.

The connection between the main rotor and the engine is a one way drive. The main rotor is able to freewheel in the direction of rotation. Thus, the main rotor may accelerate to an RPM faster than the engine drives the main rotor blades. This arrangement permits autorotation by the main rotor blades in case of engine failure, since the main rotor uses a combination of inertia, forward and vertical airspeed and low collective pitch to maintain main rotor rotation. Additionally, the freewheel or one way drive connection between the main rotor and driveline permits the main rotor to maintain rotation should the transmission or engine failure lock or seize since the seized elements would not stop the rotation of the main rotor.

The FBW system attempts to maintain the main rotor at a predetermined rotor speed or within a rotor RPM range. In some embodiments, the rotorcraft may have one or more predetermined rotor speeds that are used in different flight modes. For example, a higher main rotor RPM may be used in a takeoff, hover, or landing flight mode than in a cruising flight mode, or a main rotor RPM for a low speed flight mode may be different than the main rotor RPM at a moderate or high speed flight mode. The FBW system does monitor the main rotor RPM, and determine whether the RPM is at, or approaching a preferred or target main rotor RPM or the boundaries of a threshold associated with the preferred or target main rotor RPM. For example, the FBW system may continuously monitor the engine speed and other operating parameters, and determine whether the main rotor speed, the rate of change of the main rotor speed, a combination of the main rotor speed and the rotor speed rate of change, or one or more other operating parameters indicate that the main rotor speed is outside of an target range or threshold related to the target main rotor RPM, or is predicted to move outside of the target range or threshold within a predetermined time period. The FBW system compare a determined target rotor speed with the actual or predicted rotor speed to identify or predict a rotor RPM overspeed condition. The FBW system then determines a collective stick position that would provide a stable flight position and reduce the main rotor to within acceptable limits. The FBW system then uses the actual collective stick position to control the collective setting of the main rotor. Using the actual collective stick position permits the pilot to override the collective stick position suggested or set by the FBW system, and avoid the FBW system needing to otherwise determine whether the pilot input or FBW collective positioning should be used for the collective setting.

<FIG> illustrates a rotorcraft <NUM> according to some embodiments. The rotorcraft <NUM> has a main rotor system <NUM>, which includes a plurality of main rotor blades <NUM>. The pitch of each main rotor blade <NUM> may be controlled by a swashplate <NUM> in order to selectively control the attitude, altitude and movement of the rotorcraft <NUM>. The swashplate <NUM> may be used to collectively and/or cyclically change the pitch of the main rotor blades <NUM>. The rotorcraft <NUM> also has an anti-torque system, which may include a tail rotor <NUM>, no-tail-rotor (NOTAR), or dual main rotor system. In rotorcraft with a tail rotor <NUM>, the pitch of each tail rotor blade <NUM> is collectively changed in order to vary thrust of the anti-torque system, providing directional control of the rotorcraft <NUM>. The pitch of the tail rotor blades <NUM> is changed by one or more tail rotor actuators. In some embodiments, the FBW system sends electrical signals to the tail rotor actuators or main rotor actuators to control flight of the rotorcraft.

Power is supplied to the main rotor system <NUM> and the anti-torque system by engines <NUM>. There may be one or more engines <NUM>, which may be controlled according to signals from the FBW system. The output of the engine <NUM> is provided to a driveshaft <NUM>, which is mechanically and operatively coupled to the rotor system <NUM> and the anti-torque system through a main rotor transmission <NUM> and a tail rotor transmission, respectively.

The rotorcraft <NUM> further includes a fuselage <NUM> and tail section <NUM>. The tail section <NUM> may have other flight control devices such as horizontal or vertical stabilizers, rudder, elevators, or other control or stabilizing surfaces that are used to control or stabilize flight of the rotorcraft <NUM>. The fuselage <NUM> includes a cockpit <NUM>, which includes displays, controls, and instruments. It should be appreciated that even though rotorcraft <NUM> is depicted as having certain illustrated features, the rotorcraft <NUM> may have a variety of implementation-specific configurations. For instance, in some embodiments, cockpit <NUM> is configured to accommodate a pilot or a pilot and co-pilot, as illustrated. It is also contemplated, however, that rotorcraft <NUM> may be operated remotely, in which case cockpit <NUM> could be configured as a fully functioning cockpit to accommodate a pilot (and possibly a co-pilot as well) to provide for greater flexibility of use, or could be configured with a cockpit having limited functionality (e.g., a cockpit with accommodations for only one person who would function as the pilot operating perhaps with a remote co-pilot or who would function as a co-pilot or back-up pilot with the primary piloting functions being performed remotely. In yet other contemplated embodiments, rotorcraft <NUM> could be configured as an unmanned vehicle, in which case cockpit <NUM> could be eliminated entirely in order to save space and cost.

<FIG> illustrates a fly-by-wire flight control system <NUM> for a rotorcraft according to some embodiments. A pilot may manipulate one or more pilot flight controls in order to control flight of the rotorcraft. The pilot flight controls may include manual controls such as a cyclic stick <NUM> in a cyclic control assembly <NUM>, a collective stick <NUM> in a collective control assembly <NUM>, and pedals <NUM> in a pedal control assembly <NUM>. Inputs provided by the pilot to the pilot flight controls may be transmitted mechanically and/or electronically (e.g., via the FBW flight control system) to flight control devices by the flight control system <NUM>. Flight control devices may represent devices operable to change the flight characteristics of the rotorcraft. Flight control devices on the rotorcraft may include mechanical and/or electrical systems operable to change the positions or angle of attack of the main rotor blades <NUM> and the tail rotor blades <NUM> or to change the power output of the engines <NUM>, as examples. Flight control devices include systems such as the swashplate <NUM>, tail rotor actuator <NUM>, and systems operable to control the engines <NUM>. The flight control system <NUM> may adjust the flight control devices independently of the flight crew in order to stabilize the rotorcraft, reduce workload of the flight crew, and the like. The flight control system <NUM> includes engine control computers (ECCUs) <NUM>, flight control computers (FCCs) <NUM>, and aircraft sensors <NUM>, which collectively adjust the flight control devices.

The flight control system <NUM> has one or more FCCs <NUM>. In some embodiments, multiple FCCs <NUM> are provided for redundancy. One or more modules within the FCCs <NUM> may be partially or wholly embodied as software and/or hardware for performing any functionality described herein. In embodiments where the flight control system <NUM> is a FBW flight control system, the FCCs <NUM> may analyze pilot inputs and dispatch corresponding commands to the ECCUs <NUM>, the tail rotor actuator <NUM>, and/or actuators for the swashplate <NUM>. Further, the FCCs <NUM> are configured and receive input commands from the pilot controls through sensors associated with each of the pilot flight controls. The input commands are received by measuring the positions of the pilot controls. The FCCs <NUM> also control tactile cues to the pilot controls or display information in instruments on, for example, an instrument panel <NUM>.

The ECCUs <NUM> control the engines <NUM>. For example, the ECCUs <NUM> may vary the output power of the engines <NUM> to control the rotational speed of the main rotor blades or the tail rotor blades. The ECCUs <NUM> may control the output power of the engines <NUM> according to commands from the FCCs <NUM>, or may do so based on feedback such as measured RPM of the main rotor blades.

The aircraft sensors <NUM> are in communication with the FCCs <NUM>. The aircraft sensors <NUM> may include sensors for measuring a variety of rotorcraft systems, flight parameters, environmental conditions and the like. For example, the aircraft sensors <NUM> may include sensors for measuring airspeed, altitude, attitude, position, orientation, temperature, airspeed, vertical speed, and the like. Other sensors <NUM> could include sensors relying upon data or signals originating external to the rotorcraft, such as a global positioning system (GPS) sensor, a VHF Omnidirectional Range sensor, Instrument Landing System (ILS), and the like.

The cyclic control assembly <NUM> is connected to a cyclic trim assembly <NUM> having one or more cyclic position sensors <NUM>, one or more cyclic detent sensors <NUM>, and one or more cyclic actuators or cyclic trim motors <NUM>. The cyclic position sensors <NUM> measure the position of the cyclic stick <NUM>. In some embodiments, the cyclic stick <NUM> is a single control stick that moves along two axes and permits a pilot to control pitch, which is the vertical angle of the nose of the rotorcraft and roll, which is the side-to-side angle of the rotorcraft. In some embodiments, the cyclic control assembly <NUM> has separate cyclic position sensors <NUM> that measuring roll and pitch separately. The cyclic position sensors <NUM> for detecting roll and pitch generate roll and pitch signals, respectively, (sometimes referred to as cyclic longitude and cyclic latitude signals, respectively) which are sent to the FCCs <NUM>, which controls the swashplate <NUM>, engines <NUM>, tail rotor <NUM> or related flight control devices.

The cyclic trim motors <NUM> are connected to the FCCs <NUM>, and receive signals from the FCCs <NUM> to move the cyclic stick <NUM>. In some embodiments, the FCCs <NUM> determine a suggested cyclic stick position for the cyclic stick <NUM> according to one or more of the collective stick position, the pedal position, the speed, altitude and attitude of the rotorcraft, the engine RPM, engine temperature, main rotor RPM, engine torque or other rotorcraft system conditions or flight conditions, or according to a predetermined function selected by the pilot. The suggested cyclic stick position is a positon determined by the FCCs <NUM> to give a desired cyclic action. In some embodiments, the FCCs <NUM> send a suggested cyclic stick position signal indicating the suggested cyclic stick position to the cyclic trim motors <NUM>. While the FCCs <NUM> may command the cyclic trim motors <NUM> to move the cyclic stick <NUM> to a particular position (which would in turn drive actuators associated with swashplate <NUM> accordingly), the cyclic position sensors <NUM> detect the actual position of the cyclic stick <NUM> that is set by the cyclic trim motors <NUM> or input by the pilot, allowing the pilot to override the suggested cyclic stick position. The cyclic trim motor <NUM> is connected to the cyclic stick <NUM> so that the pilot may move the cyclic stick <NUM> while the trim motor is driving the cyclic stick <NUM> to override the suggested cyclic stick position. Thus, in some embodiments, the FCCs <NUM> receive a signal from the cyclic position sensors <NUM> indicating the actual cyclic stick position, and do not rely on the suggested cyclic stick position to command the swashplate <NUM>.

Similar to the cyclic control assembly <NUM>, the collective control assembly <NUM> is connected to a collective trim assembly <NUM> having one or more collective position sensors <NUM>, one or more collective detent sensors <NUM>, and one or more collective actuators or collective trim motors <NUM>. The collective position sensors <NUM> measure the position of a collective stick <NUM> in the collective control assembly <NUM>. In some embodiments, the collective stick <NUM> is a single control stick that moves along a single axis or with a lever type action. A collective position sensor <NUM> detects the position of the collective stick <NUM> and sends a collective position signal to the FCCs <NUM>, which controls engines <NUM>, swashplate actuators, or related flight control devices according to the collective position signal to control the vertical movement of the rotorcraft. In some embodiments, the FCCs <NUM> may send a power command signal to the ECCUs <NUM> and a collective command signal to the main rotor or swashplate actuators so that the angle of attack of the main blades is raised or lowered collectively, and the engine power is set to provide the needed power to keep the main rotor RPM substantially constant.

The collective trim motor <NUM> is connected to the FCCs <NUM>, and receives signals from the FCCs <NUM> to move the collective stick <NUM>. Similar to the determination of the suggested cyclic stick position, in some embodiments, the FCCs <NUM> determine a suggested collective stick position for the collective stick <NUM> according to one or more of the cyclic stick position, the pedal position, the speed, altitude and attitude of the rotorcraft, the engine RPM, engine temperature, main rotor RPM, engine torque or other rotorcraft system conditions or flight conditions, or according to a predetermined function selected by the pilot. The FCCs <NUM> generate the suggested collective stick position and send a corresponding suggested collective stick signal to the collective trim motors <NUM> to move the collective stick <NUM> to a particular position. The collective position sensors <NUM> detect the actual position of the collective stick <NUM> that is set by the collective trim motor <NUM> or input by the pilot, allowing the pilot to override the suggested collective stick position.

The pedal control assembly <NUM> has one or more pedal sensors <NUM> that measure the position of pedals or other input elements in the pedal control assembly <NUM>. In some embodiments, the pedal control assembly <NUM> is free of a trim motor or actuator, and may have a mechanical return element that centers the pedals when the pilot releases the pedals. In other embodiments, the pedal control assembly <NUM> has one or more trim motors that drive the pedal to a suggested pedal position according to a signal from the FCCs <NUM>. The pedal sensor <NUM> detects the position of the pedals <NUM> and sends a pedal position signal to the FCCs <NUM>, which controls the tail rotor <NUM> to cause the rotorcraft to yaw or rotate around a vertical axis.

The cyclic and collective trim motors <NUM> and <NUM> may drive the cyclic stick <NUM> and collective stick <NUM>, respectively, to suggested positions. The cyclic and collective trim motors <NUM> and <NUM> may drive the cyclic stick <NUM> and collective stick <NUM>, respectively, to suggested positions, but this movement capability may also be used to provide tactile cueing to a pilot. The trim motors <NUM> and <NUM> may push the respective stick in a particular direction when the pilot is moving the stick to indicate a particular condition. Since the FBW system mechanically disconnects the stick from one or more flight control devices, a pilot may not feel a hard stop, vibration, or other tactile cue that would be inherent in a stick that is mechanically connected to a flight control assembly. In some embodiments, the FCCs <NUM> may cause the trim motors <NUM> and <NUM> to push against a pilot command so that the pilot feels a resistive force, or may command one or more friction devices to provide friction felt when the pilot moves the stick. Thus, the FCCs <NUM> control the feel of a stick by providing pressure and/or friction on the stick.

Additionally, the cyclic control assembly <NUM>, collective control assembly <NUM> and/or pedal control assembly <NUM> may each have one or more detent sensors that determine whether the pilot is handling a particular control device. For example, the cyclic control assembly <NUM> may have a cyclic detent sensor <NUM> that determines that the pilot is holding the cyclic stick <NUM>, while the collective control assembly <NUM> has a collective detent sensor <NUM> that determines whether the pilot is holding the collective stick <NUM>. These detent sensors <NUM>, <NUM> detect motion and/or position of the respective control stick that is caused by pilot input, as opposed to motion and/or position caused by commands from the FCCs <NUM>, rotorcraft vibration, and the like, and provide feedback signals indicative of such to the FCCs <NUM>. When the FCCs <NUM> detect that a pilot has control of, or is manipulating, a particular control, the FCCs <NUM> may determine that stick to be out-of-detent (OOD). Likewise, the FCCs may determine that the stick is in-detent (ID) when the signals from the detent sensors indicate to the FCCs <NUM> that the pilot has released a particular stick. The FCCs <NUM> may provide different default control or automated commands to one or more flight systems based on the detent status of a particular stick or pilot control.

Moving now to the operational aspects of flight control system <NUM>, <FIG> illustrates in a highly schematic fashion, a manner in which flight control system <NUM> may implement FBW functions as a series of inter-related feedback loops running certain control laws. <FIG> representatively illustrates a three-loop flight control system <NUM> according to an embodiment. In some embodiments, elements of the three-loop flight control system <NUM> may be implemented at least partially by FCCs <NUM>. As shown in <FIG>, however, all, some, or none of the components (<NUM>, <NUM>, <NUM>, <NUM>) of three-loop flight control system <NUM> could be located external or remote from the rotorcraft <NUM> and communicate to on-board devices through a network connection <NUM>.

The three-loop flight control system <NUM> of <FIG> has a pilot input <NUM>, an outer loop <NUM>, a rate (middle) loop <NUM>, an inner loop <NUM>, a decoupler <NUM>, and aircraft equipment <NUM> (corresponding, e.g., to flight control devices such as swashplate <NUM>, tail rotor transmission <NUM>, etc., to actuators (not shown) driving the flight control devices, to sensors such as aircraft sensors <NUM>, position sensors <NUM>, <NUM>, detent sensors <NUM>, <NUM>, etc., and the like).

In the example of <FIG>, a three-loop design separates the inner stabilization and rate feedback loops from outer guidance and tracking loops. The control law structure primarily assigns the overall stabilization task and related tasks of reducing pilot workload to inner loop <NUM>. Next, middle loop <NUM> provides rate augmentation. Outer loop <NUM> focuses on guidance and tracking tasks. Since inner loop <NUM> and rate loop <NUM> provide most of the stabilization, less control effort is required at the outer loop level. As representatively illustrated in <FIG>, a switch <NUM> may be provided to turn outer loop flight augmentation on and off, the tasks of outer loop <NUM> are not necessary for flight stabilization.

In some embodiments, the inner loop <NUM> and rate loop <NUM> include a set of gains and filters applied to roll/pitch/yaw <NUM>-axis rate gyro and acceleration feedback sensors. Both the inner loop and rate loop may stay active, independent of various outer loop hold modes. Outer loop <NUM> may include cascaded layers of loops, including an attitude loop, a speed loop, a position loop, a vertical speed loop, an altitude loop, and a heading loop. In accordance with some embodiments, the control laws running in the illustrated the loops allow for decoupling of otherwise coupled flight characteristics, which in turn may provide for more stable flight characteristics and reduced pilot workload. Furthermore, the outer loop <NUM> may allow for automated or semi-automated operation of certain high-level tasks or flight patterns, thus further relieving the pilot workload and allowing the pilot to focus on other matters including observation of the surrounding terrain.

In some embodiments, the RPM overspeed protection function may be implemented or controlled in the outer loop <NUM>. In an embodiment, the overspeed protection function may be software running on the FCCs <NUM>, and may cause the inner loop <NUM> to perform the overspeed protection by activating a state machine that monitors feedback from the ECCUs indicating the engine operating parameters and adjusts the position of the collective stick accordingly. The inner loop <NUM> may receive sensor data from aircraft equipment <NUM> such as sensors or other instrumentation, and adjust the collective stick position, collective setting and/or power setting to maintain the main rotor RPM within the limits of associated main rotor RPM threshold or range. Thus, the inner loop <NUM> may continuously monitor the engine or main rotor operating parameters and adjust flight parameters such as the collective setting accordingly. In another embodiment, the outer loop <NUM> may monitor feedback from the ECCUs, determine any adjustments to the collective setting, and then cause, signal or message the inner loop <NUM> to set, adjust or hold the collective stick position.

<FIG> is a diagram illustrating a cockpit control arrangement <NUM> according to some embodiments. In some embodiments, a rotorcraft has three sets of pilot flight controls in three flight control assemblies that include cyclic control assemblies <NUM>, collective control assemblies <NUM>, and pedal control assemblies <NUM>. A set of each pilot flight control is provided for each pilot (which may include a pilot-in-command and a co-pilot or backup pilot).

In general, cyclic pilot flight controls may allow a pilot to provide cyclic inputs through the cyclic control assembly <NUM> to set or adjust a cyclic configuration of the main rotor blades, which changes the angle of the individual main rotor blades as the main rotor rotates. This creates variable amounts of lift at varied points in the rotation cycle, causing the rotorcraft to pitch or roll. Collective pilot flight controls may allow a pilot to provide collective inputs through the collective control assembly <NUM> to set or adjust a collective configuration of the main rotor blades so that the angle of attack for all main rotor blades may be collectively altered by equal amounts and at the same time, resulting in ascent, descent, acceleration, and deceleration. Anti-torque pilot flight controls may allow a pilot to change the amount of anti-torque force applied to the rotorcraft. Tail rotor blades may operate to counter torque created by driving the main rotor. Anti-torque pilot flight controls may allow a pilot to provide pedal inputs through the pedal control assembly <NUM> and change the amount of anti-torque force applied to change a heading of the rotorcraft. For example, providing anti-torque force greater than the torque created by driving the main rotor may cause the rotorcraft to rotate in a first direction. Similarly, providing anti-torque force less than the torque created by driving the main rotor may cause the rotorcraft to rotate in a second direction opposite the first direction. In some embodiments, anti-torque pilot flight controls may change the amount of anti-torque force applied by changing the pitch of the tail rotor blades, and increasing or reducing thrust produced by tail rotor blades.

<FIG> is a diagram illustrating an arrangement of cyclic and collective control assemblies <NUM> and <NUM> according to some embodiments. In some embodiments, two cyclic control assemblies <NUM> and two collective control assemblies <NUM> are provided. The cyclic control assemblies <NUM> each have a cyclic stick <NUM> that is coupled to cyclic trim assemblies 229A and 229B. The collective control assemblies <NUM> each have collective stick <NUM> that is coupled to a collective trim assembly <NUM>. The trim assemblies <NUM>, 229A and 229B are operable to receive and measure mechanical communications of cyclic and collective inputs from the pilot through the respective sticks <NUM> and <NUM>. In some embodiments, two cyclic trim assemblies 229A and 229B are provided and are connected to each of the cyclic control assemblies <NUM>. One of the cyclic trim assemblies is a cyclic roll trim assembly 229A that manages roll or left/right cyclic tilting movements, and the other cyclic trim assembly is a cyclic pitch trim assembly 229B that manages pitch or front/back tilting movements. In some embodiments, the trim assemblies <NUM>, 229A and 229B convert mechanical inputs into roll, pitch and collective position signals that are sent to the FCCs. These trim assemblies <NUM>, 229A and 229B may include, among other items, measurement devices for measuring the position of the collective sticks <NUM> or the different movement axes of the cyclic sticks <NUM>. Trim motors in each of the trim assemblies <NUM>, 229A and 229B may drive or set the positions of the cyclic control assembly <NUM> or collective control assembly <NUM>.

The cyclic trim assemblies 229A and 229B, and collective trim assembly <NUM> may be components of a FBW flight control system, and measurements from the cyclic trim assemblies 229A and 229B and collective trim assembly <NUM> may be sent to a FCC operable to instruct flight control devices to execute commands measured through the trim assemblies <NUM>, 229A and 229B. For example, the FCC may be in communication with actuators or other devices operable to change the position of main rotor blades, and the FCC may generate cyclic control commands and/or collective control commands which are sent to the swashplate actuators or control system to control the angle of the main rotor blades.

<FIG> is a diagram illustrating a collective control assembly <NUM> and range of motion according to some embodiments. In some embodiments, the collective stick <NUM> is mounted on a collective stick support <NUM>, and moves in an arc to indicate the collective position. In the FBW system, the collective stick <NUM> may be decoupled from the swashplate and engines, so that the range of motion of the collective stick <NUM> is not limited by the connection to the swashplate or engines. The collective control assembly <NUM> may monitor and determine the position of the collective stick <NUM>, and the FCCs may determine a collective setting according to the position of the collective stick. In order to maintain the main rotor speed at a substantially constant RPM, the collective setting may be tied to the engine settings so that the engine provides sufficient power to maintain the rotor speed.

The collective stick <NUM> may have a low position <NUM> and a high position <NUM> that are respectively associated with a lowest collective setting and a maximum normal collective setting for the main rotor blades. The low position <NUM> and high position <NUM> may define or bound a normal operating range <NUM>. In some embodiments, the normal operating range <NUM> includes collective settings that correspond to power settings below a threshold such as maximum continuous power. The collective stick <NUM> may also have a maximum position <NUM> associated with a collective setting corresponding to the maximum settable power. An overdrive range <NUM> may be defined or bounded by the maximum position <NUM> and the high position <NUM>, and may include collective settings corresponding to power setting higher than the normal operating range. In some embodiments, the overdrive range <NUM> includes the maximum takeoff power, two minute maximum power, and thirty second maximum power settings. The low position <NUM>, high position <NUM> and maximum position <NUM> may be stops or positions that are enforced or created by the collective trim assembly.

In accordance with the invention, the collective trim assembly provides the rotor overspeed protection function by driving the collective stick <NUM> in a RPM overspeed protection direction <NUM>. The RPM overspeed protection direction <NUM> is upward, or a direction associated with raising a collective setting of the main rotor blades. FCCs drives the collective stick <NUM> upward, or in the RPM overspeed protection direction <NUM> while the collective stick <NUM> remains in the normal operating range <NUM>, and may limit the drive of the collective stick <NUM> to the normal operating range <NUM>, which may prevent the collective stick <NUM> or setting from entering the overdrive range <NUM>. In illustrative examples not falling within the scope of the claims, the FCCs may drive the collective stick <NUM> into the overdrive range <NUM> as part of the RPM overspeed protection. The FCCs may maintain the drive on the collective stick <NUM> while the main rotor remains in an overspeed condition to provide a tactile cue to the pilot warning of the overspeed condition, and may terminate driving the collective stick <NUM> after the main rotor speed returns to an acceptable range based on the engine speed. Additionally, the FCCs may determine the severity of the RPM overspeed or potential RPM overspeed, and may vary the upper limit of the RPM overspeed protection drive accordingly. For example, if the FCCs determine that the collective stick is at or just below the high position, and that the RPM of the main rotor is rapidly increasing at a rate where the RPM will quickly exceed the main rotor RPM threshold, the FCCs may determine a collective position that is in the overdrive range <NUM>.

<FIG> is a diagram illustrating a collective trim assembly <NUM> that may be used to provide main rotor RPM overspeed protection according to some embodiments. The collective trim assembly <NUM> may have an output shaft <NUM> that drives the collective control assembly to move the collective stick. The collective trim assembly <NUM> has a motor <NUM> controlled by drive electronics <NUM>. The drive electronics <NUM> receive, from the FCCs, or from another element in the FBW system, a signal indicating how the motor <NUM> should perform in order to control the collective stick. For example, the FCCs send a collective set signal indicating a position to which the motor <NUM> should set the collective stick.

The motor <NUM> is connected to a transmission <NUM>, which is turn, connected to the output shaft <NUM> through a shear device <NUM>. The motor <NUM> allows the FCCs to provide a drive or force similar to a spring force on the collective stick, mimicking the feel of a mechanical spring while the collective stick is mechanically disconnected from the swashplate and engines. The transmission <NUM> is a variable coupling that permits the motor <NUM> to drive the output shaft <NUM>, but allows inputs through the output shaft <NUM> to override the drive by the motor <NUM>. Thus, if the collective stick is moved or controlled by the pilot in a way that is contrary to the drive of the motor <NUM>, the pilot's inputs overcome the force applied by the motor <NUM>. For example, in some embodiments, the transmission <NUM> is a planetary gearset, an electric clutch, or the like. The shear device <NUM> is a coupling allowing the collective stick to separate from the transmission <NUM> and motor <NUM>. For example, should the transmission <NUM> become jammed, or the motor <NUM> malfunction, the shear device <NUM> can be broken so that the collective stick may be moved and used without being impeded by the inoperable transmission <NUM> or motor <NUM>.

In some embodiments, position sensors such as rotary variable differential transformers (RVDTs) <NUM> determine the rotation of the output shaft <NUM> and generate position signals indicating the position of the collective stick. The RVDTs <NUM> are disposed between the shear device <NUM> and the output shaft <NUM> so that the position of the output shaft <NUM> can be determined even if the shear device <NUM> has been broken or sheared, allowing pilot control of the rotorcraft even if the motor <NUM> or transmission <NUM>, or other parts of the drive system are inoperable. In some embodiments, multiple RVDTs <NUM> are used to separately measure the position of the output shaft <NUM> for redundancy. Each FCC may be connected to a different RVDT <NUM> so that each FCC independently determines a positon of the output shaft <NUM>, and any disagreement between readings from different RVDTs <NUM> can be identified and handled.

In some embodiments, one or more friction devices <NUM> is connected to the transmission <NUM> to provide friction-type tactile feedback cues though the output shaft <NUM>. In an embodiment, the friction devices <NUM> are connected to, and receive command signals from, the drive electronics <NUM>. In other embodiments, the friction devices <NUM> receive command signals from outside elements, such as the FCCs. The friction devices may provide a variable friction-type feel to the collective control stick through the output shaft <NUM>. The variable friction allows the FCCs, ultimately, to provide a friction-type feel to the collective stick that pilots are familiar with, even though the collective stick is not mechanically connected to the engines or swashplate. One or more resolvers <NUM> may be connected between the transmission <NUM> and the friction devices <NUM> and may act as detent sensors to determine fine motion of the collective stick indicating whether the pilot is controlling the collective stick. The resolvers <NUM> may provide a collective detent signal indicating control or motion of the collective stick by the pilot.

In an embodiment, the FCCs may provide the RPM overspeed protection by sending a collective set signal to the drive electronics <NUM> which cause the drive electronics <NUM> to command the motor <NUM> to move the output shaft <NUM> to a position that raises the collective stick to a position corresponding to a collective setting determined to slow the rotor RPM.

<FIG> is a flow diagram illustrating a method <NUM> for performing an RPM overspeed protection function according to some embodiments. In block <NUM>, the FCCs determine an actual rotor RPM. In some embodiments, sensors in the main rotor transmission, engine, ECCU, or the like, continuously monitor operational parameters of the rotorcraft, including the RPM of the main rotor, engine RPM, airspeed, vertical speed, attitude, altitude, and the like. In some embodiments, multiple sensor readings for the main rotor RPM maybe stored in a memory of the FCCs, or another nontransitory computer readable medium for analysis and comparison. Each reading of the main rotor RPM is a current main rotor RPM sensor reading or value until a next reading or sensor value is received.

In block <NUM>, the FCCs determine a predicted rotor RPM. In some embodiments, the predicted rotor RPM is a rotor RPM that is predicted or determined for a current or future time using the current main rotor RPM value and/or one or more previous main rotor RPM values. The predicted main rotor RPM may be determined according to one or more sensor values or signals, which may indicate the main rotor RPM, may be used to determine a rate of change of the main rotor RPM, or may indicate one or more other operational parameters. In some embodiments, the current or actual main rotor RPM is used as the predicted main rotor RPM, essentially using a zero time interval for predicting the main rotor RPM. In other embodiments, the predicted main rotor RPM may be determined from multiple main rotor RPM values over a predetermined time. The predicted main rotor RPM may be determined by using a predictive procedure such as a derivative to determine the slope of the parameter values, a geometric projection, an algorithm or the like. For example, an FCC that has received main rotor RPM sensor values of <NUM>, <NUM> and <NUM> RPM over a previous <NUM> second span may project from the previous values that, in the next two seconds, that the predicted main rotor RPM would be <NUM> RPM, and in next <NUM> seconds, the predicted main rotor RPM would be <NUM> RPM. The predicted main rotor RPM may be used to determine whether the main rotor is at risk of entering an overspeed condition, to predict the severity of the overspeed condition, or to predict the likelihood that a main rotor may exceed a maximum RPM threshold.

In block <NUM>, the FCCs compare the predicted rotor RPM to one or more target parameters. The target parameters are associated with a target or desired operation of a portion of the rotorcraft. The FCCs identify a rotor overspeed condition by comparing the actual operating conditions of the rotor to the target parameters or target operation conditions. In some embodiments, the target parameters are a target main rotor speed. The FCCs may analyze operating parameters related to the predicted motor RPM, main rotor RPM rate of change, current or actual rotor RPM or another predictive or actual operational parameter with respect to one or more target parameters. The FCCs may receive signals indicating the operating parameters from, for example, aircraft equipment such as sensors, ECCUs, or the like, and compare the operational parameters to one or more target parameters, thresholds, or the like. The analysis of the operating parameters with respect to the target parameters is used to determine whether the main rotor is in, or at risk of entering, an overspeed condition.

The target parameters may be determined according to an active operating parameter such as an altitude, airspeed, or the like. In some embodiments, a target main rotor speed may be determined or scheduled in the FCCs according to altitude, airspeed of the like. The target main rotor speed may, for example, be scheduled to improve efficiency, improve performance, reduce the rotorcraft's noise footprint, or optimize other operating parameters. The FCCs determine the target main rotor RPM and send the target main rotor RPM to the ECCUs, which control engine speed and rotor RPM to achieve the target main rotor RPM. When a main rotor overspeed condition is detected or predicted, the engines may be de-clutched from the main rotor, and the FCCs may then drive the reverse tactile cueing based on the target main rotor RPM.

In some embodiments, the target parameters may include an RPM threshold, and the FCCs may determine that the main rotor is in an overspeed condition according to a relationship between the main rotor RPM and an RPM threshold. In some embodiments, the RPM threshold is a <NUM>% variation of, or from, the target main rotor RPM. Thus, in such an embodiment, for a target main rotor RPM of <NUM> RPM, the threshold would be <NUM> RPM, and a threshold range would be between <NUM> and <NUM> RPM. In other embodiments, the threshold may be a larger variation, such as <NUM>%, <NUM>% or <NUM>%. Additionally the range may not necessarily be symmetrical, with a lower threshold being different from an upper threshold. For example, a threshold range may be <NUM>% to <NUM>% of the main rotor target RPM, so that, for a target main rotor RPM of <NUM> RPM, the threshold range may be between about <NUM> and <NUM> RPM.

In accordance with the invention, the FCCs determine that a main rotor overspeed condition exists in response to the main rotor RPM exceeding the RPM threshold, or in response to the main rotor RPM being predicted to exceed, or fall outside of, the RPM threshold. Additionally, the FCCs may identify a potential or predicted rotor overspeed condition when the FCCs determine that the rate of change of the main rotor RPM will cause the main rotor RPM to exceed, or fall outside of, the RPM threshold within a predetermined period of time. In some embodiments, the target main rotor RPM may have an associated threshold range, and a predicted main rotor RPM falling outside of the threshold range indicates a main rotor overspeed condition. For example, for a main rotor target RPM of <NUM>, a predicted or actual rotor RPM of <NUM> RPM would exceed a <NUM>% RPM threshold (at <NUM> RPM) and a <NUM>% RPM threshold range (between <NUM> RPM and <NUM> RPM), and be in a rotor overspeed condition in both threshold cases. In another example, an FCC that has received main rotor RPM values of <NUM>, <NUM> and <NUM> RPM over a previous two second span may determine that the main rotor rate of change is +<NUM> RPM per second, and use the rate of change or previous values to project that, in the next two seconds, the predicted main rotor RPM would be <NUM> RPM, and in the next five seconds, the predicted main rotor RPM would be <NUM> RPM. Therefore, for a main rotor target RPM of <NUM>, the two second predicted main rotor RPM of <NUM> RPM would exceed, or fall outside, the <NUM>% RPM threshold (at <NUM> RPM) and be within the <NUM>% RPM threshold range (between <NUM> RPM and <NUM> RPM), while the five second predicted main rotor RPM of <NUM> RPM would exceed, or fall outside, both the <NUM>% RPM threshold (at <NUM> RPM) and the <NUM>% RPM threshold range (between <NUM> RPM and <NUM> RPM).

In block <NUM>, the FCCs determine one or more flight parameters. The flight parameters are parameters at which the FCCs determine the rotorcraft should operate at to avoid, or recover from, a rotor overspeed condition. Therefore, in some embodiments, the flight parameters are determined in response to a rotor overspeed condition being identified. The flight parameters include a setting for one or more flight control devices of the rotorcraft that change the main rotor RPM and in some embodiments, may be associated with reducing the main rotor RPM. In some embodiments, the flight parameters may include a collective angle for main rotor blades of the rotorcraft or a collective control setting associated with raising a collective setting of the one or more flight control devices. In some embodiments, the FCCs determine a new collective setting for the main rotor that is greater than the current collective setting for the main rotor, and that is determined to prevent the main rotor from exceeding the main rotor threshold.

In some embodiments, the FCCs may determine the flight parameters based on the RPM threshold, main rotor speed, engine operating parameters, vertical speed, and the like. For example, in slow speed forward flight, the main rotor blades may have an <NUM> degree collective angle. Should the pilot pitch the nose the rotorcraft up during the forward flight, causing the rotor to speed up, the FCCs may determine that a <NUM> degree collective angle would maintain the main rotor RPM within the threshold. As the speed of forward flight increases, the effect of the same pitch increase becomes more severe since the higher airspeed causes more air to move through the main rotor, speeding the main rotor up more for a given pitch. Thus, the main rotor blades may have a <NUM> degree pitch angle during high speed forward flight, and the FCCs may determine that the <NUM> degree pitch angle is required to maintain the rotor speed within the threshold. The greater increase in pitch angle determined by the FCCs compensates for greater rate of change main rotor speed due to forward flight.

In some embodiments, the FCCs may use a correlation between a known drag at a particular rotor speed and engine power to determine an increase in, or value for, the collective setting that will reduce the rotor speed or rate of change of the rotor speed. The correlation may be stored in a table, calculated from an algorithm, stored from previous sensor readings, or the like. In other embodiments, the FCCs may make an initial change to the collective, and adjust the collective based on sensor feedback. The FCCs continuously monitor the main rotor RPM, and may reduce or vary the collective until the main rotor RPM or rate of change of the main rotor RPM no longer indicates a rotor overspeed condition.

In some embodiments, the FCCs may limit the flight parameters based on one or more factors. For example, the FCCs may limit the flight parameters to avoid exceeding a maximum RPM threshold. The FCCs may determine that the rotor is in an overspeed position, and may increase the collective more rapidly, or to a greater degree than would be warranted by the main rotor RPM, engine speed, or the like in order to prevent the main rotor RPM from exceeding the maximum RPM threshold. In some embodiments, the maximum RPM limit threshold may <NUM>% or <NUM>% of the target main rotor speed.

In block <NUM>, the FCCs set a pilot control position. In some embodiments, the FCCs send a control set signal to one or more trim assemblies, causing the trim assemblies to set the pilot control positions. In some embodiments the FCCs generate the control set signal and cause the trim motor to drive the pilot control while the overspeed condition is maintained. The FCCs determine a pilot control setting according to the flight parameters and generate the control set signal or command according to the pilot control setting. In accordance with the invention, the FCCs provide the overspeed protection and tactile cueing by controlling positioning of one or more pilot controls, such as the collective stick, according to the flight parameters using the control set signals. In other embodiments, the FCCs may also control other pilot controls or flight control elements such as a cyclic control or the engines.

The FCCs may also determine a limit range within a range of movement for the pilot controls to determine a normal operating range to which the overspeed protection is limited. The FCCs may adjust the flight parameters to keep the position of the one or more pilot controls within the limit range. Thus, if the FCCs determine that the flight parameters call for a collective stick position that would be in an overdrive range, the FCCs may adjust the collective setting so that the collective stick position is not driven outside the normal operating range.

In block <NUM>, a pilot may optionally input a manual command through the pilot control. This permits a pilot to override the position set by the FCCs. The pilot control positions are suggested positions, and driving the pilot controls by the FCCs provides a tactile cue to the pilot that the main rotor is in an overspeed condition. The tactile cue acts as a soft stop, and the pilot may pull through the force provided by positioning the pilot controls.

In block <NUM>, the FCCs determine a pilot control position. The sensors associated with the pilot controls read the position of the pilot controls and send position signals to the FCCs. In block <NUM>, the FCCs sent one or more commands to one or more flight control elements. The FCCs generate flight control device control signals according to the positions of the pilot controls and send the flight control device control signals to the one or more flight control devices. In some embodiments, the FCCs control the collective stick for the rotor overspeed protection and tactile cueing, and a collective position sensor generates a collective position signal which is sent to the FCCs. The FCCs generate collective control signals and send the collective control signal a collective swashplate actuator. The collective position signal is used so that, when a pilot overrides the collective positon set by the FCCs for the overspeed protection, the actual position of the collective stick is used to control the collective. Thus, the FCCs may receive a position signal indicating a position of the pilot controls that is different from the position set by the FCCs and that indicates a manual pilot control.

In block <NUM>, the FCCs adjust, set or move a swashplate collective setting or collective flight control element. The FCCs receive the control position signals and control, for example, the collective angle of the main rotor blades according to positioning of the one or more pilot controls.

While the method <NUM> disclosed herein has been described in terms of discrete blocks, it should be understood that the method is not limited to the disclosed order of blocks. The FCCs continue to monitor the main rotor RPM and operation parameters, and adjust or set the collective setting while the main rotor RPM is in, or predicted to enter, the rotor overspeed condition. In some embodiments, for example, determining the actual rotor RPM and predicted rotor RPM, determining flight parameters, determining pilot control settings and setting pilot control position is a continuous feedback process to provide a protection for, or tactile cue indicating, the rotor overspeed condition.

Claim 1:
A flight control computer (FCC) (<NUM>) for a rotorcraft (<NUM>), comprising:
a processor; and
a non-transitory computer-readable storage medium storing a program to be executed by the processor, the program including instructions for providing main rotor overspeed protection, the instructions for providing the main rotor overspeed protection including instructions for:
monitoring sensor signals indicating a main rotor revolutions per minute (RPM);
determining a target operating parameter;
determining one or more flight parameters in response to a relationship between the main rotor RPM and the target operating parameter indicating a main rotor overspeed condition, wherein the rotor overspeed condition is a condition where the main rotor turns faster than an engine is driving the main rotor, wherein the determining the one or more flight parameters includes determining a setting at a first position for one or more flight control devices (<NUM>; <NUM>) of the rotorcraft (<NUM>) that reduces the main rotor RPM by increasing the collective pitch of blades of the main rotor;
sending a signal to a collective trim motor to drive a collective stick of the rotorcraft upwards to provide a force cue to a pilot, to increase the collective pitch of the blades of the main rotor according to the flight parameters; and
controlling the one or more flight control devices (<NUM>; <NUM>) of the rotorcraft (<NUM>) to increase the collective pitch of the blades of the main rotor according to positioning of the collective stick.