ZAB controller describes a situation where the aircraft suffix is different then what it actually is...

Narrative:

The pilot of aircraft X entered my airspace at FL270. The pilot requested FL350 and direct lbl just south of cme. He stated that the aircraft was equipped to fly in non-rvsm airspace. I climbed the aircraft. The pilot and I had a somewhat long discussion as to whether or not he could legally enter rvsm airspace. After questioning him; I got the unfortunate impression that it was legal for him to enter that airspace. It turns out that he could enter the airspace because he was a 'test flight' but he obviously needed the required 2000 feet separation and proper coordination; neither of which I conducted. Aircraft X didn't violate anyone in my airspace; but I'm sure he did later on during the en-route phase of his flight. Aircraft X was also filed as a /left but he was really a /G hence; no coral box.pilots need to file proper flight plans; especially concerning their equipment suffixes. Also; I as the radar controller could have used better communication with the pilot as far as non-rvsm airspace is concerned.

Original NASA ASRS Text

Title: ZAB Controller describes a situation where the aircraft suffix is different then what it actually is. This error may have led to a loss of separation throughout the flight of the aircraft. The aircraft suffix was actually a G but filed as a L; which allowed the aircraft to be in RVSM airspace.

Narrative: The pilot of Aircraft X entered my airspace at FL270. The Pilot requested FL350 and direct LBL just south of CME. He stated that the aircraft was equipped to fly in Non-RVSM airspace. I climbed the aircraft. The pilot and I had a somewhat long discussion as to whether or not he could legally enter RVSM airspace. After questioning him; I got the unfortunate impression that it was legal for him to enter that airspace. It turns out that he could enter the airspace because he was a 'test flight' but he obviously needed the required 2000 feet separation and proper coordination; neither of which I conducted. Aircraft X didn't violate anyone in my airspace; but I'm sure he did later on during the en-route phase of his flight. Aircraft X was also filed as a /L but he was really a /G hence; no coral box.Pilots need to file proper flight plans; especially concerning their equipment suffixes. Also; I as the radar controller could have used better communication with the pilot as far as NON-RVSM airspace is concerned.

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	1203332
Time
Date	201409
Local Time Of Day	1801-2400
Place
Locale Reference	ZAB.ARTCC
State Reference	NM
Environment
Light	Night
Aircraft 1
Make Model Name	Medium Large Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Climb
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (mon) 6
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

ZAB controller describes a situation where the aircraft suffix is different then what it actually is. This error may have led to a loss of separation throughout the flight of the aircraft. The aircraft suffix was actually a G but filed as a left; which allowed the aircraft to be in rvsm airspace.