Narrative:

On descent into phx, cleared to cross arlin intersection at or below 13000 ft, maintain 11000 ft, 250 KIAS. I fell behind in descent planning. Altitude change inputted into FMS prior to crossing clearance. Descent profile was not displayed as aircraft descended to the new altitude. I waited too long for FMS to display VNAV profile and combined with strong tailwinds, arrived at arlin at 13000 ft, 300 KIAS. ATC gave us relief of altitude restr, but not airspeed restr. The revised ATC clearance was: arlin at or below 15000 ft, maintain 11000 ft. At arlin, ATC did not query our airspeed or altitude. My lessons learned: better accounting for effect of tailwind on descent, and don't over rely on FMS -- especially when it is computing descent profile.

Google
 

Original NASA ASRS Text

Title: FLC OF B737 FAILED TO MEET SPEED RESTRICTION DSNDING INTO PHX.

Narrative: ON DSCNT INTO PHX, CLRED TO CROSS ARLIN INTXN AT OR BELOW 13000 FT, MAINTAIN 11000 FT, 250 KIAS. I FELL BEHIND IN DSCNT PLANNING. ALT CHANGE INPUTTED INTO FMS PRIOR TO XING CLRNC. DSCNT PROFILE WAS NOT DISPLAYED AS ACFT DSNDED TO THE NEW ALT. I WAITED TOO LONG FOR FMS TO DISPLAY VNAV PROFILE AND COMBINED WITH STRONG TAILWINDS, ARRIVED AT ARLIN AT 13000 FT, 300 KIAS. ATC GAVE US RELIEF OF ALT RESTR, BUT NOT AIRSPD RESTR. THE REVISED ATC CLRNC WAS: ARLIN AT OR BELOW 15000 FT, MAINTAIN 11000 FT. AT ARLIN, ATC DID NOT QUERY OUR AIRSPD OR ALT. MY LESSONS LEARNED: BETTER ACCOUNTING FOR EFFECT OF TAILWIND ON DSCNT, AND DON'T OVER RELY ON FMS -- ESPECIALLY WHEN IT IS COMPUTING DSCNT PROFILE.

Data retrieved from NASA's ASRS site as of July 2007 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.