Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-settings.php on line 570

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/33/d214989360/htdocs/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/33/d214989360/htdocs/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/33/d214989360/htdocs/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/33/d214989360/htdocs/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/33/d214989360/htdocs/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/33/d214989360/htdocs/wp-includes/http.php on line 61

Strict Standards: Non-static method K2::init() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/functions.php on line 31

Strict Standards: Non-static method K2::register_scripts() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 51

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Options::init() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 339

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::init() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 339

Strict Standards: Non-static method K2Header::get_header_width() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/header.php on line 8

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::filter_post_comments() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 166

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458
Category Archive for ‘Nevada’ at Campaign Diaries
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2Header::output_header_css() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 339

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Archive for the 'Nevada' Category


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: Democrats are strong in IL, have a shot in SD; Castle and Burr dominate

I wouldn’t go as far as to describe this week’s polling round-up as generally good for Democrats; after all, numerous of their House incumbents look vulnerable, Rob Portman retains a small lead in Ohio, Castle dominates, Richard Burr is up by double-digits and Pete Domenici is closer to Diane Denish than New Mexico Democrats would like. Yet, there is plenty for the party to point to as evidence that they are managing to stay afloat and that the GOP still has a lot of work to do to ensure they’ll benefit from as big a red wave as they’re hoping to. In particular, Research 2000’s Illinois poll and Quinnipiac’s Ohio survey find Democrats Alexi Giannoulias, Pat Quinn and Ted Strickland in stronger positions than conventional wisdom dictates; Democrats look like they have an unexpectedly credible shot at South Dakota’s governorship; and Rep. Harry Teague is in a far more competitive position than you would expect given that he is often described as one of November’s surest Democratic losers (2 polls have him within the MoE against former Rep. Steve Pearce).

House

New Mexico: It’s rare enough to have one House survey a week that PPP’s decision to test all three of New Mexico’s House races was a one of the week’s treats. The results are encouraging for both parties, though the most poll’s most surprising finding will delight the NRCC: Rep. Ben Lujan, who represents a district Obama won by 23% and who I had never heard described as competitive, leads his two Republican challengers by decidedly underwhelming margins: 42% to 36% against Tom Mullins, 40% to 32% against Adam Kokesh. That’s not to say he will lose, nor that the race will be competitive come the fall, but it does speak to the probability that a number of Democratic districts that are now on no one’s radar screen should find themselves vulnerable in the campaign’s final stretch (see what happened to the GOP in 2006). Interestingly, Rep. Martin Heinrich, a more obvious target since he is a freshman, leads Jon Barela by a somewhat more solid 45% to 36%.

But the more interesting race is happening NM-02, which is not only the state’s most conservative seat (it went for Bush by 17%) but former Rep. Steve Pearce is running for his old seat after running for Governor in 2008. This has led many to think Rep. Teague is one of the fall’s surest losers, which makes Pearce’s 43% to 41% lead seem like it should be a relief for Democrats as it certainly shows Teague is far from a sure loser. (In particular, consider that the traditional rules about how a challenger topping an incumbent in an early poll is clearly favored does not apply here since Pearce is probably better-known than the incumbent.) On the other hand, the poll should not be spun as bad news for the GOP: The bottom-line is that NM-02 is one of the party’s top pick-up opportunities indeed. In fact, Pearce released an internal poll last week showing himself leading 48% to 44%.

SD-AL: Stephanie Herseth Sandlin remains on top of her Republican opponents in a new Rasmussen poll, but Secretary of State Chris Nelson is within striking distance since he holds the incumbent Democrat under 50% and within single-digit: She leads 45% to 38%. Herseth-Sandlin is far stronger against Kristi Noem (49% to 34%) and against state Rep Blake Curd (51% to 33%), which certainly suggests she is in a far stronger position than many of her fellow Democrats. As the poll’s gubernatorial numbers also speak to (see below), South Dakotans don’t look committed to ushering in GOP rule.

Senate

Ohio: Democrats might be losing ground in Senate races left and right, but they remain in striking distance of picking-up Ohio’s open seat according to Quinnipiac’s new poll. Republican Rob Portman is up within the margin of error (40-37) against Democrat Lee Fisher and he leads 40-35 against Jennifer Brunner. These margins are similar to those Quinnipiac found back in November, though it should be said that both Democratic candidates spent much of 2009 crushing Portman by double-digits - an advantage that was erased as the electorate soured on the the party in the latter half of the year. Despite their prominent stature, all three candidates have low name recognition so the next few months could be crucial - starting with the run-up to the Democratic primary.

Florida: Rasmussen found more evidence of Charlie Crist’s collapse this week by showing Marco Rubio crushing him 54% to 36% - an unthinkable result just a few months ago that is now already coming to be expected; the pollster also confirms that Crist’s decline is due to his rising unpopularity among the electorate-at-large and not just among Republicans, since his once impressive approval rating is now down to 52-45. In the general election, both men lead Kendrick Meek by large margins: Crist is up 48-32, Rubio is up 51-31. But is it time to start testing 3-way match-ups with Crist as an independent?

Delaware: For once, Rasmussen and Research 2000 have similar results! The former shows Republican Rep. Mike Castle in control 53% to 32% (though the margin has shrunk by 7% since January) while the latter has him leading 53% to 35%. That does little to change the race’s “likely Republican” rating (especially when we consider Castle’s formidable 65/30 and 65/32 favorability ratings) but given the two candidates’ chances of stature the trendline also confirms it is too early for Democrats to give up.

North Carolina: Rasmussen released the most favorable poll Richard Burr is gotten in quite a while - far more favorable, in fact, than the survey PPP released last week. Not only does the Republican senator have large leads, but he also reaches 50%: He’s up 50-34 against Elaine Marshall and 51-29 against Cal Cunningham. Of course, Democrats long ago realized defeating Burr is a top proposition in this environment, but these numbers are nonetheless ugly for the party. On the other hand, an Elon University poll finds that only 24% of North Carolinians think Burr deserves re-election, versus 51% who think he should be replaced.

Pennsylvania: Franklin & Marshall sends some very ugly numbers Democrats’ way, though the bizarrely high number of undecided makes it hard to do much else than point to the wide disparity between the match-ups among registered voters and among likely voters. In the former group, Arlen Specter leads Pat Toomey 33% to 29% while Joe Sestak is only 3% behind (25-22); in the latter group, Toomey crushes both Democrats - 44-34 against Specter, 38-20 against Sestak. Could there be clearer signs of the turnout gap that’s threatening to submerge Democrats this fall?

Governor

Illinois/Ohio: I mentioned Quinnipiac and Research 2000’s polls finding Democratic Governor Pat Quinn and Ted Strickland in the lead in an earlier post, but the results are counter-intuitive enough that they bear repeating. In Ohio, Quinnipiac shows Strickand leading John Kasich 44% to 39%, which is obviously an underwhelming margin but is nonetheless an improvement over the 40-40 tie Quinnipiac found in November and is a far more encouraging result for Democrat than the large deficits Rasmussen has found in recent months; Strickland had almost started to look like a lost cause, but these numbers from a respected pollster suggest Ohio is definitely still winnable for Democrats.

In Illinois, Research 2000 has Governor Pat Quinn leading state Senator Kirk Dillard and state Senator Bill Brady 46-35 and 47-32. He might remain under 50%, but remember that in early February Quinn looked so damaged that he seemed to be marching towards a primary defeat. Yet, this is now the second post-primary poll to find him in command of the general election (the first was released last week), especially if his opponent is the more conservative Bill Brady - as still looks likely since Dillard has failed to overtake Brady after weeks of provisional ballot.

South Dakota: Would you have expected the week’s polling surprise to be that Democrats have a strong shot at picking up the governorship of this conservative state? Yea, me neither - especially considering that this finding comes out of a Rasmussen poll. Matched-up against three Republicans, state Senate Minority Leader Scott Heidepreim holds his own: While he trails Lieutenant Governor Dennis Daugaard 41% to 32%, he is ahead against two other Republicans: 37% to 29% against state Senator Gordon Howie and 34% to 31% against state Senator Dave Knudson. That is of course nothing huge, but it certainly suggest that South Dakota voters aren’t desperate to jump in the GOP’s bandwagon.

New Mexico: It helps to have a famous name! While Pete Domenici Jr. has never been in the public spotlight before, he shares the first and last name of his father, former Senator Pete Domenici, which explains how his name recognition is so much higher in a new PPP poll than that of his fellow Republican candidates. The general election match-ups show that the contest is winnable by the GOP but that Democratic Lieutenant Governor Diane Denish is the front-runner: She leads Domenici Jr. 45-40, state Rep. Janice Arnold-Jones 47-33 and DA Susana Martinez 46-42. One important factor in this campaign is whether Denish can free herself from Bill Richardson’s shadow: The outgoing governor has a catastrophic approval rating (28% to 63%).

Nevada: Earlier this week, I highlighted a POS poll that showed Governor Jim Gibbons improving his position in the GOP primary, which he was long expected not to have a chance at winning. Now, a Mason-Dixon poll confirms that Gibbons is increasingly competitive against Brian Sandoval: He trails 37% to 30%, whereas he was behind by 17% in Mason-Dixon’s prior poll. Given Gibbons’s worst-in-the-country approval rating of 17%, whether he can find a way to survive the primary will obviously go a long way towards determining the general election: While Sandoval crushes Rory Reid 51% to 29%, the Democrat tops Gibbons 42% to 38%. (The fact that Gibbons is within 4% of Reid says a lot about the latter’s weakness.)

Massachussetts: Despite a weak approval rating (35-54), Deval Patrick manages to stay on top of Suffolk’s general election match-ups because many voters who are discontent with him are choosing to support Democrat-turned-independent Tom Cahill, who enjoys a 31/16 favorability rating. Patrick tops Republican Charlie Baker 33% to 25%, with Cahill receiving 23% and 3% going to Green Party candidate Stein; if the Republican nominee is Christy Mihos, which at the moment seems unlikely given baker’s 47-17 primary lead, Patrick leads Cahill 34% to 26%, with 19% for Mihos. The main reason Democrats can hope that Cahill will actually maintain his level of support and help Patrick survive (whereas Daggett collapsed in New Jersey) is that Cahill is the state Treasurer and is better-known than either Republican candidates.

Wisconsin: Rasmussen’s latest numbers are similar to its previous ones: Republican Scott Walker would dominate Milwaukee Mayor Tom Barrett 49% to 40%, whereas the Democrat would be more competitive if he were to face former Rep. Mark Neumann (44% to 42%). While that’s nothing for Barrett to be ashamed of, the poll also suggests that Barrett is not starting out as the formidable contender Democrats were hoping for. On the other hand, Wisconsin is a state in which we have seen very few non-Rasmussen polls (only a November PPP survey that had Barrett stronger comes to mind), so it would be nice to have more polling firms test this race as well as Feingold’s vulnerability.

