Narrative:

I had just split off R13 from R12. Within 5 mins I had both a system deviation and a system error. Mdy 3 and mdy 1S was active. Cpr X was nwbound V159 from gef. Traffic was sbound from pzd at FL190. Air carrier Y was over pzd northbound FL190. Cpr Z was approximately maximum 290020 at FL230 direct vld, landing vld. It was necessary to vector him north into an arrival corridor to avoid mdy 1S. When I took the sector it was fairly busy. It got worse, I shortly called for a d-side controller. The first aircraft to call was cpr X rechking on frequency. I had no data block. When I took the data block (after request to R12), I also took another data block around pzd. Apparently I also took air carrier Y back from automatic handoff to ZTL. After cpr Z cleared traffic nwbound I descended him to FL200 and shortly thereafter turned him to a 030 heading. The strong west wind made the turn extremely slow and before he cleared the sbound traffic, he had blown east so far that another turn was given (350 degrees). Cpr X was descended to 190 but separation had been lost. At this same time frame, air carrier Y crossed the ZTL boundary without a handoff. The scope during this time was flickering. It was soon replaced. Key factors include the wind, the fact that mdy 3 is now further south causing more vectoring, high altitude turbulence causing high altitude aircraft into low strata. I was also up late and often during the previous night because my daughter was sick. After further consultations , I feel cpr Z did not comply promptly with his turn and shall be held accountable for the error and possibly the deviation.

Google
 

Original NASA ASRS Text

Title: CPR Z DSCNT TO OCCUPIED ALT HAD LTSS FROM CPR X. SYS ERROR. ACR Y UNCOORD PENETRATION OF AIRSPACE. OPDEV.

Narrative: I HAD JUST SPLIT OFF R13 FROM R12. WITHIN 5 MINS I HAD BOTH A SYS DEV AND A SYS ERROR. MDY 3 AND MDY 1S WAS ACTIVE. CPR X WAS NWBOUND V159 FROM GEF. TFC WAS SBOUND FROM PZD AT FL190. ACR Y WAS OVER PZD NBOUND FL190. CPR Z WAS APPROX MAX 290020 AT FL230 DIRECT VLD, LNDG VLD. IT WAS NECESSARY TO VECTOR HIM N INTO AN ARR CORRIDOR TO AVOID MDY 1S. WHEN I TOOK THE SECTOR IT WAS FAIRLY BUSY. IT GOT WORSE, I SHORTLY CALLED FOR A D-SIDE CTLR. THE FIRST ACFT TO CALL WAS CPR X RECHKING ON FREQ. I HAD NO DATA BLOCK. WHEN I TOOK THE DATA BLOCK (AFTER REQUEST TO R12), I ALSO TOOK ANOTHER DATA BLOCK AROUND PZD. APPARENTLY I ALSO TOOK ACR Y BACK FROM AUTO HDOF TO ZTL. AFTER CPR Z CLRED TFC NWBOUND I DSNDED HIM TO FL200 AND SHORTLY THEREAFTER TURNED HIM TO A 030 HDG. THE STRONG W WIND MADE THE TURN EXTREMELY SLOW AND BEFORE HE CLRED THE SBOUND TFC, HE HAD BLOWN E SO FAR THAT ANOTHER TURN WAS GIVEN (350 DEGS). CPR X WAS DSNDED TO 190 BUT SEPARATION HAD BEEN LOST. AT THIS SAME TIME FRAME, ACR Y CROSSED THE ZTL BOUNDARY WITHOUT A HDOF. THE SCOPE DURING THIS TIME WAS FLICKERING. IT WAS SOON REPLACED. KEY FACTORS INCLUDE THE WIND, THE FACT THAT MDY 3 IS NOW FURTHER S CAUSING MORE VECTORING, HIGH ALT TURB CAUSING HIGH ALT ACFT INTO LOW STRATA. I WAS ALSO UP LATE AND OFTEN DURING THE PREVIOUS NIGHT BECAUSE MY DAUGHTER WAS SICK. AFTER FURTHER CONSULTATIONS , I FEEL CPR Z DID NOT COMPLY PROMPTLY WITH HIS TURN AND SHALL BE HELD ACCOUNTABLE FOR THE ERROR AND POSSIBLY THE DEV.

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.