Narrative:

Upon arrival to bfi we were flying the jawbn six arrival without incident until we reached alkia fix on the arrival. At that point it diverges in three different directions depending on the runway in use at bfi; or traffic going to mcchord field. The way I had my chart set on my screen; it looked to me that the landing south heading of 070 off alkia fix was correct for the arrival; so I didn't catch it right away. (I had the chart zoomed in so I didn't clearly see the south courses on the screen.) when the airplane started to turn to the 070 degree course it looked correct to me. In addition to that; we were task saturated in the descent looking for traffic and setting the airplane up to land on a 20 minute flight. We discussed the arrival runway briefly but the FMS (flight management system) defaulted to landing south and we didn't catch it in time. The approach controller turned us to a heading; and advised of the landing runway heading requirements for the arrival at alkia; and we proceeded and landed without further incident.the arrival procedures that I have seen lately are being used for so many different airports and landing directions that it is becoming difficult to see these types of errors before they happen. Instead of having one fix where three different things can happen; have a different name for each procedure that is runway specific and leads you to a different fix; or onto the approach. Such as jawbn south; jawbn north; etc. Denver is becoming more like this as well; if we are task saturated it can be confusing to get a common split point like alkia and know for sure what is supposed to happen when you get there. Even if you have briefed the approach; it can cause confusion. In the future; I know that I am going to have to see the multi divergent courses piled on one fix as a threat and focus on them in the brief to ensure what should happen at the fix is clear before we get there and things are busy.

Related reports:

Google
 

Original NASA ASRS Text

Title: Corporate jet flight crew reported a heading deviation while on the JAWBN SIX ARRIVAL to BFI.

Narrative: Upon arrival to BFI we were flying the JAWBN SIX ARRIVAL without incident until we reached ALKIA fix on the arrival. At that point it diverges in three different directions depending on the runway in use at BFI; or traffic going to McChord Field. The way I had my chart set on my screen; it looked to me that the landing south heading of 070 off ALKIA fix was correct for the arrival; so I didn't catch it right away. (I had the chart zoomed in so I didn't clearly see the south courses on the screen.) When the airplane started to turn to the 070 degree course it looked correct to me. In addition to that; we were task saturated in the descent looking for traffic and setting the airplane up to land on a 20 minute flight. We discussed the arrival runway briefly but the FMS (Flight Management System) defaulted to landing south and we didn't catch it in time. The Approach Controller turned us to a heading; and advised of the landing runway heading requirements for the arrival at ALKIA; and we proceeded and landed without further incident.The arrival procedures that I have seen lately are being used for so many different airports and landing directions that it is becoming difficult to see these types of errors before they happen. Instead of having one fix where three different things can happen; have a different name for each procedure that is runway specific and leads you to a different fix; or onto the approach. Such as JAWBN SOUTH; JAWBN NORTH; etc. Denver is becoming more like this as well; if we are task saturated it can be confusing to get a common split point like ALKIA and know for sure what is supposed to happen when you get there. Even if you have briefed the approach; it can cause confusion. In the future; I know that I am going to have to see the multi divergent courses piled on one fix as a threat and focus on them in the brief to ensure what should happen at the fix is clear before we get there and things are busy.

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.