Narrative:

While descending to cross misen @ FL240 and managing separate ATC speed requests 250 knots; 280 knots; normal speed 300 knots while blending with normal flow. I selected VNAV and confirmed with pilot monitoring that 24;000 [feet] was selected and captured with a descent to 24;000 [feet] at misen and showing in the FMS. Pilot monitoring then went to set up approch. Aircraft was descending with magenta arrow on profile to cross misen at 24;000 [feet]. I acknowledged w/ATC at misen. Crossing at 24;000 [feet] and speed reduction and a frequency change. During frequency sign on; ATC queried our crossing restriction at misen at which time aircraft was within 2 miles or less and both pilot flying/pilot monitoring realized we were going to be unable to meet the restriction at misen by approximately 1;500 feet and reported such to ATC. ATC advised to continue and shared that no loss of separation occurred and we continued without further incident on the arrival.pilot monitoring upon rejoining radio/phase of flight request detected crossing restriction indications and confirmed our ATC instructions and checked in with new ATC assignment our crossing deviation at misen. Busy flight; multiple ATC request during busy phase of flight with duty separation by both pilots.during flight and crew debrief - both pilots acknowledged previous experience with this aircraft showing a captured VNAV descent to a waypoint with similar experience showing normal indications of captured flight profile that had to be manually rescued or re-initialized to achieve an accurate autopilot commanded VNAV solution.both pilots immediately rechecked VNAV waypoints and programming steps and found no apparent reason for suspect VNAV error which was now continuing to solve descend via calculations on our arrival.both pilots immediately agreed to joint manual time/descent monitoring for remainder of approach profile while sharing. Both pilots agreed to self-critique of not sufficient enough CRM to catch descent deviation this flight during the event and later after the flight as a debrief. I have immense respect for [other] pilot's monitoring skills and airmanship. I should have mitigated the descent profile by interacting sooner with the VNAV crosschecking.continued adherence to company and personal airmanship sops. Use every resource every time -never letting your guard down. Thankfully; early renewed CRM within the cockpit and relaying to the new ATC our deviation did not result in loss of separation on this descend via STAR.

Related reports:

Google
 

Original NASA ASRS Text

Title: Fractional aircraft Captain reported a missed crossing restriction due to workload and distraction from several clearance changes during descent.

Narrative: While descending to cross MISEN @ FL240 and managing separate ATC speed requests 250 knots; 280 knots; Normal speed 300 knots while blending with normal flow. I selected VNAV and confirmed with Pilot Monitoring that 24;000 [feet] was selected and captured with a descent to 24;000 [feet] at MISEN and showing in the FMS. Pilot Monitoring then went to set up APPROCH. Aircraft was descending with magenta arrow on profile to cross MISEN at 24;000 [feet]. I acknowledged w/ATC at MISEN. Crossing at 24;000 [feet] and speed reduction and a frequency change. During frequency sign on; ATC queried our crossing restriction at MISEN at which time Aircraft was within 2 miles or less and both Pilot Flying/Pilot Monitoring realized we were going to be unable to meet the restriction at MISEN by approximately 1;500 feet and reported such to ATC. ATC advised to continue and shared that no loss of separation occurred and we continued without further incident on the arrival.Pilot Monitoring upon rejoining radio/phase of flight request detected crossing restriction indications and confirmed our ATC instructions and checked in with new ATC Assignment our crossing deviation at MISEN. Busy Flight; multiple ATC request during busy phase of flight with duty separation by both pilots.During flight and crew debrief - both pilots acknowledged previous experience with this Aircraft showing a captured VNAV descent to a waypoint with similar experience showing normal indications of captured flight profile that had to be manually rescued or re-initialized to achieve an accurate autopilot commanded VNAV solution.Both pilots immediately rechecked VNAV WAYPOINTS and programming steps and found no apparent reason for suspect VNAV error which was now continuing to solve descend via calculations on our arrival.Both pilots immediately agreed to joint manual time/descent monitoring for remainder of approach profile while sharing. Both pilots agreed to self-critique of not sufficient enough CRM to catch descent deviation this flight during the event and later after the flight as a debrief. I have immense respect for [other] pilot's monitoring skills and airmanship. I should have mitigated the descent profile by interacting sooner with the VNAV crosschecking.Continued adherence to Company and personal airmanship SOPs. Use every resource every time -NEVER LETTING YOUR GUARD DOWN. Thankfully; early renewed CRM within the cockpit and Relaying to the New ATC our Deviation did not result in loss of separation on this descend via STAR.

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.