Narrative:

Aircraft #1 was wbound at FL360; traffic converging from the northwest; swbound at FL360. I had turned the traffic 10 degrees right to resolve the situation. With the wind out of the southwest; this slowed the traffic further and pushed the situation past my western sector boundary. Not knowing next sector's traffic situation; I felt it necessary to resolve in my airspace. There was additional traffic to aircraft #1 at approximately 5 O'clock position; 6 mi; faster; to turn aircraft 1 'right' would require a turn on this traffic to match. My radar associate and I discussed options. Associate suggested climbing one of them to FL380. Given aircraft type I decided on aircraft #1. I first asked if they could accept higher. They said 'affirmative.' I climbed them to FL380. The conflict alert started flashing at approximately FL366. I amended their altitude to FL370. They advised they went through it and were coming down. When the traffic situation was realized (conflict alert); I looked to my left; where the sector is (2 spaces over) that owns FL370 and above; there was nobody there; the controller signed in was about 5 ft behind me facing away from his sector talking to the supervisor. His radar display would've shown an aircraft at FL360 climbing. Mine; as required; only depicts aircraft up to FL370; not FL380 (maybe it should). The primary factor in this error is that we had just opened this new sector; established as the 'oom' (hoosier) sector. This lies above btv (batesville); the one I was working at the time of the error. Prior to this; I would've owned these altitudes. As a matter of experience these sectors consist of my only radar sectors ever worked since being certified at ZID (actually these altitudes). Sometimes the supervisors combine oom and btv (further confusion). The only training we received was a briefing and a computer based instrument in the month preceding; stating the altitudes and frequency. Additionally; the radar map correctly depicting oom wasn't established until 18 days later for 'procedural reasons.'

Related reports:

Google
 

Original NASA ASRS Text

Title: ZID CTLR EXPERIENCED OPERROR AT APPROX FL360 WHEN FAILING TO PROVIDE TIMELY CTL ACTIONS; CITING RECENT AIRSPACE CHANGES AS CONTRIBUTORY.

Narrative: ACFT #1 WAS WBOUND AT FL360; TFC CONVERGING FROM THE NW; SWBOUND AT FL360. I HAD TURNED THE TFC 10 DEGS R TO RESOLVE THE SITUATION. WITH THE WIND OUT OF THE SW; THIS SLOWED THE TFC FURTHER AND PUSHED THE SITUATION PAST MY WESTERN SECTOR BOUNDARY. NOT KNOWING NEXT SECTOR'S TFC SITUATION; I FELT IT NECESSARY TO RESOLVE IN MY AIRSPACE. THERE WAS ADDITIONAL TFC TO ACFT #1 AT APPROX 5 O'CLOCK POS; 6 MI; FASTER; TO TURN ACFT 1 'R' WOULD REQUIRE A TURN ON THIS TFC TO MATCH. MY RADAR ASSOCIATE AND I DISCUSSED OPTIONS. ASSOCIATE SUGGESTED CLBING ONE OF THEM TO FL380. GIVEN ACFT TYPE I DECIDED ON ACFT #1. I FIRST ASKED IF THEY COULD ACCEPT HIGHER. THEY SAID 'AFFIRMATIVE.' I CLBED THEM TO FL380. THE CONFLICT ALERT STARTED FLASHING AT APPROX FL366. I AMENDED THEIR ALT TO FL370. THEY ADVISED THEY WENT THROUGH IT AND WERE COMING DOWN. WHEN THE TFC SITUATION WAS REALIZED (CONFLICT ALERT); I LOOKED TO MY L; WHERE THE SECTOR IS (2 SPACES OVER) THAT OWNS FL370 AND ABOVE; THERE WAS NOBODY THERE; THE CTLR SIGNED IN WAS ABOUT 5 FT BEHIND ME FACING AWAY FROM HIS SECTOR TALKING TO THE SUPVR. HIS RADAR DISPLAY WOULD'VE SHOWN AN ACFT AT FL360 CLBING. MINE; AS REQUIRED; ONLY DEPICTS ACFT UP TO FL370; NOT FL380 (MAYBE IT SHOULD). THE PRIMARY FACTOR IN THIS ERROR IS THAT WE HAD JUST OPENED THIS NEW SECTOR; ESTABLISHED AS THE 'OOM' (HOOSIER) SECTOR. THIS LIES ABOVE BTV (BATESVILLE); THE ONE I WAS WORKING AT THE TIME OF THE ERROR. PRIOR TO THIS; I WOULD'VE OWNED THESE ALTS. AS A MATTER OF EXPERIENCE THESE SECTORS CONSIST OF MY ONLY RADAR SECTORS EVER WORKED SINCE BEING CERTIFIED AT ZID (ACTUALLY THESE ALTS). SOMETIMES THE SUPVRS COMBINE OOM AND BTV (FURTHER CONFUSION). THE ONLY TRAINING WE RECEIVED WAS A BRIEFING AND A COMPUTER BASED INST IN THE MONTH PRECEDING; STATING THE ALTS AND FREQ. ADDITIONALLY; THE RADAR MAP CORRECTLY DEPICTING OOM WASN'T ESTABLISHED UNTIL 18 DAYS LATER FOR 'PROCEDURAL REASONS.'

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