A B737-700 Flight Crew encountered a failure of the flaps to extend when they got a stick shaker warning at maneuvering speed for flaps five.

2010-03 · NASA ASRS report 880928

Date: 2010-03 · Aircraft: B737-700 · Phase: approach

Anomalies: aircraft-equipment-problem-critical|deviation-altitude-excursion-from-assigned-altitude|deviation-speed-all-types|inflight-event-encounter-fuel-issue

Synopsis

A B737-700 Flight Crew encountered a failure of the flaps to extend when they got a stick shaker warning at maneuvering speed for flaps five.

Narrative

The First Officer called for flaps 5 and started to slow for the approach. I immediately noted the maneuvering speeds appear on the MASI [Mach Air Speed Indicator] which led me to believe all was normal; but I did not initially check the flap gauge. As we continued to slow; we received a momentary stall warning and the First Officer executed the stall recovery. We then noticed that the flaps were still indicating zero. I informed Tower that we were going around; that we had a flap problem; and needed time to figure it out. As we climbed from 2500' to assigned missed approach altitude of 3000 feet; we overshot the altitude and informed ATC. We were vectored for a downwind to give us time to take care of the problem. My concerns at this point were fuel; weather; and runway length and condition if we had to land no flap. The First Officer continued to fly while I talked to ATC; checked performance data; and ran the appropriate checklists. We got vectors to a downwind and I checked for landing data which indicated we could land with no flaps if we had to. I then referenced the QRH for Flaps; Trailing Edge: Symmetrical Non-Normal/No Flap. We ran the checklist and extended the flaps with the alternate flap switch. We then were vectored back to the ILS and I made a flap 15 landing with autobrake set to max. We accomplished all of the above in a short time due to the amount of fuel onboard and the need to not delay our landing. We made one quick call to the Flight Attendants to let them know we were still landing at destination; but did not have time to give any detail or make a PA to the passengers. After arriving at the gate; I talked to Dispatch and Maintenance to arrange for repairs. Maintenance informed me that the same thing had happened to that aircraft only three days before. They requested that I try to raise the flaps at the gate which I did normally with the flap handle. I then tried to lower the flaps normally and the normal system worked.

Second reporter narrative

Rain/visibility made visual inspection of leading edge devices from cockpit impossible.I assumed MASI speed bugs illuminated on PFD meant flaps had correctly deployed. I assumed flap gauge/needles inop. [This event taught me] MASI bugs reflect flap handle position only.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.