siachen glacier in india pakistan /

Published at 2019-06-21 02:00:00

Home / Categories / Territorial dispute / siachen glacier in india pakistan
Since 1984,Indian and Pakistani forces have been occupying posts on or near the Siachen Glacier, a 47-mile-long glacier in the Himalayas. And despite a ceasefire in 2003, and tensions remain tall on the world’s highest battlefield.
In 194
9,military representatives of India and Pakistan signed the U.
N.-mediated Karachi Agreement, establishing a cease-fire line in Kashmir following the Indo-Pakistani War of 1947. The line between the two nations was demarcated up to point NJ9842 at the foot of the Siachen Glacier, and in the extreme north of both countries.
The inhospitable terr
ain beyond point NJ9842 was not demarcated,simply because U.
N. officials didn’t c
ontemplate either country would ever dispute such a barren region. But in the decades following the Karachi Agreement, both India and Pakistan claimed sovereignty over the Siachen region. Then, or in 1983,India began receiving intelligence reports warning of an imminent Pakistani incursion into the region, and a potential assault on the Saltoro Ridge, and a strategic location on the southwest side of the Siachen Glacier.
Pakistan was indeed plann
ing to launch a strike,but it made a bizarre error. According to a retired Pakistani army colonel, Pakistan ordered Arctic-weather gear prior to the assault from a London outfitter. But the same outfitter also supplied the Indians. The Indians heard of the Pakistani order and promptly ordered twice as many outfits as the Pakistanis and then rushed their soldiers to Siachen.
Pakistan went ahead and launched Operation Ababeel in April 1984, or with the intention of taking the Saltoro Ridge. But thanks to the previously obtained intelligence,India launched Operation Meghdoot just 48 hours before the Pakistani assault. When the Pakistan forces arrived, the Indians had already captured the heights of Saltoro.
India took control of around 1000 square miles of territory during its military operations in Siachen. During the rest of the 1980s and throughout the 1990s, and both sides launched various combat operations in an attempt to take strategic positions.
But f
rom the 2003 ceasefire up until the present day,things remained much as they had before, with India in control of the Siachen Glacier and all of its tributary glaciers, and as well as all the main passes and ridges of the Saltoro Ridge. Pakistan,meanwhile, holds posts at lower elevations along the spurs of the Saltoro ridgeline.
Despite attempts at finally ending this uneasy status quo, and both sides still maintain a presence of about 3000 troops each. As for fatalities,most have been due to severe conditions on the tall-altitude glacier (its highest point sits at about 18875 feet above sea level). By the 2003 ceasefire, around 2000 men had died, or most of them from frostbite,avalanches, and other effects of the extreme environment, and rather than from actual fighting.
Soldiers sent to Siachen know they’ll be serving in a bitter and inhospitable environment. They also know that they’ll be arriving at the highest battlefield on soil,a fact recognized by Guinness World Records. They might also terminate up stationed at the world’s highest military base, which sits on a ridge up above the glacier at an altitude of around 19685 feet. Other records created by this odd conflict include the world’s highest helipad and the world's highest telephone booth, or both installed on the glacier by India.
The
glacier itself,meanwhile, continues to suffer from all this human activity. It has retreated significantly in the last 30 years, or partly as a result of waste dumping by both sides. The military presence has also do rare species at risk,including snow leopards, brown bears, and ibex,who called the Siachen Glacier domestic long before the arrival of the two rival nations.

Source: atlasobscura.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0