Feed on

I feel remiss if I didn’t mention something that was brought to my attention in a comment on my last post.  Back in February I drove down to Vandenberg Air Force Base to photograph the launch of a test Minuteman III ICBM. This was the second one I’ve done, the last being in July last summer.  These happen 3-4 times a year on just a couple of days notice, with a very long launch window, so you have to be ready to drive down and sit it out for however many hours it could take. There was one in the fall that I missed, I think I didn’t see the press release until it was already done.

So I took a long exposure photograph of the missile launching and heading out over the Pacific. I posted the photos to Twitter because there’s a lot of space nerds on there.  I drove home and didn’t think much about it.  Later I get a heads up that my photos got linked from an RT.com (f/k/a Russia Today) article.

The article was about the missile test, and goes on talking about increased missile tension, accusations being thrown around, and missile treaties between the US and Russia. There was my Twitter post, right in the middle of it all.

Well then!  That was unexpected.  The main photo at the top of the article from Reuters looked very similar to mine, and for a minute I thought they had ripped my photo off without credit.  Looking closer, it’s taken at exactly the same location but shows a different launch.

Fortunately my post didn’t get any crazy attention beyond a few likes and extra followers. I didn’t have any visitors and haven’t had any new shady people try to be my friends. It makes for a good story and gets people to say “wait, what?” until I show them the article.

Welcome 2019

I feel like I haven’t done much that’s post-worthy the past couple of months. Maybe I have. Oh well, just checking to make sure the website still works. It does!

Thefted firewood and rope

After my last camping trip, I was hauling around three boxes of leftover firewood, a 20 L water jug, and my camping chair in the back of my truck for a couple of weeks. After I left the Sharks game at SAP Center last night, I noticed it was all gone. It was a lot of stuff to move, I suspect somebody just lifted it out of my truck into theirs. They at least left the big jug of cat litter I had just bought.

Sure, leaving it back there it was bound to happen. It’s way better than having the truck itself broken into. I’m mostly annoyed that they got my water can, but oddly I’m more annoyed they stole my 20′ rope that was used to tie it all down with. I realized this morning they also got the 5′ of chain used for my rifle gong too. Who steals rope and chain?


Earlier this year I came across some yearbooks from my school (Kinta High School) in the 1930s. Some belonged to my grandma, a couple from her brother that was killed right out of high school in WWII, and others loaned from family friends. I learned a few things in the process, such as the location and look of the old school buildings, the tea socials, the integration of the Lewisville school, and the impact of the war that crept into their pages. Earlier books had photos glued to the pages, hand colored title pages, and hand drawn ads!

I decided to scan them in so there were good electronic copies available for people to view. Dad also had quite a collection from the 50s, 60s, and beyond, so I started scanning those in too. In some years a yearbook was not published, usually to lack of budget; often the next year’s book will have a page devoted to the seniors that graduated the year no book was published. As I get time when I go home I’ll scan more.

What I have scanned so far is up on Flickr

I’ve tried to be complete and scan every page at least at 300 dpi, and I have only done little, if any, touch up work to them. The more recent ones aren’t as high a quality that I wanted (at least toward the inner edge), it was difficult to put them on a flatbed scanner without destroying the binding. I want these to be available to anyone without restraint. If they’re taken down from Flickr, I will host them on my own or find some other place for them. Tagging names on all the pages would be a nice to-do item!

Kinta Public Schools, Kinta High School, Kinta, Oklahoma

Throwing another tidbit of recently found knowledge out here. Along the way with playing different certs on my EAP-TLS I wound up removing the 802.1x password entry from the OS X Keychain (at the time thinking it would help my problem). What I discovered after that, even after reverting my RADIUS server config, I couldn’t connect back to my test SSID. OS X just threw a “unable to join network” message immediately and gave up. I couldn’t figure out why I couldn’t connect back, what would be keeping state about this network.

802.1x entry

The TL;DR is I went into System Preferences > Network > Wi-Fi and told it to forget about my test SSID. After this I was prompted for the username/password on my network when I retried it.

(Actually I’m not even sure how I got in this situation. I just deleted this again and I was able to rejoin the network?)

