The 1980 Pacific typhoon season was a slightly-below average season when compared to the long-term average, though it featured several intense storms. It ran year-round in 1980, but most tropical cyclones formed between June and December. These dates conventionally delimit the period of each year when most tropical cyclones form in the northwestern Pacific Ocean. A total of 28 tropical depressions formed this year in the Western Pacific, of which 24 became tropical storms and were assigned a name by the Joint Typhoon Warning Center. Beginning in March, tropical cyclones formed in each subsequent month through December. Of the 24 named storms, 15 storms reached typhoon intensity, of which 2 reached super typhoon strength.
Additionally, tropical depressions that enter or form in the Philippine area of responsibility are assigned a name by the Philippine Atmospheric, Geophysical and Astronomical Services Administration or PAGASA. This can often result in the same storm having two names. This year, 23 storms were named this way.
Thie 1980 Pacific typhoon season's ACE index was approximately 237.8units,[4] This number represents the sum of the squares of the maximum sustained wind speed (knots) for all tropical cyclones of at least tropical storm intensity, divided by 10,000. Therefore, tropical depressions are not included.[5]
On 2 April, a tropical disturbance located east of the International Date Line began developing alongside a parallel cyclone, the precursor to Cyclone Wally, both inside the near-equatorial trough. Steadily tracking west, later that day, Carmen intensified into a tropical storm. A few hours later, as the system crossed east of the Date Line on 5 April, the JTWC issued their first warning on the system.[6] Later that day, the JMA designated the system as a tropical storm,[7] with the JTWC following suit a few hours later, naming it Carmen.[6] Steadily intensifying, the next day, both the JTWC and JMA stated that Carmen peaked with sustained winds of 60 knots (110km/h; 70mph).[7][6] Soon after, Carmen steadily weakened, and after tracking east of the Date Line on 7 April, both the JTWC and JMA stopped tracking the system.[6][7]
On 5 May, a weak tropical disturbance began developing in the near-equatorial trough. As it tracked westward across the Caroline Islands in the following three days, little development was seen.[8] Despite that, on May 7, the Japan Meteorological Agency designated the disturbance as a tropical depression.[7] The next day, an uptick in convective activity prompted the JTWC to issue a TCFA on the system, which was south of Guam. As the circulation steadily organized, the JTWC upgraded the system into a tropical depression.[8] Two days later, the depression crossed into the Philippine Area of Responsibility (PAR), causing the Philippine Atmospheric, Geophysical, and Astronomical Services Administration (PAGASA) to name it Ditang.[3] Despite intense vertical shear, the depression intensified into a tropical storm a few hours later, being named Dom by the JTWC.[8] After the wind shear relaxed, on May 11, the JTWC stated that Dom had intensified into a typhoon, with the JMA following suit the next day.[8][7] Soon after, Dom began weakening due to the mountainous terrain of Luzon, becoming a tropical storm on May 14. However, as Dom traced eastward, the next day, it re-intensified into a typhoon.[8]
After this secondary peak, a combination of colder SSTs and unfavorable atmospheric conditions caused the system to steadily weaken, and after doing an anticyclonic loop, on May 18, Dom weakened into a tropical storm. The next day, the JTWC issued their last advisory on Dom, declaring that it had degenerated into a post-tropical cyclone.[8] PAGASA kept tracking the system until May 21,[3] when the remnants of Dom and a weakening Ellen began accelerating towards an extratropical cyclone south of Japan.[8] The remnants of Dom and Ellen later merged with the cyclone the same day,[8] causing the JMA to finally stop monitoring Dom a few hours later.[7]
On 11 May, a tropical disturbance located in an equatorial trough east of Chuuk Lagoon began developing. Despite initially showing signs of weakening, the next day, it rapidly developed, becoming a tropical storm a few hours later, causing both the JTWC and JMA to issue their first advisories early on 13 May, with the former naming it Ellen.[13][7] Slightly weakening for a few hours, on May 15, Ellen rapidly intensified, becoming a typhoon a few hours later. Soon after, Ellen deepened signficantly, reaching a minimum pressure of 930mbar (27inHg) later that day.[7] The next day, the JMA noted that Ellen had peaked with 10-minute sustained winds of 105kn (120mph; 195km/h)[7] while the JTWC stated that Ellen peaked with 1-minute sustained winds of 110kn (125mph; 205km/h).[13] Shortly after, Ellen began recurving northwest towards Japan, weakening as it neared the extratropical cyclone which absorbed Dom. On 21 May, Ellen merged with the cyclone, causing the JTWC to stop tracking it.[13] The JMA kept tracking it until 25 May.[7]
As Ellen made its closest approach to Japan, Yokosuka saw gusts of 30–35kn (35–40mph; 56–65km/h).[7] Heavy rainfall from Ellen affected western and central Japan, causing around 60 landslides and flooding almost 300 homes.[11]
On 16 May, a tropical disturbance began developing west of Kosrae.[14] Three days later, the JMA designated the disturbance as a tropical depression,[7] with the JTWC issuing a TCFA on the system just a few hours after.[14] The next day, both the JMA and JTWC designated the depression as a tropical storm, with the latter agency naming it Forrest.[7][14] On 22 May, Forrest crossed into the PAR, being named Gloring by PAGASA.[3] Steadily developing, the next day, both the JMA and JTWC noted that Forest had peaked with sustained winds of 55kn (65mph; 100km/h).[7][14] After making landfall in Luzon on 25 May, Forrest rapidly weakened,[14] and on 26 May, both PAGASA and the JTWC stopped tracking Forrest.[3][14] The JMA kept tracking a weakening Forrest until it dissipated on 29 May.[7]
On 19 May, a monsoon depression embedded in the South China sea began developing.[15] A few hours later, the JMA designated the weak circulation as a tropical depression, while the JTWC issued a TCFA on it.[7][15] Barely developing, on 21 May, the system began featuring some convective activity, causing the JTWC and PAGASA to designate the system as a depression, with the latter agency naming it Edeng.[3][15] The next day, Edeng left the PAR, causing PAGASA to stop tracking the system.[3] Soon after, both the JMA and JTWC designated the system as a tropical storm, with the latter naming it Georgia.[7][15] After making landfall in Shantou on 23 May with sustained winds of 55kn (65mph; 100km/h), Georgia rapidly weakened, causing the JTWC to stop monitoring it the next day.[15] The JMA followed suit the next day.[7]
As Georgia made its closest approach to Hong Kong, some stations recorded intense gusts, with Stanley recording a gust of 73kn (84mph; 135km/h). Additionally, light rainfall was seen. With the exception of some scaffolding blown off in Tai Kok Sui Road, no damage occurred.[16]
In mid-June, an equatorial trough was active, stretching from the Philippines to the eastern Caroline Islands near the equator. On 20 June, satellite imagery indicated increased convective activity around the eastern periphery of the trough as a result of convergent easterly flow. As a result, a TCFA was issued on the area of convective activity.[17] The next day, the disturbance was designated a depression by PAGASA, who named it Huaning.[3] Making landfall in Leyte, Philippines the next day,[17] the JMA designated the system as a tropical depression.[7] However, landfall prevented further development, causing the TCFA to be cancelled later that day.[17] However, after tracking westwards for several days, on 24 June, the JTWC reissued a TCFA. Several hours later, both the JTWC and JMA designated Huaning as a tropical storm,[17][7] with the former agency naming it Herbert.[17]
In the South China Sea, Herbert tracked northwestward toward Hainan Island while intensifying slowly.[17] After exiting the PAR on 25 June, PAGASA stopped tracking the system.[3] Later that day, both agencies stated that Herbert peaked with sustained winds of 50kn (60mph; 95km/h).[17][7] Slightly weakening, at 1800Z the next day, Herbert made its landfall in Hainan with maximum sustained winds of 45kn (50mph; 85km/h).[17] After tracking into the Gulf of Tonkin, on 28 June, Herbert made its second landfall south of Jinzhou, China with sustained winds of 45kn (50mph; 85km/h).[17] Rapidly weakening, both the JTWC and JMA stopped tracking Herbert the next day.[17][7]
As Herbert made its closest approach to Hong Kong, some stations recorded moderate gales, with Tate's Cairn recording a gust of 48kn (55mph; 89km/h). Additionally, heavy rainfall was seen, flooding some roads and causing landslides. Two men died after their helicopter crashed into the slopes of Tai Mo Shan.[18] The Paracel Islands recorded peak winds of 46kn (53mph; 85km/h).[17]
On 5 July, a surface circulation began developing northwest of the Caroline islands.[19] Later that day, the JMA designated the system as a tropical depression.[7] Aerial reconnaissance caused the JTWC to issue a TCFA, and a few hours later, they designated the system as a tropical depression.[19] The next day, the system intensified into a tropical storm, causing PAGASA to name the system Lusing as it was in the PAR, while the JTWC named it Ida.[7][3][19] Steadily intensifying, on 9 July, the JMA stated that Ida peaked as a minimal typhoon[7] while the JTWC stated that it peaked as a high-end tropical storm.[19] Slightly weakening as it tracked into the Bashi Channel, on 11 July, Ida made landfall in Southeastern China,[19] causing PAGASA to stop tracking it.[3] The JMA stopped tracking the system four days later.[19]
As Ida was developing, The naval air station in Guam received over 1.15in (29mm) of rainfall in three hours.[19] Moderate rainfall was recorded in Hong Kong.[20] In the Philippines, some damage was recorded.[21]
An area of disturbed weather developed over the Caroline Islands on July14. Tracking westward, convective activity gradually increased in both convection and coverage.[22] At 18:00 UTC on July 22, the Japan Meteorological Agency (JMA) started tracking the system.[7] By 00:00UTC on July17, the surface center and the deep convection moved closer together, prompting the JTWC to classify the system as a tropical depression.[22] Meanwhile, PAGASA tracked the storm and named it Nitang.[3]
The depression began to develop at a quicker pace, and early on July18, the JTWC upgraded it to a tropical storm.[22] After Joe developed a central dense overcast, the JMA upgraded Joe into a severe tropical storm.[7] At midday, the JTWC and JMA upgraded Joe into a typhoon.[7][22] This intensity estimate was confirmed by a Hurricane hunter plane later on July19, which measured a pressure of 974mbar (28.8inHg). An eye began to clear out on July 20. That same day, a Hurricane hunter aircraft recorded a pressure of 940mbar (28inHg). At midday, the JTWC estimated that Joe peaked in intensity, with winds of 195km/h (120mph), equal to a Category3 hurricane on the United States-based Saffir-Simpson Hurricane Wind Scale (SSHWS). Meanwhile, the JMA estimated maximum intensity of 160km/h (100mph).[7][22]
Six hours after its peak, Joe made landfall in central Luzon.[22] At the time of landfall, the JMA indicated winds of 90mph (145km/h).[7] Over land, Joe weakened rapidly, falling to tropical storm strength according to the JTWC.[22] After entering the South China Sea on July21, Joe began to re-intensify; data from the JTWC suggested that Joe regained typhoon intensity almost immediately thereafter.[22] Around this time, the JMA estimated that Joe reached its secondary peak of 135km/h (85mph).[7] On July22, the JTWC estimated that Joe attained a secondary peak of 170km/h (105mph). Despite maintaining its structure[22] as it tracked over the Leizhou Peninsula, the storm weakened as it entered the Gulf of Tonkin and approached the coast of Vietnam.[22] Both the JTWC and JMA agree that Joe had winds of 130km/h (80mph) when it moved ashore near Haiphong in Vietnam later on July22.[22][7] A combination of land interaction and vertical wind shear resulted in rapid weakening. At 00:00 UTC on July23, the JTWC issued its last warning on Joe. The remnants of Joe later moved into Laos.[22] The JMA stopped watching Joe on July24.[7]
Across the Philippines, 31citizens were killed,[23] In Vietnam, 130people were killed, 300,000others were directly affected, and 165,000others lost their homes.[23] Two large ships, a 20,000 short tons (18,145t) liner and a 50,000 short tons (45,360t) tanker, were washed ashore in Chankiang.[24] Throughout the area, 188people were killed and at least 100others were left homeless.[23]
An area of disturbed weather developed in association with the monsoon trough on July19. Later tht day, the JTWC issued a TCFA on the system as the disturbance was over warm water and low wind shear.[25] Four hours later, the JMA classified the system as a tropical depression,[7] with the JTWC following suit early the next day.[25] Early the next day, both the JTWC[25] and JMA[7] upgraded the depression into a tropical storm, with the former agency naming it Kim.[25] Further intensification was slow to occur as Kim tracked in the area where Typhoon Joe had previously trekked. However, on July23, a hurricane hunter aircraft indicated falling pressures and the beginning of an eyewall.[25] Based on this, both the JTWC and JMA announced that Kim obtained typhoon intensity.[7][25] Around this time, Kim tracked into the PAR, causing PAGASA to name it Osang.[3] Continuing to track west-northwest beneath a large subtropical ridge,[25] Kim began to clear out an eye on the evening of July 23;[26] subsequently, Kim entered a period of rapid deepening.[25]
At July24, the JTWC increased the intensity of Kim to 185km/h (115mph),[25] while the JMA raised the winds to 170km/h (105mph).[7] Ten hours later, a Hurricane hunter aircraft measured a pressure of 908mbar (26.81inHg), causing the JTWC to declare Kim a super typhoon[25] and increasing the wind speed to 240km/h (150mph). At 18:00on July24, the JMA estimated that Kim reached its peak intensity to 170km/h (105mph).[7] Almost immediately thereafter, reports from the same Hurricane Hunter aircraft indicated that the pressure of the typhoon rose sharply, likely in response to decreased inflow caused by Kim's close proximity to land. The JTWC estimated that Kim made landfall along the coast of Luzon with sustained winds of 185km/h (115mph),[25] while the JMA reported that Kim moved ashore with winds of 145km/h (90mph).[7] Continuing to weaken due to land interaction, Kim weakened into a tropical storm as it emerged into the South China Sea,[25][7] On July27, a weakening Kim crossed the coastline of China around 165km (105mi) northeast of Hong Kong.[25] At the time of its second landfall, both the JTWC and JMA estimated winds of 80km/h (50mph).[7][25] Twelve hours later, both the JTWC[25] and JMA ceased tracking Kim.[7]
Typhoon Kim caused widespread flooding across Luzon. In Manila, where floodwaters rose to more than 610mm (24in) in some suburbs, government offices and schools were closed. There, both Philippine Airlines and Philippine National Railways canceled all trips to the rest of the country.[27] The coast guard suspended sailing permits to ships throughout the country.[28] The Isabela province was the hardest hit by Typhoon Kim.[29] Across the Philippines, 40people were killed,[30] 2 via drownings,[28] and 19,000others were affected.[30] The HKO observed 136.3mm (5.37in) of rain over a 72-hour period. Within the vicinity of Hong Kong, minor damage was reported and there were no injuries. Power was knocked out in the urban city of Kowloon. Some villages were flooded and two landslides occurred.[26]
On 24 July, a tropical disturbance which had recently spawned from a tropical upper tropospheric trough (TUTT) began developing.[31] Steadily tracking westward, two days later, the JMA designated the system as a tropical depression.[7] A few hours later, the JTWC issued a TCFA on the system as it steadily developed.[31] As the depression's satellite signature improved, the JTWC issued their first warning on it early the next day.[31] Twelve hours later, both the JTWC and JMA upgraded the system into a tropical storm, with the former agency naming it Lex.[7][31] Tracking northwestward and steadily intensifying, on July 31, both agencies upgraded Lex into a typhoon.[7][31] Soon after, Lex executed a cyclonic loop, later peaking with 1-minute sustained winds of 90mph; 150km/h (80kn)[31] and 10-minute sustained winds of 85mph; 140km/h (75kn) according to the JMA.[7] However, soon after, cold air from a deep surface low caused Lex to steadily weaken.[31] As a result, on 7 August, Lex transitioned into an extratropical low according to the JTWC.[31] The JMA kept monitoring Lex until 13 August.[7]
On 6 August, due to atmospheric instability caused by a weakening Lex, an area of convection west of the Marshall Islands began developing. By the next day, the disturbance had expanded significantly, with convection being consolidated near its center of circulation.[32] As a result on 8 August, both the JMA and JTWC designated Marge as a tropical storm, with the latter agency naming it Marge.[7][32] Soon after, due to a col and a weakness inside a ridge, Marge began tracking northward.[32] Steadily developing, on August 10, both the JTWC and JMA noted that Marge had intensified into a typhoon.[7][32] The next day, Marge peaked with 1-minute sustained winds of 125mph; 205km/h (110kn)[32] and 10-minute sustained winds of 105mph; 165km/h (90kn) according to the JMA.[7] Slightly weakening, on 13 August, Marge encountered strong upper-level westerlies, causing it to rapidly weaken.[32] As a result, the next day, Marge transitioned into an extratropical cyclone, causing the JTWC to stop tracking it.[32] The JMA kept tracking it until the next day, when it merged with a mid-latitude cyclone.[7][32]
On 15 August, a weak area of convection associated with a TUTT located over the Marshall Islands began slowly coalescing. Despite a nearby weak surface circulation initially hindering much development, on 23 August, the JTWC issued a TCFA on the system as the JMA designated the system as a tropical depression.[33][7] Steadily tracking west-northwestwards, the next day, the JTWC followed suit with upgrading it into a depression,[33] with PAGASA naming it Reming as it had crossed into the PAR.[3] On 25 August, both the JMA and JTWC designated the system as a tropical storm, with the latter agency naming it Norris.[33][7] After the surface circulation which had prevented Norris from strengthening dissipated early the next day, Norris intensified significantly, being recognized as a typhoon by both agencies the next day.[33][7] A few hours later, Norris peaked with sustained winds of 90kn (105mph; 165km/h) according to the JTWC[33] and 95kn (110mph; 175km/h)[7] prior to making a landfall in Northern Taiwan.[33] The mountainous ranges of Taiwan caused Norris to rapidly weaken, and by the time it made its second landfall south of Fuzhou on 28 August,[33] both the JTWC and JMA had reported that it had weakened into a tropical storm.[33][7] As a result, both PAGASA and the JTWC ceased tracking the system.[33][3] The JMA kept monitoring it until 31 August.[7]
As Norris passed just 10 nautical miles (12 miles; 19km) southwest of Yonaguni on 27 August, winds of 90kn (100mph; 170km/h) to the island. In Taiwan, gusts of 64kn (74mph; 119km/h) were recorded.[33] Flooding caused by the typhoon swept away 60 houses in Northern Taiwan, causing two deaths. Additionally, Norris caused four fishing vessels off the eastern coast of the island to capsize. Despite that, Norris primarily brought heavy rainfall, which eased Taiwan's worst drought since 1950.[34]
On 4 September, the JMA designated a tropical disturbance as a tropical depression.[7] Two days later, the JTWC began tracking it, issuing a TCFA on the developing system.[35] The next day, both the JMA and JTWC designated the system as a tropical storm, with the latter agency naming it Orchid.[35][7] Tracking west-northwest, as it crossed into the subtropical latitudes on 9 September, both the JMA and JTWc noted that Orchid had intensified into a typhoon.[35][7] Meanwhile, PAGASA temporarily tracked the system as it was in the PAR, naming it Toyang before the system left their area of responsibility the next day.[3] As Orchid executed three cyclonic loops from 9–10 September,[35] the JMA noted that Orchid had peaked with 10-minute sustained winds of 70kn (80mph; 130km/h) while the JTWC noted that Orchid had peaked with 1-minute sustained winds of 85kn (100mph; 155km/h).[7][35] The next day, Orchid made landfall in Japan, slightly weakening due to colder waters. As a result, the JTWC stopped tracking the system.[35] The JMA kept tracking the system until it dissipated on 16 September.[7]
As the depression initially coalesced, the JTWC issued a gale warning for Guam.[35] The ninth tropical cyclone to strike Japan during the season, Orchid killed six people in Kyushu and triggered devastating landslides on the country's main island of Honshu, causing crops to sustain heavy damage.[36] More than 15,000 people were affected due to the devastating landslides and wind gusts.[37] The MV Derbyshire, a ship which was headed for Kawasaki with iron ore from Sept-Îles, Canada on July 11, was sunk by Orchid.[38] All 44 people on board died.[39] In South Korea, Orchid caused at least three deaths, leaving over a hundred fishermen missing.[35]
On 11 September, a monsoon depression in the South China Sea which was embedded in the monsoon trough started developing.[40] As it tracked quasi-stationary for the next two days,[40] early on 12 September, the JMA designated the system as a tropical depression.[7] Soon after, sypnotic data revealed that the system's circulation was developing, causing the JTWC to follow suit in upgrading it into a depression early the next day.[40] Later that day, the JTWC noted that the tropical depression had intensified into a tropical storm, naming it Ruth.[40] The JMA later followed suit early the next day.[7] Tracking northwestward, a few hours later, Ruth made landfall in Hainan Island with 1-minute sustained winds of 45kn (50mph; 85km/h).[40] Weakening, as it entered the Gulf of Tonkin early on 15 September, it became a minimal tropical storm.[40]
The warm waters of the Gulf of Tonkin, which were 29°C (84°F) as the weak cyclone tracked into there, enabled Ruth to signifcantly intensify.[40] As a result, according to the JTWC, Ruth underwent rapid intensification, peaking as a minimal typhoon with 1-minute sustained winds of 65kn (75mph; 120km/h).[40] The JMA, however, stated that Ruth peaked with 10-minute sustained winds of 55kn (65mph; 100km/h) at that time.[7] Just a few hours later, early on 16 September, Ruth made landfall south of Thanh Hóa, Vietnam at peak intensity.45kn (50mph; 85km/h)[40] Rapdily weakening, a few hours later, the JTWC stopped tracking Ruth, claiming it had dissipated.[40] The JMA kept tracking a weakening Ruth until September 17,[7] with the remnants dissipating in Bilauktaung Range the next day.[40]
In Vietnam, nearly half a million people were left homeless with 106 people dead or missing.[40] The worst typhoon to strike Thanh Hoa province in 30 years,[41] a 2022 report from GeoHazards stated that from 1970 to 2018, Ruth was the tropical cyclone which caused the most crop damage in the area.[42] Tens of thousands of buildings were inundated, and a total of 164 people died due to Ruth.[43]
On 13 September, a tropical disturbance located at the base of a mid-tropospheric trough extending south of Japan began developing.[44] Around the time that the JTWC was tracking it, the JMA designated the system as a tropical depression.[7] The next day, both the JMA and JTWC recognized the system as a tropical storm, causing the JTWC to name it Percy.[7][44] Additionally, Percy crossed into the PAR, causing PAGASA to name it Undang.[3] Soon after, Perry executed two cyclonic loops, being upgraded into a typhoon by both the JTWC and JMA on 16 September.[44][7] The next day, an aircraft fix revealed that according to the JTWC, Percy had peaked with 1-minute sustained winds of 125kn (145mph; 230km/h).[44] A few hours later, the JMA noted that Percy had peaked with 10-minute sustained winds of 100kn (115mph; 185km/h).[44]
Steadily weakening soon after, around 01:00 UTC the next day, Percy made landfall on the southern tip of Taiwan.[44] Despite crossing the Formosa Strait just a few hours later, the mountainous climate of Taiwan had caused Percy's inflow to be disrupted, preventing any strengthening and causing Percy to weaken as fast as it had strengthened.[44] Early the next day, Percy left the PAR, causing PAGASA to cease tracking it.[3] A few hours later, Percy made landfall east of Guangzhou as a minimal tropical storm.[44] Rapidly weakening once inland, on 19 September, both the JTWC and JMA had ceased tracking it, with the former agency noting that Percy had dissipated at that time.[44][3]
As Percy scraped Taiwan, heavy rainfall damaged around 140 homes, destroyed crops, and flooded rice fields. Due to the typhoon, 7 people died with 16 being injured.[44]
On 12 September, a weak area of clouds and thunderstorms began developing in the monsoon trough. Despite not having a surface circulation, the upper-air pattern was conducive for the disturbance's development, and on 14 September, it had developed a surface circulation.[45] As a result of that, the JMA designated the system as a tropical depression later that day[7] around the time that the JTWC issued a TCFA on the nascent system.[45] Early the next day, Sperry intensified into a tropical storm.[45][7] Despite that, initially, the JTWC claimed that it had developed into a tropical depression.[45] Tracking northeastward due to mid-level southeasterly flow near Japan, Sperry began recurving south of Japan on 17 September.[45] As it recurved, early the next day, the JTWC noted that Sperry had intensified and peaked as a typhoon.[45] The JMA, however, stated that Sperry was actually a severe tropical storm at the time, noting that Sperry had really peaked as a minimal typhoon early on 19 September.[7]
Despite its eastward track preventing it from initially encountering colder waters and intense wind shear, Sperry began weakening around the time that it peaked.[45][7] As a result, by the next day, both agencies stated that Sperry had weakened into a tropical storm.[7][45] Later that day, the JTWC stopped tracking Sperry as according to them, it had become an extratropical cyclone.[45] The JMA kept tracking a weakening Sperry until it dissipated near the International Date Line on 24 September.[7]
On 23 September, satellite imagery shown that an area of increased convective activity was developing in the area from Southeast Asia to the Marshall Islands. Later that day, a significant area of convection formed near Saipan, with a surface circulation just south of Guam developing from it the next day.[46] On 25 September, the JMA designated this circulation as a tropical depression,[7] with the JTWC following suit early the next day.[46] Initially slow to develop, on 27 September, both the JMA and JTWC designated it as a tropical storm, with the latter agency naming it Thelma.[7][46] Tracking northwestward, by 29 September, a surface trough caused Thelma to track northeastward instead.[46] It was at that time when both the JMA and JTWC noted that Thelma had peaked with sustained winds of 65mph (100km/h).[7][46] However, due to a restriction in Thelma's upper-level outflow alongside the storm tracking into the baroclinic zone, Thelma soon began transitioning into an extratropical low.[46] As a result, the JTWC stopped tracking Thelma the next day as it became extratropical.[46] The JMA kept tracking Thelma, noting that it had deepened to attain a minimal central pressure of 960mbar (28inHg) on 2 October.[7] However, they stopped tracking it later that day after it passed 50° N.[7]
Wynne was the strongest storm of the season, reaching a peak of 175mph (282km/h) winds and a pressure of 890 mbar. As a strengthening category 1 storm, it rapidly intensified to become the strongest storm of the season, deepening 85 mb from 975 mb to 890 mb in 23 hours 56 minutes between 0240 UTC October 8 and 0236 UTC October 9, 1980.[47] It caused 6 power outages in Japan, and 10 deaths. [citation needed]
Basiang formed in the South China Sea on November 13 before moving erratically and making landfall in Vietnam on November 16 and dissipating on the same day.
A tropical disturbance was first observed near Yap on 14 December. The disturbance moved westward at between 12 and 15 kt (22 to 28km/h) as its convective activity and overall organization continued to improve. A Tropical Cyclone Formation Alert (TCFA) was issued when a reconnaissance aircraft observed a well-defined low-level circulation with a minimum sea-level pressure of 1004 mb. The disturbance was upgraded to Tropical Storm Ed on December 15. It then became evident from synoptic analyses that Ed was moving into an area which was unfavorable for continued development. Eventually, after most of the storm's convection had been sheared off, Ed's surface center began to track to the southwest under the influence of the strong surface ridge to the north. Dissipation as a tropical cyclone was completed on the 24th as the remnants of Ed moved into northern Mindanao.
Other systems
PAGASA tracked a tropical cyclone from 12 – 14 February, naming it Asiang.[3]
The track of Biring.
On 16 March, the JTWC began tracking a tropical disturbance south-southeast of Guam. Four days later, the disturbance developed into a depression.[48] Soon after, the depression crossed into the PAR, causing PAGASA to name it Biring.[3] Persistent wind shear prevented the depression from intensifying further, and after making landfall in the Philippines on 24 March, it degenerated into a remnant low.[48] Despite that, PAGASA kept tracking the remnants until 27 March.[3] Across the Philippines, 4 people died due to the depression.[49] Due to the system and a high pressure area in mainland Asia, an extratropical warning was issued for the seas near Taiwan.[48]
PAGASA tracked a tropical cyclone from 28 April – 1 May, naming it Konsing.[3]
On 28 June, a tropical depression formed east of the Philippines.[50] Two days later, PAGASA began tracking the disturbance, naming it Isang.[3] After it made two landfalls in the Philippines,[50] PAGASA stopped tracking the depression on 2 July.[3] The depression dissipated the next day.[50]
On 15 July, the JTWC began tracking a tropical disturbance near the Philippines.[51] The next day, PAGASA began tracking the system, naming it Maring.[3] The next day, the JTWC recognized it as a depression,[51] just as it exited the PAR.[3] After making landfall in China two days later, the JTWC stopped tracking the depression.[51]
On 12 August, the JTWC began tracking a tropical disturbance south of Guam. Tracking west-northwestward, two days later, they issued a TCFA on the system as it neared Luzon.[52] Early the next day, prior to making landfall, both PAGASA and the JTWC designated the system as a tropical depression, with the former agency naming it Paring.[3][52] In the Philippines, Paring rapidly weakened, and after crossing into the South China Sea, becoming a remnant low on 16 August.[52] PAGASA kept tracking the remnants until the next day.[3] Scattered showers affiliated with the depression were recorded in Hong Kong.[53]
On 30 August, a tropical depression formed east of the Philippines.[55] Two days later, PAGASA began tracking the disturbance, naming it Seniang.[3] Despite dissipating on 2 September,[55] PAGASA kept tracking the remnants until 4 September.[3]
On 3 September, the CMA noted that a tropical depression had formed in the South China. After making landfall in Vietnam three days later, it dissipated.[56]
During the season 24 named tropical cyclones developed in the Western Pacific and were named by the Joint Typhoon Warning Center, when it was determined that they had become tropical storms. These names were contributed to a revised list which started on 1979.
Carmen
Dom
Ellen
Forrest
Georgia
Herbert
Ida
Joe
Kim
Lex
Marge
Norris
Orchid
Percy
Ruth
Sperry
Thelma
Vernon
Wynne
Alex
Betty
Cary
Dinah
Ed
Philippines
Asiang
Biring
Konsing
Ditang
Edeng
Gloring
Huaning
Isang
Lusing
Maring
Nitang
Osang
Paring
Reming
Seniang
Toyang
Unsang
Welpring
Yoning
Auxiliary list
Aring
Basiang
Kayang
Dorang
Enang(unused)
Grasing(unused)
The Philippine Atmospheric, Geophysical and Astronomical Services Administration uses its own naming scheme for tropical cyclones in their area of responsibility. PAGASA assigns names to tropical depressions that form within their area of responsibility and any tropical cyclone that might move into their area of responsibility. Should the list of names for a given year prove to be insufficient, names are taken from an auxiliary list, the first 6 of which are published each year before the season starts. Names not retired from this list will be used again in the 1984 season. This is the same list used for the 1976 season, with the exception of Ditang, which replaced Didang. PAGASA uses its own naming scheme that starts in the Filipino alphabet, with names of Filipino female names ending with "ng" (A, B, K, D, etc.). Names that were not assigned/going to use are marked in gray.
Season effects
This table will list all the storms that developed in the northwestern Pacific Ocean west of the International Date Line and north of the equator during 1980. It will include their intensity, duration, name, areas affected, deaths, and damage totals. Classification and intensity values will be based on estimations conducted by the JMA, the JTWC, and/or PAGASA. Peak wind speeds are in ten-minute sustained standards unless otherwise noted. All damage figures will be in 1981USD. Damages and deaths from a storm will include when the storm was a precursor wave or an extratropical low.
South-West Indian Ocean cyclone seasons: 1979–80, 1980–81
Related Research Articles
The 2005 Pacific typhoon season was the least active typhoon season since 2000, producing 23 named storms, of which 13 became typhoons. It was an event in the annual cycle of tropical cyclone formation, in which tropical cyclones form in the western Pacific Ocean. The season ran throughout 2005, though most tropical cyclones typically develop between May and October. The season's first named storm, Kulap, developed on January 13, while the season's last named storm, Bolaven, dissipated on November 20. The season's first typhoon, Haitang, reached typhoon status on July 13, and became the first super typhoon of the year three days later.
The 2007 Pacific typhoon season was a near average season which featured 24 named storms, fourteen typhoons, and five super typhoons. It was an event in the annual cycle of tropical cyclone formation, in which tropical cyclones form in the western Pacific Ocean. The season ran throughout 2007, though most tropical cyclones typically develop between May and November. The season's first named storm, Kong-rey, developed on March 30, while the season's last named storm, Mitag, dissipated on November 27. The season's first typhoon, Yutu, reached typhoon status on May 18, and became the first super typhoon of the year on the next day.
The 2004 Pacific typhoon season was an extremely active season that featured the second-highest ACE ever recorded in a single season, second only to 1997, which featured 29 named storms, nineteen typhoons, and six super typhoons. It was an event in the annual cycle of tropical cyclone formation, in which tropical cyclones form in the western Pacific Ocean. The season ran throughout 2004, though most tropical cyclones typically develop between May and October. The season's first named storm and also the first typhoon, Sudal, developed on April 4, later was reached typhoon status two days later, and became the first super typhoon of the year three days later. The season's last named storm, Noru, dissipated on December 21.
The 2001 Pacific typhoon season was an average season with twenty-six named storms, sixteen typhoons and three super typhoons, with a near normal Accumulated Cyclone Energy (ACE) of 307.3 units. It ran year-round in 2001, with most tropical cyclones in the northwestern Pacific Ocean tending between May and November.
The 1999 Pacific typhoon season was the last Pacific typhoon season to use English names as storm names. It also featured the lowest number of typhoons on record, with only five reaching this intensity. This was mainly due to a strong La Niña which persisted from last year. The season was also below-average in named storms, with only 20 of such spawning. This season also featured multiple landfalls in Hong Kong. It had no official bounds; it ran year-round in 1999, but most tropical cyclones tend to form in the northwestern Pacific Ocean between May and November. These dates conventionally delimit the period of each year when most tropical cyclones form in the northwestern Pacific Ocean. The first named storm, Hilda, developed on January 6, while the last named storm, Gloria, dissipated on November 16.
The 1992 Pacific typhoon season was the fourth consecutive above-average season, producing 31 tropical storms, 16 typhoons and five super typhoons. It had no official bounds; it ran year-round in 1992. Despite this, most tropical cyclones tend to form in the northwestern Pacific Ocean between May and November. These dates conventionally delimit the period of each year when most tropical cyclones form in the northwestern Pacific Ocean.
The 1988 Pacific typhoon season was a very active season in terms of named storms, though it only featured 11 typhoons and 1 super typhoon. It had no official bounds; it ran year-round in 1988, but most tropical cyclones formed between May and November. Tropical storms that formed in the entire west Pacific basin were assigned a name by the Joint Typhoon Warning Center. Tropical depressions that enter or form in the Philippine area of responsibility are assigned a name by the Philippine Atmospheric, Geophysical and Astronomical Services Administration or PAGASA. This can often result in the same storm having two names.
The 1987 Pacific typhoon season was a below average season, though it featured a relatively high amount of typhoons. It had no official bounds; it ran year-round in 1987, but most tropical cyclones formed between May and November. Tropical storms that formed in the entire basin were assigned a name by the Joint Typhoon Warning Center. Tropical depressions that enter or form in the Philippine area of responsibility are assigned a name by the Philippine Atmospheric, Geophysical and Astronomical Services Administration or PAGASA. This can often result in the same storm having two names.
The 2008 Pacific typhoon season was a below average season which featured 22 named storms, eleven typhoons, and two super typhoons. The season had no official bounds; it ran year-round in 2008, but most tropical cyclones tend to form in the northwestern Pacific Ocean between May and November. These dates conventionally delimit the period of each year when most tropical cyclones form in the northwestern Pacific Ocean.
This timeline documents all the storm formations, strengthening, weakening, landfalls, extratropical transitions, as well as dissipation during the 2008 Pacific typhoon season. The 2008 Pacific typhoon season officially started on January 1, 2008 and ended on January 1, 2009.
The 2009 Pacific typhoon season was a below average season that spawned only 22 named storms, 13 typhoons, and five super typhoons. Despite this, it was a very deadly season, with the Philippines having experienced its deadliest season in decades due to the impact of typhoons Ketsana and Parma, while typhoon Morakot went on to become the deadliest storm to impact Taiwan in its modern history. The first half of the season was very quiet, whereas the second half of the season was extremely active. The season's first named storm, Kujira, developed on May 3, while the season's last named storm, Nida, dissipated on December 3.
The 2011 Pacific typhoon season was a below average season that produced a total of 21 named storms, 8 typhoons, and four super typhoons. This season was much more active than the previous season, although both seasons were below the Pacific typhoon average of 26. The season ran throughout 2011, though most tropical cyclone tend to develop between May and October. The season's first named storm, Aere, developed on May 7 while the season's last named storm, Washi dissipated on December 19.
Most of the tropical cyclones of the 2013 Pacific typhoon season formed between May and November of that year. The scope of this article is the Pacific Ocean north of the equator, between 100°E and the International Date Line. Tropical storms which form in the Western Pacific basin are assigned a name by the Japan Meteorological Agency (JMA). Tropical depressions forming in this basin are given a number with a "W" suffix by the United States' Joint Typhoon Warning Center (JTWC). The Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns names to tropical cyclones that enter or form in the Philippine area of responsibility, but these names are not in common use outside the Philippines.
This timeline documents all of the events of the 2014 Pacific typhoon season. Most of the tropical cyclones forming between May and November. The scope of this article is limited to the Pacific Ocean, north of the equator between 100°E and the International Date Line. Tropical storms that form in the entire Western Pacific basin are assigned a name by the Japan Meteorological Agency. Tropical depressions that form in this basin are given a number with a "W" suffix by the United States' Joint Typhoon Warning Center. In addition, the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns names to tropical cyclones that enter or form in the Philippine area of responsibility. These names, however, are not in common use outside of the Philippines.
Typhoon Lingling, known in the Philippines as Typhoon Nanang, was a deadly typhoon that struck the Philippines and Vietnam in 2001 and caused 379 deaths. The name "Lingling" was given by Hong Kong. The 39th tropical depression, 22nd named storm, and 13th typhoon of the 2001 Pacific typhoon season, Lingling developed into a tropical depression on November 6 and given the local name Nanang by the PAGASA. The next day, it was upgraded into a tropical storm and given the name Lingling by the Japan Meteorological Agency (JMA). Lingling's intensity briefly stagnated as it moved over Visayas before resuming intensification and intensifying into a severe tropical storm on November 8. One day later, both the JMA and the Joint Typhoon Warning Center (JTWC) upgraded Lingling to a typhoon as it exited the Philippine archipelago and moved into the South China Sea. After intensifying into a typhoon, Lingling began to quickly intensify, peaking with 10-min sustained winds of 155 km/h (96 mph) and 1-min sustained winds of 215 km/h (134 mph), with a minimum central pressure of 940 mbar (28 inHg). Lingling began to weaken as it approached the Vietnamese coast, before making landfall on November 11 at 18:00 UTC. Lingling rapidly weakened afterward, dissipating on November 12.
Typhoon Betty, known in the Philippines as Typhoon Aring, was the strongest typhoon to strike the Philippines in ten years. An area of disturbed weather developed on October 27, 1980, near Truk Atoll. After turning east from south, the disturbance was classified as a tropical storm on October 29 as it passed near Guam, causing only minor damage. Following a turn to the west-northwest, Betty attained typhoon intensity the next day. On November 4, Betty peaked in intensity. Later that day, Betty moved ashore over Luzon, introducing a rapid weakening trend. Over land, Betty then began to turn north due to a weakening subtropical ridge to its north and a trough offshore Taiwan. By November 8, Betty, after moving offshore, had completed its transition into an extratropical cyclone, and dissipated that same day.
The 2021 Pacific typhoon season was the second consecutive to have below average tropical cyclone activity, with twenty-two named storms, and was the least active since 2011. Nine became typhoons, and five of those intensified into super typhoons. This low activity was caused by a strong La Niña that had persisted from the previous year. The season's first named storm, Dujuan, developed on February 16, while the last named storm, Rai, dissipated on December 21. The season's first typhoon, Surigae, reached typhoon status on April 16. It became the first super typhoon of the year on the next day, also becoming the strongest tropical cyclone in 2021. Surigae was also the most powerful tropical cyclone on record in the Northern Hemisphere for the month of April. Typhoons In-fa and Rai are responsible for more than half of the total damage this season, adding up to a combined total of $2.02 billion.
The 2022 Pacific typhoon season was the third consecutive season to have below average tropical cyclone activity, with twenty-five named storms forming. Of the tropical storms, ten became typhoons, and three would intensify into super typhoons. The season saw near-average activity by named storm count, although many of the storms were weak and short-lived, particularly towards the end of the season. This low activity was caused by an unusually strong La Niña that had persisted from 2020. The season's first named storm, Malakas, developed on April 6, while the last named storm, Pakhar, dissipated on December 12. The season's first typhoon, Malakas, reached typhoon status on April 12. The season ran throughout 2022, though most tropical cyclones typically develop between May and October. Tropical storms Megi and Nalgae were responsible for more than half of the casualties, while typhoons Hinnamnor and Nanmadol both caused $1 billion in damages.
The 2023 Pacific typhoon season was the fourth consecutive below-average season and became the third-most inactive typhoon season on record in terms of named storms, with just 17 named storms developing, only ahead of 2010 and 1998. Despite the season occurring during an El Niño event, which typically favors activity in the basin, activity was abnormally low. This was primarily due to a consistent period of negative PDO, which typically discourages tropical storm formation in this basin. The season was less active than the 2023 Atlantic hurricane season in terms of named storms, the fourth such season on record, after 2005, 2010 and 2020. The season's number of storms also did not exceed that of the 2023 Pacific hurricane season. Only ten became typhoons, with four strengthening further into super typhoons. However, it was very destructive, primarily due to Typhoon Doksuri which devastated the northern Philippines, Taiwan, and China in July, becoming the costliest typhoon on record as well as the costliest typhoon to hit mainland China, and Typhoon Haikui in September, which devastated China, Taiwan, and Hong Kong. The season was less active in Southeast Asia, with no tropical storm making landfall in mainland Vietnam.
Typhoon Toraji, known in the Philippines as Typhoon Isang, was one of the deadliest tropical cyclones to hit the island country of Taiwan, since 1961. The eight named storm and the third typhoon of the 2001 Pacific typhoon season, Toraji's origins were from an area of convection that persisted to the west of Guam. Moving north-northwest over favorable conditions, the disturbance intensified to a tropical depression, while the JTWC issued a TCFA on the newly developed system. On July 26, the depression entered the Philippine Area of Responsibility, with the PAGASA naming it Isang. Strong easterly wind shear inhibited further development; however, as the shear relaxed, both the JTWC and PAGASA upgraded the system to a tropical storm with also the JMA following suit hours later. Now named Toraji, the storm slowly intensified, reaching typhoon status on the next day. Toraji continued to gain strength until it made landfall as a Category 2 typhoon near Taipei on July 29. Despite the rugged terrains of the country, the JTWC upgraded the system further to a Category 3, shortly before weakening as it moved offshore on Taiwan Strait. The JMA and PAGASA downgraded the typhoon to a tropical storm, with the latter issuing their final advisory as it moved out of their AOR. It continued to weaken, with the JTWC also downgrading the system to a tropical storm, before making landfall near Fuzhou on July 31 before it was last noted by the next day.
↑ "Glossary of NHC Terms". National Oceanic and Atmospheric Administration, National Hurricane Center and Central Pacific Hurricane Center. Retrieved 31 January 2024.
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.
