F11 controller described a go around event when traffic on final executed the procedure during heavy...

Attributes
ACN	1015562
Time
Date	201206
Local Time Of Day	0001-0600
Place
Locale Reference	MCO.Airport
State Reference	FL
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Landing
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Landing
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Inflight Event / Encounter Fuel Issue

Narrative:

Heavy to extreme precipitation approaching mco from the west; the first B737 was on final for runway 35R with a second 7-8 miles in trail. Prearranged coordination with the tower was in the event of a missed approach they would be issued 2;000; eastbound. The first B737 went around due to being to fast; he first made contact I said 'climb and maintain 3;000; say your intentions?' he stated he was low on fuel and wanted to try again but if he did he needed to go right back around. I knew his company was behind him so I climbed the first B737 to 3;000 to protect for the second B737 in case he decided to go missed as well. In the mean time the second B737 decided to come out because company did; final was working the second B737 not sure what heading was assigned but he was climbed to 4;000 turning southeast bound. Final descended the second B737 to 1;600 and continued to a southbound heading. Separation was lost. Don't try and cram airplanes into an airport when extreme weather is imminent; stop arrivals before these problems arise.

Original NASA ASRS Text

Title: F11 Controller described a go around event when traffic on final executed the procedure during heavy precipitation; the reporter indicating that efforts to land too many aircraft; given the weather; contributed to the event.

Narrative: Heavy to extreme precipitation approaching MCO from the west; the first B737 was on final for Runway 35R with a second 7-8 miles in trail. Prearranged coordination with the Tower was in the event of a missed approach they would be issued 2;000; eastbound. The first B737 went around due to being to fast; he first made contact I said 'Climb and maintain 3;000; say your intentions?' He stated he was low on fuel and wanted to try again but if he did he needed to go right back around. I knew his company was behind him so I climbed the first B737 to 3;000 to protect for the second B737 in case he decided to go missed as well. In the mean time the second B737 decided to come out because company did; final was working the second B737 not sure what heading was assigned but he was climbed to 4;000 turning southeast bound. Final descended the second B737 to 1;600 and continued to a southbound heading. Separation was lost. Don't try and cram airplanes into an airport when extreme weather is imminent; stop arrivals before these problems arise.

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.

F11 controller described a go around event when traffic on final executed the procedure during heavy precipitation; the reporter indicating that efforts to land too many aircraft; given the weather; contributed to the event.