The 1980 Pacific typhoon season was a slightly-below average season compared to the long-term average, featuring at least seventeen systems.

The scope of this article is limited to the Pacific Ocean to the north of the equator between 100°E and 180th meridian. Within the northwestern Pacific Ocean, there are two separate agencies that assign names to tropical cyclones which can often result in a cyclone having two names. Tropical depressions that are monitored by the United States' Joint Typhoon Warning Center (JTWC) ^{[nb 2] [nb 1]} are given a number with a "W" suffix. Additionally, the JTWC, at the time, took most of the responsibility in the basin, including naming the storms. ^[3] The Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns names to tropical cyclones which move into or form as a tropical depression in the Philippine Area of Responsibility (PAR), located between 135°E and 115°E and between 5°N–25°N, regardless of whether or not a tropical cyclone has already been given a name by the JTWC.

Thie 1980 Pacific typhoon season's ACE index was approximately 237.8 units, ^[7] 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. ^[8]

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, the the Joint Typhoon Warning Center (JTWC) began tracking a tropical disturbance located east of the International Date Line. At the time, the disturbance was developing alongside a parallel cyclone, the precursor to Cyclone Wally, 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. ^[5] Later that day, the JMA designated the system as a tropical storm, ^[9] with the JTWC following suit a few hours later, naming it Carmen. ^[5] 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). ^{[9] [5]} 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. ^{[5] [9]}

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, using satellite imagery, the JTWC began tracking a weak tropical disturbance in the near-equatorial trough. As it tracked westward across the Caroline Islands in the following three days, little development was seen. ^[10] Despite that, on May 7, the Japan Meteorological Agency designated the disturbance as a tropical depression. ^[9] 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. ^[10] 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. ^[6] Despite intense vertical shear, the depression intensified into a tropical storm a few hours later, being named Dom by the JTWC. ^[10] 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. ^{[10] [9]} 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. ^[10]

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. ^[10] PAGASA kept tracking the system until May 21, ^[6] when the remnants of Dom and a weakening Ellen began accelerating towards an extratropical cyclone south of Japan. ^[10] The remnants of Dom and Ellen later merged with the cyclone the same day, ^[10] causing the JMA to finally stop monitoring Dom a few hours later. ^[9]

In the Philippines, Ditang resulted in 3,696 homes being damaged. ^[11]

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, the JTWC began tracking a tropical disturbance located in an equatorial trough east of Chuuk Lagoon. The next day, the disturbance had shown signs of weakening, causing the JTWC to not issue a TCFA at that time. However, soon after, it rapidly developed, becoming a tropical storm a few hours later, causing both the JTWC and JMA to issue their first advisories early the next day, with the former naming it Ellen. ^{[12] [9]} 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. ^[9] The next day, the JMA noted that Ellen had peaked with 10-minute sustained winds of 105 kn (120 mph; 195 km/h) ^[9] while the JTWC stated that Ellen peaked with 1-minute sustained winds of 110 kn (125 mph; 205 km/h). ^[12] 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. ^[12] The JMA kept tracking it until 25 May. ^[9]

As Ellen made its closest approach to Japan, Yokosuka saw gusts of 30–35 kn (35–40 mph; 56–65 km/h). ^[9]

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, the JTWC began tracking a tropical disturbance west of Kosrae. ^[13] Three days later, the JMA designated the disturbance as a tropical depression, ^[9] with the JTWC issuing a TCFA on the system soon after. ^[13] The next day, both the JMA and JTWC designated the depression as a tropical storm, with the latter agency naming it Forrest. ^{[9] [13]} On 22 May, Forrest crossed into the PAR, being named Gloring by PAGASA. ^[6] Steadily developing, the next day, both agencies noted that Forest had peaked with sustained winds of 55 kn (65 mph; 100 km/h). ^{[9] [13]} After making landfall in Luzon on 25 May, Forrest rapidly weakened, ^[13] and on 26 May, both PAGASA and the JTWC stopped tracking Forrest. ^{[6] [13]} The JMA kept tracking a weakening Forrest until 29 May. ^[9]

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, the JTWC began tracking a monsoon depression embedded in the South China sea. ^[14] A few hours later, the JMA designated the weak circulation as a tropical depression as the JTWC issued a TCFA. ^{[9] [14]} 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. ^{[6] [14]} The next day, Edeng left the PAR, causing PAGASA to stop tracking the system. ^[6] Soon after, both the JMA and JTWC designated the system as a tropical storm, with the latter naming it Georgia. ^{[9] [14]} 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. ^[14] The JMA followed suit the next day. ^[9]

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. ^[15]

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. ^[16] The next day, the disturbance was designated a depression by PAGASA, who named it Huaning. ^[6] Making landfall in Leyte, Philippines the next day, ^[16] the JMA designated the system as a tropical depression. ^[9] However, landfall prevented further development, causing the TCFA to be cancelled later that day. ^[16] 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, ^{[16] [9]} with the former agency naming it Herbert. ^[16]

