Narrative:

Second trip to slc. We were on a jammin 4 STAR and were assigned a heading to ffu to cross 20 mi south of ffu at 15000 ft and 230 KTS. Since this was not part of the STAR, we were programming FMS when center (ATC) asked us if we would meet crossing restr. We were situationally challenged and were not able to meet the crossing restr and were given a vector because center said approach couldn't take us at that altitude. No traffic conflict was mentioned. Later, approach controller stated center was having trouble getting aircraft down in time.

Google
 

Original NASA ASRS Text

Title: INABILITY TO MAKE A XING RESTR RESULTS IN A DELAYING VECTOR TO MEET HDOF ALT REQUIREMENTS.

Narrative: SECOND TRIP TO SLC. WE WERE ON A JAMMIN 4 STAR AND WERE ASSIGNED A HDG TO FFU TO CROSS 20 MI S OF FFU AT 15000 FT AND 230 KTS. SINCE THIS WAS NOT PART OF THE STAR, WE WERE PROGRAMMING FMS WHEN CTR (ATC) ASKED US IF WE WOULD MEET XING RESTR. WE WERE SITUATIONALLY CHALLENGED AND WERE NOT ABLE TO MEET THE XING RESTR AND WERE GIVEN A VECTOR BECAUSE CTR SAID APCH COULDN'T TAKE US AT THAT ALT. NO TFC CONFLICT WAS MENTIONED. LATER, APCH CTLR STATED CTR WAS HAVING TROUBLE GETTING ACFT DOWN IN TIME.

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.