ZJX controller experienced operational error at FL240 when intrafac coordination procedures were not...

Attributes
ACN	618127
Time
Date	200405
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	navaid : pie.vortac
State Reference	FL
Altitude	msl single value : 24000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zjx.artcc
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zjx.artcc
Operator	other
Make Model Name	Stratotanker 135
Operating Under FAR Part	Part 91
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller time certified in position1 : 10
ASRS Report	618127
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	airspace violation : entry conflict : airborne less severe non adherence : published procedure non adherence : required legal separation
Independent Detector	atc equipment : conflict alert
Resolutory Action	none taken : insufficient time
Consequence	faa : investigated
Miss Distance	horizontal : 23400 vertical : 600
Supplementary
Problem Areas	Airspace Structure ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Operational Error

Narrative:

I was working the ocala sector, responsible for mco departures to the northwest. I climbed a B737 to FL260. Handed aircraft off to high sector (mayo-right-16). I thought I gave a pvd of the B737 to the adjacent low sector (cedar). Data records showed no computer entry from my keyboard. I switched the aircraft to the high sector without verbally coordinating the pvd for the B737. The cedar sector had a northbound KC135 tanker climbing to FL240. Conflict alert activated when the KC135 was level at FL240 and the B737's mode C initiated FL248. Separation was lost prior to conflict alert. Cedar did not see the limited data block due to ground clutter. Cedar sector works surface to FL260. With adjacent facilities at tampa approach and jacksonville approach, it is extremely difficult to see limited data blocks and possible conflicts. If cedar sector was not working down to the ground, I believe that the controller would have caught my mistake.

Original NASA ASRS Text

Title: ZJX CTLR EXPERIENCED OPERROR AT FL240 WHEN INTRAFAC COORD PROCS WERE NOT FOLLOWED.

Narrative: I WAS WORKING THE OCALA SECTOR, RESPONSIBLE FOR MCO DEPS TO THE NW. I CLBED A B737 TO FL260. HANDED ACFT OFF TO HIGH SECTOR (MAYO-R-16). I THOUGHT I GAVE A PVD OF THE B737 TO THE ADJACENT LOW SECTOR (CEDAR). DATA RECORDS SHOWED NO COMPUTER ENTRY FROM MY KEYBOARD. I SWITCHED THE ACFT TO THE HIGH SECTOR WITHOUT VERBALLY COORDINATING THE PVD FOR THE B737. THE CEDAR SECTOR HAD A NBOUND KC135 TANKER CLBING TO FL240. CONFLICT ALERT ACTIVATED WHEN THE KC135 WAS LEVEL AT FL240 AND THE B737'S MODE C INITIATED FL248. SEPARATION WAS LOST PRIOR TO CONFLICT ALERT. CEDAR DID NOT SEE THE LIMITED DATA BLOCK DUE TO GND CLUTTER. CEDAR SECTOR WORKS SURFACE TO FL260. WITH ADJACENT FACILITIES AT TAMPA APCH AND JACKSONVILLE APCH, IT IS EXTREMELY DIFFICULT TO SEE LIMITED DATA BLOCKS AND POSSIBLE CONFLICTS. IF CEDAR SECTOR WAS NOT WORKING DOWN TO THE GND, I BELIEVE THAT THE CTLR WOULD HAVE CAUGHT MY MISTAKE.

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.

ZJX controller experienced operational error at FL240 when intrafac coordination procedures were not followed.