ATC computer entry to avoid error detection program.

Attributes
ACN	275741
Time
Date	199406
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : sji
State Reference	AL
Altitude	msl bound lower : 29000 msl bound upper : 29000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zhu
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	climbout : intermediate altitude
Route In Use	enroute : on vectors
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	climbout : intermediate altitude
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 6
ASRS Report	275741
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : published procedure other anomaly other other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

I was working the mobile sector at ZHU center. I was descending an aircraft X and climbing another aircraft Y that had crossing paths. I observed the rates of climb and descent would not be sufficient for separation. I turned each aircraft 20 degrees away from the other aircraft. I did not feel comfortable with this action, so I issued 1 aircraft to fly heading 345. This aircraft did not respond. I issued the 345 heading again. The aircraft accepted the clearance. I issued the other aircraft a heading of 180 degrees. The aircraft did not respond. I issued the 180 heading again. This time the aircraft accepted. Realizing mode C lags, I considered asking an aircraft to report reaching FL310 and set up the computer entry so that I could enter the report upon reception. However, I accidently entered the report prematurely. Realizing this mistake, I tried to make a 'track' computer entry to restore the altitude mode C of the aircraft I reported at FL310. This action appeared to fail. The aircraft 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 aircraft and the other aircraft target never entered or touched this 'J' ring. My concern is that the sequence of events concerning this situation could appear as if I was initially attempting to cover up a potential system error. This appearance could lead to disciplinary action even though an error did not occur.

Original NASA ASRS Text

Title: 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.

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.