B737 is issued ATC go around because of traffic on runway at fll.

Attributes
ACN	596440
Time
Date	200310
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : fll.airport
State Reference	FL
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tower : fll.tower
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	landing : go around
Route In Use	approach : visual
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : fll.tower
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	ground : position and hold
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 220 flight time total : 10000 flight time type : 1200
ASRS Report	596440
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 12000 flight time type : 5000
ASRS Report	596439
Events
Anomaly	conflict : ground less severe
Independent Detector	other flight crewa other flight crewb
Resolutory Action	controller : issued new clearance flight crew : took evasive action flight crew : executed go around
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 1200 vertical : 400
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

Fll approach cleared aircraft for visual approach to runway 9L. On short final, 400 ft AGL, tower instructed us to go around. After successful go around, vectored for another visual approach to runway 9L. Approach completed to full stop landing. After aircraft parked at gate, I called fll tower to inquire reason for go around. Controller apologized for having us go around and told me he had put an aircraft into position on runway 9L and had then been distraction by a call from ZMA. Upon looking up, he saw 2 aircraft (one being ours) and had us go around. Chain of events: 1) don't know why problem arose -- we never saw other aircraft. 2) I know how it arose -- controller put aircraft in position and forgot him. 3) don't know contributing factors of why he did this. 4) don't know how it was discovered -- dumb luck, I fear. 5) corrective action was go around, executed flawlessly by first officer. Human performances: 1) can't speak to controller's performance. 2) flight crew performed well and professionally. Recommendations: eliminate 'position and hold' during twilight, pre-dawn, dark and IFR.

Original NASA ASRS Text

Title: B737 IS ISSUED ATC GAR BECAUSE OF TFC ON RWY AT FLL.

Narrative: FLL APCH CLRED ACFT FOR VISUAL APCH TO RWY 9L. ON SHORT FINAL, 400 FT AGL, TWR INSTRUCTED US TO GO AROUND. AFTER SUCCESSFUL GAR, VECTORED FOR ANOTHER VISUAL APCH TO RWY 9L. APCH COMPLETED TO FULL STOP LNDG. AFTER ACFT PARKED AT GATE, I CALLED FLL TWR TO INQUIRE REASON FOR GAR. CTLR APOLOGIZED FOR HAVING US GO AROUND AND TOLD ME HE HAD PUT AN ACFT INTO POS ON RWY 9L AND HAD THEN BEEN DISTR BY A CALL FROM ZMA. UPON LOOKING UP, HE SAW 2 ACFT (ONE BEING OURS) AND HAD US GO AROUND. CHAIN OF EVENTS: 1) DON'T KNOW WHY PROB AROSE -- WE NEVER SAW OTHER ACFT. 2) I KNOW HOW IT AROSE -- CTLR PUT ACFT IN POS AND FORGOT HIM. 3) DON'T KNOW CONTRIBUTING FACTORS OF WHY HE DID THIS. 4) DON'T KNOW HOW IT WAS DISCOVERED -- DUMB LUCK, I FEAR. 5) CORRECTIVE ACTION WAS GAR, EXECUTED FLAWLESSLY BY FO. HUMAN PERFORMANCES: 1) CAN'T SPEAK TO CTLR'S PERFORMANCE. 2) FLT CREW PERFORMED WELL AND PROFESSIONALLY. RECOMMENDATIONS: ELIMINATE 'POS AND HOLD' DURING TWILIGHT, PRE-DAWN, DARK AND IFR.

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.