Falcon 50 first officer reports a track deviation while flying the HYPER5 arrival into iad. The flyi...

Attributes
ACN	1277382
Time
Date	201507
Local Time Of Day	1201-1800
Place
Locale Reference	IAD.Airport
State Reference	DC
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Falcon 50
Operating Under FAR Part	Part 91
Flight Phase	Descent
Route In Use	STAR HYPER5
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	First Officer Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 60 Flight Crew Total 14910 Flight Crew Type 1900
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

We were flying the HYPER5 arrival landing at iad. Potomac instructed us to descend via the HYPER5 before arriving at mulrr. The pilot flying had his FMS loaded for runway 1R; my FMS was loaded for 1C. However; the pilot flying had not loaded the segment of the HYPER5 after mulrr properly in his FMS. After crossing mulrr intersection; the pilot flying continued on his present heading without making the appropriate turn towards sigbe intersection and descending via the RNAV arrival. I noticed the problem and asked the pilot flying to start a turn while I corrected his FMS. Too late! Potomac noticed our deviation and began issuing headings and altitudes.we fly to iad often but not using the HYPER5 arrival. The pilot flying did not digest the entire arrival and I missed the wrong sequence of navigation fixes on his FMS. We were very busy in the cockpit and lacked attention to detail. In the future we will take a larger view of the procedures earlier in the flight.

Original NASA ASRS Text

Title: Falcon 50 First Officer reports a track deviation while flying the HYPER5 Arrival into IAD. The flying Captain's FMS was not properly programed to make the turn at MULRR to SIGBE resulting in vectors from PCT.

Narrative: We were flying the HYPER5 arrival landing at IAD. Potomac instructed us to descend via the HYPER5 before arriving at MULRR. The pilot flying had his FMS loaded for runway 1R; my FMS was loaded for 1C. However; the pilot flying had not loaded the segment of the HYPER5 after MULRR properly in his FMS. After crossing MULRR intersection; the pilot flying continued on his present heading without making the appropriate turn towards SIGBE intersection and descending via the RNAV arrival. I noticed the problem and asked the pilot flying to start a turn while I corrected his FMS. Too late! Potomac noticed our deviation and began issuing headings and altitudes.We fly to IAD often but not using the HYPER5 arrival. The pilot flying did not digest the entire arrival and I missed the wrong sequence of navigation fixes on his FMS. We were very busy in the cockpit and lacked attention to detail. In the future we will take a larger view of the procedures earlier in the flight.

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.

Falcon 50 first officer reports a track deviation while flying the HYPER5 arrival into iad. The flying captain's FMS was not properly programed to make the turn at mulrr to sigbe resulting in vectors from pct.