Air carrier first officer reported receiving a GPWS terrain alert on arrival into boi; followed by r...

Narrative:

We chose to fly the RNAV X 28R into boise. We briefed the approach in cruise including the 180 speed restriction at cubar. We flew the plane through cubar at 210 by mistake. Shortly afterward we heard the audible alert 'too low terrain.' we briefly discussed and concluded the alert was a result of our high speed; and we could see there was no terrain in or near our flight path. Our discussion set us behind the airplane. We promptly slowed and put the gear down to configure to land. The gear came down and we continued to configure to flaps 10. Once we were on final we made the decision to go missed because we were not in a normal position to land (not configured by 1;000 ft).as the flaps retracted through 10 degrees and the gear was raising we received another audible: 'too low gear.' our missed was successful and our second approach on the RNAV X 28R was flown well within the speed restrictions to a safe landing.the VFR weather in boise distracted me from monitoring the speed restrictions along the approach. It is a requirement to follow speed restrictions on approaches that one is cleared to fly. I knew that then and I know it now. This situation is a great example of the exact reason to follow those restrictions. It is easy on VFR days to neglect the requirements set on an approach.our responsibility to go missed when not in a normal position to land is an example of the value of following our procedures.

Original NASA ASRS Text

Title: Air carrier First Officer reported receiving a GPWS terrain alert on arrival into BOI; followed by recognition of an unstabilized approach that resulted in a go-around.

Narrative: We chose to fly the RNAV X 28R into Boise. We briefed the approach in cruise including the 180 speed restriction at CUBAR. We flew the plane through CUBAR at 210 by mistake. Shortly afterward we heard the audible alert 'TOO LOW TERRAIN.' We briefly discussed and concluded the alert was a result of our high speed; and we could see there was no terrain in or near our flight path. Our discussion set us behind the airplane. We promptly slowed and put the gear down to configure to land. The gear came down and we continued to configure to flaps 10. Once we were on final we made the decision to go missed because we were not in a normal position to land (not configured by 1;000 ft).As the flaps retracted through 10 degrees and the gear was raising we received another audible: 'TOO LOW GEAR.' Our missed was successful and our second approach on the RNAV X 28R was flown well within the speed restrictions to a safe landing.The VFR weather in Boise distracted me from monitoring the speed restrictions along the approach. It is a requirement to follow speed restrictions on approaches that one is cleared to fly. I knew that then and I know it now. This situation is a great example of the exact reason to follow those restrictions. It is easy on VFR days to neglect the requirements set on an approach.Our responsibility to go missed when not in a normal position to land is an example of the value of following our procedures.

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.

Attributes
ACN	1750931
Time
Date	202007
Local Time Of Day	1201-1800
Place
Locale Reference	BOI.TRACON
State Reference	ID
Aircraft 1
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Descent
Flight Plan	IFR
Person 1
Function	First Officer
Qualification	Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine
Events
Anomaly	Inflight Event / Encounter CFTT / CFIT Inflight Event / Encounter Unstabilized Approach

Air carrier first officer reported receiving a GPWS terrain alert on arrival into boi; followed by recognition of an unstabilized approach that resulted in a go-around.