Narrative:

As a coordinator, I received request from hill tower for 'zoom' departure. (Straight up climb of fgt to 17,000 within 5 NM of airport, then westbound via 255 right climb at or below FL310.) I called ci-1 and asked how it looked for zoom departure. Ci-1 responded 'I think we can handle that'. I took this to mean released, and said I would call back with vifno time. I then called salt lake center and released 8 mi radius to them with 6 min vifno of XA40. I then was distracted by another situation building 40 NM west of hif AFB, and neglected to call ci-1 back with time of release. When 'zoom' departure became airborne, the departure controller was not aware that he had even been released. No loss of separation occurred, however air carrier X had just previously flown through protected airspace.

Google
 

Original NASA ASRS Text

Title: IMPROPER RELEASE OF AIRSPACE RESULTED IN ACR ENTERING AREA WITHOUT AUTHORIZATION.

Narrative: AS A COORDINATOR, I RECEIVED REQUEST FROM HILL TWR FOR 'ZOOM' DEP. (STRAIGHT UP CLIMB OF FGT TO 17,000 WITHIN 5 NM OF ARPT, THEN WBND VIA 255 R CLIMB AT OR BELOW FL310.) I CALLED CI-1 AND ASKED HOW IT LOOKED FOR ZOOM DEP. CI-1 RESPONDED 'I THINK WE CAN HANDLE THAT'. I TOOK THIS TO MEAN RELEASED, AND SAID I WOULD CALL BACK WITH VIFNO TIME. I THEN CALLED SALT LAKE CENTER AND RELEASED 8 MI RADIUS TO THEM WITH 6 MIN VIFNO OF XA40. I THEN WAS DISTRACTED BY ANOTHER SITUATION BUILDING 40 NM W OF HIF AFB, AND NEGLECTED TO CALL CI-1 BACK WITH TIME OF RELEASE. WHEN 'ZOOM' DEP BECAME AIRBORNE, THE DEP CTLR WAS NOT AWARE THAT HE HAD EVEN BEEN RELEASED. NO LOSS OF SEPARATION OCCURRED, HOWEVER ACR X HAD JUST PREVIOUSLY FLOWN THROUGH PROTECTED AIRSPACE.

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