Georgia: Former Governor Barnes manages to stay competitive in Rasmussen’s latest poll, but the match-ups are not as favorable than the pollster found last month: Barnes now trails the three most prominent Republican candidates (45-37 against State Insurance Commissioner Oxendine, 43-37 against Rep. Deal, 45-36 against SoS Handel) while tying state Sen. Johnson at 37%. Barnes would have been better-served by a more favorable environment, but he remains in a competitive position.

Rhode Island: Brown University’s poll finds a wide-open race with an early edge for Republican-turned-independent Linc Chaffee. If the Democratic nominee is Frank Caprio, The former Senator leads 34% with 38%, with 12% to the Republican Robitaille; if the Democratic nominee is Patrick Lynch, Chaffee leads by a wider 33% to 18%, with 14% for the Republican.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

While the Reids are in rough shape, Nevada Dems should keep up hope

State Senator Mark Amodei has dropped out of the Nevada Senate race. Despite or because (depending on your take on the cycle) the fact that he is the only candidate who holds elected office, he failed to get much traction; he was unable to overcome his lack of name recognition due to his meager fundraising.

He was hoping he could have a geographical advantage as the only candidate from Northern Nevada, while David Tarkanian and Sue Lowden both come from the Las Vegas region; but Sharron Angle’s entry in the race blew to that prospect. He also had no obvious ideological niche to exploit: While Lowden is a fragile front-runner due to hostility among some conservatives, Amodei couldn’t expect much support from the party’s most motivated faction given that his name was closely associated with a push to raise or create twelve taxes at once - a tough record to defend in a GOP primary.

His withdrawal leaves a crowded field battling it out for the right to face Reid: former party chair Lowden, real estate developer Tarkanian, former Assemblywoman Angle and banker Joe Chachas, and at least 5 other lower-profile candidates.

Three weeks from the filing deadline, I have to admit that I am surprised the Republican field remains as underwhelming as it was in the fall: Sure, Reid is so unpopular that one of these individuals might very well beat him in November, but the NRSC could make this strong opportunity a near-lock if it convinced a politician like Rep. Dean Heller to jump in the Senate race after all - just as happened in Arkansas when Rep. Boozman announced he’d challenge Blanche Lincoln. Yet, it looks like Lieutenant Governor Brian Krolicki’s decision not to run a few weeks ago was the last recruitment shoe to drop.

In what looks like it could be at least a 9-way race, it should not take a large share of the vote for a Republican to advance to the general election, which means any of the candidates I mentioned above has a shot at the nomination.That includes New York banker John Chachas, who at the moment has no name recognition whatsoever but he is apparently willing to spend a lot of money: As of the end of 2009, he had donated $1,3 million of his own fortune to his campaign. Of course, many unknown businessmen who try to buy themselves Senate seats fail (the latest: Steve Pagliuca) but Lowden and Tarkanian are weak front-runners. In fact, Chachas drew favorable reviews for his latest debate performance, whereas Lowden has failed to impress.

The confusion that is still reigning in the GOP field (and the ensuing prospect that the party will produce a weaker nominee than it should) is not the only factor that should give Harry Reid hope he could still survive. I already mentioned a few weeks ago that a Tea Party had qualified as an official Nevada party and was planning on fielding a candidate in the Senate race. We now have our first look at the effect this would have on the general election, via a Public Opinion Strategies survey that tests a three-way race between Reid, Tea Party candidate Jon Ashjian (who seems to have no public record I can find) and various Republicans - and while Reid’s standing is certainly nothing he should boast about, these have to be the most favorable match-ups he has seen since the summer.

While Reid has routinely trailed by double-digits in polls conducted since August (and this poll makes it clear why, since Reid’s favorability rating is a dismal 35-58) he trails Lowden by a less catastrophic 5% (42-37), with Ashjian at 9%. Against Tarkanian, Reid is only down 40-39, with Ashjian at 11%. Against Angle, Reid actually grabs a 37% to 32% lead, with Ashjian at 16%. The clearest sign that conservative-minded voters are just as willing to vote for a Tea Party than for a GOP nominee when they know about neither candidate comes in the Chachas match-ups, as Ashjian comes out ahead of the banker (22-21) with Reid at 39%.

Of course, it is very possible that Ashjian’s support recedes to the 5%-7% range once a Republican is chosen as the nominee and increases his or her notoriety; but his presence on the ballot certainly looks like it could have a non-marginal effect on the race. The GOP could be in particular trouble if Lowden is the nominee: While Ashjian receives his lowest share of the vote against her, she would probably give him the biggest opening since she inspire mistrust among the hard-right. With Jim DeMint opening the door to supporting third-party bids against the Republican nominees, it seems more likely that Ashjian could hope for such institutional backing if he faces Lowden than Tarkanian or Angle. (While I am more unsure about Chachas’s ideological profile, his background as a New York banker could allow the Tea Party to play a more populist card.)

Dems can also hope for positive developments in non-federal races

The POS poll I cited above also suggests that all is not lost for Democrats over in the Governor’s race: While no one is denying that Governor Jim Gibbons is the clear underdog in his primary fight against former Attorney General Brian Sandoval, the same survey finds him trailing only 38% to 32%, within the margin of error. Voters who have definitely made up their mind favor Sandoval by just 1%, suggesting the Governor is closer to surviving the primary than we might think.

However unpopular incumbents get, they more often than not keep the support of their own party’s base, which is what makes the position of politicians like David Paterson and pre-switch Arlen Specter so shocking. Gibbons is probably too damaged to have a shot at moving to the general election, but his dismal standing among the electorate-at-large (a 29-58 favorability rating) does not mean he is universally despised among Republican voters. Of course, for Gibbons to pull a June upset would be amazing news for Democrats: While Rory Reid trails Brian Sandoval 50% to 34%, he leads the governor 47% to 36%.

The last reason Nevada Democrats should not let Harry Reid’s unpopularity and Rory Reid’s probable presence at the top of their ticket lead them to despair is that they are in a good position to keep the state legislation, which they fully control for the first time in two decades. While Democrats have a 28-14 edge in the state Assembly, their majority in the state Senate is a far narrower 12-9. While you would expect this to mean the GOP would have a good opportunity to take over the upper chamber, only 5 Democratic seats are in play, which gives Republicans little room to maneuver to pick-up the two districts they’ll need.

While Democratic state Senator Joyce Woodhouse appears to be the cycle’s most endangered incumbent, because the district she represents (Henderson) is divided as closely as it gets between the two parties. If Election Night is rough for Democrats, Woodhouse could very well lose, but the GOP’s second best opportunity is an open seat in a district in which Democrats outnumber Republicans 2:1. That the GOP’s rationale for why they think this race is vulnerable is that Democrats’ (June) primary is pitting two Assemblymen against other suggests Republicans can’t expect to regain any power in the legislature before at least 2012.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: GOP dominates IN and IA, has fighting chance in VT and CA

Given how much of this week’s has had us talking about Indiana, it is no surprise that its most noteworthy poll also comes from the Hoosier State: Rasmussen tested the Senate race sans Bayh - and the results are atrocious for Democrats. Reps. Brad Ellsworth and Baron Hill would be crushed by whichever Republican they are up against: Dan Coats leads them 46-32 and 48-32, John Hostettler is up 49-31 and 46-27 and even Marlin Stutzman has decisive leads, 41-33 and 40-30. If these numbers are confirmed by other pollsters, Indiana would no doubt move towards North Dakota.

Yet, it is in not certain that other pollsters will find similar results, as we already know that Rasmussen’s number are in flagrant contradiction with Research 2000 released last week. While R2000 did not test other Democrats but Bayh, it did find Coats with a 38/33 favorability rating; Rasmussen has it at 54/27. (I’ll pass on the other weird internal of Rasmussen’s poll: How can a first-term state Senator [Stutzman] have the same name recognition as a congressman?) Given that Research 2000 had found Bayh in a far stronger position when matched-up against Hostettler than Rasmussen had found last month, it’s probably safe to say their numbers would have found Ellsworth and Hill in a far more competitive position than this Rasmussen poll does.

Does this mean we should trash Rasmussen and cherry-pick Research 2000’s survey? Of course not! But we shouldn’t do the inverse either. At the moment, only two polling outlets have tested Indiana’s Senate race and both have released surveys with no glaring problem that paint a very different landscape. (Of course, this has happened in other states, most notably in Colorado where Rasmussen and R2000 have a very different take on Michael Bennet’s electability.) We will need more polling evidence to figure out what to make of all of this, and it’s too early in the cycle to decide what’s an outlier and what’s not.

Senate

Wisconsin: To my knowledge, Rasmussen and PPP are the only pollsters to have recently tested Tommy Thompson’s prospects and their results are so at odds that it is a shame no other firm is releasing a Wisconsin poll. After all, the main reason Rasmussen’s finding that Thompson would start as the front-runner has become conventional wisdom is that they are releasing a survey of the state every few weeks, and indeed a new Rasmussen poll conducted this week finds that Senator Russ Feingold trailing Thompson 48% to 43%. Feingold’s favorability rating is a mediocre 50/48 while Thompson’s is an impressive 63/34, which is the main difference with PPP since that pollster found the former Governor rather unpopular. In any case, Thompson is not running as of now and Feingold leads two low-profile Republicans - albeit by underwhelming margins: 47% t o 37% against Westlake, 47% to 39% against Terrence Wall.

North Carolina: No surprise in PPP’s monthly look at Senator Richard Burr (yet another race that is pretty much tested by only one firm). As always, he has a comfortable lead against his rivals; as always, he is very far from the 50% threshold and his approval rating is mediocre (35/35). Against Elaine Marshall, he leads 43% to 33%; against Cal Cunningham, 44% to 32%; against Kenneth Lewis, 44% to 31%. That said, those numbers are clear improvement over the December and January numbers, since Burr only led Marshall by 5% and 7%. Another bad sign for Democrats: For the first time in January, Marshall performed better than a generic Democrat, a potential sign that her campaign was catching on, but she has once again fallen behind. PPP also tested the Democratic primary, finding Elaine Marshall ahead but certainly not by enough to look like a safe bet: She has 29% versus 12% for Cal Cunningham, 5% for Kenneth Lewis and 2% for new candidate Marcus Williams, who I had not heard of before this poll.

Illinois: Internal polls are only good insofar as the other camp chooses not to release a contradictory survey so it looks like the two parties have fought themselves to a draw in Illinois. Two weeks after Mark Kirk publicized an internal poll finding him leading Alexi Giannoulias, it is now the Democrat’s turn to release a Greenberg Quinlan Rosner survey that has him up 49% to 45%. Combine that with PPP and Rasmussen’s contrasting results (the former has Giannoulias up 9%, the latter Kirk up 6%), and thi is one race whose polls are all over the map.

