A corporate challenger 605 flight crew reported they flew the wrong departure from phx when they fai...

Narrative:

Approximately 45 min prior to departure as pilot in command I was in the process of obtaining the pre departure clearance. 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 pre departure clearance 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 navigation. The aircraft crossed the first fix sprky and proceeded northeast 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 pre departure clearance 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.

Original NASA ASRS Text

Title: 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.

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.

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.

Attributes
ACN	1231697
Time
Date	201501
Local Time Of Day	0601-1200
Place
Locale Reference	PHX.Airport
State Reference	AZ
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Challenger 605
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	SID FTHLS2
Flight Plan	IFR
Component
Aircraft Component	Tablet
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 70 Flight Crew Total 10500 Flight Crew Type 300
Person 2
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 75 Flight Crew Total 13000 Flight Crew Type 1500
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

A corporate challenger 605 flight crew reported they flew the wrong departure from phx when they failed to see a change in the pre departure clearance using the ipad.