Narrative:

We were inbound to fll at FL240 proceeding direct to mrlin intersection. We were then cleared to cross mrlin at 7000 ft. Passing FL21.5 we were told to maintain FL200 for crossing traffic. After the traffic passed us I asked for further descent clearance. The controller cleared us to cross marlin at 7000 ft. Then he said he would make it easy on us and then cleared us to cross tritn intersection 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 south 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 flight planned the FMS to arrival at 7000 ft 5 mi south of mrlin. Approaching mrlin the controller asked if we were able to make the restr. We replied that we would and he told us we were over the tritn intersection. I replied that we still showed 2.4 mi to go to mrlin. He then said it was no problem but we should check our navigation. When we got on the ground I checked the position 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 north of its previous location and tritn was where mrlin used to be. Our problem actually occurred because we failed to recognize that the active data base in our FMS was not the current data base during the FMS preflight. Perhaps when they are considering moving the location of a fix they should consider changing the name as well. Supplemental information from acn 301560: to fix this problem I should have checked the data base even though the aircraft had been flown 3 times that day and it was near the middle of the month.

Google
 

Original NASA ASRS Text

Title: 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.

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.