Iowa: Democrats have never thought of Iowa as a strong opportunity, but given the number of their incumbents who are struggling to lead unknown Republicans it must be jarring to see Senator Chuck Grassley with 56% to 35% lead in a new KCCI-TV poll. Combine that with Grassley’s strong approval rating, and it certainly doesn’t look like there is anything to see in this Senate race.

Oregon: Rasmussen has released the first poll I am aware of that tests Senator Ron Wyden, and Democrats can be relieved that there isn’t yet another bad surprise. Wyden’s approval rating stands at 55-36, making it hard to see how the GOP can find an opening to defeat him. However, even he fails to crack the 50% threshold when matched-up against his largely unknown opponent, Jim Huffman, though his 49% to 35% lead is nothing for Democrats to get panicked by. Also today, SUSA found Wyden’s approval rating to be a respectable 50/37, which is a better spread than Jeff Merkley’s and Barack Obama’s.

Washington: While two surveys find Wyden with a strong approval rating, Patty Murray might not be holding on as well - at least according to SUSA. The senator’s approval rating has collapsed to 43% to 50%, by far the lowest SUSA has ever found Murray in 5 years of polling. So is this poll an outlier or does it serve as more evidence that the GOP can put Washington in play if it recruits a strong candidate?

Governor

Vermont: While this open race has looked like one of Democrats’ top opportunities of the cycle, Republican Lieutenant Governor would more than hold his own against a series of Democratic candidates according to Research 2000: He trails Secretary of State Deb Markowitz within the margin of error (43-41), leads state Senator Doug Racine 43% to 38% (also barely within the MoE) and has decisive leads ranging from 10% to 18% against lower-profile Democrats (Peter Shumlin, Matt Dunne and Bartlett). A major caveat: No more than 11% of Republican respondents say they are undecided in any of these match-ups, between 25% and 36% of Democrats say the same. When we account for that, Markowitz does start as the front-runner and the other Democrats have a lot of room to grow.

Iowa: Governor Chet Culver trails his chief Republican challenger Terry Branstad 53% to 33% in the latest Des Moines Register poll and 54% to 38% in a new Research 2000 poll conducted for KCCI-TV. Six months ago, those numbers would have been jaw-dropping; now they’ve come to be expected. The former Governor’s entry in the race has made Culver look like one of the surest gubernatorial losers of the year. The one thing that could save him would be for Branstad to be upset in the GOP primary since Culver is far more competitive against 3 other Republicans (in the DMR poll, he trails Vander Plaats by 3% while leading state Rep. Roberts by 5%; in R2000, he leads Vander Plaats by 3% and crushes Roberts by a surprising 22%). While he reaches 48% in Research 2000’s most favorable match-up, he doesn’t break 41% against any rival in the DMR survey. Combined with his dismal approval rating (36-53), this makes it hard to see how he could survive.

California: For a year now, Rasmussen has found tougher results for California Democrats than PPIC and the Field Poll, and its latest round of gubernatorial numbers are no different since Meg Whitman forces a 43%-43% tie against probable Democratic nominee Jerry Brown. Brown does have a wide 46%-34% lead against Steve Poizner, however. What should be comforting to Democrats is that this comes from Whitman’s remarkable popularity (56-28) rather than because Jerry Brown is unpopular (his favorability rating is a decent 53-41) or because the electorate has soured on Democrats (Obama’s approval rating is a solid 57-42). As long as Democrats don’t fall asleep as they did in Massachusetts, their attacks combined with Poizner’s should at least be able to increase Whitman’s negatives.

Interestingly, Arnold Schwarzenegger’s approval rating is a disastrous 26% to 73% in this Rasmussen poll and 19/80 in a newly-released SUSA poll. Republicans sure are lucky he is term-limited.

Nevada: The latest numbers of this Governor’s race are more encouraging than usual for Democrat Rory Reid, as Brian Sandoval’s lead is not as overwhelming as usual (44% to 35%) but then again it is a survey conducted by a Democratic firm, Grove Insight. The poll also confirms  just how much Democrats stand to benefit if Governor Jim Gibbons somehow manages to survive the GOP primary; weighed down by a catastrophic approval rating (20-75!), Gibbons would be crushed by Reid 49% to 33%. The survey also finds that Rory’s father Harry Reid is in bad shape, however: His approval rating stands at a dismal 34-63.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Weekly update: NM’s filing deadline passes, state Senator takes on Murray, Krolicki won’t run

The past week was dominated by an avalanche of open seats, most of which concern congressmen who were not expected to retire. Diane Watson, Patrick Kennedy, Lincoln Diaz-Balart and Vern Ehlers announced they would not seek re-election and Marco Diaz-Balart made a move for his brother’s district that opened up his own seat. Meanwhile, Jack Murtha’s death will lead to a special election that will probably be held in early May.

A fifth state saw its filing deadline pass this week: New Mexico. The main attraction is the open Governor’s race, in which there were no last minute surprises. On the Democratic side, actor Val Kilmer and state Senate Majority Michael Sanchez let the filing deadline pass without making a move, leaving Lieutenant Governor Diane Denish in control. On the Republican side, no one joined state Rep. Janice Arnold-Jones, Dona Ana County DA Susana Martinez and Pete Domenici Jr. Over on House races, all three Democratic representatives are seeking re-election, with Rep. Harry Teague (NM-02) the most endangered since Steve Pearce is seeking his old seat back. In NM-01, Rep. Martin Heinrich’s probable opponent is Jon Barela, a former vice chairman of the state GOP who will need the environment to be truly dismal for Democrats to pull off an upset.

In Washington, Republicans have yet to convince Rob McKenna, Rob Reichert or Dino Rossi to challenge Senator Patty Murray but they did get a credible candidate in the race this week: Don Benton, who has served in the state Senate since 1996. While Benton is only 52, he seems to have had a higher profile ten years ago: In 1998, he mounted a challenge to Rep. Brian Baird (who is retiring this year) and in 2000 he became chairman of the state Republican Party, though a rocky tenure led to his ouster within 8 months; also, he seems determined to emphasize conservative themes and embrace the Tea Party label, which should prove risky in a state that has trended increasingly Democratic over the entire decade (i.e. not just in 2008).

Yet, Benton’s entry is significant as it once again demonstrates the GOP’s rising confidence. In normal circumstances, Murray would likely crush Benton but if the electorate grows even more hostile to Democrats than it has for now, even a relatively low-profile state legislator can upset a seemingly solid incumbent. (While it seems hard to compare Elizabeth Dole and Patty Murray, Dole would have far tougher for Hagan to beat in most other cycles.) There is for now little reason for the DSCC to be alarmed, but the NRSC does have an eye on this state and Benton could still make life difficult for the incumbent.

In Nevada, we are getting a clearer picture of what the GOP’s Senate primary will look like. After seeing his prospects crushed by an indictment, Lieutenant Governor Brian Krolicki found himself back in contention when the charges were dropped; but he announced this week he would not jump in. On the one hand, the months of bad publicity due to his indictement surely damaged his standing (Rasmussen recently found him running weakest); on the other, he was a rare Republican with an imposing profile. The GOP field now contains at least 5 candidates with a credible shot at the nomination (Lowden, Tarkanian, Amodei, Angle, Chachas), which makes the primary wildly unpredictable; that’s always a dangerous place for a party to be, as we saw recently in Illinois’s gubernatorial primary.

A twist: A “Tea Party” group has qualified as a official party in Nevada, which will allow them to field a candidate on the November ballot; that candidate will likely be a man named Jon Ashjian. While Democrats will hope this takes some conservative votes away from the GOP, there is no evidence this will have any importance on the general election, but it still merits mentioning.

In Connecticut, week after week the gubernatorial field looks to be in as much flux. On the Republican side, Danbury Mayor Mark Boughton had joined the race last week and this week, it was Newington Mayor Jeffrey Wright’s turn. I see that I had missed Chester First Selectman Tom Marsh’s entry in the race, so we now have at least five Republicans in the race. On the Democratic side, former Speaker James Amann’s decision to drop out appeared to open the way to a clearer opposition between Dan Malloy and Ned Lamont, but then we learned that Waterbury Mayor Michael Jarjura is preparing to jump in. The state’s fifth biggest city, Waterbury has about 110,000 inhabitants; Jarjura could certainly be a major player in the primary.

As always, I list all the changes I have logged in during the week to the retirement and race-by-race pages. First, updates to Retirement Watch:

New open seats Debra Watson (D, CA-33)
Lincoln Diaz-Balart (FL-21)
Mario Diaz-Balart (FL-25): will run for FL-21, leave FL-25 open
Vern Ehlers (R, MI-02)
Patrick Kennedy (D, RI-01)
Jack Murtha (D, PA-12)
Will not retire No one
Added to retirement watch No one

Next, the recruitment page:

NV-Sen, GOP Lieutenant Governor Brian Krolicki will not run
retired Navy commander Kirk Lippold will run
NY-Sen, GOP/indie Daily News publisher Mort Zuckerman added
OR-Sen, GOP Kareem Hamdy is running
SC-Sen, Dem attorney Chad McGowan dropped out
WA-Sen, GOP state Sen. Don Benton announced run
Chris Widener is running
chiropractor Sean Salazar is running
enery trader Craig Williams is running
physician Arthur Coday Jr. is running
Rod Rieger is running

Third, updates to gubernatorial races:

CT-Gov, Dem former Speaker Jim Amann dropped out
Waterbury Mayor Michael J. Jarjura announced run
CT-Gov, GOP Chester First Selectman Tom Marsh is running
Newington Mayor Jeffrey Wright announced run
MI-Gov, Dem Lansing Mayor Virg Bernero is running
former Treasurer Bob Bowman is running
UM regent Denise Ilitch will not run
NM-Gov, Dem state Senator Michael S. Sanchez will not run
PA-Gov, Dem state Senator Anthony Williams added

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Senate GOP leads in AR, NH, NV, CO, KY, IL but Reid enjoys uptick & Ayotte struggles in primary

The week’s most dramatic polls no doubt are those from Arkansas since they suggest that Blanche Lincoln’s fate is all but sealed. Rasmussen finds the senator’s favorability rating at a dismal 36-59; PPP shows her approval rating at an even more catastrophic 27-62. Her numbers against Republicans are a disaster. PPP has her down 56% to 33% against Rep. John Boozman and 50% to 35% against Gilbert Baker; Rasmussen shows her trailing by similar margins - 54% to 35% against Boozman, 52-33 against Baker, 50-34 against Curtis Coleman, 51-35 against Kim Hendren. Those are not numbers an incumbent recovers from.

The problem for Democrats is that they can hardly pull a Dodd or a Torricelli: PPP tested a variety of alternatives to Lincoln and found the GOP generally in control. The party’s only savior could be popular Governor Mike Beebe - and even then he is down 1% against Boozman and he leads Baker by an underwhelming 46% to 38%. Rep. Mike Ross trails Boozman 48-37 but ties Baker at 39%; Wesley Clark is down 51-36 and 45-39, respectively and Halter 53-30 and 45-34.

