Narrative:

Clearance: cleared for the tandy 3 arrival to sna via the fellows VOR (flw) and cross merma at 14000 ft. The PF (sic) programmed the vertical navigation unit to provide a descent profile so as to meet the crossing restr. I failed to verify that the inputs were correct. About 4 mins prior to intersection and while descending from FL260, I began to review the ILS approach at our destination. Upon doing this, I contacted the airport FBO on our other VHF transceiver to alert them of our ETA. The sic (PF) continued to monitor ATC. I was distraction and was not paying attention to our progress. About 3 mi prior to merma, I had completed my tasks and returned to monitor ATC communication. We were now descending through FL200. It was at this point the controller asked 'north-number, are you going to make merma at 14000 ft?' 'negative' was my response. The sic deployed the air brakes and began a rapid descent. We leveled at 14000 ft, 7 mi past merma. There were no apparent traffic conflicts. The remainder of the flight was routine and uneventful. Upon landing we discussed the event. It turned out that the PF had not programmed the vertical navigation guidance unit properly. This particular arrival procedure begins at either the filmore VORTAC (fim) or the fellows VORTAC (flw). We had been cleared via the flw transition. Merma is 112 mi past flw. The PF, who incidentally has demonstrated over the last 6 months (since his employment) to be a particularly competent pilot with a good eye for detail, inadvertently programmed the vertical navigation unit to cross merma based on its distance from fim. This error went unnoticed by both of us until it was too late. Perhaps the fact that fellows and filmore sound alike and are very near to each other caused a subconscious mistaken identify of the proper VOR. Modern electronic navigation computers are nice, however, they are only as good as the data that's input. Verifying inputs and using basic rules of thumb to check reasonableness of guidance information are still necessary. This, along with distraction and complacency on my part, contributed to this error.

Google
 

Original NASA ASRS Text

Title: AN ATX LTT FLC MISREFS A XING POINT DURING A STAR TO SNA. THEY WERE TOO HIGH AT MERMA. NO CONFLICT.

Narrative: CLRNC: CLRED FOR THE TANDY 3 ARR TO SNA VIA THE FELLOWS VOR (FLW) AND CROSS MERMA AT 14000 FT. THE PF (SIC) PROGRAMMED THE VERT NAV UNIT TO PROVIDE A DSCNT PROFILE SO AS TO MEET THE XING RESTR. I FAILED TO VERIFY THAT THE INPUTS WERE CORRECT. ABOUT 4 MINS PRIOR TO INTXN AND WHILE DSNDING FROM FL260, I BEGAN TO REVIEW THE ILS APCH AT OUR DEST. UPON DOING THIS, I CONTACTED THE ARPT FBO ON OUR OTHER VHF TRANSCEIVER TO ALERT THEM OF OUR ETA. THE SIC (PF) CONTINUED TO MONITOR ATC. I WAS DISTR AND WAS NOT PAYING ATTN TO OUR PROGRESS. ABOUT 3 MI PRIOR TO MERMA, I HAD COMPLETED MY TASKS AND RETURNED TO MONITOR ATC COM. WE WERE NOW DSNDING THROUGH FL200. IT WAS AT THIS POINT THE CTLR ASKED 'N-NUMBER, ARE YOU GOING TO MAKE MERMA AT 14000 FT?' 'NEGATIVE' WAS MY RESPONSE. THE SIC DEPLOYED THE AIR BRAKES AND BEGAN A RAPID DSCNT. WE LEVELED AT 14000 FT, 7 MI PAST MERMA. THERE WERE NO APPARENT TFC CONFLICTS. THE REMAINDER OF THE FLT WAS ROUTINE AND UNEVENTFUL. UPON LNDG WE DISCUSSED THE EVENT. IT TURNED OUT THAT THE PF HAD NOT PROGRAMMED THE VERT NAV GUIDANCE UNIT PROPERLY. THIS PARTICULAR ARR PROC BEGINS AT EITHER THE FILMORE VORTAC (FIM) OR THE FELLOWS VORTAC (FLW). WE HAD BEEN CLRED VIA THE FLW TRANSITION. MERMA IS 112 MI PAST FLW. THE PF, WHO INCIDENTALLY HAS DEMONSTRATED OVER THE LAST 6 MONTHS (SINCE HIS EMPLOYMENT) TO BE A PARTICULARLY COMPETENT PLT WITH A GOOD EYE FOR DETAIL, INADVERTENTLY PROGRAMMED THE VERT NAV UNIT TO CROSS MERMA BASED ON ITS DISTANCE FROM FIM. THIS ERROR WENT UNNOTICED BY BOTH OF US UNTIL IT WAS TOO LATE. PERHAPS THE FACT THAT FELLOWS AND FILMORE SOUND ALIKE AND ARE VERY NEAR TO EACH OTHER CAUSED A SUBCONSCIOUS MISTAKEN IDENT OF THE PROPER VOR. MODERN ELECTRONIC NAV COMPUTERS ARE NICE, HOWEVER, THEY ARE ONLY AS GOOD AS THE DATA THAT'S INPUT. VERIFYING INPUTS AND USING BASIC RULES OF THUMB TO CHK REASONABLENESS OF GUIDANCE INFO ARE STILL NECESSARY. THIS, ALONG WITH DISTR AND COMPLACENCY ON MY PART, CONTRIBUTED TO THIS ERROR.

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.