Narrative:

Having executed the hawkz arrival into sea approximately 5 times now - I finally decided to provide feedback about how bad this arrival works. Today's flight included an additional ATC 'slow to 230 KTS' clearance; while maintaining all the required crossings (our FMC had us scheduled for 260 KTS). Our VNAV path was disrupted and caused distractions. Previous experiences I've had: first (two times) ATC changed expected runway close to the time we crossed a fix - causing a huge distraction and disconnect in both LNAV/VNAV because of programming. Cws was entered. In one case; the LNAV created a 'holding pattern' course. Had I not seen it before - it's likely that my captain would have been off course. Next; strong tailwinds cause inability to make crossings. Finally; ATC slows us and still asking for crossing restrictions. The hawkz arrival is a failure. FAA; my company and ATC knows this. It has consistently resulted in higher workloads; distractions and reduced safety to our operations arriving into sea. Despite numerous reports from other pilots; someone who insists on us continuing to use the arrival (personal agenda or otherwise; refuses to acknowledge the problems related to this arrival. This approach doesn't work because of the 'one size fits all aircraft' it was made to apply to. Additionally; the dynamic changes (usually runway changes assigned by ATC) in descent into sea - make it incompatible for this environment and airspace. It needs to be taken out of use until it can be fixed. If this hawkz arrival causes my fellow crews or I a violation or incident; the numerous reports that have been submitted will come forth during a hearing; should one take place. For safety reasons; I recommend the arrival be discontinued until a useful fix can be made. Those persons ignoring these reports need to acknowledge its incompatibility and resulting higher workloads and do the right thing. Acknowledge the hawkz arrival lends higher workload and less safety; then discontinue use of the hawkz arrival until it can be fixed!

Related reports:

Google
 

Original NASA ASRS Text

Title: A B737 Captain strongly expressed his dissatisfaction; supported by multiple personal examples of operational issues; with the lack of response from his Company and the FAA to numerous reports he and other pilots have submitted regarding the disfunctionality and the reduced safety resulting from use of the HAWKZ RNAV STAR into SEA.

Narrative: Having executed the HAWKZ Arrival into SEA approximately 5 times now - I finally decided to provide feedback about how BAD this arrival works. Today's flight included an additional ATC 'slow to 230 KTS' clearance; while maintaining all the required crossings (our FMC had us scheduled for 260 KTS). Our VNAV path was disrupted and caused distractions. Previous experiences I've had: First (two times) ATC changed expected runway close to the time we crossed a fix - causing a huge distraction and disconnect in both LNAV/VNAV because of programming. CWS was entered. In one case; the LNAV created a 'holding pattern' course. Had I not seen it before - it's likely that my Captain would have been off course. Next; strong tailwinds cause inability to make crossings. Finally; ATC slows us and still asking for crossing restrictions. The HAWKZ arrival is a failure. FAA; my company and ATC knows this. It has consistently resulted in higher workloads; distractions and reduced safety to our operations arriving into SEA. Despite numerous reports from other pilots; someone who insists on us continuing to use the arrival (personal agenda or otherwise; refuses to acknowledge the problems related to this arrival. This approach doesn't work because of the 'one size fits all aircraft' it was made to apply to. Additionally; the dynamic changes (usually runway changes assigned by ATC) in descent into SEA - make it incompatible for this environment and airspace. It needs to be taken out of use until it can be fixed. If this HAWKZ Arrival causes my fellow crews or I a violation or incident; the numerous reports that have been submitted will come forth during a hearing; should one take place. For safety reasons; I recommend the arrival be discontinued until a useful fix can be made. Those persons ignoring these reports need to acknowledge its incompatibility and resulting higher workloads and do the right thing. Acknowledge the HAWKZ arrival lends higher workload and less safety; then discontinue use of the HAWKZ arrival until it can be fixed!

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.