Latest Entries »

Earth Watch Report  -  Earthquakes

 photo Russia-44EQsMay20th-23rd_zpsee611354.jpg

….

M4.8 – 117km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 00:05:07 UTC

Earthquake location 52.418°N, 160.048°E

Event Time

  1. 2013-05-20 00:05:07 UTC
  2. 2013-05-20 11:05:07 UTC+11:00 at epicenter
  3. 2013-05-19 19:05:07 UTC-05:00 system time

Location

52.418°N 160.048°E depth=60.1km (37.3mi)

Nearby Cities

  1. 117km (73mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 125km (78mi) ESE of Vilyuchinsk, Russia
  3. 141km (88mi) SE of Yelizovo, Russia
  4. 981km (610mi) SE of Magadan, Russia
  5. 2455km (1525mi) NE of Tokyo, Japan

….

M5.3 – 131km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 00:13:17 UTC

Earthquake location 52.305°N, 160.170°E

Event Time

  1. 2013-05-20 00:13:17 UTC
  2. 2013-05-20 11:13:17 UTC+11:00 at epicenter
  3. 2013-05-19 19:13:17 UTC-05:00 system time

Location

52.305°N 160.170°E depth=33.2km (20.6mi)

Nearby Cities

  1. 131km (81mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 138km (86mi) ESE of Vilyuchinsk, Russia
  3. 155km (96mi) SE of Yelizovo, Russia
  4. 996km (619mi) SE of Magadan, Russia
  5. 2453km (1524mi) NE of Tokyo, Japan

….

M4.9 – 124km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 00:22:13 UTC

Earthquake location 52.432°N, 160.183°E

Event Time

  1. 2013-05-20 00:22:13 UTC
  2. 2013-05-20 11:22:13 UTC+11:00 at epicenter
  3. 2013-05-19 19:22:13 UTC-05:00 system time

Location

52.432°N 160.183°E depth=30.2km (18.7mi)

Nearby Cities

  1. 124km (77mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 132km (82mi) ESE of Vilyuchinsk, Russia
  3. 147km (91mi) SE of Yelizovo, Russia
  4. 984km (611mi) SE of Magadan, Russia
  5. 2463km (1530mi) NE of Tokyo, Japan

….

M5.1 – 121km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 01:07:39 UTC

Earthquake location 52.415°N, 160.119°E

Event Time

  1. 2013-05-20 01:07:39 UTC
  2. 2013-05-20 12:07:39 UTC+11:00 at epicenter
  3. 2013-05-19 20:07:39 UTC-05:00 system time

Location

52.415°N 160.119°E depth=42.6km (26.5mi)

Nearby Cities

  1. 121km (75mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 129km (80mi) ESE of Vilyuchinsk, Russia
  3. 145km (90mi) SE of Yelizovo, Russia
  4. 984km (611mi) SE of Magadan, Russia
  5. 2459km (1528mi) NE of Tokyo, Japan

….

M4.6 – 21km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 01:33:33 UTC

Earthquake location 52.972°N, 158.941°E

Event Time

  1. 2013-05-20 01:33:33 UTC
  2. 2013-05-20 13:33:33 UTC+12:00 at epicenter
  3. 2013-05-19 20:33:33 UTC-05:00 system time

Location

52.972°N 158.941°E depth=84.3km (52.4mi)

Nearby Cities

  1. 21km (13mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 36km (22mi) E of Vilyuchinsk, Russia
  3. 44km (27mi) ESE of Yelizovo, Russia
  4. 889km (552mi) SE of Magadan, Russia
  5. 2442km (1517mi) NNE of Tokyo, Japan

….

M4.6 – 201km SE of Petropavlovsk-Kamchatskiy, Russia

2013-05-20 03:38:50 UTC

Earthquake location 51.611°N, 160.464°E

Event Time

  1. 2013-05-20 03:38:50 UTC
  2. 2013-05-20 14:38:50 UTC+11:00 at epicenter
  3. 2013-05-19 22:38:50 UTC-05:00 system time

Location

51.611°N 160.464°E depth=15.1km (9.4mi)

Nearby Cities

  1. 201km (125mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 203km (126mi) SE of Vilyuchinsk, Russia
  3. 225km (140mi) SE of Yelizovo, Russia
  4. 1072km (666mi) SE of Magadan, Russia
  5. 2419km (1503mi) NE of Tokyo, Japan

….

M4.7 – 135km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 03:42:39 UTC

Earthquake location 52.289°N, 160.216°E

Event Time

  1. 2013-05-20 03:42:39 UTC
  2. 2013-05-20 14:42:39 UTC+11:00 at epicenter
  3. 2013-05-19 22:42:39 UTC-05:00 system time

Location

52.289°N 160.216°E depth=49.0km (30.4mi)

Nearby Cities

  1. 135km (84mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 142km (88mi) ESE of Vilyuchinsk, Russia
  3. 159km (99mi) SE of Yelizovo, Russia
  4. 999km (621mi) SE of Magadan, Russia
  5. 2454km (1525mi) NE of Tokyo, Japan

….

M4.7 – 110km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 10:54:24 UTC

Earthquake location 52.510°N, 160.023°E

Event Time

  1. 2013-05-20 10:54:24 UTC
  2. 2013-05-20 21:54:24 UTC+11:00 at epicenter
  3. 2013-05-20 05:54:24 UTC-05:00 system time

Location

52.510°N 160.023°E depth=43.8km (27.2mi)

Nearby Cities

  1. 110km (68mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 119km (74mi) ESE of Vilyuchinsk, Russia
  3. 133km (83mi) ESE of Yelizovo, Russia
  4. 971km (603mi) SE of Magadan, Russia
  5. 2461km (1529mi) NE of Tokyo, Japan

….

M4.7 – 148km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 12:43:33 UTC

Earthquake location 52.240°N, 160.402°E

Event Time

  1. 2013-05-20 12:43:33 UTC
  2. 2013-05-20 23:43:33 UTC+11:00 at epicenter
  3. 2013-05-20 07:43:33 UTC-05:00 system time

Location

52.240°N 160.402°E depth=30.5km (18.9mi)

Nearby Cities

  1. 148km (92mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 155km (96mi) ESE of Vilyuchinsk, Russia
  3. 172km (107mi) SE of Yelizovo, Russia
  4. 1010km (628mi) SE of Magadan, Russia
  5. 2460km (1529mi) NE of Tokyo, Japan

….

M4.7 – 129km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 13:57:04 UTC

Earthquake location 52.283°N, 160.096°E

Event Time

  1. 2013-05-20 13:57:04 UTC
  2. 2013-05-21 00:57:04 UTC+11:00 at epicenter
  3. 2013-05-20 08:57:04 UTC-05:00 system time

Location

52.283°N 160.096°E depth=52.8km (32.8mi)

Nearby Cities

  1. 129km (80mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 135km (84mi) ESE of Vilyuchinsk, Russia
  3. 153km (95mi) SE of Yelizovo, Russia
  4. 995km (618mi) SE of Magadan, Russia
  5. 2448km (1521mi) NE of Tokyo, Japan

….

M4.8 – 147km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 14:12:43 UTC

Earthquake location 52.308°N, 160.467°E

Event Time

  1. 2013-05-20 14:12:43 UTC
  2. 2013-05-21 01:12:43 UTC+11:00 at epicenter
  3. 2013-05-20 09:12:43 UTC-05:00 system time

Location

52.308°N 160.467°E depth=45.0km (28.0mi)

Nearby Cities

  1. 147km (91mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 156km (97mi) ESE of Vilyuchinsk, Russia
  3. 171km (106mi) SE of Yelizovo, Russia
  4. 1006km (625mi) SE of Magadan, Russia
  5. 2469km (1534mi) NE of Tokyo, Japan

….

M4.3 – 65km SE of Vilyuchinsk, Russia

2013-05-20 14:27:39 UTC

Earthquake location 52.495°N, 159.057°E

Event Time

  1. 2013-05-20 14:27:39 UTC
  2. 2013-05-21 01:27:39 UTC+11:00 at epicenter
  3. 2013-05-20 09:27:39 UTC-05:00 system time

Location

52.495°N 159.057°E depth=83.6km (51.9mi)

Nearby Cities

  1. 65km (40mi) SE of Vilyuchinsk, Russia
  2. 67km (42mi) SSE of Petropavlovsk-Kamchatskiy, Russia
  3. 89km (55mi) SSE of Yelizovo, Russia
  4. 939km (583mi) SE of Magadan, Russia
  5. 2411km (1498mi) NNE of Tokyo, Japan

….

M4.7 – 145km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 18:08:48 UTC

Earthquake location 52.340°N, 160.452°E

Event Time

  1. 2013-05-20 18:08:48 UTC
  2. 2013-05-21 05:08:48 UTC+11:00 at epicenter
  3. 2013-05-20 13:08:48 UTC-05:00 system time

Location

52.340°N 160.452°E depth=40.1km (24.9mi)

Nearby Cities

  1. 145km (90mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 153km (95mi) ESE of Vilyuchinsk, Russia
  3. 168km (104mi) ESE of Yelizovo, Russia
  4. 1003km (623mi) SE of Magadan, Russia
  5. 2470km (1535mi) NE of Tokyo, Japan

….

M5.0 – 138km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 20:13:54 UTC

Earthquake location 52.319°N, 160.315°E

Event Time

  1. 2013-05-20 20:13:54 UTC
  2. 2013-05-21 07:13:54 UTC+11:00 at epicenter
  3. 2013-05-20 15:13:54 UTC-05:00 system time

Location

52.319°N 160.315°E depth=32.2km (20.0mi)

Nearby Cities

  1. 138km (86mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 146km (91mi) ESE of Vilyuchinsk, Russia
  3. 162km (101mi) SE of Yelizovo, Russia
  4. 1000km (621mi) SE of Magadan, Russia
  5. 2462km (1530mi) NE of Tokyo, Japan

….

M4.6 – 122km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 22:36:27 UTC

Earthquake location 52.470°N, 160.195°E

Event Time

  1. 2013-05-20 22:36:27 UTC
  2. 2013-05-21 09:36:27 UTC+11:00 at epicenter
  3. 2013-05-20 17:36:27 UTC-05:00 system time

Location

52.470°N 160.195°E depth=40.0km (24.8mi)

Nearby Cities

  1. 122km (76mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 131km (81mi) ESE of Vilyuchinsk, Russia
  3. 146km (91mi) ESE of Yelizovo, Russia
  4. 981km (610mi) SE of Magadan, Russia
  5. 2466km (1532mi) NE of Tokyo, Japan

….

M4.8 – 121km SE of Petropavlovsk-Kamchatskiy, Russia

2013-05-20 22:51:47 UTC

Earthquake location 52.425°N, 160.127°E

Event Time

  1. 2013-05-20 22:51:47 UTC
  2. 2013-05-21 09:51:47 UTC+11:00 at epicenter
  3. 2013-05-20 17:51:47 UTC-05:00 system time

Location

52.425°N 160.127°E depth=43.8km (27.2mi)

Nearby Cities

  1. 121km (75mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 129km (80mi) ESE of Vilyuchinsk, Russia
  3. 145km (90mi) SE of Yelizovo, Russia
  4. 983km (611mi) SE of Magadan, Russia
  5. 2460km (1529mi) NE of Tokyo, Japan

….

M5.3 – 126km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-20 23:01:25 UTC

Earthquake location 52.426°N, 160.223°E

Event Time

  1. 2013-05-20 23:01:25 UTC
  2. 2013-05-21 10:01:25 UTC+11:00 at epicenter
  3. 2013-05-20 18:01:25 UTC-05:00 system time

Location

52.426°N 160.223°E depth=17.4km (10.8mi)

Nearby Cities

  1. 126km (78mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 135km (84mi) ESE of Vilyuchinsk, Russia
  3. 150km (93mi) ESE of Yelizovo, Russia
  4. 986km (613mi) SE of Magadan, Russia
  5. 2465km (1532mi) NE of Tokyo, Japan

….

M4.6 – 22km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 00:01:16 UTC

Earthquake location 52.957°N, 158.949°E

Event Time

  1. 2013-05-21 00:01:16 UTC
  2. 2013-05-21 12:01:16 UTC+12:00 at epicenter
  3. 2013-05-20 19:01:16 UTC-05:00 system time

Location

52.957°N 158.949°E depth=93.7km (58.2mi)

Nearby Cities

  1. 22km (14mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 36km (22mi) E of Vilyuchinsk, Russia
  3. 45km (28mi) SE of Yelizovo, Russia
  4. 891km (554mi) SE of Magadan, Russia
  5. 2441km (1517mi) NNE of Tokyo, Japan

….

M6.0 – 139km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 01:55:05 UTC

Earthquake location 52.469°N, 160.486°E

Event Time

  1. 2013-05-21 01:55:05 UTC
  2. 2013-05-21 12:55:05 UTC+11:00 at epicenter
  3. 2013-05-20 20:55:05 UTC-05:00 system time

Location

52.469°N 160.486°E depth=15.1km (9.4mi)

Nearby Cities

  1. 139km (86mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 149km (93mi) ESE of Vilyuchinsk, Russia
  3. 162km (101mi) ESE of Yelizovo, Russia
  4. 992km (616mi) SE of Magadan, Russia
  5. 2481km (1542mi) NE of Tokyo, Japan

….

Instrumental Intensity

ShakeMap Intensity Image

….

M4.9 – 138km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 02:02:45 UTC

Earthquake location 52.429°N, 160.422°E

Event Time

  1. 2013-05-21 02:02:45 UTC
  2. 2013-05-21 13:02:45 UTC+11:00 at epicenter
  3. 2013-05-20 21:02:45 UTC-05:00 system time

Location

52.429°N 160.422°E depth=44.2km (27.5mi)

Nearby Cities

  1. 138km (86mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 147km (91mi) ESE of Vilyuchinsk, Russia
  3. 161km (100mi) ESE of Yelizovo, Russia
  4. 993km (617mi) SE of Magadan, Russia
  5. 2475km (1538mi) NE of Tokyo, Japan

….

M5.5 – 137km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 03:05:50 UTC

Earthquake location 52.370°N, 160.357°E

Event Time

  1. 2013-05-21 03:05:50 UTC
  2. 2013-05-21 14:05:50 UTC+11:00 at epicenter
  3. 2013-05-20 22:05:50 UTC-05:00 system time

Location

52.370°N 160.357°E depth=14.4km (9.0mi)

Nearby Cities

  1. 137km (85mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 146km (91mi) ESE of Vilyuchinsk, Russia
  3. 161km (100mi) ESE of Yelizovo, Russia
  4. 997km (620mi) SE of Magadan, Russia
  5. 2468km (1534mi) NE of Tokyo, Japan

….

Instrumental Intensity

ShakeMap Intensity Image

….

M5.0 – 143km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 04:24:07 UTC

Earthquake location 52.335°N, 160.419°E

Event Time

  1. 2013-05-21 04:24:07 UTC
  2. 2013-05-21 15:24:07 UTC+11:00 at epicenter
  3. 2013-05-20 23:24:07 UTC-05:00 system time

Location

52.335°N 160.419°E depth=28.5km (17.7mi)

Nearby Cities

  1. 143km (89mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 151km (94mi) ESE of Vilyuchinsk, Russia
  3. 167km (104mi) SE of Yelizovo, Russia
  4. 1002km (623mi) SE of Magadan, Russia
  5. 2468km (1534mi) NE of Tokyo, Japan

….

M6.0 – 122km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 04:59:37 UTC

Earthquake location 52.325°N, 160.023°E

Event Time

  1. 2013-05-21 04:59:37 UTC
  2. 2013-05-21 15:59:37 UTC+11:00 at epicenter
  3. 2013-05-20 23:59:37 UTC-05:00 system time

Location

52.325°N 160.023°E depth=37.1km (23.1mi)

Nearby Cities

  1. 122km (76mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 128km (80mi) ESE of Vilyuchinsk, Russia
  3. 146km (91mi) SE of Yelizovo, Russia
  4. 989km (615mi) SE of Magadan, Russia
  5. 2447km (1520mi) NE of Tokyo, Japan

….

Instrumental Intensity

ShakeMap Intensity Image

….

M6.0 – 122km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 05:43:21 UTC

Earthquake location 52.307°N, 159.986°E

Event Time

  1. 2013-05-21 05:43:21 UTC
  2. 2013-05-21 16:43:21 UTC+11:00 at epicenter
  3. 2013-05-21 00:43:21 UTC-05:00 system time

Location

52.307°N 159.986°E depth=36.7km (22.8mi)

Nearby Cities

  1. 122km (76mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 127km (79mi) ESE of Vilyuchinsk, Russia
  3. 146km (91mi) SE of Yelizovo, Russia
  4. 989km (615mi) SE of Magadan, Russia
  5. 2444km (1519mi) NE of Tokyo, Japan

….

Instrumental Intensity

ShakeMap Intensity Image

….

M4.6 – 129km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 06:03:39 UTC

Earthquake location 52.284°N, 160.094°E

Event Time

  1. 2013-05-21 06:03:39 UTC
  2. 2013-05-21 17:03:39 UTC+11:00 at epicenter
  3. 2013-05-21 01:03:39 UTC-05:00 system time

Location

52.284°N 160.094°E depth=55.1km (34.2mi)

Nearby Cities

  1. 129km (80mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 135km (84mi) ESE of Vilyuchinsk, Russia
  3. 153km (95mi) SE of Yelizovo, Russia
  4. 995km (618mi) SE of Magadan, Russia
  5. 2448km (1521mi) NE of Tokyo, Japan

….

M4.7 – 114km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 06:07:54 UTC

Earthquake location 52.392°N, 159.957°E

Event Time

  1. 2013-05-21 06:07:54 UTC
  2. 2013-05-21 17:07:54 UTC+11:00 at epicenter
  3. 2013-05-21 01:07:54 UTC-05:00 system time

Location

52.392°N 159.957°E depth=61.8km (38.4mi)

Nearby Cities

  1. 114km (71mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 121km (75mi) ESE of Vilyuchinsk, Russia
  3. 138km (86mi) SE of Yelizovo, Russia
  4. 980km (609mi) SE of Magadan, Russia
  5. 2448km (1521mi) NE of Tokyo, Japan

….

M4.6 – 91km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 06:20:19 UTC

Earthquake location 52.606°N, 159.790°E

Event Time

  1. 2013-05-21 06:20:19 UTC
  2. 2013-05-21 17:20:19 UTC+11:00 at epicenter
  3. 2013-05-21 01:20:19 UTC-05:00 system time

Location

52.606°N 159.790°E depth=52.0km (32.3mi)

Nearby Cities

  1. 91km (57mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 100km (62mi) ESE of Vilyuchinsk, Russia
  3. 114km (71mi) SE of Yelizovo, Russia
  4. 954km (593mi) SE of Magadan, Russia
  5. 2456km (1526mi) NNE of Tokyo, Japan

….

M4.7 – 136km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 07:06:48 UTC

Earthquake location 52.089°N, 159.911°E

Event Time

  1. 2013-05-21 07:06:48 UTC
  2. 2013-05-21 18:06:48 UTC+11:00 at epicenter
  3. 2013-05-21 02:06:48 UTC-05:00 system time

Location

52.089°N 159.911°E depth=52.4km (32.5mi)

Nearby Cities

  1. 136km (85mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 138km (86mi) SE of Vilyuchinsk, Russia
  3. 160km (99mi) SE of Yelizovo, Russia
  4. 1007km (626mi) SE of Magadan, Russia
  5. 2424km (1506mi) NE of Tokyo, Japan

….

M4.8 – 140km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 08:15:16 UTC

Earthquake location 52.362°N, 160.398°E

Event Time

  1. 2013-05-21 08:15:16 UTC
  2. 2013-05-21 19:15:16 UTC+11:00 at epicenter
  3. 2013-05-21 03:15:16 UTC-05:00 system time

Location

52.362°N 160.398°E depth=48.6km (30.2mi)

Nearby Cities

  1. 140km (87mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 149km (93mi) ESE of Vilyuchinsk, Russia
  3. 164km (102mi) ESE of Yelizovo, Russia
  4. 999km (621mi) SE of Magadan, Russia
  5. 2469km (1534mi) NE of Tokyo, Japan

….

M4.8 – 93km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 10:00:08 UTC

Earthquake location 52.659°N, 159.873°E

Event Time

  1. 2013-05-21 10:00:08 UTC
  2. 2013-05-21 21:00:08 UTC+11:00 at epicenter
  3. 2013-05-21 05:00:08 UTC-05:00 system time

Location

52.659°N 159.873°E depth=66.8km (41.5mi)

Nearby Cities

  1. 93km (58mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 103km (64mi) ESE of Vilyuchinsk, Russia
  3. 116km (72mi) ESE of Yelizovo, Russia
  4. 952km (592mi) SE of Magadan, Russia
  5. 2464km (1531mi) NNE of Tokyo, Japan

….

M4.8 – 143km ESE of Petropavlovsk-Kamchatskiy, Russia

2013-05-21 10:21:02 UTC

Earthquake location 52.327°N, 160.404°E

Event Time

  1. 2013-05-21 10:21:02 UTC
  2. 2013-05-21 21:21:02 UTC+11:00 at epicenter
  3. 2013-05-21 05:21:02 UTC-05:00 system time

Location

52.327°N 160.404°E depth=47.2km (29.3mi)

Nearby Cities

  1. 143km (89mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 151km (94mi) ESE of Vilyuchinsk, Russia
  3. 166km (103mi) SE of Yelizovo, Russia
  4. 1002km (623mi) SE of Magadan, Russia
  5. 2467km (1533mi) NE of Tokyo, Japan

….

M4.7 – 147km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 12:39:32 UTC

Earthquake location 52.373°N, 160.528°E

Event Time

  1. 2013-05-21 12:39:32 UTC
  2. 2013-05-21 23:39:32 UTC+11:00 at epicenter
  3. 2013-05-21 07:39:32 UTC-05:00 system time

Location

52.373°N 160.528°E depth=41.6km (25.8mi)

Nearby Cities

  1. 147km (91mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 156km (97mi) ESE of Vilyuchinsk, Russia
  3. 170km (106mi) ESE of Yelizovo, Russia
  4. 1003km (623mi) SE of Magadan, Russia
  5. 2477km (1539mi) NE of Tokyo, Japan

….

M4.6 – 20km S of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 13:23:29 UTC

Earthquake location 52.863°N, 158.705°E

Event Time

  1. 2013-05-21 13:23:29 UTC
  2. 2013-05-22 01:23:29 UTC+12:00 at epicenter
  3. 2013-05-21 08:23:29 UTC-05:00 system time

Location

52.863°N 158.705°E depth=92.0km (57.2mi)

Nearby Cities

  1. 20km (12mi) S of Petropavlovsk-Kamchatskiy, Russia
  2. 21km (13mi) ESE of Vilyuchinsk, Russia
  3. 42km (26mi) SSE of Yelizovo, Russia
  4. 891km (554mi) SE of Magadan, Russia
  5. 2422km (1505mi) NNE of Tokyo, Japan

….

M5.3 – 143km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 14:51:20 UTC

Earthquake location 52.549°N, 160.617°E

Event Time

  1. 2013-05-21 14:51:20 UTC
  2. 2013-05-22 01:51:20 UTC+11:00 at epicenter
  3. 2013-05-21 09:51:20 UTC-05:00 system time

Location

52.549°N 160.617°E depth=41.2km (25.6mi)

Nearby Cities

  1. 143km (89mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 155km (96mi) ESE of Vilyuchinsk, Russia
  3. 166km (103mi) ESE of Yelizovo, Russia
  4. 990km (615mi) SE of Magadan, Russia
  5. 2494km (1550mi) NE of Tokyo, Japan

….

M4.5 – 142km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 15:53:24 UTC

Earthquake location 52.602°N, 160.632°E

Event Time

  1. 2013-05-21 15:53:24 UTC
  2. 2013-05-22 02:53:24 UTC+11:00 at epicenter
  3. 2013-05-21 10:53:24 UTC-05:00 system time

Location

52.602°N 160.632°E depth=38.7km (24.0mi)

Nearby Cities

  1. 142km (88mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 154km (96mi) ESE of Vilyuchinsk, Russia
  3. 164km (102mi) ESE of Yelizovo, Russia
  4. 985km (612mi) SE of Magadan, Russia
  5. 2498km (1552mi) NE of Tokyo, Japan

….

M4.5 – 136km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 17:13:36 UTC

Earthquake location 52.494°N, 160.452°E

Event Time

  1. 2013-05-21 17:13:36 UTC
  2. 2013-05-22 04:13:36 UTC+11:00 at epicenter
  3. 2013-05-21 12:13:36 UTC-05:00 system time

Location

52.494°N 160.452°E depth=47.0km (29.2mi)

Nearby Cities

  1. 136km (85mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 146km (91mi) ESE of Vilyuchinsk, Russia
  3. 159km (99mi) ESE of Yelizovo, Russia
  4. 989km (615mi) SE of Magadan, Russia
  5. 2481km (1542mi) NE of Tokyo, Japan

….

M4.9 – 110km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 17:42:19 UTC

Earthquake location 52.368°N, 159.840°E

Event Time

  1. 2013-05-21 17:42:19 UTC
  2. 2013-05-22 04:42:19 UTC+11:00 at epicenter
  3. 2013-05-21 12:42:19 UTC-05:00 system time

Location

52.368°N 159.840°E depth=48.1km (29.9mi)

Nearby Cities

  1. 110km (68mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 115km (71mi) ESE of Vilyuchinsk, Russia
  3. 134km (83mi) SE of Yelizovo, Russia
  4. 978km (608mi) SE of Magadan, Russia
  5. 2441km (1517mi) NE of Tokyo, Japan

….

M4.5 – 121km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 18:01:55 UTC

Earthquake location 52.452°N, 160.154°E

Event Time

  1. 2013-05-21 18:01:55 UTC
  2. 2013-05-22 05:01:55 UTC+11:00 at epicenter
  3. 2013-05-21 13:01:55 UTC-05:00 system time

Location

52.452°N 160.154°E depth=37.9km (23.5mi)

Nearby Cities

  1. 121km (75mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 129km (80mi) ESE of Vilyuchinsk, Russia
  3. 144km (89mi) ESE of Yelizovo, Russia
  4. 981km (610mi) SE of Magadan, Russia
  5. 2463km (1530mi) NE of Tokyo, Japan

….

M4.9 – 91km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-21 19:37:41 UTC

Earthquake location 52.443°N, 159.579°E

Event Time

  1. 2013-05-21 19:37:41 UTC
  2. 2013-05-22 06:37:41 UTC+11:00 at epicenter
  3. 2013-05-21 14:37:41 UTC-05:00 system time

Location

52.443°N 159.579°E depth=19.1km (11.9mi)

Nearby Cities

  1. 91km (57mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 96km (60mi) SE of Vilyuchinsk, Russia
  3. 115km (71mi) SE of Yelizovo, Russia
  4. 962km (598mi) SE of Magadan, Russia
  5. 2433km (1512mi) NE of Tokyo, Japan

….

M4.9 – 85km E of Petropavlovsk-Kamchatskiy, Russia

 2013-05-22 06:36:37 UTC

Earthquake location 52.991°N, 159.921°E

Event Time

  1. 2013-05-22 06:36:37 UTC
  2. 2013-05-22 18:36:37 UTC+12:00 at epicenter
  3. 2013-05-22 01:36:37 UTC-05:00 system time

Location

52.991°N 159.921°E depth=32.2km (20.0mi)

Nearby Cities

  1. 85km (53mi) E of Petropavlovsk-Kamchatskiy, Russia
  2. 102km (63mi) E of Vilyuchinsk, Russia
  3. 105km (65mi) ESE of Yelizovo, Russia
  4. 923km (574mi) SE of Magadan, Russia
  5. 2491km (1548mi) NNE of Tokyo, Japan

….

M4.6 – 126km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-22 13:49:00 UTC

Earthquake location 52.785°N, 160.486°E

Event Time

  1. 2013-05-22 13:49:00 UTC
  2. 2013-05-23 00:49:00 UTC+11:00 at epicenter
  3. 2013-05-22 08:49:00 UTC-05:00 system time

Location

52.785°N 160.486°E depth=50.5km (31.4mi)

Nearby Cities

  1. 126km (78mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 141km (88mi) E of Vilyuchinsk, Russia
  3. 148km (92mi) ESE of Yelizovo, Russia
  4. 963km (598mi) SE of Magadan, Russia
  5. 2504km (1556mi) NE of Tokyo, Japan

….

M4.6 – 147km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-22 16:56:01 UTC

Earthquake location 52.501°N, 160.644°E

Event Time

  1. 2013-05-22 16:56:01 UTC
  2. 2013-05-23 03:56:01 UTC+11:00 at epicenter
  3. 2013-05-22 11:56:01 UTC-05:00 system time

Location

52.501°N 160.644°E depth=40.7km (25.3mi)

Nearby Cities

  1. 147km (91mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 158km (98mi) ESE of Vilyuchinsk, Russia
  3. 170km (106mi) ESE of Yelizovo, Russia
  4. 995km (618mi) SE of Magadan, Russia
  5. 2492km (1548mi) NE of Tokyo, Japan

….

M4.5 – 62km E of Petropavlovsk-Kamchatskiy, Russia

 2013-05-23 09:57:54 UTC

Earthquake location 53.012°N, 159.581°E

Event Time

  1. 2013-05-23 09:57:54 UTC
  2. 2013-05-23 21:57:54 UTC+12:00 at epicenter
  3. 2013-05-23 04:57:54 UTC-05:00 system time

Location

53.012°N 159.581°E depth=72.5km (45.0mi)

Nearby Cities

  1. 62km (39mi) E of Petropavlovsk-Kamchatskiy, Russia
  2. 79km (49mi) E of Vilyuchinsk, Russia
  3. 82km (51mi) ESE of Yelizovo, Russia
  4. 908km (564mi) SE of Magadan, Russia
  5. 2476km (1539mi) NNE of Tokyo, Japan

….

M4.4 – 77km E of Petropavlovsk-Kamchatskiy, Russia

 2013-05-23 10:47:09 UTC

Earthquake location 52.967°N, 159.796°E

Event Time

  1. 2013-05-23 10:47:09 UTC
  2. 2013-05-23 22:47:09 UTC+12:00 at epicenter
  3. 2013-05-23 05:47:09 UTC-05:00 system time

Location

52.967°N 159.796°E depth=61.9km (38.5mi)

Nearby Cities

  1. 77km (48mi) E of Petropavlovsk-Kamchatskiy, Russia
  2. 93km (58mi) E of Vilyuchinsk, Russia
  3. 98km (61mi) ESE of Yelizovo, Russia
  4. 920km (572mi) SE of Magadan, Russia
  5. 2483km (1543mi) NNE of Tokyo, Japan

Related Links

 

….

Tectonic Summary

Seismotectonics of the Kuril-Kamchatka Arc

The Kuril-Kamchatka arc extends approximately 2,100 km from Hokkaido, Japan, along the Kuril Islands and the Pacific coast of the Kamchatka Peninsula to its intersection with the Aleutian arc near the Commander Islands, Russia. It marks the region where the Pacific plate subducts into the mantle beneath the Okhotsk microplate, part of the larger North America plate. This subduction is responsible for the generation of the Kuril Islands chain, active volcanoes located along the entire arc, and the deep offshore Kuril-Kamchatka trench. Relative to a fixed North America plate, the Pacific plate is moving towards the northwest at a rate that increases from 75 mm/year near the northern end of the arc to 83 mm/year in the south.

Plate motion is predominantly convergent along the Kuril-Kamchatka arc with obliquity increasing towards the southern section of the arc. The subducting Pacific plate is relatively old, particularly adjacent to Kamchatka where its age is greater than 100 Ma. Consequently, the Wadati-Benioff zone is well defined to depths of approximately 650 km. The central section of the arc is comprised of an oceanic island arc system, which differs from the continental arc systems of the northern and southern sections. Oblique convergence in the southern Kuril arc results in the partitioning of stresses into both trench-normal thrust earthquakes and trench-parallel strike-slip earthquakes, and the westward translation of the Kuril forearc. This westward migration of the Kuril forearc currently results in collision between the Kuril arc in the north and the Japan arc in the south, resulting in the deformation and uplift of the Hidaka Mountains in central Hokkaido.

The Kuril-Kamchatka arc is considered one of the most seismically active regions in the world. Deformation of the overriding North America plate generates shallow crustal earthquakes, whereas slip at the subduction zone interface between the Pacific and North America plates generates interplate earthquakes that extend from near the base of the trench to depths of 40 to 60 km. At greater depths, Kuril-Kamchatka arc earthquakes occur within the subducting Pacific plate and can reach depths of approximately 650 km.

This region has frequently experienced large (M>7) earthquakes over the past century. Since 1900, seven great earthquakes (M8.3 or larger) have also occurred along the arc, with mechanisms that include interplate thrust faulting, and intraplate faulting. Damaging tsunamis followed several of the large interplate megathrust earthquakes. These events include the February 3, 1923 M8.4 Kamchatka, the November 6,1958 M8.4 Etorofu, and the September 25, 2003 M8.3 Hokkaido earthquakes. A large M8.5 megathrust earthquake occurred on October 13, 1963 off the coast of Urup, an island along the southern Kuril arc, which generated a large tsunami in the Pacific Ocean and the Sea of Okhotsk, and caused run-up wave heights of up to 4-5 m along the Kuril arc. The largest megathrust earthquake to occur along the entire Kurile-Kamchatka arc in the 20th century was the November 4, 1952 M9.0 event. This earthquake was followed by a devastating tsunami with run-up wave heights as high as 12 m along the coast of Paramushir, a small island immediately south of Kamchatka, causing significant damage to the city of Severo-Kurilsk.

On October 4,1994, a large (M8.3) intraplate event occurred within the subducted oceanic lithosphere off the coast of Shikotan Island causing intense ground shaking, landslides, and a tsunami with run-up heights of up to 10 m on the island.

The most recent megathrust earthquake in the region was the November 15, 2006 M8.3 Kuril Island event, located in the central section of the arc. Prior to this rupture, this part of the subduction zone had been recognized as a seismic gap spanning from the northeastern end of the 1963 rupture zone to the southwestern end of the 1952 rupture. Two months after the 2006 event, a great (M8.1) normal faulting earthquake occurred on January 13, 2007 in the adjacent outer rise region of the Pacific plate. It has been suggested that the 2007 event may have been caused by the stresses generated from the 2006 earthquake.

More information on regional seismicity and tectonics

 

 

….

 

About these ads

Earth Watch Report  -  Earthquakes

 

….

M4.3 – 119km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 10:18:27 UTC

Earthquake location 52.313°N, 159.942°E

Event Time

  1. 2013-05-19 10:18:27 UTC
  2. 2013-05-19 21:18:27 UTC+11:00 at epicenter
  3. 2013-05-19 05:18:27 UTC-05:00 system time

Location

52.313°N 159.942°E depth=61.6km (38.3mi)

Nearby Cities

  1. 119km (74mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 124km (77mi) ESE of Vilyuchinsk, Russia
  3. 143km (89mi) SE of Yelizovo, Russia
  4. 987km (613mi) SE of Magadan, Russia
  5. 2442km (1517mi) NE of Tokyo, Japan

 

….

M4.4 – 205km SE of Nikol’skoye, Russia

2013-05-19 12:24:51 UTC

Earthquake location 54.113°N, 168.571°E

Event Time

  1. 2013-05-19 12:24:51 UTC
  2. 2013-05-19 23:24:51 UTC+11:00 at epicenter
  3. 2013-05-19 07:24:51 UTC-05:00 system time

Location

54.113°N 168.571°E depth=32.2km (20.0mi)

Nearby Cities

  1. 205km (127mi) SE of Nikol’skoye, Russia
  2. 667km (414mi) ENE of Petropavlovsk-Kamchatskiy, Russia
  3. 681km (423mi) ENE of Yelizovo, Russia
  4. 686km (426mi) ENE of Vilyuchinsk, Russia
  5. 3026km (1880mi) NE of Tokyo, Japan

 

….

M4.5 – 118km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 14:45:32 UTC

Earthquake location 52.395°N, 160.036°E

Event Time

  1. 2013-05-19 14:45:32 UTC
  2. 2013-05-20 01:45:32 UTC+11:00 at epicenter
  3. 2013-05-19 09:45:32 UTC-05:00 system time

Location

52.395°N 160.036°E depth=68.4km (42.5mi)

Nearby Cities

  1. 118km (73mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 125km (78mi) ESE of Vilyuchinsk, Russia
  3. 142km (88mi) SE of Yelizovo, Russia
  4. 982km (610mi) SE of Magadan, Russia
  5. 2453km (1524mi) NE of Tokyo, Japan

 

….

M4.7 – 128km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 15:45:23 UTC

Earthquake location 52.360°N, 160.173°E

Event Time

  1. 2013-05-19 15:45:23 UTC
  2. 2013-05-20 02:45:23 UTC+11:00 at epicenter
  3. 2013-05-19 10:45:23 UTC-05:00 system time

Location

52.360°N 160.173°E depth=44.6km (27.7mi)

Nearby Cities

  1. 128km (80mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 135km (84mi) ESE of Vilyuchinsk, Russia
  3. 152km (94mi) SE of Yelizovo, Russia
  4. 991km (616mi) SE of Magadan, Russia
  5. 2457km (1527mi) NE of Tokyo, Japan

 

….

M4.6 – 124km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 15:58:44 UTC

Earthquake location 52.366°N, 160.114°E

Event Time

  1. 2013-05-19 15:58:44 UTC
  2. 2013-05-20 02:58:44 UTC+11:00 at epicenter
  3. 2013-05-19 10:58:44 UTC-05:00 system time

Location

52.366°N 160.114°E depth=61.2km (38.0mi)

Nearby Cities

  1. 124km (77mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 131km (81mi) ESE of Vilyuchinsk, Russia
  3. 148km (92mi) SE of Yelizovo, Russia
  4. 988km (614mi) SE of Magadan, Russia
  5. 2455km (1525mi) NE of Tokyo, Japan

 

….

M5.1 – 132km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 17:44:45 UTC

Earthquake location 52.425°N, 160.318°E

Event Time

  1. 2013-05-19 17:44:45 UTC
  2. 2013-05-20 04:44:45 UTC+11:00 at epicenter
  3. 2013-05-19 12:44:45 UTC-05:00 system time

Location

52.425°N 160.318°E depth=40.3km (25.0mi)

Nearby Cities

  1. 132km (82mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 141km (88mi) ESE of Vilyuchinsk, Russia
  3. 155km (96mi) ESE of Yelizovo, Russia
  4. 990km (615mi) SE of Magadan, Russia
  5. 2469km (1534mi) NE of Tokyo, Japan

 

….

M4.7 – 80km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 17:47:31 UTC

Earthquake location 52.582°N, 159.573°E

Event Time

  1. 2013-05-19 17:47:31 UTC
  2. 2013-05-20 04:47:31 UTC+11:00 at epicenter
  3. 2013-05-19 12:47:31 UTC-05:00 system time

Location

52.582°N 159.573°E depth=59.7km (37.1mi)

Nearby Cities

  1. 80km (50mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 88km (55mi) ESE of Vilyuchinsk, Russia
  3. 104km (65mi) SE of Yelizovo, Russia
  4. 948km (589mi) SE of Magadan, Russia
  5. 2443km (1518mi) NNE of Tokyo, Japan

 

….

M4.8 – 128km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 18:32:58 UTC

Earthquake location 52.271°N, 160.059°E

Event Time

  1. 2013-05-19 18:32:58 UTC
  2. 2013-05-20 05:32:58 UTC+11:00 at epicenter
  3. 2013-05-19 13:32:58 UTC-05:00 system time

Location

52.271°N 160.059°E depth=37.8km (23.5mi)

Nearby Cities

  1. 128km (80mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 134km (83mi) ESE of Vilyuchinsk, Russia
  3. 152km (94mi) SE of Yelizovo, Russia
  4. 995km (618mi) SE of Magadan, Russia
  5. 2445km (1519mi) NE of Tokyo, Japan

 

….

M4.8 – 133km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 18:33:00 UTC

Earthquake location 52.337°N, 160.239°E

Event Time

  1. 2013-05-19 18:33:00 UTC
  2. 2013-05-20 05:33:00 UTC+11:00 at epicenter
  3. 2013-05-19 13:33:00 UTC-05:00 system time

Location

52.337°N 160.239°E depth=53.8km (33.5mi)

Nearby Cities

  1. 133km (83mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 140km (87mi) ESE of Vilyuchinsk, Russia
  3. 157km (98mi) SE of Yelizovo, Russia
  4. 995km (618mi) SE of Magadan, Russia
  5. 2459km (1528mi) NE of Tokyo, Japan

 

….

M5.1 – 123km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 18:41:16 UTC

Earthquake location 52.370°N, 160.103°E

Event Time

  1. 2013-05-19 18:41:16 UTC
  2. 2013-05-20 05:41:16 UTC+11:00 at epicenter
  3. 2013-05-19 13:41:16 UTC-05:00 system time

Location

52.370°N 160.103°E depth=44.1km (27.4mi)

Nearby Cities

  1. 123km (76mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 130km (81mi) ESE of Vilyuchinsk, Russia
  3. 147km (91mi) SE of Yelizovo, Russia
  4. 987km (613mi) SE of Magadan, Russia
  5. 2454km (1525mi) NE of Tokyo, Japan

 

….

M5.9 – 129km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 18:44:10 UTC

Earthquake location 52.278°N, 160.090°E

Event Time

  1. 2013-05-19 18:44:10 UTC
  2. 2013-05-20 05:44:10 UTC+11:00 at epicenter
  3. 2013-05-19 13:44:10 UTC-05:00 system time

Location

52.278°N 160.090°E depth=16.5km (10.3mi)

Nearby Cities

  1. 129km (80mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 135km (84mi) ESE of Vilyuchinsk, Russia
  3. 153km (95mi) SE of Yelizovo, Russia
  4. 995km (618mi) SE of Magadan, Russia
  5. 2447km (1520mi) NE of Tokyo, Japan

 

….

M4.6 – 173km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 19:05:55 UTC

Earthquake location 52.261°N, 160.862°E

Event Time

  1. 2013-05-19 19:05:55 UTC
  2. 2013-05-20 06:05:55 UTC+11:00 at epicenter
  3. 2013-05-19 14:05:55 UTC-05:00 system time

Location

52.261°N 160.862°E depth=23.0km (14.3mi)

Nearby Cities

  1. 173km (107mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 182km (113mi) ESE of Vilyuchinsk, Russia
  3. 196km (122mi) ESE of Yelizovo, Russia
  4. 1026km (638mi) SE of Magadan, Russia
  5. 2486km (1545mi) NE of Tokyo, Japan

 

….

M5.1 – 122km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 19:21:28 UTC

Earthquake location 52.380°N, 160.095°E

Event Time

  1. 2013-05-19 19:21:28 UTC
  2. 2013-05-20 06:21:28 UTC+11:00 at epicenter
  3. 2013-05-19 14:21:28 UTC-05:00 system time

Location

52.380°N 160.095°E depth=54.3km (33.7mi)

Nearby Cities

  1. 122km (76mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 129km (80mi) ESE of Vilyuchinsk, Russia
  3. 146km (91mi) SE of Yelizovo, Russia
  4. 986km (613mi) SE of Magadan, Russia
  5. 2455km (1525mi) NE of Tokyo, Japan

 

….

M4.9 – 123km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 19:37:30 UTC

Earthquake location 52.453°N, 160.198°E

Event Time

  1. 2013-05-19 19:37:30 UTC
  2. 2013-05-20 06:37:30 UTC+11:00 at epicenter
  3. 2013-05-19 14:37:30 UTC-05:00 system time

Location

52.453°N 160.198°E depth=48.6km (30.2mi)

Nearby Cities

  1. 123km (76mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 132km (82mi) ESE of Vilyuchinsk, Russia
  3. 147km (91mi) ESE of Yelizovo, Russia
  4. 983km (611mi) SE of Magadan, Russia
  5. 2465km (1532mi) NE of Tokyo, Japan

 

….

M5.0 – 121km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 19:43:22 UTC

Earthquake location 52.404°N, 160.098°E

Event Time

  1. 2013-05-19 19:43:22 UTC
  2. 2013-05-20 06:43:22 UTC+11:00 at epicenter
  3. 2013-05-19 14:43:22 UTC-05:00 system time

Location

52.404°N 160.098°E depth=52.5km (32.6mi)

Nearby Cities

  1. 121km (75mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 128km (80mi) ESE of Vilyuchinsk, Russia
  3. 144km (89mi) SE of Yelizovo, Russia
  4. 984km (611mi) SE of Magadan, Russia
  5. 2457km (1527mi) NE of Tokyo, Japan

 

….

M5.1 – 121km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 19:51:28 UTC

Earthquake location 52.434°N, 160.143°E

Event Time

  1. 2013-05-19 19:51:28 UTC
  2. 2013-05-20 06:51:28 UTC+11:00 at epicenter
  3. 2013-05-19 14:51:28 UTC-05:00 system time

Location

52.434°N 160.143°E depth=54.1km (33.6mi)

Nearby Cities

  1. 121km (75mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 130km (81mi) ESE of Vilyuchinsk, Russia
  3. 145km (90mi) SE of Yelizovo, Russia
  4. 983km (611mi) SE of Magadan, Russia
  5. 2461km (1529mi) NE of Tokyo, Japan

 

….

M5.1 – 38km SE of Vilyuchinsk, Russia

2013-05-19 19:53:18 UTC

Earthquake location 52.706°N, 158.837°E

Event Time

  1. 2013-05-19 19:53:18 UTC
  2. 2013-05-20 07:53:18 UTC+12:00 at epicenter
  3. 2013-05-19 14:53:18 UTC-05:00 system time

Location

52.706°N 158.837°E depth=92.7km (57.6mi)

Nearby Cities

  1. 38km (24mi) SE of Vilyuchinsk, Russia
  2. 39km (24mi) SSE of Petropavlovsk-Kamchatskiy, Russia
  3. 61km (38mi) SSE of Yelizovo, Russia
  4. 911km (566mi) SE of Magadan, Russia
  5. 2416km (1501mi) NNE of Tokyo, Japan

 

….

M4.6 – 43km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 20:07:02 UTC

Earthquake location 52.834°N, 159.200°E

Event Time

  1. 2013-05-19 20:07:02 UTC
  2. 2013-05-20 07:07:02 UTC+11:00 at epicenter
  3. 2013-05-19 15:07:02 UTC-05:00 system time

Location

52.834°N 159.200°E depth=86.2km (53.6mi)

Nearby Cities

  1. 43km (27mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 54km (34mi) E of Vilyuchinsk, Russia
  3. 67km (42mi) SE of Yelizovo, Russia
  4. 911km (566mi) SE of Magadan, Russia
  5. 2444km (1519mi) NNE of Tokyo, Japan

 

….

M5.1 – 115km SE of Petropavlovsk-Kamchatskiy, Russia

2013-05-19 20:20:12 UTC

Earthquake location 52.410°N, 159.993°E

Event Time

  1. 2013-05-19 20:20:12 UTC
  2. 2013-05-20 07:20:12 UTC+11:00 at epicenter
  3. 2013-05-19 15:20:12 UTC-05:00 system time

Location

52.410°N 159.993°E depth=43.6km (27.1mi)

Nearby Cities

  1. 115km (71mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 122km (76mi) ESE of Vilyuchinsk, Russia
  3. 138km (86mi) SE of Yelizovo, Russia
  4. 980km (609mi) SE of Magadan, Russia
  5. 2452km (1524mi) NE of Tokyo, Japan

 

….

M5.1 – 124km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 21:05:17 UTC

Earthquake location 52.352°N, 160.088°E

Event Time

  1. 2013-05-19 21:05:17 UTC
  2. 2013-05-20 08:05:17 UTC+11:00 at epicenter
  3. 2013-05-19 16:05:17 UTC-05:00 system time

Location

52.352°N 160.088°E depth=43.3km (26.9mi)

Nearby Cities

  1. 124km (77mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 130km (81mi) ESE of Vilyuchinsk, Russia
  3. 148km (92mi) SE of Yelizovo, Russia
  4. 988km (614mi) SE of Magadan, Russia
  5. 2452km (1524mi) NE of Tokyo, Japan

 

….

M4.8 – 126km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 21:12:55 UTC

Earthquake location 52.267°N, 160.010°E

Event Time

  1. 2013-05-19 21:12:55 UTC
  2. 2013-05-20 08:12:55 UTC+11:00 at epicenter
  3. 2013-05-19 16:12:55 UTC-05:00 system time

Location

52.267°N 160.010°E depth=58.0km (36.1mi)

Nearby Cities

  1. 126km (78mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 131km (81mi) ESE of Vilyuchinsk, Russia
  3. 150km (93mi) SE of Yelizovo, Russia
  4. 994km (618mi) SE of Magadan, Russia
  5. 2442km (1517mi) NE of Tokyo, Japan

 

….

M5.0 – 130km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 22:38:50 UTC

Earthquake location 52.359°N, 160.217°E

Event Time

  1. 2013-05-19 22:38:50 UTC
  2. 2013-05-20 09:38:50 UTC+11:00 at epicenter
  3. 2013-05-19 17:38:50 UTC-05:00 system time

Location

52.359°N 160.217°E depth=40.1km (24.9mi)

Nearby Cities

  1. 130km (81mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 138km (86mi) ESE of Vilyuchinsk, Russia
  3. 154km (96mi) SE of Yelizovo, Russia
  4. 992km (616mi) SE of Magadan, Russia
  5. 2459km (1528mi) NE of Tokyo, Japan

 

….

M4.5 – 45km ESE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 23:33:54 UTC

Earthquake location 52.886°N, 159.265°E

Event Time

  1. 2013-05-19 23:33:54 UTC
  2. 2013-05-20 10:33:54 UTC+11:00 at epicenter
  3. 2013-05-19 18:33:54 UTC-05:00 system time

Location

52.886°N 159.265°E depth=78.2km (48.6mi)

Nearby Cities

  1. 45km (28mi) ESE of Petropavlovsk-Kamchatskiy, Russia
  2. 58km (36mi) E of Vilyuchinsk, Russia
  3. 68km (42mi) ESE of Yelizovo, Russia
  4. 908km (564mi) SE of Magadan, Russia
  5. 2451km (1523mi) NNE of Tokyo, Japan

 

….

M5.1 – 45km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 23:50:24 UTC

Earthquake location 52.748°N, 159.112°E

Event Time

  1. 2013-05-19 23:50:24 UTC
  2. 2013-05-20 10:50:24 UTC+11:00 at epicenter
  3. 2013-05-19 18:50:24 UTC-05:00 system time

Location

52.748°N 159.112°E depth=70.2km (43.6mi)

Nearby Cities

  1. 45km (28mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 51km (32mi) ESE of Vilyuchinsk, Russia
  3. 69km (43mi) SE of Yelizovo, Russia
  4. 916km (569mi) SE of Magadan, Russia
  5. 2433km (1512mi) NNE of Tokyo, Japan

 

….

M5.2 – 117km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 23:51:35 UTC

Earthquake location 52.365°N, 159.987°E

Event Time

  1. 2013-05-19 23:51:35 UTC
  2. 2013-05-20 10:51:35 UTC+11:00 at epicenter
  3. 2013-05-19 18:51:35 UTC-05:00 system time

Location

52.365°N 159.987°E depth=49.7km (30.9mi)

Nearby Cities

  1. 117km (73mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 124km (77mi) ESE of Vilyuchinsk, Russia
  3. 141km (88mi) SE of Yelizovo, Russia
  4. 984km (611mi) SE of Magadan, Russia
  5. 2448km (1521mi) NE of Tokyo, Japan

 

….

M5.0 – 114km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-19 23:58:15 UTC

Earthquake location 52.383°N, 159.952°E

Event Time

  1. 2013-05-19 23:58:15 UTC
  2. 2013-05-20 10:58:15 UTC+11:00 at epicenter
  3. 2013-05-19 18:58:15 UTC-05:00 system time

Location

52.383°N 159.952°E depth=58.8km (36.5mi)

Nearby Cities

  1. 114km (71mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 121km (75mi) ESE of Vilyuchinsk, Russia
  3. 138km (86mi) SE of Yelizovo, Russia
  4. 981km (610mi) SE of Magadan, Russia
  5. 2448km (1521mi) NE of Tokyo, Japan

 

 

….

 

 

 

 

Earth Watch Report  -  Earthquake

….

M4.5 – 249km SSW of Severo-Kuril’sk, Russia

 2013-05-13 15:46:45 UTC

Earthquake location 48.586°N, 154.872°E

Event Time

  1. 2013-05-13 15:46:45 UTC
  2. 2013-05-14 01:46:45 UTC+10:00 at epicenter
  3. 2013-05-13 10:46:45 UTC-05:00 system time

Location

48.586°N 154.872°E depth=54.1km (33.6mi)

Nearby Cities

  1. 249km (155mi) SSW of Severo-Kuril’sk, Russia
  2. 543km (337mi) SSW of Vilyuchinsk, Russia
  3. 562km (349mi) SSW of Petropavlovsk-Kamchatskiy, Russia
  4. 568km (353mi) SSW of Yelizovo, Russia
  5. 1897km (1179mi) NE of Tokyo, Japan

….

M4.2 – 189km S of Ust’-Kamchatsk Staryy, Russia

2013-05-13 17:23:40 UTC

Earthquake location 54.556°N, 161.938°E

Event Time

  1. 2013-05-13 17:23:40 UTC
  2. 2013-05-14 05:23:40 UTC+12:00 at epicenter
  3. 2013-05-13 12:23:40 UTC-05:00 system time

Location

54.556°N 161.938°E depth=51.2km (31.8mi)

Nearby Cities

  1. 189km (117mi) S of Ust’-Kamchatsk Staryy, Russia
  2. 274km (170mi) NE of Petropavlovsk-Kamchatskiy, Russia
  3. 279km (173mi) NE of Yelizovo, Russia
  4. 295km (183mi) NE of Vilyuchinsk, Russia
  5. 2707km (1682mi) NNE of Tokyo, Japan

….

M5.3 – 271km ENE of Kuril’sk, Russia

2013-05-15 13:51:43 UTC

Earthquake location 46.148°N, 151.117°E

Event Time

  1. 2013-05-15 13:51:43 UTC
  2. 2013-05-15 23:51:43 UTC+10:00 at epicenter
  3. 2013-05-15 08:51:43 UTC-05:00 system time

Location

46.148°N 151.117°E depth=119.8km (74.5mi)

Nearby Cities

  1. 271km (168mi) ENE of Kuril’sk, Russia
  2. 539km (335mi) NE of Nemuro, Japan
  3. 547km (340mi) ENE of Shibetsu, Japan
  4. 588km (365mi) ENE of Abashiri, Japan
  5. 1505km (935mi) NE of Tokyo, Japan

….

M4.7 – 124km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-16 09:23:40 UTC

Earthquake location 52.322°N, 160.052°E

Event Time

  1. 2013-05-16 09:23:40 UTC
  2. 2013-05-16 20:23:40 UTC+11:00 at epicenter
  3. 2013-05-16 04:23:40 UTC-05:00 system time

Location

52.322°N 160.052°E depth=60.8km (37.8mi)

Nearby Cities

  1. 124km (77mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 130km (81mi) ESE of Vilyuchinsk, Russia
  3. 148km (92mi) SE of Yelizovo, Russia
  4. 990km (615mi) SE of Magadan, Russia
  5. 2448km (1521mi) NE of Tokyo, Japan

….

M4.6 – 133km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-16 10:50:10 UTC

Earthquake location 52.293°N, 160.192°E

Event Time

  1. 2013-05-16 10:50:10 UTC
  2. 2013-05-16 21:50:10 UTC+11:00 at epicenter
  3. 2013-05-16 05:50:10 UTC-05:00 system time

Location

52.293°N 160.192°E depth=57.4km (35.6mi)

Nearby Cities

  1. 133km (83mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 140km (87mi) ESE of Vilyuchinsk, Russia
  3. 157km (98mi) SE of Yelizovo, Russia
  4. 998km (620mi) SE of Magadan, Russia
  5. 2453km (1524mi) NE of Tokyo, Japan

….

M4.4 – 110km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-18 03:44:03 UTC

Earthquake location 52.375°N, 159.851°E

Event Time

  1. 2013-05-18 03:44:03 UTC
  2. 2013-05-18 14:44:03 UTC+11:00 at epicenter
  3. 2013-05-17 22:44:03 UTC-05:00 system time

Location

52.375°N 159.851°E depth=64.1km (39.8mi)

Nearby Cities

  1. 110km (68mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 115km (71mi) ESE of Vilyuchinsk, Russia
  3. 134km (83mi) SE of Yelizovo, Russia
  4. 978km (608mi) SE of Magadan, Russia
  5. 2442km (1517mi) NE of Tokyo, Japan

…..

M4.4 – 146km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-18 07:26:23 UTC

Earthquake location 52.198°N, 160.302°E

Event Time

  1. 2013-05-18 07:26:23 UTC
  2. 2013-05-18 18:26:23 UTC+11:00 at epicenter
  3. 2013-05-18 02:26:23 UTC-05:00 system time

Location

52.198°N 160.302°E depth=40.0km (24.9mi)

Nearby Cities

  1. 146km (91mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 152km (94mi) ESE of Vilyuchinsk, Russia
  3. 170km (106mi) SE of Yelizovo, Russia
  4. 1011km (628mi) SE of Magadan, Russia
  5. 2452km (1524mi) NE of Tokyo, Japan

….

M4.9 – 45km SSE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-18 22:39:46 UTC

Earthquake location 52.672°N, 158.942°E

Event Time

  1. 2013-05-18 22:39:46 UTC
  2. 2013-05-19 09:39:46 UTC+11:00 at epicenter
  3. 2013-05-18 17:39:46 UTC-05:00 system time

Location

52.672°N 158.942°E depth=73.8km (45.8mi)

Nearby Cities

  1. 45km (28mi) SSE of Petropavlovsk-Kamchatskiy, Russia
  2. 46km (29mi) SE of Vilyuchinsk, Russia
  3. 68km (42mi) SSE of Yelizovo, Russia
  4. 918km (570mi) SE of Magadan, Russia
  5. 2419km (1503mi) NNE of Tokyo, Japan

….

M4.7 – 23km SE of Petropavlovsk-Kamchatskiy, Russia

 2013-05-18 23:29:31 UTC

 

Earthquake location 52.883°N, 158.876°E

Event Time

  1. 2013-05-18 23:29:31 UTC
  2. 2013-05-19 11:29:31 UTC+12:00 at epicenter
  3. 2013-05-18 18:29:31 UTC-05:00 system time

Location

52.883°N 158.876°E depth=85.3km (53.0mi)

Nearby Cities

  1. 23km (14mi) SE of Petropavlovsk-Kamchatskiy, Russia
  2. 32km (20mi) E of Vilyuchinsk, Russia
  3. 47km (29mi) SE of Yelizovo, Russia
  4. 895km (556mi) SE of Magadan, Russia
  5. 2432km (1511mi) NNE of Tokyo, Japan

….

Tectonic Summary

Seismotectonics of the Kuril-Kamchatka Arc

The Kuril-Kamchatka arc extends approximately 2,100 km from Hokkaido, Japan, along the Kuril Islands and the Pacific coast of the Kamchatka Peninsula to its intersection with the Aleutian arc near the Commander Islands, Russia. It marks the region where the Pacific plate subducts into the mantle beneath the Okhotsk microplate, part of the larger North America plate. This subduction is responsible for the generation of the Kuril Islands chain, active volcanoes located along the entire arc, and the deep offshore Kuril-Kamchatka trench. Relative to a fixed North America plate, the Pacific plate is moving towards the northwest at a rate that increases from 75 mm/year near the northern end of the arc to 83 mm/year in the south.

Plate motion is predominantly convergent along the Kuril-Kamchatka arc with obliquity increasing towards the southern section of the arc. The subducting Pacific plate is relatively old, particularly adjacent to Kamchatka where its age is greater than 100 Ma. Consequently, the Wadati-Benioff zone is well defined to depths of approximately 650 km. The central section of the arc is comprised of an oceanic island arc system, which differs from the continental arc systems of the northern and southern sections. Oblique convergence in the southern Kuril arc results in the partitioning of stresses into both trench-normal thrust earthquakes and trench-parallel strike-slip earthquakes, and the westward translation of the Kuril forearc. This westward migration of the Kuril forearc currently results in collision between the Kuril arc in the north and the Japan arc in the south, resulting in the deformation and uplift of the Hidaka Mountains in central Hokkaido.

The Kuril-Kamchatka arc is considered one of the most seismically active regions in the world. Deformation of the overriding North America plate generates shallow crustal earthquakes, whereas slip at the subduction zone interface between the Pacific and North America plates generates interplate earthquakes that extend from near the base of the trench to depths of 40 to 60 km. At greater depths, Kuril-Kamchatka arc earthquakes occur within the subducting Pacific plate and can reach depths of approximately 650 km.

This region has frequently experienced large (M>7) earthquakes over the past century. Since 1900, seven great earthquakes (M8.3 or larger) have also occurred along the arc, with mechanisms that include interplate thrust faulting, and intraplate faulting. Damaging tsunamis followed several of the large interplate megathrust earthquakes. These events include the February 3, 1923 M8.4 Kamchatka, the November 6,1958 M8.4 Etorofu, and the September 25, 2003 M8.3 Hokkaido earthquakes. A large M8.5 megathrust earthquake occurred on October 13, 1963 off the coast of Urup, an island along the southern Kuril arc, which generated a large tsunami in the Pacific Ocean and the Sea of Okhotsk, and caused run-up wave heights of up to 4-5 m along the Kuril arc. The largest megathrust earthquake to occur along the entire Kurile-Kamchatka arc in the 20th century was the November 4, 1952 M9.0 event. This earthquake was followed by a devastating tsunami with run-up wave heights as high as 12 m along the coast of Paramushir, a small island immediately south of Kamchatka, causing significant damage to the city of Severo-Kurilsk.

On October 4,1994, a large (M8.3) intraplate event occurred within the subducted oceanic lithosphere off the coast of Shikotan Island causing intense ground shaking, landslides, and a tsunami with run-up heights of up to 10 m on the island.

The most recent megathrust earthquake in the region was the November 15, 2006 M8.3 Kuril Island event, located in the central section of the arc. Prior to this rupture, this part of the subduction zone had been recognized as a seismic gap spanning from the northeastern end of the 1963 rupture zone to the southwestern end of the 1952 rupture. Two months after the 2006 event, a great (M8.1) normal faulting earthquake occurred on January 13, 2007 in the adjacent outer rise region of the Pacific plate. It has been suggested that the 2007 event may have been caused by the stresses generated from the 2006 earthquake.

More information on regional seismicity and tectonics

….

H7N9 bird flu found to spread through the air

Virus can also infect pigs, say HKU researchers, who warn officials to maintain tight scrutiny even though threat seems under control

Friday, 24 May, 2013, 5:50am


The H7N9 bird flu virus can be transmitted not only through close contact but by airborne exposure, a team at the University of Hong Kong found after extensive laboratory experiments.

Though the virus appears to have been brought under control recently, the researchers urged the Hong Kong authorities to maintain strict surveillance, which should include not only poultry but humans and pigs.

“We also found that the virus can infect pigs, which was not previously known,” said Dr Maria Zhu Huachen, a research assistant professor at HKU’s School of Public Health.

There have been 131 confirmed human infections, with 36 deaths, the World Health Organisation said. All but one of the cases was on the mainland. The virus appears to have been brought under control largely due to restrictions at bird markets and there have been no new confirmed cases since May 8.

But Zhu said that although there was no evidence of sustained human-to-human transmission, their study provided evidence that H7N9 was infectious and transmissible in mammals.

In the study, to be published today in the journal Science, ferrets were used to evaluate the infectivity of H7N9. It was found the virus could spread through the air, from one cage to another, albeit less efficiently.

Inoculated ferrets were infected before the appearance of most clinical symptoms. This means there may be more cases than have been detected or reported.

We also found that the virus can infect pigs, which was not previously known … People may be transmitting the virus before they even know that they’ve got it
Dr Maria Zhu Huachen, HKU’s School of Public Health

“People may be transmitting the virus before they even know that they’ve got it,” Zhu said.

Additional tests using pigs, a major host of influenza viruses, showed that they could also get infected with H7N9. Zhu warned that H7N9 may combine with pig viruses to generate new variants.

On a more positive note, it was found that the virus is relatively mild.

“Most of the fatal H7N9 cases had underlying medical conditions, so there are probably some other factors that contribute to this kind of fatality,” Zhu said.

 

Read Full Article Here

 

*******************************************************************************

 

Scientists create hybrid flu that can go airborne

H5N1 virus with genes from H1N1 can spread through the air between mammals.

02 May 2013

Researchers have crossed two strains of avian flu virus to create one that can be transmitted through the air — and possibly settle on the cilia of lung cells as in this conceptual image.

KARSTEN SCHNEIDER/SCIENCE PHOTO LIBRARY

As the world is transfixed by a new H7N9 bird flu virus spreading through China, a study reminds us that a different avian influenza — H5N1 — still poses a pandemic threat.

A team of scientists in China has created hybrid viruses by mixing genes from H5N1 and the H1N1 strain behind the 2009 swine flu pandemic, and showed that some of the hybrids can spread through the air between guinea pigs. The results are published in Science1.

Flu hybrids can arise naturally when two viral strains infect the same cell and exchange genes. This process, known as reassortment, produced the strains responsible for at least three past flu pandemics, including the one in 2009.

There is no evidence that H5N1 and H1N1 have reassorted naturally yet, but they have many opportunities to do so. The viruses overlap both in their geographical range and in the species they infect, and although H5N1 tends mostly to swap genes in its own lineage, the pandemic H1N1 strain seems to be particularly prone to reassortment.

“If these mammalian-transmissible H5N1 viruses are generated in nature, a pandemic will be highly likely,” says Hualan Chen, a virologist at the Harbin Veterinary Research Institute of the Chinese Academy of Sciences, who led the study.

“It’s remarkable work and clearly shows how the continued circulation of H5N1 strains in Asia and Egypt continues to pose a very real threat for human and animal health,” says Jeremy Farrar, director of the Oxford University Clinical Research Unit in Ho Chi Minh City, Vietnam.

Flu fears

Chen’s results are likely to reignite the controversy that plagued the flu community last year, when two groups found that H5N1 could go airborne if it carried certain mutations in a gene that produced a protein called haemagglutinin (HA)2, 3. Following heated debate over biosecurity issues raised by the work, the flu community instigated a voluntary year-long moratorium on research that would produce further transmissible strains. Chen’s experiments were all finished before the hiatus came into effect, but more work of this nature can be expected now that the moratorium has been lifted.

There  seem to be   alot  more  questions and dead bodies than real answers or connections  in the  search to  verify  the  Official  version of the truth. 

I wonder how far  the  rabbit hole really  goes …….

~Desert Rose~

****************************************************************************************

Ибрагим Тодашев

The wife of Ibrahim Todashev who was killed Wednesday during a scandalous FBI interrogation in Florida says she was sure her husband participated neither in April’s Boston Marathon bombings nor in a 2011 triple murder that US law-enforcement agents now suggest involved her late husband. “Everything was a setup”, she said.

Reni Manukyan, a 24-year-old assistant hotel-housekeeping manager who married Ibragim Todashev in July 2010, says agents from the Federal Bureau of Investigation arrived at her house in Atlanta and her mom’s house in Savannah, Ga., late Tuesday night, the same time they started questioning her husband at his home in Orlando.

An interesting detail that Ms Manukyan supposedly did not know about was that Todashev had a girlfriend named Tatiana Gruzdeva (this may be her Facebook page), who was arrested by ICE on May 16 and is currently in custody for immigration violations. Whether it was a coincidence or a pre-planned detention by the FBI is debatable.

Ms Manukyan, an Armenian who moved to the US in early 2006, met her husband in 2010 through a mutual friend in Boston. Even though she and Todashev were separated since last November they remained good friends. Up until Tuesday the two had been in regular contact and Ms Manukian even partly supported her husband financially through their joint bank account. The grieving widow last saw her husband last week when he came to visit her in Atlanta.

Judging by Ms Manukyan’s account in one of the popular European social networks she spent past few months in her home-country Armenia where she stayed from March 24 till April 6 visiting her brother and mother, who, allegedly serves in Armenian army. Later on Ms Manukyan went to Russia’s Volgograd to attend her good friend’s wedding and on April 22 she returned back to the US where she is now staying. On March 23 the widow posted a message on her wall saying: “killing my husband Ibragim was another prove that everything is set up about Tsarnaevs brothers as well”.

According to Ms Manukyan, FBI agents who came to question her primarily asked about alleged Boston Marathon bomber Tamerlan Tsarnaev and her husband’s relationship with him. The widow claimed she was never asked about 2011 Waltham massacre in which three victims—25-year-old Brendan Mess, 31-year-old Erik Weissman and 37-year-old Raphael Teken—were found dead with their throats slit and bodies covered in marijuana and cash.

“They never, ever—in all the interviews that I had and all the interviews that he had—never did they mention anything about a murder,” said Ms Manukyan. “Everything was about the bombing and about him knowing Tamerlan. They would show me a picture of Tamerlan or Tamerlan’s wife or some other guys that I haven’t a clue who they are, but nothing about a murder—nothing ever.”

She also added that even if she was asked about 2011 incident she would have found it very difficult to believe that her husband was involved because he did not have any American associates. Instead, he was mainly friends with other immigrants who moved to the US from Russia. Ms Manukyan also said that given that Todashev did “not do drugs, he did not smoke, and didn’t even drink alcohol,” she finds it extremely daunting that her husband could have been accused of Waltham massacre.

Todashev’s close friend and former roommate Khusen Taramov also claimed Todashov was never questioned about the Waltham murders. “We told each other everything, everything,” Taramov said. “He never said anything about any murder and they never asked him anything about that. Just about the bombings and Tsarnaev.”

Ms Manukyan also claimed she did not believe Todashev could have pulled a knife on the law-enforcement agents. She asserted that her husband had never had a pocket knife and that during interrogation he would have been very far from the kitchen to grab a kitchen knife. The widow also noted that Todashev was recovering from a knee surgery and was still learning to walk properly which made it senseless for him to attack an FBI agent.

Todashev’s father, Abdulbaki Todashev, concurred that his son was disabled by knee surgery earlier this year.

As for Todashev’s relationship with Tsarnaev, Ms Manukyan said that the men were briefly acquainted because they shared some things in common: both came from one country, both were interested in martial arts, and both were living in the Boston area. “They had a chat because they were from the same country,” she said. “It was a small community. They all knew each other.” “I believe Tamerlan only called him once and asked him how he was doing after the surgery,” she claimed.

*****************************************************************************************

Wife of man killed by FBI agent says he was never questioned about Waltham triple murder

 05/23/2013 2:44 PM

By Wesley Lowery, Globe Staff

ORLANDO — The wife and best friend of the Chechen man shot and killed here by an FBI agent on Wednesday insisted today that authorities never questioned him, or them, prior to the fatal confrontation, about an unsolved triple slaying in Waltham, Mass., just outside of Boston.

Ibragim Todashev, 27, a friend of Boston Marathon bombing suspect Tamerlan Tsarnaev, was shot and killed after allegedly attacking an FBI agent who was interviewing him along with two Massachusetts State Police troopers.

Todashev acknowledged a role in the 2011 triple homicide when he attacked the agent early Wednesday with a blade, the Globe reported today. Todashev was not considered a suspect in the Marathon terror attacks, law enforcement officials told the Globe.

Todashev’s wife, Reni Manukyan, said her husband could not have been involved in the Waltham murders, and that the subject had never been brought up in FBI interviews.

Manukyan, 24, said today that Todashev told her that his previous interviews with law enforcement dealt with just two subjects: the Boston Marathon bombing and Tamerlan Tsarnaev.

Manukyan, who separated from Todashev in November, said that in her own interview with the FBI, conducted in Georgia where she lives, the unsolved murders were never mentioned.

“It never, ever came up,” she said, wiping tears from beneath her sunglasses. “Everything they asked was about the bombing.”

Middlesex District Attorney Marian T. Ryan issued a statement today defending the pace of the Waltham investigation, a statement that also made clear Ryan’s office believes it is constrained by ethics rules for lawyers from publicly discussing it.

“While we can not discuss details pertaining to the investigation, including evidence, suspects or witnesses, this office and its law enforcement partners have conducted a thorough, far-reaching investigation beginning in 2011 when this horrific crime occurred,’’ Ryan said in the statement. “This investigation has not concluded and is by no means closed.’’

Read Full Article and  Wach Video Here

******************************************************************************************

Image Source

FBI agent in charge says both bombs in black backpacks – photo is of black backpack – but Dzhokhar Tsarnaev’s is white!

Explosive News: Dzokhar Tsarnaev’s back-pack was photo-shopped out

The photo and the FBI lead investigator says that both bombs were in black backpacks  –  see below  — BUT TSARNAEV’S BACKPACK IN EVERY SHOT OF IT  IS WHITE — except the shot released by the FBI to identify the “suspects.”

Don’t underestimate the importance of this.

Will someone watching a lot of news please tell me how this is being explained?

Details and photos establishing this follow:

At 2:49 p.m. EDT (18:49 UTC), about two hours after the winner crossed the finish line,[13] but with more than 5,700 runners yet to finish,[14] two bombs detonated on Boylston Street near Copley Square about 180 yards (170 m) apart,[15][16] just before the finish line.[11] The first exploded outside Marathon Sports at 671–673 Boylston Street at 2:49:43 p.m. EDT.[17] At the time of the first explosion, the race clock at the finish line showed 04:09:43.[18] The second bomb was located one block farther west at 755 Boylston Street and exploded at 2:49:57 p.m. EDT,[13][19] about 13 seconds after the first one.[3] fill the sidewalk behind race barricades after the explosions blow metal pellets and nails into victims’ legs. Race tents become makeshift trauma units.

The Federal Bureau of Investigation led the investigation, assisted by the Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF), the Central Intelligence Agency (CIA), the National Counterterrorism Center (NCTC), and the Drug Enforcement Administration (DEA);[57] treating the bombings as a terrorist attack and naming two alleged perpetrators officially as suspects.[42][58]

At the site of the explosion, investigators found shrapnel that included bits of metal, nails, and bearing balls,[35] as well as black nylon pieces from a backpack.[61] The lid of a Fagor-brand[62] pressure cooker was found on a nearby rooftop.[63] Investigators also found the remains of an electronic circuit board and wiring, possibly used as a timer of the bomb.[35] Rep. Mike McCaul said “most likely, gunpowder was used in the devices”.[64] All evidence was sent to the FBI Laboratory for analysis.[65] Both of the improvised explosive devices are reported to be pressure cooker bombs.[65][66]

Investigators believe the bombs were hidden in black nylon backpacks and housed inside sealable metal pots called pressure cookers. Pressure cooker bombs can help boost the power of relatively small devices by briefly constraining the blast. And when the cookers do explode, they can add large chunks of metal to the shrapnel spray. The IEDs have been popular with terrorists. Al Qaeda published a how-to recipe in an online Jihadi magazine. Several of the bombs were used in the 2006 attack on trains in Mumbai, India.

At a news conference late Tuesday afternoon in Boston, FBI Special Agent in Charge, Richard Deslauriers, indicated that the range of suspect and motive is “wide open,” and that the investigation is still in its “infancy.” He also mentioned that the FBI had received about 2,000 tips as of noon as agents looked for any photographic or video evidence from witnesses.

exploded bag

Deslauriers also said that both explosive devices appears to have been placed in a black nylon bag or backpack. A law enforcement source told CBS News senior investigative producer Pat Milton that investigators also found pieces of an electronic circuit board possibly indicating a timer was used in the detonation of the bomb.

Dick Eastman note:  The FBI released the ONLY picture in which you cannot tell that Dzhokhar Tsarnaev is carrying a white backpack over his shoulder!!!!  Now we understand their selectivity and their reluctance to show more pictures to aid the manhunt.

blackbag2

Without an arrest three days after the blasts, investigators at about 6 p.m. publicly release images of the two alleged bombing suspects taken from a Lord & Taylor department store surveillance camera.

The man who became known as “Suspect No. 1″ is wearing a black baseball cap, and “Suspect No. 2″ has a white baseball cap on backwards and is carrying a black backpack. Authorities say they suspect the dark backpack was left in front of the Forum Restaurant on Boylston Street on Monday and then exploded — the second blast.
  Read Full Article Here

***************************************************************************************

Live Leak

2 FBI Agents Involved in Dzhokhar Tsarnaev’s Arrest “FALL” Out of Helicopter and Die

Remember that scene in Scarface?

2 FBI Agents Involved in Dzhokhar Tsarnaev’s Arrest “FALL” Out of Helicopter and Die

Remember that scene in Scarface?

Two members of the FBI’s elite counterterrorism unit died Friday while practicing how to quickly drop from a helicopter to a ship using a rope, the FBI announced Monday in a statement.

The statement gave few details regarding the deaths of Special Agents Christopher Lorek and Stephen Shaw, other than to say the helicopter encountered unspecified difficulties and the agents fell a “significant distance.”

Last month, the team was involved in the arrest of Dzhokhar Tsarnaev, a suspect in the Boston Marathon bombings……

Read Full Article Here
****************************************************************************************

2 Agents From Team Involved in Tsarnaev’s Arrest Fall Out of Helicopter and Die

2013 05 23
By Elizabeth Leafloor | Red Ice Creations

Details are few at this point, but it’s being reported via several media outlets that two members of the special FBI Hostage Rescue Team (involved in arresting 19-year-old Dzhokhar Tsarnaev) have died after “falling from a helicopter” into the ocean.

The Hostage Rescue Team is “part of the Tactical Support Branch of the FBI’s Critical Incident Response Group. It is based at the FBI Academy in Quantico, Virginia.” Source

The Virginian-Pilot reports on the May 17 deaths:

The statement gave few details regarding the deaths of Special Agents Christopher Lorek and Stephen Shaw, other than to say the helicopter encountered unspecified difficulties and the agents fell a “significant distance.”

A law enforcement source told The Pilot the incident happened about 12 nautical miles off the coast of Virginia Beach. The official blamed bad weather for the incident and said the agents – members of the FBI’s Hostage Rescue Team, based in Quantico – fell into the water. The official said he believed the agents died as a result of the impact rather than drowning.

Glenn McBride, a spokesman for the state medical examiner’s office, said it could be months before his staff can release a final cause and manner of death for the two agents. He said they must wait for the results of routine toxicology tests.

[...]

In interviews Monday, the founder of the Hostage Rescue Team and other former special agents called the unit “elite” while outlining the difficult training exercises members must endure.

“It’s the most rigorous training regiment in law enforcement, probably in the world,” said Danny Coulson, a former deputy assistant director of the FBI who started the team 30 years ago and served as its first commander. “They have to be able to do any mission, at any time.”

Among other things, members of the Hostage Rescue Team are trained to rappel from helicopters, scuba dive and use explosives to break down doors and walls. When needed, the team can deploy within four hours to anywhere in the U.S.

“It sounds risky, and it absolutely is,” Coulson said. “They have the same skill sets as SEAL Team 6 and Delta Force.”

In all, the team has responded to more than 850 incidents involving terrorism, violent crimes and foreign counterintelligence, according to the FBI’s website.

Last month, the team was involved in the arrest of Dzhokhar Tsarnaev, a suspect in the Boston Marathon bombings. And in February, it rescued a 5-year-old boy held hostage for six days in an underground bunker in Alabama.

“Whenever things go really wrong, the FBI calls in the Hostage Rescue Team. It’s the government’s 911,” Coulson said.

Read Full Article Here
****************************************************************************************

The Paducah Gaseous Diffusion Plant in Paducah, Kentucky, is the only U.S.-owned uranium enrichment
facility in the United States.

Paducah Gaseous Diffusion Plant | usec.com  Home Page

USEC Home Page

***********************************************************************************************************

EcoWatch: Uniting the voice of the grassroots environmental movement

Countdown to Nuclear Ruin at Paducah

May 22, 2013

By Geoffrey Sea

Disaster is about to strike in western Kentucky, a full-blown nuclear catastrophe involving hundreds of tons of enriched uranium tainted with plutonium, technetium, arsenic, beryllium and a toxic chemical brew. But this nuke calamity will be no fluke. It’s been foreseen, planned, even programmed, the result of an atomic extortion game played out between the U.S. Department of Energy (DOE) and the most failed American experiment in privatization, the company that has run the Paducah plant into the poisoned ground, USEC Inc.

As now scheduled, main power to the gargantuan gaseous diffusion uranium plant at Paducah, Kentucky, will be cut at midnight on May 31, just nine days from now—cut because USEC has terminated its power contract with TVA as of that time [“USEC Ceases Buying Power,” Paducah Sun, April 19, page 1] and because DOE can’t pick up the bill.

DOE is five months away from the start of 2014 spending authority, needed to fund clean power-down at Paducah. Meanwhile, USEC’s total market capitalization has declined to about $45 million, not enough to meet minimum listing requirements for the New York Stock Exchange, pay off the company’s staggering debts or retain its operating licenses under financial capacity requirements of the Nuclear Regulatory Commission.

The Paducah plant cannot legally stay open, and it can’t safely be shut down—a lovely metaphor for the end of the Atomic Age and a perfect nightmare for the people of Kentucky.

Dirty Power-Down

If the main power to the diffusion cascade is cut as now may be unavoidable, the uranium hexafluoride gas inside thousands of miles of piping and process equipment will crystallize, creating a very costly gigantic hunk of junk as a bequest to future generations, delaying site cleanup for many decades and risking nuclear criticality problems that remain unstudied. Unlike gaseous uranium that can be flushed from pipes with relative ease, crystallized uranium may need to be chiseled out manually, adding greatly to occupational hazards.

The gaseous diffusion plant at Oak Ridge, TN, was powered-down dirty in 1985, in a safer situation because the Oak Ridge plant did not have near the level of transuranic contaminants found at Paducah. The Oak Ridge catastrophe left a poisonous site that still awaits cleanup a quarter-century later, and an echo chamber of political promises that such a stupid move would never be made again. But that was before the privatization of USEC.

Could a dirty power-down at Paducah—where recycled and reprocessed uranium contaminated with plutonium and other transuranic elements was added in massive quantities—result in “slow-cooker” critical mass formations inside the process equipment?

No one really knows.

Everybody does know that the Paducah plant is about to close. Its technology is Jurassic, requiring about ten times the energy of competing uranium enrichment methods around the world. The Paducah plant has been the largest single-meter consumer of electric power on the planet, requiring two TVA coal plants just to keep it operating, and it’s the largest single-source emitter of the very worst atmospheric gasses—chlorofluorocarbons (CFCs).

The plant narrowly escaped the selection process that shuttered its sister plants in Tennessee and Ohio long ago. A 2012 apocalypse for Paducah workers was averted only by a last-second, five-party raid on the U.S. Treasury involving four federal entities pitching together to bail out USEC financially, a deal so arcane that knowledge of Mayan astrological codices would be required to grasp its basic principles. The plot would make for a great super-crime Hollywood movie in which Kentucky’s own George Clooney and Ashley Judd could star, if only the crafting lawyers and bureaucrats had made the Code of Federal Regulations as easy to decipher as bible code, or half as interesting.

“The deal” that saved Paducah operations for a year, past one crucial election non-coincidentally, probably consumed more net energy than it produced by stupidly paying USEC to run depleted uranium waste back through the inefficient Paducah plant—like a massive government program paying citizens to drink their own pee as a way to cut sewerage costs and keep medics employed prior to a Presidential contest. The deal never would have passed muster if it had been subjected to environmental or economic reviews of any kind, but it wasn’t. The “jobs” mantra was chanted, and all applicable laws from local noise-control ordinances to the Geneva Conventions were waived.

But the deal expires on May 31, in nine days. USEC and DOE have both said that discussions for a new extension deal continue, but rumors of a new deal were dashed on May 7, sending USEC stock into a flip-flop, when in an investor conference call, the company announced that no extension had been agreed, with very pessimistic notes about even a “short-term” postponement. That accompanied news that USEC had suffered a $2 million loss in the first quarter of 2013, largely attributable to the power bill at Paducah, which USEC says it’s under no obligation to keep paying.

Showing no enthusiasm whatsoever, USEC CEO John Welch said on May 7:

“While we continue to pursue options for a short-term extension of enrichment at Paducah beyond May 31, we also continue to prepare to cease enrichment in early June.”

Meanwhile, the Kentucky DOE field office in charge, managed by William A. Murphie, has advertised a host of companies “expressing interest” in future use of the Paducah site, with no explanation of how the existing edifice of egregiousness will be made to disappear. “Off the record,” the Kentucky field office has floated dates like 2060 for the completion of Paducah cleanup.

That’s two generations from now and kind of a long time for the skilled workforce and other interested parties to hang around. Even the 2060 date assumes that costs can be minimized by evacuating the diffusion cells before power-down—the scenario that seems certain not to happen because no one has the funding for it. Flushing the cells of uranium hexafluoride gas is the only sensible way to power-down, but it’s costly and time-consuming. At the Piketon, Ohio, plant a semi-clean power-down has cost billions of dollars and has taken twelve years and counting to accomplish. (Murphie will have to explain why he paid USEC so much money for the extended power-down at Piketon, while simultaneously asserting that a Paducah power-down can be accomplished swiftly and cheaply). Clean power-down also requires that workers and supplies be available on demand, and in the Paducah case, there simply isn’t time.

According to reliable sources, contracts are being prepared for the work of placing the plant into what Murphie calls “cold storage”—a term of his invention. But those contracts won’t take effect until October when fiscal 2014 funds are available. “Cold storage” at that point means closing the doors, posting guards outside, and otherwise walking away.

Can there yet be an extension deal to hold over the plant until 2014 funds are available? Probably not, because USEC may not last that long, the equipment in the plant has been run to decrepitude with no attention to maintenance, there isn’t sufficient time to make the arrangements, and a second end-run around environmental compliance would likely generate lawsuits.

Read Full Article here

**********************************************************************************************************

USEC to Cease Enrichment at Paducah Plant

- Operations for inventory management and site transition to continue -

BETHESDA, Md.–(BUSINESS WIRE)– USEC Inc. (NYSE: USU) announced today that it had not been able to conclude a deal for the short-term extension of uranium enrichment at the Paducah Gaseous Diffusion Plant in Kentucky, and the company will begin ceasing uranium enrichment at the end of May. The Paducah plant is the only U.S.-owned and operated uranium enrichment facility in the United States. USEC leases the plant from the U.S. Department of Energy (DOE).

“While we have pursued possible opportunities for continuing enrichment, DOE has concluded that there were not sufficient benefits to the taxpayers to extend enrichment. I am extremely disappointed to say we must now begin to take steps to cease enrichment,” said Robert Van Namen, USEC senior vice president and chief operating officer.

“We will continue to meet our customers’ orders from our existing inventory, purchases from Russia under the historic Megatons to Megawatts program and our transitional supply contract with Russia that runs through 2022,” Van Namen said. “In addition, our work to commercialize the American Centrifuge technology continues through our research, development and demonstration program with DOE, which remains on schedule and within budget, as we remain on a path to deploy this critical technology.”

USEC will take steps to cease enrichment at the Paducah plant over the next month and to prepare the plant site for return to DOE. USEC expects to continue operations at the site into 2014 in order to manage inventory, continue to meet customer orders and to meet the turnover requirements of its lease with DOE.

“We will be working with DOE during the coming months and expect to reach agreement on how to best transition the site. The company and our workforce have unparalleled expertise that should be drawn on. We can provide significant value to the government in making that transition in the most cost-effective and timely manner,” Van Namen said.

USEC expects to begin reducing its workforce at the plant in the coming months. The Company will begin notifying workers as the specifics of the transition activities are defined. USEC anticipates maintaining a workforce at the site into next year to support ongoing operations, perform transition activities and meet regulatory requirements.

“We want to thank our employees and the entire Paducah community for their efforts to support continued enrichment at the plant. Although the community has known about this possibility for a number of years, we recognize that the Paducah area will soon feel the real impact of this decision and its effects on many individuals and families,” said Steve Penrod, vice president of enrichment operations.

“For 60 years, Paducah employees and the community have supported our national security and energy security. For now, at least, that mission is ending, but we are committed to working with the community and DOE for the smoothest possible transition that positions the plant site for its future role in the area’s economy.

“We want to thank members of the Kentucky delegation and our unions, the United Steel Workers and the Security, Police & Fire Protection Professionals, all of whom have worked tirelessly on behalf of the employees at this plant. We fully expect they will now recommit to helping the community create the next economic chapter for this site.”

USEC Inc., a global energy company, is a leading supplier of enriched uranium fuel for commercial nuclear power plants.

Read Full Article  Here

 

*********************************************************************************************************

Weapons of Mass Destruction (WMD)

PADUCAH GASEOUS DIFFUSION PLANT

globalsecurity.org

 

The Paducah Gaseous Diffusion Plant (PGDP) is located in western Kentucky, 10 miles west of the City of Paducah, near the Ohio River in McCracken County. The plant sits on a 3,425-acre tract of property, 750 acres of which are enclosed inside the PGDP security fence and 74 of those contain process buildings. The site is owned by DOE and leased and operated by the United States Enrichment Corporation (USEC), a subsidiary of USEC, Inc.

It is the only operating uranium enrichment facility in the U.S. The site contains uranium enrichment process equipment and support facilities. The mission of the Plant is to “enrich” uranium for use in domestic and foreign commercial power reactors. Enrichment involves increasing the percentage of uranium-235 in the material used for creating reactor fuel (UF6). Uranium-235 is highly fissionable, unlike the more common isotope uranium-238. The PGDP enriches the UF6 from roughly 0.7 percent uranium-235 to about 2.75 percent uranium-235…….

 

Read  In Full Here

 

***********************************************************************************************************

USEC preparing for close down

May 24, 2013
The United States Enrichment Corp. sits 15 miles west of Paducah on land the Department of Energy owns.

The United States Enrichment Corp. sits 15 miles west of Paducah on land the Department of Energy owns.

USEC will start taking steps to close down its operations at the Paducah Gaseous Diffusion Plant over the next month and to prepare the plant site for return to DOE, said Robert Van Namen, USEC senior vice president and chief operating officer.

USEC expects to begin reducing its work force at the plant in the coming months and anticipates maintaining a work force at the site into next year, Van Namen said.

Read Full Article Here

 

**********************************************************************************************************

Wikipedia

Paducah Gaseous Diffusion Plant

History

The former Kentucky Ordnance Works site was chosen from a candidate list of eight sites in 1950. The construction contractor was F.H. McGraw of Hartford, Connecticut, and the operating company was Union Carbide. The plant was opened in 1952 as a government-owned, contractor-operated facility, producing enriched uranium to fuel military reactors and for use in nuclear weapons. The mode of enrichment was the gaseous diffusion of uranium hexaflouride to separate the lighter fissile isotope, U-235, from the heavier non-fissile isotope, U-238. The Paducah plant originally produced low-enriched uranium, which was further refined at Portsmouth and the K-25 plant at Oak Ridge, Tennessee. From the 1960s the Portsmouth and Paducah plants were dedicated to uranium enrichment for nuclear power plants. In 1984 the operating contract was assumed by Martin Marietta Energy Systems. Lockheed Martin has operated the plant since the merger of Martin Marietta with Lockheed in 1995. From 2001, all USEC production has been consolidated at Paducah.[2][3]

The Paducah plant had a capacity of 11.3 million separative work units per year (SWU/year) in 1984. 1812 stages were located in five buildings: C-310 with 60 stages, C-331 with 400 stages, C-333 with 480 stages, C-335 with 400 stages and C-337 with 472 stages.[4]

Employment and Economic Impact

USEC employs around 1100 to operate the plant. The Department of Energy employs around 600 through contractors to maintain the grounds, portions of the infrastructure, and to remediate environmental contamination at the site. The facility has had a positive economic impact on the local economy and continues to be an economic driver for the community. Elected officials are working to ensure that the plant continues to operate though other methods of enriching uranium, such as centrifuge, are more efficient.[1]

Contamination

Plant operations have contaminated the site over time. The primary contamination of concern is trichloroethylene (TCE), which was a commonly used degreaser at the site. TCE leaked and contaminated groundwater on and off the site. The groundwater is also contaminated with trace amounts of technetium-99, a radioactive fission product; other contaminates include polychlorinated biphenyl (PCBs). Through normal operations, portions of the plant are contaminated with uranium.

In 1988, TCE and trace amounts of technetium-99 was found in the drinking water wells of residences located near the plant site in McCracken County, Kentucky. To protect human health the Department of Energy provided city water, at no cost, to the affected residents and continues to do so.

Cleanup status

The Department of Energy is using electrical resistance heating, ET-DSP(trademarked) to vaporize the TCE from the groundwater. This clean up action began in mid-2010. Much of the contamination of the actual plant will not be cleaned up until the plant ceases operations.

 

 

 

 

File:Lake Mead by air.jpg

Lake Mead by air

Craig Morey from Emsworth, Hants, UK

Creative Commons Attribution-Share Alike 2.0 Generic license.

 

David Fulmer

Flickr: Kayakin’ on Colorado River     Creative Commons Attribution 2.0 Generic license.

Dust-storm-Texas-1935  -  Dust Bowl

NOAA George E. Marsh Album    -    Public  Domain

*********************************************************************************************************

The Colorado River, The High Plains Aquifer And The Entire Western Half Of The U.S. Are Rapidly Drying Up

 

What is life going to look like as our precious water resources become increasingly strained and the western half of the United States becomes bone dry?  Scientists tell us that the 20th century was the wettest century in the western half of the country in 1000 years, and now things appear to be reverting to their normal historical patterns.  But we have built teeming cities in the desert such as Phoenix and Las Vegas that support millions of people.  Cities all over the Southwest continue to grow even as the Colorado River, Lake Mead and the High Plains Aquifer system run dry.  So what are we going to do when there isn’t enough water to irrigate our crops or run through our water systems?  Already we are seeing some ominous signs that Dust Bowl conditions are starting to return to the region.  In the past couple of years we have seen giant dust storms known as “haboobs” roll through Phoenix, and 6 of the 10 worst years for wildfires ever recorded in the United States have all come since the year 2000.  In fact, according to the Los Angeles Times, “the average number of fires larger than 1,000 acres in a year has nearly quadrupled in Arizona and Idaho and has doubled in every other Western state” since the 1970s.  But scientists are warning that they expect the western United States to become much drier than it is now.  What will the western half of the country look like once that happens?

A recent National Geographic article contained the following chilling statement…

The wet 20th century, the wettest of the past millennium, the century when Americans built an incredible civilization in the desert, is over.

Much of the western half of the country has historically been a desolate wasteland.  We were very blessed to enjoy very wet conditions for most of the last century, but now that era appears to be over.

To compensate, we are putting a tremendous burden on our fresh water resources.  In particular, the Colorado River is becoming increasingly strained.  Without the Colorado River, many of our largest cities simply would not be able to function.  The following is from a recent Stratfor article

The Colorado River provides water for irrigation of roughly 15 percent of the crops in the United States, including vegetables, fruits, cotton, alfalfa and hay. It also provides municipal water supplies for large cities, such as Phoenix, Tucson, Los Angeles, San Diego and Las Vegas, accounting for more than half of the water supply in many of these areas.

In particular, water levels in Lake Mead (which supplies most of the water for Las Vegas) have fallen dramatically over the past decade or so.  The following is an excerpt from an article posted on Smithsonian.com

And boaters still roar across Nevada and Arizona’s Lake Mead, 110 miles long and formed by the Hoover Dam. But at the lake’s edge they can see lines in the rock walls, distinct as bathtub rings, showing the water level far lower than it once was—some 130 feet lower, as it happens, since 2000. Water resource officials say some of the reservoirs fed by the river will never be full again.

Today, Lake Mead supplies approximately 85 percent of the water that Las Vegas uses, and since 1998 the water level in Lake Mead has dropped by about 5.6 trillion gallons.

So what happens if Lake Mead continues to dry up?

Well, the truth is that it would be a major disaster

Way before people run out of drinking water, something else happens: When Lake Mead falls below 1,050 feet, the Hoover Dam’s turbines shut down – less than four years from now, if the current trend holds – and in Vegas the lights start going out.

Ominously, these water woes are not confined to Las Vegas. Under contracts signed by President Obama in December 2011, Nevada gets only 23.37% of the electricity generated by the Hoover Dam. The other top recipients: Metropolitan Water District of Southern California (28.53%); state of Arizona (18.95%); city of Los Angeles (15.42%); and Southern California Edison (5.54%).

 

Read Full Article Here

 

**********************************************************************************************************

 

U.S. Has Depleted Two Lake Eries’ Worth Of Groundwater Since 1900

Aquifer water levels are rapidly falling across most of the U.S., according to a new study.
By Francie Diep Posted 05.21.2013 at 3:30 pm 8 Comments

 

Aquifers in the Continental US

Aquifers in the Continental US This map of major aquifers in the U.S. highlights the High Plains Aquifer (green) and the Dakota Aquifer (white, outlined in black). L.F. Konikow, U.S. Geological Survey

Over the last century, the U.S. has depleted enough of its underground freshwater supply to fill Lake Erie twice, according to a new study from the U.S. Geological Survey. Here’s another way to understand how much water we’ve used. Just between 2000 and 2008, the latest period in the study and the period of fastest depletion, Americans brought enough water aboveground to contribute to 2 percent of worldwide ocean level rise in that time.

“We think it’s serious,” Leonard Konikow, the U.S. Geological Survey hydrologist who performed the study, tells Popular Science. “It’s more serious in certain areas.”

Lowering aquifers mean less local water for the communities that depend upon them. They can also suck dry springs, wetlands and other surface water features, Konikow wrote in a report the survey published yesterday. Scientists don’t always have a tally for how much water an aquifer holds, however, so it’s more difficult to say what percentage of the U.S.’ overall groundwater is gone. (In some systems, it’s difficult to determine where the bottom of the aquifer is, Konikow explains.)

 

Read Full Article Here

You  know this   will probably  not be a  very popular  thing to say. However on the heels of the outrage  over the lack of respect  of Obama  in  regards  to a  Marine holding an   umbrella  for  him.   It  seems  to  me that   we  as Americans are  losing sight  of  the sense  of  Respect.  I am not an  Obama supporter.  there  are  many things  he  has  done and plans to do that  I am not in  agreement  with.  That  being  said  I  have a   question.

What  ever  happened to  civility?

When did  it  become ok to be  rude, obnoxious and just  plain  disrespectful and be  proud  of  it?

Whether  we  agree  with the  man  or  not, there  is a certain  amount  of respect that  must  me  given the Office .

You  don’t  have to agree with  him or even like him, but  you  have to respect the  office.  I know  people  are frustrated  and angry, but  that  does  not  excuse  the  degradation of  civility.  We  must  be  able to  express our  differences  in a  respectful manner.  Otherwise how can  we demand  respect in return if  we  are  willing  to lower  ourselves  to this type of behavior.  This is exactly  the  type of behavior that  was   criticized  from Occupy.  No  respect,  no  civility, just  right  in your  face  screaming and   yelling disrespect.  You  cannot have it  both ways.  You  either behave  the  way  you   would have others  behave or  you  accept  that   you  will be  treated  disrespectfully  because civility  has  gone to  hell in a  hand basket and no one  cares.

That  is not  to  say  that  we cannot  voice our  displeasure.  Of course  we  have  free speech and  should be  able to  express it  .  but  crashing a function such as  this and  making a  show  of it  like this. I  truly  believes it  reflects badly on the person.

That  is  a very  personal opinion  and I  respect the opinion of  anyone  who is  not  in  agreement  .  However, I believe  that  we  as  a  society  are  losing our  sense of respect  and   propriety. Protests serve a  purpose, they   get a  dissenting message  across and  if your  cause is  just and  it resonates with  others  then  you   will have  what  it takes  to make   people take notice.   But  Heckling only  makes  the  heckler look bad.  It is  very  sad to  see……..

****I would also like to add that  Madea was arrested with  her  boyfriend and quite a few others for  dancing at the  Jefferson Memorial during  an  Adam  Kokesh demonstration.   Video has  been  added  below. ****

~Desert Rose ~
***********************************************************************************************************

RTAmerica RTAmerica

Published on May 23, 2013

President Obama’s speech Thursday on national security wasn’t just a one-sided affair. The president paused multiple times when Code Pink founder Medea Benjamin shouted out, literally stopping Obama in his place and forcing him to respond. Benjamin was demanding answers for the drone strikes that killed four American citizens as well as the end to holding detainees at Guantanamo Bay. Benjamin is a well-known anti-war protester recognized around the world, and she joined us to talk about why she couldn’t remain silent during the president’s speech.

**********************************************************************************************************

Mass Arrests At Jefferson Memorial For Public Displays Of Affection/Dancing Incl. Adam Kokesh (RT)

Published on May 28, 2011

A disgusting over-reach by federal goons at the Jefferson Memorial results in the mass arrests of innocent tourists, including a couple who were kissing. Adam Kokesh was also arrested for dancing.

desertrosetx

Published on May 23, 2013

Tectonic Summary

The May 23, 2013 Mw 7.4 earthquake southwest of Vaini, Tonga, occurred as a result of normal faulting at a depth of approximately 170 km. At the location of this earthquake, the Pacific and Australia plates are converging at a rate of approximately 73 mm per yr in an east-west direction, resulting in the westward subduction of the Pacific plate beneath Tonga at the Tonga-Kermadec trench. The depth and faulting mechanism of the May 23rd earthquake indicate it ruptured a fault within the subducting Pacific lithosphere rather than on the shallower thrust interface between the two plates.

The Tonga-Kermadec arc has frequent moderate-to-large earthquakes, and has hosted over a dozen M6.5 plus earthquakes within 500 km of the May 23rd earthquake over the past 40 years. Most of these also occurred at intermediate depths; the largest was an Mw 7.7 earthquake in October of 1997, approximately 110 km to the north-northeast of the May 23 2013 event. None are known to have caused significant damage. Intermediate-depth (70-300 km) and deep-focus (depth less than 300 km) earthquakes are distinguished from shallow earthquakes (0-70 km) by the nature of their tectonic setting, and are in general less hazardous than their shallow counterparts, though they may be felt at great distances from their epicenters. The Tonga-Kermadec slab in the region of the May 23 2013 earthquake is seismically active to depths of over 650 km.

Seismotectonics of the Eastern Margin of the Australia Plate

The eastern margin of the Australia plate is one of the most sesimically active areas of the world due to high rates of convergence between the Australia and Pacific plates. In the region of New Zealand, the 3000 km long Australia-Pacific plate boundary extends from south of Macquarie Island to the southern Kermadec Island chain. It includes an oceanic transform (the Macquarie Ridge), two oppositely verging subduction zones (Puysegur and Hikurangi), and a transpressive continental transform, the Alpine Fault through South Island, New Zealand.

Since 1900 there have been 15 M7.5 plus earthquakes recorded near New Zealand. Nine of these, and the four largest, occurred along or near the Macquarie Ridge, including the 1989 M8.2 event on the ridge itself, and the 2004 M8.1 event 200 km to the west of the plate boundary, reflecting intraplate deformation. The largest recorded earthquake in New Zealand itself was the 1931 M7.8 Hawke’s Bay earthquake, which killed 256 people. The last M7.5 plus earthquake along the Alpine Fault was 170 years ago; studies of the faults’ strain accumulation suggest that similar events are likely to occur again.

The Kermadec-Tonga subduction zone generates many large earthquakes on the interface between the descending Pacific and overriding Australia plates, within the two plates themselves and, less frequently, near the outer rise of the Pacific plate east of the trench. Since 1900, 40 M7.5 plus earthquakes have been recorded, mostly north of 30°S. However, it is unclear whether any of the few historic M8 plus events that have occurred close to the plate boundary were underthrusting events on the plate interface, or were intraplate earthquakes. On September 29, 2009, one of the largest normal fault (outer rise) earthquakes ever recorded (M8.1) occurred south of Samoa, 40 km east of the Tonga trench, generating a tsunami that killed at least 180 people.

Earth Watch Report  -  Epidemic Hazards

Image Source

….

Today Epidemic Hazard Colombia Municipality of Garzon , Garzon Damage level
Details

….

 

….

Epidemic Hazard in Colombia on Thursday, 23 May, 2013 at 02:41 (02:41 AM) UTC.

Description
An epidemic of acute respiratory infection (ARI) in the municipality of Garzon in the center of the Department of Huila has resulted in 2 deaths and another 23 people infected with the dangerous illness. Carlos Daniel Mazabel, departmental secretary for health, warned that pregnant women, people older than 60 years, and cancer patients are the most vulnerable groups. The 2 fatal victims to date are a 61-year-old woman and a 52-year-old man, a community leader from the municipality of Garzon, who, according to the medical diagnosis, died after a complicated fever and respiratory distress syndrome.
Biohazard name: Acute respiratory illness
Biohazard level: 4/4 Hazardous
Biohazard desc.: Viruses and bacteria that cause severe to fatal disease in humans, and for which vaccines or other treatments are not available, such as Bolivian and Argentine hemorrhagic fevers, H5N1(bird flu), Dengue hemorrhagic fever, Marburg virus, Ebola virus, hantaviruses, Lassa fever, Crimean-Congo hemorrhagic fever, and other hemorrhagic or unidentified diseases. When dealing with biological hazards at this level the use of a Hazmat suit and a self-contained oxygen supply is mandatory. The entrance and exit of a Level Four biolab will contain multiple showers, a vacuum room, an ultraviolet light room, autonomous detection system, and other safety precautions designed to destroy all traces of the biohazard. Multiple airlocks are employed and are electronically secured to prevent both doors opening at the same time. All air and water service going to and coming from a Biosafety Level 4 (P4) lab will undergo similar decontamination procedures to eliminate the possibility of an accidental release.
Symptoms:
Status: confirmed

….

 

Acute respiratory infections: a review*

Abstract

Acute respiratory infections (ARI) constitute one of the principal causes of morbidity and mortality in many countries. Data from 88 countries in five continents, with a total population of nearly 1200 million, showed that deaths due to ARI in 1972 amounted to 666 000. Pneumonia, both viral and bacterial, accounted for 75.5% of the total deaths from ARI. Mortality from ARI represents 6.3% of deaths from all causes. Considerable differences in mortality rates exist both between and within continents. Mortality from ARI is highest in infants and old people. The data suggest that in some areas of the world mortality due to ARI is extremely high.

 

Full Report  May Be Found Here

….

 

….

Follow

Get every new post delivered to your Inbox.

Join 742 other followers