2020 North Indian Ocean cyclone season

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

2020 North Indian Ocean cyclone season
First system formed May 16, 2020
Last system dissipated December 5, 2020
Strongest storm1 Amphan – 920 hPa (mbar), 240 km/h (150 mph) (3-minute sustained)
Depressions 9
Deep depressions 6
Cyclonic storms 5
Severe cyclonic storms 4
Very severe cyclonic storms 3
Super cyclonic storms 1
Total fatalities 269 total
Total damage > $16 billion (2020 USD)
(Costliest North Indian Ocean cyclone season on record)
1Strongest storm is determined by lowest pressure
North Indian Ocean tropical cyclone seasons
2018, 2019, 2020, 2021, 2022
Related article

The 2020 North Indian Ocean cyclone season was the costliest North Indian Ocean cyclone season on record, mostly due to 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 scope of the season 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 the basin is the India Meteorological Department (IMD), while the United States's Joint Typhoon Warning Center (JTWC) releases unofficial advisories. On average, three to four cyclonic storms form in this basin every season.[1]

Season summary

The season began on May 16 with the designation of Depression BOB 01 in the Bay of Bengal, which later became Cyclone Amphan, the strongest storm in the Bay of Bengal recorded since the 1999 Odisha cyclone and breaking the record of Cyclone Nargis of 2008 as the costliest storm ever recorded in the basin. Two more cyclones formed in the Arabian Sea, ARB 01, affecting Yemen and Oman, and Cyclone Nisarga, which made landfall in Maharashtra. After a four-month pause of activity, BOB 02 formed, causing 98 fatalities. Its remnants formed ARB 03. It was a weak storm. After 2 days, BOB 03 formed, impacting and affecting West Bengal, Bangladesh and Northeast India. It was also a weak storm, lasting for 2 days. After its break, Cyclone Gati formed, leaving 8 confirmed, 30 missing as of today, on Somalia and Yemen, where the cyclone took place. On November 23, a depression formed in the Bay of Bengal, and it strengthened into Very Severe Cyclonic Storm Nivar, two days later. It made landfall between Puducherry and Chennai close to Mahabalipuram in the midnight of November 25. It weakened into a well marked low pressure in the early hours of November 27. On November 28, a low pressure formed off the coast of Tamil Nadu, it gradually intensified into a depression, BOB 05. It later intensified into a deep depression and then into a cyclonic storm, named Cyclone Burevi. It made landfall on Sri Lanka as a weak cyclonic storm before it degenerated to an area of low pressure.

Systems

Super Cyclonic Storm Amphan

Super cyclonic storm (IMD)
Category 5 tropical cyclone (SSHWS)
150px 150px
Duration May 16 – May 20
Peak intensity 240 km/h (150 mph) (3-min)  920 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Cyclone Amphan

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

See also: Effects of Cyclone Amphan in India

At 00:00 UTC on May 16, a depression formed in the southeast Bay of Bengal and was identified as BOB 01. Six hours later, the India Meteorological Department (IMD) upgraded the system to a deep depression. The system began bringing torrential rainfall to Sri Lanka and Southern India. Around 15:00 UTC, the system further developed into Cyclonic Storm Amphan.[2][3] That morning, landslide and flooding warnings were hoisted for parts of eastern Sri Lanka and the Indian state of Kerala were given expectations of torrential rainfall in the coming days.[4] By 09:00 UTC on May 17, Amphan had intensified into a very severe cyclonic storm. Within 12 hours, the storm had developed an eye and started to rapidly intensify, becoming an extremely severe cyclonic storm. According to the JTWC, it explosively intensified from a Category 1-equivalent cyclone to a Category 4-equivalent cyclone in just 6 hours. The following morning around 10:30 UTC, the IMD upgraded Amphan to a super cyclonic storm with 3-minute sustained winds of 240 km/h (150 mph) and a minimum pressure of Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value).. This marked the second year in a row featuring a super cyclonic storm, the previous year seeing Kyarr in the Arabian Sea. On May 20, at approximately 17:30 IST, the cyclone made landfall near Bakkhali, West Bengal after weakening subsequently. It rapidly weakened once inland, and dissipated on the next day. It left behind a trail of catastrophic damage, and was later confirmed to be the costliest storm ever recorded in the basin.

Depression ARB 01

Depression (IMD)
150px 150px
Duration May 29 – May 31
Peak intensity 45 km/h (30 mph) (3-min)  1000 hPa (mbar)

A depression formed overland near Salalah, Oman on May 29.

