Air carrier X possible less than standard separation from air carrier Y and air carrier Z. Possible ...

Attributes
ACN	162725
Time
Date	199011
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : int
State Reference	NC
Altitude	msl bound lower : 11000 msl bound upper : 15000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : ztl artcc : zdc tower : dca
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	cruise other
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	descent other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller non radar : 3 controller radar : 4
ASRS Report	162725
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Miss Distance	horizontal : 30000
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Inter Facility Coordination Failure other

Narrative:

I was working sector R29 just finishing up inbound push to clt. Took a point out from ZDC (south boston) sector W22 on limited data block air carrier X. I held up air carrier Y at 160 and released air carrier X to 150. Subsequently I got side tracked. It had been a busy day and I had been hassled earlier by another controller. It was 10 min before enf of my shift. I was thinking about going home and starting the weekend. I descended air carrier Y and later climbed air carrier Z off gso for atl. I observed limited data block outside my airspace. I do not believe a loss of sep occurred, but I'm not sure neither is my 'D' side. No mode C intruder went off and neither did the snitch as far as I know, but I'm not sure. I can't remember consciously separating the traffic. Suggestions. Be careful especially in the last 30 min of shift and put a 'watch' data block on your scope so as not to forget limited data block. Otherwise its too easy to forget them.

Original NASA ASRS Text

Title: ACR X POSSIBLE LESS THAN STANDARD SEPARATION FROM ACR Y AND ACR Z. POSSIBLE SYSTEM ERROR.

Narrative: I WAS WORKING SECTOR R29 JUST FINISHING UP INBND PUSH TO CLT. TOOK A POINT OUT FROM ZDC (S BOSTON) SECTOR W22 ON LIMITED DATA BLOCK ACR X. I HELD UP ACR Y AT 160 AND RELEASED ACR X TO 150. SUBSEQUENTLY I GOT SIDE TRACKED. IT HAD BEEN A BUSY DAY AND I HAD BEEN HASSLED EARLIER BY ANOTHER CTLR. IT WAS 10 MIN BEFORE ENF OF MY SHIFT. I WAS THINKING ABOUT GOING HOME AND STARTING THE WEEKEND. I DSNDED ACR Y AND LATER CLBED ACR Z OFF GSO FOR ATL. I OBSERVED LIMITED DATA BLOCK OUTSIDE MY AIRSPACE. I DO NOT BELIEVE A LOSS OF SEP OCCURRED, BUT I'M NOT SURE NEITHER IS MY 'D' SIDE. NO MODE C INTRUDER WENT OFF AND NEITHER DID THE SNITCH AS FAR AS I KNOW, BUT I'M NOT SURE. I CAN'T REMEMBER CONSCIOUSLY SEPARATING THE TFC. SUGGESTIONS. BE CAREFUL ESPECIALLY IN THE LAST 30 MIN OF SHIFT AND PUT A 'WATCH' DATA BLOCK ON YOUR SCOPE SO AS NOT TO FORGET LIMITED DATA BLOCK. OTHERWISE ITS TOO EASY TO FORGET THEM.

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.

Air carrier X possible less than standard separation from air carrier Y and air carrier Z. Possible system error.