While none of these results are encouraging for Democrats, all four of her potential replacements perform better than the senator. Since Halter, Ross and Clark’s name recognition is lower and favorability ratings is incomparably stronger than Lincoln, they would also have more hope of improving their results while it is hard to envision the incumbent doing so. In short, the GOP is more likely than not to pick-up this seat but it does not mean Democrats should not at least try a switcheroo.

Senate: GOP also leads in NH, NV, CO, KY and IL…

New Hampshire: The first public poll of the GOP’s Senate primary finds that Attorney General Kelly Ayotte has her work cut out for her: Research 2000 has her only leading Ovide Lamontagne 36% to 27%, with William Binnie at 4%. If conservatives decide they can add New Hampshire to an already long list of summer primaries they want to prioritize, Lamontagne could very well pull the upset and thus give Democrats a boost in the general election. While Rep. Paul Hodes trails Ayotte 46% to 39%, leads Lamontagne 46% to 36% - a 17% differential. The bad news for Democrats, of course, is that Ayotte remains the front-runner and her high favorability ratings and early poll lead presage good things for the NRSC.

Nevada: Harry Reid arguably just received the best poll he has seen in months - and it came from Rasmussen! While his numbers remain very rough, they are for once not insurmountable: His favorability rating stands at 44/55 and he trails all of his competitors “only” by single-digits: 45-39 against Lowden, 47-39 against Tarkanian and 44-40 against Angle. Of course, an incumbent has nothing to boast about when stuck around 40%, but last month Reid trailed by double-digits in all match-ups. We’ll have to see whether this trendline is an outlier or whether it is due to Reid’s well-financed attempts to improve his image. The poll’s most interesting part is the match-up between Reid and Lieutenant Governor Brian Krolicki, who has been mulling the race ever since he was cleared of an indictement: Krolicki has the smallest lead among these four Republicans, 44% to 41%.

Colorado: No miracle for Michael Bennet in Rasmussen’s new poll: the unelected senator leads trails Republican front-runner Jane Norton by a massive 51% to 37%. That said, Bennet’s favorability rating remains (barely) positive and he should have an easier time to improve his numbers than other incumbents since he is less well-known and thus has more room to grow. And yet, his primary challenger Andrew Romanoff performs far better against Norton since he only trails 45% to 38% - a sign Democrats would be better off dumping the incumbent to start fresh? Both Democrats trail by more narrowly against Republicans Tom Wiens and Ken Buck.

Kentucky: Rasmussen’s monthly Kentucky poll confirms not only that the GOP has gained edge in this open seat (a red state’s electorate naturally gravitates rightward in this environment), but also that Rand Paul would be a far more formidable candidate than had been expected: He leads LG Mongiardo 48% to 37% and AG Conway 47% to 39%. Tray Grayson’s leads are more uneven, as his 49-35 rout over Mongiardo contrasts with his 44-40 lead over Conway. Democrats look like they’d be better off with Conway, whose favorability rating stands at 47-32, than with Mongiardo, whose favorability rating is a mediocre 45-43.

Illinois: Conducted by Rasmussen, The first public poll to test the Illinois Senate race since voters chose their nominees finds Mark Kirk leading Alexi Giannoulias 46% to 40%, a result that contradicts PPP’s recent finding that the Democrat has an 8% lead; note that PPP’s poll was conducted just before Giannoulias was hit by new questions over his family bank, so that might account for some of the difference. In any case, Illinois is one state the DSCC simply cannot afford to lose so Kirk’s early lead is an ugly one for Democrats to see.

Connecticut: Even Rasmussen agrees there is nothing to see in this race since Chris Dodd’s retirement. Thanks to a massive 70% to 26% favorability rating, Richard Blumenthal crushes Rob Simmons 54% to 35% and Linda McMahon 56% to 36%.

New York: I already reported Marist’s Senate survey earlier this week, and Quinnipiac’s poll draws the same lessons: Gillibrand starts with an edge in the Democratic primary but Harold Ford certainly has an opening (Gillibrand is up 36-18 with Tasini at 4) and the incumbent would be favored in the general election against Bruce Blakeman; however, she does not pass 50% in this survey (she leads 44% to 27%), a potential sign Blakeman could still gain traction as he introduces himself.

Arizona: John McCain and John Hayworth both released internal polls of what is shaping up to be a rough primary. As you would expect, the two camps’ numbers tell a different story. Hayworth’s survey (conducted by McLaughlin) has the incumbent leading 49% to 33% while McCain’s survey (conducted by POS) has him up 59% to 30%. Given that there is still a long time to go, that McCain is after all the GOP’s former presidential nominee and that he is better known than Hayworth, the latter set of numbers is also quite underwhelming and signals that the challenger has an opening.

Governor: White within single-digits of Perry, Michigan’s Cox leads

Texas: Since Bill White’s entry in the race, Democrats have been paying more attention to this gubernatorial race but Rasmussen is the first pollster to find a real opening for the Houston Mayor: When matched-up with Governor Rick Perry, he trails 48% to 39% - a sign of vulnerability for the incumbent since he is only up single-digits and remains under 50%. Against Kay Bailey Hutchison, White trails by a larger 49% to 36%. As such, whether the general election will be competitive depends from the outcome of the March-April primary; there is no little doubt White would rather face an incumbent with a mediocre 50-48 approval rating.

New York: David Paterson still looks to be heading towards certain defeat in Marist and Quinnipiac’s new polls. His approval rating stands at 26% in the former and 37% in the latter; that might be an improvement over his low points of 2009, but it leaves him in no position to be competitive against the ultra-popular Andrew Cuomo. Marist shows the Attorney General would crush the Governor by a stunning 70% to 23% in the primary, while Quinnipiac shows the margin to be a comparatively modest 55% to 23%. Both surveys have Paterson struggling against Rick Lazio (he trails by 3% in Marist, leads by 1% in Quinnipiac), while Cuomo crushes the former congressman by 37% and 32%.

Michigan: While some cheered Lieutenant Governor John Cherry’s early January withdrawal as an opportunity to field a stronger candidate, EPIC-MRA’s latest poll finds state Democrats are hardly saved: Attorney General Mike Cox crushes the three Democrats he is matched-up against by margins ranging from 17% to 22%. Yet, Cox is not certain of surviving the primary, since he leads 32% to 25% against Rep. Pete Hoekstra, who does not fare quite as well in the general election: He leads by 17% against Virg Bernero but only by 8% against Andy Dillon and by 7% against Denise Ilitch. The other good news for Democrats is that former GOP Rep. Schwarz is now saying he is 75% certain of running as an independent, which could lead Republicans to snatch defeat from the jaws of victory.

Connecticut: Democrats don’t have as clear an edge in this Governor’s race since Susan Bysiewicz dropped out, though they still lead all match-ups in Rasmussen’s new poll: Ned Lamont is up 41-33 against Lieutenant Governor Michael Fedele and 40-37 against Tom Foley while while Stamford Mayor Dan Malloy tops the two Republicans by just 1%.

New Hampshire: Governor Lynch is one incumbent Democrats will apparently not have to worry about. In Research 2000’s new poll, he crushes low-profile businessman Kimball 59% to 13%.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Poll watch: Rubio edges ahead for the first time, Castle and McCollum grab decisive leads

For the first time, Marco Rubio leads Charlie Crist in Florida’s Republican primary - and it’s not even a Rasmussen poll! He has a 47% to 44% over the Governor in Quinnipiac’s latest poll of the race.

The surprise isn’t necessarily that Rubio has edged ahead (while Crist looked truly formidable when he jumped in the Senate race in May, the primary always looked like it could get very tricky) but that he has done so effortlessly. In June, Crist had a 54% to 23% lead, which he maintained in August; by October, his margin was cut by half (50-35) and Rubio gained another 20% since the fall. There are still 9 months to go before the election, Rubio has yet to air any ad or deploy the heavy artillery but Crist has already collapsed! What will it be once the former Speaker has spent his money introducing himself to all voters? After all, 42% of Republican respondents say they do not know him well, versus only 6% who say the same of Crist.

This is not simply due to conservatives turning against Crist, far from it. Like so many of his colleagues, the Governor has seen his approval rating melt during the economic crisis. Back in June, it stood at 62-28; now, at 50-38. What this means is that Democrats might be better off facing Charlie Crist in the general election - something I frankly never thought I would say.

For now, both Republicans have a commanding lead over Rep. Kendrick Meek: Crist is up 48% to 36%, Rubio is up 44% to 35%. But this does not mean Democrats should give up on this race. For one, 72% of respondents say they know little about Meek, which makes his name recognition far weaker than either of his opponents’. As importantly, what might these numbers look like after Crist and Rubio have spent their millions (both are very prolific fundraisers) blasting each other throughout the summer? (The primary won’t be held before August 24th.) Their favorability rating should be far lower, while Meek is also a well-financed candidate who might have been able to use that time to air unchallenged positive ads.

Meanwhile, in other Senate polls…

Delaware: No Beau Biden, no Ted Kaufmann, no Matt Denn, no John Carney - the highest-profile candidate Democrats can hope for at this point is Newcastle County Executive Chris Coons. Always eager to crush Democrats’ spirits, Rasmussen wasted no time before coming out with a poll pitting Coons to Rep. Mike Castle and the results are rather brutal for the defending party: Castle leads by a massive 56% to 27%! Research 2000’s October survey had Castle up 51% to 39% over Coons, which is 17% more optimistic for Democrats, so we’ll say what other surveys have to say, but there’s no question that Republicans have now become very likely to pick-up this seat. Most stunning is the 31% of Democrats who say they are voting for Castle; sure, that means Coons has some room to grow, but if these respondents are willing to support the Republican outright rather than say they are undecided, it says much more about the congressman’s popularity than Coons’s lack of name recognition.

Nevada: No surprises in Research 2000’s latest Nevada poll: Harry Reid is still in a terrible position. Weighed down by a 34-55 favorability rating, he trails his opponents by brutal margins: 52-41 against Danny Tarkanian and 51-42 against Sue Lowden. Research 2000 tested potential replacements and found that Nevada Democrats cannot hope to pull a Dodd: Rep. Berkley trails 46-40 and 45-40 and Secretary of State Rose Miller is down 44-36 and 43-37. That such well-known Democrats are polling this weakly against such low-profile Republicans suggests NV is very determined to vote Republican in November. One candidate who manages small leads is Las Vegas Mayor Oscar Goodman, but he just announced he wouldn’t seek statewide office - not that Democrats had much reason to rest their hopes on him, since he is over 70!

