HDG TRACK DEV WHEN APCHING DEST WHILE B737-700 FLC IS USING THE WRONG ARR PROC INTO PHX; AZ.

Narrative

ARR DEV. ARR INTO PHX. CDU DEFAULT FOR RTE WAS BRUSR ARR; WHILE RELEASE USED MAHEM ARR. THE CAPT AND I FAILED TO DO PROPER XCHK. S OF DRAKE; CLRED TO CROSS BRUSR AT 250 KTS; 12000 FT. (THIS POINT IS ON BOTH THE BRUSR AND MAHEM ARRS; SO THIS CLRNC DID NOT KEY OUR MIND THAT WE WERE ON THE WRONG ARR.) WHILE ON A N DOWNWIND FOR PHX RWY 26 APCH QUERIED US AS TO WHICH ARR WE WERE ON AFTER STATING 'BRUSR' WE WERE ASKED TO CONTACT TRACON. WE OBVIOUSLY FAILED TO DO PROPER REVIEW OF DEFAULT CDU RTE VERSUS RELEASE RTE. THERE WERE NO CONFLICTS OR NEAR MISSES. RECOMMEND DIFFERENT ARRS USE DIFFERENT NAMES FOR POINTS. SUPPLEMENTAL INFO FROM ACN 545955: UPON FURTHER INVESTIGATION ON OUR PART; WE FOUND THAT IN ENTERING DATA IN THE RTE BOX GAVE US THE BRUSR ARR. WE DID NOT XCHK THIS BEFORE DEP AND WE OBVIOUSLY SHOULD HAVE. DURING DSCNT WE WERE CLRED TO CROSS BRUSR AT 12000 FT; 250 KTS -- NO MENTION OF THE MAYHEM ARR. I BELIEVE IT IS A MISTAKE TO NAME XING POINTS ON ONE ARR THE SAME NAME AS ANOTHER ARR. IT IS ALSO CONFUSING HAVING ARRS AND POINTS ON OTHER ARRS DESIGNATED THE SAME.