Date   
Re: Recovery mystery

dampguy
 

After 2 disasters, we always fly with two redundant tracking system. Our main is a weather probe that has been modified for 70mm radio. The backup is a GSM tracker...

Re: Recovery mystery

John Kovac KM6GKF
 

Thanks Dale, greatly appreciate your reply and the info.


On Friday, February 21, 2020, 08:08:32 PM PST, Dale Wegner <dalewegner@...> wrote:


The NOAA archived wind data for 2/18/20 21Z had a layer of wind below
5,000' coming out of the SSE before resuming its W wind direction
below 2,000' in the Chowchilla area.  Attached is wind file.
https://ready.arl.noaa.gov/READYcmet.php

I ran the wind data thru an oldy but goody BALTRK, exported the kml
prediction file for the final landing approach starting at the last
reported aprs position and merged the kml file with the aprs actual
track.  KML combined file is attached also.  It has a landing only 60
yards NE of its last reported position.  This should have been an easy
find.

We have had farmers pickup the payload before the chase team arrives,
and drive off to another field to work.  But the aprs tracker
eventually gets a signal out leading the chase team to the farmer. We
have used Spots in the passed with out any problems.

Thanks for this exercise to help sharpen my software skills for our
high school's spring time launch.

On 2/21/20, Hank Riley via Groups.Io <n1ltv=yahoo.com@groups.io> wrote:
>  [completed first sentence from last message]
> Sometimes a reasoned best estimate of the landing spot can mean the
> difference between the success or failure of missing balloon recovery
> efforts.
>
>
>
>



Re: Recovery mystery

John Kovac KM6GKF
 

Thanks to all of you for the detailed replies.  Greatly appreciated.  We just spent the third day in a row searching, without success.

The Spot Trace indicated the final stop in the exact same area:


37.098920, -120.313110

It's a few hundred feet north from the point Hank shows below, and directly across the street from the field James noted.

We scoured the area for about a mile in every direction, and used a metal detector in the low grass for about 500 feet in every direction from the point above to reduce the unlikely possibility that the Spot had come out of the sealed container and was no longer with the payload.  All of the irrigation ditches were not deep enough to conceal a payload under water, so we know it didn't go in water anywhere near there.

At this point our best guess is that in the ten or so minutes between when our payload landed and we got there, a car took the payload.  In testing the Spot I've found it is pretty good at giving a last "motion detected" ping even if you throw it in your car upside down, so I'm not sure why it would have failed in this case.  And there was maybe one car every 15 minutes while we were there, not a busy area.  This was I think the sixth time this Spot had been over 100K, so it certainly could have just worn out from the abuse, but it appeared to be working perfectly through landing.

We had the container well-marked with phone number and a request to contact us, but at this point I'm not holding out much hope.  

Thanks again for all of the info and suggestions. 


On Friday, February 21, 2020, 04:23:22 PM PST, Hank Riley via Groups.Io <n1ltv@...> wrote:


Sometimes a reasoned best estimate of the landing spot can mean the difference

Here's mine ( both imbedded and attached).  I've annotated the graphic with the last APRS (from aprs.fi) reported altitudes and speeds.  Above sea level elevation of the farmland is around 210 feet so a very small contributor to the simple arithmetic employed to give a landing spot and the larger circular zone that should enclose the real landing spot given uncertainties.

Essentially the last segment labelled X marks a drop of 3.3 k feet.  To drop the remaining 4.9 k feet I've shown a 1.5 X translation almost straight to the east. Actually the average bearing the payload was heading over the last few postions.

As James asked, it would be nice to know the last Spot position.  The more data, the better.  How was road traffic when you were on the way?  Non-existent?

Was the payload marked on the outside with prominent recovery info?  Also the inside?

I realize many people would not go inside a payload, but I think it's a good idea anyway.


Inline image




Re: Recovery mystery

Dale Wegner
 

The NOAA archived wind data for 2/18/20 21Z had a layer of wind below
5,000' coming out of the SSE before resuming its W wind direction
below 2,000' in the Chowchilla area. Attached is wind file.
https://ready.arl.noaa.gov/READYcmet.php