The Public Authority for Civil Aviation (PACA) in Oman advised residents to exercise caution and not to venture to low-lying areas or sea. The Supreme Committee asked people to remain at home in non-emergency circumstances.[5] The hospital in Sadah was evacuated as the depression intensified.[6] Over 200 mm (7.9 in) of rain fell in Dhofar Governorate on May 29;[7] some areas received the equivalent of 2 years of rainfall.[8] The highest precipitation total was measured in Mirbat, where 1,055 mm (41.5 in) of rain fell.[9] 2 days of heavy rainfall, accumulating to 260 mm (10 in), caused floods in Salalah.[10] Operations at the port of Salalah were interrupted by the tropical depression.[11] Residents in central Salalah experienced disruptions to power and water services. Military police were dispatched to clear roads and airlift people marooned by the floods.[12] Engineering teams from the Ministry of Defence were deployed to restore utilities and render air where necessary.[13] 2 people were found dead in a wadi due to flash floods,[14] while another person died and three were injured when a building collapsed.[8] More than 50 people were rescued from floods.[15]

Severe Cyclonic Storm Nisarga

Severe cyclonic storm (IMD)
Category 2 tropical cyclone (SSHWS)
150px 150px
Duration June 1 – June 4
Peak intensity 110 km/h (70 mph) (3-min)  984 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Cyclone Nisarga

During May 31, an area of low pressure developed over the south-eastern Arabian Sea and remained as a well marked low-pressure area over the same region until the evening. It strengthened into a depression over the east-central and south-east Arabian Sea in the early morning of June 1 when it was centered about 340 km south-west of Goa, 630 km south-southwest of Mumbai and 850 km south-southwest of Gujarat. It gave nearly 400 mm of extremely heavy rain at Kavaratti, Lakshadweep. On June 2, around noon, the prevailing deep depression intensified into a cyclonic storm thereby receiving the name Nisarga. The name has been contributed by Bangladesh. Nisarga intensified into a severe cyclonic storm before making landfall near the coastal town of Alibag in Maharashtra at 12:30 (IST) on June 3. At the time, the system was at peak intensity with 3-minute sustained winds of 110 km/h (70 mph) and a central pressure of Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value).. The cyclone subsequently weakened into a deep depression by June 4.[16][17]

Deep Depression BOB 02

Deep depression (IMD)
150px 150px
Duration October 11 – October 14
Peak intensity 55 km/h (35 mph) (3-min)  999 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Further information: 2020 Hyderabad floods

After 3 months of inactivity, on October 11, a depression developed over the west-central Bay of Bengal, though the system was originally observed near the Spratly Islands over the South China Sea on October 6. It continued to move westwards, making landfall in the Khánh Hòa province and further weakened into a low pressure cell while crossing the Indochina Peninsula and re-emerged in the Andaman Sea on October 9. It intensified into a well-marked low-pressure area and then into a depression over the Bay of Bengal on October 10. It further intensified into a deep depression on October 12, remaining practically stationary over the same region.[18][19] After that, BOB 02 moved west-northwestwards and made landfall in Andhra Pradesh near Kakinada in the early hours of October 13 and weakened again into a depression.[20]

Due to BOB 02, Yanam (Puducherry), Andhra Pradesh, Telangana, Kerala, Maharashtra, and coastal Karnataka experienced heavy rain on October 12 and 13, with Hyderabad experiencing 32 cm of record-breaking torrential rain, creating flash floods in the city by October 13. At least 50 people died in different parts of Telangana (of which at least 19 were in the capital city of Hyderabad), 10 in Andhra Pradesh, and 38 in Maharashtra.[21] Extreme crop loss in north Karnataka, Andhra Pradesh and Telangana occurred due to the system. The Telangana CM estimated damage costs to be ₹1,305 crore (US$682 million).[22] The system weakened into a well-marked low-pressure area in south-central Maharashtra on the evening of October 14.[23] Though the system's lower-level circulation was partially exposed due to high vertical wind shear and continuous land interaction, the JTWC re-issued a tropical cyclone advisory on October 15. The IMD also forecasted BOB 02 to reintensify in the Arabian Sea.[24][25] The low-pressure area intensified into Depression ARB 03 on the early hours of October 17.[26]

The system delayed the withdrawal of the southwest monsoon season by almost a week, a delay compounded by the formation of Depression ARB 03 and Depression BOB 03.[27]

Depression ARB 03

Depression (IMD)
150px 150px
Duration October 17 – October 19
Peak intensity 45 km/h (30 mph) (3-min)  1000 hPa (mbar)

On October 17, the remnants of Deep Depression BOB 02 intensified into a depression in the East Central Arabian Sea. Moving westwards, the system dissipated into a well marked low pressure on the morning of October 19 over the West Central Arabian Sea due to unfavorable atmospheric conditions. Fishermen were advised not to go out to sea due to very rough sea conditions. Heavy rainfall occurred off the coast of Mumbai and its surroundings due to the system. No warnings were issued by IMD as no landfall occurred in the Arabian Peninsula.[28]

