Narrative:

I was working the radar side by myself. My airspace at the time was from 35;000-38;000 feet. A departure southeast bound was requesting 41;000 feet. I climbed the aircraft to 37;000 feet and started a handoff to ZKC92. I noticed there was a limited data block 20 miles south of my airspace that had apparently been flashed through my sector from the controller that I had relieved 10 minutes earlier.upon bringing up the data block I determined that aircraft X was going to go behind aircraft Y without incident. In fact aircraft X was climbing at such a good rate I also determined that aircraft X was going to be well above aircraft Y which ensured two forms of separation! ZKC92 accepted the hand off which in turn gives approval for the climb. Moments later I got a call from the ZKC92 controller to stop aircraft X's climb at 35;000 feet. The controller sarcastically added that aircraft X needed to be stopped for traffic that came from my airspace. I told the ZKC controller that I would stop aircraft X at 35;000 feet and gave my initials.I stopped aircraft X's climb at 35;000 feet; obtained the read back; entered it in the data block and handed off aircraft X back to ZKC92. I transferred communications to ZKC92. Seconds later I noticed aircraft X climbing through 35;000 feet still in my airspace. I immediately called ZKC92 to make certain that aircraft X got his clearance correctly. He responded that he climbed the aircraft! I confirmed that he climbed the aircraft; in my airspace; without approval. He responded; 'yes; I'm trying to provide a service!' I responded that perhaps he should atsap that. He replied that he would and that the atsap would read ZMP handed him a 'deal.'I immediately notified my supervisor and area manager. They reviewed the scenario on falcon and determined to file a mandatory occurrence report (mor) on ZKC controller.in my opinion this is a very malicious and dangerous individual. He made the decision out of spite to climb an aircraft that was not his control in another controller's airspace. Aircraft Y had been out of my airspace for 90 miles and aircraft X was more than 40 miles out of my airspace when they passed 8 miles behind and aircraft X level at 41;000 feet. This is an example of a rogue; vigilante controller in ZKC.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZMP Controller reported a ZKC controller climbing an aircraft in his airspace without approval.

Narrative: I was working the Radar side by myself. My airspace at the time was from 35;000-38;000 feet. A departure southeast bound was requesting 41;000 feet. I climbed the aircraft to 37;000 feet and started a handoff to ZKC92. I noticed there was a limited data block 20 miles south of my airspace that had apparently been flashed through my sector from the controller that I had relieved 10 minutes earlier.Upon bringing up the data block I determined that aircraft X was going to go behind aircraft Y without incident. In fact aircraft X was climbing at such a good rate I also determined that aircraft X was going to be well above aircraft Y which ensured two forms of separation! ZKC92 accepted the hand off which in turn gives approval for the climb. Moments later I got a call from the ZKC92 controller to stop aircraft X's climb at 35;000 feet. The controller sarcastically added that aircraft X needed to be stopped for traffic that came from my airspace. I told the ZKC controller that I would stop aircraft X at 35;000 feet and gave my initials.I stopped aircraft X's climb at 35;000 feet; obtained the read back; entered it in the data block and handed off aircraft X back to ZKC92. I transferred communications to ZKC92. Seconds later I noticed aircraft X climbing through 35;000 feet still in my airspace. I immediately called ZKC92 to make certain that aircraft X got his clearance correctly. He responded that he climbed the aircraft! I confirmed that he climbed the aircraft; in my airspace; without approval. He responded; 'Yes; I'm trying to provide a service!' I responded that perhaps he should ATSAP that. He replied that he would and that the ATSAP would read ZMP handed him a 'deal.'I immediately notified my Supervisor and Area Manager. They reviewed the scenario on FALCON and determined to file a Mandatory Occurrence Report (MOR) on ZKC controller.In my opinion this is a very malicious and dangerous individual. He made the decision out of spite to climb an aircraft that was not his control in another controller's airspace. Aircraft Y had been out of my airspace for 90 miles and aircraft X was more than 40 miles out of my airspace when they passed 8 miles behind and aircraft X level at 41;000 feet. This is an example of a rogue; vigilante controller in ZKC.

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.