Traffic separation is lost between departure and arrival air carrier's near clt, nc.

Attributes
ACN	565179
Time
Date	200211
Day	Thu
Local Time Of Day	1201 To 1800
Place
State Reference	NC
Altitude	msl single value : 8500
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : clt.tracon
Operator	common carrier : air carrier
Make Model Name	A319
Operating Under FAR Part	Part 121
Navigation In Use	other other vortac
Route In Use	arrival star : unarm
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : clt.tracon
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : intermediate altitude
Route In Use	departure : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 184 flight time total : 15000 flight time type : 704
ASRS Report	565179
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	conflict : airborne less severe
Independent Detector	aircraft equipment : tcas other controllera
Resolutory Action	controller : separated traffic
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

Clearance was via 'unarm arrival' to clt. ZTL issued clearance to cross adena at 12000 ft, normal speed. At adena, we contacted clt approach and he said to expect runway 18R approach. We were then issued a clearance to 7000 ft. Both the first officer and I heard 7000 ft. I read back 7000 ft and we both verified 7000 ft was set in FMA. Aircraft was slowed to 250 KTS and we descended. At approximately 8500 ft, approach said to stop descent and climb back to 9000 ft. At approximately 8300 ft, a climb back to 9000 ft was initiated. The TCASII issued a traffic alert, but no traffic avoidance commands were issued by TCASII. The reason was a B737 on departure vector was proceeding from right to left at 12 O'clock position at 7000 ft at approximately 3 mi. We told the approach controller we were sure a clearance had been issued to 7000 ft and asked if he wanted a call on the ground, but he said no and we continued with a normal approach and landing. I have no suggestions as to how to avoid this type of problem. I believe we were mistakenly cleared to 7000 ft. However, the system worked as it should have. If the controller had not issued a climb, I am sure the TCASII would have.

Original NASA ASRS Text

Title: TFC SEPARATION IS LOST BTWN DEP AND ARR ACR'S NEAR CLT, NC.

Narrative: CLRNC WAS VIA 'UNARM ARR' TO CLT. ZTL ISSUED CLRNC TO CROSS ADENA AT 12000 FT, NORMAL SPD. AT ADENA, WE CONTACTED CLT APCH AND HE SAID TO EXPECT RWY 18R APCH. WE WERE THEN ISSUED A CLRNC TO 7000 FT. BOTH THE FO AND I HEARD 7000 FT. I READ BACK 7000 FT AND WE BOTH VERIFIED 7000 FT WAS SET IN FMA. ACFT WAS SLOWED TO 250 KTS AND WE DSNDED. AT APPROX 8500 FT, APCH SAID TO STOP DSCNT AND CLB BACK TO 9000 FT. AT APPROX 8300 FT, A CLB BACK TO 9000 FT WAS INITIATED. THE TCASII ISSUED A TFC ALERT, BUT NO TFC AVOIDANCE COMMANDS WERE ISSUED BY TCASII. THE REASON WAS A B737 ON DEP VECTOR WAS PROCEEDING FROM R TO L AT 12 O'CLOCK POS AT 7000 FT AT APPROX 3 MI. WE TOLD THE APCH CTLR WE WERE SURE A CLRNC HAD BEEN ISSUED TO 7000 FT AND ASKED IF HE WANTED A CALL ON THE GND, BUT HE SAID NO AND WE CONTINUED WITH A NORMAL APCH AND LNDG. I HAVE NO SUGGESTIONS AS TO HOW TO AVOID THIS TYPE OF PROB. I BELIEVE WE WERE MISTAKENLY CLRED TO 7000 FT. HOWEVER, THE SYS WORKED AS IT SHOULD HAVE. IF THE CTLR HAD NOT ISSUED A CLB, I AM SURE THE TCASII WOULD HAVE.

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.