I ran the wind data thru an oldy but goody BALTRK, exported the kml
prediction file for the final landing approach starting at the last
reported aprs position and merged the kml file with the aprs actual
track. KML combined file is attached also. It has a landing only 60
yards NE of its last reported position. This should have been an easy
find.

We have had farmers pickup the payload before the chase team arrives,
and drive off to another field to work. But the aprs tracker
eventually gets a signal out leading the chase team to the farmer. We
have used Spots in the passed with out any problems.

Thanks for this exercise to help sharpen my software skills for our
high school's spring time launch.

On 2/21/20, Hank Riley via Groups.Io <n1ltv=yahoo.com@groups.io> wrote:
[completed first sentence from last message]
Sometimes a reasoned best estimate of the landing spot can mean the
difference between the success or failure of missing balloon recovery
efforts.



Re: Recovery mystery

Hank Riley
 

[completed first sentence from last message]

Sometimes a reasoned best estimate of the landing spot can mean the difference between the success or failure of missing balloon recovery efforts.

Re: Recovery mystery

Hank Riley
 

Sometimes a reasoned best estimate of the landing spot can mean the difference

Here's mine ( both imbedded and attached).  I've annotated the graphic with the last APRS (from aprs.fi) reported altitudes and speeds.  Above sea level elevation of the farmland is around 210 feet so a very small contributor to the simple arithmetic employed to give a landing spot and the larger circular zone that should enclose the real landing spot given uncertainties.

Essentially the last segment labelled X marks a drop of 3.3 k feet.  To drop the remaining 4.9 k feet I've shown a 1.5 X translation almost straight to the east. Actually the average bearing the payload was heading over the last few postions.

As James asked, it would be nice to know the last Spot position.  The more data, the better.  How was road traffic when you were on the way?  Non-existent?

Was the payload marked on the outside with prominent recovery info?  Also the inside?

I realize many people would not go inside a payload, but I think it's a good idea anyway.


Inline image




Re: Recovery mystery

Richard Babington
 

Or void your SPOT warranty by taking it apart and jazzing up your gimbal with a bit of 3D printing ;-)






On Friday, 21 February 2020, 21:31:42 GMT, Jeff Ducklow <jeffducklow@...> wrote:


Feedback on why you might not hear from it:

Not knowing the geography there, are there any water features it could have hit, such as a water filled farm ditch?  A submerged SPOT would explain why you have not heard from it.  

Or it could have landed with the SPOT upright on first contact and then the landing energy caused it to roll on its side or upside down.  As you might know, the SPOT is very orientation sensitive for connecting with satellites. It must have its logo facing up to be reliable and will fail often if it is on its side or upside down. 

Too solve this issue you can make a gimbal out of different sized embroidery bamboo loops (lightweight and cheap) to keep it facing up regardless of how the payload box lands.






Jeff
N0NQN
Merryberry Galactic


On Feb 21, 2020, at 12:58 PM, James Ewen VE6SRV <ve6srv@...> wrote:

I have not used the Spot Trace device, just relaying information that I have heard. No expectation of accuracy is to be assumed.

One of the first stories I read about using the Spot device talked about getting a good lat/long fix from the device, but upon arrival, there was no payload to be found. This baffled the recovery team until they noticed a cellular tower not too far away.

Their supposition was that the Spot device was giving them a location based on the tower, not an actual GPS reading from the device. There was also an instance where the Spot device stopped working on the way down. When they opened the battery case, there was a good suction "pop", and the unit began working. The device was assumed to have depressurized on the way up, but held the vacuum on the rapid descent. The membrane over the soft press buttons got pushed in by the higher external pressure, and the multiple button presses confused the device.

I'm pretty sure this was the same launch/recovery where these two stories came from. They fixed the vacuum issue by drilling a small hole in the case to allow it to vent. I can't recall how they managed to locate the package.

If the Spot device ends up upside down, I hear it might not get a GPS position as well.

Now, what about the APRS tracking you had on board? Did you listen for the transmissions on RF? You should have been able to hear them. From 4900 feet, the horizontal drift wouldn't be much. I would expect to find the payload north of Avenue 24, and south of Avenue 24 1/2. east of road 13, and west of road 14. Even if the GPS on the APRS payload couldn't get a fix, you should be able to track the payload transmitter using RDF techniques. Unless of course you have the payload configured to only transmit with a valid GPS lock.

