Narrative:

While on the mirok 1 arrival into las vegas, after leaving mirok awaiting radar vectors we were asked by approach to confirm we were on the lynsy 2 arrival. I replied we were on the mirok 1. We were then given heading 360 degrees and dscnd to 8000 ft and handed off to the final controller. After landing, we were requested to call the TRACON. I discussed this with the TRACON and was asked if we had been cleared via the lynsy arrival. I remembered being cleared direct lynsy by ZLA but not the lynsy RNAV arrival nor did I recall reading that back. The TRACON indicated they had been having problems with the RNAV arrival. Upon reflection at the hotel I recalled the readback by me as cleared direct lynsy and the arrival. I heard the mirok arrival but did not include it in my readback. To prevent this in the future I recommend the following: 1) full readback of clrncs by myself. 2) file and clear us via the RNAV arrs with our initial ATC clearance (pre departure clearance). 3) use the phrase 'new arrival, now cleared' -- similar to when flying into lax -- allowing time to set up the new arrival (ie, mitts versus civet). 4) name arrs so they are not easily confused. Both lynsy and mirok are on both arrs. Name the RNAV arrival with a distinctive intersection only applicable to itself such as utare, which is only on the lynsy RNAV 2. 5) delay putting the arrival into the FMC. Our initial ATC clearance at dfw included the mirok 1 and we had that in our plans and loaded in the FMC. 6) this flight was after an all nighter to mia -- sleep during the day and 2 legs mia-dfw-las. Despite our sleep planning, fatigue played a role.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN ACR B757-200 CREW FLIES THE MIROK 1 ARR INSTEAD OF THE LYNSY RNAV 2 ARR TO LAS, NV, UNTIL QUESTIONED BY THE APCH CTLR.

Narrative: WHILE ON THE MIROK 1 ARR INTO LAS VEGAS, AFTER LEAVING MIROK AWAITING RADAR VECTORS WE WERE ASKED BY APCH TO CONFIRM WE WERE ON THE LYNSY 2 ARR. I REPLIED WE WERE ON THE MIROK 1. WE WERE THEN GIVEN HDG 360 DEGS AND DSCND TO 8000 FT AND HANDED OFF TO THE FINAL CTLR. AFTER LNDG, WE WERE REQUESTED TO CALL THE TRACON. I DISCUSSED THIS WITH THE TRACON AND WAS ASKED IF WE HAD BEEN CLRED VIA THE LYNSY ARR. I REMEMBERED BEING CLRED DIRECT LYNSY BY ZLA BUT NOT THE LYNSY RNAV ARR NOR DID I RECALL READING THAT BACK. THE TRACON INDICATED THEY HAD BEEN HAVING PROBS WITH THE RNAV ARR. UPON REFLECTION AT THE HOTEL I RECALLED THE READBACK BY ME AS CLRED DIRECT LYNSY AND THE ARR. I HEARD THE MIROK ARR BUT DID NOT INCLUDE IT IN MY READBACK. TO PREVENT THIS IN THE FUTURE I RECOMMEND THE FOLLOWING: 1) FULL READBACK OF CLRNCS BY MYSELF. 2) FILE AND CLR US VIA THE RNAV ARRS WITH OUR INITIAL ATC CLRNC (PDC). 3) USE THE PHRASE 'NEW ARR, NOW CLRED' -- SIMILAR TO WHEN FLYING INTO LAX -- ALLOWING TIME TO SET UP THE NEW ARR (IE, MITTS VERSUS CIVET). 4) NAME ARRS SO THEY ARE NOT EASILY CONFUSED. BOTH LYNSY AND MIROK ARE ON BOTH ARRS. NAME THE RNAV ARR WITH A DISTINCTIVE INTXN ONLY APPLICABLE TO ITSELF SUCH AS UTARE, WHICH IS ONLY ON THE LYNSY RNAV 2. 5) DELAY PUTTING THE ARR INTO THE FMC. OUR INITIAL ATC CLRNC AT DFW INCLUDED THE MIROK 1 AND WE HAD THAT IN OUR PLANS AND LOADED IN THE FMC. 6) THIS FLT WAS AFTER AN ALL NIGHTER TO MIA -- SLEEP DURING THE DAY AND 2 LEGS MIA-DFW-LAS. DESPITE OUR SLEEP PLANNING, FATIGUE PLAYED A ROLE.

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.