Medium transport aircraft captain reported an altitude deviation occurred while on the BAYYY3 arriva...

Narrative:

We were flying the BAYYY3 arrival into hou. We were cleared to descend via the arrival; but to maintain FL220. We read back the altitude. We were then cleared to now maintain FL230 and we read that altitude clearance back to ATC. Shortly after leveling off we were then cleared to maintain FL200. We the PNF [pilot not flying] read back the new altitude clearance; PF [pilot flying] set the altitude in the selector and proper call outs were made. Passing FL215 the controller asked us where are you going? The PNF replied FL200 as cleared. The controller stated he only cleared us to FL230. (Not correct). We momentarily stopped the descent and shortly thereafter he re-cleared us to continue the descent. The controller said it was 'not an issue and he had taken care of it.' we have tried and tried again to stress the use of full call signs; but ATC continues to use only the last 3 digits. Multiple times we have had to query ATC when multiple call signs are on the same frequency with the exact same last 3 digits in the tail number. My recommendation: quit using former company call signs and use current company call sign with the full tail number.

Original NASA ASRS Text

Title: Medium Transport aircraft Captain reported an altitude deviation occurred while on the BAYYY3 arrival into HOU airport. It was also reported that ATC's use of incomplete call signs may have contributed to the clearance deviation.

Narrative: We were flying the BAYYY3 arrival into HOU. We were cleared to descend VIA the arrival; but to maintain FL220. We read back the altitude. We were then cleared to now maintain FL230 and we read that altitude clearance back to ATC. Shortly after leveling off we were then cleared to maintain FL200. We the PNF [Pilot not Flying] read back the new altitude clearance; PF [Pilot Flying] set the altitude in the selector and proper call outs were made. Passing FL215 the Controller asked us where are you going? The PNF replied FL200 as cleared. The Controller stated he only cleared us to FL230. (Not correct). We momentarily stopped the descent and shortly thereafter he re-cleared us to continue the descent. The Controller said it was 'not an issue and he had taken care of it.' We have tried and tried again to stress the use of full call signs; but ATC continues to use only the last 3 digits. Multiple times we have had to query ATC when multiple call signs are on the same frequency with the exact same last 3 digits in the tail number. My recommendation: quit using former company call signs and use current company call sign with the full tail number.

Data retrieved from NASA's ASRS site 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	1721357
Time
Date	202001
Local Time Of Day	0001-0600
Place
Locale Reference	HOU.Airport
State Reference	TX
Environment
Light	Daylight
Aircraft 1
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Descent
Route In Use	STAR BAYYY3
Flight Plan	IFR
Person 1
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine
Events
Anomaly	ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance

Medium transport aircraft captain reported an altitude deviation occurred while on the BAYYY3 arrival into hou airport. It was also reported that ATC's use of incomplete call signs may have contributed to the clearance deviation.