Controller uses wrong call sign causing confusion to flight crew.

Attributes
ACN	152738
Time
Date	199008
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : mia
State Reference	FL
Altitude	msl bound lower : 22000 msl bound upper : 23000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zma
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	152738
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

Air carrier 2803 was cleared to FL230 and acknowledged. We climbed out of FL220 when the controller was frantically attempting to call air carrier 2083. After a couple of calls to air carrier 2083 I asked if they were really talking to air carrier 2803. She replied yes that air carrier 2083 was cleared to FL210 and she showed us going through FL220. We requested a couple of time if air carrier 2803 was cleared to FL230. A male voice answered 'yes'. The whole situation left a lot to be desired for the following reasons. Correct call signs must be used. Even after we determined incorrect call signs were being used it continued. The supervisor should have been more forceful to correct the misunderstanding. I was very concerned that we may have busted an altitude. We were also given an intercept heading for the transition to the goofy 1 arrival to mco. When we asked the next controller whether he wanted the palm beach or the pahokee transition, he said that he 'didn't care'. I guess that the crews are still required to care?

Original NASA ASRS Text

Title: CTLR USES WRONG CALL SIGN CAUSING CONFUSION TO FLT CREW.

Narrative: ACR 2803 WAS CLRED TO FL230 AND ACKNOWLEDGED. WE CLBED OUT OF FL220 WHEN THE CTLR WAS FRANTICALLY ATTEMPTING TO CALL ACR 2083. AFTER A COUPLE OF CALLS TO ACR 2083 I ASKED IF THEY WERE REALLY TALKING TO ACR 2803. SHE REPLIED YES THAT ACR 2083 WAS CLRED TO FL210 AND SHE SHOWED US GOING THROUGH FL220. WE REQUESTED A COUPLE OF TIME IF ACR 2803 WAS CLRED TO FL230. A MALE VOICE ANSWERED 'YES'. THE WHOLE SITUATION LEFT A LOT TO BE DESIRED FOR THE FOLLOWING REASONS. CORRECT CALL SIGNS MUST BE USED. EVEN AFTER WE DETERMINED INCORRECT CALL SIGNS WERE BEING USED IT CONTINUED. THE SUPVR SHOULD HAVE BEEN MORE FORCEFUL TO CORRECT THE MISUNDERSTANDING. I WAS VERY CONCERNED THAT WE MAY HAVE BUSTED AN ALT. WE WERE ALSO GIVEN AN INTERCEPT HDG FOR THE TRANSITION TO THE GOOFY 1 ARR TO MCO. WHEN WE ASKED THE NEXT CTLR WHETHER HE WANTED THE PALM BEACH OR THE PAHOKEE TRANSITION, HE SAID THAT HE 'DIDN'T CARE'. I GUESS THAT THE CREWS ARE STILL REQUIRED TO CARE?

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.