ZID controller described a conflict alert event when traffic transferred to an adjacent facility was...

Narrative:

I was working R84 (altitudes: FL240-330) when I handed aircraft X off to ZME (sector M63) going westbound on J6 and I then switched the aircraft to memphis centers frequency. Moments later aircraft X began to climb and flash (conflict alert) with an aircraft who was being worked by the sector above me (attitudes: FL340 and above.) memphis never coordinated with me to climb the aircraft although they did point the aircraft out the sector above me 'climbing.' memphis center sectors are configured a bit different than ours in that the same sector (sector M63) owns up FL240-FL340 so it appears as though they just forgot that at ZID rebel sector actually owns FL330 and therefore forget to get control to climb the aircraft from that sector. Recommendation; memphis center sectors are configured a bit different than ours in that the same sector (sector M63) owns up FL240-FL340 so it appears as though they just forgot that at ZID rebel sector actually owns FL330 and therefore forget to get control to climb the aircraft from that sector. Therefore; the only thing that may help would be for all sectors to own the same altitudes to make it consistent; but I don't think that's possible given certain traffic flows.

Original NASA ASRS Text

Title: ZID Controller described a conflict alert event when traffic transferred to an adjacent facility was issued a climb without coordination with the proper sector with regard to altitude ownership.

Narrative: I was working R84 (altitudes: FL240-330) when I handed Aircraft X off to ZME (Sector M63) going Westbound on J6 and I then switched the aircraft to Memphis Centers frequency. Moments later Aircraft X began to climb and flash (conflict alert) with an aircraft who was being worked by the sector above me (attitudes: FL340 and above.) Memphis never coordinated with me to climb the aircraft although they did point the aircraft out the sector above me 'climbing.' Memphis Center sectors are configured a bit different than ours in that the same sector (Sector M63) owns up FL240-FL340 so it appears as though they just forgot that at ZID Rebel Sector actually owns FL330 and therefore forget to get control to climb the aircraft from that sector. Recommendation; Memphis Center sectors are configured a bit different than ours in that the same sector (Sector M63) owns up FL240-FL340 so it appears as though they just forgot that at ZID Rebel Sector actually owns FL330 and therefore forget to get control to climb the aircraft from that sector. Therefore; the only thing that may help would be for all sectors to own the same altitudes to make it consistent; but I don't think that's possible given certain traffic flows.

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

Attributes
ACN	871537
Time
Date	201002
Local Time Of Day	1201-1800
Place
Locale Reference	ZID.ARTCC
State Reference	IN
Aircraft 1
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	None
Flight Plan	IFR
Person 1
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

ZID controller described a conflict alert event when traffic transferred to an adjacent facility was issued a climb without coordination with the proper sector with regard to altitude ownership.