<div dir="ltr"><div><div>It was really great fun -- we had a convoy of Noisebridge And Proximal Nodes folk going down, and even though we didn't really see much in the fog (the fog that was later blamed for the landing leg failure on the stage 1 return -- <a href="http://www.popsci.com/watch-spacexs-falcon-9-rocket-land-on-drone-ship-then-tip-over">http://www.popsci.com/watch-spacexs-falcon-9-rocket-land-on-drone-ship-then-tip-over</a> boooo), the /extremely hard-to-describe sound of a rocket lifting off, the spectacle of hundreds of space fans lining a stretch of road and blinking into the distance, and the chance to see so many SF hackers more than made up for it.<br><br></div>Thank you everyone!<br><br></div>d.<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 17, 2016 at 7:33 PM, Michael Toren <span dir="ltr"><<a href="mailto:mct@toren.net" target="_blank">mct@toren.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Someone had the internet stream going from the viewing area, but from there<br>
it was about a full two minutes behind.<br>
<br>
My VX-7R couldn't receive on 368.300, but my friend's VX-8R could! So<br>
we piped though someone's SUV sound system parked next to us, and pumped<br>
up the volume, which was nice. That frequency only covered Falcon during<br>
the early flight. We heard MECO, separation, traffic about stage two<br>
performing well, and some traffic about stage1 firing again, presumably to<br>
return to the barge, but I'm not certain. It did not cover the Falcon9<br>
landing at the barge, which was unfortunate. As someone pointed out, by<br>
that far into the launch, it's not really a Vandenberg AFB problem :-)<br>
<br>
There was no visibility. We were on Ocean Road, perhaps a quarter mile<br>
away from the barricade. Loud roar of the engines, but never saw it behind<br>
the fog and cloud cover. The cows (and goats, I hear) were significantly<br>
freaked out about the whole thing and started running around, charging away<br>
from the hill that obstructed our view of the pad.<br>
<br>
Space!<br>
<br>
~mct<br>
<div class="HOEnZb"><div class="h5"><br>
On Sun, Jan 17, 2016 at 11:39:27AM -0800, Henner Zeller wrote:<br>
> Watching <a href="http://www.spacex.com/webcast/" rel="noreferrer" target="_blank">http://www.spacex.com/webcast/</a> from home ...<br>
><br>
> On 17 January 2016 at 11:35, Alex Merlin Glowaski<br>
> <<a href="mailto:alex.glowaski@gmail.com">alex.glowaski@gmail.com</a>> wrote:<br>
> > WOOOOOOOOOO<br>
> ><br>
> > On Jan 17, 2016 10:39 AM, "Michael Toren" <<a href="mailto:mct@toren.net">mct@toren.net</a>> wrote:<br>
> >><br>
> >> A spacex guy here was listening from a scanner, directly from mission<br>
> >> control on 368.300. My HT can't receive on that band Next time :-) someone<br>
> >> theorized it might be from Vandenberg, the 30th Space Wing simulcasting.<br>
> >><br>
> >> ~mobilemct<br>
> >><br>
> >> On January 17, 2016 9:58:56 AM PST, Adrian Chadd <<a href="mailto:adrian.chadd@gmail.com">adrian.chadd@gmail.com</a>><br>
> >> wrote:<br>
> >>><br>
> >>> I'll be on 146.580<br>
> >>><br>
> >>> On Jan 17, 2016 6:32 AM, "Michael Toren" <<a href="mailto:mct@toren.net">mct@toren.net</a>> wrote:<br>
> >>>><br>
> >>>> Latest update from the launch-alert mailing list:<br>
> >>>><br>
> >>>> > This morning's planned launch of a Falcon 9 rocket from Vandenberg<br>
> >>>> > AFB appears to be on schedule. Liftoff is planned for 10:42:18<br>
> >>>> a.m.<br>
> >>>> > PST, the start of a 30-second launch window.<br>
> >>>> ><br>
> >>>> > If you will be using optical assistance (binoculars, telescope,<br>
> >>>> etc.)<br>
> >>>> > to view the launch, try following the first stage after stage 1/2<br>
> >>>> > separation. You may be able to follow the stage part or much of<br>
> >>>> its<br>
> >>>> > way down to its attempted landing on a barge in the ocean.<br>
> >>>><br>
> >>>> ~mct<br>
> >>>><br>
> >>>> On Sat, Jan 16, 2016 at 11:50:32PM -0800, Michael Toren wrote:<br>
> >>>> > , from 2003. Brian runs the "launch<br>
> >>>> > alert" list (<a href="http://mailman.qth.net/mailman/listinfo/launch-alert" rel="noreferrer" target="_blank">http://mailman.qth.net/mailman/listinfo/launch-alert</a>),<br>
> >>>> > where<br>
> >>>> > you can learn about upcoming Vandenberg activity. (Very good list,<br>
> >>>> > highly<br>
> >>>> > recommended!) Getting ready for another launch last year, I pinged<br>
> >>>> > Brian<br>
> >>>> > asking if there was any way to tune into the countdown. He replied:<br>
> >>>> ><br>
> >>>> > > Providing Vandenberg launch status info over ham radio is<br>
> >>>> > something<br>
> >>>> > > that is not actively encouraged. As a matter of fact, one ham<br>
> >>>> > radio<br>
> >>>> > > repeater in Santa Barbara prohibited this activity.<br>
> >>>> > ><br>
> >>>> > > Why can't you use an I-phone and listen to the launch over the<br>
> >>>> > > Internet from NASA TV, Spaceflightnow.com, or the United Launch<br>
> >>>> > > Alliance web site?<br>
> >>>> ><br>
> >>>> > So, we'll see. I really hope it works! I don't have a clear memory<br>
> >>>> > of us<br>
> >>>> > trying the repeaters last time, but I'm sure we must have. We brought<br>
> >>>> > our<br>
> >>>> > radios this trip, anyway, just in case. :-)<br>
> >>>> ><br>
> >>>> > ~mct<br>
> >>>> > _______________________________________________<br>
> >>>> > Noisebridge-discuss mailing list<br>
> >>>> > <a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a><br>
> >>>> > <a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" rel="noreferrer" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
> >>>> _______________________________________________<br>
> >>>> Noisebridge-discuss mailing list<br>
> >>>> <a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a><br>
> >>>> <a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" rel="noreferrer" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> Noisebridge-discuss mailing list<br>
> >> <a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a><br>
> >> <a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" rel="noreferrer" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
> >><br>
> ><br>
> > _______________________________________________<br>
> > Noisebridge-discuss mailing list<br>
> > <a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a><br>
> > <a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" rel="noreferrer" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
> ><br>
_______________________________________________<br>
Noisebridge-discuss mailing list<br>
<a href="mailto:Noisebridge-discuss@lists.noisebridge.net">Noisebridge-discuss@lists.noisebridge.net</a><br>
<a href="https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss" rel="noreferrer" target="_blank">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</a><br>
<br>
<br>
</div></div></blockquote></div><br></div>