A FLC FAILED TO COMPLY WITH A XING RESTR ATTRIBUTING AN FMS OUTDATED REVISION AND AN INTXN'S RELOCATION; AS THE CAUSE.

Narrative

WE WERE INBOUND TO FLL AT FL240 PROCEEDING DIRECT TO MRLIN INTXN. WE WERE THEN CLRED TO CROSS MRLIN AT 7000 FT. PASSING FL21.5 WE WERE TOLD TO MAINTAIN FL200 FOR XING TFC. AFTER THE TFC PASSED US I ASKED FOR FURTHER DSCNT CLRNC. THE CTLR CLRED US TO CROSS MARLIN AT 7000 FT. THEN HE SAID HE WOULD MAKE IT EASY ON US AND THEN CLRED US TO CROSS TRITN INTXN AT 7000 FT. WE LOOK AT OUR LEGS PAGE ON THE FMS AND DID NOT FIND TRITN. WE LOCATED IT ON THE FLL 10-2B STAR AND SAW THAT IT WAS 5 NM S OF MRLIN. WE THEN LOOKED AT THE ACTIVE DATA BASE IN OUR FMS AND DISCOVERED THAT THE ACTIVE DATA BASE WAS NOT THE CURRENT DATA BASE WHICH EXPLAINED WHY TRITN WAS NOT ON OUR LEGS PAGE. WE FLT PLANNED THE FMS TO ARR AT 7000 FT 5 MI S OF MRLIN. APCHING MRLIN THE CTLR ASKED IF WE WERE ABLE TO MAKE THE RESTR. WE REPLIED THAT WE WOULD AND HE TOLD US WE WERE OVER THE TRITN INTXN. I REPLIED THAT WE STILL SHOWED 2.4 MI TO GO TO MRLIN. HE THEN SAID IT WAS NO PROB BUT WE SHOULD CHK OUR NAV. WHEN WE GOT ON THE GND I CHKED THE POS OF MRLIN IN THE OLD DATA BASE AND COMPARED IT TO THE LOCATION IN THE CURRENT DATA BASE. THAT WAS WHEN I DISCOVERED THAT MRLIN WAS NOW ABOUT 5 MI N OF ITS PREVIOUS LOCATION AND TRITN WAS WHERE MRLIN USED TO BE. OUR PROB ACTUALLY OCCURRED BECAUSE WE FAILED TO RECOGNIZE THAT THE ACTIVE DATA BASE IN OUR FMS WAS NOT THE CURRENT DATA BASE DURING THE FMS PREFLT. PERHAPS WHEN THEY ARE CONSIDERING MOVING THE LOCATION OF A FIX THEY SHOULD CONSIDER CHANGING THE NAME AS WELL. SUPPLEMENTAL INFO FROM ACN 301560: TO FIX THIS PROB I SHOULD HAVE CHKED THE DATA BASE EVEN THOUGH THE ACFT HAD BEEN FLOWN 3 TIMES THAT DAY AND IT WAS NEAR THE MIDDLE OF THE MONTH.