Date: 201507
Local time of day: 1201-1800
Location: ZJX.ARTCC, FL
Flight conditions: IMC
Weather elements / visibility: Cloudy
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZJX
ATC / advisory: Center ZJX
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Human-Machine Interface
Second reporter function: Pilot Flying; First Officer
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: When in cruise flight over the top of SAV VOR. We were filed the HUSTN2 arrival into CLT. Once over the top of SAV VOR the aircraft turned to what I thought was NAVEE; instead it turned direct to HUSTN. Within 30 seconds the ATC controller asked if we were filed on the HUSTN2 arrival into CLT. I was the pilot monitoring so I said yes. The controller then said I show the aircraft left of course for the arrival. I then realized that the aircraft was indeed going to HUSTN instead of NAVEE. I quickly went into the FMS and redid the arrival; confirmed and executed the FMS direct to NAVEE. The controller never said anything else; and we continued back to the original course and arrival.The crew did review the flight plan in the FMS before the flight; as the captain I confirmed and copied the flight plan. After the event I asked the first officer; who put the flight plan in the FMS on the ground; if he understood what had happened. He realized that when he put the flight plan in the FMS he didn't add the transition to the arrival. So instead of selecting the HUSTN2 SAV transition he put SAV; HUSTN2 with no transition into the FMS. When I reviewed the FMS I read; SAV; HUSTN2 but didn't realize the transition wasn't inputted. Due to this the fixes on the arrival where not added in the FMS between SAV and HUSTN. I fixed the FMS and corrected the aircrafts course. I do not think the aircraft was more than 1/4 mile off course. Make sure to watch the first officer when he inputs the route into the FMS. Review the route closer on the before start checklist.


Second narrative: While I was loading FMS prior to flight; I loaded flight according to our paper release. However; as I did load both SAV and the HUSTN2 arrival; I did not properly select SAV as a 'transition' and a few fixes on the arrival were not properly loaded. Note: I brought HUSTN2 up under SAV to close out discontinuity. Which to my understanding now is why the fixes were not properly loaded.


Synopsis: CRJ700 flight crew is informed of a track deviation after crossing SAV on the HUSTN2 Arrival to CLT. The First Officer had not entered the SAV transition when entering the HUSTN2 into the FMC and had merely closed the route discontinuity.