Narrative:

I was D side training on sector 25 with an right side who is lazy and incompetent (example: he doesn't believe in efcs (expect further clearance). I wasn't aware their use was optional; but to him it is). He did a traffic call; didn't use 'heavy' or 'caution wake turbulence' despite me telling the D side that it should be done that way. The controller rolled his eyes and said they were fine. About 90 seconds after crossing 1;000 feet below a heavy on directly opposite courses; aircraft X reported he got wake and asked if that was a super. The right side seemed confused and said the rides were reported smooth. I tried to explain to the right side what the pilot was asking but he said 'it's all good'. I didn't report it to management as they were not in the control room but instead hanging out elsewhere (I think chatting with the operations manager).there was another wake event; where I was again D side training on R20. The right side trainee called traffic and did not say heavy or caution wake turbulence as an aircraft passed opposite direction; 1;000 feet below a heavy. I told the right side trainee to give him a wake turbulence advisory and he said he hadn't been taught to do that. While he protested; the pilot came back and said he 'got bounced around pretty good from the wake of whatever that was'. Then the right trainee panicked a little. The supervisor was notified but said he didn't care because nothing happened.cover wake events in training for new hires. Cover wake events in refresher training. Tell the supervisors to man the desk or leave a controller in charge (controller in charge). Tell the supervisors we care about these so we can track the occurrences accurately. Hold the cpcs (certified professional controller) to a minimum standard; or fire them. As a matter of interest; this cpc right side had just been talked to regarding his phraseology and had an airspace violation; both in the previous week.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZMP Center Controller reported that another Controller does not follow procedures; is lazy; and incompetent.

Narrative: I was D side training on sector 25 with an R side who is lazy and incompetent (example: he doesn't believe in EFCs (Expect Further Clearance). I wasn't aware their use was optional; but to him it is). He did a traffic call; didn't use 'heavy' or 'caution wake turbulence' despite me telling the D side that it should be done that way. The controller rolled his eyes and said they were fine. About 90 seconds after crossing 1;000 feet below a Heavy on directly opposite courses; Aircraft X reported he got wake and asked if that was a Super. The R side seemed confused and said the rides were reported smooth. I tried to explain to the R side what the pilot was asking but he said 'it's all good'. I didn't report it to management as they were not in the control room but instead hanging out elsewhere (I think chatting with the Operations Manager).There was another wake event; where I was again D side training on R20. The R side trainee called traffic and did not say heavy or caution wake turbulence as an aircraft passed opposite direction; 1;000 feet below a heavy. I told the R side trainee to give him a wake turbulence advisory and he said he hadn't been taught to do that. While he protested; the pilot came back and said he 'got bounced around pretty good from the wake of whatever that was'. Then the R trainee panicked a little. The supervisor was notified but said he didn't care because nothing happened.Cover wake events in training for new hires. Cover wake events in refresher training. Tell the Supervisors to man the desk or leave a CIC (Controller In Charge). Tell the Supervisors we care about these so we can track the occurrences accurately. Hold the CPCs (Certified Professional Controller) to a minimum standard; or fire them. As a matter of interest; this CPC R side had just been talked to regarding his phraseology and had an airspace violation; both in the previous week.

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.