Find someone with a drone, and have them fly over the suspected landing area with a camera on board. 

Whats' the last Spot location?

James
VE6SRV


On Fri, Feb 21, 2020 at 8:09 AM John Kovac KM6GKF <jkovac@...> wrote:

We did a flight Tuesday in Northern California.   Followed it in flight and arrived at the landing location indicated by Spot Trace within a few minutes of landing.   But it wasn’t there.   Last APRS ping was at about 4900 ft and confirms same general landing area.

The Spot Trace has always led us directly to the exact landing site for all previous flights.  At this point we have searched a large area around the apparent landing site to no avail.   It is open farmland with few structures or people.   

As of right now, a few days post flight, there has been no ping from the Trace since the landing ping.   So that seems to indicate that no one has moved or taken it.  I stupidly did not set it up in advance to do a daily check in ping, so we are not going to get another ping until someone moves it unless the batteries die first, which Trace support guesses will be a few months.  And if that ping is in the same location we’ll still be baffled.

Any input greatly appreciated.

Best,

John Kovac




Re: Recovery mystery

James Ewen VE6SRV
 

Based on the APRS track, guessing that KM6GKF-11 was the payload, I'd say the payload is in this field.


It would be easy to spot if the field still looks like this, but there may be some type of crop growing there now, which allows the payload to hide between the rows of plants.

There is one long narrow water hazard that might have beckoned to the payload... https://goo.gl/maps/Ep7VqbHwE5fUmJ8x8 


James
VE6SRV


On Fri, Feb 21, 2020 at 2:32 PM Jeff Ducklow <jeffducklow@...> wrote:
Feedback on why you might not hear from it:

Not knowing the geography there, are there any water features it could have hit, such as a water filled farm ditch?  A submerged SPOT would explain why you have not heard from it.  

Or it could have landed with the SPOT upright on first contact and then the landing energy caused it to roll on its side or upside down.  As you might know, the SPOT is very orientation sensitive for connecting with satellites. It must have its logo facing up to be reliable and will fail often if it is on its side or upside down. 

Too solve this issue you can make a gimbal out of different sized embroidery bamboo loops (lightweight and cheap) to keep it facing up regardless of how the payload box lands.






Jeff
N0NQN
Merryberry Galactic


On Feb 21, 2020, at 12:58 PM, James Ewen VE6SRV <ve6srv@...> wrote:

I have not used the Spot Trace device, just relaying information that I have heard. No expectation of accuracy is to be assumed.

One of the first stories I read about using the Spot device talked about getting a good lat/long fix from the device, but upon arrival, there was no payload to be found. This baffled the recovery team until they noticed a cellular tower not too far away.

Their supposition was that the Spot device was giving them a location based on the tower, not an actual GPS reading from the device. There was also an instance where the Spot device stopped working on the way down. When they opened the battery case, there was a good suction "pop", and the unit began working. The device was assumed to have depressurized on the way up, but held the vacuum on the rapid descent. The membrane over the soft press buttons got pushed in by the higher external pressure, and the multiple button presses confused the device.

I'm pretty sure this was the same launch/recovery where these two stories came from. They fixed the vacuum issue by drilling a small hole in the case to allow it to vent. I can't recall how they managed to locate the package.

If the Spot device ends up upside down, I hear it might not get a GPS position as well.

Now, what about the APRS tracking you had on board? Did you listen for the transmissions on RF? You should have been able to hear them. From 4900 feet, the horizontal drift wouldn't be much. I would expect to find the payload north of Avenue 24, and south of Avenue 24 1/2. east of road 13, and west of road 14. Even if the GPS on the APRS payload couldn't get a fix, you should be able to track the payload transmitter using RDF techniques. Unless of course you have the payload configured to only transmit with a valid GPS lock.

Find someone with a drone, and have them fly over the suspected landing area with a camera on board. 

Whats' the last Spot location?

James
VE6SRV


On Fri, Feb 21, 2020 at 8:09 AM John Kovac KM6GKF <jkovac@...> wrote:

