Narrative:

I received an altitude restr of 13000 ft from ord south departure. Because of the ongoing problem we have at that sector of repositioning the altitude restr 'sticker,' I could not put the 'sticker' in my airspace. Therefore it was not in my 'scan' area (airspace). I climbed traffic off mdw to FL210. At 12700 ft I noticed an untagged target at 14000 ft in my departure path. I told my aircraft to maintain 13000 ft. He said he'd have to go through it but would return to 13000 ft I issued traffic he reported it in sight. I told him maintain visual separation although standard separation may have been compromised. I feel the primary reason this situation occurred was the problem we have of repositioning the altitude restr sticker where it is obvious. Callback conversation with reporter revealed the following information: reporter stated there was no less than standard separation. Reporter indicated a blinking sticker is displayed on the scope automatically when activated by an ARTS keyboard entry. The departure controller will make this entry when coordination is received from the center regarding over flight traffic. The reporter alleges the sticker cannot be moved to a more advantageous location where it can be seen to call attention to the restr for traffic. Reporter said a ucr has been filed and returned acknowledging the problem. Reporter indicated that the software change needed to remedy the problem requires approval from outside the facility before it can be changed.

Google
 

Original NASA ASRS Text

Title: RPTR FAILED TO INITIALLY RESTRICT A DEP TO 13000 FT BASED ON PREVIOUS INTRAFAC COORD BY THE DEP CTLR FOR TFC AT 14000 FT. RPTR CLAIMS THE RESTR 'STICKER' WAS NOT IN SCAN AREA.

Narrative: I RECEIVED AN ALT RESTR OF 13000 FT FROM ORD S DEP. BECAUSE OF THE ONGOING PROB WE HAVE AT THAT SECTOR OF REPOSITIONING THE ALT RESTR 'STICKER,' I COULD NOT PUT THE 'STICKER' IN MY AIRSPACE. THEREFORE IT WAS NOT IN MY 'SCAN' AREA (AIRSPACE). I CLBED TFC OFF MDW TO FL210. AT 12700 FT I NOTICED AN UNTAGGED TARGET AT 14000 FT IN MY DEP PATH. I TOLD MY ACFT TO MAINTAIN 13000 FT. HE SAID HE'D HAVE TO GO THROUGH IT BUT WOULD RETURN TO 13000 FT I ISSUED TFC HE RPTED IT IN SIGHT. I TOLD HIM MAINTAIN VISUAL SEPARATION ALTHOUGH STANDARD SEPARATION MAY HAVE BEEN COMPROMISED. I FEEL THE PRIMARY REASON THIS SIT OCCURRED WAS THE PROB WE HAVE OF REPOSITIONING THE ALT RESTR STICKER WHERE IT IS OBVIOUS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THERE WAS NO LTSS. RPTR INDICATED A BLINKING STICKER IS DISPLAYED ON THE SCOPE AUTOMATICALLY WHEN ACTIVATED BY AN ARTS KEYBOARD ENTRY. THE DEP CTLR WILL MAKE THIS ENTRY WHEN COORD IS RECEIVED FROM THE CTR REGARDING OVER FLT TFC. THE RPTR ALLEGES THE STICKER CANNOT BE MOVED TO A MORE ADVANTAGEOUS LOCATION WHERE IT CAN BE SEEN TO CALL ATTN TO THE RESTR FOR TFC. RPTR SAID A UCR HAS BEEN FILED AND RETURNED ACKNOWLEDGING THE PROB. RPTR INDICATED THAT THE SOFTWARE CHANGE NEEDED TO REMEDY THE PROB REQUIRES APPROVAL FROM OUTSIDE THE FACILITY BEFORE IT CAN BE CHANGED.

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.