Narrative:

Called by foqa gatekeeper and advised of overspeed of 8 knots when flaps moved to 10. Flaps were inadvertently moved to 10 when flaps were at 2 and flaps 5 was called for. I cannot see gate settings from captain's seat and must have moved the handle too far and into the gate for flaps 10; when flaps 5 was called for. Gatekeeper stated the event occurred at 4073 ft; on final for runway 25L and outside of hunda intersection. We were behind a B767 and given 9 miles separation and cautions about possible wake turbulence; of which there was some. Winds were down the runway at 8-10 knots. This was day 6 out of 6 in a row of being on duty. Given the callouts and verification procedures we already have in place; it seems emphasis for captain's as non-flying pilots to look around the throttles to verify the requested flap gate is actually selected; after verification; may help. Problem is; in the busy approach/speed and configure changes environment; it may not be possible to do that at all times.

Google
 

Original NASA ASRS Text

Title: B737-800 Captain reported mistakenly selecting flaps 10 when flaps 5 were called for; leading to an overspeed.

Narrative: Called by FOQA Gatekeeper and advised of overspeed of 8 knots when flaps moved to 10. Flaps were inadvertently moved to 10 when flaps were at 2 and Flaps 5 was called for. I cannot see gate settings from Captain's seat and must have moved the handle too far and into the gate for Flaps 10; when Flaps 5 was called for. Gatekeeper stated the event occurred at 4073 FT; on final for Runway 25L and outside of HUNDA intersection. We were behind a B767 and given 9 miles separation and cautions about possible wake turbulence; of which there was some. Winds were down the runway at 8-10 knots. This was day 6 out of 6 in a row of being on duty. Given the callouts and verification procedures we already have in place; it seems emphasis for Captain's as non-flying pilots to look around the throttles to verify the requested flap gate is actually selected; after verification; may help. Problem is; in the busy approach/speed and configure changes environment; it may not be possible to do that at all times.

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