Retreating blade stall

Retreating blade stall is a hazardous flight condition in helicopters and other rotary wing aircraft, where the retreating rotor blade has a lower relative blade speed, combined with an increased angle of attack, causing a stall and loss of lift. Retreating blade stall is the primary limiting factor of a helicopter's never exceed speed, VNE.[1]

Advancing vs. retreating blades

retreating blade side advancing blade side

A rotor blade that is moving in the same direction as the aircraft is called the advancing blade and the blade moving in the opposite direction is called the retreating blade.

Balancing lift across the rotor disc is important to a helicopter's stability. The amount of lift generated by an airfoil is proportional to the square of its airspeed (velocity). In a zero airspeed hover the rotor blades, regardless of their position in rotation, have equal airspeeds and therefore equal lift. In forward flight the advancing blade has a higher airspeed than the retreating blade, creating unequal lift across the rotor disc.

A fuller treatment is provided in dissymmetry of lift.

Compensation

Most helicopter designs compensate for this by incorporating a certain degree of vertical "flap" movement of the rotor blades. When flapping, a rotor blade will travel upward during its advance, creating a lesser angle of attack (AOA) and therefore lesser lift. When the blade retreats, the blade falls downward again, increasing the AOA and therefore generating greater lift.

There are three general designs. The earliest, and by far, least common design today, is the fully rigid rotor system; the blades are rigidly fixed to the rotor hub but made of a flexible material that allows some degree of flap.

Semi-rigid rotor systems have a horizontal hinge at the base of the blades that allow flap as they rotate. By necessity they always have an even number of blades, as each opposing pair is mechanically connected to prevent vibration.

Fully articulated rotor systems use a combination of flapping and a horizontal motion that moves the retreating blades forward slightly and moves them back again on the advancing side, thus creating more relative airflow and lift on the retreating side at the expense of the advancing side.

In all cases, the pilot may compensate the induced roll with left or right cyclic control input (as determined by the rotation of the rotor) up to a degree. However, the rapid rate of change of blade flex and angle of attack causes uncontrolled longitudinal twist and severe vibration in later stages, resulting in total loss of cyclic control if left unchecked.

Assuming no rotor damage, recovery from the condition is possible by using the procedure described below under Flight performance during a retreating blade stall.

Failure

External video
Helicopter Blade Stall, NASA Langley

These compensations can only do so much. Increasing angle of attack to compensate for reduced blade airspeed has the effect of maintaining lift only until the point where critical angle of attack is reached, after this point lift sharply decreases.

All airfoils have a critical angle of attack (also called a stall angle of attack) which is the angle of attack that produces most lift. Above this angle flow over the airfoil becomes detached and lift decreases, this is commonly called a stall.

When a fixed-wing aircraft exceeds its critical angle of attack the entire aircraft loses lift and enters a condition called a stall. The usual results of a fixed-wing stall are a sharp drop in aircraft altitude and a dive. Stalls in fixed-wing aircraft are virtually always a recoverable event.

In a retreating-blade stall, however, only the retreating half of the helicopter's rotor disc experiences a stall. The advancing blade continues to generate lift, but the retreating blade enters a stall condition, usually resulting in an uncommanded increase in pitch of the nose and a roll in the direction of the retreating side of the rotor disc. In counter-clockwise rotating rotor systems (as in most American-made types) this is the left side. In clockwise rotating systems it is a roll to the right.

Flight performance during a retreating blade stall

As the aircraft approaches retreating blade stall conditions, it will shudder and the nose will begin to pitch up. The resultant upward pitching of the nose will naturally begin to correct the situation as it results in slowing the aircraft. If forced to continue the acceleration via flight controls (forward cyclic + collective), it may roll to the side of the retreating blade. Recovery involves lowering the collective pitch, relieving forward pressure on the cyclic or more commonly, both. Either of these control movements should restore the proper attached airflow over the retreating blade thus generating lift again. This is normally an automatically corrected condition if one just 'lets go' of the controls.

Causes of retreating blade stall