Along the way I found out the Wireless Diagnostic tool on OS X is actually nice and useful, you wouldn’t think it from the surface. It collects a ton of logs and even packet captures to review. From what I gathered from the internets I needed to look for “eapolclient” logging. In this case eapolclient was reporting “Acquired: cannot prompt for missing user name”. I didn’t get many leads hunting for this message. It wasn’t until I thought about the forgetting thing that fixed my problem.

eapolclient “cannot prompt for missing user name”

Yay, fixed.


Not really relevant to the post, but I found it amusing

You think you know something just enough to get by, until you have something that challenges your workflow and tools. Then you have to brush away the cobwebs, learn a few things, and work on some scripts. Based upon my recent adventures in dealing with EAP-TLS for wireless, I realized I was doing several things wrong with OpenSSL and my private certificate authority (CA) over the years. I never really spent any time reading good docs beyond creating cert requests and converting certificates, nor learning what all the options and extensions do.

I found a great instruction guide on how to properly set up not only a CA with OpenSSL, but an intermediate CA, revocation lists, and certificates for servers and users: https://jamielinux.com/docs/openssl-certificate-authority/. It goes a good job of explaining just the options you need and why.

Based on this guide and copious amounts of Googling to fix other problems I set about putting my CA house in order. Among other things, I wanted to make sure I was generating appropriate certs and finally get around to stop doing some things by hand. (And insert an intermediate CA to my setup for giggles because my home lab isn’t complicated enough Never mind, dealing with certificate chains and applications are annoying.)


Things I learned while yak shaving certificates, all in one place so hopefully other people can avoid my folly:

(disclaimer: I’m possibly wrong about some of this)

iOS needs a common name on certs to trust them: This is what started it all. On Apple iOS devices (unsure when this started, iOS 11?) if your private root CA certificate does not have a Common Name (CN) value set, you will not be able to trust the certificate on the device. Without a CN, the certificate just does not show up under General > About > Certificate Trust Settings > Enable Full Trust For Root Certificates. You can install the root certificate all day long, but you can’t get device-level trust without this.

Certificate Trust Settings: No CN on root cert


Certificate Trust Settings: root cert has CN

Can’t just casually add a CN: Based on what I read for regenerating a root certificate with the same key, I thought I might be able to issue a new root cert and fix the CN. Turns out you can’t just add the CN on your existing root CA certificate because this breaks the chain of trust of any certificates you’ve signed with it. In particular, OpenSSL is going to throw an “unable to get local issuer certificate” when it tries to verify a signed certificate against your newly altered root certificate:

# Existing cert, newly modified root, verification fails:
# openssl verify -CAfile /opt/pki/CA/certs/wannnet-ca-20180913-cert.pem \
certs/raptor.wann.net-20170624-cert.pem: C = US, ST = California, L = Fremont, O = wann.net, CN = raptor.wann.net, emailAddress = pki@wann.net
error 20 at 0 depth lookup:unable to get local issuer certificate

# Existing cert, original root, verification is OK:
# openssl verify -CAfile /opt/pki/CA/certs/wannnet-ca-20170624-cert.pem \
certs/raptor.wann.net-20170624-cert.pem: OK

This is because the Issuer: of our root certificates has changed and mismatched what the cert expects:

# Existing server certificate, signed with original root CA (without a CN):
# openssl x509 -in certs/raptor.wann.net-20170624-cert.pem -text | grep Issuer
        Issuer: C=US, ST=California, L=Fremont, O=wann.net, OU=wann.net CA/emailAddress=pki@wann.net

# Issuer: of original root CA certificate:
# openssl x509 -in wannnet-ca-20170624-cert.pem -text | grep Issue
        Issuer: C=US, ST=California, L=Fremont, O=wann.net, OU=wann.net CA/emailAddress=pki@wann.net

# Issuer: of new root CA certificate with a proper CN added:
# openssl x509 -in wannnet-ca-20180913-cert.pem -text | grep Issue
        Issuer: C=US, ST=California, L=Fremont, O=wann.net, OU=wann.net CA, CN=wann.net Root CA/emailAddress=pki@wann.net

