An aircraft checked on to the controller's frequency and advised they were non-rvsm qualified. The a...

Attributes
ACN	1325982
Time
Date	201601
Local Time Of Day	1801-2400
Place
Locale Reference	ZLA.ARTCC
State Reference	CA
Aircraft 1
Make Model Name	Citationjet (C525/C526) - CJ I / II / III / IV
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	Direct
Flight Plan	IFR
Aircraft 2
Make Model Name	Regional Jet 700 ER/LR (CRJ700)
Operating Under FAR Part	Part 121
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) 1.0
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

Narrative:

Aircraft X checked on frequency out of climbing to 29;000 feet and stated that he was non-rvsm. There was nothing indicated in his flight plan that showed that aircraft X was non-rvsm. There was also no coral colored box around the aircraft altitude. Aircraft Y was in level flight at 30;000 feet on a course that I thought would clear aircraft X. I was still processing the fact that the non-rvsm information from the plane and my display were at odds; so I failed to stop aircraft X at 28;000 feet. When I realized that the proximity was going to be too close; I turned aircraft Y 20 degrees left. During this time my assist changed the equipment qualifier on aircraft X to show he was non-rvsm and conflict alert activated. After separation was reestablished; aircraft Y was cleared back on course. The pilot of aircraft X stated that he had filed the same flight equipment numerous times and it kept showing that he was rvsm qualified when he wasn't.when a flight plan is filed it should give feedback to the pilot to show whether the altitude request is showing rvsm or non-rvsm based on the equipment that is input.

Original NASA ASRS Text

Title: An aircraft checked on to the Controller's frequency and advised they were Non-RVSM qualified. The aircraft flight plan suffix or radar data tag did not indicate they were Non-RVSM. The controller only used 1;000 feet vertical separation between this aircraft and another one.

Narrative: Aircraft X checked on frequency out of climbing to 29;000 feet and stated that he was Non-RVSM. There was nothing indicated in his flight plan that showed that Aircraft X was Non-RVSM. There was also no coral colored box around the aircraft altitude. Aircraft Y was in level flight at 30;000 feet on a course that I thought would clear Aircraft X. I was still processing the fact that the Non-RVSM information from the plane and my display were at odds; so I failed to stop Aircraft X at 28;000 feet. When I realized that the proximity was going to be too close; I turned Aircraft Y 20 degrees left. During this time my Assist changed the equipment qualifier on Aircraft X to show he was Non-RVSM and conflict alert activated. After separation was reestablished; Aircraft Y was cleared back on course. The pilot of Aircraft X stated that he had filed the same flight equipment numerous times and it kept showing that he was RVSM qualified when he wasn't.When a flight plan is filed it should give feedback to the pilot to show whether the altitude request is showing RVSM or NON-RVSM based on the equipment that is input.

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.

An aircraft checked on to the controller's frequency and advised they were non-rvsm qualified. The aircraft flight plan suffix or radar data tag did not indicate they were non-rvsm. The controller only used 1;000 feet vertical separation between this aircraft and another one.