Battle of Tokyo
For the battles depicted in Ace Combat: Joint Assault, see First Battle of Tokyo and Second Battle of Tokyo.
For the battles depicted in Ace Combat Infinity, see Operation Gambit and Operation Override.
The battle of Tokyo was an aerial skirmish between the Japan Self-Defense Forces and remnants of the New Russian Federation on September 15, 2018. The attack was the prelude to a greater bombing attack on Tokyo masterminded by the Blatnoi syndicate, but was foiled by the intervention of an F-3 Shinden II test squadron. The battle has been described as an experience for the Japanese people similar to the September 11 attacks on the United States.[1]
Overview of events
Sanriku tests
In the days prior to the battle, the JASDF conducted live fire tests of the Type 19 air-to-air missile, or AAM-7, using the ASF-X Shinden II FSD models. The tests had taken place smoothly, to the point where the missile was tested on unmanned drones a day before the attack. Immediately before the incident, an emergency situation simulacrum was taking place over the Sanriku Coast, which involved the four "-00" Shinden prototypes. All four units were armed with AAM-7 and AAM-5 missiles for emergencies, a decision triggered by the previous year's attack on Haneda.[2]
When the exercise concluded, the flight was preparing to return to Gifu when the base sent an emergency transmission, dispatching two F-15Js in response, while Misawa Air Base remained on standby. Likewise, the USAF dispatched F-16s to assess the situation. At 11:08AM, two A-50 Mainstay AEW aircraft of the Russian intruders covered their approach with electronic interference, causing televisions and mobile phones across the Kanto area to fail— the event was initially attributed to a solar wind event. However, the ASF-X unit retained communication thanks to the aircraft's fiber-optic systems. Later, at 11:24, a second group of bogies was detected approaching Tokyo from the Miura Peninsula.[2]
Attack on Tokyo
The lack of information on civilian aircraft caused by the loss of radar forced the Shindens to take a 200 km detour to Tokyo Bay through Hachijo Island. After arriving to the capital, the squadron's third member detected a formation of eight aircraft approaching from the Pacific side of Honshu, which included a number of A-50s escorted by Su-37K jets. Because of the loss of ground communication, the unit decided to split into two groups to make advantage of stealth. Using reconnaissance pods, the squadron discovered that the fighters were carrying iron bombs and ground attack missiles, suggesting an imminent attack on Tokyo.[2]
The jets approached the unit under X-02's lead, releasing their drop tanks in preparation for action. Initially, SDF policy on unknown targets caused the ASF-Xs to hold fire; however, a missile attack on ASF-X-02 caused them to retaliate. The skirmish between the Shindens and the Terminators was witnessed by many on the ground, who were unable to ascertain the situation on account of the vast combat airspace. In the middle of the fight, a burning Terminator crashed on a waterfront warehouse, causing a fire.[2]
Aftermath
At 11:44, the NRF aborted the attack on Tokyo. A fleet of Su-37s fled towards the Pacific, followed by the Mainstays, who dropped their jamming and followed them. The ASF-Xs were poised to pursue the escaping Russians, only for a fuel shortage to force them to return to Gifu Air Base. Meanwhile, the JSDF dispatched a fleet of F-15Js, EC-1 early warning aircraft and frigates to continue the mission. Meanwhile, the Defense Ministry officially announced the use of electronic countermeasures on Tokyo.[2]
The incident proved the combat reliability of the ASF-X Shinden II to the Japanese military, who went as far as describing a "generation gap" between it and the Su-37, and became the factor that caused the aircraft's formal entry to active service. In the other hand, the Tokyo skirmish proved a major victory for the JSDF in terms of radar-less engagements. While no aircraft were lost in the operation, one of the Shindens was damaged by cannon fire, but nonetheless remained operational.[2]