Tag Archives: Meteor

Seismic Evidence From the Russian Meteorite Explosion

Today we're going to follow up on the last blog post about the explosion of a meteorite over Chelyabinsk, Russia.  The process of figuring out precise infrasound arrival times is quite a tricky process, the travel times depend on winds, humidity, and many other atmospheric variables that are hard to constrain over such a long travel path.  I've had several fantastic discussions with Dr. Charles Ammon here at Penn State to try to obtain the infrasound data that was collected near the blast, but so far we have not been able to get it.  When/if we do, expect another posting.

The focus of this post will actually be the seismic data near the blast.  There are many seismometers all over the Earth that record the motion of the ground many times a second.  After some discussion of the infrasound and seismic data available with Dr. Ammon, we found some really nice, simple results that would make a great laboratory assignment for an introductory seismology or geoscience class.  The activity could range from reading times of arrivals on provided graphs for a non-majors class, to filtering and grid searching to estimate the precise detonation location for a more advanced class.  I've provided the data and some thoughts on it below.

We'll consider data from five seismic observatories, the station names are ARU, BRVK, KURK, OBN, and ABKAR.  Below is a map showing the station location, distance to the blast (red star), and a seismogram from that station.  The seismogram shows how the ground is moving through time, in this case I'm showing the "Z" component.   This really just means we're looking at how the ground is moving up and down, though these stations also record North/South and East/West movement.  What we see is ground motion caused by the shock wave hitting the ground and that ground motion propagating away.

Fig. 1 - Map view of the seismic stations used.  Distance from the explosion, time after the explosion to a phase arrival, and arrival order (rank) are shown along with the seismogram.  All seismograms begin at the instant of the explosion.

It's common sense to expect the energy from the explosion to arrive at a later time at stations further away, which it does.  Notice how the sharp peak corresponds to distance? We can actually make a plot of this and learn some more from the data.  To do this, pick a feature that is easily identified in each waveform (we used the first trough) and record how many seconds after the blast it arrives at the instrument.  We then plot that on the x-axis of a graph and the distance of the station from the blast on the y-axis.  The result should be something like that shown in figure 2.  Now we can use some basic math to figure out how fast this energy was traveling.  The red line on the figure is the "best fit line" to the data.  We use some basic statistics (a linear regression) to make this line, but any plotting program will do it for you.  A line has a slope (how steep it is) and a y-intercept (where it touches the y-axis when x is zero).  The slope of a line is how much the y values change per a certain change on the x axis, often taught as "rise over run" in the classroom.  The slope of this line turns out to be about 3km/s.  That's a pretty reasonable speed for surface waves (which these are) through the ground!

Fig. 2 - The distance from the blast against arrival times.  This data indicates the surface waves traveled about 3km/s, a reasonable speed.

If we could pick out a "p-wave" in the data (difficult for reasons we will discuss), the intercept of the line would be the height above the ground that the blast happened.  I haven't seen a really good estimate of the height, probably because the p-wave is hard to find and the speed of the meteorite. The meteorite was traveling about 40,000 mph when it exploded.  It's hard to imagine something moving that fast, so let's change around the units: that's something like 11 miles every second!

The p-wave could be hard to see because 1) it's going to be relatively small, and 2) there are waves from an earthquake in Tonga arriving about the same time as the meteorite explosion.  We know the waves we picked aren't from the tonga event, those would have arrived at all the stations at almost the same time because they were reflecting off the Earth's core.  It would be an interesting project to play with trying to pick p-waves and/or estimate their arrival window by guessing the height of detonation.

We don't have to stop here though.  This morning I saw this youtube video, a compilation of people recording the shockwave.  The meteorite had streaked past, exploded, and they were recording this when the shock wave hit.  Shockwaves behave in a funny way, but luckily it's been studied a lot by the government.  Why? Nuclear weapons! Seismologists are commonly employed to determine if a nuclear test has taken place, and estimate it's size, location, etc.  A lot of very interesting information on air-blast and it's interaction with buildings can be found in the book "The Effects of Nuclear Weapons".  The book has lots of formulas and relations that could make many interesting lab exercises, but we'll just discuss reflection in this post.

A shock wave is really a front of very high air pressure that is propagating through some material.  The high pressure is followed (in a developed shock wave) by a small, longer, suction, then a small overpressure.    I've tried to locate meteorological observations and so far have only found hourly observations.  If we can find short term observations we would expect to see wind rushing away from the blast, then more weakly towards it, then very weakly away from the blast.  By knowing those wind velocities we could estimate the pressure differential that caused the shock.  The local airport (station USCC) does report hourly average winds (data here).  There is a small bump in the average winds between 9-10am local time, when the meteorite entered.  The lack of a gust report though makes this observation a bit too shaky to use for a pressure estimate.  

Shock waves move faster than the speed of sound if they are a high enough "overpressure", or the pressure above atmospheric.  Shock waves will reflect off the ground when they reach it, as shown in figure 3.  The overpressure in the region of "regular reflection" is much higher than the overpressure of the shock wave due to a combined stacking effect.  There can also be complicating patterns such as "Mach Reflections".  

