Narrative:

Air carrier X san departure as per letter of agreement was assigned heading 020 from sector 9 with sector 40 control for turns. Procedure and practice is sector 40 pointout to sector 31 for climb. Sector 31 referenced pointout with air carrier X arrival to lax from mexican airspace via JLI2 arrival descending to FL240. I recoordinated asking for at least FL240 to put air carrier X into high altitude structure. Sector 31 controller countered with FL250 approved and higher reference air carrier Y went clear. Air carrier X checked on frequency data block on air carrier Y still reflected descend to FL240, so in turn I waited until data block of air carrier Y was updated to show what had been coordinated. Once asa's data block showed FL260, I then climbed arrival X to FL250. Conflict alert flashed, all data blocks reflected what was coordinated. A loss of mode C occurred, when data block mode C returned air carrier X showed FL250 air carrier Y showed FL247 descending, targets had passed and was 3 mi. I was informed first that it was a pilot deviation, then later that the R31 controller had marked strips showing FL260 entered into data block FL260 but had failed to issue altitude to air carrier Y. Additionally oep never activated nor was there a TCASII alert either. Initially was reported as an operational error, but after xchking with dark this error never occurred and was being reclassified with right.O. I disagree, there was an error. Sector 31 controller needed to issue altitude restriction to air carrier Y. 80 percent of aircraft that depart san on this departure should be handed off to sector 31 to eliminate the pointout. Why did oep never go off? So far as oep program is concerned it is in serious need of being reevaluated. Many times it will not activate, also with the changing of leader lines you can prevent oep from activating. This practice I have seen over and over again with supervision standing behind and observing this cover up.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR X HAD LTSS FROM ACR Y. SYS ERROR.

Narrative: ACR X SAN DEP AS PER LETTER OF AGREEMENT WAS ASSIGNED HDG 020 FROM SECTOR 9 WITH SECTOR 40 CTL FOR TURNS. PROC AND PRACTICE IS SECTOR 40 POINTOUT TO SECTOR 31 FOR CLB. SECTOR 31 REFED POINTOUT WITH ACR X ARR TO LAX FROM MEXICAN AIRSPACE VIA JLI2 ARR DSNDING TO FL240. I RECOORDINATED ASKING FOR AT LEAST FL240 TO PUT ACR X INTO HIGH ALT STRUCTURE. SECTOR 31 CTLR COUNTERED WITH FL250 APPROVED AND HIGHER REF ACR Y WENT CLR. ACR X CHKED ON FREQ DATA BLOCK ON ACR Y STILL REFLECTED DSND TO FL240, SO IN TURN I WAITED UNTIL DATA BLOCK OF ACR Y WAS UPDATED TO SHOW WHAT HAD BEEN COORDINATED. ONCE ASA'S DATA BLOCK SHOWED FL260, I THEN CLBED ARR X TO FL250. CONFLICT ALERT FLASHED, ALL DATA BLOCKS REFLECTED WHAT WAS COORDINATED. A LOSS OF MODE C OCCURRED, WHEN DATA BLOCK MODE C RETURNED ACR X SHOWED FL250 ACR Y SHOWED FL247 DSNDING, TARGETS HAD PASSED AND WAS 3 MI. I WAS INFORMED FIRST THAT IT WAS A PLTDEV, THEN LATER THAT THE R31 CTLR HAD MARKED STRIPS SHOWING FL260 ENTERED INTO DATA BLOCK FL260 BUT HAD FAILED TO ISSUE ALT TO ACR Y. ADDITIONALLY OEP NEVER ACTIVATED NOR WAS THERE A TCASII ALERT EITHER. INITIALLY WAS RPTED AS AN OPERROR, BUT AFTER XCHKING WITH DARK THIS ERROR NEVER OCCURRED AND WAS BEING RECLASSIFIED WITH R.O. I DISAGREE, THERE WAS AN ERROR. SECTOR 31 CTLR NEEDED TO ISSUE ALT RESTRICTION TO ACR Y. 80 PERCENT OF ACFT THAT DEPART SAN ON THIS DEP SHOULD BE HANDED OFF TO SECTOR 31 TO ELIMINATE THE POINTOUT. WHY DID OEP NEVER GO OFF? SO FAR AS OEP PROGRAM IS CONCERNED IT IS IN SERIOUS NEED OF BEING REEVALUATED. MANY TIMES IT WILL NOT ACTIVATE, ALSO WITH THE CHANGING OF LEADER LINES YOU CAN PREVENT OEP FROM ACTIVATING. THIS PRACTICE I HAVE SEEN OVER AND OVER AGAIN WITH SUPERVISION STANDING BEHIND AND OBSERVING THIS COVER UP.

Data retrieved from NASA's ASRS site as of July 2007 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.