ZID PROVIDES RADAR ASSOCIATE TO NEWLY CERTIFIED CTLR WHEN OBSERVING TFC COMPLEXITY BUILD AND THE CTLR WORKING ON THE WRONG RADAR RANGE.

Narrative

THE PROB AROSE WHEN RADAR CTLR TOOK A HDOF ON A CLBING ACFT FROM A SECTOR S OF US (THE REGIONAL JET) AND CLBED A DEP FROM THE E TO THE SAME ALT (THE T38). IT WAS DISCOVERED WHEN THE SUPVR TOLD THE RADAR TO ROLL THE RANGE IN SO HE COULD SEE HIS TFC BECAUSE ALL THE DATA BLOCKS WERE OVERLAPPING. CONTRIBUTING FACTORS: THE RADAR WAS WORKING ON A VERY DANGEROUS RANGE. THE DATA WAS COVERING ALL THE AIRSPACE AND OVERLAPPING EACH OTHER. THE CTLR WAS ONLY CERTIFIED FOR ABOUT 2 WKS AND THIS WAS HIS FIRST RADAR POS. THE SECTOR HAS TO SERVE AN ENRTE AND APCH FUNCTION WHICH I THINK IS TOO MUCH. THE S SECTOR THAT HANDED OFF THE REGIONAL JET DIDN'T COORD THE CLB IT WAS IN. CORRECTIVE ACTIONS: DON'T HAVE ENRTE CTLRS WORKING SECTORS WITH ENRTE AND TERMINAL FUNCTIONS -- SPLIT THEM UP! ENRTE CTLRS ARE NOT VERY SKILLED AT TERMINAL FUNCTIONS IN THIS CASE WHERE ONLY 1 SECTOR OF 6 IS TERMINAL. BY THE TIME YOU HAPPEN UPON THE SECTOR; YOU'RE NOT VERY -PROFICIENT AT IT. THE S SECTOR HANDING OFF THE CLBING REGIONAL JET SHOULD HAVE COORD THE CLB. IT WOULD BE NICE IF; WHEN YOU ROLLED THE RANGE OUT; THE DISPLAY WOULD SHRINK THE DATA BLOCKS APPROPRIATELY. IT WOULD BE NICE IF THE COMPUTER WOULD OFFSET THE DATA BLOCKS ALWAYS! SUPPLEMENTAL INFO FROM ACN 522132: I NOTICED THAT THE SECTOR TFC WAS BUILDING. I ASSIGNED A D-SIDE TO THE SECTOR. WHILE ATTENDING TO OTHER DUTIES; I STILL RETURNED TO THE SECTOR TO WATCH. THE CTLR WAS A NEWLY CERTIFIED R-CTLR. THE CTLR WAS ON 100 NM RANGE -- TOO SMALL FOR THE AMOUNT OF TFC. I QUESTIONED THE RANGE AND CTLR CHANGED IT TO 75 NM RANGE. WHEN THAT WAS DONE; I SAW THE COMMUTER'S ALT CLB THROUGH FL192. THE T38 WAS LEVEL AT FL190 AND TURNED TO VHP ON COURSE. I ASKED IF THE COMMUTER WAS CLBING. THE CTLR THEN SAW TFC. CTLR CLBED THE T38 TO FL230; BUT ADEP HAD ALREADY ACTIVATED. BECAUSE THE CTLR HAD JUST TURNED THE T38 TOWARDS VHP; CONFLICT ALERT NEEDED TIME TO RE-EVALUATE THE SIT. I FEEL THAT THE PRIMARY REASON FOR THE ADEP WAS (OP ERROR) THE RANGE IN USE; BECAUSE THE COMMUTER'S DATA BLOCK WAS OVERLAPPING ANOTHER ONE. ONCE THE RANGE WAS CHANGED; THE CTLR SAW THAT THE COMMUTER WAS CLBING SLOWLY THROUGH FL192 TO FL200.