ARTCC CTLR SECOND GUESSES CTL ACTIONS TOO LATE AND ALLOWS DSNDING SF340 TO CONFLICT WITH ENRTE B737. CTLR QUESTIONS CONFLICT ALERT FUNCTION AND CHALLENGES FACILITY QUALITY ASSURANCE PERSONNEL ABOUT RADAR SYS; CONFLICT ALERT; RELIABILITY.

Narrative

ON MAY/XA/98 I HAD AN OPERROR. THE CONFLICT ALERT DID NOT ACTIVATE UNTIL SEPARATION WAS ACTUALLY LOST. BOTH DATA BLOCKS WERE IN FLAT TRACK AND THE ALT INFO WAS ENTERED CORRECTLY ON BOTH. OUR CONFLICT ALERT IS SO OVERLY SENSITIVE THAT IT ROUTINELY GOES OFF WITH A DEP AND AN OVERFLT THAT ARE SEPARATED BY 30000 FT OR MORE. WHEN THE CONFLICT ALERT DID NOT ACTIVATE IT CREATED A FALSE SENSE OF SECURITY. I HESITATED AND THOUGHT; WELL; THE COMPUTER THINKS IT WILL WORK; THEN RE-EVALUATED AND TOOK CORRECTIVE ACTION TO SOLVE THE ERROR. OUR QUALITY ASSURANCE OFFICE INSISTED THAT ACCORDING TO THEIR DATA; CONFLICT ALERT ACTIVATED SECONDS PRIOR TO MY REACTION TO CORRECT IT. ANOTHER CTLR WITNESSED THIS ERROR AND AGREES AND SUPPORTS MY STATEMENT THAT CONFLICT ALERT DID NOT ACTIVATE UNTIL IT WAS LESS THAN 5 MI. WE CAN'T TRUST AND USE CONFLICT ALERT IF IT IS THIS UNRELIABLE. WE TEND TO OVERLOOK IT SOMETIMES SINCE IT GOES OFF SO OFTEN UNNECESSARILY AND YET FAILS US AS A BACKUP TOOL WHEN WE MAKE AN ERROR AND NEED IT.