New York: The third poll to test Harold Ford Jr.’s primary prospects is also the one to found him closest: Research 2000 shows Kirsten Gillibrand leading 41% to 27%, with 3% for Jonathan Tasini. Ford is surprisingly well-known among New York Democrats (his favorability rating is 40-13), while Gillibrand has more than avoided David Paterson’s fate (her rating is 46-26). Whatever Ford’s baggage, there is no denying that he still has plenty of room to grow and this will be a real race if he jumps in but that has more to do with Gillibrand’s vulnerability than anything else - remember that she’s been in trouble in primary polls no matter who she’s been matched-up against, and she did trail repeatedly against Carolyn Maloney over the summer.

Meanwhile, in other gubernatorial polls…

Florida: If Alex Sink and Bill McCollum were within the margin of error throughout 2009, how long could that have lasted in the current environment? While the conventional wisdom has been that McCollum comes with electability issues, the bottom line is that we are talking about an open seat race between two credible candidates in a swing states, a situation which in 2010 is bound to favor the GOP. Indeed, the new Quinnipiac poll finds McCollum grabbing a decisive 51% to 41% lead, up from the 4% edge he held in October; at this point, it goes beyond name recognition, though Sink should at least be able to somewhat get closer once she reduces the notoriety gap. One good news for Sink in the poll: 22% of Democrats say they are undecided, but only 11% of Republicans.

Illinois: Attacked from all corners and seeing his primary fortunes sink, Governor Pat Quinn is also in a bad position in the general election according to a new PPP poll. He trails former AG Jim Ryan 42% to 35% and trails former state party chair Andy McKenna 42% to 36%; Dan Hynes, however, leads both Republicans (40-35 against Ryan, 38-36 against McKenna). This is quite a decisive

Arizona: This has been one of Democrats’ top opportunities of the cycle because of Governor Jan Brewer’s unpopularity, but a new Rasmussen poll shows that the GOP is in a position to nominate someone who can perform much better: Treasurer Dean Martin has a 31% to 29% edge over Brewer, with John Munger at 7% and Vernon Parker at 5% (Parker has dropped out). The swap would be helpful to Republicans: Not only does Brewer have a dismal approval rating (37-60) but she trails Democratic front-runner Goddard 43% to 41% whereas Martin leads 44% to 35%. That’s a turnaround from Rasmussen’s last 2009 poll, in which Goddard had a lead against Martin. The shifting landscape is affecting Democratic candidates everywhere.

Ohio: The University of Cincinnati found yet more confirmation that the once mighty Ted Strickland is facing a very tough re-election race: he trails former Rep. John Kasich 51% to 45%. Interestingly, his rating is positive - 50% to 45% - so voters looking for a change are not necessarily doing so because they disapprove of the governor’s performance. This is further supported by the survey asking who respondents blame for the economic crisis. 24% say Bush, 23% say Wall Street and 19% say Congress; only 13% say Obama and 3% say Strickland. Yet, it’s Democrats who are preparing to lose a lot of seats.

Utah: Last week, a Deseret News poll found Salt Lake County Mayor Peter Corroon was holding Governor Herbert under 50%, but Mason Dixon shows Herbert in a stronger position, crushing Corroon 55% to 30%. While Coroon is popular (his approval rating is 47-17), Herbert is showing no sign of vulnerability, with 62% of respondents approving of his job.

New York: No miracle for David Paterson in Research 2000. His favorability rating stands at 34-54 (and yes, that’s just among Democrats) while Andrew Cuomo’s is a formidable 71-15. The trial heat results would be stunning if we hadn’t already seen it dozens of times: Cuomo crushes Paterson 63% to 19%. I’m still at a loss as to how the governor hopes to win the Democratic nod.

Republican Internal polls

NH-Sen: Conservatives have failed to derail Mark Kirk’s candidacy, but we have gotten no look at the primary situation in New Hampshire, where Kelly Ayotte’s situation has seemed a bit more precarious than Kirk’s. (Of course, Democrats would love nothing more than to see the A.G. crash out.) Ayotte sought to remedy the situation by releasing an internal poll that has her dominating the GOP field: Ayotte has 43%, Ovide Lamontagne 11%, Bill Binnie 5% and Jim Bender 3%. Last spring, Lamontagne’s allies claimed he remained well-known among state Republicans so a 32% margin is disappointing but there is a very long way to go until the September primary; given the name recognition gap, Lamontagne has room to grow - not to mention that this is an internal poll.

PA-15: Rep. Charlie Dent is one of the few Republican incumbents who are considered vulnerable at this point, which must not be an enjoyable position. The congressman’s camp sought to counter that perception by releasing an internal poll showing him with a dominant lead over Bethlehem Mayor John Callahan. Conducted by The Tarrance Group, the survey has him leading by a massive 56% to 27%. Take the results with a big grain of salt (it’s an internal, and the polling memo doesn’t even include exact wording questions) but the numbers are obviously tough for Democrats; it would be nice to see a public survey from this district.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

An epic polling roundup to get our minds off Massachussetts

Research 2000 and ARG just released two of Massachussetts’s final polls - if not the final polls. ARG found a 7% lead for Brown (52% to 45%), up 4% from where he was just last week. Research 2000, meanwhile, found… a tie: Scott Brown and Martha Coakley receive 48% apiece, a testament to how unpredictable the contest remains heading into Election Day. While at this point any poll that doesn’t have Brown ahead is a relief for Democrats, I don’t have to tell you that even that survey is rough for Coakley: Just last week, Research 2000 found her ahead by 8%, which makes this yet another poll to found stunning momentum for the Republican.

Yet, Research 2000 also confirms the hypothesis I enunciated this morning, as an update to last night’s post: Coakley performs better in polls that include Libertarian nominee Joe Kennedy, who will be on the ballot tomorrow. Pajamas Media and PPP, which gave Brown large leads yesterday, did not include Kennedy at all; surveys that have the race within the margin of error do include Kennedy, who for instance receives 3% in Research 2000. There’s every reason to believe that Kennedy is drawing his voters from the conservative camp, so if the race is close his presence on the ballot could allow Coakley to shave off a few points off Brown compared to PPP’s survey. (ARG’s website appears to be down, so I cannot determine whether they included him.)

It’s hard to think of anything but Massachussetts, but let’s try to do just that: Over the past week, there was so much news to cover that I ignored an avalanche of polls, to which I’ll now get to. Now that we’ve entered 2010, there will be more and more surveys released weekly - even daily - so I will obviously not attempt to cover each one in as much detail as I did over the past year; I will however start with polls that are testing election we’ve seen little data on. Today, those consist in 3 House districts and 2 Western Governor’s races.

(Yes, this is a fairly long post… but I let polls accumulate without covering them for more than a week, so I wanted to get to them all at once to make sure I can focus on Massachussetts and other important news after this!)

Three House races find mixed results for Dems

NC-08: PPP managed to find a freshman Democrat from a swing district with solid standing! In NC-08, a district that swung from Bush to Obama, not only does Rep. Larry Kissell have a strong approval rating (45% to 30%), but he displays no sign of vulnerability in three match-ups against his challengers, leading Lou Huddleston 55% to 37%, Tom D’Annunzio 54% to 38%, Hal Jordan 55% to 39% and Harold Johnson 53% to 39%. Sure, none of these Republicans have much name recognition, but consider all the polls we have seen recently in which incumbent Democrats have struggled to mount any sort of lead against unknown opponents. Yet, not only is Kissell up big but he’s also topping 50%.

ND-AL: The DCCC is relieved Rep. Earl Pomeroy decided to seek re-election, but it doesn’t mean he is a shoo-in to win another term. A new poll by Research 2000 finds him solidly ahead of all of his competitors Kevin Cramer and Duane Sand, but he fails to clear 50% against either. (He’s ahead 46-24 and 47-22, respectively.) This is all the more problematic when you consider that Republicans are 5 times more likely to be undecided than Democrats, so the GOP candidates have a lot of room to grow once they introduce themselves, and the NRCC especially has hope in Cramer (North Dakota Public Service Commissioner). In short: Pomeroy has a good standing and he is clearly favored to win re-election, but he is not safe.

OH-01: If Kissell and Pomeroy look strong, Rep. Steve Driehaus is sinking according to a SUSA poll commissioned by FiredogLake. We already knew that this freshman Democrat was one of the most endangered of the cycle (he is facing a rematch against the Republican he ousted in 2008, and OH-01 is a district with a substantial African-American population, so a drop in black turnout compared to the past cycle would be particularly hurtful to his chances), but SUSA’s numbers are uglier than even optimistic Republicans surely expected: Driehaus trails 39% to 56% for former Rep. Steve Chabot. I don’t need to tell you the odds that an incumbent who trails by 17% might win re-election. (Coincidentally, this is the same exact margin SUSA found against Rep. Vic Snyder on Friday.)

An unexpected Dem opportunity in UT, door is closing in OK

Utah: Democrats were excited at Salt Lake County Mayor Peter Coroon’s decision to challenge Governor Herbert, and a Deseret News poll confirms that Coroon could make the race well-worth watching: Herbert leads 48% to 35%, down from his 56-32 lead back in November. There’s no question that Herbert is heavily favored, but Coroon does represent one third of the state’s population in a capacity that ensures he is a visible presence. At the very least, Coroon’s presence on the ballot could help Democrats ensure that Rep. Jim Matheson isn’t a victim of any potential red wave.

Oklahoma: Whatever Oklahoma’s staunchly conservative status, Democrats had enough of a bench they were expecting to mount a highly competitive bid to defend the state’s governorship. (Governor Henry is term-limited.) Yet, a Tulsa News poll finds that Lieut. Gov. Jari Askins and Attorney General Drew Edmonson are no match for Rep. Mary Fallin; despite their strong favorability rating (Edmonson’s stands at 51-31), they trail the Republican 52% to 36% and 51% to 39%, respectively. A former Lieutenant Governor, Fallin is well-known and popular (54% to 29%). Democrats shouldn’t entirely give up, but the race most certainly leans Republican.

Connecticut and North Dakota won’t be competitive

From the moment Senators Byron Dorgan and Chris Dodd retired two weeks ago, we have known that the races to replace them are unlikely to be competitive. Three new poll confirm that John Hoeven and Richard Blumenthal are very heavily favored to be sworn into the Senate come January 2011.

North Dakota: Richard 2000 finds Hoeven leading 56% to 32% against Ed Schulz, 55% to 34% against former AG Heidi Heitkamp and 56% to 32% against Jasper Schneider. Sure, Hoeven’s lead doesn’t quite reach “overwhelming” status, but looking at the internals it’s hard to see a path to victory for whoever Democrats nominate: There are few undecideds, including among Democratic voters; Hoeven enjoys near unanimous support among Republicans; and he has daunting leads among independents.

