Narrative:

I was working aircraft #1 northbound to bli at FL340. Aircraft #2 a hawker hunter was handed off to me from low altitude sector 5 up to FL230 H10.J15.imb..twf.boi. I was working high altitude sector 16; one man; normal traffic. I pointed out aircraft #2 to an adjoining high altitude sector for climb and then climbed aircraft #2 to FL350. I did not recognize that aircraft #2 was non-rvsm. He was a civilian pilot flying to hif. He was improperly using a military call sign. He should not have filed into rvsm airspace; and when cleared into rvsm airspace; he did not say 'non-rvsm; climbing to FL350.' instead he said 'leaving 230 for 350.' I recognized that aircraft #2 and aircraft #1 could be a problem; so I cleared aircraft #2 direct twf to go behind aircraft #1. I then sequenced 3 pdx arrs. After that sequencing (8-9 xmissions) I returned to the aircraft #1 and aircraft #2 situation and asked aircraft #2 his rate of climb. He said 1000 FPM. I asked him to increase to 1500 FPM and called traffic aircraft #1. He leveled at FL350 about 15 NM west of aircraft #1. I called traffic to aircraft #1 saying '17 mi west at FL350.' aircraft #2 flew behind aircraft #1 and 2 hits inside 5 NM bubble 4.77; 4.73 NM and 1100 ft according to ZSE data. I did not recognize that aircraft #2 was non-rvsm. My data blocks were set to #2; I will increase this size to 4 and turn up my fdb brightness so the coral box around the 'C' is brighter. I only realized non-rvsm when conflict alert flashed once when they were past each other; at the point of error. No uret red alerts on these two; no conflict alert. These were all contributing factors. I was healthy and alert -- no contributing human factors on my part like sickness; tired; etc and no distrs. I wrongly assumed he was military flight and rvsm.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZSE CTLR EXPERIENCED OPERROR AT APPROX FL340 FORGETTING THE FACT THAT AN ACFT INVOLVED WAS NOT RVSM EQUIPPED.

Narrative: I WAS WORKING ACFT #1 NBOUND TO BLI AT FL340. ACFT #2 A HAWKER HUNTER WAS HANDED OFF TO ME FROM LOW ALT SECTOR 5 UP TO FL230 H10.J15.IMB..TWF.BOI. I WAS WORKING HIGH ALT SECTOR 16; ONE MAN; NORMAL TFC. I POINTED OUT ACFT #2 TO AN ADJOINING HIGH ALT SECTOR FOR CLB AND THEN CLBED ACFT #2 TO FL350. I DID NOT RECOGNIZE THAT ACFT #2 WAS NON-RVSM. HE WAS A CIVILIAN PLT FLYING TO HIF. HE WAS IMPROPERLY USING A MIL CALL SIGN. HE SHOULD NOT HAVE FILED INTO RVSM AIRSPACE; AND WHEN CLRED INTO RVSM AIRSPACE; HE DID NOT SAY 'NON-RVSM; CLBING TO FL350.' INSTEAD HE SAID 'LEAVING 230 FOR 350.' I RECOGNIZED THAT ACFT #2 AND ACFT #1 COULD BE A PROB; SO I CLRED ACFT #2 DIRECT TWF TO GO BEHIND ACFT #1. I THEN SEQUENCED 3 PDX ARRS. AFTER THAT SEQUENCING (8-9 XMISSIONS) I RETURNED TO THE ACFT #1 AND ACFT #2 SITUATION AND ASKED ACFT #2 HIS RATE OF CLB. HE SAID 1000 FPM. I ASKED HIM TO INCREASE TO 1500 FPM AND CALLED TFC ACFT #1. HE LEVELED AT FL350 ABOUT 15 NM W OF ACFT #1. I CALLED TFC TO ACFT #1 SAYING '17 MI W AT FL350.' ACFT #2 FLEW BEHIND ACFT #1 AND 2 HITS INSIDE 5 NM BUBBLE 4.77; 4.73 NM AND 1100 FT ACCORDING TO ZSE DATA. I DID NOT RECOGNIZE THAT ACFT #2 WAS NON-RVSM. MY DATA BLOCKS WERE SET TO #2; I WILL INCREASE THIS SIZE TO 4 AND TURN UP MY FDB BRIGHTNESS SO THE CORAL BOX AROUND THE 'C' IS BRIGHTER. I ONLY REALIZED NON-RVSM WHEN CONFLICT ALERT FLASHED ONCE WHEN THEY WERE PAST EACH OTHER; AT THE POINT OF ERROR. NO URET RED ALERTS ON THESE TWO; NO CONFLICT ALERT. THESE WERE ALL CONTRIBUTING FACTORS. I WAS HEALTHY AND ALERT -- NO CONTRIBUTING HUMAN FACTORS ON MY PART LIKE SICKNESS; TIRED; ETC AND NO DISTRS. I WRONGLY ASSUMED HE WAS MIL FLT AND RVSM.

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.