Narrative:

Aircraft X; filed for the arrival; ZZZ1 transition. Flight was unremarkable until during the arrival descent. Flight passed ZZZ1 at XA40Z and continued on the arrival. As the flight approached the planned top of descent point; ATC directed the flight to 'cross zzzzz at 14;000; maintain 280 knots' (arrival has zzzzz with a window from 16;000 to FL190); and to advise if we could not make that restriction. We were not given any runway assignment at that time. To expedite the descent; PF used lvl change; increased airspeed via the MCP to 320 knots and deployed the speed brakes to reach the new descent path; and adjusted the legs page accordingly. Once the vertical descent path indicator showed us on profile; VNAV was reengaged and the flight maintained VNAV path to zzzzz. The flight was never cleared to 'descend via' the arrival; and was not yet given a runway assignment. At this time; the flight began to get three ACARS messages from the crew desk regarding a reassignment on arrival in ZZZ (first one received at XA46Z; second one at XA52Z; third one at XA55Z). Crew noted the reassignment and after the third ACARS message; flight responded via ACARS with 'copy all'; and we redirected our attention to the flight. Approaching zzzzz; we received another frequency change; and upon check in with that controller; we were directed to 'descend and maintain 6000 ft; expect runway xx'. Because we were still maintaining 280 knots as previously cleared; I selected lvl chg for 6000 ft and we proceeded to brief the approach and complete the descent checklist. As we were doing that; I (as PF) failed to slow the aircraft to 250 knots at 10;000 ft per far 91.117. I realized the error passing 8;500 ft and then selected 250 knots in the MCP speed window; and by 8;000 ft we were slowed to 250 knots. The remainder of the approach was conducted without incident; and there was no communications with ATC regarding the speed exceedance. To be clear; while ATC handling was different from the arrival (hard descents and airspeeds; instead of the VNAV profile); all ATC directions were standard and clearly understood. Bottom line is we had numerous distractions in what was a critical phase of flight; and in spite of our best efforts to stay ahead of the aircraft and our expectation for a late runway assignment; I still failed to slow the aircraft to 250 knots at 10;000 ft.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737 Captain reported a FAR violation due to distractions from the company during a sterile flight deck period.

Narrative: Aircraft X; filed for the Arrival; ZZZ1 transition. Flight was unremarkable until during the arrival descent. Flight passed ZZZ1 at XA40Z and continued on the arrival. As the flight approached the planned top of descent point; ATC directed the flight to 'cross ZZZZZ at 14;000; maintain 280 knots' (arrival has ZZZZZ with a window from 16;000 to FL190); and to advise if we could not make that restriction. We were not given any runway assignment at that time. To expedite the descent; PF used LVL Change; increased airspeed via the MCP to 320 knots and deployed the speed brakes to reach the new descent path; and adjusted the LEGS page accordingly. Once the vertical descent path indicator showed us on profile; VNAV was reengaged and the flight maintained VNAV PATH to ZZZZZ. The flight was never cleared to 'descend via' the arrival; and was not yet given a runway assignment. At this time; the flight began to get three ACARS messages from the crew desk regarding a reassignment on arrival in ZZZ (first one received at XA46Z; second one at XA52Z; third one at XA55Z). Crew noted the reassignment and after the third ACARS message; flight responded via ACARS with 'COPY ALL'; and we redirected our attention to the flight. Approaching ZZZZZ; we received another frequency change; and upon check in with that controller; we were directed to 'descend and maintain 6000 FT; expect Runway XX'. Because we were still maintaining 280 knots as previously cleared; I selected LVL CHG for 6000 FT and we proceeded to brief the approach and complete the descent checklist. As we were doing that; I (as PF) failed to slow the aircraft to 250 knots at 10;000 FT per FAR 91.117. I realized the error passing 8;500 FT and then selected 250 knots in the MCP speed window; and by 8;000 FT we were slowed to 250 knots. The remainder of the approach was conducted without incident; and there was no communications with ATC regarding the speed exceedance. To be clear; while ATC handling was different from the arrival (hard descents and airspeeds; instead of the VNAV profile); all ATC directions were standard and clearly understood. Bottom line is we had numerous distractions in what was a critical phase of flight; and in spite of our best efforts to stay ahead of the aircraft and our expectation for a late runway assignment; I still failed to slow the aircraft to 250 knots at 10;000 FT.

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.