a memorial for all wars: the Polynational War Memorial
 

LIST OF WARS: DETAILS

Manchurian War

Also called: Second Sino-Japanese War

Years: 1931-1933
Battle deaths: 60,000 [1]

Nation(s) involved and/or conflict territory [note]
Japan, China

Published prior to 2013 | Altered: 2013-08-14 22:04:58
The Mukden Incident, also known as the Manchurian Incident, was a staged event engineered by Japanese military personnel as a pretext for invading the northern part of China, known as Manchuria, in 1931.

On September 18, 1931, a small quantity of dynamite was detonated by Lt. Kawamoto Suemori close to a railroad owned by Japan’s South Manchuria Railway near Mukden (now Shenyang). Although the explosion was so weak that it failed to destroy the lines and a train passed minutes later, the Imperial Japanese Army, accusing Chinese dissidents of the act, responded with a full invasion that led to the occupation of Manchuria, in which Japan established its puppet state of Manchukuo six months later. The ruse was soon exposed to the international community, leading Japan to diplomatic isolation and its March 1933 withdrawal from the League of Nations.

The actual event is known as the "Liutiaohu Incident" (simplified Chinese: 柳条湖事变; traditional Chinese: 柳條湖事變; pinyin: Liǔtiáohú Shìbiàn, Japanese: 柳条湖事件, Ryūjōko-jiken), and the event including its aftermath is known in Japan as the "Manchurian Incident" (Kyūjitai: 滿洲事變, Shinjitai: 満州事変, Manshū-jihen) and in China as the "September 18 Incident" (simplified Chinese: 九一八事变; traditional Chinese: 九一八事變; pinyin: Jiǔyībā Shìbiàn).

Source: Wikipedia, published under the GNU FDL. Retrieved [dat]

SOURCES: FATALITY DATA

Notes on fatalities

[1] Battle deaths: Correlates of War, Inter-State War Data v4.0

More about sources

NOTE ON NATION DATA

NOTE! Nation data for this war may be inconlusive or incomplete. In most cases it reflects which nations were involved with troops in this war, but in some it may instead reflect the contested territory.

UPDATES

Check if this section is being updated on the update page.

Back