Narrative:

Enroute; left flaps transit light; with 3D led on right wing annunciator. Complied with QRH and contacted dispatch via ACARS. During coordination with dispatch the light went out. Approach: all normal (no lights) visual flaps 30. After completely configured for landing flaps 30 and slowing to target airspeed at around 1;500 feet AGL at about 155 knots IAS we received stick shaker; followed by 'airspeed low' voice indication. We immediately did a full power go-around. I noted that the HUD; my primary flight display (pfd); first officer pfd and standby; all said same airspeed. After clean-up from go-around; the same leading edge extension light came back on as before.downwind vectors: repeated QRH steps. As per QRH; set up for a flaps 15 landing. This time I did not communicate with dispatch due to time constraints with three page QRH procedure and lots of approach control issues. While being vectored around; I discussed with first officer that if we received stick shaker again that we would both confirm and verify that all airspeed indications are correct and if so that we would continue the approach. My feeling is that going around and doing it all again was not going to fix anything; and a third time vectoring around could make fuel a problem.final: flaps 15 fully configured. At same airspeed as first approach 155 knots; again received stick shaker. This time though it was about same as target airspeed (because of QRH flaps 15). I double/triple checked all airspeed indications. Also aircraft attitude and engines were normal. Before I could verify with first officer; the stick shaker quit and all seemed normal. We elected to continue to a normal flaps 15 landing.post flight: maintenance met us at gate; first check they did was stick shaker check; and the check failed.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737-700 Captain reported that after running the QRH for a left flaps transit light they received a stick shaker on approach that was later traced to a malfunctioning stall warning system.

Narrative: Enroute; left flaps transit light; with 3D LED on right wing annunciator. Complied with QRH and contacted Dispatch via ACARS. During coordination with Dispatch the light went out. Approach: All normal (no lights) visual flaps 30. After completely configured for landing flaps 30 and slowing to target airspeed at around 1;500 feet AGL at about 155 knots IAS we received stick shaker; followed by 'Airspeed Low' voice indication. We immediately did a full power go-around. I noted that the HUD; my Primary Flight Display (PFD); FO PFD and standby; all said same airspeed. After clean-up from go-around; the same leading edge extension light came back on as before.Downwind vectors: Repeated QRH steps. As per QRH; set up for a flaps 15 landing. This time I did not communicate with Dispatch due to time constraints with three page QRH procedure and lots of Approach Control issues. While being vectored around; I discussed with FO that if we received stick shaker again that we would both confirm and verify that all airspeed indications are correct and if so that we would continue the approach. My feeling is that going around and doing it all again was not going to fix anything; and a third time vectoring around could make fuel a problem.Final: Flaps 15 fully configured. At same airspeed as first approach 155 knots; again received stick shaker. This time though it was about same as target airspeed (because of QRH flaps 15). I double/triple checked all airspeed indications. Also aircraft attitude and engines were normal. Before I could verify with FO; the stick shaker quit and all seemed normal. We elected to continue to a normal flaps 15 landing.Post Flight: Maintenance met us at gate; first check they did was stick shaker check; and the check failed.

Data retrieved from NASA's ASRS site 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.