This means unless you re-issue every single certificate you have to reflect the new CN on the root cert, you’re going to be carrying around both root CA certificates in your devices’ trust stores until the child certificates eventually expire and you re-issue/re-sign them with the new root certificate. (2 years for me).

Upgrading signature algorithm on the root: However! Allegedly you can regenerate the root CA certificate with different signatures (the SHA1 -> SHA256 signature fracas recently) or new validity periods as long as you use the same key file you originally created the self signed cert with. You just can’t change the subject or CN details. (I wish I had known this before reissuing all of my client certs last year when I needed SHA256 signatures)

Adding subjectAltNames is messy: Somewhere along the way browsers such as Chrome started requiring valid Subject Alternative Name (SAN) on TLS certificates. For our purposes this is a list of DNS names (e.g. CNAMEs) that the certificate is valid with.

There’s not an easy way to add this to certificate requests (yet*), and every example on the Internet has you cracking open openssl.cnf in a text editor every time you want a new cert (what could go wrong?!). For a while I did this, I couldn’t be bothered learning a better way and hated myself each time I made a cert.  There’s also some convoluted bash “one-line” scripts out there that attempt to remedy this, but they’re hard to follow what they’re doing until you understand what they’re doing.

Of course my script is better than everyone else’s script: https://github.com/bwann/pki-tools/blob/master/make-wannnet-csrkey.sh. I’ve tried to simplify the bash and make it a little easier to understand. For the skeptical, here’s some sample output.

This script generates an RSA key and certificate request with the server name/common name as the first argument to the script, and any further arguments adds them to the request as Subject Alternative Names.

[1] As of OpenSSL 1.1.1 just released in September 2018, they’ve tweaked the req -extension option to make this a bit easier: https://github.com/openssl/openssl/commit/bfa470a4f64313651a35571883e235d3335054eb

CAs drop subjectAltNames when signing: By default OpenSSL will drop any user-submitted extensions (such as subjectAltNames) from a certificate request when it comes time to sign the certificate with your CA. This means when you sign a certificate request that includes your alternative names, this undoes all the work you just did to add them. Now you’ve got to re-supply the subjectAltNames via the OpenSSL config somehow as seen above for the signing process. There’s a good reason for this behavior, preventing unwanted user input: a rogue user could submit a certificate request with an extension something like basicConstraints=CA:TRUE, and unless it’s caught at signing time, the root has just issued a CA certificate.

You can get around this in your own CA environment by configuring copy_extensions in your openssl.cnf under the CA_default section. There’s a couple of options for this and the man page (man ca) has clear warnings about the implications. By setting this to copy_extensions=copy, this will copy the subjectAltNames from the certificate request; however you will want to make sure whichever extensions you’re using to sign a certificate, you’ve already nailed down basicConstraints and keyUsage in them so the extensions from the request don’t try to overwrite them.

Key extensions for servers and clients: This is what I first learned while setting up certificates for EAP-TLS. There’s extensions you can add to the X509 certificate that tell what the intended purpose of the certificate is (man x509v3_config). I haven’t ever had to use these because Linux has always been pretty happy (blissfully ignorant?) with what I was using before. Apparently things like Windows and Android cares about these extensions, i.e. they expect a server cert on the server, a client cert on the client app.

