Narrative:

Location: approximately 35 southwest of grd VORTAC when I loaded the FMS manually with the flight plan, I did not load the grd VORTAC into the unarm arrival into clt. Therefore neither I, the PNF, nor the PF caught it going direct to unarm intersection from atl VORTAC, which would have bypassed grd. As we were trying to figure this out, ZTL asked if we were going to grd. I replied we were going to unarm intersection on arrival. We were then cleared to grd, and cross it at FL240, and we did so. No other aircraft were observed near us at our flight level on the TCASII or visually. The controller also did not mention any problems or conflicts. This illustrates the need to check, check, and rechk the data in the FMS and highlights a new one for me, that even if the lines connect, that it is not necessarily correct with the published data.

Related reports:

Google
 

Original NASA ASRS Text

Title: NAV ERROR OCCURS WHEN FLC FAILS TO PROPERLY LOAD A MANUAL FLT PLAN INTO THEIR FMS.

Narrative: LOCATION: APPROX 35 SW OF GRD VORTAC WHEN I LOADED THE FMS MANUALLY WITH THE FLT PLAN, I DID NOT LOAD THE GRD VORTAC INTO THE UNARM ARR INTO CLT. THEREFORE NEITHER I, THE PNF, NOR THE PF CAUGHT IT GOING DIRECT TO UNARM INTXN FROM ATL VORTAC, WHICH WOULD HAVE BYPASSED GRD. AS WE WERE TRYING TO FIGURE THIS OUT, ZTL ASKED IF WE WERE GOING TO GRD. I REPLIED WE WERE GOING TO UNARM INTXN ON ARR. WE WERE THEN CLRED TO GRD, AND CROSS IT AT FL240, AND WE DID SO. NO OTHER ACFT WERE OBSERVED NEAR US AT OUR FLT LEVEL ON THE TCASII OR VISUALLY. THE CTLR ALSO DID NOT MENTION ANY PROBS OR CONFLICTS. THIS ILLUSTRATES THE NEED TO CHK, CHK, AND RECHK THE DATA IN THE FMS AND HIGHLIGHTS A NEW ONE FOR ME, THAT EVEN IF THE LINES CONNECT, THAT IT IS NOT NECESSARILY CORRECT WITH THE PUBLISHED DATA.

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.