Narrative:

To start off I just want to say it involves an unsafe situation/event with the aircraft but also a safety issue with the constant actions and mentality of the controllers at the facility.starting with the event; aircraft Z was one of four aircraft on final to runway 28R at fll. The aircraft order on final is as follows: aircraft X; aircraft Y; aircraft Z and aircraft a (aircraft a is the last aircraft for a good 20 miles). All aircraft are instructed to maintain 170 knots until a 5 mile final. When aircraft X drops off my scope there is 4.5 miles between him and aircraft Y who is slowing because they are just inside a 5 mile final. We have a display (passur) at the left of the positions that show the ground radar at fll so we can see taxiing traffic and give gaps when necessary (I will note not all controllers do this). When I glanced at the display I noticed one aircraft taxiing and one waiting out there as aircraft X is short final; but that would be the gap to hit. When aircraft Y drops off the scope there are 3.5 miles between him and aircraft Z with a slightly faster speed so it is still compressing. When aircraft Z is on about a mile to half mile final I notice he is at 300 feet and starting a climb. At this point aircraft a is 3.6 miles behind aircraft Z and no one is behind aircraft a. I look at the passur screen to see if aircraft Y was stuck on the runway or didn't clear; but what I saw was a departure rolling down the runway. Not only am I baffled as to why; but now I'm worried because aircraft Z is straight out climbing and here pops up aircraft B a half mile in front of him climbing same heading and about 600 feet apart and closing. I know the tower can provide visual separation; but they did nothing [to] turn aircraft Z or aircraft B until the departure end when the collision alert is going off because aircraft Z is speeding up and aircraft B climbs into them. This is completely unsafe and shouldn't have happened.the safety issue is with fll and the mentality they have there that lead to this incident and multiple others that have happened before this. It is a well-known fact that the controllers at fll have the idea of if I have a departure and no gap I'll just clear them for takeoff or line up and wait and send the next one around. This happens constantly and has become what I believe is the normal thinking for them and they just do it as seen above. They are constantly putting aircraft in gaps that can easily be seen as not big enough for a departure. All it takes is one stuck mike; radio failure or miss applied go-around procedure for a major accident to happen. When they are busy they have asked us to give them 5 miles between arrivals which we do; but how do [you] need 4-5 miles for a departure and yet put an aircraft in a 3.5 mile and closing gap. The mindset of these controllers is negligent and this is a major safety issue. They are going to get someone killed.we have two runways at fll and try to balance it as best as we can. We do have a best operating practice; that in times of busy traffic to send certain arrival gates to certain runways; but most of the time it is not a balanced arrival push so one runway gets hit more if you follow it. To not follow it (and balance the traffic to suit our needs) draws attention of certain supervisors who then yell and force you to do it. We also use 5 miles and 170 knots when we can to help them; but it is not always possible when we get so strung out. They are supposed to balance the departures between the two runways which is not always followed as well. We both need to balance the traffic better; in-air and on the ground. But this mentality of lock and load and go around has to stop. This has been going on for months now and it is getting worse; and for safety I cannot in good conscience let this continue without something being said.

Google
 

Original NASA ASRS Text

Title: MIA TRACON Controller reported FLL Tower has a constantly practiced procedure of allowing aircraft to line up and wait while traffic is on a short enough final to require a go-around. They then have issued a takeoff clearance which creates a conflict on climbout.

Narrative: To start off I just want to say it involves an unsafe situation/event with the aircraft but also a safety issue with the constant actions and mentality of the controllers at the facility.Starting with the event; Aircraft Z was one of four aircraft on final to Runway 28R at FLL. The aircraft order on final is as follows: Aircraft X; Aircraft Y; Aircraft Z and Aircraft A (Aircraft A is the last aircraft for a good 20 miles). All aircraft are instructed to maintain 170 knots until a 5 mile final. When Aircraft X drops off my scope there is 4.5 miles between him and Aircraft Y who is slowing because they are just inside a 5 mile final. We have a display (PASSUR) at the left of the positions that show the ground radar at FLL so we can see taxiing traffic and give gaps when necessary (I will note not all controllers do this). When I glanced at the display I noticed one aircraft taxiing and one waiting out there as Aircraft X is short final; but that would be the gap to hit. When Aircraft Y drops off the scope there are 3.5 miles between him and Aircraft Z with a slightly faster speed so it is still compressing. When Aircraft Z is on about a mile to half mile final I notice he is at 300 feet and starting a climb. At this point Aircraft A is 3.6 miles behind Aircraft Z and no one is behind Aircraft A. I look at the PASSUR screen to see if Aircraft Y was stuck on the runway or didn't clear; but what I saw was a departure rolling down the runway. Not only am I baffled as to why; but now I'm worried because Aircraft Z is straight out climbing and here pops up Aircraft B a half mile in front of him climbing same heading and about 600 feet apart and closing. I know the Tower can provide visual separation; but they did nothing [to] turn Aircraft Z or Aircraft B until the departure end when the collision alert is going off because Aircraft Z is speeding up and Aircraft B climbs into them. This is completely unsafe and shouldn't have happened.The safety issue is with FLL and the mentality they have there that lead to this incident and multiple others that have happened before this. It is a well-known fact that the controllers at FLL have the idea of if I have a departure and no gap I'll just clear them for takeoff or line up and wait and send the next one around. This happens constantly and has become what I believe is the normal thinking for them and they just do it as seen above. They are constantly putting aircraft in gaps that can easily be seen as not big enough for a departure. All it takes is one stuck mike; radio failure or miss applied go-around procedure for a major accident to happen. When they are busy they have asked us to give them 5 miles between arrivals which we do; but how do [you] need 4-5 miles for a departure and yet put an aircraft in a 3.5 mile and closing gap. The mindset of these controllers is negligent and this is a major safety issue. They are going to get someone killed.We have two runways at FLL and try to balance it as best as we can. We do have a best operating practice; that in times of busy traffic to send certain arrival gates to certain runways; but most of the time it is not a balanced arrival push so one runway gets hit more if you follow it. To not follow it (and balance the traffic to suit our needs) draws attention of certain supervisors who then yell and force you to do it. We also use 5 miles and 170 knots when we can to help them; but it is not always possible when we get so strung out. They are supposed to balance the departures between the two runways which is not always followed as well. We both need to balance the traffic better; in-air and on the ground. But this mentality of lock and load and go around has to stop. This has been going on for months now and it is getting worse; and for safety I cannot in good conscience let this continue without something being said.

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.