2016–17 South-West Indian Ocean cyclone season

Severe tropical storm (MFR)
Tropical storm (SSHWS)
Duration	July 15 – July 19
Peak intensity	95 km/h (60 mph) (10-min); 987 hPa (mbar)

On July 15, a tropical depression formed to the southwest of Diego Garcia.[2] This marked only the fourth occurrence of a tropical cyclone existing in the southwest Indian Ocean during the month of July, with the others being 1971, Tropical Depression M2 in 1997 and Tropical Cyclone 01U in July 2007.[3][4] The next day, the depression acquired moderate tropical storm status as gale-force winds extended more than halfway around the center.[2] The system tracked west-southwest, organizing slowly in the face of moderate vertical wind shear. On the evening of July 17, RSMC La Réunion initiated warnings on the storm after a scatterometer pass revealed 75 km/h (45 mph) winds. At the same time, Mauritius Meteorological Services named the storm Abela.[5] The small system briefly attained severe tropical storm strength the next day as a low-level eye developed.[2][6] Abela began to weaken quickly in the subsequent hours as it moved into a region with cool sea surface temperatures and low oceanic potential.[7] Abela became a remnant low on July 20 as it neared the coast of Madagascar.[2]

Subtropical depression (MFR)
Duration	October 3 – October 6
Peak intensity	100 km/h (65 mph) (10-min); 987 hPa (mbar)

A zone of disturbed weather developed into a subtropical depression to the south of Madagascar on October 2.[8] The subtropical depression was analysed in post-analysis to have developed peak winds of 95 km/h (60 mph) on October 3.[8] The system slowly weakened as it executed an anticyclonic loop until it had winds of 75 km/h (45 mph) early on October 5, when RSMC La Réunion began to operationally warn on the system and Direction Generale de la Meteorologie (DGM) of Madagascar named it Bransby.[9] Bransby went unmonitored by the Joint Typhoon Warning Center until the next day. The storm continued to weaken throughout the day until it was barely producing gale-force winds. The next day, Bransby developed a defined banding eye as it re-intensified and accelerated to the southeast.[10] Six hours later, Bransby reattained its peak intensity. RSMC La Réunion noted that Bransby had once again developed winds of 95 km/h (60 mph), equivalent to that of the severe tropical storm rating given to tropical cyclones of the same intensity.[8] Throughout the evening of October 6, the organization of Bransby deteriorated rapidly as northwesterly wind shear took its toll, resulting in rapid weakening.[11] On October 7, Bransby became a remnant low with an elongated circulation devoid of convection while moving over 16 °C waters.[12]

Tropical depression (MFR)
Duration	January 27 – January 28
Peak intensity	55 km/h (35 mph) (10-min); 1005 hPa (mbar)

A tropical disturbance developed in the Indian Ocean on January 27.[13] The system rapidly developed, and Météo-France upgraded the system to a depression six hours later.[14] The system was short-lived; the depression would later weaken and Météo-France discontinued advisories for the system on January 28.[15]

Tropical cyclone (MFR)
Category 1 tropical cyclone (SSHWS)
Duration	February 3 – February 10
Peak intensity	130 km/h (80 mph) (10-min); 965 hPa (mbar)

A tropical disturbance formed to the north of Mauritius on January 27.[16] Over the next few days, it gradually organized under low to moderate shear, until Météo-France upgraded the disturbance to a depression.[17] 12 hours later, the agency further upgraded the system, naming it 'Carlos'.[18] The JTWC would follow suit at the same time, designating it as '04S'.[19] Carlos intensified further until Météo-France upgraded Carlos to a severe tropical storm; the system would later weaken, becoming exposed on February 6.[20] Then, Carlos reintensified; the storm would later peak on February 9, with sustained winds of 70 knots and a pressure of 965 mb.[21][19] Afterwards, Carlos rapidly weakened below category 1 strength,[22][19] then undergo extratropical transition, a process that will be completed by February 10.[23][19] Both agencies would monitor the extratropical system until Carlos completely dissipated by February 13.[24][19]

Tropical cyclone (MFR)
Category 2 tropical cyclone (SSHWS)
Duration	February 13 – February 17
Peak intensity	140 km/h (85 mph) (10-min); 955 hPa (mbar)

The origins of Dineo can be tracked back to a cluster of thunderstorms that organized into an area of low pressure in the Mozambique Channel on February 11. Over the next two days, the system gradually drifted in a generally southern track as it gained intensity and prompted the JTWC to issue a TCFA.[25] On February 13, RSMC La Réunion had declared that a Tropical Disturbance has formed in the area and began issuing advisories.[26] Located in a very favorable environment, the depression quickly gained intensity and both the RSMC and JTWC had noted winds of at least 65 km/h (40 mph) later that day, with the RSMC subsequently naming the storm Dineo.[27][28]

