Center controller reported an unsafe operation where he did not remember giving a higher altitude to...

Narrative:

I was working the mid shift after a heavy complex rush of over 20 + aircraft on frequency by myself and aircraft X was direct pye climbing to what I thought was FL300. I was also working aircraft Y direct tij that was opposite direction level at FL310. I thought aircraft X was only climbing to FL300 and was not merging with the opposite direction aircraft so no merging target procedures needed to be issued. ZOA accepted radar on aircraft X so I switched radio communications. I then observed conflict alert as aircraft X continued to climb through FL300 putting him in conflict with aircraft Y and I immediately issued control instructions to aircraft Y to turn 30R to avoid the aircraft X and also called ZOA. They turned the aircraft X 40R I believe. Aircraft Y turned but received an RA to climb; which then put him in conflict with an aircraft at FL320. After the situation had been remedied I cleared aircraft Y back on course. I then alerted the operations manager of the situation. After review of the falcon it was determined that during the rush I originally climbed the aircraft X to the requested altitude of 300. Later aircraft X asked to climb to FL320 and I apparently climbed him to FL320 and failed to update the data block. I was overwhelmed with the amount of aircraft and frequency congestion and made a mistake and take full responsibility. The mid shifts are becoming too overwhelming and congested with aircraft at later times and I have brought this to the attention of my area rep and the union. I have also voiced my complaints and concerns about the overwhelming traffic levels to management numerous times. I am consistently working 20 + aircraft after the sectors are combined and the complexity is becoming too great. Tonight I was issuing departure clearances off smx and running an arrival into sba while sct was slamming me with multiple dual departures. Additionally; it is so busy that I do not have time to run over to the a side and filter through the oceanic strips that I need for my sector. Aircraft are constantly stepping on each other along with ZOA calling to coordinate oceanic aircraft that I don't have time to go to the a side to shuffle through the strips. I take full responsibility for my error; but we as controllers need to stop caring more about our breaks and support the mission of separating aircraft. Our staffing levels are probably too low to accommodate a third person here; but that would sure help.

Original NASA ASRS Text

Title: Center Controller reported an unsafe operation where he did not remember giving a higher altitude to an aircraft that later climbs and became a conflict with opposite direction traffic.

Narrative: I was working the mid shift after a heavy complex rush of over 20 + aircraft on frequency by myself and Aircraft X was direct PYE climbing to what I thought was FL300. I was also working Aircraft Y direct TIJ that was opposite direction level at FL310. I thought Aircraft X was only climbing to FL300 and was not merging with the opposite direction aircraft so no merging target procedures needed to be issued. ZOA accepted radar on Aircraft X so I switched radio communications. I then observed conflict alert as Aircraft X continued to climb through FL300 putting him in conflict with Aircraft Y and I immediately issued control instructions to Aircraft Y to turn 30R to avoid the Aircraft X and also called ZOA. They turned the Aircraft X 40R I believe. Aircraft Y turned but received an RA to climb; which then put him in conflict with an aircraft at FL320. After the situation had been remedied I cleared Aircraft Y back on course. I then alerted the Operations Manager of the situation. After review of the Falcon it was determined that during the rush I originally climbed the Aircraft X to the requested altitude of 300. Later Aircraft X asked to climb to FL320 and I apparently climbed him to FL320 and failed to update the data block. I was overwhelmed with the amount of aircraft and frequency congestion and made a mistake and take full responsibility. The mid shifts are becoming too overwhelming and congested with aircraft at later times and I have brought this to the attention of my area rep and the union. I have also voiced my complaints and concerns about the overwhelming traffic levels to management numerous times. I am consistently working 20 + aircraft after the sectors are combined and the complexity is becoming too great. Tonight I was issuing departure clearances off SMX and running an arrival into SBA while SCT was slamming me with multiple dual departures. Additionally; it is so busy that I do not have time to run over to the A side and filter through the Oceanic strips that I need for my sector. Aircraft are constantly stepping on each other along with ZOA calling to coordinate oceanic aircraft that I don't have time to go to the A side to shuffle through the strips. I take full responsibility for my error; but we as controllers need to stop caring more about our breaks and support the mission of separating aircraft. Our staffing levels are probably too low to accommodate a third person here; but that would sure help.

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

Attributes
ACN	1381243
Time
Date	201608
Local Time Of Day	0601-1200
Place
Locale Reference	ZLA.ARTCC
State Reference	CA
Environment
Light	Night
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 10
Person 2
Function	First Officer Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Total 63 Flight Crew Type 63
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy

Center controller reported an unsafe operation where he did not remember giving a higher altitude to an aircraft that later climbs and became a conflict with opposite direction traffic.