Date: 201501
Local time of day: 0601-1200
Location: PHX.Airport, AZ
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Challenger 605
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B PHX
ATC / advisory: TRACON P50
Aircraft component: Tablet
Component problem: Improperly Operated
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; 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; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Aircraft; Procedure
Primary problem: Human Factors

Narrative: Approximately 45 min prior to departure as pilot in command I was in the process of obtaining the PDC. We have 2 methods whereby this can be obtained. One is through our on board FMS system. The other is on iPads thru ARINC (Aeronautical Radio Incorporated). I chose to use the iPad. I saw the clearance for departure as the LULUZ 2 with ABQ transition and programmed the FMS as such. Unknown to me at that time what I now think I had done was looked at the filed route and mistook it for the cleared route. On the iPads the ARINC PDC is formatted as follows. The first line in small non bold print is the ATC clearance. Located immediately under that in much larger print and in bold is the ATC filed route. What I believe now is that while filling out my TOLD card my eyes going back and forth to the iPad I mistakenly looked at the bold print and wrote down the LALUZ 2 ABQ transition. That made sense as it was what I filed. The actual clearance was the FTHLS 2 ABQ transition. With the actual clearance printed in the small print I believe my eyes focused on the bold printed line which was the filed route.So we departed 7R and once airborne engaged the autopilot and selected NAV. The aircraft crossed the first fix SPRKY and proceeded NE to FORPE. Soon after beginning the turn the controller called us to verify we were on the FTHLS 2 Departure. We stated we were given the LALUZ 2 as we believed was the truth at that time. He instructed us to turn to a 080 heading and join the FTHLS 2 Departure which we complied with immediately. As the flight continued and I had time to reflect I made the determination after reviewing the iPad PDC that I had mistakenly programmed the filed route as opposed to the cleared route.Approximately an hour later when on with ABQ Center were given a phone number to call upon arrival. I immediately called upon arriving and spoke to the supervisor at PHX Approach Control. I told him everything I have stated here. I also asked him to confirm that at no time did we bust an altitude or have any other traffic conflicts of any kind. He assured me that he had reviewed the event and that there no traffic conflicts or altitude violations of any kind regarding this event.


Second narrative: It was interesting that the PHX controller on the phone stated that they have as many as 3 departure issues every week by airlines and part 91 alike. I would like to see the formatting change on the ARINC (Aeronautical Radio Incorporated) iPad PDC application; and I would like to see PHX adopt similar procedures like other major airports do; such as naming the first cleared fix when cleared for take-off; or adding the departure name with the take-off clearance.


Synopsis: A corporate Challenger 605 flight crew reported they flew the wrong departure from PHX when they failed to see a change in the PDC using the iPad.