Narrative:

Upon descent and transition from ARTCC to approach; we requested the RNAV (rnp) 30 approach. The approach controller cleared us from our present position (approximately 40 miles southeast of the field) to rokny. We referenced the approach chart and saw ronky as the IAF from which we planned to commence our approach. We didn't catch the fact that when controller pronounced rokny that it differed from what we saw on the approach plate - ronky. Because the FMC was presently sequenced to the mso VOR (our cleared/planned route); rokny was not an available option listed when the pilot monitoring (pm) pressed the dir button; so pm hand typed ronky into the dir to field. The temperature INS orange dashed line showed a turn to 180 degrees magnetic which obviously didn't make sense. We queried the controller as to the spelling of the waypoint; at which time controller phonetically spelled r-o-K-north-Y. The pm had trouble initially inserting this correctly as he was mentally convinced that it was what he was reading on the approach plate (ronky). I mentioned that the controller spelled it rokny; at which time we inserted the correct waypoint and verified it on the nd. We cleaned up and verified the flight plan in the FMC and executed the approach from the rokny IAF and landed without incident. Upon landing; I called the duty phone and got a hold of the chief pilot. I relayed what had happened and conveyed my concerns for the next crew who might be flying into mso using that approach/IAF. Coincidentally; an employee of jeppesen heard about this event and contacted me so they are likely aware of the error. The approach plate is mso 12-21 dated 18 may 18. I verified this against the nga (national geospatial agency) product; which shows the waypoint correctly spelled rokny.suggestions: create process to validate all waypoints/coordinates in our jeppesen products.

Google
 

Original NASA ASRS Text

Title: Air carrier First Officer reported that while on the MSO RNAV Runway 30 approach; it was discovered the waypoint ROKNY is misspelled as RONKY on the Jeppesen chart.

Narrative: Upon descent and transition from ARTCC to Approach; we requested the RNAV (RNP) 30 approach. The approach controller cleared us from our present position (approximately 40 miles southeast of the field) to ROKNY. We referenced the approach chart and saw RONKY as the IAF from which we planned to commence our approach. We didn't catch the fact that when controller pronounced ROKNY that it differed from what we saw on the approach plate - RONKY. Because the FMC was presently sequenced to the MSO VOR (our cleared/planned route); ROKNY was not an available option listed when the Pilot Monitoring (PM) pressed the DIR button; so PM hand typed RONKY into the DIR TO field. The TEMP INS orange dashed line showed a turn to 180 degrees magnetic which obviously didn't make sense. We queried the controller as to the spelling of the waypoint; at which time controller phonetically spelled R-O-K-N-Y. The PM had trouble initially inserting this correctly as he was mentally convinced that it was what he was reading on the approach plate (RONKY). I mentioned that the controller spelled it ROKNY; at which time we inserted the correct waypoint and verified it on the ND. We cleaned up and verified the flight plan in the FMC and executed the approach from the ROKNY IAF and landed without incident. Upon landing; I called the duty phone and got a hold of the chief pilot. I relayed what had happened and conveyed my concerns for the next crew who might be flying into MSO using that approach/IAF. Coincidentally; an employee of Jeppesen heard about this event and contacted me so they are likely aware of the error. The approach plate is MSO 12-21 dated 18 May 18. I verified this against the NGA (National Geospatial Agency) product; which shows the waypoint correctly spelled ROKNY.Suggestions: Create process to validate all waypoints/coordinates in our Jeppesen products.

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.