US puts anti-ship missiles 62 miles from Taiwan for an 11-day exercise

Picture a sourcing lead whose boards come off a line in Taiwan. Before Keen Sword starts on Oct 19 ^[1], a VP forwards a link about US missiles near Taiwan and wants to know whether the supplier plan needs to change.

NMESIS is much closer this time. Yonaguni sits roughly 62 miles from Taiwan ^[17]. That is about 88 miles nearer than last year's Ishigaki spot ^[13], less than half the distance ^[14]. NMESIS carries Naval Strike Missiles that can engage ships beyond 115 miles ^[4]. At Ishigaki, the gap to Taiwan was longer than that stated figure. On Yonaguni, the figure exceeds the gap by about 53 miles ^[15]. Interesting Engineering, the outlet reporting the deployment, writes that this range lets a Yonaguni launcher threaten ships across a substantial area around the island and toward Taiwan ^[4].

The shape of the deployment matters as much as the distance. NMESIS is a remotely operated launcher on an unmanned vehicle ^[4], and this placement is tied to an exercise that runs 11 days, counting both ends ^[1][12]. It is the third NMESIS stop near Taiwan in the reporting, after Batanes and Ishigaki ^[16]. The US 2026 National Defense Strategy calls for strengthening a denial defense along the First Island Chain ^[10].

Some of the evidence points to a longer stay. Keen Sword will set up a joint coordination center at the Yonaguni garrison ^[6]. Japan's Ground Self-Defense Force has held that garrison since 2016 ^[9]. Tokyo plans more air-defense capability there in the coming years ^[11]. The reporting does not say whether any US hardware or the coordination center remains after Oct 29 ^[1], and it does not cover commercial shipping or supplier operations.

In my view, the 62-mile figure goes in the supplier risk log as a dated entry. On its own it is not enough to pull a second-source project forward. A rotation that follows a published strategy and repeats two earlier placements is the expected path ^[10][16]. The tradeoff is plain. If you wait for a standing deployment, you act after the signal is public. If you move now, you pay to qualify a supplier you may never use.

The forcing function I'd hand the VP has two axes. One is whether the hardware leaves when the exercise ends. The other is whether anything reaches your own line, such as a lead time your supplier quotes or a route your freight takes. If the hardware leaves and nothing reaches your line, log it and keep the plan. If it stays and nothing reaches your line, bring the second-source review into the next planning cycle. If your line moves while the deployment is still temporary, the first call goes to the supplier. If both happen, fund the dual source. On what has been published so far, Yonaguni goes in the first box.