ATC COMPUTER ENTRY TO AVOID ERROR DETECTION PROGRAM.

Date: 1994-06 · Aircraft: Commercial Fixed Wing · Phase: climb

Anomalies: deviation-discrepancy-procedural-published-material-policy|other-no-specific-anomaly-occurred|other-unspecified

Synopsis

ATC COMPUTER ENTRY TO AVOID ERROR DETECTION PROGRAM.

Narrative

I WAS WORKING THE MOBILE SECTOR AT ZHU CTR. I WAS DSNDING AN ACFT X AND CLBING ANOTHER ACFT Y THAT HAD XING PATHS. I OBSERVED THE RATES OF CLB AND DSCNT WOULD NOT BE SUFFICIENT FOR SEPARATION. I TURNED EACH ACFT 20 DEGS AWAY FROM THE OTHER ACFT. I DID NOT FEEL COMFORTABLE WITH THIS ACTION; SO I ISSUED 1 ACFT TO FLY HDG 345. THIS ACFT DID NOT RESPOND. I ISSUED THE 345 HDG AGAIN. THE ACFT ACCEPTED THE CLRNC. I ISSUED THE OTHER ACFT A HDG OF 180 DEGS. THE ACFT DID NOT RESPOND. I ISSUED THE 180 HDG AGAIN. THIS TIME THE ACFT ACCEPTED. REALIZING MODE C LAGS; I CONSIDERED ASKING AN ACFT TO RPT REACHING FL310 AND SET UP THE COMPUTER ENTRY SO THAT I COULD ENTER THE RPT UPON RECEPTION. HOWEVER; I ACCIDENTLY ENTERED THE RPT PREMATURELY. REALIZING THIS MISTAKE; I TRIED TO MAKE A 'TRACK' COMPUTER ENTRY TO RESTORE THE ALT MODE C OF THE ACFT I RPTED AT FL310. THIS ACTION APPEARED TO FAIL. THE ACFT INVOLVED NEVER LOST LATERAL SEPARATION. THE TARGETS INVOLVED NEVER GOT CLOSER THAN 6 MI. I KNOW THIS BECAUSE I HAD A 6 MI 'J' RING AROUND ONE OF THE ACFT AND THE OTHER ACFT TARGET NEVER ENTERED OR TOUCHED THIS 'J' RING. MY CONCERN IS THAT THE SEQUENCE OF EVENTS CONCERNING THIS SIT COULD APPEAR AS IF I WAS INITIALLY ATTEMPTING TO COVER UP A POTENTIAL SYS ERROR. THIS APPEARANCE COULD LEAD TO DISCIPLINARY ACTION EVEN THOUGH AN ERROR DID NOT OCCUR.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.