Narrative:

We were on a left downwind at 3;000 ft. Heading 090 approximately 5 miles offset to the south. Shortly after passing abeam the threshold; we were cleared for a visual approach. The first officer put 1;600 ft. In the MCP altitude window (FAF altitude); and after we both verified the altitude; began a descent in flch. He bugged clean maneuvering speed and extended the speedbrakes. Around 1 to 2 miles past abeam the final approach fix he started a base turn to the left. Descending through 1;900 ft. At 220 kts. We received a caution terrain warning. I quickly glanced outside but did not see any terrain or obstacles. A second later the GPWS started a terrain terrain warning. We immediately initiated the CFIT recovery maneuver. Even though we were VMC; we could not immediately or unequivocally determine that there was not a terrain issue. The moment our descent rate was arrested; the warning stopped. We reached an altitude of 2;900 ft. Before discontinuing the CFIT maneuver. We continued the base turn and visual approach. The rest of the approach and landing was uneventful. After landing; we remembered seeing hills depicted on the approach chart almost directly south of the final approach fix. The day prior we flew the exact approach with no issues. Today; approach control vectored us further to the south before clearing us for a visual approach. I typically never set an MCP altitude below 2;000 ft. Until on final. This time I believed we had enough altitude and airspeed to lose that setting 1;600 ft. In the MCP window would be ok. That was my mistake. Had we set 2;500 ft. In the MCP window until after turning base; we most likely would not have received a GPWS warning.

Related reports:

Google
 

Original NASA ASRS Text

Title: Flight Crew reported receiving a GPWS alert due to their configuration settings.

Narrative: We were on a left downwind at 3;000 ft. Heading 090 approximately 5 miles offset to the south. Shortly after passing abeam the threshold; we were cleared for a Visual Approach. The First Officer put 1;600 ft. in the MCP altitude window (FAF altitude); and after we both verified the altitude; began a descent in FLCH. He bugged clean maneuvering speed and extended the speedbrakes. Around 1 to 2 miles past abeam the Final Approach fix he started a base turn to the left. Descending through 1;900 ft. at 220 kts. we received a CAUTION TERRAIN warning. I quickly glanced outside but did not see any terrain or obstacles. A second later the GPWS started a TERRAIN TERRAIN warning. We immediately initiated the CFIT recovery maneuver. Even though we were VMC; we could not immediately or unequivocally determine that there was not a terrain issue. The moment our descent rate was arrested; the warning stopped. We reached an altitude of 2;900 ft. before discontinuing the CFIT maneuver. We continued the base turn and Visual Approach. The rest of the approach and landing was uneventful. After landing; we remembered seeing hills depicted on the approach chart almost directly south of the final Approach Fix. The day prior we flew the exact approach with no issues. Today; approach control vectored us further to the south before clearing us for a Visual Approach. I typically never set an MCP altitude below 2;000 ft. until on final. This time I believed we had enough altitude and airspeed to lose that setting 1;600 ft. in the MCP window would be ok. That was my mistake. Had we set 2;500 ft. in the MCP window until after turning base; we most likely would not have received a GPWS warning.

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.