We did a flight Tuesday in Northern California.   Followed it in flight and arrived at the landing location indicated by Spot Trace within a few minutes of landing.   But it wasn’t there.   Last APRS ping was at about 4900 ft and confirms same general landing area.

The Spot Trace has always led us directly to the exact landing site for all previous flights.  At this point we have searched a large area around the apparent landing site to no avail.   It is open farmland with few structures or people.   

As of right now, a few days post flight, there has been no ping from the Trace since the landing ping.   So that seems to indicate that no one has moved or taken it.  I stupidly did not set it up in advance to do a daily check in ping, so we are not going to get another ping until someone moves it unless the batteries die first, which Trace support guesses will be a few months.  And if that ping is in the same location we’ll still be baffled.

Any input greatly appreciated.

Best,

John Kovac




Re: Recovery mystery

Jeff Ducklow
 

Feedback on why you might not hear from it:

Not knowing the geography there, are there any water features it could have hit, such as a water filled farm ditch?  A submerged SPOT would explain why you have not heard from it.  

Or it could have landed with the SPOT upright on first contact and then the landing energy caused it to roll on its side or upside down.  As you might know, the SPOT is very orientation sensitive for connecting with satellites. It must have its logo facing up to be reliable and will fail often if it is on its side or upside down. 

Too solve this issue you can make a gimbal out of different sized embroidery bamboo loops (lightweight and cheap) to keep it facing up regardless of how the payload box lands.






Jeff
N0NQN
Merryberry Galactic


On Feb 21, 2020, at 12:58 PM, James Ewen VE6SRV <ve6srv@...> wrote:

I have not used the Spot Trace device, just relaying information that I have heard. No expectation of accuracy is to be assumed.

One of the first stories I read about using the Spot device talked about getting a good lat/long fix from the device, but upon arrival, there was no payload to be found. This baffled the recovery team until they noticed a cellular tower not too far away.

Their supposition was that the Spot device was giving them a location based on the tower, not an actual GPS reading from the device. There was also an instance where the Spot device stopped working on the way down. When they opened the battery case, there was a good suction "pop", and the unit began working. The device was assumed to have depressurized on the way up, but held the vacuum on the rapid descent. The membrane over the soft press buttons got pushed in by the higher external pressure, and the multiple button presses confused the device.

I'm pretty sure this was the same launch/recovery where these two stories came from. They fixed the vacuum issue by drilling a small hole in the case to allow it to vent. I can't recall how they managed to locate the package.

If the Spot device ends up upside down, I hear it might not get a GPS position as well.

Now, what about the APRS tracking you had on board? Did you listen for the transmissions on RF? You should have been able to hear them. From 4900 feet, the horizontal drift wouldn't be much. I would expect to find the payload north of Avenue 24, and south of Avenue 24 1/2. east of road 13, and west of road 14. Even if the GPS on the APRS payload couldn't get a fix, you should be able to track the payload transmitter using RDF techniques. Unless of course you have the payload configured to only transmit with a valid GPS lock.

Find someone with a drone, and have them fly over the suspected landing area with a camera on board. 

Whats' the last Spot location?

James
VE6SRV


On Fri, Feb 21, 2020 at 8:09 AM John Kovac KM6GKF <jkovac@...> wrote:

We did a flight Tuesday in Northern California.   Followed it in flight and arrived at the landing location indicated by Spot Trace within a few minutes of landing.   But it wasn’t there.   Last APRS ping was at about 4900 ft and confirms same general landing area.

The Spot Trace has always led us directly to the exact landing site for all previous flights.  At this point we have searched a large area around the apparent landing site to no avail.   It is open farmland with few structures or people.   

As of right now, a few days post flight, there has been no ping from the Trace since the landing ping.   So that seems to indicate that no one has moved or taken it.  I stupidly did not set it up in advance to do a daily check in ping, so we are not going to get another ping until someone moves it unless the batteries die first, which Trace support guesses will be a few months.  And if that ping is in the same location we’ll still be baffled.

Any input greatly appreciated.

Best,

John Kovac




Re: Recovery mystery

James Ewen VE6SRV
 

