Narrative:

The local regional office routinely issues a waiver to a rocketry club to launch model rockets up to 8000 ft within the confines of V-12 about 40 miles west of the ape VOR. The waiver gives a location reference off the rod VOR, the rod 115 radial at 29 DME. Unfortunately, rod isn't depicted on our radar maps. On 02/sat/2002 this waiver was in effect and since we don't depict rod, we used a sectional to locate the launch site and placed a tag there on our radar scopes. They had a C172 on a local IFR training flight depart I78 going to uyf at 3000 ft. I was vectoring the C172 around where I thought the rocket launch was and attempting an automated handoff to day ATCT. Day approach called me to advise me I was vectoring the C172 toward the rocket launch, not away from it. At the very least, we need these rocket launches referenced to the ape VOR, but I don't think anyone should be allowed to launch rockets into a federal airway up to 7000 ft AGL. Callback conversation with reporter revealed the following information: reporter alleges that the position plotted for the rocketry tfr did not agree with the depicted tfr with day TRACON. The controller did not know if a copy of the waiver was available with the operational shift supervisor. When questioned, the area supervisor did not appear to be aware of who to coordination with, or obtain verification about, the waiver. The controller's greatest concern is that the tfr was not identified from a NAVAID displayed from the affected sector

Related reports:

Google
 

Original NASA ASRS Text

Title: CMH DEP CTLR INADVERTENTLY VECTORS C172 TOWARDS, INSTEAD OF AWAY FROM AMATEUR ROCKETRY FIRING RESTRED AIRSPACE ALONG V12.

Narrative: THE LOCAL REGIONAL OFFICE ROUTINELY ISSUES A WAIVER TO A ROCKETRY CLUB TO LAUNCH MODEL ROCKETS UP TO 8000 FT WITHIN THE CONFINES OF V-12 ABOUT 40 MILES WEST OF THE APE VOR. THE WAIVER GIVES A LOCATION REFERENCE OFF THE ROD VOR, THE ROD 115 RADIAL AT 29 DME. UNFORTUNATELY, ROD ISN'T DEPICTED ON OUR RADAR MAPS. ON 02/SAT/2002 THIS WAIVER WAS IN EFFECT AND SINCE WE DON'T DEPICT ROD, WE USED A SECTIONAL TO LOCATE THE LAUNCH SITE AND PLACED A TAG THERE ON OUR RADAR SCOPES. THEY HAD A C172 ON A LCL IFR TRAINING FLT DEPART I78 GOING TO UYF AT 3000 FT. I WAS VECTORING THE C172 AROUND WHERE I THOUGHT THE ROCKET LAUNCH WAS AND ATTEMPTING AN AUTOMATED HANDOFF TO DAY ATCT. DAY APCH CALLED ME TO ADVISE ME I WAS VECTORING THE C172 TOWARD THE ROCKET LAUNCH, NOT AWAY FROM IT. AT THE VERY LEAST, WE NEED THESE ROCKET LAUNCHES REFERENCED TO THE APE VOR, BUT I DON'T THINK ANYONE SHOULD BE ALLOWED TO LAUNCH ROCKETS INTO A FEDERAL AIRWAY UP TO 7000 FT AGL. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR ALLEGES THAT THE POSITION PLOTTED FOR THE ROCKETRY TFR DID NOT AGREE WITH THE DEPICTED TFR WITH DAY TRACON. THE CTLR DID NOT KNOW IF A COPY OF THE WAIVER WAS AVAILABLE WITH THE OPERATIONAL SHIFT SUPVR. WHEN QUESTIONED, THE AREA SUPVR DID NOT APPEAR TO BE AWARE OF WHO TO COORD WITH, OR OBTAIN VERIFICATION ABOUT, THE WAIVER. THE CTLR'S GREATEST CONCERN IS THAT THE TFR WAS NOT IDENTIFIED FROM A NAVAID DISPLAYED FROM THE AFFECTED SECTOR

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