Heat in Talbot, Maryland
Heat July 28, 2002 – July 30, 2002 · Talbot, Maryland
The wider storm
Another hot and very humid air mass moved into the Maryland Eastern Shore on the 28th. In most areas this hot spell produced some of the highest heat indices of the summer as they reached between 105F and 110F during the afternoon of the 29th. A cold front moved through the region during the night of the 30th. While temperatures on the 31st still reached into the 90s, dew point temperatures and the moisture content of the air mass was considerably lower. The apparent temperature (or heat index) matched afternoon high temperatures. More humid air again moved in during the start of August. The string of days with high temperatures of 90 degrees or higher did not end until August 6th. There was one heat related death on the Eastern Shore in Talbot County. A 48-year-old man succumbed from the heat. There were also three instances of dogs dying in vehicles. The hot weather and high humidity levels taxed electric utilities and the PJM Interconnection issued a usage advisory.For most places the highest temperatures with the July part of this hot spell occurred on the 29th and included 99 degrees in Chestertown (Kent County), 97 degrees in Salisbury (Wicomico County), 96 degrees in Easton (Talbot County) and 95 degrees at the Baltimore-Washington International Airport and Stevensville (Queen Anne's County). The hot spell at the end of July cemented the month as being well above normal. Monthly mean temperatures averaged about 2 degrees warmer than normal. The July monthly mean temperature at the Baltimore-Washington International Airport was 78.6 degrees, 2.1 degrees warmer than normal. At Royal Oak in Talbot County, 22 of the 31 days in July had high temperatures of 90 degrees or higher.
Source: NOAA Storm Events Database, event 5308766. Narratives are written by the National Weather Service forecast office that issued the report.
Tornadoes near your address
See every tornado that passed near a place you know, measured to its path.
We couldn’t get your location. Check that location access is allowed for this site, or type an address.