An air carrier B727-100 flight crew experienced a stick shaker well outside of the normal limits of ...

Attributes
ACN	344353
Time
Date	199608
Day	Thu
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : ind
State Reference	IN
Altitude	msl bound lower : 5000 msl bound upper : 5000
Environment
Flight Conditions	Mixed
Light	Night
Aircraft 1
Controlling Facilities	tracon : ind
Operator	common carrier : air carrier
Make Model Name	B727-100
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 90 flight time total : 4000 flight time type : 200
ASRS Report	344353
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	aircraft equipment problem : critical
Independent Detector	aircraft equipment other aircraft equipment : unspecified
Resolutory Action	none taken : insufficient time other
Consequence	Other
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	other

Narrative:

While being radar vectored for approach, speed 210 KTS, top bug 187 KTS, gear up, flaps up, speed brakes extended, the stick shaker activated while rolling out of 15 degree bank turn. The throttles were advanced, the speed brakes stowed. The resulting overspd of engines #1 and #2 was written up. Callback conversation with reporter revealed the following information: since the captain (PF) reported to ASRS, the B727-100 engines were boroscoped and no damage was found. The reason for the stick shaker is still a mystery. Operating procedures do not distinguish between erroneous stick shakers and the real thing, so the captain believes that his response was correct. The manual states that the stick shaker may occur within 10 KIAS of computed maneuvering speed if maneuvering at 30 degrees of bank and decelerating with speed brakes and to be alert to retract speed brakes if maneuvering is required under these circumstances. The reporter experienced something that was well outside the parameters for stick shaker activation. He was aware of this type of problem since he had also heard reports similar to this incident from peers. Reporter does not know what their speed, bank, and confign was, however.

Original NASA ASRS Text

Title: AN ACR B727-100 FLC EXPERIENCED A STICK SHAKER WELL OUTSIDE OF THE NORMAL LIMITS OF ACTIVATION. THE PF RESPONDED WITH MAX PWR WHICH IN TURN REQUIRED A WRITEUP FOR AN ENG INSPECTION BY MAINT.

Narrative: WHILE BEING RADAR VECTORED FOR APCH, SPD 210 KTS, TOP BUG 187 KTS, GEAR UP, FLAPS UP, SPD BRAKES EXTENDED, THE STICK SHAKER ACTIVATED WHILE ROLLING OUT OF 15 DEG BANK TURN. THE THROTTLES WERE ADVANCED, THE SPD BRAKES STOWED. THE RESULTING OVERSPD OF ENGS #1 AND #2 WAS WRITTEN UP. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: SINCE THE CAPT (PF) RPTED TO ASRS, THE B727-100 ENGS WERE BOROSCOPED AND NO DAMAGE WAS FOUND. THE REASON FOR THE STICK SHAKER IS STILL A MYSTERY. OPERATING PROCS DO NOT DISTINGUISH BTWN ERRONEOUS STICK SHAKERS AND THE REAL THING, SO THE CAPT BELIEVES THAT HIS RESPONSE WAS CORRECT. THE MANUAL STATES THAT THE STICK SHAKER MAY OCCUR WITHIN 10 KIAS OF COMPUTED MANEUVERING SPD IF MANEUVERING AT 30 DEGS OF BANK AND DECELERATING WITH SPD BRAKES AND TO BE ALERT TO RETRACT SPD BRAKES IF MANEUVERING IS REQUIRED UNDER THESE CIRCUMSTANCES. THE RPTR EXPERIENCED SOMETHING THAT WAS WELL OUTSIDE THE PARAMETERS FOR STICK SHAKER ACTIVATION. HE WAS AWARE OF THIS TYPE OF PROB SINCE HE HAD ALSO HEARD RPTS SIMILAR TO THIS INCIDENT FROM PEERS. RPTR DOES NOT KNOW WHAT THEIR SPD, BANK, AND CONFIGN WAS, HOWEVER.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

An air carrier B727-100 flight crew experienced a stick shaker well outside of the normal limits of activation. The PF responded with maximum power which in turn required a writeup for an engine inspection by maintenance.