Date: 201503
Local time of day: 1201-1800
Location: ZDV.ARTCC, CO
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZDV
ATC / advisory: Center ZDV
Reporter organization: Government
Reporter function: Enroute; Handoff / Assist
Reporter qualification: Air Traffic Control Fully Certified
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic; Flight Crew Returned To Clearance
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: I was in the control room and noticed that the Sector 12 Controller seemed to be busy.  I asked if he wanted me to split out half of the sectors he was working; but he was indecisive.  At that moment Aircraft X informed the controller that he was late starting down for the RNAV arrival.  He asked if he could get relief from the crossing restriction at RAMMS.The R-side controller asked me if I could coordinate a point out to North Departure while he called Approach to ask for the waiver; there were no planes in the vicinity.As I was grabbing my headset the R-side made the call to Approach control; which denied the request and told the R-side to spin the Aircraft.  I had just plugged into the adjacent sector to call north departure when the R-side controller grabbed the handset; also plugged into that sector for communication reasons and issued a clearance to Aircraft X to spin.  Unfortunately; I had already grabbed the shout line to North Departure.  I waited for the R-side to stop talking; and then he asked me again to help him with the Point-out. As I reached for the shout line button; I noticed it was already selected; so I made the point out to North Departure.After a bit I noticed that Aircraft X wasn't turning and was now at least 5 miles in approaches airspace; nearly level at the altitude assigned previously; according the RNAV restrictions(the pilot had really descended quickly); still flashing to approach.  I realized that the R-side had issued the clearance; not on the frequency; but on the shout line to North Departure.  At that point; since I was in the process of opening that sector anyway; I told the pilot that apparently approach control couldn't take the handoff and I issued a right 360 to Aircraft X.Soon after that; I received a shout line call from approach asking what was going on with Aircraft X; now 10 miles inside their airspace; still flashing at approach; with no handoff.  I advised the approach controller the aircraft was in a right 360.  After the aircraft was obviously in the turn; the approach controller accepted the handoff and I shipped the Aircraft to approach.Honestly; the controller who refused the handoff should face disciplinary actions.  This pilot asked for relief from the crossing restriction.  There were no aircraft within 20 miles of Aircraft X and the demand on the airport was very light at that time of the morning.  Due to a transmission error; which was partly my fault for selecting the shout line right before the R-side tried to issue the clearance; the pilot had no clue that he needed to do anything.  He actually crossed just 1 or 2 thousand feet above the window for the RNAV arrival.  By the time I realized that the aircraft wasn't turning; Aircraft X was established on the RVAV arrival at altitude and speed; with no other aircraft within 20 miles of him.  The Approach controller seemed to make me spin this aircraft out of spite; or negligence; either one is a tragedy.I have worked arrivals into Denver for the past 25 years and I have never had so much trouble with TRACON controllers as I have the past 2 years.  The skill of the Denver TRACON is highly suspect in my view.  Each day; the controllers in my area have a new story of how terrible the TRACON controllers are.  It is embarrassing.  There was a time when I held TRACON controllers in high regard because of the traffic I watched them handle.  Now; as center controllers; we spoon feed approach; but if they don't get everything exactly as they want; they complain; make us spin aircraft; or make immediate calls to the supervisors or operations managers.  Somebody needs to get this system fixed. Aircraft X failed to make his crossing restriction and TRACON made us spin the aircraft just to prove a point.   Then they forced us to violate their airspace before taking the handoff.  Inexcusable.




Synopsis: A Denver Center Controller describes a situation where an aircraft is reporting that it will be high at a crossing restriction and wants relief. The Controller attempts coordination to be high with Denver TRACON (D01) and the D01 controller replies they are unable and to spin the aircraft. The aircraft is told to turn but is slow in doing so and violates D01 airspace. The Controller then goes on to complain about the performance of the D01 controllers and how they think there service is diminishing over the last couple of years.