In the South China Sea, Herbert tracked northwestward toward Hainan Island while intensifying slowly. ^[16] After exiting the PAR on 25 June, PAGASA stopped tracking the system. ^[6] Later that day, both agencies stated that Herbert peaked with sustained winds of 50 kn (60 mph; 95 km/h). ^{[16] [9]} 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). ^[16] 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). ^[16] Rapidly weakening, both the JTWC and JMA stopped tracking Herbert the next day. ^{[16] [9]}

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. ^[17] The Paracel Islands recorded peak winds of 46 kn (53 mph; 85 km/h). ^[16]

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, the JTWC began tracking a surface circulation northwest of Woleai. ^[18] Later that day, the JMA designated the system as a tropical depression. ^[9] Aerial reconnaissance caused the JTWC to issue a TCFA, and a few hours later, they designated the system as a tropical depression. ^[18] 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. ^{[9] [6] [18]} Steadily intensifying, on 9 July, the JMA stated that Ida peaked as a minimal typhoon ^[9] while the JTWC stated that it peaked as a high-end tropical storm. ^[18] Slightly weakening as it tracked into the Bashi Channel, on 11 July, Ida made landfall in Southeastern China, ^[18] causing PAGASA to stop tracking it. ^[6] The JMA stopped tracking the system four days later. ^[18]

As Ida was developing, The naval air station in Guam received over 1.15 in (29 mm) of rainfall in three hours. ^[18] Moderate rainfall was recorded in Hong Kong. ^[19] In the Philippines, some damage was recorded. ^[20]

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. ^[21] At 18:00 UTC on July 22, the Japan Meteorological Agency (JMA) started tracking the system. ^[9] 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. ^[21] Meanwhile, PAGASA tracked the storm and named it Nitang. ^[6]

The depression began to develop at a quicker pace, and early on July 18, the JTWC upgraded it to a tropical storm. ^[21] After Joe developed a central dense overcast, the JMA upgraded Joe into a severe tropical storm. ^[9] At midday, the JTWC and JMA upgraded Joe into a typhoon. ^{[9] [21]} 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). ^{[9] [21]}

Six hours after its peak, Joe made landfall in central Luzon. ^[21] At the time of landfall, the JMA indicated winds of 90 mph (145 km/h). ^[9] Over land, Joe weakened rapidly, falling to tropical storm strength according to the JTWC. ^[21] 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. ^[21] Around this time, the JMA estimated that Joe reached its secondary peak of 135 km/h (85 mph). ^[9] On July 22, the JTWC estimated that Joe attained a secondary peak of 170 km/h (105 mph). Despite maintaining its structure ^[21] as it tracked over the Leizhou Peninsula, the storm weakened as it entered the Gulf of Tonkin and approached the coast of Vietnam. ^[21] 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. ^{[21] [9]} 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. ^[21] The JMA stopped watching Joe on July 24. ^[9]

Across the Philippines, 31 citizens were killed, ^[22] In Vietnam, 130 people were killed, 300,000 others were directly affected, and 165,000 others lost their homes. ^[22] 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. ^[23] Throughout the area, 188 people were killed and at least 100 others were left homeless. ^[22]

Very strong typhoon (JMA)
Category 4 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. ^[24] Four hours later, the JMA classified the system as a tropical depression, ^[9] with the JTWC following suit early the next day. ^[24] Early the next day, both the JTWC ^[24] and JMA ^[9] upgraded the depression into a tropical storm, with the former agency naming it Kim. ^[24] 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. ^[24] Based on this, both the JTWC and JMA announced that Kim obtained typhoon intensity. ^{[9] [24]} Around this time, Kim tracked into the PAR, causing PAGASA to name it Osang. ^[6] Continuing to track west-northwest beneath a large subtropical ridge, ^[24] Kim began to clear out an eye on the evening of July 23; ^[25] subsequently, Kim entered a period of rapid deepening. ^[24]