I have not used the Spot Trace device, just relaying information that I have heard. No expectation of accuracy is to be assumed.

One of the first stories I read about using the Spot device talked about getting a good lat/long fix from the device, but upon arrival, there was no payload to be found. This baffled the recovery team until they noticed a cellular tower not too far away.

Their supposition was that the Spot device was giving them a location based on the tower, not an actual GPS reading from the device. There was also an instance where the Spot device stopped working on the way down. When they opened the battery case, there was a good suction "pop", and the unit began working. The device was assumed to have depressurized on the way up, but held the vacuum on the rapid descent. The membrane over the soft press buttons got pushed in by the higher external pressure, and the multiple button presses confused the device.

I'm pretty sure this was the same launch/recovery where these two stories came from. They fixed the vacuum issue by drilling a small hole in the case to allow it to vent. I can't recall how they managed to locate the package.

If the Spot device ends up upside down, I hear it might not get a GPS position as well.

Now, what about the APRS tracking you had on board? Did you listen for the transmissions on RF? You should have been able to hear them. From 4900 feet, the horizontal drift wouldn't be much. I would expect to find the payload north of Avenue 24, and south of Avenue 24 1/2. east of road 13, and west of road 14. Even if the GPS on the APRS payload couldn't get a fix, you should be able to track the payload transmitter using RDF techniques. Unless of course you have the payload configured to only transmit with a valid GPS lock.

Find someone with a drone, and have them fly over the suspected landing area with a camera on board. 

Whats' the last Spot location?

James
VE6SRV


On Fri, Feb 21, 2020 at 8:09 AM John Kovac KM6GKF <jkovac@...> wrote:

We did a flight Tuesday in Northern California.   Followed it in flight and arrived at the landing location indicated by Spot Trace within a few minutes of landing.   But it wasn’t there.   Last APRS ping was at about 4900 ft and confirms same general landing area.

The Spot Trace has always led us directly to the exact landing site for all previous flights.  At this point we have searched a large area around the apparent landing site to no avail.   It is open farmland with few structures or people.   

As of right now, a few days post flight, there has been no ping from the Trace since the landing ping.   So that seems to indicate that no one has moved or taken it.  I stupidly did not set it up in advance to do a daily check in ping, so we are not going to get another ping until someone moves it unless the batteries die first, which Trace support guesses will be a few months.  And if that ping is in the same location we’ll still be baffled.

Any input greatly appreciated.

Best,

John Kovac

Recovery mystery

John Kovac KM6GKF
 

We did a flight Tuesday in Northern California.   Followed it in flight and arrived at the landing location indicated by Spot Trace within a few minutes of landing.   But it wasn’t there.   Last APRS ping was at about 4900 ft and confirms same general landing area.

The Spot Trace has always led us directly to the exact landing site for all previous flights.  At this point we have searched a large area around the apparent landing site to no avail.   It is open farmland with few structures or people.   

As of right now, a few days post flight, there has been no ping from the Trace since the landing ping.   So that seems to indicate that no one has moved or taken it.  I stupidly did not set it up in advance to do a daily check in ping, so we are not going to get another ping until someone moves it unless the batteries die first, which Trace support guesses will be a few months.  And if that ping is in the same location we’ll still be baffled.

Any input greatly appreciated.

Best,

John Kovac

Another found payload

Mark Conner N9XTN
 


