Date: 201406
Local time of day: 1801-2400
Location: ZAB.ARTCC, NM
Light: Daylight
Aircraft: Military
Operator: Military
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class A ZAB
ATC / advisory: Center ZAB
Second aircraft: Military
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Contributing factors: Aircraft; Procedure
Primary problem: Procedure

Narrative: I was initially giving OJT to a Developmental on Sector 15 whose airspace is ground to FL280. Sector 87 called to APREQ Aircraft X flight; which was an ALRV from TCC to IRW scheduled at FL250B270; with a revised altitude of FL250B290. The Developmental approved it after clarifying with Sector 87 that they would accomplish a point out to Sector 97 which owns FL290 and up directly over Sector 15. Within a few minutes of that approval OJT was discontinued and I stayed on sector as CPC. Soon after Aircraft X flight entered Sector 15's airspace ZFW called with a point out near SYO of Aircraft Y climbing to FL300. Aircraft Y's route was SYO..PNH..TCC. directly head on with the Aircraft X flight. Aircraft Y would easily be level near PNH when crossing out with the Aircraft X flight. I did not think there was any problem with these two flights since they were both RVSM and no coral box showed on the data block. I thought in the back of my mind that if one of the flights was negative RVSM it would be a problem; but I felt confident that all aircraft were RVSM qualified based on my cursory glance at their flight plans. I had seen the ALTRV sheet earlier in the day for the Aircraft X flight; and noted that the two fighter's were in tow. I failed to note all aircraft equipment suffixes at that time; and did not think to look at them again. As Aircraft X flight and Aircraft Y passed each other east of PNH; the Sector 97 Controller called me to quick look them and issue traffic on the two flights. I issued traffic to the Aircraft X flight and they acknowledged they were looking. No data blocks flashed and neither pilot said anything unusual. One thing that would have been very helpful would be having the lead aircraft say 'negative RVSM' if the whole flight is negative RVSM. 99% of all aircraft I have talked to that were negative RVSM specified; on contact with a new sector; that they are negative RVSM. Another item would be in the ALTRV sheets that are given out to specify and spell out in plain language somewhere that the flight is negative RVSM. Last; I would ask for clarification to avoid any doubts whatsoever that: 1) Any aircraft in a block altitude flight that is negative RVSM makes the whole flight negative RVSM.2) Negative RVSM separation needs to be accomplished even if the flight is in a two or three thousand foot block (e.g. FL310B330).




Synopsis: ZAB Controller describes situation where aircraft are not RVSM equipped and has a loss of separation due to one on the aircraft being a flight with non-RVSM aircraft in tow.