Monsoon withdrawal was delayed in Maharashtra by a week due to ARB 03.[29]

Depression BOB 03

Depression (IMD)
150px 150px
Duration October 22 – October 24
Peak intensity 45 km/h (30 mph) (3-min)  1000 hPa (mbar)

On October 20, a low pressure formed over Central Bay of Bengal. The system then became more well-marked on October 21 over West Central Bay of Bengal. It further intensified into depression over northwest Bay of Bengal and adjoining Odisha Coast. The system crossed West Bengal's North 24 Parganas and South 24 Parganas and moved over the adjoining Bangladeshi coast on the noon of October 23 with the maximum wind speed of 45 km/h (30 mph). The system weakened into a well marked low-pressure area, 50 km north-northwest of Dhaka on the morning of October 24.[30][31]

Very Severe Cyclonic Storm Gati

Very severe cyclonic storm (IMD)
Category 3 tropical cyclone (SSHWS)
150px 150px
Duration November 21 – November 24
Peak intensity 140 km/h (85 mph) (3-min)  976 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Cyclone Gati

On November 17, the India Meteorological Department (IMD) noted the potential for tropical cyclogenesis over the central Arabian Sea in association with an area of low pressure near the Maldives.[32] Convective activity was enhanced by the Madden–Julian oscillation while sea surface temperatures of 29 to 30 °C (84 to 86 °F) and low wind shear favored additional development.[33][34] By November 18, a weak low-level circulation developed about 1,185 km (735 mi) east-southeast of Socotra.[34] Organization thereafter was stymied as it became embedded within a monsoon trough. Two additional circulations developed to the east and west of the original low; however, the original low steadily became the dominant system by absorbing the previous two circulations.[35] On November 21, two scatterometer passes revealed a single, well-defined low with gale-force winds underneath an area of flaring convection.[36] At 18:00 UTC, the IMD classified the system as Depression ARB 04 about 410 km (255 mi) east-southeast of Socotra.[37] Similarly, the Joint Typhoon Warning Center (JTWC) initiated advisories on the system as Tropical Cyclone 03A. Steered west by a subtropical ridge to the north, little intensification was expected before the cyclone's forecast landfall in Somalia.[36]

During the overnight of 21 to November 22 the small cyclone quickly organized,[38] with a well-defined eye developing.[39] The IMD upgraded the system to a Deep Depression early on November 21 and a Cyclonic Storm soon after. Upon becoming a cyclonic storm, it was assigned the name Gati.[40][41] Classified as a "midget system" by the JTWC with a core diameter of only 120 km (70 mi) and a 27 km (17 mi) wide eye, Gati explosively intensified that morning.[42] Within a 12-hour period, the JTWC estimated one-minute sustained winds to have increased from 65 km/h (40 mph) to a peak of 185 km/h (115 mph). This was the fastest intensification during such a short period ever observed in the North Indian Ocean basin. The system's small size enabled it to take advantage of low wind shear and high sea surface temperatures.[43] The IMD assessed Gati to have reached its peak intensity as a Very Severe Cyclonic Storm around 12:00 UTC, with three-minute sustained winds of 140 km/h (85 mph) and a minimum pressure of Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value)..[44] Six hours later, Gati had made landfall near Hafun in northeastern Somalia with estimated one-minute sustained winds of 165 km/h (105 mph).[43] This made Gati the first hurricane-force cyclone to strike the country since reliable records began and by default the nation's strongest.[43]

Once onshore, land friction-based shear caused convection to quickly become displaced from the storm's center.[45] The low-level circulation became completely exposed early on November 23 as it traversed northeastern Somalia; the system's upper-level circulation and associated convection detached and accelerated west ahead of the surface low.[46] The increasingly elongated circulation of Gati emerged over the Gulf of Aden by 12:00 UTC,[47] and the JTWC issued their final advisory on the system shortly thereafter.[48]

Very Severe Cyclonic Storm Nivar

Very severe cyclonic storm (IMD)
Category 1 tropical cyclone (SSHWS)
150px 150px
Duration November 23 – November 27
Peak intensity 120 km/h (75 mph) (3-min)  980 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Cyclone Nivar

On November 22, an area of low pressure was formed in the Bay of Bengal, off the coast of Tamil Nadu. On the same day, the JTWC issued a Tropical Cyclone Formation Alert on the disturbance. It intensified into a depression on the early hours of November 23, as the JTWC also cited that the disturbance intensified into a tropical storm, designating it as Tropical Cyclone 04B.[49] Early on November 24, it intensified into a cyclonic storm and it was named Nivar. It gradually intensified into a Very Severe Cyclonic Storm, reaching its peak intensity. Due to the wind shear, it weakened to a Severe cyclonic storm, shortly before making landfall between Karaikal and Mamallapuram around Puducherry(also known as Pondicherry), Wednesday evening. It reemerged on the Bay of Bengal as a strong deep depression before making its last landfall at Andhra Pradesh before weakening to a well marked low pressure on the morning of November 27. The name Nivar was contributed by Iran which means light.

