Narrative:

ATC computers clear ord ZZZ flts via a fix that isn't on any map we have and apparently ATC doesn't have it either. We file ord rbs ZZZ but the computer replies with ord acito adell lukey ZZZ. When the controller saw that we were filed acito and adell he sounded shocked that we would be able to actually accept it. Of course I informed him that we indeed did not have adell but could accept acito. He got a little upset that we didn't let the clearance guy know. We told him about the previous week and how it was handled. The controller just cleared us back to rbs as expected and ZZZ. Last week we had the same error from the ATC computer. We attempted to fix it on the ground and they just said we would get direct rbs or lukey. This week we were busy and decided to fix the error in the air since it wasn't safety of flight and the previous week we never even got to those fixes above. We would always be in ATC radar coverage and could accept rv to either fix if need be. Or we could just go back to rbs and ZZZ as filed. I asked the controller for the latitude/longitudes of the adell fix but he didn't have them. I think it's an error in the ATC computer and doesn't exist. I was going to have an email issued or a message on the release that we sometimes get when we have strange fixes on our route. Since he didn't have that I sent a message to dispatch to have the canned flight plan amended to include remarks 'unable to accept routing over adell and/or acito.' that should take care of the problem till ATC fixes the routing in the computer. But this is the second week its been occurring so I'm not sure ATC can fix it.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN ACR CREW WAS CLRED TO WAYPOINTS AFTER DEP THAT DID NOT EXIST ON THE FMC DATABASE.

Narrative: ATC COMPUTERS CLR ORD ZZZ FLTS VIA A FIX THAT ISN'T ON ANY MAP WE HAVE AND APPARENTLY ATC DOESN'T HAVE IT EITHER. WE FILE ORD RBS ZZZ BUT THE COMPUTER REPLIES WITH ORD ACITO ADELL LUKEY ZZZ. WHEN THE CTLR SAW THAT WE WERE FILED ACITO AND ADELL HE SOUNDED SHOCKED THAT WE WOULD BE ABLE TO ACTUALLY ACCEPT IT. OF COURSE I INFORMED HIM THAT WE INDEED DID NOT HAVE ADELL BUT COULD ACCEPT ACITO. HE GOT A LITTLE UPSET THAT WE DIDN'T LET THE CLRNC GUY KNOW. WE TOLD HIM ABOUT THE PREVIOUS WEEK AND HOW IT WAS HANDLED. THE CTLR JUST CLRED US BACK TO RBS AS EXPECTED AND ZZZ. LAST WK WE HAD THE SAME ERROR FROM THE ATC COMPUTER. WE ATTEMPTED TO FIX IT ON THE GND AND THEY JUST SAID WE WOULD GET DIRECT RBS OR LUKEY. THIS WK WE WERE BUSY AND DECIDED TO FIX THE ERROR IN THE AIR SINCE IT WASN'T SAFETY OF FLT AND THE PREVIOUS WK WE NEVER EVEN GOT TO THOSE FIXES ABOVE. WE WOULD ALWAYS BE IN ATC RADAR COVERAGE AND COULD ACCEPT RV TO EITHER FIX IF NEED BE. OR WE COULD JUST GO BACK TO RBS AND ZZZ AS FILED. I ASKED THE CTLR FOR THE LAT/LONGITUDES OF THE ADELL FIX BUT HE DIDN'T HAVE THEM. I THINK IT'S AN ERROR IN THE ATC COMPUTER AND DOESN'T EXIST. I WAS GOING TO HAVE AN EMAIL ISSUED OR A MESSAGE ON THE RELEASE THAT WE SOMETIMES GET WHEN WE HAVE STRANGE FIXES ON OUR RTE. SINCE HE DIDN'T HAVE THAT I SENT A MESSAGE TO DISPATCH TO HAVE THE CANNED FLT PLAN AMENDED TO INCLUDE REMARKS 'UNABLE TO ACCEPT ROUTING OVER ADELL AND/OR ACITO.' THAT SHOULD TAKE CARE OF THE PROB TILL ATC FIXES THE ROUTING IN THE COMPUTER. BUT THIS IS THE SECOND WEEK ITS BEEN OCCURRING SO I'M NOT SURE ATC CAN FIX IT.

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