The 2011 Pacific typhoon season was an event in which tropical cyclones formed in the Western Pacific Ocean. The season ran throughout 2011 with most tropical cycle agency storming between May and November. The scope of this article is limited to the Pacific Ocean to the north of the equator between 100th meridian east and the 180th meridian.
Within the Northwestern Pacific Ocean, there are two separate agencies who assign names to tropical cyclones. This can often result in a cyclone having two names. The Japan Meteorological Agency named a tropical cyclone if it was judged to have 10-minute sustained wind speeds of at least 65 km/h (40 mph) anywhere in the basin.
While the Philippine Atmospheric, Geophysical and Astronomical Services Administration assigned names to tropical cyclones which moved into or form as a tropical depression in their area of responsibility between 135°E and 115°E and between 5°N and 25°N even if the cyclone has had a name assigned to it by the Japan Meteorological Agency. Tropical depressions that were monitored by the United States' Joint Typhoon Warning Center were given a number with a "W" suffix. On average, 27 storms form in this basin every year.
During each season several national meteorological services and scientific agencies forecast how many tropical cyclones, tropical storms, and typhoons will form during a season and/or how many tropical cyclones will affect a particular country.
City University of Hong Kong
Since the 2000 Pacific typhoon season, the Guy Carpenter Asia-Pacific Climate Impact Centre (GCACIC), of the City University of Hong Kong (CityUHK), have issued forecasts of activity for each upcoming typhoon season. On May 4 and July 5, 2011, the GCACIC issued forecasts which predicted the amount of tropical cyclones, tropical storms and typhoons there would be during 2011 as well as for how many tropical cyclones will make landfall on China or pass within 100 km (60 mi) of the Korean Peninsula or Japan.[1]
This season the GCACIC predicted in May that 31 tropical cyclones, 27 tropical storms, and 17 typhoons would either form or move into the northwestern Pacific this year.[1] In their July forecast, the GCACIC lowered their prediction for the number of tropical storms developing into a typhoon by one which they blamed on the strength of the India-Burma trough.[5] For Southern China the GCACIC predicted in May that seven tropical cyclones would make landfall, during the year compared to an average of five.[1] They further predicted that five of the cyclones would make landfall on Southern China between May and August, while the other two would landfall between September and December.[1] After two tropical cyclones had made landfall on Southern China during June, the July GCACIC forecast predicted that seven tropical cyclones would make landfall, during the main season between July and December.[5] For the Korean Peninsular and Japan, the GCACIC predicted in May that six tropical cyclones would affect either Japan or the peninsular during the year compared to an average of four, and predicted that there would be an above average amount of landfalls on Japan.[1] After three tropical cyclones affected the region in May and June, the GCACIC predicted that seven tropical cyclones would affect either the Korean Peninsular or Japan during the main part of the season.[5]
Tropical Storm Risk Consortium
Since the 2000 Pacific typhoon season, the Tropical Storm Risk Consortium (TSR) of University College London have issued forecasts of activity for each upcoming typhoon season.[2] Forecasts on the number of tropical storms, typhoons and intense typhoons there would be during 2011 in the Western Pacific were released in March, May, July and August.[nb 1] In all of their forecasts this year, TSR predicted that the season would see activity close to the average with 28 tropical storms, 18 typhoons and 8 intense typhoons developing during the season.[2][3][6]
National meteorological service predictions
On January 17, the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) reported that they were expecting between 20 and 22 tropical cyclones to pass through the Philippine area of responsibility during 2011.[8] On March 23 the Hong Kong Observatory (HKO), reported that they had predicted that 6-9 tropical cyclones would affect Hong Kong during the season.[9] On April 26, the Thai Meteorological Department predicted that 2 tropical storms would affect Thailand during 2011. They predicted that 1 would move through Vietnam and affect Upper Thailand, during August or September. While the second tropical storm was expected to move through Southern Thailand during October or November.[10] On June 30, Taiwan's Central Weather Bureau predicted that the 2011 season would be near its normal climatic average of 25.7, and predicted that 22-26 tropical storms, would occur over the Western Pacific during 2011, with 3 to 5 of them affecting Taiwan.[4]
On April 1, the Japan Meteorological Agency (JMA) and Joint Typhoon Warning Center (JTWC) began monitoring an area of low pressure associated with intermittent convection over the South China Sea, roughly 535 km (335 mi) east-southeast of Ho Chi Minh City, Vietnam.[11] The former of these two agencies immediately declared the system a tropical depression, the first of the 2011 season.[12] Following further development of the system, most notably convective banding around the low-level circulation center,[13] the JTWC issued a Tropical Cyclone Formation Alert on the storm.[14] Early on April 2, the agency followed through with this alert and designated the low as Tropical Depression 01W.[15] However, within hours of this, the depression became devoid of convection as wind shear buffeted the system. This prevented the cyclone from intensifying beyond depression status as it remained nearly stationary.[16] Failing to regain convection by April 3, the depression degenerated into a remnant low and the final advisory from the JTWC was issued.[17] The JMA continued to monitor the system as a tropical depression for another day before issuing their last warning on the system.[18]
On March 30, the JMA began monitoring an area of low pressure southwest of Yap.[19] By April 2, the system developed a low-level circulation, though convection appeared disorganized. Exhibiting good outflow within a region of weak wind shear, the low was anticipated to develop further over the following several days as it drifted west-northwestward.[20] After briefly stalling early on April 3,[21] the storm turned towards the east. Additionally, the JMA considered the system sufficiently organized to be declared a tropical depression.[22] As the system was to the west of 135°E, PAGASA began issuing advisories on the depression as well, assigning it the name "Amang".[23] Tracking northeastward, the depression eventually developed enough convection to be declared Tropical Depression 02W by the JTWC on April 4. However, this was expected to be brief as a decaying frontal boundary approached from the west and prompted the system to undergo an extratropical transition.[24] This intensification prompted the National Weather Service (NWS) in Tiyan, Guam to issue a tropical storm warning for the islands of Agrihan, Pagan and Alamagan.[25] Interacting with the front and high wind shear, the system became partially exposed and elongated as it moved over cooler waters.[26] Early on April 6, the JTWC issued their final advisory on the depression as it began to dissipate over open waters.[27] Following degradation of the storm's structure, the NWS discontinued warnings for the Mariana Islands on April 6.[28] The JMA continued to monitor the system for several more hours before ceasing advisories on it as well.[29]
Early on May 4, an area of low pressure formed about 140 km (85 mi) to the west of Palau Island.[30] On that same day, the low pressure starts to strengthen rapidly with improved LLCC, tightly–wrapped shallow convective banding and a well–defined center. On the next day the low pressure starts to move northwest in general direction to the seas east of Philippine Islands. However it remained almost stationary by afternoon due to the influence of high pressure in the northeast of the system. By that time, its LLCC starts to become elongated and the system was also in favorable sea surface temperatures with low vertical wind shear. Later of that day, its LLCC starts to consolidate again and the system starts to move northwest slowly, whilst the Japan Meteorological Agency upgraded the system into a tropical depression[31] In the afternoon of May 6, Joint Typhoon Warning Center upgraded the low pressure into a tropical depression. In the same evening, PAGASA upgraded the low pressure into a tropical depression and assigned its local name 'Bebeng'. In the afternoon of May 7, JMA upgraded the tropical depression to a tropical storm, and assigned the name 'Aere'. During the early morning of May 12, the JMA downgraded Aere to a tropical depression while south of Kyushu Island.
Throughout the Philippines, multiple agencies activated their emergency plans as the storm approached. The Armed Forces of the Philippines, the Philippine National Police, and the Philippine Coast Guard were all placed on standby to deploy to areas struck by Aere once the storm passed. Several ports were affected by the storm, stranding 1,379 passengers by the afternoon of May 7.[32] According to the National Disaster Risk Reduction and Management Council, at least 35 people have been killed and two more are missing as a result of Aere. Agricultural losses are estimated at PHP1.37 billion (US$31.7 million).[33] Widespread flooding and landslides damaged homes, blocked off roads and severed communications. In Catarman, Northern Samar, 377.4 mm (14.86 in) of rain fell in just 24 hours, resulted in significant flash flooding.[34]
On May 19, the JTWC reported that an area of low pressure had persisted about 510 km (320 mi) to the southeast of Yap. As the system moved towards the northwest under the influence of a subtropical ridge of high pressure, it rapidly consolidated in an area of light to moderate vertical windshear. The JMA then started to monitor the system as a tropical depression later that day, before the JTWC designated it as Tropical Depression 04W early on May 20. The JTWC then reported later that day that the depression had intensified into a tropical storm with windspeeds of 65 km/h (40 mph), however it later reported that it had overestimated the windspeeds and consequently lowered the storm's status to a tropical depression, based on observations from Yap island. Late on May 21, both the JMA and the JTWC reported that the depression had now become a tropical storm with the JMA naming it as Songda. Over the next couple of days, the system gradually intensified further while moving northwest into PAGASA's area of responsibility. PAGASA named it as Chedeng. At 1200 UTC on May 24, the JTWC reported that Songda had intensified into a typhoon. 12 hours later the JMA followed suit while the system was about 800 km (500 mi) to the southeast of Manila in the Philippines. It rapidly intensified into a Category 5 typhoon. In the afternoon of May 29, Songda became extratropical south of Shikoku Island.[35]
Although Songda remained offshore, heavy rains within the typhoon's outer bands impacted the Philippines, causing significant flash flooding and landslides. Four fatalities are attributed to the system there.[36] Further north, Okinawa experience intense wind gusts, measured up to 198 km/h (123 mph), along with torrential rain.[37] Extensive damage took place across the area with losses reaching ¥23.2 billion ($287 million);[38] however, there were no fatalities.[39] As it became extratropical, Songda brought heavy rains from Kyushu to eastern Honshu, causing significant flooding. At least 13 people were killed in the country and an estimated 400,000 had to be evacuated around Tokyo alone.[40][41]
During the evening of May 31, the JMA upgraded an area of low pressure to a tropical depression. Initially, the tropical depression was about 400 km (250 miles) southwest of Hong Kong.[42] The system did not develop further and was downgraded to an area of low pressure by the JMA on June 2.
On early June 8, an area of low pressure formed about 10 km west of Cebu City, Philippines. As it moved towards the Mindoro Strait the JMA and JTWC began to monitor the system. In the early morning hours of June 9, the Philippines' PAGASA upgraded the system to a tropical depression and reported the storm center to be about 450 km west of Dagupan City in the Philippines. The next day, the JMA and JTWC upgraded the tropical depression into a tropical storm, with the JMA naming it Sarika. During the morning of June 11 the JTWC downgraded Sarika to a tropical depression after making landfall in Shantou, China. The JTWC soon issued their final advisory on Sarika. Sarika made landfall on mainland China with winds of 75 km/h (45 mph). As a result of the storm, 23 people were killed in Xianning, and ten more were declared missing. Damages from Sarika are estimated at $248 million.[43]
Early June 15 an area of low pressure area embedded along the Intertropical Convergence Zone about 250 km west of Puerto Princesa, Palawan. As is moved towards the South China Sea, both the JMA and the JTWC started monitoring it. During the morning of June 15, the JMA upgraded it into a tropical depression. Due to an anticyclone, the system dissipated during the early morning of June 16,as it made landfall in Hong Kong.As it drifted over Hong Kong, the Hong Kong observatory's radar captured the center of the system.[source?]
On June 15, the JTWC started to monitor an area of disturbed weather that was about 1350 km (835 mi), to the southeast of Manila, Philippines. Over the next couple of days the system gradually developed further, before late on June 16, the JMA, JTWC and PAGASA, all reported that the system had developed into a tropical depression, with PAGASA naming it as Egay. Egay continued to develop during June 17 as it moved towards the northeast, and on June 18 the JTWC reported that Egay had intensified into a tropical storm. Late on June 19, the JTWC downgraded Egay to a tropical depression, but they upgraded Egay again to a tropical storm on June 20. Early on June 20, the JTWC downgraded Egay to a tropical depression again. On June 21, the JMA upgraded the system into a tropical storm and named it Haima, with the JTWC following suit on June 22.
During the evening of June 23, the JTWC downgraded Haima to a tropical depression after making landfall in Zhanjiang, Guangdong, China but upgraded it to a tropical storm again on June 24. Early on June 25, Haima became a tropical depression after moving inland in Vietnam. As it made landfall over Hanoi, Vietnam, the JTWC and the Hong Kong Observatory downgraded Haima to a low pressure area.
Early on June 20, and area of low pressure about 760 km (470 miles), east of the Philippines began to be monitored by both the JTWC and JMA. That evening, the JTWC issued a Tropical Cyclone Formation Alert. Soon afterwards, PAGASA upgraded the system into a tropical depression, naming it as "Falcon". At the time of the upgrade, Falcon was about 1000 km (620 miles), east northeast of Cebu City. During the evening of June 21, the JTWC also reported that Falcon had strengthened into a tropical depression. On June 22, both the JTWC and the JMA upgraded Falcon into a tropical storm, and the JMA named it Meari. Meari leaves Philippines with 2 deaths and 5 missing. In the afternoon on June 24, the JMA upgraded Meari to a severe tropical storm as it passed Okinawa, Japan.
On June 26, Meari rapidly moved to the Yellow Sea but slowly passed Weihai, Shandong, China, and then the JMA downgraded Meari to a tropical storm on the same day. On June 27, the JTWC downgraded Meari to a tropical depression before it made landfall in North Korea, and the JMA reported that Meari became a low pressure area later.
Heavy rains from the storm's outer bands triggered significant flooding and landslides in South Korea. At least nine people were killed and three others were reported missing across the country.[44] In North Korea, heavy rains from the storm caused widespread flooding and damage. At least 160 homes were destroyed and 50,000 hectares of crops submerged. Several reports of confirmed fatalities arose but no details on how many were given to news agencies.[45]
Late July 9, 2011, an area of low pressure area formed about 300 km (186 mi) east of Aurora. The center was 460 km (290 mi) north of Basco, Batanes.[46] On the morning of July 9, JMA upgraded the low pressure area into a tropical depression and it was 450 km northeast of Cagayan. In the afternoon, PAGASA upgraded the low pressure area into a tropical depression and named it Goring. After moving to Fujian, China, it weakened into an overland low pressure area on the evening on July 10.The remnant low of Goring appears to have redeveloped into a Tropical Depression on July 16
On July 11, both the JMA and JTWC upgraded a tropical disturbance to a tropical depression which was near Minamitorishima. On July 12, both the JMA and JTWC upgraded the system to a tropical storm and named it Ma-on. Early on July 13, the JMA upgraded Ma-on to a severe tropical storm. Late on July 13, both the JMA and the JTWC upgraded Ma-on to a typhoon. After absorbing Tokage, Ma-on reached its peak strength on July 16. The PAGASA named it Ineng on July 17.
As Ma-on was affecting Japan, the JTWC downgraded it to a tropical storm in the evening on July 19. Ma-on made landfall in Tokushima later. The JMA downgraded Ma-on to a severe tropical storm after it made landfall in Wakayama early on July 20. The JTWC downgraded Ma-on to a tropical depression on July 21 and discontinued advisories the following day. The JMA downgraded Ma-on to a tropical storm early on July 23. On July 24, Ma-on weakened into an extratropical cyclone east of the Tōhoku region.
A low pressure area has formed about 740 km north-northwest of Palau. Early on July 14, the JMA upgraded it into a tropical depression, and the JTWC issued a Tropical Cyclone Formation Alert. On July 15, the JMA upgraded the system to a tropical storm and named it Tokage, and the JTWC upgraded it to a tropical depression later. PAGASA also upgraded it to a tropical depression and named it Hanna. Due to the Fujiwhara effect, Typhoon Ma-on, the powerful storm just northeast of Tokage, later weakened Tokage to a tropical depression and completely absorbed it early on July 16.
It can be traced back to a Tropical Depression on July 10, which made landfall over Fujian, China.The remnant low of the weak depression drifted back south, and entered the South China Sea on July 13, and later started to reintensify as it drift back inland, the JMA reported that a low has strengthen into tropical depression as it drifted over Guangdong, China on July 16. On July 17, the depression dissipated completely.
Originally a low pressure area, the JMA reported that a tropical depression formed from it in the Gulf of Tonkin near Guangdong, China on July 16. However, it quickly dissipated after only six hours.
Early on July 22, an area of low pressure formed to the east of Philippines.[47] The system gradually drifted west over the next few days and late on July 24, the Joint Typhoon Warning Center Started Monitoring the system as a Tropical Depression.[48] Early the next day, the Japan Meteorological Agency (JMA) upgraded the area of low pressure into a Tropical Depression.[49] A few hours later, the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) started monitoring the system as a Tropical Depression and named it 'Juaning'.[50] The system continued to drift westwards and strengthened rapidly, that on midnight, that day, the JMA furhter upgraded the system into a Tropical Storm, naming it Nock-Ten.[51] Early on July 27, the JMA reported that Nock-ten continued to strengthen and upgraded it into a Severe Tropical Storm.[52] A few hours later, the JTWC reported that Nock-ten rapidly intensified to a category 1 typhoon and made its landfall over northern Aurora (province) and started weakening.[53] Later the same day, the JMA reported that Nock-ten has exited the Luzon island at Candon maintaining severe tropical storm strength.[54] However, overnight, the storm rapidly weakened and the JMA downgraded it into a minor tropical storm the next day.[55] However, on July 29, the storm gradually regained strength and approached south China coast at Qionghai, China.[56] Later that day, the storm strengthened over land and headed north towards Hainan's provincial capital region Haikou.[57] Over the next day, the storm drifted to the west and made landfall over Northern Vietnam.[58] The storm weakened rapidly and at midnight that day, the JMA, issuing their final warning on the system, Downgraded it into a tropical low.[59]
The provinces of Albay and Camarines were reported to be completely flooded by the rain.[60] Minor damage to rice crops was reported. More heavier rains were expected throughout the day as the system has exited land into south china sea and will soon start reintensifying.[61] The number of missing was also pushed up to 31 after 25 crewmembers of a fishing boat were reported missing when their fishing boat was caught in the storm off Masbate.[62] Nock-ten suspended all classes in Luzon from Pre-school to college levels on July 26 and 27.[63] In Northern Luzon, Nock-ten poured down heavy rainfall becoming widespread flooding in the area. The national roads were impassable and landslides were also reported.[64] About 26 domestic flights were cancelled from July 26 to 27 due to heavy rains and strong winds.[65]
Late on July 23, an area of low pressure formed to the southeast of Chuuk.[66] the system gradually drifted to the west and on July 25, the JTWC upgraded the low pressure area to a tropical depression. At that time, it was about 505 nautical miles (935 km; 581 mi) to the west of Guam.[67] At midnight, that day, the JMA started monitoring the system as a tropical depression.[68] Early on July 28, the JTWC upgraded the system into a Tropical Storm.[69] A few hours later, the JMA too upgraded the system to a tropical storm, naming it Muifa.[70] Soon, the storm moved into the Philippine Area of Responsibility (PAR), and the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) named it Kabayan.[71] The storm gradually drifted north over the next day maintaining strength. On the night of July 29, Muifa was upgraded into a Severe Tropical Storm.[72] Overnight, the storm strengthened rapidly and was upgraded into a Typhoon the next morning.[73] The storm strengthened so rapidly, and the JTWC reported that the storm's peak winds were reaching 140 knots (260 km/h; 160 mph) (1-min sustained), as it strengthened into a Category 5 Typhoon. However, the typhoon could not maintain Category 5 strength for a long time. According to the JTWC, On July 31, the typhoon interacted with an upper-level trough and weakened into a Category 4 Typhoon on the SSHS.[74] The system gradually moved north, then turned west and drifted towards Okinawa, before turning northwest again, when it was finally downgraded into a Tropical Storm by the JTWC.[75] Soon afterwards, the JMA too downgraded Muifa to a Severe Tropical storm.[76] After weakening to a tropical storm, Muifa made landfall at the estuary of the Yalu River on August 8, and the JTWC issued the final warning. Early on August 9, Muifa weakened to a tropical depression in Northeast China and became a low pressure area later.
Muifa killed 2 men, as their boat was capsized in the vicinity of Hagonoy, Bulacan and Pampanga Delta.[77] Due to the southwest monsoon enhanced by Muifa, it caused heavy rains in several parts of Luzon including Metro Manila. Early of August 2, the Malacañang Palace suspended government offices and Pre-school to college level in NCR.[78] Nearby provinces like Calabarzon (Region IV-A) also suspended their classes. In Marikina 200 residents or 31 families living in communities along the Marikina River have sought shelter in evacuation centers.[79]
On July 28, an area of low pressure formed about 85 nautical miles (157 km; 98 mi) to the West of Guam.[80] Over the next few days, the system gradually drifted to the northwest and on July 31, the Japan Meteorological Agency (JMA) upgraded the low into a Tropical Depression to the west of Philippines.[81] Later that day, The Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) started monitoring the system as a tropical depression and named it Lando. The system slowly tracked northward. However, on the next day, due to Fujiwhara effect, Typhoon Muifa the much more powerful system, just to the northeast of Lando, weakened Lando.[82] As a result, the PAGASA issued their final warning on the system, downgrading it to a tropical low.[83] But despite this, Tropical Depression Lando regenerated soon afterwards, and the JMA reissued their advisories on Lando. Tropical Depression Lando continued to persist for another day, as it slowly tracked eastward, just off the western coast of Luzon. Then, during the late afternoon of August 2, the JMA stopped tracking Lando, as it had dissipated. Early on August 3, the remmants of Tropical Depression Lando dissipated completely, without ever reaching Luzon.
Early on August 3, the Japan Meteorological Agency (JMA) upgraded an area of low pressure near Wake Island to a tropical depression.[84] The system intensified rapidly and just 6 hours later, the JMA upgraded the system to a tropical storm, naming it Merbok.[85] Soon, the Joint Typhoon Warning Center (JTWC) started monitoring the system as a tropical depression, and upgraded it to a tropical storm later.[86] Merbok began to move westward slowly, but soon afterwards, it turned northwest and gradually drifted in that direction. Late on August 5, the JMA upgraded Merbok into a Severe Tropical Storm.[87] Early on August 6, the JTWC upgraded Merbok into a Category 1 Typhoon 830 nautical miles (1,540 km; 960 mi) East-southeast of Tokyo, Japan.[88] Early the next day, the storm's winds reached a peak of 80 knots (150 km/h; 92 mph) (1-min sustained) on the SSHS.[89] Later that day, the system was caught in a moderate Vertical Wind Shear and started weakening.[90] On August 8, the system started accelerating towards north at the speed of 20 knots (37 km/h; 23 mph) and was gradually diminishing because of colder and colder sea surface temperatures and unfavorable conditions.[91] As a result, the JMA reporting that the system was no longer a Severe Tropical Storm, downgraded Merbok to a Tropical Storm.[92] Late on that day, the system started showing extratropical characteristics as the convection near the eye dissipated rapidly. Thus, the JTWC issued their final warning on the system reporting that the system was no longer tropical.[93] Later, the JMA, issuing their final warning on the system, reported that the system was no longer tropical.[94]
Early on August 3, a tropical depression formed near the Bonin Islands. The system slowly began to track northwestwards, towards Japan. Late on August 4, the system dissipated near the Kii Peninsula.
Late on August 8, the JMA upgraded a low pressure area to a tropical depression west of Guam, and the JTWC issued a TCFA.[95][96] The system gradually drifted north and early on August 10, the JTWC started monitoring the system as a tropical depression and designated it with 13W.[97] Initially, the JMA predicted the system to strengthen into a tropical storm, but on August 11, as it moved further north into cool waters and experienced unfavourable conditions, the JMA issued their final advisory.[98] Later, the JTWC too issued their final warning on the system, reporting that it has moved into a subtropical ridge and was expected to dissipate into a remnant low.[99] However, the JMA continued to track the remants as a weak tropical depression over the next few days until the system dissipated on August 15.
Late on August 8, the JMA upgraded an area of low pressure to a tropical depression, to the northwest of Minamitorishima.[100] The system gradually moved to the northeast. On August 10, the system was caught in a moderate vertical wind shear and due to cold sea surface temperature, the system dissipated into a remnant low.[101]
On August 19, a low pressure area developed east-northeast of Guam.[102] Early on August 20, the system developed a broad area of low level circulation center and a good divergence aloft becoming more well defined.[103] Later that day, the JMA upgraded the system to a tropical depression southeast of the Bonin Islands.[104] On August 22, the system started interacting with an anticyclone and was exposed to a strong vertical wind shear, prompting the JMA to stop monitoring the system as a tropical depression, as the system dissipated to a remnant low.[105][106] However, at midnight, the same day, the remnants regenerated, and the JMA started tracking the system as a tropical depression again, until it last appeared near Okinawa, Japan on August 25, as the system dissipated completely.[107][108]
Late on August 19, an area of low pressure developed north of Palau.[109] Early on August 20, the system became more better organized and developed a low-level circulation center.[110] The system then turned north and continued to drift north until on August 21, when the JMA upgraded the low pressure area to a tropical depression east of Philippines.[111] The JTWC also issued a Tropical Cyclone Formation Alert (TCFA) on the system reporting that the system was becoming more well organized.[112] Later that day, the PAGASA started monitoring the system as a tropical depression and named it Mina.[113] Late on August 22, the system became more well organized prompting the JTWC to initiate advisories on the system, designating it with 14W.[114] On August 23, the JMA upgraded 14W to a tropical storm, naming it Nanmadol.[115] Overnight, the system continued to intensify and early on August 24, the JMA upgraded Nanmadol to a severe tropical storm.[116] Later that day, convective banding improved and Nanmadol developed an eye-like feature.[117] As a result, Nanmadol continued to intensify rapidly and became a typhoon, by midnight, that day.[118] Nanmadol continued to drift northeast and made landfall over Gonzaga, Cagayan, Philippines with strong winds of over 95 knots (176 km/h; 109 mph).[119] Nanmadol weakened significantly after interacting with land and early on August 28, the JMA downgraded Nanmadol to a severe tropical storm.[120] Late on August 28, Nanmadol made its second landfall over Taimali in the Taitung County of Taiwan and started weakening.[121] Landfall weakened the system rapidly prompting the JMA to downgrade Nanmadol to a tropical storm with winds of under 45 knots (83 km/h; 52 mph).[122] Soon it started experiencing strong wind shear and continued weakening. The shear pushed convection about 70 knots (130 km/h; 81 mph) south of the LLCC. The system also accelerated towards China at 08 knots (15 km/h; 9.2 mph) and weakened to a minimal tropical storm.[123] After its third landfall over Fujian, China, Nanmadol weakened rapidly prompting both the JTWC and the JMA to issue their final warnings on the system.[124][125]
On August 27, five people died after Nanmadol caused landslides.[126] At least two Filipino fishermen were reported to be missing after Nanmadol's strong winds whipped up large waves.[127]
Late on August 22, an area of low pressure developed to the west of Guam.[128] At midnight that day, the system became sufficiently well organized that the JMA started tracking it as a tropical depression.[107] On August 23, the system moved into an environment of low wind shear and warm sea surface temperatures prompting the JTWC to issued a TCFA on it.[129] By August 25, the system grew strong enough that the JMA upgraded it to a tropical storm, naming it Talas.[130] Later that day, the JTWC followed suit and initiated advisories on Talas.[131] Talas continued to strengthen and by midnight that day, it became a severe tropical storm.[132] Over the next few days, Talas continued to drift north very slowly until late on August 29, when the JMA upgraded Talas to a typhoon.[133] Soon, a subtropical ridge to the west of the storm weakened and the subtropical ridge to the east of the system pushed Talas to the west. As a result, Talas accelerated towards the west maintaining strength and outflow.[134] An upper-level cyclone over the system suppressed the convection and kept it from reaching the center. Therefore, Talas remained weak and did not strengthen further. Convection never managed to consolidate the center and convective banding remained well away from the fully exposed low-level circulation center.[135] The convective banding continued to expand more and more with the outer rainbands already brushing parts of Japan. Coastal areas in the nation have already reported gale-force winds several hours before landfall, while the Omega block continued to drive Talas towards the nation.[136] Land interaction weakened Talas, prompting the JMA to downgrade Talas from a typhoon to a severe tropical storm with winds of under 60 knots (110 km/h; 69 mph).[137] Early on September 3, Talas made landfall over Aki, Japan.[138] After landfall, Talas accelerated north at over 13 knots (24 km/h; 15 mph) and its central convection became significantly eroded and was displaced to the northeast as Talas was exposed to a very strong wind shear of over 50 knots (93 km/h; 58 mph) that made the LLCC very distorted and difficult to pin-point. Talas was embedded in a baroclinic zone and the JTWC anticipated an extratropical transition, which prompted them to issue their final warning on the system.[139] On September 5, the JMA issued their final warning on the system, reporting that Talas has become extratropical on the Sea of Japan.[140][141]
On September 1, a low pressure area formed to the northeast of Guam.[142] On the next day, the JMA started monitoring the low pressure area as a tropical depression.[143] Soon, the system developed a well-defined but partially exposed low-level circulation center (LLCC), prompting the JTWC to issue a tropical cyclone formation alert.[144] On September 3, the central convection around the LLCC deepened with favorable equatoward outflow prompting the JTWC to initiate advisories on the system, designating it with 16W.[145] Soon, 16W accelerated north at over 18 knots (33 km/h; 21 mph) with its LLCC being being consolidated by convection. Also, data from an ASCAT scatterometer pass revealed that the LLCC was tightly wrapped with 40 knots (74 km/h; 46 mph) winds prompting the JTWC to upgrade 16W to a tropical storm.[146] An Aqua microwave imagery depicted that the LLCC remained partially exposed though consolidated with deep central convection. Albeit in an area of moderate vertical wind shear, an anticyclone enhanced northeastward outflow while a tropical upper tropospheric trough (TUTT cell) suppressed the outflow towards the west.[147] As 16W continued to accelerate north at a staggering 35 knots (65 km/h; 40 mph), convective banding became fragmented and detached behind the main area of central convection.[148] However, the outflow to the southeast of the storm remained favorable and 16W continued to strengthen, prompting the JMA upgraded the system to a tropical storm, naming it Noru.[149]
Late on September 4, Noru's LLCC that remained partially exposed since formation unexpectedly became elongated and started weakening. However, data from an ASCAT scatterometer pass depicted that the LLCC had an expansive area of strong tropical storm force winds along the eastern and northern peripheries. A TUTT cell wrapped the east and northeastern sides of Noru suppressing its outflow.[150] Soon, the convective banding, which was already fragmented started becoming disorganized causing Noru to start weakening. A new TUTT cell developed over the system and started restraining outflow.[151] As a result, the LLCC became fully exposed and virtually lacked convection. The TUTT cell moved over Noru snuffing outflow in all directions and sheared the remnant central convection, prompting the JTWC to downgrade Noru to a tropical depression.[152] However, data from an scatterometer pass depicted that Noru had winds of over 35 knots (65 km/h; 40 mph) near the center, prompting the JTWC to reupgrade the system to a tropical storm.[153] On September 5, Noru started to appear like a hybrid system, primarily showing subtropical characteristics. The JTWC added that Noru was undergoing an extratropical transition and would become an extratropical cyclone within 24 hours.[154] Noru continued to transition into an extratropical cyclone with a broadening LLCC and weaker winds at the core, being embedded in an upper-level trough that suppressed the formation of convection within the LLCC.[155] With the extratropical transition well underway, Noru drifted into an area of low sea surface temperatures and started weakening, prompting the JTWC to downgrade Noru to a tropical depression.[156] On September 6, Noru finished the extratropical transition becoming an extratropical cyclone east-southeast of Hokkaido, Japan, prompting the JMA and the JTWC to issue their final warning on the system.[157]
Late on September 4, an area of low pressure developed to the southeast of Okinawa, Japan.[158] Over the next two days, the system drifted north and developed a well defined LLCC with organized convective banding, prompting the JMA to upgrade the low pressure area to a tropical depression.[159] On September 7, convection consolidated the low-level circulation center very well with tightly curved banding wrapped into it. Also, high sea-surface temperatures and very low wind shear caused the system to undergo rapid deepening,[160] prior to which, the JMA upgraded the system to a tropical storm and named it Kulap.[161] However, the system stopped strengthening soon after as the LLCC became partially exposed and the convection was displaced to the south. Kulap remained small in size and dry air entering from the western periphery kept it from strengthening further.[162] Wind shear increased, pushing convection about 180 nautical miles (330 km; 210 mi) south of the LLCC. Also, Kulap was beneath a tropical upper tropospheric trough (TUTT cell) that caused subsidence. A mid-level subtropical steering ridge cuased Kulap to track in a northwestward direction.[163] On September 8, Kulap moved into the east-northeast periphery of the Philippine Area of Responsibility (PAR) prompting the PAGASA to start issuing advisories on the system, naming it Nonoy.[164] However, Kulap quickly accelerated north and exited the PAR on the same evening, prompting the PAGASA to issued their final advisory on the system.[165] After increasing wind shear caused further weakening, the JTWC downgraded Kulap to a tropical depression late on September 8.[166] Early on September 10, the JMA too downgraded Kulap to a tropical depression,[167] and continued to track Kulap's remnants as a tropical depression until it finally dissipated early on September 11.
Early on September 8, a cluster of thunderstorms came together as a low pressure area with imporoving outflow and a developing low-level circulation center (LLCC).[168] Later that day, the JMA upgraded the low pressure area to a tropical depression north-northeast of the Northern Mariana Islands.[169] Over the next two days, the system gradually drifted west and intensified slightly, prompting the JTWC to issue a Tropical Cyclone Formation Alert (TCFA) on it.[170] Convection gradually consolidated the LLCC and the JTWC initiated advisories on the system on September 11, designating it with 18W.[171] The next day, the depression drifted into the Philippine Area of Responsibility (PAR) and the PAGASA initiated advisories on the depression, naming it Onyok.[172] However, just as similar to Kulap, Onyok also exited the PAR in 6 hours from entering the region.[173] In an advisory, the JTWC reported that there were at-least two more vortices associated with the system, that caused an abrupt, erratic movement.[174] However, being in an area of warm sea surface temperatures and low vertical wind shear, the depression continued to strengthen and on September 13, the JMA upgraded the depression to a tropical storm and named it Roke.[175] On September 17, Roke developed a small, deep convective eye promoting the JMA to upgrade Roke to a severe tropical storm with winds of over 50 knots (93 km/h; 58 mph).[176] Between September 19 and 20, Roke underwent Explosive intensification, a more extreme case of rapid deepening that involves a tropical cyclone deepening at a rate of at least 2.5 mbar per hour for a minimum of 12 hours. Also, they added that Roke developed a 10 nautical miles (19 km; 12 mi) eye and a good poleward outflow channel.[177] On September 21, Typhoon Roke made landfall over Hamamatsu, Japan at about 5:00 UTC (14:00 JST).[178] Soon Roke started weakening as cloud tops started getting warmed up and eye diameter started to decrease. However, the system still maintained a near radial outflow and the convective structure continued to remain organized that kept Roke from dissipating rapidly.[179] Although Roke entered a de-intensification phase, it still had plenty of strength that posed a great threat to regions of Japan. Being about 330 nautical miles (610 km; 380 mi) southwest of Yokosuka, Kanagawa, the typhoon accelerated north-northwestward at about 16 knots (30 km/h; 18 mph) with winds of over 100 knots (190 km/h; 120 mph) (1-min sustained) being a Category 3 typhoon on the SSHS.[180] Being embedded in the baroclinic zone, Roke started its extratropical transition. Also, land interaction severely weakened the storm to a minimal Category 1 typhoon with winds of under 70 knots (130 km/h; 81 mph) (1-min sustained).[181] Only six hours later, the storm further weakened and accelerated northeastward at about 31 knots (57 km/h; 36 mph) with rapidly dissipating deep convection completely sheared to the northeast of the LLCC. As a result, the JTWC ceased advisories on the storm, as it became fully extratropical.[182]
Early on September 13, a low pressure area formed northeast of the Northern Mariana Islands.[183] The system gradually drifted north and steadily intensified until the next day when the JMA upgraded the system to a tropical depression.[184] Later on September 14, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system reporting that the system could intensify into a tropical storm within 24 hours from then.[185] Convection rapidly consolidated the center with persistent, deep convection around the northeastern periphery, prompting the JTWC to initiate advisories on the system, designating it with 19W.[186] Soon, the JMA also initiated advisories on the system, upgrading it to Tropical Storm Sonca.[187] In the begging, Sonca seemed to have intensified rapidly since formation, however, soon the storm weakened back to a minimal tropical storm because of dry air entering the LLCC that caused it to elongate and weaken.[188] However, that was not for too long as vigorous convection persisted over the well defined LLCC with tightly curved banding wrapped in, Sonca continued to strengthen gradually and the JTWC reported winds of at-least 50 knots (93 km/h; 58 mph) near the center.[189] As Sonca continued to strengthen, and the JMA upgraded it to a severe tropical storm on September 17.[190] Later that day, Sonca developed a large 10 nautical miles (19 km; 12 mi) ragged eye with deep convective banding tightly wrapped into it.[191] As a result, Sonca strengthened more rapidly and by early the next day, it became a typhoon.[192] On September 18, Sonca reached a peak intensity of 85 knots (157 km/h; 98 mph) (1-min mean) and 70 knots (130 km/h; 81 mph) (10-min mean) and soon the convection around the northern periphery started weakening.[193] Being embedded in a baroclinic zone with low sea surface temperatures, Sonca started its extratropical transition late on September 19.[194] The transition took place relatively fast because of a frontal boundary and the JTWC reported that Sonca became extratropical early on September 20,[195] while the JMA did the same later in the evening.[196]
Early on September 14, the JMA started monitoring a cluster of thunderstorms to the southeast of Taiwan as a tropical depression.[184] But because of the land interaction, the system could not be empowered and the JMA stopped tracking the depression late on September 15, as the system dissipated.[197]
In the evening of September 21, a low pressure area developed to the east-southeast of Palau.[198] The low gradually drifted west and became more well organized prompting the JTWC to issue a Tropical Cyclone Formation Alert (TCFA) on it.[199] Later, the LLCC became well organized with flaring deep convection developing around it, so the JMA started monitoring the low as a tropical depression.[200] Later on September 23, the JTWC also initiated advisories on the system designating it with 20W.[201] Early on September 24, the JMA further upgraded 20W to a tropical storm and named it Nesat.[202] Nesat continued to drift west with expanding deep convection around the entire system and consolidating convection around the LLCC. The mid-level warm anomaly near the system continued to intensify and convective banding near the LLCC became more and more tighter.[203] As a result, the JMA upgraded Nesat to a severe tropical storm on September 25.[204] Late on the same day, the JMA further upgraded Nesat to a typhoon.[205]
On the evening of September 21, at almost the same time when Nesat was first seen, another low pressure area persisted far south of Hong Kong.[198] The low slowly drifted north and strengthened slowly until on September 24, when the JMA upgraded the system to a tropical depression east of Vietnam.[206] Later that day, the JTWC issued a Tropical Cyclone Formation Alert stating that the low could develop into a tropical cyclone.[207] Early on September 25, the JMA upgraded the system to a tropical storm and named it Haitang.
On September 26, the Japan Meteorological Agency (JMA) started to monitor a weak tropical depression. It had developed about 1,260 km (785 mi)* to the northwest of Manila in the Philippines.[208] The next day the JTWC issued a tropical cyclone formation alert on the system.[209] However less than 3 hours later, the JTWC designated it as Tropical Depression 22W. JMA reported that the depression had become a tropical storm and named it Nalgae.[208][210][211]
The storm slowly drifted to the west. It got stronger slowyl. Nalgae developed a microwave eye like feature and well defined convective banding in all the quadrants. The system had a tiny radius of winds. It was still strengthening significantly and was very well defined.[212] On the evening of September 28, the JMA reported that Nalgae continued to intensify. They upgraded it to a severe tropical storm with winds of over 55 knots (102 km/h; 63 mph).[213] On that night, the PAGASA began advisories on Nalgae. They gave it the local name Quiel as it entered the Philippine Area of Responsibility (PAR).[214] Late on September 29, the JMA upgraded Nalgae to a typhoon. Nalgae quickly intensified on September 30, and became a category 4 super typhoon early on October 1. This was just before making landfall over Luzon. Due to land interaction and colder sea surface temperature in the South China Sea, the JMA downgraded Nalgae to a severe tropical storm on October 2. Then a tropical storm late on October 3. The JTWC downgraded Nalgae to a tropical depression on October 4. The JMA also did it on the next day. Later on October 5, the last low of Nalgae dissipated.
Hitting the Philippines just days after Typhoon Nesat, Nalgae caused further damage across Luzon. It was first feared that Nalgae would cause much more damage to Luzon. But damage from the storm was lighter than Typhoon Nesat. Nearly 2,900 homes were destroyed and about another 15,400 took damage. At least 18 people were killed by the storm and another 7 were reported as missing as of October 11. A total of 1,113,763 people were affected by the storm. Total losses in the country reached just over 115 million PHP (US$2.62 million).[215]
On October 7, the JTWC started monitoring a tropical disturbance about 750 km (465 mi) to the south of Hagåtña, Guam.[216] Over the next couple of days the system gradually developed further while moving towards the west. The JMA reported on October 9, that the disturbance had become a tropical depression.[217] Early on October 10, the JTWC upgraded the system to a tropical depression called 23W. The PAGASA also upgraded it to a tropical depression and named it Ramon. On October 11, the JMA and the JTWC upgraded the system to a tropical storm and named it Banyan. Early on October 12, Banyan made landfall over Leyte, Philippines. The JTWC downgraded it to a tropical depression. A half day later, the JMA also downgraded Banyan to a tropical depression. The system dissipated in the South China Sea on October 16.
While going through the Philippines, Banyan had heavy rains across much of the country. This led to widespread flooding. At least ten people were killed by the storm. A total of 75,632 people were affected by the storm.[218]
On December 11, a disturbance formed and stayed near Chuuk. On December 13, the low pressure area quickly got stronger. On the same day, the JTWC upgraded the low pressure to a tropical depression. They named it 27W. The JMA also upgraded it to a tropical depression. The JTWC upgraded the system to a tropical storm on December 14. They then downgraded it to a tropical depression early on December 15. The PAGASA called it Sendong as it entered the Philippine Area of Responsibility. After passing Palau on December 15, both the JTWC and the JMA upgraded the system to a tropical storm. They named it Washi. On December 16, Washi made landfall over Surigao del Sur, a province of the Philippines. Several hours later, Washi arrived at the Sulu Sea and regained its strength quickly. Late on December 17, Washi crossed Palawan, and arrived at the South China Sea. On December 19, Washi weakened into a tropical depression and dissipated.
Storm Names
Within the Northwestern Pacific Ocean, there are two separate agencies who assign names to tropical cyclones which often results in a cyclone having two names. The Japan Meteorological Agency names tropical cyclones should they be judged to have 10-minute sustained windspeeds of 65 km/h, (40 mph), to the north of the equator between the 180° and 100°E. Whilst the Philippine Atmospheric, Geophysical and Astronomical Services Administration assigns names to tropical cyclones which move into or form as a tropical depression in their area of responsibility between 135°E and 115°E and between 5°N-25°N even if the cyclone has had a name assigned to it by the Japan Meteorological Agency.
Tropical Cyclones are named from the following lists by the Regional Specialized Meteorological Centre in Tokyo, Japan, once they reach tropical storm strength.[219] Names are contributed by members of the ESCAP/WMO Typhoon Committee. Each of the 14 nations or territories submitted 10 names, which are used in alphabetical order, by the English name of the country.[220] The next 24 names on the naming list are listed here.
Aere (1101)
Songda (1102)
Sarika (1103)
Haima (1104)
Meari (1105)
Ma-on (1106)
Tokage (1107)
Nock-ten (1108)
Muifa (1109)
Merbok (1110)
Nanmadol (1111)
Talas (1112)
Noru (1113)
Kulap (1114)
Roke (1115)
Sonca (1116)
Nesat (1117) (active)
Haitang (1118) (active)
Megi (unused)
Banyan (unused)
Washi (unused)
Pakhar (unused)
Sanvu (unused)
Mawar (unused)
Philippines
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 10 of which are published each year before the season starts.[221]
During their 2012 annual session the ESCAP/WMO Typhoon Committee said that the name Washi would be retired from its naming lists. The Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) said that the names Bebeng, Juaning, Mina, Pedring were retired from PAGASA's list of local names after they each caused over 1 billion PHP in damages to the Philippines during 2011.[222][223] The name Sendong was also retired from the list after it caused over 300 deaths, when it made landfall on the Philippines during December 2011.[224]
Season effects
This table lists all the storms that developed in the western Pacific Ocean to the west of the International Date Line during the 2011 season. It includes their intensity, duration, name, landfalls, deaths, and damages. All damage figures are in 2011 USD. Damages and deaths from a storm include when the storm was a precursor wave or extratropical low.
↑According to TSR: An intense typhoon is a typhoon that has one-minute winds of at least 175 km/h (110 mph); according to the JMA, an intense typhoon has ten-minute winds of at least 54 m/s (105 kt)
↑"Tropical Cyclone Formation Alert". Joint Typhoon Warning Center. United States Navy. April 1, 2011. Archived from the original on January 23, 2012. Retrieved May 7, 2011. "Archived copy". Archived from the original on May 14, 2009. Retrieved July 31, 2022.{{cite web}}: CS1 maint: archived copy as title (link) CS1 maint: bot: original URL status unknown (link)
↑"Tropical Depression 01W Advisory One". Joint Typhoon Warning Center. United States Navy. April 2, 2011. Archived from the original on January 18, 2012. Retrieved May 7, 2011. "Archived copy". Archived from the original on January 18, 2012. Retrieved September 14, 2022.{{cite web}}: CS1 maint: archived copy as title (link) CS1 maint: bot: original URL status unknown (link)
↑"Tropical Depression 01W Advisory Two". Joint Typhoon Warning Center. United States Navy. April 2, 2011. Archived from the original on January 18, 2012. Retrieved May 7, 2011. "Archived copy". Archived from the original on January 18, 2012. Retrieved September 14, 2022.{{cite web}}: CS1 maint: archived copy as title (link) CS1 maint: bot: original URL status unknown (link)
↑"Tropical Depression 01W Advisory Six (Final)". Joint Typhoon Warning Center. United States Navy. April 3, 2011. Archived from the original on January 19, 2012. Retrieved May 7, 2011. "Archived copy". Archived from the original on January 19, 2012. Retrieved September 14, 2022.{{cite web}}: CS1 maint: archived copy as title (link) CS1 maint: bot: original URL status unknown (link)
↑"Tropical Depression "Amang" Severe Weather Bulletin One". Philippine Atmospheric Geophysical and Astronomical Services Administration. April 3, 2011. Archived from the original on January 18, 2012. Retrieved May 8, 2011. "Archived copy". Archived from the original on July 26, 2009. Retrieved September 14, 2022.{{cite web}}: CS1 maint: archived copy as title (link) CS1 maint: bot: original URL status unknown (link)
↑Michael G. Middlebrooke (April 5, 2011). "Tropical Depression 02W Advisory Number One". National Weather Service Office in Tiyan, Guam. National Oceanic and Atmospheric Administration. Archived from the original on January 19, 2012. Retrieved May 8, 2011. "Archived copy". Archived from the original on January 19, 2012. Retrieved September 14, 2022.{{cite web}}: CS1 maint: archived copy as title (link) CS1 maint: bot: original URL status unknown (link)
↑"Tropical Depression 02W Advisory Five (Final)". Joint Typhoon Warning Center. United States Navy. April 6, 2011. Archived from the original on January 23, 2012. Retrieved May 8, 2011. "Archived copy". Archived from the original on January 23, 2012. Retrieved September 14, 2022.{{cite web}}: CS1 maint: archived copy as title (link) CS1 maint: bot: original URL status unknown (link)
↑Paul Stanko and Marcus Landon Aydlett (April 6, 2011). "Tropical Depression 02W Advisory Number Four". National Weather Service Office in Tiyan, Guam. National Oceanic and Atmospheric Administration. Archived from the original on January 23, 2012. Retrieved May 8, 2011. "Archived copy". Archived from the original on January 23, 2012. Retrieved September 14, 2022.{{cite web}}: CS1 maint: archived copy as title (link) CS1 maint: bot: original URL status unknown (link)
↑"None". Archived from the original on 2010-01-25. Retrieved 2011-09-26. "Archived copy". Archived from the original on 2013-10-13. Retrieved 2011-09-26.{{cite web}}: CS1 maint: archived copy as title (link) CS1 maint: bot: original URL status unknown (link)
↑ 38.038.1(in Japanese) Unattributed (June 23, 2011). "保険支払い２０億円に 台風２号". Okinawa Times. Archived from the original on June 24, 2011. Retrieved July 2, 2011.
↑Joint Typhoon Warning Center (September 27, 2011). "Tropical Cyclone Formation Alert 2011-09-27 06z". United States Navy, United States Air Force. Archived from the original on February 2, 2016. Retrieved September 29, 2011. "Archived copy". Archived from the original on February 2, 2016. Retrieved September 14, 2022.{{cite web}}: CS1 maint: archived copy as title (link) CS1 maint: bot: original URL status unknown (link)
↑Joint Typhoon Warning Center (September 27, 2011). "JTWC Tropical Depression 22W Warning 2011-09-27 09z". United States Navy, United States Air Force. Archived from the original on January 20, 2012. Retrieved September 29, 2011. "Archived copy". Archived from the original on January 20, 2012. Retrieved September 14, 2022.{{cite web}}: CS1 maint: archived copy as title (link) CS1 maint: bot: original URL status unknown (link)
↑Staff Writer (2010-09-22). "Philippine Tropical cyclone names". Philippine Atmospheric, Geophysical and Astronomical Services. The next name will be used Lando Administration. Archived from the original on 2012-01-18. Retrieved 2010-09-23. "Archived copy". Archived from the original on 2009-10-30. Retrieved 2022-09-14.{{cite web}}: CS1 maint: archived copy as title (link) CS1 maint: bot: original URL status unknown (link)