The IMD issued cyclone warnings early on November 24 on Tamil Nadu, Pondicherry and the country of Sri Lanka as the cyclonic storm accelerates and intensifies.

Cyclonic Storm Burevi

Cyclonic storm (IMD)
Tropical storm (SSHWS)
150px 150px
Duration November 30 – December 5
Peak intensity 85 km/h (50 mph) (3-min)  996 hPa (mbar)

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: Cyclone Burevi

On November 28, a low-pressure area formed off the coast of Aceh. It gradually intensified into a depression on November 30.[50] The JTWC then issued a Tropical Cyclone Formation Alert on the system, that same day.[51] At 03:00 UTC on December 1, the depression was upgraded into a deep depression.[52] At 15:00 UTC, both the IMD and JTWC upgraded it to a cyclonic storm and tropical storm respectively and it was named Burevi, the fifth named storm of the season.[53][54] The name was initially suggested by the Maldives.[55] At this time, microwave imagery showed well-defined convective banding wrapping tightly around the low-level circulation (LLCC).[56] At 15:00 UTC on December 2, Burevi reached its peak intensity with 1-minute sustained winds of around 85 km/h (55 mph) and a barometric pressure of 996 mbar (29.41 inHg).[57] Shortly afterwards, Burevi made landfall along the east coast of Sri Lanka according to the Sri Lanka's Department of Meteorology.[58]

After weakening over Sri Lanka, Burevi exited into the Gulf of Mannar, early on December 3.[59] However, Burevi slowed down quickly as it became stuck in a col between two subtropical ridges on December 4; thus it stalled just west of Sri Lanka while it weakened back down to the equivalent of a tropical depression due to increasing vertical wind shear.[60] At 06:00 UTC on December 5, Burevi degenerated into an area of low pressure according to the IMD.[61]

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 65 km/h (40 mph). The names were selected by members of the ESCAP/WMO panel on Tropical Cyclones between 2000 and May 2004, before the Regional Specialized Meteorological Center in New Delhi started to assign names in September 2004. 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 next eight names from the list of North Indian Ocean storm names are listed below. Amphan is the last name from the original naming list published in 2004, while Nisarga is the first name from the new naming list published in 2020.

Season effects

This is a table of all storms in the 2020 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 2020 USD.

Name Dates active Peak classification Sustained
wind speeds		 Pressure Land areas affected Damage
(USD)		 Deaths Refs
Amphan May 16 – 21 Super cyclonic storm 240 km/h (150 mph) Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). West Bengal, Odisha, Bangladesh, Sri Lanka, Bhutan $13.6 billion 128 [62]
ARB 01 May 29 – 31 Depression 45 km/h (30 mph) Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). Oman, Yemen Unknown 3 [8]
Nisarga June 1 – 4 Severe cyclonic storm 110 km/h (70 mph) Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). Maharashtra, Goa $803 million 6 [63]
BOB 02 October 11 – 14 Deep depression 55 kilometres per hour (34 mph) Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). Andhra Pradesh, Puducherry, Telangana, Kerala, Karnataka, Goa, Maharashtra $681 million 98 [64][21]
ARB 03 October 17 – 19 Depression 45 km/h (30 mph) Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). Maharashtra None None
BOB 03 October 22 – 24 Depression 45 km/h (30 mph) Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). West Bengal, Bangladesh, Northeast India None None
Gati November 21 – 24 Very severe cyclonic storm 140 km/h (85 mph) Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). Somalia, Yemen, Djibouti $1 million 9 [65][66]
Nivar November 23 – 27 Very severe cyclonic storm 120 km/h (75 mph) Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). Sri Lanka, Andhra Pradesh, Tamil Nadu, Puducherry $600 million 14
Burevi November 30  – December 5 Cyclonic storm 85 km/h (55 mph) Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). Sri Lanka, Tamil Nadu, Kerala Unknown 11
Season Aggregates
9 systems May 16  – December 5 240 km/h (150 mph) Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). $16 billion 269

See also

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ 8.0 8.1 8.2 Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ 34.0 34.1 Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ 36.0 36.1 Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ 43.0 43.1 43.2 Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ Lua error in package.lua at line 80: module 'strict' not found.[permanent dead link]
  52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  57. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ Lua error in package.lua at line 80: module 'strict' not found.[permanent dead link]
  65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=2020_North_Indian_Ocean_cyclone_season&oldid=726568795"