Message
Up Archive1 Archive2 Archive3 Archive4 Archive5 Archive6

Folks, we appreciate your interest in the Radiation Network, and thank you for your support.  You may send us an email, but we will not be able to respond to most.  Instead, this Message page will address issues that you raise.  So please read this page and the archived Messages in lieu of, or before emailing us.  We update it occasionally, and it will answer a lot of your questions.

Email:    tim@radiationnetwork.com

Epilogue: 03/22/14, 10:00 A.M. - Post Falls, ID alert

Interesting conclusion to the Post Falls , Idaho radiation alert from 12/23/13 - Station operator commissioned a professional Radon test, which did in fact confirm that his monitoring environment was radon infested, showing a reading of 17 picocuries/liter versus a normal standard of 4 pCi/l or so.  The test was performed over two days using an electronic Radon monitor which simultaneously tracked barometric pressure.  The bottom of the two graphs at left shows Radon levels on the top graph line, and barometric pressure on the bottom graph line.  You can see that as barometric pressure dropped, which happens when a low pressure weather pattern moves through, the Radon levels rose.

Meanwhile, the station operator ran his PRM-9000 Geiger counter simultaneously with the Radon test.  Look how perfectly the radioactivity levels shown on the colored graph at top tracked with the Radon levels being monitored by the electronic Radon sensor.  So the Radon monitor turns out to have been an excellent corroborating instrument for the PRM-9000.

Since that time, the station operator instituted Radon mitigation, and ever since, his readings have fallen to relatively normal levels, and he is back online now, reporting an average of 54 CPM, not unexpected for a pancake tubed model at his 2,300' elevation.

The Radiation Network has seen other monitoring stations show a similar graph pattern, especially when running a pancake-tubed model, probably relating to its ultra sensitive alpha detection, which makes sense because the Radon decay process generates a significant alpha emission, I am told.

Update: 12/27/13, 7:40 A.M. - Station operator took himself offline to conduct some specific tests in the last couple of days.  Most everything he scanned for 10 minutes each read pretty normally - kitchen wood/formica counter at 61 CPM, shoes at 71 CPM, another rainfall test (paper towel swipe of car) at 62 CPM.  But here is the very telling experiment - a 10 minute outdoor background count 20" off the ground which read at 61 CPM - close to normal background for his high count rate pancake-tubed Geiger counter at his 2,300' altitude.  This test was necessary to remove the Geiger counter completely from any specific substance and/or indoor environment that may have contributed to his continuous 100+ CPM readings on 12/23, and assure that the Geiger counter itself was not contaminated.

But here is the next interesting part - after the above tests, he plugged his detector back into his computer for a logged and continuous monitoring again from indoors, and after many hours, he reports his graph showed the same elevating pattern, peaking at a sustained level above 100 CPM.  So this most likely points to a radon gas infested environment indoors, as opposed to a passing radioactive weather pattern.  I would add that he monitors from a one story house with basement, where the two sections are connected via a door-less doorway.  To confirm the radon theory, the plan is to ventilate the kitchen from where he is monitoring, confirm readings subsided to normal, then close up the house, and plug back into the network so we can remotely watch if his graph re-elevates over a period of time again.  So stay tuned.

Follow up: 12/24/13, 8:10 A.M. - Spoke with the station operator this morning.  He states that the rainwater scan was conducted independent of these elevated readings, so we are still investigating the cause.  We want to rule out possible explanations like a contaminated instrument, a contaminated operator, or a local indoor radioactive environment, so station operator will do a timed background count outdoors later today.  Until then, he took his station offline.  Hopefully, his outdoor count will reveal his normal background for the pancake-tubed PRM-9000 at his 2,300' altitude of about 55 CPM.  If not, we'll need to consider either the contamination explanations, or a radioactive environment that moved into his area.

Update: 12/23/13, 9:45 P.M. - Testing Rainwater online?

A new station in Post Falls, Idaho is alerting at levels over 100 CPM as I write this.  We are trying to establish the reason - it may be the station is doing a scan of captured rainwater while still plugged in to to the network.  We will try to confirm this in the morning.

 

 

 

