B737-700 first officer reported missing a crossing restriction on the BRUSR1 RNAV to phx. ATC had as...

Narrative:

BRUSR1 RNAV arrival into phx. Need I say more?briefed as a threat and even mentioned the number of as soon as possible's related to this arrival. Issued by ATC a separate altitude at tents that was not published on the arrival. Issued an early speed reduction not published. Issued another early speed reduction that was not published. We told ATC we would not make the crossing restriction of 9000 at zilub due to the speed reduction and they said that was okay. We went to lvl chg to descend as quickly as possible at 210 knots and received a TCAS alert which took both of our heads outside to look for traffic. When we came back inside we were at 7800' slightly below the briez restriction between 8000 and 9000. We leveled off immediately and resumed the arrival. ATC never mentioned anything and he flight continued uneventfully.totally our fault for not resetting the MCP altitude window when we left VNAV; but that TCAS was perfectly timed to distract us. We failed to reset MCP altitude when switching from VNAV to lvl chg due to a TCAS distraction.as a regular line pilot who reads the as soon as possible news; what in the world has to be done with this arrival into phx? We either fly the arrivals as it is published or the controllers should revert back to issuing clearances. If they aren't going to just issue descend via then get rid of the arrival. We had 1 altitude and 2 speed reductions that weren't published within 100 miles. That can be a normal thing; but the speeds and altitudes they issued were impossible to make. If they give a speed reduction they should know we can't make the altitudes and then just issue a descend and maintain clearance. I know we messed this up; but this arrival is an as soon as possible waiting to happen when ATC gets involved; which it seems like they always do.

Original NASA ASRS Text

Title: B737-700 First Officer reported missing a crossing restriction on the BRUSR1 RNAV to PHX. ATC had assigned one altitude change and two speed adjustments during the arrival and the crew experienced a TCAS event just before the altitude overshoot.

Narrative: BRUSR1 RNAV arrival into PHX. Need I say more?Briefed as a threat and even mentioned the number of ASAP's related to this arrival. Issued by ATC a separate altitude at TENTS that was not published on the arrival. Issued an early speed reduction not published. Issued another early speed reduction that was not published. We told ATC we would not make the crossing restriction of 9000 at ZILUB due to the speed reduction and they said that was okay. We went to LVL CHG to descend as quickly as possible at 210 knots and received a TCAS alert which took both of our heads outside to look for traffic. When we came back inside we were at 7800' slightly below the BRIEZ restriction between 8000 and 9000. We leveled off immediately and resumed the arrival. ATC never mentioned anything and he flight continued uneventfully.Totally our fault for not resetting the MCP altitude window when we left VNAV; but that TCAS was perfectly timed to distract us. We failed to reset MCP altitude when switching from VNAV to LVL CHG due to a TCAS distraction.As a regular line pilot who reads the ASAP news; what in the world has to be done with this arrival into PHX? We either fly the arrivals as it is published or the controllers should revert back to issuing clearances. If they aren't going to just issue descend via then get rid of the arrival. We had 1 altitude and 2 speed reductions that weren't published within 100 miles. That can be a normal thing; but the speeds and altitudes they issued were impossible to make. If they give a speed reduction they should know we can't make the altitudes and then just issue a descend and maintain clearance. I know we messed this up; but this arrival is an ASAP waiting to happen when ATC gets involved; which it seems like they always do.

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.

Attributes
ACN	1350518
Time
Date	201604
Local Time Of Day	0001-0600
Place
Locale Reference	P50.TRACON
State Reference	AZ
Environment
Light	Dawn
Aircraft 1
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	STAR BRUSR1
Flight Plan	IFR
Component
Aircraft Component	MCP
Person 1
Function	First Officer Pilot Not Flying
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Published Material / Policy

B737-700 first officer reported missing a crossing restriction on the BRUSR1 RNAV to phx. ATC had assigned one altitude change and two speed adjustments during the arrival and the crew experienced a TCAS event just before the altitude overshoot.