Narrative:

We were on descent into ord; cleared for the benky 4 RNAV STAR arrival. Vnav descent winds were inserted prior to descent (approximately 100 tailwinds). Ord had a high altimeter setting about 30.39. We then received a clearance to cross benky intersection at 12000 ft. & 300kts. It is also possible we 'might have' received an earlier clearance to fly direct to benky. This was an 'all nighter'; so I'm using best recall.we had 12000 ft selected into the altitude mode control panel & had -vnav path- displayed on my pfd. & We had benky 12000 ft. & 300 kts inserted in the legs page. Everything looked normal. While my first officer (first officer) was briefing the approach; and I noticed the speed was suddenly increasing to 320-325 knots. But still in vnav path & 'right on' the vertical descent path display. I then deployed max (flight) speed brakes -to slow it down back to 300 kts. The plane was not slowing down; very much; at all - so I briefly pushed 'level change' mode to attempt to slow it down; further- to 300 kts @ benky intersection. (I still had full speed brakes deployed) near benky intersection; the vnav path began to show our vertical path 'high' & we crossed benky around 13000 ft & just above 300 kts. ATC never commented on our 'high crossing' altitude at benky intersection & there was no further incident.high tailwinds; on descent & a 'direct clearance' reduced the distance to descend to cross 12000 ft clearance at benky intersection.more proactive monitoring on descent and notifying ATC that we might not make the crossing restriction assigned- if it looks difficult to comply with.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737-800 flight crew reported missing a crossing restriction on arrival into ORD; citing fatigue; strong tailwinds; and automation dependency as factors.

Narrative: We were on descent into ORD; cleared for the BENKY 4 RNAV STAR arrival. Vnav descent winds were inserted prior to descent (approximately 100 tailwinds). ORD had a high altimeter setting about 30.39. We then received a clearance to cross BENKY intersection at 12000 ft. & 300kts. It is also possible we 'might have' received an earlier clearance to fly direct to BENKY. This was an 'all nighter'; so I'm using best recall.We had 12000 ft selected into the altitude mode control panel & had -Vnav Path- displayed on my PFD. & we had BENKY 12000 ft. & 300 kts inserted in the legs page. Everything looked normal. While my First officer (FO) was briefing the approach; and I noticed the speed was suddenly increasing to 320-325 knots. But still in Vnav Path & 'right on' the vertical descent path display. I then deployed max (flight) speed brakes -to slow it down back to 300 kts. The plane was not slowing down; very much; at all - so I briefly pushed 'level change' mode to attempt to slow it down; further- to 300 kts @ BENKY intersection. (I still had full speed brakes deployed) near BENKY intersection; the Vnav Path began to show our vertical path 'high' & we crossed BENKY around 13000 ft & just above 300 kts. ATC never commented on our 'high crossing' altitude at BENKY intersection & there was no further incident.High tailwinds; on descent & a 'direct clearance' reduced the distance to descend to cross 12000 ft clearance at BENKY intersection.More proactive monitoring on descent and notifying ATC that we might not make the crossing restriction assigned- if it looks difficult to comply with.

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.