MD-11 flight crew reported receiving an ATC clearance to the waypoint RUMSY; however; the FMS database indicated the nearest RUMSY waypoint was located beyond the aircraft's limits and in the wrong direction. ATC provided a vector and clearance to another waypoint.
Synopsis
MD-11 flight crew reported receiving an ATC clearance to the waypoint RUMSY; however; the FMS database indicated the nearest RUMSY waypoint was located beyond the aircraft's limits and in the wrong direction. ATC provided a vector and clearance to another waypoint.
Narrative
Our clearance from OAK to ZZZ was OAK5.OAK - GRTFL - ENI - FOT - BOXER - ZZZZZ - etc. On initial climb-out from OAK; we received a CPDLC message for a route change to go direct to RUMSY - BOXER - flight plan route. We acknowledged this message and then proceeded to load the RUMSY waypoint into the FMS. Upon entering the fix RUMSY; the only waypoint that showed up was one almost 6000 NM away from our present position. We initially turned towards that waypoint but quickly realized that something was amiss. The RUMSY we entered was well past BOXER. We returned back to the FMS and tried to find the correct waypoint using a couple of different methods to type it in the FMS to identify the correct fix; but the only one in the FMS database was almost 6000 NM away. Meanwhile; ATC queried us as to our direction of flight and we told them that we were heading to RUMSY; but that it did not appear to be the correct fix. ATC then gave us a heading in the right direction. Meanwhile; we finally looked up and found the intended RUMSY fix on our Jeppesen app; only about 25 NM from our present position. Because it was not in the FMS database; we notified ATC of this discrepancy and requested direct BOXER. After a short bit; ATC cleared us direct to BOXER and then flight plan route. A few minutes later; ATC queried us about the RUMSY waypoint and we explained to them that it was not in our database and that we would file a report on it when we landed. The remainder of the flight was flown without incident.The FMS did not have the intended RUMSY waypoint in the database. The only RUMSY in the box was almost 6000 NM away. The waypoint RUMSY; near OAK; needs to be added to the FMS database.
Second reporter narrative
Passing 10;000 ft; cleared direct to RUMSY and BOXER for traffic. FMS database RUMSY showed 6000 NM away. The RUMSY ATC cleared us to was approximately 60 NM from our position. As pilot flying; I selected autopilot and verified the correct RUMSY by searching iPad fixes. Pilot monitoring was working FMS and talking to ATC. We eventually were assigned a heading and then direct BOXER. We then told ATC about database discrepancy which included verification of the correct spelling; which we as a crew did correctly.[The cause was] ATC / FMS database error. Only thing I could suggest is ATC to know if MD-11s have historically been given this fix; query if it's in our nav database; or just give us a heading to avoid traffic.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.