ZHU controllers experience operational error with oceanic non radar traffic at FL330.

Attributes
ACN	625067
Time
Date	200407
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : zhu.artcc
State Reference	TX
Altitude	msl single value : 33000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zhu.artcc
Operator	common carrier : air carrier
Make Model Name	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Route In Use	enroute airway : a321.airway
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zhu.artcc
Operator	common carrier : air carrier
Make Model Name	MD-83
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Route In Use	enroute airway : a509.airway
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar other personnel other
Qualification	controller : radar
Experience	controller limited radar : 19 controller military : 4 controller non radar : 15 controller radar : 19
ASRS Report	625067
Person 2
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller radar : 19.5 controller time certified in position1 : 2
ASRS Report	625247
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation
Independent Detector	other controllera other controllerb
Resolutory Action	controller : issued new clearance
Consequence	faa : investigated
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

This is my 6TH consecutive work day. It is an XB00-XJ00 jaunt. I arrived at XA45, and I was tired. At around XS00, I was trying to relieve the ocean controller who was 'one-manning' the sector. He was busy, so I plugged in the d-side and started helping him. I coordinated a flight plan on aircraft X with merida center, an A321 at FL330. Aircraft X and aircraft Y on A509, FL370, were already in the board. Apparently the previous controller had already traffic searched and not caught the confliction at eliom. They originally showed 10 mins at eliom. This intersection requires 15 mins separation crossing. After time updates on both aircraft, the time dropped to 6 mins at eliom. The controller I had intended to relieve was then relieved by another controller. During this time I assumed the d-side and was fairly busy for several mins. I did not catch the conflict. The new 'right' main caught the conflict. When aircraft Y checked on, he then descended aircraft X to FL290 and I recoordinated with merida center. Both aircraft were non radar. I estimate there were 5-7 mins between aircraft when vertical separation was established via a report out of FL310 by aircraft X.

Original NASA ASRS Text

Title: ZHU CTLRS EXPERIENCE OPERROR WITH OCEANIC NON RADAR TFC AT FL330.

Narrative: THIS IS MY 6TH CONSECUTIVE WORK DAY. IT IS AN XB00-XJ00 JAUNT. I ARRIVED AT XA45, AND I WAS TIRED. AT AROUND XS00, I WAS TRYING TO RELIEVE THE OCEAN CTLR WHO WAS 'ONE-MANNING' THE SECTOR. HE WAS BUSY, SO I PLUGGED IN THE D-SIDE AND STARTED HELPING HIM. I COORDINATED A FLT PLAN ON ACFT X WITH MERIDA CTR, AN A321 AT FL330. ACFT X AND ACFT Y ON A509, FL370, WERE ALREADY IN THE BOARD. APPARENTLY THE PREVIOUS CTLR HAD ALREADY TFC SEARCHED AND NOT CAUGHT THE CONFLICTION AT ELIOM. THEY ORIGINALLY SHOWED 10 MINS AT ELIOM. THIS INTXN REQUIRES 15 MINS SEPARATION XING. AFTER TIME UPDATES ON BOTH ACFT, THE TIME DROPPED TO 6 MINS AT ELIOM. THE CTLR I HAD INTENDED TO RELIEVE WAS THEN RELIEVED BY ANOTHER CTLR. DURING THIS TIME I ASSUMED THE D-SIDE AND WAS FAIRLY BUSY FOR SEVERAL MINS. I DID NOT CATCH THE CONFLICT. THE NEW 'R' MAIN CAUGHT THE CONFLICT. WHEN ACFT Y CHKED ON, HE THEN DSNDED ACFT X TO FL290 AND I RECOORDINATED WITH MERIDA CTR. BOTH ACFT WERE NON RADAR. I ESTIMATE THERE WERE 5-7 MINS BTWN ACFT WHEN VERT SEPARATION WAS ESTABLISHED VIA A RPT OUT OF FL310 BY ACFT X.

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.