Fig.3 - The initial pressure wave (solid lines) and the reflected shock (dashed lines).  Image from "The Effects of Nuclear Weapons"

What's interesting about all this is the audio of the clips at about 20 and 40 seconds into the YouTube video.  Notice these clips contain two bangs.  The first clip with two shocks could be reflection off the building behind the camera, the second shock follows the first very close and is very loud.  The next clip has a significant delay though.  At any height above the surface the initial reflection occurred on, there will be a delay between the initial and reflected shock.  If we knew the location of this video it would help constrain the shock location.  (After some google searching I can't locate the "Assorty" store in the footage anywhere.)

Overall with the observations of glass breaking over such a large area, we can assume the reflected pressure was probably in the area of 1psi.  This means the initial overpressure was very small at the ground.  Could you work backwards from the estimate of 500 kiltons TNT? Sure! That's a topic for another day or for your students in lab! Be sure to check out the book "The Effects of Nuclear Weapons", many campus libraries have it, Penn State has it online even.

Below is a link to a zip file that contains the .SAC files for the seismic stations (starting at detonation time and low pass filtered as well as raw data) and high quality figures.  If I end up writing up a lab from the event, expect the data and lab to be on my academic website.  A review of literature on the Tunguska event may be helpful as well!

Zip file of data.

Chelyabinsk Meteorite - Infrasound, Seismic, and Satellites oh my!

Just as Earth was about to have a close encounter with asteroid 2012 DA14, the people of Chelyabinsk, Russia had a personal experience.  Before we talk about both 2012 DA14 and the Chelyabinsk event some terminology needs to be set out.  A meteoroid is a small chunk of debris in space, generally anything from a fleck of dust to a small boulder.  A larger space bit of debris is termed an asteroid.  A meteor is when some of this debris enters our atmosphere, heating up due to friction.  A meteor is called a meteorite if it actually reaches the surface of the Earth and survives impact.  Everyday we are pelted with many tiny meteors, but few reach the surface.  Most meteorites are never discovered as they are statistically much more likely to land in the ocean due to it's coverage of Earth's surface.  Sometimes meteorites are found on land, in fact it is common for scientists to go to Antarctica to look for the dark rocks on the surface of a white sheet of ice.  There are many pages on hunting meteorites  and a book as well, it's worth reading about if your curious how we find rocks that landed a long time ago.

It's worth saying that there are different kinds of space debris, some more stony, some made of almost solid metal, and some of ice.  While it's worth discussing, I'd rather focus on the current events in this post, so if you are curious there is a nice page at geology.com that gives the basics.

To begin, lets talk about 2012 DA14, or the non-intuitive name that we gave a near Earth asteroid that is about 160 feet in diameter and weighs a massive 190,000 metric tons.  This asteroid could do some serious damage and was scheduled to have a close call with Earth on February 15th.  How close? Well, it would be about 17,200 miles from the surface, which seems like a long way.  It's not.  The moon is 250,000 miles away (roughly) and we've been there and back in a matter of a few days.  In fact, the geosynchronous satellites that beam TV and weather data down to Earth orbit about 22,236 miles above the surface to rotate at the same rate the Earth does.  As shown in the figure below, 2012 DA14 passed between us and the geostationary satellite band; a very close call.

Why talk about 2012 DA14 in a post about a meteor over Russia? To say they are not related in any way.  They approached from entirely different directions and it just happened to be a coincidence of space and time.

Now for the event in Russia.  At 3:20:26 UTC on Feburary 15th a large meteor about the size of a schoolbus entered the atmosphere.  The 49-55 foot estimated diameter object probably weighed about 7000-10000 tons.  While heating up upon atmospheric entry the meteor "detonated" or exploded in mid-air.  This has happened before, a list of historic airbursts can be found here.  The most famous being a large explosion (also over Russia) in 1908 called the Tunguska event.  That explosion released the energy of 10-15 million tons of TNT, leveling forests and destroying an area of about 830 square miles.  The event that just occurred was about 500 kilotons of TNT equivalent, or roughly 20 times smaller.  Shock waves from the event still managed to send around 1500 people to local hospitals with shards of glass and building materials in their faces/skin from rushing to a window too see what was happening.  Videos of the entry are all over the web, in several you can hear the detonation and shock wave.

So how do we know so much about this object considering we didn't know anything about it until it exploded overhead? Well, remote sensing helps us.  When a meteor entered over Wisconsin in 2010, I wrote about following the trail on the US Doppler Radar Network (here).  This time we could see the meteor from weather satellites (Meteosat 10 image below) as well as on seismic and infrasound stations.  Another meteosat also captured several frames that have been made into a video here.  Current estimates of the entry speed are in the area of 40,000 mph with a very shallow entry angle.

First the seismic observations.  So far I've seen reports of the Borovoye, Kazakhstan station seeing a gorgeous signal (thanks to Luke Zoet on this one). The station details, and even a photo are available at the USGS network operations page.  Below is a filtered (0.15 Hz low-pass) seismogram from BRVK.  This would be a result of the shock wave rattling the ground and seismic station.

