1980 Pacific typhoon season

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "1980 Pacific typhoon season" – news · newspapers · books · scholar · JSTOR (April 2016) (Learn how and when to remove this message)

1980 Pacific typhoon season
Season summary map
Seasonal boundaries
First system formed	February 12, 1980
Last system dissipated	December 21, 1980
Strongest storm
Name	Wynne
• Maximum winds	220 km/h (140 mph) (10-minute sustained)
• Lowest pressure	890 hPa (mbar)
Seasonal statistics
Total depressions	44
Total storms	24
Typhoons	15
Super typhoons	2 (unofficial)
Total fatalities	493 total
Total damage	$195 million (1980 USD)
Related articles
1980 Atlantic hurricane season 1980 Pacific hurricane season 1980 North Indian Ocean cyclone season
Pacific typhoon seasons 1978, 1979, 1980, 1981, 1982

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.8 units,^[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]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	April 5 (Entered basin) – April 7 (Exited basin)
Peak intensity	110 km/h (70 mph) (10-min); 985 hPa (mbar)

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 (110 km/h; 70 mph).^[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]

Very strong typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	May 7 – May 22
Peak intensity	155 km/h (100 mph) (10-min); 960 hPa (mbar)

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]

As Ditang tracked towards the Philippines, PAGASA issued Public Storm Warning Signal (PSWS) #3 for Catanduanes, Camarines Norte and Sur, Aurora, Quirino, Cagayan, Mountain Province, Nueva Vizcaya, Ifugao, Batanes, and Abra. Heavy rains and gusts were seen in Eastern Luzon.^[9] As a result of the typhoon, Baguio received 730.3 mm (28.75 in) of rain on May 15.^[10] At least four provinces suffered a loss of tobacco crops.^[11] In total, Ditang resulted in 3,696 homes being damaged.^[12]