Dineo struck Mozambique on February 15 as a tropical cyclone, bringing torrential rain and damaging winds.[29] Dineo was the first tropical cyclone to hit Mozambique since Cyclone Jokwe in 2008.[30] Satellite-derived estimates indicated up to 200 mm (7.9 in) of rain fell in Inhambane.[29] At least seven people were killed across the country,[31] including a child crushed by a fallen tree in Massinga.[32] An estimated 20,000 homes were destroyed and approximately 130,000 people were directly affected.[31] Widespread flooding took place in Zimbabwe, with Mutare, Chiredzi, and Beitbridge particularly hard-hit.[33] At least 271 people were killed by the storm and damage exceeded US$200 million.[34][35][36] The storm's remnants triggered destructive floods in Botswana.[37] In the month following the storm, a cholera outbreak in Mozambique and Malawi infected more than 1,200 people and claimed 2 lives.[38]

Intense tropical cyclone (MFR)
Category 4 tropical cyclone (SSHWS)
Duration	March 2 – March 10
Peak intensity	205 km/h (125 mph) (10-min); 932 hPa (mbar)

A monsoon trough started to persist west of Diego Garcia in late February 2017 as the Madden–Julian oscillation (MJO) over the Indian Ocean grew more noticeable.[39] On 2 March, a zone of disturbed weather formed within the area, although it was initially difficult to define a clear centre;[40] later, the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert for the improving low-level structure and favourable environmental conditions.[41] Only six hours after the system about 820 km (510 mi) north of Mauritius intensifying to a tropical disturbance, Météo-France upgraded it to a moderate tropical storm at 06:00 UTC on 3 March with the name Enawo from the Mauritius Meteorological Services, because of the recent ASCAT-B data suggesting gale-force winds.[42][43] The JTWC also began to issue tropical cyclone warnings on Enawo.[44]

Enawo developed into a severe tropical storm at around 18:00 UTC on 4 March, for showing an impressive embedded centre pattern associated with extremely cold cloud tops.[45] Enawo formed a ragged eye soon thanks to favourable conditions of excellent outflow, weaker vertical wind shear, and warm sea surface temperatures;[46] however, the strengthening phase was halted for a half of day owing to a possible eyewall replacement cycle.[47] Enawo started to intensify again and developed a well-defined eye indicated by both of satellite and microwave imageries, prompting Météo-France upgrading the system to an intense tropical cyclone at 12:00 UTC based on the structural improvements.[48] Enawo reached its peak intensity at 06:00 UTC on 7 March, with ten-minute maximum sustained winds at 205 km/h (125 mph) and the central pressure at 925 hPa (27.32 inHg).[49] Soon after that, Enawo made landfall over the area between Antalaha and Sambava in Sava Region, Madagascar at around 09:30 UTC (12:30 EAT), becoming the strongest landfall to the country since Gafilo in 2004.[50] The cyclone started to rapidly weaken due to land interaction with a cloud-filled eye and the warming cloud tops;[51] the JTWC also issued a final warning later for the inland movement.[52]

Moderate tropical storm (MFR)
Tropical storm (SSHWS)
Duration	March 6 – March 14
Peak intensity	70 km/h (45 mph) (10-min); 992 hPa (mbar)

A tropical wave developed far east off the British Indian Ocean Territory on March 3. Drifting slowly towards the southwest over the next couple of days, it gradually organized into a well marked area of low pressure.[53] On March 6, RSMC La Réunion began tracking the system as Tropical Disturbance 7.[54] As the low-level circulation center (LLCC) became more consolidated and bands of convection improved, the JTWC issued a TCFA for the system;[55] and less than three hours later, RSMC La Réunion began tracking it as a tropical depression.[56] It wasn't until late on March 8, however, that the JTWC issued their first warning on the depression. The system was drifting southwestward under the influence of a strong subtropical ridge location just south of it. It was located about 940 kilometres (580 mi) south-sowthwest Diego Garcia when winds of 65 km/h (40 mph) were first noted.[57]

While the JTWC had reported tropical-storm force winds over the next two days, RSMC La Réunion only tracked it as a tropical depression until March 10 when both the agencies reported that the system had dissipated. RSMC had downgraded the depression to a Zone of Disturbed Weather while the JTWC reported that the LLCC was dissipating into a trough.[58][59] The system continued to track in a generally southwestern direction and exhibited subtropical characteristics. RSMC La Réunion resumed tracking it as a tropical depression on March 14.[60] Later that day, the RSMC had further upgraded the system to a Moderate Tropical Storm and named it Fernando, despite its subtropical nature.[61] RSMC La Réunion first reported the post-tropical nature of Fernando on March 15 at 00:00 UTC while the central pressure continued to drop.[62] They issued their final warning later that day.[63]

During May 30, the Australian Bureau of Meteorology started to monitor Tropical Low 31U, which had developed about 2,000 km (1,245 mi) west of Jakarta, Indonesia.[64] Over the next few days, the system moved southwestwards and was classified as an area of low pressure by RSMC La Réunion, before it started to fill up and dissipated on June 2.[65]