Next, and rather interesting, are the infrasound observations.  Infrasound is very low frequency sound (below 20Hz) that we can't hear, but can record as air pressure variations.  It so happens that Steve Piltz of the Tulsa National Weather Service has a microbarograph.  Upon seeing his data from an earlier earthquake (yes, ground movement causes air pressure waves), I immediately bought a unit from Infiltec and set it up in the office at Penn State.  Below is a picture of the station.

Infrasound propagation is incredibly complex and difficult to predict over such long distances, so I've done a simple calculation that is very likely going to be revised upon some discussions with seismologists this week.  First, I wanted to know how long the sound would have to travel.  To find the shortest travel distance between a latitude and longitude set you can assume a spherical Earth (not too bad for such a back of the envelope calculation) and some math.  Remember trigonometry? Well when it's modified to work on a sphere instead of in a plane it's creatively called 'spherical trigonometry' and consists of a strange function called the haversin.  If you are curious about how I calculated the travel path of the sound waves checkout the wikipedia page on the Haversine formula, but I've included the formula below.  Below is the result of the calculation, a great circle path between Chelyabinsk and State College, PA.
d = 2 r \arcsin\left(\sqrt{\operatorname{haversin}(\phi_2 - \phi_1) + \cos(\phi_1) \cos(\phi_2)\operatorname{haversin}(\lambda_2-\lambda_1)}\right)

The distance the wave would travel would be something like 8670 kilometers.  Sound travels at 340.29 m/s at sea level, but since we're making assumptions we'll say 300 m/s is a nice number.  So the wave would take somewhere in the 7-8 hour range to reach State College (assuming it's non-dispersive and many other likely not so great assumptions).  Luckily for us, the event and the arrivals are overnight.  During the day my infrasound station is swamped by signals from office doors opening and closing amongst other things.  The meteor entered the atmosphere at 10:20 pm local time, so I've plotted the infrasound from 10 minutes before the meteor entered to well after the energy should arrive.  There is a large increase in the noise shortly after entry, but this is too soon.  Could it be seismic energy or arrival of a faster shock path? Maybe, that's a point for some discussion and revision later.  The big thing to notice is the noise increase at about 7-8 hours after the entry.  It's still early in the morning, so it is doubtful that this is people coming into work.

I've made a .SAC (seismic analysis code) file of the raw data for about 24 hours around the event available to download here.  Download the file (~19Mb) and play with it! The data is collected at 50Hz, but all that is in the meta-data (as well as location details).  I use ObsPy to do most of my analysis in Python, but you could use SAC or other codes meant for seismic event analysis.

Steve's station in Oklahoma recorded similar signatures.  His data over a slightly shorter time span (5:21-11:42 UTC) is below, showing similar signatures.

Infrasound is actually what allows us to determine the energy release from the explosion.  As it turns out seismic stations and infrasound have been used to monitor nuclear testing for years (a relevant topic currently considering the recent tests by North Korea).

Overall, I'd say stay tuned for any updates.  Eventually the infrasound station I have will be setup for live streaming.  I'm sure after discussion with some folks more versed in infrasound travel we can clean up the data and maybe do some more back of the envelope energy/rate calculations for demonstation purposes.

Wisconsin Meteor - A Great Time to Play with Radar Data

As I'm sure you've heard by now last week, what is believed to be a meteor, passed into our atmosphere and exploded over Wisconsin.  The light was seen as far away at St.Louis, MO and was captured on a camera at the University of Wisconsin-Madison.  The video frames have been played on most news networks and are available everywhere online.
As you can imagine the 911 call center (actually 911 call centers over 6 states) was/were flooded with reports of the light, the sonic boom, and other observations.  The NWS also noticed a new trail appear on the radar.  I downloaded the level 2 data and plotted it up.  First we'll look at the reflection.

You can see the trail in the SW corner of Iowa county.  (KDVN radar)  Next is just a blow up of this image.  The meteor path was from west to east.  According to NASA scientists the meteorite was likely not from the current Gamma Virginids meteor shower, but a rock from the asteroid belt.
Next it would be interesting to look at this trail in 3D.  Using level II radar data this is possible.  The next images show this from several different angles.   The directions are labeled so it's easy to get bearings on which way you're looking.  If you notice the trail is sloping down slightly towards the SE.

The average hight for the event was right around 24,000-25,000 ft.  Looking at the plot you can see how small the plot was and how large the strongest reflector in the center is! A few back of the envelope calculations can be done using basic trig to determine some interesting things.  You can try this yourself.  I've posted a link to the radar data at the bottom and a link to a website where you can download a 21 day trail of GR2Analyst.  Just open the data and start slicing it!

Finally a sample of the meteorite has been recovered at is being examined currently.  There should be many other samples in the area also and hunters are already out looking for them.  With all this in mind you should remember it's not that uncommon for meteorites to enter the atmosphere.  Washing machine size chunks of rock are not abnormal and they burn up in the atmosphere.  If any material makes it to the ground it's probably never seen.  (Since most of the Earth is covered in water most probably hit there.)
 
Below: Scientists prepare a sample of the meteorite for a test


LINKS:
Gibson Ridge Software
Data for This Radar Scan