E120 landing gtr experienced go around followed by sequencing confusion for subsequent approach.

Attributes
ACN	581700
Time
Date	200304
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : gtr.airport
State Reference	MS
Altitude	agl bound lower : 300 agl bound upper : 1500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : mht.tower
Operator	common carrier : air carrier
Make Model Name	Brasilia EMB-120 All Series
Operating Under FAR Part	Part 121
Flight Phase	descent : approach landing : missed approach
Route In Use	approach : visual arrival : on vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Beechjet 400
Flight Phase	landing : roll
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 19000 flight time type : 12000
ASRS Report	581700
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	conflict : airborne less severe non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance flight crew : took precautionary avoidance action flight crew : executed go around
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	ATC Human Performance

Narrative:

Approximately 3 mi from gtr received vectors for sequence. Traffic was called approximately 15 mi from gtr. We finally got visual approximately 10 mi from gtr on traffic and airport. Visual approach was issued, we squared base to final and contacted tower at gtr. To get more spacing, we slightly s-turned on final -- tower was aware of this. Approximately 5 mi final, we got landing clearance. Aircraft we were following was touching down. The aircraft, BE40, missed an intersection and slowly proceeded to end of runway. We decided, too close, so, we went around. On downwind, controller advised a baron on final that we would be turning base in front of him and to do a left 360 degree turn. We were not on base. We extended downwind because we could not see the traffic that was called to us. We finally got the traffic and advised controller to let him go in and we would follow. Controller told us to turn base and cleared us to land. Baron was to follow us, which he did. We stayed high pattern altitude because the baron was low and converging our path. We continued and landed. Problem: aircraft that caused go around was exceptionally slow exiting runway. Problem: controller did not know exact location of baron on final and did not know normal size of pattern. After go around, we need about 5-6 mi final to have aircraft in landing confign.

Original NASA ASRS Text

Title: E120 LNDG GTR EXPERIENCED GAR FOLLOWED BY SEQUENCING CONFUSION FOR SUBSEQUENT APCH.

Narrative: APPROX 3 MI FROM GTR RECEIVED VECTORS FOR SEQUENCE. TFC WAS CALLED APPROX 15 MI FROM GTR. WE FINALLY GOT VISUAL APPROX 10 MI FROM GTR ON TFC AND ARPT. VISUAL APCH WAS ISSUED, WE SQUARED BASE TO FINAL AND CONTACTED TWR AT GTR. TO GET MORE SPACING, WE SLIGHTLY S-TURNED ON FINAL -- TWR WAS AWARE OF THIS. APPROX 5 MI FINAL, WE GOT LNDG CLRNC. ACFT WE WERE FOLLOWING WAS TOUCHING DOWN. THE ACFT, BE40, MISSED AN INTXN AND SLOWLY PROCEEDED TO END OF RWY. WE DECIDED, TOO CLOSE, SO, WE WENT AROUND. ON DOWNWIND, CTLR ADVISED A BARON ON FINAL THAT WE WOULD BE TURNING BASE IN FRONT OF HIM AND TO DO A L 360 DEG TURN. WE WERE NOT ON BASE. WE EXTENDED DOWNWIND BECAUSE WE COULD NOT SEE THE TFC THAT WAS CALLED TO US. WE FINALLY GOT THE TFC AND ADVISED CTLR TO LET HIM GO IN AND WE WOULD FOLLOW. CTLR TOLD US TO TURN BASE AND CLRED US TO LAND. BARON WAS TO FOLLOW US, WHICH HE DID. WE STAYED HIGH PATTERN ALT BECAUSE THE BARON WAS LOW AND CONVERGING OUR PATH. WE CONTINUED AND LANDED. PROB: ACFT THAT CAUSED GAR WAS EXCEPTIONALLY SLOW EXITING RWY. PROB: CTLR DID NOT KNOW EXACT LOCATION OF BARON ON FINAL AND DID NOT KNOW NORMAL SIZE OF PATTERN. AFTER GAR, WE NEED ABOUT 5-6 MI FINAL TO HAVE ACFT IN LNDG CONFIGN.

Data retrieved from NASA's ASRS site as of July 2007 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.