Date: 201504
Local time of day: 1201-1800
Location: ZJX.ARTCC, FL
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Flight phase: Cruise
Airspace: Class E ZJX
ATC / advisory: Center ZJX
Reporter organization: Government
Reporter function: Handoff / Assist; Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Confusion; Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: I was working sector 10 combined with sector 09 as the D-side.  The sector had been busy all morning with activity in the Pensacola North MOA and associated alert area below it.  Aircraft X was a VFR aircraft we were giving flight following to.  There were a lot of targets ahead for Aircraft X so the R side told the pilot that there are many targets ahead; 'too many to call'.  In a way the controller was right; there were a lot of targets ahead and it was difficult to see their altitudes; but he had no heartburn whatsoever to try to help keep that aircraft safe and avoid a collision.  He didn't offer a vector around that area; he didn't try to temporarily zoom in on the scope to get a closer look to see some of the target's altitudes; he basically didn't care.  As the aircraft continued; a few minutes later there was now a conflict alert on the scope between Aircraft X and one of the aircraft in the beehive of assuredly navy trainers that were in that area.  Because there was a conflict alert I could now see the altitude on the data tag the other VFR Navy trainer and it was I recall about 300 feet above Aircraft X and turning right behind within about 1/2 to 1 sm behind Aircraft X.  I brought the situation to the R sides attention and he basically shrugged it of; didn't care and didn't bother to call the traffic to Aircraft X.  This was a senior controller.  I think this is wrong.  Adding to the situation was the fact that staffing was lower today and we had sun-n-fun aircraft flying through our area.  We had been put on 35 minute breaks because of staffing.  The North MOA sector should have been split off so proper service can be given to the North MOA sector so VFR aircraft who are flying through our sector or IFR for that matter can be given proper service in calling traffic in that alert area.I will now submit another report with the same thing that happened a few minutes later with a different aircraftI know that this report is not a disciplinary venue and that's not my intent; but you can give all the briefings about safety you want and for the need to help avoid a collision with VFR aircraft on flight following; but until there is tangible consequence for controllers with hazardous attitudes; and management has the ability to make this type of behavior stop; these types of situations will continue.




Synopsis: A Jacksonville Center (ZJX) Controller; while working the D Side of a sector; reports that the R side controller didn't call traffic or offer a vector to an aircraft to clear a known area of high volume fast moving aircraft. The R side controller shrugged off the controller's desire to issue traffic or vector the traffic they were giving flight following to.