Narrative:

Just passing mem; crew discovered that point KM360 was not correctly loaded into FMC route. Route was non-standard and manually typed into FMC on ground. Both pilots noted KM360 being loaded to route page; but neither verified correct route after route activation. Turns out that KM360 was not in database and had to be manually entered using latitude long. Crew received direct to vxv negating need to proceed to KM360. This mistake caused by crew not verifying route page two against filed clearance after route activation. Contributing factor was fix not being pre-programmed into database.

Google
 

Original NASA ASRS Text

Title: An air carrier crew manually loaded the FMS with a company non-standard route. Enroute ATC notified them about a track deviation because KM360 was not in the database. The crew did not verify the route against the clearance.

Narrative: Just passing MEM; crew discovered that point KM360 was not correctly loaded into FMC route. Route was non-standard and manually typed into FMC on ground. Both pilots noted KM360 being loaded to route page; but neither verified correct route after route activation. Turns out that KM360 was not in database and had to be manually entered using LAT LONG. Crew received direct to VXV negating need to proceed to KM360. This mistake caused by crew not verifying route page two against filed clearance after route activation. Contributing factor was fix not being pre-programmed into database.

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