Connecticut: We’ve already seen a few surveys displaying Blumenthal’s dominance, but over the past 5 days Quinnipiac and Research 2000 both released surveys confirming it. In Research 2000, Blumenthal leads Rob Simmons 54% to 35%, Linda McMahon 56% to 34% and Peter Schiff 56% to 33%. In Quinnipiac, whose brutal numbers for Dodd were as responsible for driving the narrative of his doom than those of any other pollster, his leads are gigantic: 62% to 27% against Simmons, 64% to 23% against McMahon, 66% to 19% against Schiff. Everything can happen if Democrats aren’t careful (see neighboring Massachussetts), but Blumenthal isn’t Martha Coakley.

CO, NH, NV, OH: 4 key Senate races, 7 rough polls for Senate Democrats.

Ohio: Democrats led this open race for much of 2009, but Rasmussen’s new poll is its second in a row to find Rob Portman has grabbed the edge. He leads Lieutenant Governor Lee Fisher 44% to 37% and Secretary of State Jennifer Brunner 43% to 40%. These numbers are very interesting because the Democratic establishment holds Fisher to be a stronger candidate; yet, Portman increased his lead against Fisher whilelosing ground against Brunner! Overall, then, the two parties are roughly where they were in early December.

Colorado: This week, we received three surveys testing Colorado, which until this week an underpolled state:

  • Rasmussen has by far the worst set of results for Democrats: Senator Michael Bennet trails former Lieut. Gov. 49% to 37%, and he’s also behind lower-profile Tom Wiens (44% to 38%) and Ken Buck (43% to 38%). Former Speaker Andrew Romanoff trails Norton and Wiens by the same margin but is only behind Buck by 1%.
  • In response to these ugly numbers, Bennet released an internal poll, which might have found better results but he is still behind Jane Norton, 43% to 40%.
  • Finally, just this afternoon Research 2000 released the best news Bennet has received in quite some time: Bennet leads Norton 40% to 39%, Buck 41% to 38% and Wiens 42% to 38%; Romanoff trails Norton by 2% but leads Buck and Wiens by 1% and 2%.

There is quite a lot of disparity between these three surveys, and Bennet’s camp will be delighted that he finally manages a lead in a poll - even if it’s well within the MoE. That said, it is clear from all of these surveys that Bennet is stuck at 40% - a dismal place for an incumbent to be, even an appointed one. Colorado remains a major problem for Democrats.

New Hampshire: Another tough Rasmussen poll, since it shows that what once looked like a Democratic-leaning open seat might now be leaning Republican: Attorney General Kelly Ayotte leads Rep. Paul Hodes 49% to 40%. (This is roughly the same margin Rasmussen found in September.) Hodes does led lower-profile Republicans Ovide Lamontagne and Bill Binnie 45% to 38% and 43% to 37%, respectively. This is

Nevada: With everyone now aware that Harry Reid is one of the Democrats’ most vulnerable senators, there’s been speculation that the party might try to convince him to pull a Chris Dodd, as in retire for the good of the party. But a new poll released last week revealed that Democrats don’t have a Blumenthal-like savior:

  • PPP found Harry Reid trailing Sue Lowden 51% to 41% and Danny Tarkanian 50% to 42% - very ugly margins for a longtime senator against second-tier challengers. Yet, the Republicans enjoy similar margins against other Democrats! Rep. Shelly Berkley trails by 8% against both; Rose Miller trails by 10% and 11%, respectively. Only Las Vegas Mayor Oscar Goodman manages to stay on an equal footing: he ties Tarkanian at 41%, leads Lowden 42% to 40%.
  • If PPP’s numbers were ugly, how can we describe Rasmussen’s? Here, Reid is crushed Lowden 48% to 36% and Tarkanian 50% to 36%! He manages to stay close to former Assemblywoman Sharron Angle, but even here he’s stuck at 40%, trailing 44% to 40%.

If polls showing other Democrats doing better than Reid started piling up, the party could hope to convince him to retire; but PPP’s survey cuts that hope short (Research 2000 will also soon release a similar poll), which allows Republicans to feel increasingly confident about picking-up Nevada.

OH, NV and MA: 3 key Governor’s races, three tough polls for Dems

Ohio: If Ted Strickland started 2009 as the clear favorite, he starts 2010 trailing former Rep. John Kasich. Rasmussen finds him trailing 47% to 40%, which is actually a 2% improvement over December’s numbers. Other surveys have found a closer race, but there’s no question that Strickland is in for a very tough battle.

Nevada: Rory Reid is in as much trouble as his father, only the position they’re vying for is different. Sure, Reid manages to lead incumbent Governor Jim Gibbons 43% to 36% in Mason Dixon’s poll, but considering that Gibbons is even more unpopular (his favorability rating is 18% to 53%) than David Paterson that doesn’t mean much; the favorite to win the Republican nomination, Brian Sandoval, crushes Reid 53% to 31%! In a three-way race involving Las Vegas Mayor Oscar Goodman, who is considering running as an independent, Sandoval and Goodman are close (35% to 33% for the former), with 20% for Reid. There’s no mystery as to why: Reid’s favorability rating is 25% to 35%, Goodman’s 43-15 and Sandoval’s 36-5. Hard to explain Reid’s numbers by anything but his last name.

Massachussetts: Two new polls confirm that Martha Coakley isn’t the only struggling Massachussetts Democrat:

  • PPP shows that Governor Deval Patrick has a dismal approval rating of just 22%. In three-way races involving Treasurer Tom Cahill (as an independent) and one of his 2 Republican opponents, Patrick is ahead but he receives less than 30% (!) and leads whoever is in second place by just 2% or 3%. In both match-ups, the 3 candidates are within 8%.
  • The Boston Globe poll is more favorable to Patrick: His favorability rating is a bad but not horrendous 39/50 and his leads over Cahill are a bit larger. If the GOP nominee is Charlie Baker, Patrick receives 30, Cahill 23% and Baker 19%; if the GOP nominee is Mihos, the numbers are 32, 23 and 19 for Mihos.

Much will depend on how Cahill positions his campaign. A former Democrat, he has been inching closer to the right since announcing he would run as an independent, for instance asking a conservative Republican state legislator to join his ticket.

Democrats’ silver lining is definitely Connecticut

Not only did Chris Dodd’s retirement all but guarantee Democrats will save Connecticut’s Senate seat, but Research 2000 shows they can look forward to in the Governor’s race - and also the 2012 Senate contest. Susan Bysiewicz, who just dropped out of the race last week, was in a very strong position: she led Lieutenant Governor Michael Fedele 52% to 33%, Tom Foley 51% to 35% and Mark Boughton 52% to 32%. But the Democrats left in the race look solid as well: Ned Lamont leads 46-36, 46-37 and 46-34 while Dan Malloney is up 44-35, 43-37 and 44-34, respectively.

Research 2000 also tested the 2012 Senate race. In a two-way general election match-up between Joe Lieberman and Chris Murphy, the representative leads the independent senator 45% to 26% - it’s quite stunning to see such a longtime senator fail to receive more than a quarter of the vote. Not only does Murphy crush Lieberman among Democrats (71% to 20%), but also among independents (41% to 22%). Democrats might fear a lot of losses in 2010, but at least Lieberman looks to have too low support to have much hope to win re-election in 2012.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Dems get still more ugly Senate numbers

The Boston Herald poll that was rumored to be coming today has not surfaced, which leaves us with no better idea of MA than this morning; while I did spend more time arguing that PPP should not be dismissed (this Blumenthal post is also worth reading), I agree with those who say the race is certainly Coakley’s to lose and that the poll’s release is one of the best thing that could have happened for her campaign. Unfortunately for Democrats, they have a lot more to worry about than Massachussetts since other polls released over the past few days find them in very tough spots in 3 key Senate races: AR, KY, NV. (These come on top of ARG’s NH poll, which I covered on Tuesday and which found Hodes trailing two Republicans outside of the MoE.) However, Democrats do get news from CT thanks to the combination of Dodd and Rell’s retirements and Lieberman’s unpopularity.

Nevada

Mason-Dixon paints quite an ugly picture for Harry Reid: He trails 50% to 40% against Sue Lowden, 49% to 41% against Danny Tarkanian and 45% to 40% against Sharron Angle. That latter result suggests Democrats can’t even root for Angle to win in the hope she’d be less electable, because there’s a good chance they would then find themselves with her as a senator. Here again, what’s striking is that none of the GOP nominees are particularly formidable or even high-profile, which makes their leads all the more telling of the huge trouble Reid is in. And as if those margins were not ugly enough, the Senate Majority Leader is plagued by a dismal 33% to 52% favorability rating. How can one envision winning re-election in such conditions?

This poll comes at a particularly troubled time for Reid, who is fielding a media firestorm since he admitted having told reporters during the 2008 campaign that Obama’s electability was helped by his light skin and his lack of a “Negro dialect.” The obvious parallel for Reid’s comments is Joe Biden’s 2007 remark on Obama, but the GOP is trying to tie them to the uproar that cost Trent Lott his leadership in 2002. I fail to see any similarity between Reid and Lott’s comments: The latter expressed regret that a segregationist candidate didn’t win the 1948 presidential election, i.e. he signaled support for racist policies, while the latter assessed the state of race relations. He used indefensible and insensitively anachronistic language, but that doesn’t change the fact that these two things have nothing in common. In any case, this episode will surely damage his standing in Nevada - and as the Mason-Dixon poll reveals he has no more room for any error.

Arkansas

Blanche Lincoln is sinking, according to Rasmussen’s latest poll. Make of his methodology what you will, but dismissing his samples as too skewed towards Republicans do nothing to diminish trendlines, which are also very worrisome for the senator. She trails 51% to 39% against Gilbert Baker (compared to 7% in December), 48% to 38% against both Curtis Coleman and Tom Cox (she trailed both by 4% in December), 47% to 39% against Kim Hendren. I don’t need to tell you how atrocious it is for an incumbent to be stuck under 40%, let alone when a challenger manages to cross 50%, let alone when opponents she is trailing by double-digits are low-profile and little-known. Ugly, ugly, ugly.

Kentucky

At least, Democrats have nothing to lose in KY as it is currently by the GOP; but that doesn’t mean they didn’t have high hopes for contesting it. According to Rasmussen’s latest survey, however, the two Republican candidates have for the first time grabbed healthy lead. Trey Grayson leads Jack Conway and Dan Mongiardo 45% to 35% and 44% to 37% respectively (in September, he was tied with the former and led the latter by the same margin); Rand Paul leads Conway 46% to 38% (he trailed by 4% in September) and crushes Mongiardo 49% to 35% (he led by 4% last month).