Ideally in your openssl.cnf you’d have a section defining options to use while signing a certificate for servers (e.g. [ server_cert ], and another section for client/user certificates (e.g. [ user_cert ], each containing the appropriate extendedKeyUsage settings for each type. Then when it comes time to sign a cert, tell OpenSSL which extension to use.

Android needs magic to install a root CA with system level trust. I haven’t gone through the effort to figure this one out yet, every time I install my root CA certificate on my Nexus it only winds up as a user-level cert, and displays a fabulous “warning third parties are snooping on your network” notification. From what I gather some root-level muckery needs to happen. Surely some MDM software has figured this out already.


https://github.com/bwann/pki-tools/ : Some of my own scripts for generating cert requests, keys, signing them with an OpenSSL CA. Server-centric for now, still ironing out the kinks in user certificates for now and will post whenever they’re decent.

https://www.phildev.net/ssl/ : A friend’s guide to X509 certs that I had forgotten about until I posted this

https://jamielinux.com/docs/openssl-certificate-authority/ : The other CA setup guide I mentioned at the beginning of this post

If you’ve ever tried setting up FreeRADIUS and WPA2-Enterprise, and wondered how the example certs wind up with the X509v3 extended key “TLS Web Server Authentication” on it, the trick here is a config file specifying a numerical OID for the key instead of a text description. (Apparently Windows expects to see these TLS extended keys when connecting to a wireless network with EAP/TLS).

This puzzled me for a while, I’ve never seen this key and couldn’t figure out how they were getting it on their certs. It’s obvious now, but I spent way longer than I care to admit carefully combing over the example *.cnf files that came with the package, my system’s openssl.cnf, another system’s pristine openssl.cnf for any missing extendedKeyUsage or nsCertType directives, and the OpenSSL manual page for x509 looking for any missed defaults. It wasn’t until I carefully followed the Makefile in the example that they were pulling in an extension file via -extfile xpextensions and using an section with -extensions xpserver_ext that were specifying the options as OIDs. I had overlooked this file in earlier spelunking. Mystery solved.


P.S. this dude wrote an incredibly detailed instruction guide on a home lab setup using a Raspberry Pi as a UniFi wireless controller, private CA, FreeRADIUS, and WPA2-Enterprise.  It’s got more screenshots and explanations than most of the internet deserves.  https://dot11zen.blogspot.com/2018/04/wpa2-entreprise-using-unifi-access.html

P.P.S. FreeRADIUS has been incredibly annoying to write an attribute-API-driven Chef cookbook for.

users file? Easy, we’ll just iterate over a loop and dump out the values — not so fast, the last entry on a user can’t have a trailing comma, oh and we use tabs in some spots.

Config file? We’ll define convenience variables in it, using them all over the place and then use them to create more convenience variables in other config files we include. (I get it, for human maintainers this makes it easy) Without writing templates for each and every config file to get rid of them all, it took a while to locate the major ones to maintain compatibility.

Ubuntu? We’ll use completely different paths to store our RADDB, daemon names, TLS certs, system users and groups than CentOS, because we’re Ubuntu. And amazingly CentOS 7.x has FreeRADIUS v3, whereas Ubuntu 16.x has v2, which uses slightly different syntax.

The majority of the work is done now so hopefully I can post the cookbook on Github soon.

Yosemite trip: August

[photos: flickr – Yosemite]

A couple of weeks ago a friend passing through Yosemite informed me the smoke had cleared up, highways and campgrounds were open again. In theory this meant there should be a lot of campsites available from to all the recent cancellations due to the park closure. I sat on this for a few days and by the weekend I was itching to go. I checked the reservation.gov website, all the campgrounds in the valley were still booked solid, but there were three nights available in the middle of the week at Tuolumne Meadows Campground. I grabbed them and left home on Tuesday afternoon.

I arrived at the campground around 7 PM. The late list was posted with my assigned campsite, along with several warnings about bears in the area. The good news was that despite the recent Ferguson fires, camp fires were allowed above 8,000 feet. I pitched camp, wandered over to the store for firewood, started a fire and set in for the night. I had just received Chris Hadfield’s book An Astronaut’s Guide to Life on Earth from Amazon before I left, so that was my evening reading material under red headlamp light.

Coming from sea level, the altitude was not my friend. Moving around setting up my gear I was starting to get slightly lightheaded. It was cold at night and I tossed and turned many times trying to sleep. Before my last Death Valley trip I had given trying to find the slow leak in my Thermarest EvoLite (I even submerged it in the swimming pool) and bought a NeoAir on clearance from REI. For truck camping I didn’t really care about the weight or bulk of a pad very much. The NeoAir worked perfectly to keep me insulated from the cold ground, gave me cushion to sleep on my side, and best of all it wasn’t fucking deflated by the time I woke up!

Wednesday I had a bit of a headache and decided to take it easy until I acclimated a bit. I drove out to Lee Vining and back to scope out what was around me and what I had missed on the last trip. I had considered hiking up Lembert Dome or up to Elizabeth Lake, but not today. Instead I went over to Soda Springs and wandered around the meadows. It was nearly a full moon at night which did a great job of illuminating the mountains so I spent some time photographing around Tenaya Lake.


Thursday I drove over to Yosemite Valley, where I had wanted to hike the Valley Loop Trail. I found parking near Camp 4 and picked up the trail from there. Not too long after, I spotted a bear walking along the opposite bank of the Merced River before it disappeared back into the trees.

I intended to do the half loop, so I crossed over the river near El Capitan. In the meadow I spotted a pretty good spot to photograph the whole southern face of El Capitan. Using my long lens I was able to pick out a couple of climbers on the face of the rock. I still don’t know how they do it, even with bolts and rope.

Right after I passed Swinging Bridge on the south side, I sucked my Camelback dry. It was after 6 PM, I was annoyed by the flies, so I called it quits and cut back over to Camp 4. I drove up to Tunnel View after sunset to check it out, and wished I had gotten there about 30 minutes sooner for better light. I headed back to camp at Tuolumne Meadows for the night. Sitting by the campfire reading, a deer wandered by, completely undisturbed by my presence.

Friday morning I packed up camp, it was the last of my reservation. I got a bit of an earlier start, grabbed breakfast at the store, and returned to the valley. I was expecting it to be crazytown on a Friday afternoon, I got there right before noon and managed to beat most of the crowd. I wanted to finish off the half Valley Loop, I picked it up again at Camp 4 and headed east. I passed by Lower Yosemite Falls, it was bone dry. It turns out the Valley Loop Trail is considerably longer than the prescribed hiking guide tells you, not only does it go west toward Bridalveil Fall, it goes allllll the way east past Mirror Lake. I wasn’t about to go that far out, so I looped around Upper Pines and Half Dome village on the way back.

It was sometime around 4 PM when I made it back to where I left off Thursday at Swinging Bridge. I grabbed dinner and coffee, hung around for a while and headed back up to Tunnel View again before sunset. The light was great, but still smokey looking off down the valley. While I was there a bride and groom showed up with their photographers and took wedding photos.

After nightfall I stayed in the valley for a few more hours taking night shots. It was a full moon and it did a great job of illuminating the rock and trees. I was reluctant to wander back into the meadow at night by myself, but I did while making a bunch of racket along the way. I got my shots and bugged out!

I drove home after this and got in around 2 AM. I keep forgetting Yosemite is only about a 3 hour drive, I need to go out there more. I had wanted to go up to Glacier Point at night, but from reading the info signs I got the impression that you could only hike up or had to buy a bus ticket to get to the top. Only after I got home and looked at the maps I realized not only can you drive up there, there’s a snack shop up there. It wouldn’t have mattered though, I saw where the road was still closed due to the fires.

Death Valley: August

Joshua Tree at Lee Flat

[photos: flickr – Death Valley]

[bonus video: Death Valley hyperlapse hwy 190 to Furnace creek]

Last weekend was a new moon and it happened to coincide with the peak of the Perseid meteor shower. I thought “great! an excuse to go out to Death Valley and take photos of it!”

The trip turned out to be a dud as far as photography went, but at least I explored some new territory. I had planned to go out to Furnace Creek or Stovepipe Wells and frame some of my shots with some of the local landmarks, but nature had different ideas. Driving in from the west over the Panamint Range, the sky was clear and stars were easily seen. As I got closer to Emigrant I noticed I couldn’t see any stars anymore and wondered if it was clouds or smoke from all the wildfires. Finally when I got into Stovepipe Wells I realized what was going on: a dust storm. There was strong winds whipping up dust everywhere, and despite being midnight it was still 104 F there. I bailed and headed back up to Panamint and spent the night at Father Crowley Vista Point.

Poor man’s manual shutter switch

I wasn’t the only one in the parking lot in the dark, there was another group next to me with their lawn chairs out doing some stargazing. It wasn’t a clear night, there were still some scattered clouds all around. I was miffed that I had forgotten to bring the manual shutter release for my second camera body for the long exposures, so I wound up improvising by lashing a wad of tissue over the shutter button with a length of paracord.  I set up one camera pointed at the Milky Way and the other camera toward Perseus and waited. The meteors came every 5-10 minutes, but I didn’t get any interesting photos out of it.

Sunday morning I drove down to Panamint Springs Resort to grab some breakfast and mull over plans. I went to Darwin Falls, which is right next to Panamint Springs and hiked the mile or so up to the waterfall. Surprisingly even in August there was a lot of running water here which gradually disappeared into the creek bed. There was also a 4″ pipeline that ran all the way from the falls, along the canyon wall, out to the highway, and presumably providing drinking water to Panamint Springs.

Next I drove up Saline Valley Alternative Road, which skirts the west edge of the park from highway 190. This led me through BLM land and then up inside the park again at Lee Flat, where there was a large swath of Joshua Trees. I tried to continue north toward Hunter Mountain but gave up several miles out because the road was starting to get rougher.

115 F at Furnace Creek

Later that afternoon I made a quick trip over to Furnace Creek to see how things were. At 4:30 PM it was “only” 116 F at the visitors center. Along the way I threw a tripod in my front seat, mounted up my iPhone and used the Instagram Hyperlapse app to make a super long hyperlapse video of the drive in. I didn’t hang around in Furnace Creek very long, I returned to Father Crowley for another attempt at night photography.

As the sun went down I decided to go back out on Saline Valley road to find a place to camp and set up. I found a freshly graded road, followed it for a couple of miles even further in the middle of nowhere. This time the sky was perfectly clear and I was in pitch darkness. I had set up one camera for a Milky Way timelapse starting at dusk, which started out great, then I thought about how it was going to track to the west and I should’ve aimed the camera differently. So I had the big idea to move the tripod and ruin my timelapse. The other camera I started using later on to get star trails around Polaris. That kind of worked out until I got home and couldn’t retrieve anything off the CF card. sigh.


Defeated I was ready to leave. Another breakfast at Panamint Springs I stopped by Father Crowley one last time, wondering if there would be any jets flying through Rainbow Canyon this time of day. As soon as I pulled in my question was answered as a F/A 18 came flying up through the canyon. I hung around at the viewpoint for a couple of hours. Aside from myself, there was one family out there, we had the whole place to ourselves. In the time I was there I saw 6-7 passes through the canyon and one very loud flyover. The 1.4x teleconverter I bought worked out pretty well here, giving me effectively 280mm of zoom. The jet that flew directly over, I didn’t even have to crop, it nearly filled frame! By noon I was starting to cook and decided to come home.

Minuteman III launch 7/31

Long exposure of Minuteman III launch

Sunday morning I got an email from the launch-alert mailing list about an upcoming Minuteman III ICBM test out of Vandenberg AFB on Tuesday morning. I had just gotten back from photographing the Iridium 7 launch a few days prior, but being a cold war nerd I definitely did not want to miss seeing an ICBM going up. So, I headed south once again, bringing along gear to camp out on the central coast.

The Air Force occasionally pulls a random active missile out of a silo in Montana, South Dakota, or Wyoming, removes the nuclear warhead, and ships it down to Vandenberg AFB to test launching it. They make sure the thing still flies and hits the expected target way out in the South Pacific, usually near Kwajalein or sometimes near Guam.

VAFB – Kwaj path

I didn’t know much about Minuteman launches so I scrambled to find out more. I knew roughly whereabouts on base they were launched from, and the path they’d take, but didn’t know how high it’d get, how visible it’d be, nor the best vantage for photographing it. Most importantly I didn’t know exactly when it would launch, for this launch there was a 6 hour window between 12:01 AM and 6:01 AM, which is a lot of uncertainty. Without a way to know exact timing I’d have to watch the horizon constantly for launch to avoid having super long exposure photos. From what I gathered it would lift off a lot faster than a Falcon 9, have a considerably higher apogee, and because it was a solid fuel booster the exhaust plume should be much brighter.

Some people had compiled information about Minuteman launches, but most had ran out of steam and interest in the late 2000s. Not many people have photographed a launch recently either it seems. Fortunately the 30th Space Wing posts a ton of launch video on Youtube, and cross referencing against news articles, I was able to get a rough idea of the launch windows and when the launch actually takes place. Apparently I had just missed MMIII launches in April and May. They seem to launch at the beginning of the window, but there were still many that launched much later.

Trivia: the “GT” in launch titles, e.g. GT-226GM, apparently stands for “Glory Trip”, an Air Force designation stretching back into the 70s. Interestingly they also occasionally test launches by sending commands from an airborne launch command in case silos become isolated from ground launch command centers.

==== 2018 ====
GT-226GM  2018-04-25  05:26:00 AM  LF-10  Window 03:26 AM-09:36 AM
GT-225GM  never flown?
GT-224GM  2018-05-14  01:23:00 AM  LF-04  Window 01:21 AM-07:21 AM
==== 2017 ====
GT-223GM  2017-08-02  00:02:10 AM  LF-10  Window 12:01 AM-06:01 AM
GT-222GM  2017-05-03  00:01:59 AM  LF-04  Window 12:01 AM-06:01 AM
GT-221GM  2017-02-08  11:38:59 PM  LF-04  Window 11:30 PM-05:39 AM
GT-220GM  2017-04-26  00:03:06 AM  LF-09  Window 12:01 AM-06:01 AM
==== 2016 ====
GT-219GM  2016-09-05  02:10:00 AM  LF-04  Window 12:01 AM-06:00 AM
GT-218GM  2016-02-25  11:00:59 PM  LF-10  Window 11:00 PM-05:00 AM
GT-217GM  2016-02-20  11:34:02 PM  LF-09  Window 11:00 PM-05:00 AM

I settled in on a site in the Los Padres National Forest north of Santa Ynez. From there in the distance I could see the red lights of the antenna tower at Vandenberg just off Ocean Ave, right next to the unofficial viewing area for SpaceX launches from SLC-4E. I knew the Minuteman launches happened just north of this, but didn’t know how far, so I aimed my camera in this direction and hoped for the best. I was relieved when I turned on my radio and heard the launch net chatter discussing the launch checklist, because then I would know for sure when it would launch and click off the camera right before.

Recycle, recycle

At first everything was going fine for a 12:01 AM launch, when I heard “not clear to proceed” about T-15 minutes. The held the countdown, then started recycling after mention of some sort of launch anomaly. After a while they restarted the countdown for 1:20 AM, then another hold until 1:40 AM. At the last minute they held and recycled again due to an anomaly. Then they tried for 2:55 AM and again held at the last minute of the countdown. The moon had risen around 11 PM and was conveniently staying out of the way. By now it was starting to add glare to my photos.

(Times are approximate from bits of video+audio I recorded and photo EXIF, I didn’t know I’d be making a timeline later)

Finally after a long time they tried again around 4:40 AM and it finally launched. The sky to the west was still fairly dark and the missile made this bright, rich, orange dot as it rose up in the air. About a minute or two into the flight I thought I saw the first stage separate and glimmering as it fell back to earth. After this, there was just a very faint spec continuing westward. I kind of expected see a brighter exhaust plume for longer, but wrote it off as flying so far away from me. The arc is barely noticeable on the photo I took, but it’s there. Like the Falcon 9 launch from afar, after a few minutes a very very faint rumbling sound comes in and goes away.

Looking at the photo the glimmering is following the upward trajectory, so I’m not sure what I was looking at. The shitty iPhone video I made clearly shows something falling away around 4:41 AM and something else continuing to burn upward. Lesson for next time, get a heck of a lot closer and further south.

Surprise ending

I later found out from the news they actually terminated the flight of this missile due to an anomaly (I’m finally learning how to spell “anomaly”). The article says they terminated at 4:42 AM, in theory I was still exposing the photo. It makes me wonder if the pulsating brightness was the missile being destroyed, a sign of the problem, or that’s just what it normally does. It probably explains why I could barely see anything after it arced over. I never saw a giant explosion or flash, nor heard a big boom to indicate it went out in a blaze of glory.

At the time during all the launch holds I was thinking to myself “gee I thought these were supposed to launch at a minute’s notice”. Then it entered my mind that because this is a test flight, they could be intentionally running down to the last minute to test recycling the missile and exercising their checklists so people get practice. I guess this one really did have problems.

« Newer Posts - Older Posts »