At July 24, the JTWC increased the intensity of Kim to 185 km/h (115 mph), ^[24] while the JMA raised the winds to 170 km/h (105 mph). ^[9] 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 ^[24] 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). ^[9] 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), ^[24] while the JMA reported that Kim moved ashore with winds of 145 km/h (90 mph). ^[9] Continuing to weaken due to land interaction, Kim weakened into a tropical storm as it emerged into the South China Sea, ^{[24] [9]} On July 27, a weakening Kim crossed the coastline of China around 165 km (105 mi) northeast of Hong Kong. ^[24] At the time of its second landfall, both the JTWC and JMA estimated winds of 80 km/h (50 mph). ^{[9] [24]} Twelve hours later, both the JTWC ^[24] and JMA ceased tracking Kim. ^[9]

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. ^[26] The coast guard suspended sailing permits to ships throughout the country. ^[27] The Isabela province was the hardest hit by Typhoon Kim. ^[28] Across the Philippines, 40 people were killed, ^[29] 2 via drownings, ^[27] and 19,000 others were affected. ^[29] 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. ^[25]

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, the JTWC began tracking a tropical disturbance which had spawned from a Tropical upper tropospheric trough (TUTT). ^[30] Steadily tracking westward, two days later, the JMA designated the system as a tropical depression. ^[9] A few hours later, the JTWC issued a TCFA on the system as it steadily developed. ^[30] As the depression's satellite signature improved, the JTWC issued their first warning on it early the next day. ^[30] Twelve hours later, both the JTWC and JMA upgraded the system into a tropical storm, with the former agency naming it Lex. ^{[9] [30]} Tracking northwestward and steadily intensifying, on July 31, both agencies upgraded Lex into a typhoon. ^{[9] [30]} Soon after, Lex executed a cyclonic loop, later peaking with 1-minute sustained winds of 90 mph; 150 km/h (80 kn) ^[30] and 10-minute sustained winds of 85 mph; 140 km/h (75 kn) according to the JMA. ^[9] However, soon after, cold air from a deep surface low caused Lex to steadily weaken. ^[30] As a result, on 7 August, Lex transitioned into an extratropical low according to the JTWC. ^[30] The JMA kept monitoring Lex until 13 August. ^[9]

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, the JTWC began tracking an area of convection west of the Marshall Islands. Developing due to atmospheric instability caused by Typhoon Lex, by the next day, the disturbance had expanded signficantly, with convection being consolidated. ^[31] As a result on 8 August, both the JMA and JTWC designated Marge as a tropical storm, with the latter agency naming it Marge. ^{[9] [31]} Soon after, due to a col and a weakness inside a ridge, Marge began tracking northward. ^[31] Steadily developing, on August 10, both the JTWC and JMA noted that Marge had intensified into a typhoon. ^{[9] [31]} The next day, Marge peaked with 1-minute sustained winds of 125 mph; 205 km/h (110 kn) ^[31] and 10-minute sustained winds of 105 mph; 165 km/h (90 kn) according to the JMA. ^[9] Slightly weakening, on 13 August, Marge encountered strong upper-level westerlies, causing it to rapidly weaken. ^[31] As a result, the next day, Marge transitioned into an extratropical cyclone, causing the JTWC to stop tracking it. ^[31] The JMA kept tracking it until the next day, when it merged with a mid-latitude cyclone. ^{[9] [31]}

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

• On 16 March, JTWC began tracking a tropical disturbance south-southeast of Guam. Four days later, the disturbance developed into a depression. ^[32] Soon after, the depression crossed into the PAR, causing PAGASA to name it Biring. ^[6] 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. ^[32] Despite that, PAGASA kept tracking the remnants until 27 March. ^[6] Across the Philippines, 4 people died due to the depression. ^[33] Due to the system and a high pressure area in mainland Asia, an extratropical warning was issued for the seas near Taiwan. ^[32]
• PAGASA tracked a tropical cyclone from 28 April – 1 May, naming it Konsing. ^[6]
• On 28 June, a tropical depression formed east of the Philippines. ^[34] Two days later, PAGASA began tracking the disturbance, naming it Isang. ^[6] After it made two landfalls in the Philippines, ^[34] PAGASA stopped tracking the depression on 2 July. ^[6] The depression dissipated the next day. ^[34]
• On 15 July, the JTWC began tracking a tropical disturbance near the Philippines. ^[35] The next day, PAGASA began tracking the system, naming it Maring. ^[6] The next day, the JTWC recognized it as a depression, ^[35] just as it exited the PAR. ^[6] After making landfall in China two days later, the JTWC stopped tracking the depression. ^[35]
• 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. ^[36] 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. ^{[6] [36]} In the Philippines, Paring rapidly weakened, and after crossing into the South China Sea, becoming a remnant low on 16 August. ^[6] PAGASA kept tracking the remnants until the next day. ^[36] Scattered showers affiliated with the depression were recorded in Hong Kong. ^[37]

This table summarizes all the systems that developed within or moved into the North Pacific Ocean, west of the International Date Line during 1980. The table also provide an overview of a system's intensity, duration, land areas affected, and any deaths or damages associated with the system.

• Weather of 1980
• Tropical cyclones in 1980
• Pacific typhoon season
• 1980 Atlantic hurricane season
• 1980 Pacific hurricane season
• 1980 North Indian Ocean cyclone season
• South-West Indian Ocean cyclone seasons: 1979–80, 1980–81
• Australian region cyclone seasons: 1979–80, 1980–81
• South Pacific cyclone seasons: 1979–80, 1980–81

Wikimedia Commons has media related to 1980 Pacific typhoon season.

• China Meteorological Agency
• Digital Typhoon
• Hong Kong Observatory
• Japan Meteorological Agency
  • Multilingual Tropical Cyclone Information
• Joint Typhoon Warning Center
• Korea Meteorological Administration
• Malaysian Meteorological Department
• National Weather Service Guam
• Philippine Atmospheric, Geophysical and Astronomical Services Administration
• Taiwan Central Weather Bureau
• TCWC Jakarta
• Thai Meteorological Department
• Typhoon2000
• Vietnam's National Hydro-Meteorological Service{{ 1980 Pacific typhoon season buttons}}