North Korea confirmed that the ballistic missile it launched over Japan on Tuesday morning was indeed a KN17/Hwasong-12 intermediate-range ballistic missile as suspected. It released video footage of the launch, as per usual. (You can watch the launch here.)
Images released by North Korea’s Korea Central News Agency (KCNA) showed that little had changed physically about this missile since we first saw it fly successfully in May 2017. (North Korea had attempted three flight tests in April—all of which failed.)
As is common, one of the images released by KCNA showed North Korean leader Kim Jong-un sitting with a map that was just visible enough and high resolution enough for open source analysts to scrutinize it for a better idea of what the intended trajectory of the launch may have been.Enjoying this article? Click here to subscribe for full access. Just $5 a month.
One such analysis, published by Marco Langbroek on his blog, suggests that the observed range of the missile on Tuesday morning—2,700 kilometers per U.S. and Japanese intelligence—may have been far shorter than what North Korea intended. Langbroek’s georeferencing of the map (shown below) makes this point obvious.
There are two conclusions that may be drawn from this analysis. North Korea’s missile either did not perform to spec during the test or the map Kim Jong-un was given is not a reliable indicator of the actual trajectory sought during the flight test.
Previous tests where maps have been visible for scrutiny have revealed similar discrepancies. (Notably, a map of North Korea’s first intercontinental-range ballistic missile flight in July showed a splashdown point that likely was not the actual point of impact for its reentry vehicle.)
More evidence in the coming days and weeks about this launch should help formulate a better assessment about what North Korea was seeking to observe technically from what is, to date, it’s longest-range flight of a ballistic missile.
One data point shared with me by a U.S. government source with access to the latest intelligence on North Korea’s ballistic missile programs is that the burn time—or powered flight time—of the August 29 test was much shorter than the May test.
The August 29 missile burned its engines for 110 seconds—much shorter than the 139 seconds observed during the first-ever successful flight of the KN17, which took the missile to an apogee of 2,811 kilometers.
The short burn time confirms that North Korea cut the missile’s engines early during this test or experienced an unplanned engine shutoff, shortening the trajectory from a longer one. A longer trajectory, of course, would have had the added political benefit of showing that the KN17 is indeed capable of striking ranges as far as Guam—North Korea’s highest-value Pacific military target for now.
There may have been much more going on with this test as well. One analysis from Mike Elleman speculates as to the possibility that North Korea piloted use of a post-boost vehicle with the KN17. North Korea may have also fired the August 29 missile at a depressed trajectory—a possible contributor to the observed trajectory.
As a closing note, it looks increasingly like Pyongyang deliberately chose a trajectory that would overfly Japan while minimizing the actual risk posed to Japanese territory. It appears, for example, that the overflight of Hokkaido transpired with the missile well into the midcourse phase of flight, when its altitude was well in exoatmospheric ranges.
Moreover, the azimuth meant that the missile likely flew over the Tsugaru Strait, which separates Hokkaido from Honshu. The most populous Japanese city to have faced direct risk from the missile, had it failed in midcourse, would have been Hakodate. Either way, it’s not difficult to imagine a trajectory that would have put far more Japanese territory directly underneath the path of this missile.
It’s worth recalling too that despite this test easily being the most provocative North Korean ballistic missile launch ever, the core purpose wasn’t to prod and provoke Japan. I take a look at the probable logic behind this launch in a recent article for The Atlantic.