Narrative:

During arrival on the hawkz two with north flow in sea; we were initially assigned runway 34C while descending through approximately 12;000 ft. The crossing altitude for foott intersection on the arrival has charted between 12;000 ft and 10;000 ft. The captain had trouble re-establishing his vpath so we crossed foott intersection on the arrival 700 ft high. We proceeded across goalz at the back calculated altitude in the FMS. At this point we switched to heading and vertical speed modes in order to cross fill the approach for 34C as the approach for 34L had been preloaded. As expected this dumped the back calculated altitude and we were left with no vertical guidance except the altitude alerter. About 3 NM from sondr we reported the airport and the commons mall in sight but were cleared for the ILS to 34C via the transition to lorie. Since the transition from cidug had been loaded in anticipation of a visual approach; the approach once again had to be modified in the FMS. At this point we crossed sondr at airspeed of approximately 225 KTS instead of the published 210 KT speed restriction. The controller then asked us to reduce speed to 210 KTS. Upon intercepting the final approach course to 34C we were assigned a speed of 160 KTS and then subsequently the controller changed our runway assignment to 34L. We then were asked if we had company traffic in sight which we did not. The controller then canceled our approach clearance; turned us out to the west; and climbed us to 4;000 ft to attempt the approach again. I believe this event can partially be attributed to pre-planning and pre-programming the FMS in anticipation of a visual approach after sondr. The cause of this event can also be attributed to the high workload created by numerous altitude and airspeed gates that must be achieved on the hawkz two arrival coupled with sea TRACON's uncertainty on runway assignments. The nature of this arrival creates a programming nightmare below 10;000 ft primarily when the expected approach and runway assignment aren't given until late in the arrival.

Google
 

Original NASA ASRS Text

Title: SEA TRACON canceled an air carrier approach to Runway 34L on the HAWKZ TWO RNAV because they did not see traffic ahead but the Captain was still attempting to reprogram his FMS after ATC changed the landing runway from 34C to 34L.

Narrative: During arrival on the HAWKZ TWO with north flow in SEA; we were initially assigned Runway 34C while descending through approximately 12;000 FT. The crossing altitude for FOOTT intersection on the arrival has charted between 12;000 FT and 10;000 FT. The Captain had trouble re-establishing his VPATH so we crossed FOOTT intersection on the arrival 700 FT high. We proceeded across GOALZ at the back calculated altitude in the FMS. At this point we switched to heading and vertical speed modes in order to cross fill the approach for 34C as the approach for 34L had been preloaded. As expected this dumped the back calculated altitude and we were left with no vertical guidance except the altitude alerter. About 3 NM from SONDR we reported the airport and the Commons Mall in sight but were cleared for the ILS to 34C via the transition to LORIE. Since the transition from CIDUG had been loaded in anticipation of a visual approach; the approach once again had to be modified in the FMS. At this point we crossed SONDR at airspeed of approximately 225 KTS instead of the published 210 KT speed restriction. The Controller then asked us to reduce speed to 210 KTS. Upon intercepting the final approach course to 34C we were assigned a speed of 160 KTS and then subsequently the Controller changed our runway assignment to 34L. We then were asked if we had company traffic in sight which we did not. The Controller then canceled our approach clearance; turned us out to the west; and climbed us to 4;000 FT to attempt the approach again. I believe this event can partially be attributed to pre-planning and pre-programming the FMS in anticipation of a visual approach after SONDR. The cause of this event can also be attributed to the high workload created by numerous altitude and airspeed gates that must be achieved on the HAWKZ TWO arrival coupled with SEA TRACON's uncertainty on runway assignments. The nature of this arrival creates a programming nightmare below 10;000 FT primarily when the expected approach and runway assignment aren't given until late in the arrival.

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