Violent typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	May 13 – May 25
Peak intensity	195 km/h (120 mph) (10-min); 930 hPa (mbar)

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 930 mbar (27 inHg) later that day.^[7] The next day, the JMA noted that Ellen had peaked with 10-minute sustained winds of 105 kn (120 mph; 195 km/h)^[7] while the JTWC stated that Ellen peaked with 1-minute sustained winds of 110 kn (125 mph; 205 km/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–35 kn (35–40 mph; 56–65 km/h).^[7] Heavy rainfall from Ellen affected western and central Japan, causing around 60 landslides and flooding almost 300 homes.^[11]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	May 19 – May 29
Peak intensity	100 km/h (65 mph) (10-min); 992 hPa (mbar)

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 55 kn (65 mph; 100 km/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]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	May 19 – May 25
Peak intensity	100 km/h (65 mph) (10-min); 980 hPa (mbar)

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 55 kn (65 mph; 100 km/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 73 kn (84 mph; 135 km/h). Additionally, light rainfall was seen. With the exception of some scaffolding blown off in Tai Kok Sui Road, no damage occurred.^[16]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	June 22 – June 29
Peak intensity	95 km/h (60 mph) (10-min); 990 hPa (mbar)

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 50 kn (60 mph; 95 km/h).^[17][7] Slightly weakening, at 1800Z the next day, Herbert made its landfall in Hainan with maximum sustained winds of 45 kn (50 mph; 85 km/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 45 kn (50 mph; 85 km/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 48 kn (55 mph; 89 km/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 46 kn (53 mph; 85 km/h).^[17]

Typhoon (JMA)
Tropical storm (SSHWS)
Duration	July 5 – July 15
Peak intensity	130 km/h (80 mph) (10-min); 980 hPa (mbar)

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.15 in (29 mm) of rainfall in three hours.^[19] Moderate rainfall was recorded in Hong Kong.^[20] In the Philippines, some damage was recorded.^[21]

Very strong typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	July 15 – July 24
Peak intensity	155 km/h (100 mph) (10-min); 940 hPa (mbar)

An area of disturbed weather developed over the Caroline Islands on July 14. 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:00 UTC on July 17, 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 July 18, 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 July 19, which measured a pressure of 974 mbar (28.8 inHg). An eye began to clear out on July 20. That same day, a Hurricane hunter aircraft recorded a pressure of 940 mbar (28 inHg). At midday, the JTWC estimated that Joe peaked in intensity, with winds of 195 km/h (120 mph), equal to a Category 3 hurricane on the United States-based Saffir-Simpson Hurricane Wind Scale (SSHWS). Meanwhile, the JMA estimated maximum intensity of 160 km/h (100 mph).^[7][22]

Six hours after its peak, Joe made landfall in central Luzon.^[22] At the time of landfall, the JMA indicated winds of 90 mph (145 km/h).^[7] Over land, Joe weakened rapidly, falling to tropical storm strength according to the JTWC.^[22] After entering the South China Sea on July 21, 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 135 km/h (85 mph).^[7] On July 22, the JTWC estimated that Joe attained a secondary peak of 170 km/h (105 mph). 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 130 km/h (80 mph) when it moved ashore near Haiphong in Vietnam later on July 22.^[22][7] A combination of land interaction and vertical wind shear resulted in rapid weakening. At 00:00 UTC on July 23, the JTWC issued its last warning on Joe. The remnants of Joe later moved into Laos.^[22] The JMA stopped watching Joe on July 24.^[7]

Across the Philippines, 31 citizens were killed,^[23] In Vietnam, 130 people were killed, 300,000 others were directly affected, and 165,000 others lost their homes.^[23] Two large ships, a 20,000 short tons (18,145 t) liner and a 50,000 short tons (45,360 t) tanker, were washed ashore in Chankiang.^[24] Throughout the area, 188 people were killed and at least 100 others were left homeless.^[23]

Very strong typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	July 17 – July 25
Peak intensity	185 km/h (115 mph) (10-min); 910 hPa (mbar)

An area of disturbed weather developed in association with the monsoon trough on July 19. 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 July 23, 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 July 24, the JTWC increased the intensity of Kim to 185 km/h (115 mph),^[25] while the JMA raised the winds to 170 km/h (105 mph).^[7] Ten hours later, a Hurricane hunter aircraft measured a pressure of 908 mbar (26.81 inHg), causing the JTWC to declare Kim a super typhoon^[25] and increasing the wind speed to 240 km/h (150 mph). At 18:00 on July 24, the JMA estimated that Kim reached its peak intensity to 170 km/h (105 mph).^[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 185 km/h (115 mph),^[25] while the JMA reported that Kim moved ashore with winds of 145 km/h (90 mph).^[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 July 27, a weakening Kim crossed the coastline of China around 165 km (105 mi) northeast of Hong Kong.^[25] At the time of its second landfall, both the JTWC and JMA estimated winds of 80 km/h (50 mph).^[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 610 mm (24 in) 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, 40 people were killed,^[30] 2 via drownings,^[28] and 19,000 others were affected.^[30] The HKO observed 136.3 mm (5.37 in) 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]

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	July 28 – August 13
Peak intensity	140 km/h (85 mph) (10-min); 960 hPa (mbar)

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 90 mph; 150 km/h (80 kn)^[31] and 10-minute sustained winds of 85 mph; 140 km/h (75 kn) 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]

Very strong typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	August 8 – August 16
Peak intensity	165 km/h (105 mph) (10-min); 945 hPa (mbar)

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 125 mph; 205 km/h (110 kn)^[32] and 10-minute sustained winds of 105 mph; 165 km/h (90 kn) 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]

Very strong typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	August 23 – August 31
Peak intensity	175 km/h (110 mph) (10-min); 945 hPa (mbar)

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 90 kn (105 mph; 165 km/h) according to the JTWC^[33] and 95 kn (110 mph; 175 km/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; 19 km) southwest of Yonaguni on 27 August, winds of 90 kn (100 mph; 170 km/h) to the island. In Taiwan, gusts of 64 kn (74 mph; 119 km/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]

Typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	September 4 – September 16
Peak intensity	130 km/h (80 mph) (10-min); 960 hPa (mbar)

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 70 kn (80 mph; 130 km/h) while the JTWC noted that Orchid had peaked with 1-minute sustained winds of 85 kn (100 mph; 155 km/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]

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
Duration	September 12 – September 17
Peak intensity	100 km/h (65 mph) (10-min); 980 hPa (mbar)

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 45 kn (50 mph; 85 km/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 65 kn (75 mph; 120 km/h).^[40] The JMA, however, stated that Ruth peaked with 10-minute sustained winds of 55 kn (65 mph; 100 km/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.45 kn (50 mph; 85 km/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]

Very strong typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	September 13 – September 19
Peak intensity	185 km/h (115 mph) (10-min); 915 hPa (mbar)

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 125 kn (145 mph; 230 km/h).^[44] A few hours later, the JMA noted that Percy had peaked with 10-minute sustained winds of 100 kn (115 mph; 185 km/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]

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	September 14 – September 24
Peak intensity	120 km/h (75 mph) (10-min); 975 hPa (mbar)

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]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	September 25 – October 2
Peak intensity	100 km/h (65 mph) (10-min); 960 hPa (mbar)

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 65 mph (100 km/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 960 mbar (28 inHg) on 2 October.^[7] However, they stopped tracking it later that day after it passed 50° N.^[7]

Very strong typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	September 27 – October 3
Peak intensity	175 km/h (110 mph) (10-min); 935 hPa (mbar)

Vernon was a potent typhoon that stayed from land.

Violent typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	October 3 – October 14
Peak intensity	220 km/h (140 mph) (10-min); 890 hPa (mbar)

Wynne was the strongest storm of the season, reaching a peak of 175 mph (282 km/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]}

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	October 9 – October 14
Peak intensity	65 km/h (40 mph) (10-min); 998 hPa (mbar)

Alex stayed over water.

Very strong typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	October 28 – November 7
Peak intensity	185 km/h (115 mph) (10-min); 925 hPa (mbar)

Betty hit the Philippines as a strong typhoon. Betty killed 101 people in the Philippines.

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	October 28 – November 2
Peak intensity	85 km/h (50 mph) (10-min); 996 hPa (mbar)

Cary moved into the South China Sea.

Tropical depression (JMA)
Duration	November 13 – November 16
Peak intensity	55 km/h (35 mph) (10-min); 1004 hPa (mbar)

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.

Very strong typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	November 18 – November 25
Peak intensity	165 km/h (105 mph) (10-min); 950 hPa (mbar)

Dinah hit the Northern Mariana Islands directly. Saipan sustained significant damage.

Tropical depression (JMA)
Duration	November 19 – November 21
Peak intensity	Winds not specified; 1004 hPa (mbar)

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	December 14 – December 21
Peak intensity	85 km/h (50 mph) (10-min); 990 hPa (mbar)

A tropical disturbance was first observed near Yap on 14 December. The disturbance moved westward at between 12 and 15 kt (22 to 28 km/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.

• PAGASA tracked a tropical cyclone from 12 – 14 February, naming it Asiang.^[3]

• 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]
• The China Meteorological Administration (CMA) tracked a tropical depression from 26 – 31 August.^[54]
• 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.

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.

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 1981 USD. Damages and deaths from a storm will include when the storm was a precursor wave or an extratropical low.

• List of Pacific typhoon seasons
• 1980 Pacific hurricane season
• 1980 Atlantic hurricane season
• 1980 North Indian Ocean cyclone season
• Australian cyclone seasons: 1979–80, 1980–81
• South Pacific cyclone seasons: 1979–80, 1980–81
• South-West Indian Ocean cyclone seasons: 1979–80, 1980–81

• Japan Meteorological Agency
• Joint Typhoon Warning Center Archived 2010-03-01 at the Wayback Machine.
• China Meteorological Agency
• National Weather Service Guam
• Hong Kong Observatory
• Macau Meteorological Geophysical Services
• Korea Meteorological Agency
• Philippine Atmospheric, Geophysical and Astronomical Services Administration
• Taiwan Central Weather Bureau
• Digital Typhoon – Typhoon Images and Information
• Typhoon2000 Philippine typhoon website