The 2021 North Indian Ocean cyclone season was an event in the annual cycle of tropical cycloneformation. The North Indian Ocean cyclone season has no official bounds, but cyclones tend to form between April and December, peaking between May and November. These dates conventionally delimit the period of each year when most tropical cyclones form in the northern Indian Ocean. The season began on April 2, when a depression designated as BOB 01 was formed in the north Andaman Sea and quickly made landfall in Myanmar. The basin remained quiet for over a month before Cyclone Tauktae formed. It rapidly intensified into an extremely severe cyclonic storm before making landfall in Gujarat, become the strongest storm ever to strike that state since the 1998 Gujarat cyclone. Later that month, BOB 02 formed and later strengthened into Cyclone Yaas. Yaas rapidly intensified into a very severe cyclonic storm before making landfall in northwestern Odisha. The season's strongest tropical cyclone was Cyclone Tauktae, with maximum wind speeds of 185km/h (115mph) and a minimum barometric pressure of 950hPa (28.05inHg).
No systems formed in the basin until April 2, when a depression near the Myanmar coast in the North Andaman Sea formed, however it dissipated the next day. It was considered rare since the storm formation usually begins from mid-April to May. After a month of inactivity, another depression formed off the coasts of Kerala and Lakshadweep. It intensified into a deep depression on the same day and later into a cyclonic storm, being assigned the name Tauktae by the IMD. It continued intensifying, and on May 17, Tauktae peaked as an extremely severe cyclonic storm before making landfall in Gujarat hours later, dissipating on May 19. A few days after Tauktae dissipated, a depression formed in the Bay of Bengal on May 23. It intensified gradually to a cyclonic storm and assigned the name Yaas. It further intensified into a very severe cyclonic storm on May 25 and made landfall in the state of Odisha by the next day, becoming the second cyclone to hit the nation within a span of ten days. After a long gap of three and a half months, a depression formed in the Bay of Bengal on September 12, becoming the first system in the monsoon season. Not a week later, another depression formed over the east-central Bay of Bengal, making the second system in the post-monsoon season. It later intensified into a deep depression and on 25 September 2021, it intensified into cyclonic storm which was named Gulab, marking the first named storm in the post-monsoon season. Then, after only two days, the remnants of Cyclonic Storm Gulab entered the Arabian sea and regenerated into a Depression and became ARB 02. ARB 02 intensified into a cyclonic storm and was named Shaheen by the IMD. After an unusual month of inactivity, Depression ARB 03 formed in early November and remained out to sea. A couple of days later, Depression BOB 05 formed in the Bay of Bengal but failed to further intensify due to high wind shear. BOB 05 impacted portions of southern India with flooding, and some areas experienced cyclonic storm sustained winds. A few days later, Depression BOB 06 formed which gave additional rainfall and damages to the same places in southern India which were affected by BOB 05 earlier with the worst damages being in Rayalaseema region of Andhra Pradesh. In the month of December, a low pressure area entered into the Andaman Sea from the West Pacific Ocean and it intensified gradually into a cyclonic storm named as Jawad. Initially expected to make landfall over Odisha but due to extremely high wind shear, it weakened rapidly into a low pressure area without making a landfall.
A tropical wave developed stretching between the Malay Peninsula and the equatorial Indian Ocean. From this wave a cyclonic circulation formed on March 26 over the southeast Bay of Bengal. The strong pulse of the Madden–Julian oscillation, high Tropical Cyclone Heat Potential, moderate sea surface temperatures up to 29–30°C (84–86°F), and moderate wind shear, caused the system intensify into a low-pressure area on March 31. An anticyclonic circulation in southeast Asia and an upper tropospheric ridge in the westerlies caused the system to move north-northeastwards. These conditions influenced the system and its intensification as it became a well-marked low-pressure area on April 1 at 09:00UTC (14:30IST), and later becoming a depression on April 2 at 00:00UTC (05:30IST). Satellite imagery revealed that during its intensification, the clouds of the system organised and developed a low-level circulation center with intense to very intense convection at its center. It continued to maintain its intensity, however, at 00:00UTC (05:30IST) on April 3, vertical wind shear increased, causing the system to weaken slightly and the system's clouds to become disorganised, however, a scatterometer pass revealed that it still maintained its intensity. On April 3, at 03:00UTC (08:30IST), the clouds further became disorganised, while maintaining its low-level circulation. The system continued to weaken under similar unfavourable conditions with further disorganising of clouds, and at 06:00UTC (11:30IST), the system was downgraded to a well-marked low-pressure area, with the system barely having a circulation.[2]
The influence of the system caused light to moderate rainfall in most places of Andaman Islands and heavy rainfall in few places. The system's remnant low caused isolated rainfall over the Myanmar coast. Estimated winds of up to 40 to 50km/h (25 to 30mph) gusting up to 60km/h (35mph) were recorded on the island.[2] The first tropical depression of the basin, it was also a rare disturbance since it formed in early April while the most cyclogenesis occurs during mid-April or throughout May.[2]
On May 14, a depression formed in the Arabian Sea off the coast of Kerala.[3] The JTWC began monitoring the depression, and designated it as Tropical Cyclone 01A.[4] The system gradually intensified, before intensifying into a Deep Depression by 12:00UTC (17:30IST) that day.[5] Around 18:00UTC (23:30IST) that day, the system intensified into a Cyclonic Storm, and it was given the name Tauktae by the IMD.[6][7] The name Tauktae was contributed to the naming list by Myanmar, and it means gecko in the Burmese language.[8] It later intensified into a Severe Cyclonic Storm at 15:00UTC (20:30IST) in May 15.[9]Tauktae's intensification was unusual as it intensified from a depression to a severe cyclonic storm over a period of just two days, with equivalent storms generally taking four to five days to intensify into a severe cyclonic storm.[10] Three hours later, the JTWC upgraded Tauktae to a Category 1-equivalent tropical cyclone on the Saffir–Simpson scale.[11] Tauktae further intensified into a Very Severe Cyclonic Storm at 00:00UTC (05:30IST) May 16.[12] At 06:00UTC (11:30IST) that day, the JTWC upgraded the storm further to a Category 2 tropical cyclone.[13]INSAT imagery showed that the cyclone had developed an eye by 09:00UTC (14:30IST).[14] However, the eye had started to degrade by 15:00UTC (20:30IST), according to INSAT imagery, and remained ragged for the rest of the storm's lifetime.[15]
At 03:00UTC on May 17, Tauktae intensified into an Extremely Severe Cyclonic Storm on 03:00UTC (08:30IST) of May 17,[16] which was unexpected since many forecaster predicted that it would be a very severe cyclonic storm.[17] The JTWC upgraded Tauktae to a Category 4-equivalent tropical cyclone soon afterward.[18] However, Tauktae quickly weakened into a Category 3-equivalent tropical cyclone later that day.[19] The cyclone made landfall in the region of Saurashtra between Diu and Una at around 15:30UTC (21:00IST). After landfall, Tauktae weakened to a Very Severe Cyclonic Storm. Wind speeds of approximately 150 to 175km/h (93 to 109mph) were recorded at the district of Diu in the union territory of Dadra and Nagar Haveli and Daman and Diu. It became one of strongest tropical cyclone to make landfall in the Indian state of Gujarat since the 1998 Gujarat cyclone.[20][21] Meanwhile, the JTWC issued their last tropical cyclone warning on the storm at 21:00UTC (02:30IST) on May 17.[22] The weakening trend although slower than usual due to the brown ocean effect mostly because of the influence of a western disturbance, which continued as it moved further inland until 14:00UTC (19:30IST) on May 19, when it was downgraded to a well-marked low pressure area over Eastern Rajasthan and adjoining west Madhya Pradesh, later dissipating.[23][24] The combination of a western disturbance and the remnants of Cyclone Tauktae have also caused heavy rainfall in Northwestern India.[25]
A total of 174 people were confirmed to have been killed by the storm, and 81 others are still missing.[26] Heavy rainfall was reported over areas of Kerala,[27] causing flash floods and waterlogging soil;[28] fishing was temporarily banned in the area due to rough seas.[29] Parts of Kerala and Lakshadweep were placed under a red alert on May 14.[30] The second state experienced heavy rainfall as the cyclone tracked west of the Indian coast. In Chellanan, a village in Ernakulam district, homes were submerged underwater due to unexpected rain and coastal erosion. Agricultural losses statewide was ₹828 crore (US$113 million).[31] The administration opened up a relief camp at the local St. Mary's School for the inhabitants of low-lying areas. Due to the ongoing second wave of the COVID-19 pandemic in India, isolated testing facilities were arranged.[32] The most severe effects of Cyclone Tauktae occurred in the states of Maharashtra and Saurashtra in Gujarat. The latter state reported the losses of ₹10,000 crore (US$1.37 billion).[33] The city of Mumbai experienced heavy rainfall, very strong trees and waves crashed the shores. Trees were uprooted and streets were waterlogged. It was the strongest cyclone since Cyclone Nisarga in 2020.[34] As a precaution, flight operations at Chhatrapati Shivaji Maharaj International Airport were temporarily halted before resuming hours later.[35] The cyclone also affected neighbouring countries like Pakistan, Maldives and Sri Lanka.[36] In the Sindh province of Pakistan, four people died due to a roof collapse caused by strong winds.[37][38]
On May 22, a low-pressure area formed in the Bay of Bengal. On the next day, at 09:30UTC (15:00IST), the disturbance organised into a Depression, and was assigned the designation BOB 02 by the IMD.[39] Later that day, the JTWC issued a Tropical Cyclone Formation Alert for the system.[40] The storm subsequently intensified into a Deep Depression at 15:00UTC (20:30IST) on May 23.[41] Several hours later, the storm further intensified into a Cyclonic Storm at 03:00UTC (08:30IST) on May 24, and was given the name Yaas by the IMD.[42] The name Yaas was provided by Oman,[7] and it means "a Jasmin-like tree", which has good fragrance in Persian.[8] In Arabic, the name Yaas is known as despair or desperation.[43] Meanwhile, JTWC designated as Tropical Cyclone 02B.[44] On May 24, at 18:00UTC (23:30IST) it rapidly intensified into a severe cyclonic storm,[45] then becoming a very severe cyclonic storm on 15:00UTC (20:30IST) of May 25 despite being present in moderate to high easterly wind shear.[46] Meanwhile, JTWC upgraded it into a Category 1 tropical cyclone on 15:00UTC (20:30IST) of the same day.[47] The cyclone made landfall north of Dhamra Port and south of Bahanaga at around 03:30UTC (09:00IST) in May 26.[48] The process completed at around 05:30UTC (11:00IST ), with estimated winds up to 130 to 140km/h (80 to 85mph). Storm surge caused most of the damage in south Bengal and northwestern Odisha.[49] After landfall it started to weaken rapidly into a severe cyclonic storm then into a cyclonic storm.[50] As it moved further inland towards Nepal, IMD discontinuing advisories for Cyclone Yaas, as it became a well marked low pressure on 00:00UTC (05:00IST) of May 28.[51] JTWC later issued their last warning at 09:00UTC (11:30IST) in May 26, stating that it rapidly weakened into a tropical storm after landfall.[52] The remnant of Cyclone Yaas continued moving north-northwestwards and impacted Bihar, Jharkhand and eastern Uttar Pradesh. Heavy rainfall and gusty winds were reported in these areas.[53][54][55] The cyclone also helped the monsoon to strengthen over the Bay of Bengal, after Tauktae disrupted it on May 15.[56]
Eleven people had been reported dead due to Cyclone Yaas. Of them, two died in a tornado outbreak which struck West Bengal's Hooghly District and North 24 Paraganas, according to Chief Minister Mamata Banerjee. At least 80 homes had been damaged.[57] Another died as a tree fell onto him, and a teen was found dead in a river. Two farmers had also died after being struck by lightning, and an elderly woman was trapped in a collapsed house, eventually dying there. Two individuals were killed as they were crushed by uprooted trees while in Jharkhand, two more people were found dead in a collapsed house on May 27. estimated the total damages in West Bengal from the system to be at ₹20 thousand crore (US$2.76 billion).[58] The most affected states are West Bengal and Odisha. At least 10 million people were affected and 300,000 houses were damaged. Most them were caused by storm surge, high astronomical tides and broken embankments. The West Bengal Government verified that 134 embankments has been damaged. At least two million people were evacuated in the states of West Bengal, Odisha and Jharkhand.[59] Towns of Frazerganj, Bakkhali, Sundarban, Kakdwip, Namkhana, Ganga Sagar and Gosaba were flooded by seawater.[60] As a precautionary measure, airports of Bhubaneswar, Jharsuguda, Kolkata, Rourkela and Durgapur were closed temporarily until May 27.[61] Cyclone Yaas generated high waves and storm surge which crashed the coastal beaches of Digha and Mandarmoni. The concrete embankments broke and seawater flooded the entire Digha—Mandarmoni Belt.[62] Because of big wind field of Cyclone Yaas, Kolkata experienced powerful gusty winds, Alipore Meteorological Department recorded 62km/h (39mph) winds.[63] Minimal damage was reported, however high tides caused the Hooghly River to flood neighboring banks like Kalighat, Howrah and Chelta.[64] The cyclone also affected Nepal and Bangladesh.[65][66] The remnants of Cyclone Yaas made landfall in Nepal and triggered heavy rainfall.[65] Meanwhile, Bangladesh experienced high tide and storm surge which flooded many villages.[66]
On September 11 at 00:00UTC (05:30IST), under an influence of a cyclonic disturbance, an area of low pressure had formed over the east central and the adjoining northeastern Bay of Bengal, which later intensified into a well marked low pressure area, a day later. At 12:00UTC (17:30IST) the same day, it further concentrated into a depression as it approached the coast of Odisha. Conditions like low to moderate vertical wind shear, warm sea-surface temperature and strong pulse of Madden Julian Oscillation helped the system's intensification to a depression. Due to the prevailing monsoonal trade winds, the system moved west-northwestwards for the rest of its lifetime.[67][68] As the system was about to make landfall near Chandbali, Odisha, it further concentrated deep depression at 00:00UTC (05:30IST). At the same moment it crossed near Chandbali between 00:00UTC and 01:00UTC (05:30IST and 06:30IST) as a deep depression. After crossing, it weakened into a depression over the border of Chhattisgarh and Odisha, at 03:00UTC (08:30IST) the next day, but it managed to maintain its intensity for the rest of its lifetime, because of the prevailing monsoonal conditions. This unusual phenomenon is called the brown ocean effect.[69][68] It continued to move on its trajectory, until at 00:00UTC of September 15, it further weakened into a well-marked low pressure area over northeastern Madhya Pradesh and its neighbourhood.[68] The JTWC didn't tracked the system, but they did monitored as an invest.[70]
The system caused vigorous monsoonal conditions over eastern India, mainly Odisha and West Bengal and central India. It led to extremely heavy rainfall over few places of Odisha, isolated places of Chhattisgarh between September 12 and 13 and over eastern Madhya Pradesh on September 14. As the system moved westwards, it interacted with another low pressure system off the coast of Gujarat caused extremely heavy rainfall over Saurashtra region of Gujarat and the Konkan division of Maharashtra on September 13. The outer bands of the system also caused extremely heavy rainfall in isolated places of West Bengal on September 14.[68] Three fatalities have been reported, all from Odisha and 1.953 million people had been affected.[71][68] Some cities recorded exceptionally heavy rainfall like Puri recorded 341mm (13.4in) of rain, breaking the 88-year-old record which was made in 1934 and Bhubaneswar which recorded 195mm (7.7in) of rain, breaking the 63-year-old record which was made in 1958.[71] A goods train which ran on the Angul–Talcher Road rail route derailed at around 02:30IST (20:00UTC) and fell over a river. No one was injured.[72] The Kolkata airport was inundated in floodwaters causing disruptions in flight's timings however no flights were cancelled.[73]
On September 24, the JTWC noted a cyclone which was producing tropical storm-force winds located over the east-central Bay of Bengal, 211nmi (391km; 243mi) south of Chittagong, Bangladesh, designating the system as 03B.[74] The IMD noted the system as a low pressure area at 03:00 UTC (08:30 IST); the system formed from a cyclonic circulation which persisted over the Gulf of Martaban.[75][76] It was later upgraded to a well-marked low-pressure area at 11:00 UTC (16:30 IST), as it developed a cyclonic vortex at 06:00 UTC (11:30 IST).[77][78] At 15:00 UTC (20:30 IST), the IMD upgraded it to a Depression, as the convection had further organized and the clouds were moving in a curved manner. Favorable conditions such as moderate to high sea-surface temperatures, the Madden–Julian oscillation being favorable for tropical cyclone development, and low vertical wind shear allowed intensification.[79] By 03:00 UTC the next day, the system was upgraded to a Deep Depression, as the cloud further organized near the center. There were also the presence of warm moist air over the center of the system.[80][81] At 15:00 UTC (20:30 IST), the IMD upgraded it to a cyclonic storm as its convection had become better organized with a defined central dense overcast.[82] The system was named Gulab, which was suggested by Pakistan.[82][7] The name means rose in Urdu/Hindi.[83] As it continued westward, the cloud bands of Cyclone Gulab had touched the coastal regions of northern Andhra Pradesh and southern Odisha, which indicated that it had started its landfall process at about 18:00 IST (12:30 UTC) on September 26.[84] By 17:00 UTC (10:30 IST), it had crossed 20km (10mi) north of Kalingapatnam.[85] At 21:00 UTC (02:30 IST), the JTWC had issued its final warning prior to landfall.[86] Three hours later, the IMD downgraded it to a deep depression, as it had lost its energy after travelling over rough Indian terrain.[87] It further weakened into a depression by 20:00 IST (14:30 UTC) as it entered the state of Telangana.[88] It maintained its intensity as it travelled westwards until at 14:00 IST (08:30 UTC), when it weakened into a well-marked low pressure area over west Vidarbha.[89] The remnant of Gulab later became Cyclone Shaheen over the Arabian Sea.[90][91]
Gulab caused severe floods and landslide in several states in southern and central India killing 17 people and caused ₹20 billion (US$269 million) in damage.[92] In Andhra Pradesh, heavy damage were caused by Gulab over Srikakulam and Vizianagaram districts. Communications and electricity were disrupted and uprooted trees caused congestion in roads. The city of Vizianagaram was inundated with waterlogging because of improper underground drainage system and hundreds of trees and billboards were fallen in different places.[93] In Vizag, heavy rainfall caused regional floods and gusty winds which caused uprooting of several trees.[94] The heavy rainfall also caused the inundation of the airport.[95] The city recorded 282mm (11.1in) in 24 hours making the wettest September only behind the year 2005.[96] Two people died because of drowning.[97] As Gulab weakened into a deep depression, it entered Telangana and Chhattisgarh dumping enormous amounts of heavy rainfall. In Telangana especially Hyderabad, flash flooding caused disruption in traffic and severe hardships to the residents. Two people were washed away by an overflowed stream. Because of the above situation, the government of Telangana declared a holiday for all government offices, schools, and institutions.[98] The heavy rainfall caused the Musi river to overflow.[99] Heavy rainfall were also seen in Chhattisgarh.[100] The remnant of Cyclone Gulab, caused devastating rainfall and landslides in Maharashtra. According to the State Disaster Response Force, thirteen people and 206 livestock were killed by the flooding from eight districts of the state. Four people went missing after a Maharashtra state transport bus was swept away by an overflowing stream near Umarkhed, Maharashtra, however two of the six travellers were rescued successfully.[101]
On September 29, the remnant of Cyclone Gulab entered north-eastern Arabian Sea as a well-marked low pressure area.[90] On the same day at 17:30 UTC (23:00 IST), the JTWC issued a TCFA, as it developed a well-defined convection and a low-level circulation center.[102] At 00:00 UTC (05:30 IST) next day, the IMD upgraded it to a depression over the Gulf of Kutch and it was designated as ARB 02. Latest INSAT 3D satellite imagery showed that the convection had increased near its center.[103][104] At 21:00 UTC (02:30 IST), the JTWC upgraded it as a tropical storm, however they had designated it 03B, as the agency claims Shaheen to be a continuation of Cyclone Gulab.[105] At the same moment, the IMD upgraded it to a deep depression.[106] Six hours later, the system was further upgraded to a cyclonic storm, as the spiral bands were seen wrapping over the obscure low-level circulation center.[91] The system was named Shaheen, which was offered by Qatar.[91][7] The name Shaheen means royal white falcon or hawk.[107] At 15:00 UTC (20:30 IST), the IMD further upgraded it to a severe cyclonic storm, as the clouds had become well-organized moving with a defined curved pattern.[108] At 03:00 UTC (08:30 IST) the next day, the JTWC upgraded it to a Category 1 equivalent tropical cyclone, as it developed an eye-like feature. However, it struggled for further development, due to lack of convection.[109] By 06:00 UTC (11:30 IST), the cyclone developed a defined but ragged eye.[110] At 09:00 UTC (14:30 IST), the JTWC downgraded it to a tropical storm,[111] but six hours later, the JTWC re-upgraded it to a Category 1 tropical cyclone.[112] Between 19:00 UTC and 20:00 UTC (00:30 IST and 01:30 IST), Shaheen made landfall over the northern Oman coast,[113] making it one of the rare cyclones to strike this region since 1890.[114][115] At 21:00 UTC (02:30 IST), the JTWC issued its final warning for the storm as it made landfall.[116] After making landfall, Shaheen underwent a rapid weakening because of the dry landmass of the Arabian Desert. From 00:00 UTC till 12:00 UTC, it rapidly weakened from a severe cyclonic storm to a well-marked low pressure area. Satellite imagery showed that after making landfall, the cloud mass had quickly become disorganized and the center became less defined.[117][118][119]
Cyclone Shaheen caused devastating effects mainly in Oman and Iran, killing 14 people and caused a loss of OMR200 million (US$520 million), mainly in Oman.[120] The precursor of Cyclone Shaheen caused heavy to very heavy rainfall in parts of Gujarat.[121] As the cyclone strengthened, it moved along the Iranian coast generating dust storms which affected the province of Sistan and Baluchestan. Due to the dust storm caused by the cyclone, many people went to hospital as they suffered of eye and respiratory problems. Two fisherman was found dead out of the five fishermen that went missing.[122][123] In Oman, the cyclone caused widespread heavy rainfall that the country had never seen. Because of the dry landmass, it couldn't absorb water quickly, causing deadly flash flooding.[124] Most of the damage happened in the region of Batineh, which experienced wind up to 60kn (110km/h; 70mph) and waves up to 12m (39ft).[125][126] It killed 12 people in Oman alone.[122][123] In United Arab Emirates, the country experienced light rainfall in parts of Dubai, Al Ain and Ajman. Dust storms were also reported which reduced visibility.[127] The remnant of Cyclone Shaheen caused heavy rainfall in Yemen and damaging historical sites. Reports of around 20 vehicles had been washed away by flash flooding.[128]
On November 3, a low pressure area entered into the Arabian Sea,[129] which formed over south-central Bay of Bengal on October 27.[130] The low pressure area later organized into a well-marked low pressure area on November 6, as the system gradually moved northwards.[131] On the next day, conditions became more favourable for further intensification, like further intensification of the MJO index, warm sea-surface temperature and moderate wind shear. Thus the system further intensified into a depression at 06:00 UTC (11:30 IST).[132] However, conditions did not allowed the system for further intensification. Thus, at 03:00 UTC (08:30 IST) of November 9, the IMD downgraded it to a well-marked low pressure area.[133] The JTWC also tracked the system, from 18:00 UTC (23:30 IST) of November 4 while located at 537 nautical miles (995km; 618mi) to the south-southwest of Mumbai until the same time of November 6.[134][135]
On November 6, the IMD noted the formation of a cyclonic circulation over southeastern Bay of Bengal near Sumatra.[136] Two days later at 13:30 UTC (19:00 IST), the JTWC started tracking the same system as Invest 91B.[137] On November 9, under the influence of the cyclonic circulation, a low-pressure area formed over the same area.[138] On the next day, it was upgraded to a well-marked low pressure area after noting a formation of a defined vortex in associated with the system.[139][140] At 15:00 UTC (21:30 IST), the IMD further upgraded it to a depression as its convective structure had improved significantly.[141] Later at 19:30 UTC (01:00 IST), the JTWC issued a TCFA for system.[142] At 09:00 UTC of November 11, the JTWC declared it as a tropical cyclone and designated as 04B.[143] However, the system could not further intensify as it was already near to the coast and high wind shear produced by an upper tropospheric ridge.[143][141] Between 12:00 and 13:00 UTC (17:30 and 18:30 IST), the system made landfall near to Chennai,[144] and by 00:00 UTC (05:30 IST) the next day the system weakened into a well-marked low pressure area.[145] The JTWC issued its final advisory at 15:00 UTC of November 11.[146]
The depression further worsened the floods that occurred in Tamil Nadu and Andhra Pradesh. It took lives of 16 people in India and 25 people in Sri Lanka.[147]
On November 12, a cyclonic circulation persisted over the Gulf of Thailand and the adjoining Malay Peninsula,[148] which on the next day became a low pressure area by the IMD and Invest 92B by the JTWC.[149][150] The IMD and the JTWC previously forecasted that it would become a depression by November 15 and further intensify on November 18 as it reaches the coast of Andhra Pradesh.[149][150] However both the agencies downgraded to nil chance of becoming a depression on November 15, because of a formation of another low pressure system over the Arabian Sea and the formation of a trough to the south of the system over the east of the equatorial Indian Ocean, which blocked the inflow of warm moist winds to the center of the system.[151][152] As the low pressure area meandered westwards towards the Tamil Nadu coast, the system rapidly intensified into a depression by 07:00 UTC (12:30 IST) of November 18, as its convection rapidly consolidated and formed a distinct low-level center. By the same time, the JTWC issued a TCFA on the system and started to retrack.[153][154] Between 21:30 and 22:30 UTC (03:00 and 04:00 IST) of the same day, the depression crossed north of Pondicherry,[155] and by 08:00 UTC (13:30 IST) the system weakened into a well-marked low pressure area.[156] The JTWC cancelled the TCFA as it made landfall.[157]
On November 28, the JTWC and the JMA acknowledged a formation of an area of low pressure, which they dubbed as Invest 94W over the South China Sea, which was located 251nmi (465km; 289mi) from Ho Chi Minh City.[158][159] Two days later, at 12:00 UTC (17:30 IST) on November 30, the system crossed into the Andaman Sea, and the IMD started to monitor the system as a low-pressure area.[160] On December 2, at 00:00 UTC (05:30 IST), the system further intensified into a well-marked low-pressure area, as the department found that the storm's thunderstorms had been organizing over the past day, with a distinct shear pattern.[161] Shortly afterward, the JTWC issued a TCFA for the system.[162] Later that day, at 12:00 UTC (17:30 IST), the system intensified into a depression, with the IMD designating the system as BOB 07, after the storm's convection organized further.[163] By the next day, at 03:00 UTC (08:30 IST), the system further intensified into a deep depression.[164] At the same time, the JTWC declared it a tropical cyclone, assigning a tropical storm intensity to the system, as the cyclone developed a well-defined mid-level circulation, though its low-level circulation center was displaced to the northwest.[165] Three hours later, the system was upgraded to a cyclonic storm, with IMD assigning the system the name Jawad, which was submitted by Saudi Arabia,[166][7] which means "generous" or "merciful" in Arabic.[167] After 00:00 UTC of December 4, Jawad started to lose steam after reaching its peak at 12:00 UTC the previous day,[168][169] and by 12:00 UTC the same day, Jawad lost its organization and the IMD downgraded the storm back into a deep depression, most possibly due to decreasing sea surface temperatures along the storm's track with unfavorable wind shear.[170] This same reasoning was also used by the JTWC in the agency's final warning on the system, three hours earlier.[171] At the same time by the next day, Jawad was further downgraded into a depression as it started to make a northwestward move,[172] and by December 6 at 00:00 UTC, the system further degenerated into a well-marked low-pressure over the northwest Bay of Bengal without making landfall; its convection moved inland over West Bengal and Bangladesh, however.[173]
Since Cyclone Jawad stayed mainly over the sea, it didn't cause any significant damages. However it did take two lives because of a falling coconut tree.[174]
Storm names
Within this basin, a tropical cyclone is assigned a name when it is judged to have reached cyclonic storm intensity with winds of 65km/h (40mph). The names were selected by a new list from the Regional Specialized Meteorological Center in New Delhi by mid year of 2020. There is no retirement of tropical cyclone names in this basin as the list of names is only scheduled to be used once before a new list of names is drawn up. Should a named tropical cyclone move into the basin from the Western Pacific, then it will retain its original name. The names which were used for the 2021 season are listed below.[7]
This is a table of all storms in the 2021 North Indian Ocean cyclone season. It mentions all of the season's storms and their names, duration, peak intensities (according to the IMD storm scale), damage, and death totals. Damage and death totals include the damage and deaths caused when that storm was a precursor wave or extratropical low, and all of the damage figures are in 2021 USD.
In the Indian Ocean north of the equator, tropical cyclones can form throughout the year on either side of the Indian subcontinent, although most frequently between April and June, and between October and December.
Severe Cyclonic Storm Agni was a tropical cyclone of the 2004 North Indian Ocean cyclone season notable for its record proximity to the equator. It was the second North Indian Ocean cyclone to receive a name, after Onil earlier in the year. Agni formed on November 28 well to the southwest of India in the Arabian Sea, and steadily intensified as it tracked northwestward. The Joint Typhoon Warning Center (JTWC) estimated peak 1 minute sustained winds of 120 km/h (75 mph), while the India Meteorological Department (IMD) estimated peak 3 minute sustained winds of 100 km/h (60 mph); the IMD is the official warning center for the north Indian Ocean. After peaking, it weakened due to wind shear, dry air, and cooler waters, and the JTWC issued its final advisory on December 3 as it approached the coast of Somalia. The remnants of Agni moved along the Somalian coastline until dissipating on December 5.
Below is a timeline of the 2007 North Indian Ocean cyclone season, documenting major events with regards to tropical cyclone formation, strengthening, weakening, landfall, extratropical transition, as well as dissipation. The 2007 North Indian Ocean cyclone season was an ongoing event in the annual cycle of tropical cyclone formation.
The 2008 North Indian Ocean cyclone season officially ran throughout the year during 2008, with the first depression forming on April 27. The timeline includes information that was not operationally released, meaning that information from post-storm reviews by the Joint Typhoon Warning Center (JTWC), and the India Meteorological Department (IMD), such as information on a storm that was not operationally warned on. This timeline documents all the storm formations, strengthening, weakening, landfalls, extratropical transitions, as well as dissipation's during the 2008 North Indian Ocean cyclone season.
The 2009 North Indian Ocean cyclone season was an event in the annual cycle of tropical cyclone formation. The North Indian Ocean cyclone season has no official bounds, but cyclones tend to form between April and December, with peaks in May and November. These dates conventionally delimit the period of each year when most tropical cyclones form in the northern Indian Ocean.
Cyclonic Storm Phyan developed as a tropical disturbance to the southwest of Colombo in Sri Lanka on November 4, 2009. Over the next couple of days, the disturbance gradually developed before weakening as it made landfall on Southern India on November 7. After the disturbance emerged into the Arabian Sea, it rapidly became more of a concern to the India Meteorological Department (IMD) reporting early on November 9 that the disturbance had intensified into a Depression, and designated it as Depression ARB 03 whilst the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert. Later that day, the JTWC designated the system as Cyclone 04A. During the next day, the Depression turned towards the northeast the IMD reported that it had intensified into a Cyclonic Storm and named it as Phyan.
The 2011 North Indian Ocean cyclone season was the least active tropical cyclone season in the North Indian Ocean since 1993. Only two cyclonic storms formed, below the average of four to six. The North Indian Ocean cyclone season has no official bounds, but cyclones tend to form between April and December, with peaks in May and November. These dates conventionally delimit the period of each year when most tropical cyclones form in the northern Indian Ocean. The scope of this article is limited to the Indian Ocean in the Northern Hemisphere, east of the Horn of Africa and west of the Malay Peninsula. There are two main seas in the North Indian Ocean — the Arabian Sea to the west of the Indian subcontinent, abbreviated ARB by the India Meteorological Department (IMD); and the Bay of Bengal to the east, abbreviated BOB by the IMD.
The 2012 North Indian Ocean cyclone season was a very inactive season. The season had a very late start, with the first system forming in October. During the season, only five systems formed, of which only two became cyclonic storms. Both the storms made landfall, and they, along with the deep depressions, were responsible for 128 deaths and economic losses worth at least $56.7 million.
The 2012 North Indian Ocean cyclone season was an event in the annual cycle of tropical cyclone formation. The scope of this article is limited to the Indian Ocean in the Northern Hemisphere, east of the Horn of Africa and west of the Malay Peninsula. There are two main seas in the North Indian Ocean — the Arabian Sea to the west of the Indian subcontinent, abbreviated ARB by the India Meteorological Department (IMD); and the Bay of Bengal to the east, abbreviated BOB by the IMD. The official Regional Specialized Meteorological Centre in this basin is the India Meteorological Department (IMD), while the Joint Typhoon Warning Center releases unofficial advisories. This timeline includes information that was operationally released, meaning that data from post-storm reviews by the IMD, such as a storm that was not operationally warned upon, has not been included. This timeline documents tropical cyclone formations, strengthening, weakening, landfalls, and dissipations during the season.
The 2016 North Indian Ocean cyclone season was an event in the annual cycle of tropical cyclone formation. It was the deadliest season since 2010, killing more than 400 people. The season was an average one, seeing four named storms, with one further intensifying into a very severe cyclonic storm. The first named storm, Roanu, developed on 19 May while the season's last named storm, Vardah, dissipated on 18 December. The North Indian Ocean cyclone season has no official bounds, but cyclones tend to form between April and December, with the two peaks in May and November. These dates conventionally delimit the period of each year when most tropical cyclones form in the northern Indian Ocean.
The 2019 North Indian Ocean cyclone season was the most active North Indian Ocean cyclone season on record, in terms of cyclonic storms, however the 1992 season was more active according to the Joint Typhoon Warning Center. The season featured 12 depressions, 11 deep depressions, 8 cyclonic storms, 6 severe cyclonic storms, 6 very severe cyclonic storms, 3 extremely severe cyclonic storms, and 1 super cyclonic storm, Kyarr, the first since Cyclone Gonu in 2007. Additionally, it was also the third-costliest season recorded in the North Indian Ocean, only behind the 2020 and 2008 seasons.
The 2020 North Indian Ocean cyclone season was the costliest North Indian Ocean cyclone season on record, mostly due to the devastating Cyclone Amphan. The North Indian Ocean cyclone season has no official bounds, but cyclones tend to form between April and November, with peaks in late April to May and October to November. These dates conventionally delimit the period of each year when most tropical cyclones form in the northern Indian Ocean. The season began on May 16 with the designation of Depression BOB 01 in the Bay of Bengal, which later became Amphan. Cyclone Amphan was the strongest storm in the Bay of Bengal in 21 years and would break Nargis of 2008's record as the costliest storm in the North Indian Ocean. The season concluded with the dissipation of Cyclone Burevi on December 5. Overall, the season was slightly above average, seeing the development of five cyclonic storms.
The 2022 North Indian Ocean cyclone season was an event in the annual cycle of tropical cyclone formation. It was an above-average season in terms of depressions and average in terms of deep depressions, but slightly below average in terms of cyclonic storms. It was also the least deadly North Indian Ocean cyclone season since 1988, according to official data. The season's strongest tropical cyclone was Cyclone Asani, with maximum wind speeds of 100 km/h and a minimum barometric pressure of 982 hPa. The North Indian Ocean cyclone season has no official bounds, but cyclones tend to form between April and December, with the peak from May to November. These dates conventionally delimit the period of each year when most tropical cyclones form in the northern Indian Ocean.
Extremely Severe Cyclonic Storm Tauktae was a powerful, deadly and damaging tropical cyclone in the Arabian Sea that became the strongest tropical cyclone to make landfall in the Indian state of Gujarat since the 1998 Gujarat cyclone and one of the strongest tropical cyclones to ever affect the west coast of India and above all It was the strongest storm of 2021 North Indian Ocean cyclone season. The second depression, first cyclonic storm, first severe cyclonic storm, first very severe cyclonic storm, and first extremely severe cyclonic storm of the 2021 North Indian Ocean cyclone season, Tauktae originated from an area of low pressure in the Arabian Sea, which was first monitored by the India Meteorological Department on May 13. The low drifted eastward and organized into a deep depression by May 14. The storm soon took a northward turn, continuing to gradually intensify because of warm waters near the coast, and the system strengthened into a cyclonic storm and was named Tauktae later that same day. Tauktae continued intensifying into May 15, reaching severe cyclonic storm status later that day. Tauktae began to parallel the coast of the Indian states of Kerala, Karnataka, Goa and Maharashtra, before rapidly intensifying into a very severe cyclonic storm, early on May 16. Early on May 17, Tauktae intensified into an extremely severe cyclonic storm, reaching its peak intensity soon afterward. Later that same day, Tauktae underwent an eyewall replacement cycle and weakened, before restrengthening as it neared the coast of Gujarat, making landfall soon afterward.
Cyclonic Storm Gulab and Severe Cyclonic Storm Shaheen were two tropical cyclones that caused considerable damage to South and West Asia during the 2021 North Indian Ocean cyclone season. Gulab impacted India and Pakistan, while Shaheen impacted Iran, Oman and the United Arab Emirates. Gulab was the third named storm of the 2021 North Indian Ocean cyclone season, as well as the fourth named storm of the season after its reformation in the Arabian Sea as Shaheen. The cyclone's origins can be traced back to a low-pressure area situated over the Bay of Bengal on September 24. The Pakistan Meteorological Department got turn to name this new cyclone that has formed and named it Gulab by the IMD. On September 26, Gulab made landfall in India's Andhra Pradesh but weakened overland, before degenerating into a remnant low on September 28. The system continued moving westward, emerging into the Arabian Sea on September 29, before regenerating into a depression early on September 30. Early on October 1, the system restrengthened into a Cyclonic Storm, which the IMD named Shaheen. The system gradually strengthened as it entered the Gulf of Oman. While slowly moving westward, the storm turned southwestward, subsequently making an extremely rare landfall in Oman on October 3, as a Category 1-equivalent cyclone. Shaheen then rapidly weakened, before dissipating the next day.
The 2021 South India floods are a series of floods associated with Depression BOB 05 and a low pressure system that caused widespread disruption across the Indian states of Tamil Nadu, Andhra Pradesh, and the nearby Sri Lanka. The rainfall started on 1 November in Tamil Nadu. The flooding was caused by extremely heavy downpours from BOB 05, killing at least 41 people across India and Sri Lanka.
Cyclonic Storm Jawad was a weak tropical cyclone that caused disruptions over the East India and Bangladesh while bringing heavy rainfall and strong winds over these states as a weakened system. The tenth depression, sixth deep depression and fifth cyclonic storm of the active 2021 North Indian Ocean cyclone season, its predecessor was first tracked by Joint Typhoon Warning Center (JTWC) in the South China Sea as an area of low pressure. It then moved west-northwestwards into the Gulf of Thailand, where it crossed into the Andaman Sea by December 1. Near midnight of that day, the JTWC issued a TCFA on the system and on the next day, the India Meteorological Department (IMD) upgraded the system to a depression after passing through the Nicobar Islands. Further intensification ensued as the depression tracked through environmental conditions favorable for strengthening, and the system was upgraded into a deep depression on December 3 and into a cyclonic storm by 06:00 UTC that day, with the IMD naming it Jawad. However, this intensification was short-lived, as the system weakened to a deep depression back due to wind shear.
The 2023 North Indian Ocean cyclone season was a very active season, featuring the 2nd highest ACE on record for the basin, only behind 2019. It was an event in the annual cycle of tropical cyclone formation. The North Indian Ocean cyclone season has no official bounds, but cyclones tend to form between April and December, with the peak from May to November. These dates conventionally delimit the period of each year when most tropical cyclones form in the northern Indian Ocean. However, a cyclone can form at any time during the year shown by an unnamed depression that affected Sri Lanka in January-February.
Severe Cyclonic Storm Asani was a strong tropical cyclone that made landfall in India in May 2022. It was the strongest storm of 2022 North Indian Ocean cyclone season. The third depression and deep depression, and the first named storm of the 2022 North Indian Ocean cyclone season, Asani originated from a depression that the Indian Meteorological Department first monitored on May 7. Conditions rapidly favored development as the system became a deep depression by that day before intensifying to a Cyclonic Storm Asani. On the next day it further intensified and peak to a severe cyclonic storm, before making landfall as a deep depression system over Andhra Pradesh. It degenerated into a well marked low-pressure on May 12.
Severe Cyclonic Storm Mandous was the third cyclonic storm, as well as the third most intense tropical cyclone of the 2022 North Indian Ocean cyclone season. The remnants of the system later regenerated into Deep Depression ARB 03 in the Arabian Sea. The system struck the Andaman and Nicobar Islands, as well as South India.
1 2 Nalla Babu (December 4, 2021). "Relief for north coastal Andhra Pradesh as cyclone Jawad weakens into deep depression". The Times of India. Archived from the original on December 4, 2021. Retrieved December 5, 2021. A 17- year-old girl, identified as G Indu, died after a coconut tree uprooted and fell on her due to the strong winds at Meliaputti village Mandal in Srikakulam district on Saturday morning.
This page is based on this Wikipedia article Text is available under the CC BY-SA 4.0 license; additional terms may apply. Images, videos and audio are available under their respective licenses.