Update: 11/6/13, 6:30 A.M. - New Alert Level activated

The Radiation Network has been transitioning some new features in over the last few months.  To review, we are an equal opportunity Network, i.e. almost any model of Geiger counter is welcome to contribute its readings.  But most of us now know that not all Geiger counters are created equal.  This historically presented a problem in establishing both a common and meaningful Alert level for stations on the network.  In the past, we just used a simple 100 CPM level, however, that resulted in our "lower count rate" stations typically being 'left out' of most alerts, i.e. those stations would have to detect elevated levels perhaps seven times background before alerting.  So we have now adopted a more precise Alert level which you can see foot-noted under the Map on the main page and repeated here:

   3 consecutive minutes of the lesser of 100 CPM or 2.5 times a Station's baseline

The simulated Alert level symbol on the Map inset at right shows how a low count rate station can alert at less than 100 CPM, so be on the lookout for that.  The idea behind requiring 3 consecutive minutes of alert level readings to actually issue an alert is to filter out stations exhibiting momentary spikes which usually relate to connection glitches and the like.  In general, what really matters in radiation detection are elevated levels that are sustained.  As the courtroom judge often says, "Sustained!"

Update: 8/21/13, 7:45 A.M. - Dangerously high Radiation levels at Fukushima

A Japanese news agency is reporting that readings of 100 mSv/hr are being emitted from leaking tanks of contaminated water at the Fukushima nuclear power plant.  Let's put that reading in context.  First of all, the dose rate of mSv/hr stands for milli-Sieverts per hour, or one thousandth of a Sievert/hr.  In contrast, typical background readings at sea level approximate .1 ÁSv/hr, expressed as .1 micro-Sieverts/hr.  The micro-prefix stands for one millionth, so if my math is correct, the readings of the leaking water therefore amount to 1 million times normal background levels!!!

Beyond the obvious point of the story, what I would offer is that when communicating readings of radiation levels, it is not enough, and is even irresponsible to report just a number, like 100.  The number must always be accompanied by the applicable unit of measurement, such as 100 milli-Sv/hr or 100 CPM.  And in this business, decimal places also matter.  I pass on this reminder because in the early days of the Fukushima disaster, it was common for readings to be mis-reported.  By now though, most of us understand that radiation dose levels can be expressed in a variety of units.

Update: 8/10/13, 8:00A.M. - Recent Radiation Detections/Alerts

For the record, I am posting graphs and descriptions of a few recent alerts over the last couple of weeks.  The Anchorage station on July 25th was operating an Eberline model with pancake tube, set up outdoors and shielded from direct sun.  The station operator is not sure of the cause for the steady rise in radiation levels, indicating that weather conditions were particularly hot and sunny during the elevation.  Otherwise, the graph pattern resembles that often generated during passing storms.

At left, the Greensboro, NC station was operating a standard tubed Monitor 4 on July 28th when his average background count of 10 CPM gave way to a 3 minute surge of 352, 545, and 760 CPM, then just as quickly subsided to normal levels.  This pattern could be explained by brief handling of a radioactive sample, or momentary passing of a human still radioactive from a medical test, but the operator claims neither.  Logistically, his detector is facing out a second story window toward an airport, with clear skies at the time - cause unknown.

Then just yesterday, August 9th, the Williston,  ND station broadcast an alert, exceeding 200 CPM against his normal background of 49 CPM.  He operates the PRM-9000, an ultra-sensitive pancake tubed Geiger counter.  No feedback yet from the operator as to an explanation.  In case it is relevant, Williston is ground central for the recent oil boom surrounding the rich Bakken geological formation.

On a related matter, many of you email for an explanation of the chronically high reading in the Pennsylvania/New Jersey area.  This is a station located in Philadelphia, running the high count rate Inspector model.  The station's average is, and has been from the beginning, about 59 CPM.  This is unexpected - near sea level, the Inspector would normally read about 35 CPM.  Thus far, I have still received no response from the Philly station.

Thanks again for your support. Tim Flanegin

Back to the Radiation Network

Click here to go to Archived Messages