Narrative:

I was training on the r-side of the orf high sector (sector 34). The volume was steady and high. No weather noted. Good rides. The fighter auto popped on the scope. It is not uncommon for them to auto pop when it says FL231. But this was different. The fighter continued to climb. Then I received a call from approach to inform us that fighter was a priority aircraft low on fuel and trying to return to pxt. The approach controller said that fighter was climbing to FL280. I immediately responded directing them to stop the aircraft's climb at FL260. I then told the approach controller where the traffic was located so that he could see why the fighter needed to not be in my airspace; especially with no prior coordination or approval to be climbing. The fighter continued to climb beyond FL280 and was now looking like it would be a direct merge with aircraft Y southbound at FL320. I issued a traffic alert to aircraft Y and a control instruction to turn 40 degrees left immediately and continued to issue traffic information. For at that point; I had no idea what the fighter would do and no communication with the fighter. Aircraft Y responded immediately; said he was climbing and turning. The fighter continued to climb to FL320 merging with aircraft Y's target. Then they separated as aircraft Y climbed out of the altitude and had turned; as well as the fighter seemed to now be descending. They were 6.24 miles apart and both at FL320 at the time of the target merging. When they were separated; I returned aircraft Y to FL320 and southbound on course. I asked to make sure there were no injuries. Meanwhile; the fighter continued to be traffic for a rdu arrival at FL260 and descending; and another aircraft at FL280. Then fighter checked in on my frequency. I instructed him to maintain FL260 and to say intentions. I also quoted him all the additional traffic. I coordinated with sby sector (sector 54) since this was mostly occurring in that sector. I then transferred communications of the fighter to sector 54. Please note that the fighter was choosing to return to pxt; when many other airports were available for landing. I feel that many aircrafts' safety were put at risk unnecessarily.it has been explained to me that this is normal procedure for the fighter when low on fuel. But I can't imagine how anyone would think it is safe to allow a fighter jet to fly at free while in IFR airspace outside of restricted military airspace with so many civilian flights safety at risk. It is my understanding that when a situation occurs; the aircraft is to land as soon as practical. The procedure for the military in non-military airspace should be seriously reviewed.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZDC Center Instructor and Developmental reported a military fighter auto-popped on the scope and continued to climb unrestricted. Separation was lost due to the military traffic climbing aggressively and without coordination.

Narrative: I was training on the R-side of the ORF high sector (Sector 34). The volume was steady and high. No weather noted. Good rides. The Fighter auto popped on the scope. It is not uncommon for them to auto pop when it says FL231. But this was different. The Fighter continued to climb. Then I received a call from Approach to inform us that Fighter was a priority aircraft low on fuel and trying to return to PXT. The approach controller said that Fighter was climbing to FL280. I immediately responded directing them to stop the aircraft's climb at FL260. I then told the approach controller where the traffic was located so that he could see why the Fighter needed to not be in my airspace; especially with no prior coordination or approval to be climbing. The Fighter continued to climb beyond FL280 and was now looking like it would be a direct merge with Aircraft Y southbound at FL320. I issued a traffic alert to Aircraft Y and a control instruction to turn 40 degrees left immediately and continued to issue traffic information. For at that point; I had no idea what the Fighter would do and no communication with the Fighter. Aircraft Y responded immediately; said he was climbing and turning. The Fighter continued to climb to FL320 merging with Aircraft Y's target. Then they separated as Aircraft Y climbed out of the altitude and had turned; as well as the Fighter seemed to now be descending. They were 6.24 miles apart and both at FL320 at the time of the target merging. When they were separated; I returned Aircraft Y to FL320 and southbound on course. I asked to make sure there were no injuries. Meanwhile; the Fighter continued to be traffic for a RDU arrival at FL260 and descending; and another aircraft at FL280. Then Fighter checked in on my frequency. I instructed him to maintain FL260 and to say intentions. I also quoted him all the additional traffic. I coordinated with SBY sector (Sector 54) since this was mostly occurring in that sector. I then transferred communications of the Fighter to sector 54. Please note that the Fighter was choosing to return to PXT; when many other airports were available for landing. I feel that many aircrafts' safety were put at risk unnecessarily.It has been explained to me that this is normal procedure for the Fighter when low on fuel. But I can't imagine how anyone would think it is safe to allow a fighter jet to fly at free while in IFR airspace outside of restricted military airspace with so many civilian flights safety at risk. It is my understanding that when a situation occurs; the aircraft is to land as soon as practical. The procedure for the military in non-military airspace should be seriously reviewed.

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.