What’s most striking is that Paul is performing so well; it’s still hard to believe a general election featuring him could be as smooth for the GOP as one featuring Grayson, but there’s certainly little evidence at this point that the Texas congressman’s son would perform poorly against Democrats. The second striking fact is the very pronounced trendline, as the Republicans improve by more than 10% in three of the four match-ups. (I have a hard time believing that Rasmussen didn’t misreport its Grayson-Mongiardo numbers, which make little sense: Not only is is the only match-up to show no GOP improvement whatsoever, but it also has Mongiardo and Grayson performing better than their party rivals, something the other match-ups contradict.)

Connecticut

Thankfully for Democrats’ spirits, Rasmussen also released a poll confirming that Chris Dodd’s retirement immediately transformed a lean-GOP seat into a safe-Democratic seat: Attorney General Richard Blumenthal crushes Rob Simmons 56% to 33%, Linda McMahon 58% to 34% and Peter Schiff 60% to 24%. These margins are slightly smaller than the ones PPP found earlier this week, but they’re certainly very decisive and show no hint of vulnerability on Blumenthal’s part since he very solidly clears the 50% threshold.

In fact, Connecticut could cheer Democrats overall in November, since PPP also found the party is clearly favored to win a gubernatorial election for the first time since 1986. While all candidates have somewhat low name recognition, the bottom-line is that Secretary of State Susan Bysiewicz leads the two Republican candidates (Lieutenant Governor Michael Fedele and former Ambassador Tom Foley) by 25% and 22%; Ned Lamont and Dan Malloy leads’ are less decisive, but they do reach double-digits.

On top of polling the senatorial and gubernatorial numbers, PPP also tested Joe Lieberman’s approval rating, and the numbers are brutal: While Lieberman managed to keep somewhat decent numbers after his endorsement of McCain, it seems like the health care debate did cost him whatever support he had left among Democrats. His approval rating stands at 25% (14% among Democrats), with 67% disapproving, which has got to make him one of the most unpopular senators in the country. Only 19% approved of Lieberman’s health-care related actions (versus 68%). Sure, Blumenthal can no longer be of service to dislodge Lieberman in 2012, but with numbers like this there are many other Democrats who’d have a strong shot.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Rasmussen showers Senate Dems with troubling polls: GOP leads in 5 Dem-held seats

In the heels of his polls from Connecticut, Ohio and Pennsylvania’s Senate races, which he released earlier this week, Rasmussen conducted surveys from other states, finding worrisome signs for Democrats across the board. It speaks to this year’s reversal of fortunes that the best news the party can muster is that Lee Fisher (who was in the lead for much of the year) is staying afloat in Ohio while Alexi Giannoulias has pulled ahead to a lead within the MoE in staunchly blue Illinois.

Put all of this together, and we find that this week Rasmussen has released polls of 5 Senate races Dems are defending in which Republican candidates lead at least one match-up: Connecticut, Colorado, Illinois, Nevada, Pennsylvania. (And that still leaves out Arkansas and Delaware, which get us to 7 highly endangered Democratic seats.) On the other hand, the trendline are positive for Democrats in some of these polls, suggesting that the party might have already hit rock-bottom in some of these states; in particular, Rasmussen’s poll is I believe the ever to find Giannoulias with any sort of lead over Mark Kirk!

Let’s start by stating what needs to be said from the get go: Rasmussen’s results have been more favorable to Republicans than any other pollster’s all year, so these surveys represent the worse of the spectrum of possibilities for Democrats. Yet, it would be a mistake for Democrats to dismiss these results as outliers. First, the consistency with which Rasmussen’s results are skewed to the right means that the discrepancy is due to differing turnout models (and there is for now little evidence with which to say that theirs is wrong). Second, Rasmussen’s results are increasingly less divergent with those of other pollsters; PPP, Quinnipiac and Mason-Dixon have all recently found similar results in states like NV, PA and OH.

Colorado

Colorado is one state that has been so underpolled that we haven’t had a good idea of the incumbent’s vulnerability. This week, Rasmussen gave us a rare look into Michael Bennet’s prospects - and things look very ugly for the senator, who trails three Republicans challengers: 46% to 37% against former Lieutenant Governor Jane Norton, 42% to 41% against former state Senator Tom Wiens and 42% to 38% against District Attorney Ken Buck. In September, Rasmussen had Bennett leading Buck by 4% - and that was a more favorable result to the Democrat than PPP’s August survey.

Weighed down by a negative favorability rating (39-46), Bennet looks very vulnerable: I don’t have to tell for any incumbent to be stuck at 40% or to trail against opponents who are as low-profile statewide as Wiens and Buck is a dismal showing. Complicating matters is that state Speaker Andrew Romanoff is performing at similar levels: He faces a slightly larger deficit against Norton (45% to 34%), a slightly smaller one against Buck (41% to 39%) and the same one against Wiens (41% to 40%). Given that Romanoff is not an incumbent, that he can appeal to undecided voters as an outsider and that he has a positive name recognition, he is certainly in a position to make the case that he is more electable than Bennet. (A reminder: Bennet has never  before faced voters in any election.)

Nevada

Harry Reid might face smaller deficits, but his position is arguably far shakier than Bennet because he has far less room to grow as en entrenched incumbent and because his favorability rating is truly atrocious (40% to 57%). Furthermore, he trails former Assemblywoman Sharron Angle 47% to 43% in the very first survey testing her candidacy; a staunch conservative, Angle is reputed the weakest of Reid’s potential opponents so that the senator cannot even muster a lead against her is an ugly sign. Furthermore, Reid trails both Sue Lowden and Danny Tarkanian 49% to 43%.

The good news for Reid is that he has improved his numbers from Rasmussen’s prior poll of the race: In September, he trailed Lowden by 10% and Tarkanian by 7%, so perhaps his early efforts to improve his image have yielded results. Furthermore, the fact that the results are the same whoever Reid’s opponent confirms that voters aren’t voting Republican because they are enamored with any of the choices but only because of how much they have grown to dislike their senator; unfortunately for Reid, it won’t be easy for him to take advantage of that fact since he is too well-known to easily escape having this race be a referendum on his tenure.

Illinois

Democrats face far less of an uphill climb here, but Illinois is so blue that the party has nothing to boast about consideirng Rep. Mark Kirk’s competitive results: The Republican congressman, who has a stronger favorability rating than any of the 3 Democratic candidates, is within the margin of error in all match-ups. He trails Alexi Giannoulias 42% to 39%, leads Cheryle Jackson 42% to 39% and leads Dave Hoffman 42% to 38%. Just as in Nevada, Democrats can take some comfort in the trendline: Rasmussen’s summer poll had Kirk leading by 3%, while the October survey had a tie.

In fact, I believe this might be the first survey to find Giannoulias with any sort of lead because PPP’s only survey also had a tie while an internal GOP poll had the Republican leading by 7% earlier in October. This could due to the fact that Democrats are occupying airwaves right now: Their primary, which is coming up in February, is more obviously competitive, and Giannoulias and Hoffman are already up on air. (I don’t believe the same is true for Kirk.) Another reassuring nugget for Democrats is that Barack Obama’s approval rating remains strong in his home state (58% to 42%), so Republicans still have to show they can convince state voters to go against their usual party loyalty.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Weekly 2010 update: House Dems get themselves 2 unexpected headaches

Last night, city comptroller Annise Parker was elected Mayor of Houston on a 53% to 47% vote, making Houston the largest city to elect a gay mayor after a runoff election that was marked by explicitly homophobic campaigning. This vote added to gay rights activists’ ballot-box successes this year: Washington State passing RI-71, Chapel Hill’s mayoral race, a local referendum in Kalamazoo, Georgia electing its first gay African-American legislator. That track record has been understandably overshadowed by Maine’s vote on gay marriage, but Parker’s victory (combined with California preparing to elect its first gay Speaker) caps the year favorably.

In national politics, this week’s dominant story is that House Democrats got themselves two unexpected headaches. First is Brian Baird’s out-of-nowhere retirement announcement, which makes the swing WA-03 district a prime pick-up opportunity for the GOP; second, Neil Abercrombie’s resignation creates a tricky special election that gives a Republican a chance to capture HI-01 with a plurality of the vote. The other high-profile development came from MA, where Martha Coakley and Scott Brown won their party’s nominations to face off in the January Senate special election. In other news:

In Nevada, Harry Reid’s prospects might still take a turn for the worse. Lieutenant Governor Brian Krolicki, who was at the top of the NRSC’s list when the cycle started, was eliminated from contention when he was indicted on charges of misappropriation and falsification of accounts. This week, a court dismissed the charges as overly vague, potentially enabling Krolicki to mount a challenge to the Senate Majority Leader. While his spokesperson initially said he would not be running but reports now say he is considering jumping in. We would have to see how much lasting damage Krolicki’s image endured because of his indictment, but his entry should still be a step-up for the GOP.

In Rhode Island, Linc Chaffee’s prospects of winning the Governor’s Mansion improved this week as the sole Republican in the race (businessman Rory Smith) announced he was dropping out. If the GOP fails to file a credible contender, Chaffee would become the contest’s right-most option despite the fact that he will be running as an independent. Rhode Island is a staunchly blue state in Democrats have a strong bench, but a Lieberman-Lamont type scenario would help the former Senator’s political comeback.

In Alaska, Governor Sean Parnell (who was elevated to that position after Sarah Palin’s resignation) got himself a primary challenger:  former Speaker Ralph Samuels, who left the legislature in 2008 to work as a vice-president for Holland America Line. Samuels made it clear that the catalyst that pushed him towards a run was Parnell’s support for taxes on oil companies Palin pushed during her tenure. As such, it will be interesting to see how fiscal conservatives react considering Parnell has been a protege of the Club for Growth.

In South Dakota, Matt McGovern dropped out of the Senate race, depriving Democrats of the one challenger they had found to John Thune. The party would be well-advised to field a credible contender: While Thune will be the overwhelming favorite no matter who Democrats nominate, if he does not have to work for his re-election at all he would be free to travel around the country, building a network that would be useful for a future presidential campaign.

In Idaho, it’s still highly unlikely that Governor Butch Otter will have to sweat to win re-election; but from the sound of this article, the state’s political establishment was shocked to learn that former professor Keith Allred would challenge him as a Democrat. Allred had formed a citizens group that had acquired clout in Boise, and he had a nonpartisan profile that had won him many allies in both parties. Democrats now seem delighted at his unexpected gubernatorial candidacy, which could make the race worth watching - but the bottom line is that Idaho is ranked the 35th most vulnerable race (out of 37) in my latest gubernatorial ratings.

Finally, we are still waiting to find out whether to Southern senators will face primary challenges. This week, the buzz surrounding Louisiana Secretary of State Jay Dardenne and Arkansas Lieutenant Governor Brian Halter increased, as the former stated again that he was considering challenging David Vitter and the latter traveled to D.C. to meet with some union leaders and progressives about the possibility he might run against Blanche Lincoln.

As always, I list all the changes I have logged in during the week to the “retirement watch” and recruitment pages. First, updates to Retirement Watch:

