Narrative:

I attempted to call N90 TRACON to approve a frg arrival (aircraft X) at 11;000 feet under the jfk arrivals at 12;000 feet. This is a common request. I received no answer on the line. I descended the frg arrival to 11;000 feet and made the required point out to the adjacent TRACON sector; which was approved and began handing off. At this point I intended to try the TRACON again and slow the frg arrival to 250 knots but fell behind because I was busy. I noticed TRACON descending the jfk arrival; aircraft Y; from 12;000 feet. Immediately I turned aircraft X and issued a wake turbulence advisory. The pilot said he had the traffic in sight and would rather turn in the opposite direction; which I approved and then told them to contact the TRACON controller; who didn't have the handoff yet; but I mistakenly thought did due to the conflict alert flashing. The TRACON controller then called me and said they didn't see aircraft X and that now it was 'radar contact.' I realize I didn't do everything right here but I also feel the TRACON controller must have seen aircraft X at 11;000 feet since it was in handoff status. Immediately following this the TRACON controller refused to accept the handoff on 2 jfk arrivals which I needed to vector out and delay for about 10 minutes without any heads- up.I should have gotten approval for the jfk; frg stack; slowed the frg arrival to 250 knots; and not changed aircraft X's frequency until they had the handoff. If there was a 'glitch' in the system and the TRACON controller really didn't see the guy in handoff status then that needs to be fixed. Otherwise it would be disappointing to think a controller would descend a perfectly separated airplane through another and then refuse to accept handoffs on multiple international arrivals just to prove a point.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZBW Center Controller reported a TRACON Controller would not take their handoffs.

Narrative: I attempted to call N90 TRACON to approve a FRG arrival (Aircraft X) at 11;000 feet under the JFK arrivals at 12;000 feet. This is a common request. I received no answer on the line. I descended the FRG arrival to 11;000 feet and made the required point out to the adjacent TRACON sector; which was approved and began handing off. At this point I intended to try the TRACON again and slow the FRG arrival to 250 knots but fell behind because I was busy. I noticed TRACON descending the JFK arrival; Aircraft Y; from 12;000 feet. Immediately I turned Aircraft X and issued a wake turbulence advisory. The pilot said he had the traffic in sight and would rather turn in the opposite direction; which I approved and then told them to contact the TRACON controller; who didn't have the handoff yet; but I mistakenly thought did due to the conflict alert flashing. The TRACON Controller then called me and said they didn't see Aircraft X and that now it was 'radar contact.' I realize I didn't do everything right here but I also feel the TRACON controller must have seen Aircraft X at 11;000 feet since it was in handoff status. Immediately following this the TRACON Controller refused to accept the handoff on 2 JFK arrivals which I needed to vector out and delay for about 10 minutes without any heads- up.I should have gotten approval for the JFK; FRG stack; slowed the FRG arrival to 250 knots; and not changed Aircraft X's frequency until they had the handoff. If there was a 'glitch' in the system and the TRACON controller really didn't see the guy in handoff status then that needs to be fixed. Otherwise it would be disappointing to think a controller would descend a perfectly separated airplane through another and then refuse to accept handoffs on multiple international arrivals just to prove a point.

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.