| Extremely Severe Cyclonic Storm Nilofar | |
| Formed: | October 25, 2014 |
| Dissipated: | October 31, 2014 |
| Winds: | 110 |
| Pressure: | 950 |
| Winds: | 115 |
| Pressure: | 937 |
| Fatalities: | 4 total |
| Damages: | Minimal |
| Areas: | Oman, India, Pakistan |
Extremely Severe Cyclonic Storm Nilofar was, at the time, the third-strongest cyclone in the Arabian Sea. In late October 2014, it reached peak maximum sustained winds estimated between 110kn and 115kn. The India Meteorological Department (IMD) named it Nilofar; the name refers to the water lily, and was suggested by Pakistan.[1] The western fringes of the storm caused flash flooding in northeastern Oman, killing four people.
Nilofar originated from a low-pressure area between India and the Arabian Peninsula. It developed into a depression on October 25 and moved generally northward through an area of favorable conditions. The system intensified into a cyclonic storm on October 26. Quickly organizing due to the conditions, Nilofar developed a well-defined eye and structure, attaining its peak intensity on October 28. At the time, Nilofar was expected to make landfall in western India, prompting evacuations and preparations. However, high wind shear caused the storm to rapidly weaken, and Nilofar degraded into a remnant low-pressure area on October 31 off the Indian state of Gujarat.
Toward the middle of October 2014, the monsoon trough was active over the Arabian Sea off the west coast of India. A circulation formed on October 19 near the Lakshadweep archipelago, remaining nearly stationary for several days. It developed a distinct low-pressure area on October 21,[2] and produced an intense area of convection by the next day. Despite moderate wind shear, conditions favored further development, including warm water temperatures and good outflow,[3] amplified by an anticyclone to its east-northeast.[2] The structure became more organized by October 24, when broken rainbands were rotating around a poorly-defined circulation.[4] That day, the American-based Joint Typhoon Warning Center (JTWC) classified it as a tropical depression, although the agency did not issue warnings at the time.[5] At 00:00 UTC on October 25, the India Meteorological Department (IMD) classified the system as a depression about 1270 km (790 mi) southeast of Muscat, Oman.[2]
When the system first formed, it benefited from warm water temperatures of 28to and a favorable phase of the Madden–Julian oscillation. Moderate wind shear and continued interaction with the monsoon dislocated the bulk of the deepest convection to the western periphery.[2] By 12:00 UTC on October 25, the system organized enough for the JTWC to classify it as Tropical Cyclone 04A, and there were hints of an eye feature within the thunderstorms. By the time of classification, the storm was moving to the northeast, steered by the subtropical ridge to the south,[6] although the motion slowed on October 26 due to competing influence of another subtropical ridge to the northwest.[7] That day, the system strengthened quickly; the IMD upgraded the depression to a deep depression at 03:00 UTC, to Cyclonic Storm Nilofar at 06:00 UTC, and further to a severe cyclonic storm at 21:00 UTC.[2] At 00:00 UTC on October 27, the JTWC upgraded Nilofar to the equivalent of a minimal hurricane, based on the development of a 54 km (33 mi) eye.[8] Throughout that day, the cyclone turned more to the northwest as a ridge built to the east, while the inner core of convection became more symmetrical and compact. Also by that time, tropical cyclone forecast models anticipated that Nilofar would eventually recurve to the northeast and make landfall in western India.[9]
At 06:00 UTC on October 27, the IMD upgraded Nilofar to a very severe cyclonic storm. The storm was rapidly intensifying at the time, after the wind shear had decreased,[2] and the eye contracted to a diameter of 19 km (12 mi).[10] At 09:00 UTC on October 28, the IMD upgraded Nilofar further to an extremely severe cyclonic storm.[2] Six hours later, the JTWC estimated peak 1-minute winds of 115kn;[5] at the time, the agency anticipated further strengthening due to the favorable conditions and good organization.[11] At 18:00 UTC on October 28, the IMD estimated peak 3-minute winds of 110kn.[2] At the time, it was the third-strongest storm on record in the Arabian Sea.[12] On October 29, Nilofar started weakening due to increased wind shear, and the convection diminished in intensity.[13] At the same time, the storm turned northeastward while rounding the ridge to the east.[14] Increasingly cooler and drier air, as well as cooler waters, caused the storm to degrade rapidly.[2] The eye, previously small and well defined, dissipated by 06:00 UTC on October 29.[15] Later that day, the center began decoupling from the convection, a sign of rapid weakening,[16] and by 21:00 UTC the IMD downgraded it to a severe cyclonic storm.[2] Early on October 30, the JTWC downgraded Nilofar to a tropical storm,[17] and subsequently the circulation became exposed from the convection.[18] At 18:00 UTC that day, the JTWC posted their final advisory.[19] Nilofar weakened further into a depression on October 31, and soon after degenerated into a remnant low off coast of the Indian state of Gujarat.[2]
Offshore buoys recorded 3.2 m (10.5 ft) waves and winds of 41 km/h (25 mph).[2] The outskirts of the storm caused flash flooding in Al-Rustaq in northeastern Oman, killing four people after a vehicle was swept away in a flooded wadi.[20] Five people were rescued when another car was stranded amid floods west of Al-Rustaq.[21]
In the storm's developmental stages, the outskirts of Nilofar dropped 410mm of rainfall in Margao, Goa,[2] helping the state record its wettest October in four years.[22] Other nearby areas along India's west coast received heavy rainfall.[2] The threat of the storm prompted officials to evacuate nearly 30,000 people in western India, utilizing 200 storm shelters. Most of the displaced people were living in thatched huts and weak structures. In coastal areas, schools were canceled for two days.[23] Most of the evacuees quickly returned home after the storm weakened. To minimize damage, trees were trimmed down to eliminate damage due to falling debris, and a total suspension of fishing activities was ordered,[24] with about 5,000 boats advised to return to port.[25] Officials in Gujarat sent a warning of the storm to all operators of ham radios.[26] A distant warning signal 2 was hoisted in the ports of Kandla and Mundra. National Disaster Response Force deployed rescue and rehabilitation teams at Gandhidham, Dwarka, Porbandar, Veraval, Rajkot and Bhuj while standby teams were stationed at Ahmedabad and Vadodara.[27] [28] After facing problems during deadly floods in September and Cyclone Hudhud in October, mobile companies enacted greater preparations during Nilofar to guarantee operations during the storm, including an emergency hotline, setting up internet in shelters, and mobile cell towers.[29] Despite the threat from the storm, Nilofar only produced light rainfall and gusty winds along the Gujarat coast.[30] Unseasonable rainfall damaged mangoes in Maharashtra, causing prices to rise.[31] Shifting air patterns brought cooler temperatures to western India, signaling the end of the monsoon season,[32] while also bringing haze and smog over Delhi from polluting areas to the south.[33]
In Pakistan, fishermen were also warned to avoid the sea, and people in coastal areas were evacuated. The country's navy, coast guard, Pakistan Maritime Security Agency, and fishermen organizations helped rescue fishermen stationed offshore.[34] Along the coast of Sindh province, bathing and swimming were banned for several days.[35] There were minor power outages in Karachi due to heavy rainfall from Nilofar.[36]