Air Traffic Control Developmental
Communication Breakdown; Situational Awareness; Confusion
ATC Issue All Types; Conflict NMAC
Human Factors; Aircraft
While working approach for the satellite airports; Aircraft X had been released IFR with the previous controller. Several flights of fighters were inbound for their recoveries back to HIF. I misjudged the climb rate characteristics for Aircraft X and had anticipated them to climb at a faster rate than they did. They were assigned a vector to join the airway; climbing. Traffic was issued to Aircraft Y; 4/fighters several times and also to Aircraft X. The conflict alert did not go off. When the fighters were 4NM west; I answered another flight checking in instead of issuing a traffic alert. I felt the projected flight path of the fighters was behind that of Aircraft X. However; after reviewing the tape I recognized that I did not see the wingman's primary target pass directly below Aircraft X. At the crossing point; Aircraft X was at 8100 feet and Aircraft Y flight indicated 7600 feet. I do not know what altitude the wingman who passed below Aircraft X was. The pilot of that aircraft called to report a NMAC. Consider aircraft characteristics more appropriately. Maintain a more diligent scan.
S56 controller reports of a NMAC caused by an un-anticipated climb rate of one aircraft and the possible altitude deviation of a flight of four aircraft.