Narrative:

Flying the lateral portion of the stocr arrival into clt. It is very common for atl center to descend aircraft; change speeds; and give exceptions to this published arrival. Given the arrival starts at FL290; it is common to receive descent clearances as low at 14;000; then a descend via clearance is given. On this leg; we were descended to FL210 over the course of the last many miles; stepped down from cruise and disregarding the published altitudes on the arrival. We were at 320 knots as we were significantly late. No objections on the speed from center. Level at FL210; we were between the fllgg and ffnsh intersections. Atl center cleared us via the stocr arrival landing north. Set 6;000 feet in the MCP and verified VNAV armed. The next published speed was 280 knots at ffnsh. The airplane was armed to slow to 280 at this fix. Prior to reaching ffnsh; ATC asked if we were 'flying published speeds'. Stated flying 320 and would slow to 280 as published at ffnsh. There was no loss of separation; but apparently they didn't have the in trail they needed. Told us to slow to 250; then 'resume published speeds at ffnsh'. Later gave us a vector for additional spacing.like many of the other arrivals in clt; if ATC would just use the published arrivals and let the aircraft fly them; it would prevent issues like this. ATC gave us no other speed clearances. This is also very common landing to the east in phx. After this happened; captain and first officer discussed and both expected to slow to 280 at ffnsh and not prior.ATC makes exceptions to published arrivals; then re-clears onto the arrival. ATC should keep us on the arrival. Or redesign the arrival.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air Carrier First Officer reported that ATC did not keep them on the published arrival.

Narrative: Flying the lateral portion of the STOCR arrival into CLT. It is very common for ATL center to descend aircraft; change speeds; and give exceptions to this published arrival. Given the arrival starts at FL290; it is common to receive descent clearances as low at 14;000; then a descend VIA clearance is given. On this leg; we were descended to FL210 over the course of the last many miles; stepped down from cruise and disregarding the published altitudes on the arrival. We were at 320 knots as we were significantly late. NO objections on the speed from center. Level at FL210; we were between the FLLGG and FFNSH intersections. ATL center cleared us via the STOCR arrival landing north. Set 6;000 feet in the MCP and verified VNAV armed. The next published speed was 280 knots at FFNSH. The airplane was armed to slow to 280 at this fix. Prior to reaching FFNSH; ATC asked if we were 'flying published speeds'. Stated flying 320 and would slow to 280 as published at FFNSH. There was no loss of separation; but apparently they didn't have the in trail they needed. Told us to slow to 250; then 'resume published speeds at FFNSH'. Later gave us a vector for additional spacing.Like many of the other arrivals in CLT; if ATC would just use the published arrivals and let the aircraft fly them; it would prevent issues like this. ATC gave us no other speed clearances. This is also very common landing to the east in PHX. After this happened; CAPT and FO discussed and both expected to slow to 280 at FFNSH and not prior.ATC makes exceptions to published arrivals; then re-clears onto the arrival. ATC should keep us on the arrival. Or redesign the arrival.

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.