Narrative:

Approaching crw from the northwest; we were cleared direct to the FAF for the ILS runway 23; instructed to maintain 4;000 feet and expect a visual approach runway 23. At this point; we were approximately 10 NM from the field; with the runway in sight.during the arrival briefing; we had discussed the terrain around the airport to be aware of; as well as the necessity to back up the approach with the ILS; as well as the PAPI visual indicators associated with the runway since it would be dusk by the time we were on the approach. About 3-5 miles from the marker; the controller asked us to 'keep it close in' to allow a military aircraft to follow us to the field. As I turned a right base (approximately 4 miles north of the field); I called for 'gear down; flaps 22' and was descending through approximately 2;800 feet with the runway and PAPI in sight. Just after the pilot monitoring selected the gear and flaps; we received a single 'terrain' aural warning; followed by 'landing gear'. I immediately began a climb; turned toward the field; and subsequently called for a go-around. The tower instructed us to maintain 3;000 feet and to enter a right downwind. We then completed a normal approach to landing runway 23 backed up by the ILS.threats were mountainous terrain; dusk conditions; ATC requesting 'close in' approach. [Our] errors: accepting a challenging approach clearance resulting in a unwanted aircraft state (uas). Uas: aircraft ended up in a position that triggered a terrain warning.despite the fact we had discussed the threats associated with the arrival airport; I allowed myself to be rushed at the suggestion of ATC. In hindsight; we never should have accepted a short approach clearance at an unfamiliar airport in dusk conditions. I should have had the pilot monitoring request vectors behind the other traffic approaching the field; or even better; vectors to the instrument approach.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air carrier regional jet Captain reported receiving a GPWS Terrain warning during a night visual approach to CRW.

Narrative: Approaching CRW from the northwest; we were cleared direct to the FAF for the ILS Runway 23; instructed to maintain 4;000 feet and expect a visual approach Runway 23. At this point; we were approximately 10 NM from the field; with the runway in sight.During the arrival briefing; we had discussed the terrain around the airport to be aware of; as well as the necessity to back up the approach with the ILS; as well as the PAPI visual indicators associated with the runway since it would be dusk by the time we were on the approach. About 3-5 miles from the marker; the controller asked us to 'keep it close in' to allow a military aircraft to follow us to the field. As I turned a right base (approximately 4 miles north of the field); I called for 'gear down; flaps 22' and was descending through approximately 2;800 feet with the runway and PAPI in sight. Just after the pilot monitoring selected the gear and flaps; we received a single 'terrain' aural warning; followed by 'landing gear'. I immediately began a climb; turned toward the field; and subsequently called for a go-around. The Tower instructed us to maintain 3;000 feet and to enter a right downwind. We then completed a normal approach to landing Runway 23 backed up by the ILS.Threats were mountainous terrain; dusk conditions; ATC requesting 'close in' approach. [Our] errors: Accepting a challenging approach clearance resulting in a Unwanted Aircraft State (UAS). UAS: Aircraft ended up in a position that triggered a terrain warning.Despite the fact we had discussed the threats associated with the arrival airport; I allowed myself to be rushed at the suggestion of ATC. In hindsight; we never should have accepted a short approach clearance at an unfamiliar airport in dusk conditions. I should have had the pilot monitoring request vectors behind the other traffic approaching the field; or even better; vectors to the instrument approach.

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.