Will retire Rep. Brian Baird (WA-04)
Will resign Rep. Brian Abercrombie (HI-01)
Will not resign Rep. Mike Capuano (MA-08)

Second, updates to the Senate recruitment page:

KY-Sen, Dem doctor James Buckmaster is running
retired customs officer Darlene Price is running
businessman Maurice Sweeney is running
KY-Sen, GOP businessman Bill Johnson is running
Gurley Martin is running
consultant Roger Thoney is running
MA-Sen, Dem Attorney General Martha Coakley won nomination
MA-Sen, GOP state Senator Scott Brown won nomination
NC-Sen, Dem former state Sen. Cal Cunningham announced run
Chapel Hill Mayor Kevin Foy wlll not run
NV-Sen, GOP Lieutenant Governor Brian Krolicki added
SD-Sen, Dem Matt McGovern dropped out

Third, updates to gubernatorial races:

AK-Gov, GOP former state Rep. Ralph Samuels announced run
ID-Gov, Dem Keith Allred announced run
NH-Gov, GOP Karen Testerman announced run
OR-Gov, Dem Soloflex founder Jerry Wilson is running
RI-Gov, GOP businessman Rory Smith dropped out
TX-Gov, Dem teacher Felix Alvarado is running
Bill Dear is running
hair products magnate Farouk Shami is running

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Democrats have to defend fewer freshmen than they did in 1994

Over the past few weeks, I have repeatedly discussed how low a number of vulnerable open seats Democrats have to defend in 2010; even with Dennis Moore and John Tanner’s unexpected retirements, the situation bears no resemblance to anything the party experienced in 1994 or that Republicans had to deal within 2006 and in 2008. Via Swing State Project’s Twitter feed, there is another historical comparison that should prevent Republicans from scoring the huge gains they are hoping for.

Going into 1994, Democrats had two big weaknesses. We’ve talked at length about the first - open seats; they lost 22. Teh second was the large number of junior lawmakers in their caucus: Due to a big wave of retirements in the 1992 cycle and to the redistricting changes of 1991, there were 63 freshmen Democrats running for re-election in 1994. (16 ended up losing.) In 2010, there will be a lower number of Democratic freshmen: 37.

This is a great firewall for the party because freshmen are by far the most vulnerable lawmakers: They have not had time to build a solid infrastructure in the district, they have yet to build the fundraising, name recognition and institutional network that allows so many incumbents to keep their seats indefinitely, and they haven’t been in Congress long enough to tout their experience or their seniority. In short, they have to suffer through the disadvantages of incumbency (insider status, tough votes) without many of its benefits. In 1994, 16 of the 63 freshmen Democrats lost (that’s more than 25%); in 2008, 4of the 5 Democrats who lost their seat were freshmen.

Of course, none of this is to say that 37 freshmen is a small number. Quite the contrary, it’s far larger than the number Republicans had to defend in 2006 (18) and in 2008 (13). Republicans could certainly inflict major damage in Democratic ranks since a red wave would be likely to submerge many of these first-term lawmakers; looking at these 37 Democrats, only 10 are sure to win re-election no matter what which does makes 27 pick-up opportunities for Republicans.

For instance, Mason Dixon released a very rare public poll of a House race this week-end, and the result was not pretty for Democrats in a district (NV-03) that Obama won by 12%: freshman Rep. Dina Titus is tied at 40% with former state Sen. Joe Heck. Now, Heck is a top GOP recruit (at the beginning of the cycle, the NRSC was hoping to get him to challenge Reid) and Titus does manage a healthier 48-32 lead against lesser-known Rob Lauer; she will also draw comfort from the fact that she has a 9% lead among independents and has more room to grow among Dems (she’s at 69%). But it goes without saying that any incumbent who polls at 40% is very vulnerable.

My overall point, then, is merely that 37 should prove insufficient compared to the huge number of pick-ups the GOP has to score to recapture the majority - especially when you combine it to the fact that at this point they only have to worry about 5 open seats and to the fact that the GOP hasn’t made a priority of defeating all 27 aforementioned Democrats. (Ann Kirkpatrick, Eric Massa, Michael McMahon, Kurt Schrader or Scott Murphy don’t face that worrisome a cycle for now.)

What’s important to emphasize is that picking-up open seats and beating freshmen can often be done easily. It becomes obvious early in the fall that a district is going to switch so that neither party devotes much attention (and money) to it and the battle is displaced somewhere else; in 2006 and in 2008, Democrats put countless of districts in the bag like this, which allowed them to expand the map. On the other hand, entrenched incumbents can be beat - but that almost always takes a major battle that consumes resources; there’s only so many veterans who can be ousted like that.

In short: Republicans’ ability to expand the map to districts that have sometimes not been contested in decades positions them to make substantial gains, but to approach a 41 seat pick-up they’d need more easy opportunities than they have. Democrats did short of that number in 2006 and in 2008 - and it’s not like the environment (or the number of open seats they had a shot at) left a lot to be desired.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Harry and Rory transform Nevada into land mine for Democrats

For Democrats, Nevada is threatening to be as much of a nightmare in 2010 as it was close to perfection in 2008 - and month by month, it is looking increasingly likely that Dick Durbin and Chuck Schumer will have a shot at becoming Senate Majority Leader come January 2011.

The latest Mason Dixon poll of the Senate race finds that Harry Reid’s numbers are as low as ever. A favorability rating of 38/49 (his approval rating is probably lower) is bound to put any senator in trouble; and in case there are any doubts left that Nevadans are committed to getting rid of their senator, they should be dissipated by the fact that he is trailing 51% to 41% against Sue Lowden and 48% to 42% against Danny Tarkanian.

If it’s a sign of weakness for an incumbent to be under 50%, we reach a whole other level of vulnerability when the challenger clears that threshold - especially when we’re talking about a little-known candidate. (Note that a surprisingly large share of the electorate says they recognize Tarkanian and Lowden’s names, which suggests they are not that low-profile. Yet, many of these respondents also say they do not have a clear opinion of these candidates, which does mean they have room to grow.)

Perhaps most worrisome for Reid is that this poll was conducted after he launched ad campaigns meant to improve his image: That certainly doesn’t look like it has helped, which only confirms how hard it is for well-known incumbents to change voters’ perception. Sure, Reid’s large cash-on-hand will help him attack his challengers, thus blunting their ability to introduce themselves to voters in a positive light. Yet, he is tied up by the fact that he won’t know who is opponent will be until early June: The GOP nomination could be won by any number of candidates, and it wouldn’t be a good idea for Reid to launch preemptive attacks against even just two or three of them.

Reid will have to wait for the primary to be resolved, and hope not only that the candidates have emptied each other’s bank account but also that Republicans have chosen a nominee who’s weak enough to have trouble in the general election. Facing former Assemblywoman Sharron Angle is probably Reid’s best bet. (This is a case where Democrats should be careful what they wish for, though. There isn’t in the conservative Angle’s profile to make her unelectable against as unpopular a senator as Reid.) In testing the GOP primary, Mason Dixon found Angle receiving 13%, not far behind Lowden (25%) and Tarkanian (24%); unfortunately, she was not tested in the general election.

The Reid family’s prospects are looking just as damaged in the Governor’s race: Not that Rory Reid stands at depths of unpopularity, but given that he is an elected official at the county level the fact that he has a favorability rating of 23-28 can only be due to the trickle-down effect of his father’s vulnerability.

Rory is taking the time to insist that Harry’s standing won’t impact his campaign, but it’s hard to see how the fact that the state’s Democratic ticket could be led by two members of the same family might possibly not have major consequences on the results.

Rory’s numbers are all the more worrisome for Democratic chances compared to those of Republican frontrunner Brian Sandoval, whose favorability rating stands at 39-6. In that context, Sandoval unsurprisingly vaults to a 49% to 34% lead over Reid. He not only leads by 17% among independents, but he also receives 21% of the Democratic vote; he even leads in Clark County.

Sure, Reid does manage a 48% to 34% lead over Governor Jim Gibbons, who stands no chance of winning in the general election (no incumbent with a 19% favorability rating and a 50% unfavorability rating can hope to even be competitive); the problem for Democrats is that Gibbons will not make it that far. In the GOP primary, he trails Sandoval 39% to 18%; sure, that’s far smaller than the deficit David Paterson faces against Andrew Cuomo but it’s truly an atrocious level of support for an incumbent to receive from his base.

Interestingly, Mason Dixon chose to once again not test what would happen if Oscar Goodman ran as a Democrat (a possibility he has not ruled out), but they do test three-way races that include the Las Vegas Mayor as an independent. Whoever his opponents, Goodman leads - easily if his GOP opponent is Gibbons (Goodman receives 38%, with 25% for Reid and Gibbons), narrowly if his GOP opponent if Reid (he receives 35%, with 32% for Sandoval and 24% for Reid). It’s telling of Reid’s weak standing that he gets as much support as Gibbons in the first configuration; in the second, he only receives 16% among independents.

The GOP is lucky that Harry Reid’s unpopularity and Sandoval’s popularity are so pronounced, because the scandals surrounding their own incumbents could have otherwise dominated the state’s political environment and sank the party’s chances otherwise. I already mentioned just how unpopular Gibbons is, and the interview the governor’s former wife just gave to the Reno Gazette certainly won’t help him turn the page.

As significantly, Senator John Ensign’s troubles over his affair and the financial transactions that surrounded it continue to mount since the Senate Ethics Committee is now stepping up its investigations and issuing subpoenas. With Doug Hampton continually upping the stakes in his statements to the press, it will be interesting to see what he tells the committee if he testifies under oath. Yet, Ensign has found an effective counter-argument that should dissuade Republicans from ever calling for his resignation: point out that a special election to fill his seat could distract from the party’s efforts to unseat the Senate Majority Leader. “For the people who want to beat Harry Reid if you have a second Senate race in this state, that takes the attention off of Senator Reid,” he said this week.



If you like the website...

... Support Campaign Diaries


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method K2::filter_post_comments() should not be called statically in /homepages/33/d214989360/htdocs/wp-includes/plugin.php on line 166

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Strict Standards: array_filter() expects parameter 2 to be a valid callback, non-static method K2::strip_trackback() should not be called statically in /homepages/33/d214989360/htdocs/wp-content/themes/k2/app/classes/k2.php on line 458

Recent Posts


    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • All good things must come to an end

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • What remains on the table

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Confusion in Connecticut (Updated)

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Results thread, part 2: Dems suffer staggering losses in House and legislatives races, limit damage in statewide races

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Election Night results thread: Rep. Boucher’s fall first surprise of the night

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Election night cheat sheet

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • Final ratings: Democrats brace for historic losses

  • Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55
  • What to watch for down-ballot

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/33/d214989360/htdocs/wp-includes/functions.php on line 55

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/33/d214989360/htdocs/wp-includes/kses.php on line 1003

Archives