Narrative:

Air carrier X was handed off to me southbound at 310; I had control to climb via LOA reference sector 68 traffic shown to me. I observed pertinent crossing overflight traffic; air carrier Y; westbound at 340; and climbed air carrier X to 330. Subsequently; sector 68 descended air carrier Y to 320. Conflict alert went off too late for any vector/altitude resolution. The closest point was 800 ft and 3.8 miles. It would be good practice for sector 68 to hold onto ocean departures when we are on the psx playbook until they are clear of the overflight traffic. There is a lot of data block overlap.

Google
 

Original NASA ASRS Text

Title: Enroute Controller experienced a loss of separation during multiple play book re-route procedures; the reports listing weather; non-familiar routing's; Data Block overlap; traffic complexity/volume as causal factors.

Narrative: Air Carrier X was handed off to me southbound at 310; I had control to climb via LOA reference Sector 68 traffic shown to me. I observed pertinent crossing overflight traffic; Air Carrier Y; westbound at 340; and climbed Air Carrier X to 330. Subsequently; Sector 68 descended Air Carrier Y to 320. Conflict Alert went off too late for any vector/altitude resolution. The closest point was 800 FT and 3.8 miles. It would be good practice for Sector 68 to hold onto ocean departures when we are on the PSX playbook until they are clear of the overflight traffic. There is a lot of Data Block overlap.

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