Retreating blade stall is more likely to occur in a helicopter when the following conditions exist either alone or in combination:

Recovery

Recovery includes lowering the collective to reduce the blade angle of attack, followed by application of aft cyclic to reduce airspeed.[1]

gollark: ```[13:45:16] Unhandled rejection TypeError: connection.query(...).on is not a function at /home/osmarks/Documents/Krist/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:179:31 at Promise._execute (/home/osmarks/Documents/Krist/node_modules/bluebird/js/release/debuggability.js:303:9) at Promise._resolveFromExecutor (/home/osmarks/Documents/Krist/node_modules/bluebird/js/release/promise.js:483:18) at new Promise (/home/osmarks/Documents/Krist/node_modules/bluebird/js/release/promise.js:79:10) at /home/osmarks/Documents/Krist/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:178:12 at PassThroughHandlerContext.finallyHandler (/home/osmarks/Documents/Krist/node_modules/bluebird/js/release/finally.js:57:23) at PassThroughHandlerContext.tryCatcher (/home/osmarks/Documents/Krist/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/home/osmarks/Documents/Krist/node_modules/bluebird/js/release/promise.js:512:31) at Promise._settlePromise (/home/osmarks/Documents/Krist/node_modules/bluebird/js/release/promise.js:569:18) at Promise._settlePromise0 (/home/osmarks/Documents/Krist/node_modules/bluebird/js/release/promise.js:614:10) at Promise._settlePromises (/home/osmarks/Documents/Krist/node_modules/bluebird/js/release/promise.js:693:18) at Async._drainQueue (/home/osmarks/Documents/Krist/node_modules/bluebird/js/release/async.js:133:16) at Async._drainQueues (/home/osmarks/Documents/Krist/node_modules/bluebird/js/release/async.js:143:10) at Immediate.Async.drainQueues [as _onImmediate] (/home/osmarks/Documents/Krist/node_modules/bluebird/js/release/async.js:17:14) at runCallback (timers.js:763:18) at tryOnImmediate (timers.js:734:5)```repeatedly.
gollark: ```[13:44:18] (node:2784) UnhandledPromiseRejectionWarning: Error: Please install 'pg' module manually at new ConnectionManager (/home/osmarks/Documents/Krist/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:27:13) at new PostgresDialect (/home/osmarks/Documents/Krist/node_modules/sequelize/lib/dialects/postgres/index.js:12:28) at new Sequelize (/home/osmarks/Documents/Krist/node_modules/sequelize/lib/sequelize.js:233:18) at /home/osmarks/Documents/Krist/src/database.js:54:24 at new Promise (<anonymous>) at Function.Database.init (/home/osmarks/Documents/Krist/src/database.js:36:9) at /home/osmarks/Documents/Krist/main.js:47:11 at <anonymous> at process._tickCallback (internal/process/next_tick.js:182:7)[13:44:18] (node:2784) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)[13:44:18] (node:2784) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.```
gollark: ```[13:44:18] [Error] Uncaught error: [13:44:18] TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string at assertPath (path.js:39:11) at Object.basename (path.js:1300:5) at /home/osmarks/Documents/Krist/src/errors/errors.js:46:47 at Array.forEach (<anonymous>) at Object.<anonymous> (/home/osmarks/Documents/Krist/src/errors/errors.js:44:27) at Module._compile (internal/modules/cjs/loader.js:654:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:665:10) at Module.load (internal/modules/cjs/loader.js:566:32) at tryModuleLoad (internal/modules/cjs/loader.js:506:12) at Function.Module._load (internal/modules/cjs/loader.js:498:3)```
gollark: ```// The dialect used to connect, one of: mysql, postgres, mariadb or mssql. (sqlite not supported, fuck you Taras!)```How professional.
gollark: It errored when I tried to run it without running a redis server.

References

  1. Helicopter Flying Handbook, FAA-H-8083-21A (PDF). U.S. Dept. of Transportation, FAA, Flight Standards Service. 2012. pp. 11-8–11-12, 11-17–11-20.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.