Enroute controller described a conflict event between a military aircraft on an ir route and an IFR ...

Narrative:

A heavy B1 bomber; was flying on [an airway] in my sector. In the middle of the sector; the aircraft descended IFR below radar coverage. The last altitude I saw on the B1 was 095. ZZZ tower called me for a release on a super king air 200. I told them that I had a B1 on a route near their airspace; and that I did not have that aircraft on radar. The tower controller then said to me; 'but he's a lifeguard; he has to get out.' I then said released. After I got off the landline with ZZZ tower; I looked again at the track coast for the B1; and it indicated that the aircraft was at 529 knots. I realized that I would not have the required non-radar separation with the two aircraft. I called the tower back to cancel the release; but when they answered the landline; they said that the king air was already airborne. At that point; the king air checked onto the frequency; and I gave the aircraft a 260 degree heading to avoid. I feel the event happened for two reasons. First; because the aircraft at ZZZ was a lifeguard and because the tower controller was insistent that they get off the ground; I felt pressured not to delay their flight. The second reason is because of the location of [the airway]. It is a seldom used procedure; and I had not seen or worked [this airway] in at least 5 years. The exit point for [the airway] is in conflict with the departure procedure at ZZZ. I think that this event can be prevented from re-occurring by changing the exit point of [this airway] to a location prior to the current location; and/or changing the altitude of the route to an altitude that would keep the flight within radar coverage when the flight is within the vicinity of ZZZ. I also think that the event could be prevented from re-occurring by providing further guidance to ZZZ tower about [the airway] and the difficulties it presents to the center controller when the route is in use. This way; when the center controller informs the ZZZ tower controller that [the airway] is in use; they will not persist in requesting immediate departures.

Original NASA ASRS Text

Title: Enroute Controller described a conflict event between a military aircraft on an IR route and an IFR Lifeguard flight departure; the reporter suggesting the IR route be adjusted a prevent future occurrences.

Narrative: A heavy B1 bomber; was flying on [an airway] in my sector. In the middle of the sector; the aircraft descended IFR below RADAR coverage. The last altitude I saw on the B1 was 095. ZZZ Tower called me for a release on a Super King Air 200. I told them that I had a B1 on a route near their airspace; and that I did not have that aircraft on RADAR. The Tower Controller then said to me; 'But he's a Lifeguard; he has to get out.' I then said released. After I got off the landline with ZZZ Tower; I looked again at the track coast for the B1; and it indicated that the aircraft was at 529 knots. I realized that I would not have the required non-RADAR separation with the two aircraft. I called the Tower back to cancel the release; but when they answered the landline; they said that the King Air was already airborne. At that point; the King Air checked onto the frequency; and I gave the aircraft a 260 degree heading to avoid. I feel the event happened for two reasons. First; because the aircraft at ZZZ was a Lifeguard and because the Tower Controller was insistent that they get off the ground; I felt pressured not to delay their flight. The second reason is because of the location of [the airway]. It is a seldom used procedure; and I had not seen or worked [this airway] in at least 5 years. The exit point for [the airway] is in conflict with the departure procedure at ZZZ. I think that this event can be prevented from re-occurring by changing the exit point of [this airway] to a location prior to the current location; and/or changing the altitude of the route to an altitude that would keep the flight within RADAR coverage when the flight is within the vicinity of ZZZ. I also think that the event could be prevented from re-occurring by providing further guidance to ZZZ Tower about [the airway] and the difficulties it presents to the Center Controller when the route is in use. This way; when the Center Controller informs the ZZZ Tower Controller that [the airway] is in use; they will not persist in requesting immediate departures.

Data retrieved from NASA's ASRS site as of July 2013 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.

Attributes
ACN	1103150
Time
Date	201307
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.ARTCC
State Reference	US
Aircraft 1
Make Model Name	Super King Air 200
Flight Phase	Initial Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	B1 Lancer
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

Enroute controller described a conflict event between a military aircraft on an ir route and an IFR lifeguard flight departure; the reporter suggesting the ir route be adjusted a prevent future occurrences.