| Formed: | November 7, 1995 |
| Dissipated: | November 11, 1995 |
| Winds: | 65 |
| Pressure: | 978 |
| Winds: | 70 |
| Year: | 1995 |
| Fatalities: | 236 overall |
| Damage: | 46300000 |
| Areas: | India, Bangladesh, Nepal |
The 1995 India cyclone was a tropical cyclone that struck southeastern India which later spawned a rare snowstorm in Nepal, triggering the deadliest mountain trekking incident in the country's history in November 1995. The storm originated from the monsoon trough on November 7 in the Bay of Bengal, east of India, becoming the penultimate storm of the 1995 North Indian Ocean cyclone season. Moving northwestward, the system gradually intensified while moving toward land, eventually developing an eye in the middle of the convection. Reaching peak winds of at least 120abbr=onNaNabbr=on, the India Meteorological Department (IMD) classified the system as a very severe cyclonic storm on November 8, in line with intensity estimates from the American-based Joint Typhoon Warning Center (JTWC). On November 9, the cyclone made landfall near the border of Andhra Pradesh and Orissa. A typical for most November storms, the system continued to the north and dissipated over Nepal on November 11.
In India, the cyclone's strong winds were accompanied by heavy rainfall and a storm surge of 1.5m (04.9feet) that inundated the coastline several hundred feet inland. Power lines, crops, and houses were damaged, and many boats were damaged, causing several nautical fatalities. The cyclone killed at least 128 people in India, with hundreds remaining unaccounted for, and damage was estimated at RS$1.1 billion (US$32.2 million). In neighboring Bangladesh, high waves killed 45 people after sinking or sweeping away four ships. The cyclone later spawned a rare November snowstorm across eastern Nepal, with depths reaching 2000mm. The snowfall occurred without warning amid the busy mountain trekking season, and there were several avalanches and landslides across the country. One such incident killed 24 people at a lodge near Gokyo, and there were 63 deaths related to the cyclone in the country. The Nepal government launched the largest search and rescue mission in the country's history, rescuing 450 people, some of whom trapped for days in the snow.
In early November 1995, the monsoon trough was active across the Bay of Bengal, with several associated circulations. A disturbance near the Andaman Islands became the focus of the overall system on November 6. Located south of the subtropical ridge, the system moved to the west-northwest.[1] Based on the improved organization, the JTWC issued a Tropical Cyclone Formation Alert late on November 6, and at 00:00 UTC the next day initiated advisories on Tropical Cyclone 03B just west of the Andaman Islands.[2] Six hours later, the IMD likewise classified the system as a depression.[3]
After development, the depression steadily intensified while moving through the Bay of Bengal; rounding the ridge, it accelerated and turned more to the northwest. The IMD upgraded the system to a deep depression by 12:00 UTC on November 7, and further to a cyclonic storm by 00:00 UTC on the following day. The convection, or thunderstorms, organized into a comma-like structure, which further evolved into a central dense overcast.[3] Intensification was also aided by increased upper-level divergence or the increased upward movement of air.[1] At 09:00 UTC on November 8, the IMD upgraded the system to a severe cyclonic storm, and six hours later to a very severe cyclonic storm. By that time, an eye had developed, described by the IMD as a "banding-type eye". As such, the agency estimated peak 3 minutes sustained winds of 120abbr=onNaNabbr=on. The minimum barometric pressure was estimated at 978mbar.[3] The JTWC estimated slightly higher 1-minute winds of 130abbr=onNaNabbr=on.[2]
Around 05:00 UTC on November 9, the cyclone made landfall at peak intensity in eastern India, near the state borders of Andhra Pradesh and Odisha, and close to the city of Ichchapuram. Although the IMD officially estimated peak winds of 120abbr=onNaNabbr=on, winds could have been as high as 150abbr=onNaNabbr=on, based on the damage and estimates from the Dvorak technique. After moving ashore, the storm turned more to the north and rapidly weakened over land.[3] By 12:00 UTC on November 9, the JTWC discontinued advisories.[2] The storm weakened into a depression over the northern Bihar state early on November 10. On the next day, the system degenerated into a remnant low,[3] by which time the system had turned to the northeast and spread into Nepal. The circulation dissipated, although moisture and convection from the storm spread through Nepal.[2]
Moving ashore eastern India, the cyclone brought strong winds, with a peak gust of 115abbr=onNaNabbr=on at the Visakhapatnam Airport, well southwest of the landfall location. Winds in Gopalpur, Odisha were estimated at 130abbr=onNaNabbr=on. The lowest barometric pressure in India was 982.1mbar in Kalingapatnam. The storm produced a storm surge of 1.5m (04.9feet), which spread several hundred feet inland. In addition to the winds and surge, the cyclone dropped heavy rainfall along its path, particularly in Andhra Pradesh and Odisha, peaking at over 200 mm (8 in).[3]
Along the Indian coast from Andhra Pradesh to West Bengal, 2,688 boats were damaged, accounting for 48 fishermen deaths in Visakhapatnam alone.[3] An Indian Coast Guard ship was washed ashore near Bhubaneswar, trapping the crew inside until they were rescued.[4] In Andhra Pradesh, the high winds damaged 21km (13miles) of power lines, affecting 12,733 electrical units. The storm damaged 27,945 houses, mostly in Orissa.[3] In the state, the storm's high winds and rainfall wrecked stalls for a festival in Paradip, and raining out two days play of a Test cricket match in Cuttack between India and New Zealand.[5] [4] There was also widespread crop damage on 11043653ha of crop fields. In West Bengal, paddy crops, mustard trees, and potatoes were damaged. Throughout India, the cyclone killed 73 people, with 402 people missing after the storm.[3] The International Disaster Database indicated that the storm killed 128 people and caused US$46.3 million in damage.
Farther east, officials in Bangladesh evacuated residents along offshore islands, while boats were ordered to return to the coast.[6] The storm ultimately produced 60to winds along with heavy rainfall in the country.[7] High seas, reaching 18abbr=onNaNabbr=on in height, capsized a boat in the Chunkuri River and left three other boats missing, killing 45 people.[8] The waves also flooded about 3000ha of crop fields.[9]
Atypical for November, the storm continued northward and became the most intense cyclone to affect Nepal in the autumn in 50 years. The country's Department of Meteorology did not issue warnings for the storm, as no mountain trekking teams requested a forecast. As a result, many mountain climbers and guides were caught off guard, and thousands of mountaineers from around the world were in the region when the cyclone struck. When the energy from the storm spread into the Himalayan Mountains of Nepal,[2] a process known as orographic lift occurred, whereby the moisture coalesced in mountainous regions. At elevations generally below 3500m (11,500feet), the precipitation resulted in 50to of rainfall, reaching 220mm in Dhankuta. In some areas, totals were 3,000% of the average November rainfall, which is usually a dry month. At higher elevations, the precipitation caused intense snowfall, reaching up to 2000mm deep in Dingboche. Gorakshep recorded 1200mm of snowfall. The Khumbu region of eastern Nepal received rare snowfall, as it is normally part of a rain shadow. The village of Thame was buried for eight days until people could travel freely again; the rarity of the snowfall meant that residents did not have skis or snow shoes. By November 14, or five days after the arrival of the storm, the snow had receded.[10]
The heavy snowfall across Nepal produced landslides and avalanches,[2] mostly on November 10 and into the following day. Near Gokyo, two avalanches combined and destroyed a lodge housing 25 mountain climbers, killing all but one; the survivor was rescued after being trapped for 40 hours.[10] The hikers were climbing Gokyo Ri, a mountain 11abbr=onNaNabbr=on southeast of Mount Everest.[11] This marked the deadliest avalanche in Nepal to affect a hiking expedition.[12] Another avalanche killed seven people in Kangchenjunga.[10] With levels reaching as high as the roofs of houses,[12] the heavy snowfall damaged the roofs of several buildings, including one school, and killed about 100 animals. Across the country, the storm killed 63 people, 33 of them related to avalanches,[10] including 22 foreigners, although the Trekking Workers' Association believed the death toll was higher.[10] Several of the deaths were the result of collapsed houses,[13] while others were the result of people freezing to death.[14] The Mani Rimdu festival likely prevented additional deaths, as over 1,000 residents in the hardest hit areas left for the ceremony. After the snowfall, the Nepal government coordinated the largest search and rescue mission in the country's history, utilizing helicopters to rescue 450 stranded people,[10] encompassing an area of 600km2, before the mission was ended on November 15.[15] Several of the rescued people required medical attention.[10] Stranded victims had to stay in the snow for a day and a half before being spotted and rescued,[16] and inclement weather disrupted efforts.[13]