Date: 202012
Local time of day: 0601-1200
Location: ZZZ.Tower, US
Flight conditions: VMC
Aircraft: Medium Transport
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb; Climb
Airspace: Class E ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Distraction
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: While flying the ZZZZZ RNAV departure this morning; ATC asked us if we were assigned a heading from the last Controller. The PM replied stating we were direct ZZZZZ1; with ZZZZZ behind us on the FMS legs page. This made us look closely at our legs page and moving map on our iPads; which showed us off course. ATC replied with 'roger.' Shortly following that; we were handed off to the next controller. When we checked in we mentioned our box input error and he said; 'No problem; proceed direct ZZZ1. How's that?' No further discussion with ATC. I immediately knew what happened and why. The FMS would not download our flight plan (not uncommon) so I built in manually. As I looked at the clearance I noticed the departure and selected it; but failed to assign the ZZZZZ1 transition. ZZZZZ1 appeared on our route packet as a different fix; not part of the departure and I fell for it. I had a lot of fixes and airways to type in so I focused on getting them correct and failed to notice how I had loaded the departure; without the transition. Ultimately we were missing 4 fixes in the legs page. I checked the first 5 fixes in the legs page to confirm the altitude restrictions since we were cleared to climb Via. Normally I check all the fixes but the other contributing factors today were no coffee or breakfast at this point. I wanted to get setup and ready so I could get coffee. Due to COVID; food and coffee was not available at the hotel so we catered it for our morning departure. Additionally; the pax showed up XX minutes early which squashed my plans to eat before we took off. Additionally; the lead pax birth date was incorrect on our brief so we were further distracted.Human error. I caused this event during the FMS setup. The pre-flight distractions becoming more and more common place with passenger related issues of catering and name details; today it got me. Another potential cause could be how the flight plan route is displayed on our packets. I'm used to seeing something like 'ZZZZZ.ZZZZZ1 ZZZ2; etc.;' as the FMS shows; but the filed route on our flight plan shows 'ZZZZZ ZZZZZ1 ZZZ2; etc.' Seeing it with the period would have drawn my attention to the ZZZZZ1 transition. Suggestions - For me; all things being the same again; if the filed route on our flight plan packet showed 'ZZZZZ.ZZZZZ1' this deviation wouldn't have happened today. Regardless of this and the distractions; I need to be more careful.


Second narrative: Clearance was ZZZZZ departure ZZZZZ1 transition; data link would not download flight plan. Flight plan was manually entered by PF loaded ZZZZZ departure to ZZZZZ then direct ZZZZZ1.  When verifying flight plan off filed route page neither of us caught this manual entry error.  When asked if on heading by ATC we started wondering why so checked departure and GPS position and found our error.  Asked ATC if we needed to correct error and they said no and cleared us farther down line on clearance.  Possible contributing factor were passengers showed XX minutes early; the way ARINC flight plan filed route shows on first page.  Things could do to correct this issue on future.  Verify and check each fix on the departure and also check mark each fix on lat long pages in flight plan compared to what is in the box.The way filed route showed on ARINC page; not loading transition properly when manually entering flight plan.Cross check each leg of the departure versus the plate.  Also check mark each way point matches the lag/long pages in the ARINC flight plan.  Any time having to manually enter information verify everything a couple times.


Synopsis: Corporate flight crew reported a track heading deviation due to loading an incorrect transition fix in the FMS.