Center controllers reported an aircraft in rvsm airspace that was not rvsm capable.

Attributes
ACN	1417944
Time
Date	201701
Local Time Of Day	1801-2400
Place
Locale Reference	ZAU.ARTCC
State Reference	IL
Aircraft 1
Make Model Name	Learjet 31
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	Direct
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 2.5
Person 2
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 10.0
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

Narrative:

While I was working the ZAU sector; I was reviewing my routes to ensure correctness. I also read what was in the remarks. I noticed that aircraft X had written negative rvsm; but he was filed rvsm capable; non-rnav. I called back to ZMP so that they could check with the pilot to see if he meant non rnav; not non rvsm. He told them that he in fact was negative rvsm; and it was filed wrong. ZMP fixed it in their computer. Aircraft X was above rvsm altitudes at the time; however he flew for quite sometime outside my airspace at 41000b43000 feet and many other altitudes to get there. I am unaware if there was ever a loss of rvsm separation; however I feel I should fill this out because I was aware of this. I told my quality control local department of this event. I then coordinated appropriately with all adjacent sectors for any new clearances and point outs needed.I believe airlines and companies need to have some type of fail safe system in place to not allow an aircraft who is negative rvsm capable file as rvsm capable based upon their tail number.

Original NASA ASRS Text

Title: Center Controllers reported an aircraft in RVSM airspace that was not RVSM capable.

Narrative: While I was working the ZAU sector; I was reviewing my routes to ensure correctness. I also read what was in the remarks. I noticed that Aircraft X had written negative RVSM; but he was filed RVSM capable; non-rnav. I called back to ZMP so that they could check with the pilot to see if he meant Non Rnav; not Non RVSM. He told them that he in fact was negative RVSM; and it was filed wrong. ZMP fixed it in their computer. Aircraft X was above RVSM altitudes at the time; however he flew for quite sometime outside my airspace at 41000B43000 feet and many other altitudes to get there. I am unaware if there was ever a loss of RVSM separation; however I feel I should fill this out because I was aware of this. I told my Quality Control local department of this event. I then coordinated appropriately with all adjacent sectors for any new clearances and point outs needed.I believe airlines and companies need to have some type of fail safe system in place to not allow an aircraft who is Negative RVSM capable file as RVSM capable based upon their tail number.

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.