A B737-700 first officer executed a go-around from an unstabilized approach to abq runway 3 and was ...

Narrative:

We were cleared the visual approach to runway 3 crossing the ridge line from the east. Configuration and sequencing looked good until the pilot flying cut downwind off to a tight base. I made a challenge that we were high on base. The pilot flying acknowledged. We were not stabilized at a thousand feet so as pilo monitoring; I directed a go-around. The PF carried the approach a couple hundred feet more and satisfying his curiosity; he initiated the go-around. I notified tower and we were assigned a climb to 8;000 ft and a turn to 310 degrees. We were then given a visual to runway 8. I set the navaids up and made the modifications to the MCP. Stable on the downwind; I updated the box. Tower asked for the reason for the go-around and; after I answered; he gave us the option to use runway 3. I asked the pilot flying which runway he preferred and he said runway 3 as that was the runway he thought we were going to anyway. I reset the MCP and navaids; and updated the box. As he was hand flying; I went to set his course select window; which he asked me not to. The go-around maneuver was smooth and deliberate; but I was surprised that after tower assigning runway 8 and the change of the MCP and navaids; which I recall verbalizing; that the PF felt a bit out of the loop as to aircraft setup. The second approach was established at 1;000 ft and a nice landing was made.a go-around causes a lot of activity and in the case of a directed go-around; the pilot flying is not always focused on what will happen but is still thinking about what has happened. I should be more careful on the set; acknowledge; and verify the sequence to make sure everyone is staying up with the progress of the aircraft.

Original NASA ASRS Text

Title: A B737-700 First Officer executed a go-around from an unstabilized approach to ABQ Runway 3 and was assigned Runway 8 but preferred Runway 3 for the second successful approach.

Narrative: We were cleared the visual approach to Runway 3 crossing the ridge line from the east. Configuration and sequencing looked good until the Pilot Flying cut downwind off to a tight base. I made a challenge that we were high on base. The Pilot Flying acknowledged. We were not stabilized at a thousand feet so as Pilo Monitoring; I directed a go-around. The PF carried the approach a couple hundred feet more and satisfying his curiosity; he initiated the go-around. I notified Tower and we were assigned a climb to 8;000 FT and a turn to 310 degrees. We were then given a visual to Runway 8. I set the NAVAIDs up and made the modifications to the MCP. Stable on the downwind; I updated the box. Tower asked for the reason for the go-around and; after I answered; he gave us the option to use Runway 3. I asked the Pilot Flying which runway he preferred and he said Runway 3 as that was the runway he thought we were going to anyway. I reset the MCP and NAVAIDs; and updated the box. As he was hand flying; I went to set his Course Select window; which he asked me not to. The go-around maneuver was smooth and deliberate; but I was surprised that after Tower assigning Runway 8 and the change of the MCP and NAVAIDs; which I recall verbalizing; that the PF felt a bit out of the loop as to aircraft setup. The second approach was established at 1;000 FT and a nice landing was made.A go-around causes a lot of activity and in the case of a directed go-around; the Pilot Flying is not always focused on what will happen but is still thinking about what has happened. I should be more careful on the set; acknowledge; and verify the sequence to make sure everyone is staying up with the progress of the aircraft.

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.

Attributes
ACN	1125286
Time
Date	201310
Local Time Of Day	0601-1200
Place
Locale Reference	ABQ.TRACON
State Reference	NM
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Captain Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 145 Flight Crew Type 27000
Events
Anomaly	Deviation - Altitude Undershoot Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Unstabilized Approach

A B737-700 first officer executed a go-around from an unstabilized approach to abq runway 3 and was assigned runway 8 but preferred runway 3 for the second successful approach.