Narrative:

Controller 1 gave us direct [to a fix]; then he gave us pilots discretion to FL240. We then started our descent. When we reached FL240 we were then cleared again pilot's discretion to FL190. We were never given a descend via clearance - we were only given direct. We were then switched to another controller. This controller then cleared us to descend via [the] arrival into ZZZ. I set the lowest altitude 5;000 feet for transition. Before I moved my finger I verified that the pilot flying (PF) put it in managed descent and managed speed of which he did. Aircraft started to slow and we were on profile. Shortly thereafter the controller was very curt in his question of our speed of which I professionally replied 278 knots. His agitated response was you should've been at 270 knots. This controller took it further by now telling us to call when we land. We were surprised by this tone; that we actually needed to have him repeat it. If there were separation issues; I don't think giving us a phone number twice fixes the separation issue - (of which we were not aware of any other aircraft - he did not point any traffic out). We are on a descent into mountainous terrain at night and becoming confused by ATC's handling of our flight. After that he told us to fly an off course heading. I heard turn 30 degrees left; the captain initiated a 30 degree right turn to what he thought was to be a 030 heading. When I saw him turn right I responded turning 30 degrees right thinking I misunderstood him of which the controller did not correct us. The next transmission came from the controller and he said I thought I told you to turn to the left. The controller told us stay on your course to the right to I believe a 030 heading. I queried the captain and said that's where the high terrain is; we need to go back left. When I was about to ask ATC to go left he cleared us direct [to a fix] descend and maintain 7;000. There was a chain of events that started because we never were initially cleared to descend via the arrival until inside the arrival. The manner in which this was handled; in my opinion raised safety issues by creating communication barriers and confusion. We landed without incident and then called the phone number at the gate. The captain called and spoke with the ATC supervisor. I did not hear the conversation the captain had but I was told a synopsis from the captain. He gave me a thumbs up that it's no problem and not to worry. Apparently this controller had a very heated discussion regarding this arrival with the chief pilot over this exact thing regarding speed on the arrival. In my opinion; from what I was briefed by the captain; it almost seems we were almost setup to fall into what I believe was a 'trap'; so as to possibly validate his discussion with the chief pilot; just my opinion.

Google
 

Original NASA ASRS Text

Title: An A320 flight crew received a 'Descend Via' clearance and were in Managed Descent and Managed Speed. ATC queried the crew about their speed and they replied '278 knots'; they were slowing to the required 270 knots as required by the profile. The Controller gave them a number to call upon landing. The Captain called and spoke to a supervisor who relayed that the controller on duty had recently had a heated discussion with the Chief Pilot about his dissatisfaction with pilot's arrival and communications errors.

Narrative: Controller 1 gave us direct [to a fix]; then he gave us Pilots Discretion to FL240. We then started our descent. When we reached FL240 we were then cleared again Pilot's Discretion to FL190. We were never given a descend via clearance - we were only given direct. We were then switched to another controller. This controller then cleared us to descend via [the] arrival into ZZZ. I set the lowest altitude 5;000 feet for transition. Before I moved my finger I verified that the Pilot flying (PF) put it in Managed Descent and Managed Speed of which he did. Aircraft started to slow and we were on profile. Shortly thereafter the Controller was very curt in his question of our speed of which I professionally replied 278 knots. His agitated response was you should've been at 270 knots. This controller took it further by now telling us to call when we land. We were surprised by this tone; that we actually needed to have him repeat it. If there were separation issues; I don't think giving us a phone number twice fixes the separation issue - (of which we were not aware of any other aircraft - he did not point any traffic out). We are on a descent into mountainous terrain at night and becoming confused by ATC's handling of our flight. After that he told us to fly an off course heading. I heard turn 30 degrees left; the captain initiated a 30 degree right turn to what he thought was to be a 030 heading. When I saw him turn right I responded turning 30 degrees right thinking I misunderstood him of which the controller did not correct us. The next transmission came from the controller and he said I thought I told you to turn to the left. The controller told us stay on your course to the right to I believe a 030 heading. I queried the Captain and said that's where the high terrain is; we need to go back left. When I was about to ask ATC to go left he cleared us direct [to a fix] descend and maintain 7;000. There was a chain of events that started because we never were initially cleared to Descend Via the Arrival until inside the arrival. The manner in which this was handled; in my opinion raised safety issues by creating communication barriers and confusion. We landed without incident and then called the phone number at the gate. The Captain called and spoke with the ATC Supervisor. I did not hear the conversation the Captain had but I was told a synopsis from the Captain. He gave me a thumbs up that it's no problem and not to worry. Apparently this controller had a very heated discussion regarding this arrival with the Chief Pilot over this exact thing regarding speed on the arrival. In my opinion; from what I was briefed by the Captain; it almost seems we were almost setup to fall into what I believe was a 'trap'; so as to possibly validate his discussion with the Chief Pilot; just my opinion.

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.