Narrative:

We were flying the bonham 4 arrival to dfw, positioned somewhere between fixes glove and robey, when ATC gave us an arrival change to the wilbr 2. Copilot's leg, so he immediately started looking up the wilbr 2 in his flight manual while I started programming the FMS. We were unfamiliar with the wilbr 2. Soon after receiving the clearance, we received another clearance to cross addvl at 11000 ft. The copilot and I were a little confused on the clearance because of the controller's pronunciation of addvl. We were tracking the 064 degree radial off byp in navigation track and started our descent in order to meet the altitude restr. After I put the wilbr 2 in the box, we noticed a mileage disparity between raw data and the navigation on the distance to addvl. Trying to resolve this disparity, we ended up flying 1 DOT right of the 222 degree inbound course to it. It seemed we did not have enough time between the time we were given the clearance to find the arrival, set it up, program the navigation and figure where we were relative to it before a critical course change was required. We were attempting to correct back onto course when the ATC controller gave us a heading of 240 degrees. Then another controller, possibly a supervisor, questioned our course and said that we had flown through a 'jump zone.' at that time, we got a TCASII RA alert, had visual contact, and a small civil aircraft flew over us 700 ft above. From there, the controller gave us vectors to an uneventful landing on runway 17C at dfw. Multiple factors could have led to this navigation error. It definitely took us longer than expected to set up for this arrival while trying to resolve our confusion with the clearance and the navigation. Also we had ATIS information and there was no mention on the ATIS, or from the controller about jump zone traffic in the vicinity of byp. In the future, I will put more emphasis on flying raw data. Trying to fly the navigation without having it properly set up is what led us off course.

Google
 

Original NASA ASRS Text

Title: MD80 FLT CREW BECOMES DISORIENTED AND FLIES THE INCORRECT HDG AFTER RECEIVING A NEW ARR CLRNC DURING APCH INTO DFW.

Narrative: WE WERE FLYING THE BONHAM 4 ARR TO DFW, POSITIONED SOMEWHERE BTWN FIXES GLOVE AND ROBEY, WHEN ATC GAVE US AN ARR CHANGE TO THE WILBR 2. COPLT'S LEG, SO HE IMMEDIATELY STARTED LOOKING UP THE WILBR 2 IN HIS FLT MANUAL WHILE I STARTED PROGRAMMING THE FMS. WE WERE UNFAMILIAR WITH THE WILBR 2. SOON AFTER RECEIVING THE CLRNC, WE RECEIVED ANOTHER CLRNC TO CROSS ADDVL AT 11000 FT. THE COPLT AND I WERE A LITTLE CONFUSED ON THE CLRNC BECAUSE OF THE CTLR'S PRONUNCIATION OF ADDVL. WE WERE TRACKING THE 064 DEG RADIAL OFF BYP IN NAV TRACK AND STARTED OUR DSCNT IN ORDER TO MEET THE ALT RESTR. AFTER I PUT THE WILBR 2 IN THE BOX, WE NOTICED A MILEAGE DISPARITY BTWN RAW DATA AND THE NAV ON THE DISTANCE TO ADDVL. TRYING TO RESOLVE THIS DISPARITY, WE ENDED UP FLYING 1 DOT R OF THE 222 DEG INBOUND COURSE TO IT. IT SEEMED WE DID NOT HAVE ENOUGH TIME BTWN THE TIME WE WERE GIVEN THE CLRNC TO FIND THE ARR, SET IT UP, PROGRAM THE NAV AND FIGURE WHERE WE WERE RELATIVE TO IT BEFORE A CRITICAL COURSE CHANGE WAS REQUIRED. WE WERE ATTEMPTING TO CORRECT BACK ONTO COURSE WHEN THE ATC CTLR GAVE US A HDG OF 240 DEGS. THEN ANOTHER CTLR, POSSIBLY A SUPVR, QUESTIONED OUR COURSE AND SAID THAT WE HAD FLOWN THROUGH A 'JUMP ZONE.' AT THAT TIME, WE GOT A TCASII RA ALERT, HAD VISUAL CONTACT, AND A SMALL CIVIL ACFT FLEW OVER US 700 FT ABOVE. FROM THERE, THE CTLR GAVE US VECTORS TO AN UNEVENTFUL LNDG ON RWY 17C AT DFW. MULTIPLE FACTORS COULD HAVE LED TO THIS NAV ERROR. IT DEFINITELY TOOK US LONGER THAN EXPECTED TO SET UP FOR THIS ARR WHILE TRYING TO RESOLVE OUR CONFUSION WITH THE CLRNC AND THE NAV. ALSO WE HAD ATIS INFO AND THERE WAS NO MENTION ON THE ATIS, OR FROM THE CTLR ABOUT JUMP ZONE TFC IN THE VICINITY OF BYP. IN THE FUTURE, I WILL PUT MORE EMPHASIS ON FLYING RAW DATA. TRYING TO FLY THE NAV WITHOUT HAVING IT PROPERLY SET UP IS WHAT LED US OFF COURSE.

Data retrieved from NASA's ASRS site as of July 2007 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.