The payload was stuck in a tree for a couple of months in northern New Jersey before the homeowner decided to pull it out of the tree (it was 40' up).  It's a Raspberry Pi payload that used a Verizon hotspot to communicate.  The SD card in the Pi was broken and apparently unreadable.  

The word "Atticus" appears to be written (somewhat poorly) in Sharpie on the Pi itself.

Unfortunately without any date information it'll be hard to correlate where the payload might have been launched.

73 de Mark N9XTN

Re: FW: Air Force Pilot Sends Ring to Space in Epic Marriage Proposal

Mark Conner N9XTN
 

I'm guessing it wasn't ham radio as his name is not associated with a callsign.  But he could have a friend who does that.  

73 de Mark N9XTN


On Thu, Feb 13, 2020 at 2:21 PM Garrett, Mark <ma-garrett@...> wrote:
I was wondering how it was being tracked as it lacked that information in the article. 

Mark

On Thu, Feb 13, 2020 at 1:54 PM James Ewen VE6SRV <ve6srv@...> wrote:
Chicken!

We sent up the real ring and retrieved it. 

I haven’t asked how much the ring was worth. There was enough pressure just making sure we retrieved the payload. 

I blew out a calf muscle walking in to the field to retrieve the payload. Just about needed to have the ring owner come out and carry me back to my truck!



On Thu, Feb 13, 2020 at 8:10 AM Mark Conner N9XTN <mconner1@...> wrote:
https://www.military.com/daily-news/2020/02/12/air-force-pilot-sends-ring-space-epic-marriage-proposal.html

https://www.youtube.com/watch?v=22FtHdVJ7hE

Near space, actually - it was a weather balloon flight from Missouri I
believe.  Launched by a B-2 pilot assigned to Whiteman AFB.

73 de Mark N9XTN



--
James
VE6SRV



--
Mark Garrett
Tri States Public Radio

Re: FW: Air Force Pilot Sends Ring to Space in Epic Marriage Proposal

Garrett, Mark
 

I was wondering how it was being tracked as it lacked that information in the article. 

Mark

On Thu, Feb 13, 2020 at 1:54 PM James Ewen VE6SRV <ve6srv@...> wrote:
Chicken!

We sent up the real ring and retrieved it. 

I haven’t asked how much the ring was worth. There was enough pressure just making sure we retrieved the payload. 

I blew out a calf muscle walking in to the field to retrieve the payload. Just about needed to have the ring owner come out and carry me back to my truck!



On Thu, Feb 13, 2020 at 8:10 AM Mark Conner N9XTN <mconner1@...> wrote:
https://www.military.com/daily-news/2020/02/12/air-force-pilot-sends-ring-space-epic-marriage-proposal.html

https://www.youtube.com/watch?v=22FtHdVJ7hE

Near space, actually - it was a weather balloon flight from Missouri I
believe.  Launched by a B-2 pilot assigned to Whiteman AFB.

73 de Mark N9XTN



--
James
VE6SRV



--
Mark Garrett
Tri States Public Radio

Re: FW: Air Force Pilot Sends Ring to Space in Epic Marriage Proposal

James Ewen VE6SRV
 

Chicken!

We sent up the real ring and retrieved it. 

I haven’t asked how much the ring was worth. There was enough pressure just making sure we retrieved the payload. 

I blew out a calf muscle walking in to the field to retrieve the payload. Just about needed to have the ring owner come out and carry me back to my truck!



On Thu, Feb 13, 2020 at 8:10 AM Mark Conner N9XTN <mconner1@...> wrote:
https://www.military.com/daily-news/2020/02/12/air-force-pilot-sends-ring-space-epic-marriage-proposal.html

https://www.youtube.com/watch?v=22FtHdVJ7hE

Near space, actually - it was a weather balloon flight from Missouri I
believe.  Launched by a B-2 pilot assigned to Whiteman AFB.

73 de Mark N9XTN



--
James
VE6SRV

FW: Air Force Pilot Sends Ring to Space in Epic Marriage Proposal

Mark Conner N9XTN
 

https://www.military.com/daily-news/2020/02/12/air-force-pilot-sends-ring-space-epic-marriage-proposal.html

https://www.youtube.com/watch?v=22FtHdVJ7hE

Near space, actually - it was a weather balloon flight from Missouri I
believe. Launched by a B-2 pilot assigned to Whiteman AFB.

73 de Mark N9XTN

Re: Unknown weather balloon payload from 2017 launch found in NC

Garrett, Mark
 

Fantastic!

On Thu, Jan 16, 2020 at 8:29 PM Mark Conner N9XTN <mconner1@...> wrote:
The payload owner has been found - don't know any more details than that at the moment.


73 de Mark N9XTN 

On Sun, Jan 12, 2020 at 11:28 AM Mark Conner <mconner1@...> wrote:

This appears to have been a flight launched late morning on July 5, 2017 according to the timestamps visible in the Facebook photos.  I think it was a GoPro camera, photo filenames begin with "G".  T-shirt on the guy that launched it is for a shop in Charlottesville VA.  Payload was found about a week ago near Statesville NC.

73 de Mark N9XTN

 



--
Mark Garrett
Tri States Public Radio
WIUM Macomb, IL
WIUW Warsaw, IL
WVKC Galesburg, IL
K292GR Burlington, IA
Office (309) 298-1104
Cell    (309) 255-6987
Fax    (309) 298-2133

Re: Unknown weather balloon payload from 2017 launch found in NC

Mark Conner N9XTN
 

The payload owner has been found - don't know any more details than that at the moment.


73 de Mark N9XTN 


On Sun, Jan 12, 2020 at 11:28 AM Mark Conner <mconner1@...> wrote:

This appears to have been a flight launched late morning on July 5, 2017 according to the timestamps visible in the Facebook photos.  I think it was a GoPro camera, photo filenames begin with "G".  T-shirt on the guy that launched it is for a shop in Charlottesville VA.  Payload was found about a week ago near Statesville NC.

73 de Mark N9XTN

 

Re: Unknown weather balloon payload from 2017 launch found in NC

Mark Conner N9XTN
 

Hank's posted nudged me to go have a look at the archived analysis data (go to ready.arl.noaa.gov and selected "Archived Meteorology" on the left).  

With the relatively light winds out of the west, I would guess the launch site was along I-40 east of or near Asheville.  

73 de Mark N9XTN

image.png
 PRESS HGT(MSL) TEMP DEW PT  WND DIR  WND SPD
 HPA       M      C     C       DEG     M/S
 E = Estimated Surface Height

  973.   405.E  27.8   22.9   233.3     1.5
  950.   618.   24.5   22.4   259.1     1.7
  925.   852.   22.4   21.1   274.7     2.9
  900.  1090.   20.8   19.1   291.3     6.4
  875.  1334.   19.4   16.9   295.3     9.5
  850.  1583.   17.7   14.5   294.7    11.5
  825.  1838.   16.0   11.5   293.4    12.6
  800.  2100.   14.6    8.3   291.2    12.8
  775.  2368.   13.6    5.1   286.1    12.6
  750.  2643.   12.6    2.2   281.6    12.6
  725.  2927.   11.0   -0.1   280.1    12.8
  700.  3219.    9.1   -1.5   279.1    12.8
  650.  3828.    5.0   -4.2   277.4    12.6
  600.  4476.    1.1   -8.0   277.3    11.9
  550.  5170.   -2.8  -12.8   282.2     9.8
  500.  5920.   -6.5  -17.4   281.2     7.0
  450.  6736.  -11.6  -23.6   264.0     7.7
  400.  7627.  -17.4  -28.0   261.5     9.9
  350.  8614.  -23.6  -33.6   271.5     9.4
  300.  9725.  -31.0  -44.8   287.4     3.4
  250. 10990.  -41.7  -53.3   276.5     2.3
  200. 12460.  -53.0  -61.2   284.5     6.7
  150. 14252.  -67.1  -72.2   268.5    11.1
  100. 16654.  -69.8  -79.5   282.2     5.0
   50. 20892.  -59.2  -81.6    88.1     7.8
  


On Sun, Jan 12, 2020 at 2:04 PM Hank Riley via Groups.Io <n1ltv=yahoo.com@groups.io> wrote:
Inline image



Inline image


_________________________________________________________________________________



This appears to have been a flight launched late morning on July 5, 2017 according to the timestamps visible in the Facebook photos.  I think it was a GoPro camera, photo filenames begin with "G".  T-shirt on the guy that launched it is for a shop in Charlottesville VA.  Payload was found about a week ago near Statesville NC.

73 de Mark N9XTN

 

Re: Unknown weather balloon payload from 2017 launch found in NC

Hank Riley
 

Inline image



Inline image


_________________________________________________________________________________



This appears to have been a flight launched late morning on July 5, 2017 according to the timestamps visible in the Facebook photos.  I think it was a GoPro camera, photo filenames begin with "G".  T-shirt on the guy that launched it is for a shop in Charlottesville VA.  Payload was found about a week ago near Statesville NC.

73 de Mark N9XTN