Narrative:

N90 put aircraft X on the ILS runway 34. Shortly after aircraft Y was put on the ILS for runway 34 following aircraft X with a 100 knot overtake. Aircraft Y did slow it back and a aircraft Z was inbound behind aircraft Y . I noticed that the radar wasn't displaying the flying miles warning so I sent aircraft Y around. I got no response from aircraft Y so I issued the go around again. I coordinated with N90 lga sector and he got mad that I would send him around. It was IFR conditions and I felt I was losing separation. Aircraft Y was given a 090 heading at 2000 feet and handed back off to N90 as was coordinated.I continued working and eventually departed [an] aircraft where the N90 controller yelled that I was stopped. It got into a shouting match where I said I did not hear of any stop. If I was stopped I never acknowledged it because I was busy working on top of dealing with the go around. The N90 controller stopped my departures. After about 20 minutes roughly I got put on individual releases. I called N90 traffic management unit (tmu) to find out if it was necessary to put us on individual releases and they said they didn't know anything. I called N90 lga supervisor and asked why we were on individual releases and he didn't have an answer as to why but he would ask about it. Eventually I was given an excuse that it was a west restriction that wasn't in the log and we were not heavy on west departures. Most were going north and south or on a low level tech route. This leads me to think individual releases was a punishment by the TRACON controller that tmu and the supervisor were unaware of. The supervisor told me over the phone that it was a separation error after they looked at it. I said that I would [report] it but I was mostly upset that when I send someone around for safety that I not be berated or punished. I would require N90 to give me a final that isn't losing separation. I also would require them to act like professionals so when I send someone around they don't throw a fit and punish our departures with a stop and individual releases. It's not our fault no one bids N90 because of its reputation so their staffing is short. Guess what hpn has a staffing issue too because I was the only controller in the building as this was going on. If they cannot act like professional adults then give us our radar room back at hpn and we will do the job. It seems if they can't use visual approaches with the aircraft then it either doesn't work or barely works. I would rather we control our approach than someone who doesn't care or take any pride in the job. They have a 'its good enough attitude' and if not hpn will fix it or take the baby deal as they call it.

Related reports:

Google
 

Original NASA ASRS Text

Title: HPN Tower Controller reported a go-around instruction due to insufficient spacing on the final approach course.

Narrative: N90 put Aircraft X on the ILS Runway 34. Shortly after Aircraft Y was put on the ILS for runway 34 following Aircraft X with a 100 knot overtake. Aircraft Y did slow it back and a Aircraft Z was inbound behind Aircraft Y . I noticed that the radar wasn't displaying the flying miles warning so I sent Aircraft Y around. I got no response from Aircraft Y so I issued the go around again. I coordinated with N90 LGA sector and he got mad that I would send him around. It was IFR conditions and I felt I was losing separation. Aircraft Y was given a 090 heading at 2000 feet and handed back off to N90 as was coordinated.I continued working and eventually departed [an] aircraft where the N90 controller yelled that I was stopped. It got into a shouting match where I said I did not hear of any stop. If I was stopped I never acknowledged it because I was busy working on top of dealing with the go around. The N90 controller stopped my departures. After about 20 minutes roughly I got put on individual releases. I called N90 Traffic Management Unit (TMU) to find out if it was necessary to put us on individual releases and they said they didn't know anything. I called N90 LGA Supervisor and asked why we were on individual releases and he didn't have an answer as to why but he would ask about it. Eventually I was given an excuse that it was a west restriction that wasn't in the log and we were not heavy on west departures. Most were going north and south or on a low level tech route. This leads me to think individual releases was a punishment by the TRACON controller that TMU and the supervisor were unaware of. The supervisor told me over the phone that it was a separation error after they looked at it. I said that I would [report] it but I was mostly upset that when I send someone around for safety that I not be berated or punished. I would require N90 to give me a final that isn't losing separation. I also would require them to act like professionals so when I send someone around they don't throw a fit and punish our departures with a stop and individual releases. It's not our fault no one bids N90 because of its reputation so their staffing is short. Guess what HPN has a staffing issue too because I was the only Controller in the building as this was going on. If they cannot act like professional adults then give us our radar room back at HPN and we will do the job. It seems if they can't use Visual Approaches with the aircraft then it either doesn't work or barely works. I would rather we control our approach than someone who doesn't care or take any pride in the job. They have a 'its good enough attitude' and if not HPN will fix it or take the baby deal as they call it.

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.