MD-80
Flight Crew Air Transport Pilot (ATP)
Troubleshooting; Situational Awareness; Human-Machine Interface; Confusion
ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Chart Or Publication; Aircraft; Human Factors; Procedure
Flying the DEBBB1 arrival with a planned south runway arrival. Reviewed pictorial of arrival and text; but text was not reviewed thoroughly enough. When aircraft passed NCONA; it began a left turn to PHAUP. Both Captain and I felt this was in error; and the Captain as the Pilot Flying (PF) engaged heading hold to keep aircraft on path towards THASA.  15-20 seconds later I reviewed the text again; and informed the Captain that our path should be towards PHAUP for our southern runway assignment. He concurred; and we began to make the left turn back to PHAUP in heading mode; while he reprogrammed the FMS. While in the turn we were queried by ATC as to what we were doing. The Captain answered and advised that we were now direct PHAUP. It was at this time ATC broke us off of the approach and assigned us a heading. Upon landing; the Captain was asked to call ATC to discuss the incident. After this discussion; he advised that ATC was only interested in learning of any troubles with the new approaches; and that no action would be taken.[I suggest that] text that is associated with a procedure [be placed] at/near the intersection of that procedure where it is pertinent. We both had our arrivals on the IPAD zoomed in to insure compliance with altitudes and speeds on the arrival; thus putting the text of the arrival out of view. Once the aircraft starting doing something that we both thought was incorrect; we relied only on the zoomed-in pictorial; rather than using the text that was also associated with the procedure. Only a few seconds later; after shrinking our zoomed-in view; was the text revisited; and the aircraft turned back towards the correct flight path.While we both reviewed the FMS prior to commencing the approach; I failed to stay ahead of the procedure as the Non-flying pilot; to ensure that the pilot flying was sufficiently backed-up. A review of the runway specific information AFTER receiving our specific runway assignment would also help in this situation.
While flying the DEBBB arrival at NCONA intersection; it was unclear to us if we would be flying the 18r or 13r transition. Approach control was busy on the radio; and by the time we could call they simply cleared us to legre intersection on 18r. After landing I talked to the approach control supervisor; and we discussed the confusion as to which runway we would be landing on; and how all of the new sids and stars could be implemented so to lessen confusion for the pilots and controllers.[My suggestion was that] as soon as check in with approach control occurs; atc should inform the pilots of intended landing runway such that time permits to load the fms/fmc with the appropriate runway transition.
Center's failure to provide the planned landing runway when clearing the MD-82 for the DEBBB RNAV STAR to DFW contributed to a track deviation at NCONA where they should have tracked toward PHAUP but; instead; attempted to redirect the jet to THASA.