1995 India cyclone

Map plotting the storm's track and intensity, according to the Saffir–Simpson scale

Map key

Saffir–Simpson scale

  Tropical depression (≤38 mph, ≤62 km/h)
  Tropical storm (39–73 mph, 63–118 km/h)
  Category 1 (74–95 mph, 119–153 km/h)
  Category 2 (96–110 mph, 154–177 km/h)
  Category 3 (111–129 mph, 178–208 km/h)
  Category 4 (130–156 mph, 209–251 km/h)
  Category 5 (≥157 mph, ≥252 km/h)
  Unknown

Storm type

Tropical cyclone

Subtropical cyclone

Extratropical cyclone, remnant low, tropical disturbance, or monsoon depression

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.[3] 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.[4] Six hours later, the IMD likewise classified the system as a depression.[5]

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.[5] Intensification was also aided by increased upper-level divergence or the increased upward movement of air.[3] 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 120 km/h (75 mph). The minimum barometric pressure was estimated at 978 mbar (28.9 inHg).[5] The JTWC estimated slightly higher 1-minute winds of 130 km/h (80 mph).[4]

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 120 km/h (75 mph), winds could have been as high as 150 km/h (95 mph), 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.[5] By 12:00 UTC on November 9, the JTWC discontinued advisories.[4] 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,[5] 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.[4]

Gokyo

Location in Nepal where avalanche occurred

Moving ashore eastern India, the cyclone brought strong winds, with a peak gust of 115 km/h (70 mph) at the Visakhapatnam Airport, well southwest of the landfall location. Winds in Gopalpur, Odisha were estimated at 130 km/h (80 mph). The lowest barometric pressure in India was 982.1 mbar (29.00 inHg) in Kalingapatnam. The storm produced a storm surge of 1.5 m (4.9 ft), 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).[5]

Along the Indian coast from Andhra Pradesh to West Bengal, 2,688 boats were damaged, accounting for 48 fishermen deaths in Visakhapatnam alone.[5] An Indian Coast Guard ship was washed ashore near Bhubaneswar, trapping the crew inside until they were rescued.[6] In Andhra Pradesh, the high winds damaged 21 km (13 mi) of power lines, affecting 12,733 electrical units. The storm damaged 27,945 houses, mostly in Orissa.[5] 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.[7][6] There was also widespread crop damage on 11,043,653 ha (27,289,460 acres) 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.[5] The International Disaster Database indicated that the storm killed 128 people and caused US$46.3 million in damage.[8]

Farther east, officials in Bangladesh evacuated residents along offshore islands, while boats were ordered to return to the coast.[9] The storm ultimately produced 60 to 80 km/h (37 to 50 mph) winds along with heavy rainfall in the country.[10] High seas, reaching 5.5 m (18 ft) in height, capsized a boat in the Chunkuri River and left three other boats missing, killing 45 people.[11] The waves also flooded about 3,000 ha (7,400 acres) of crop fields.[12]

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,[13] as no mountain trekking teams requested a forecast.[14] As a result, many mountain climbers and guides were caught off guard,[15] and thousands of mountaineers from around the world were in the region when the cyclone struck.[14] When the energy from the storm spread into the Himalayan Mountains of Nepal,[4] a process known as orographic lift occurred, whereby the moisture coalesced in mountainous regions. At elevations generally below 3,500 m (11,500 ft), the precipitation resulted in 50 to 200 mm (2.0 to 7.9 in) of rainfall, reaching 220 mm (8.7 in) in Dhankuta. In some areas, totals were 3,000% of the average November rainfall, which is usually a dry month.[13] At higher elevations, the precipitation caused intense snowfall, reaching up to 2,000 mm (79 in) deep in Dingboche.[13] Gorakshep recorded 1,200 mm (47 in) of snowfall.[16] 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.[13]

The heavy snowfall across Nepal produced landslides and avalanches,[4] 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.[13] The hikers were climbing Gokyo Ri, a mountain 18 km (11 mi) southeast of Mount Everest.[17] This marked the deadliest avalanche in Nepal to affect a hiking expedition.[18] Another avalanche killed seven people in Kangchenjunga.[13] With levels reaching as high as the roofs of houses,[18] 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,[13] including 22 foreigners,[16] although the Trekking Workers' Association believed the death toll was higher.[13] Several of the deaths were the result of collapsed houses,[15] while others were the result of people freezing to death.[16] 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,[13] encompassing an area of 600 km² (230 sq mi), before the mission was ended on November 15.[14] Several of the rescued people required medical attention.[13] Stranded victims had to stay in the snow for a day and a half before being spotted and rescued,[19] and inclement weather disrupted efforts.[15]

• Cyclone Hudhud – powerful cyclone in 2014 that also spawned snowfall and deadly avalanches in Nepal