Narrative:

On the localizer DME 15 approach to ase; at 0.2 miles prior to the fix xtrem; I called for the altitude alerter to be set to 9700. This is what was indicated on the FMS next to the fix kyack. About 0.5 miles from xtrem requested the first officer increase the descent rate from 1200 FPM to 1800fpm in order to put the descent indicator in the proper position just beyond the fix. We received the caution terrain; promptly followed by caution obstacle when descending near the fix kyack. We immediately executed a go-around; then followed the published missed and notified ATC that we went missed due to a terrain caution. After completing the missed approach; I realized that when programming the FMS; I had incorrectly entered the altitude at the fix kyack as 9700; instead of 10300 as published. This error wasn't caught on our FMS cross-check. I called for the altitude to be set; and glanced at the chart; but didn't catch the error. In the future I will maintain a heightened awareness when setting up a complex approach and ask the first officer to carefully cross check my work. An extra moments care would have revealed the error if I took an extra second to interpret the profile view of the chart. Also; if I see the need for an unusual descent rate without any contributing factors; I will immediately question if the descent angle or altitude is wrong.

Google
 

Original NASA ASRS Text

Title: CRJ700 Captain reported entering the wrong step down altitude in the FMC for the LOC DME Runway 15 to ASE. The error was not detected and the approach chart was not consulted during the approach. This resulted in a terrain warning and a go-around.

Narrative: On the LOC DME 15 approach to ASE; at 0.2 miles prior to the fix XTREM; I called for the altitude alerter to be set to 9700. This is what was indicated on the FMS next to the fix KYACK. About 0.5 miles from XTREM requested the FO increase the descent rate from 1200 FPM to 1800fpm in order to put the descent indicator in the proper position just beyond the fix. We received the Caution Terrain; promptly followed by Caution Obstacle when descending near the fix KYACK. We immediately executed a Go-Around; then followed the published missed and notified ATC that we went missed due to a terrain caution. After completing the missed approach; I realized that when programming the FMS; I had incorrectly entered the altitude at the fix KYACK as 9700; instead of 10300 as published. This error wasn't caught on our FMS cross-check. I called for the altitude to be set; and glanced at the chart; but didn't catch the error. In the future I will maintain a heightened awareness when setting up a complex approach and ask the FO to carefully cross check my work. An extra moments care would have revealed the error if I took an extra second to interpret the profile view of the chart. Also; if I see the need for an unusual descent rate without any contributing factors; I will immediately question if the descent angle or altitude is wrong.

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.