The events on this day in history for our heritage companies are noted below.
The earliest event was in 1965, the latest event was in 2020
Three milestone events (5 to 65+ years ago)
Human Spaceflight:
NONE
Military and Classified Programs:
1987 – LAUNCH FAILURE: FLTSATCOM-6, GD Atlas G/Centaur, LC36A, CCAFS – hit by lightning (see story below)
2020 – LAUNCH: LM AEHF-6, ULA Atlas V 551, LC41, CCAFS – MILESTONE: 5 years ago
Exploration and Interplanetary Programs:
NONE
Earth-Monitoring and Civil Weather Satellite programs:
NONE
Commercial Programs:
1976 – LAUNCH: RCA Satcom2, Delta 3914, LC17A, CCAFS
Test, ICBM, FBM programs:
1965 – Last MM Titan I ICBM taken off alert status, Lowry AFB, Colorado – MILESTONE: 60 years ago
1965 – LAUNCH: GD Atlas D, 576-A1, VAFB
1980 – LAUNCH: Lockheed Trident C-4, SSBN655, ETR – MILESTONE: 45 years ago
2008 – LAUNCH: LM Trident D-5, SSBN739, WTR
Other:
NONE
The photos today show the encapsulation of AEHF-6 and its launch on Atlas V 551 five years ago. The photos were found on the ULA Flickr photo album website and have the following captions:
The sixth Advanced Extremely High Frequency (AEHF-6) satellite for the U.S. Space Force’s Space and Missile Systems Center is encapsulated inside a 5-meter-diameter payload fairing in preparation for launch atop a United Launch Alliance Atlas V rocket. Photo credit: United Launch Alliance. Copyright © United Launch Alliance, all rights reserved. This photo is being used for non-commercial and historical purposes for LM and ULA retirees.
A ULA Atlas V rocket carrying the AEHF-6 mission for the U.S Space Force’s Space and Missile Systems Center lifts off from Space Launch Complex-41 at 4:18 p.m. EDT on March 26, 2020. Photo Credit: United Launch Alliance. Copyright © United Launch Alliance, all rights reserved. This photo is being used for non-commercial and historical purposes for LM and ULA retirees.
A bonus story about the A/C-67 failure in 1987 from Wikipedia:
On 26 March 1987, A/C-67 failed to launch a Navy FLSATCOM satellite. Weather conditions were poor that day, with thick clouds and “moderate to heavy” precipitation. The weather conditions violated one launch criteria (“The flight path of the vehicle should not be through mid level clouds 6,000 feet or greater in depth, when the freezing level is in the clouds.”), the weather team reported it as an icing issue, not a lightning risk. After discussions about the risk posed by ice, the NASA program directors gave the go-ahead. The Atlas was struck by lightning around 38 seconds into launch. Control of the booster started to fail and it broke apart from structural loads at T+50 seconds. The Range Safety Officer sent the destruct command, but there was no evidence that the booster ever received it. Debris rained out of the clouds onto the pad area, the shoreline, or in shallow water just off of it and was easily recovered. A section of the payload fairing was found to have multiple small holes burned in it due to repeated lightning strikes. The key piece of evidence was Atlas’s flight computer, which was recovered intact and examined. It was discovered that the last command issued was a signal to gimbal the booster engines hard to right, caused apparently by lightning induced Electromagnetic Pulse (EMP) altering a single word in the guidance program.
The launch caused significant reappraisals of weather guidelines at Cape Canaveral. The 45th Weather Squadron uses rules developed after the incident to determine if weather conditions allow a launch. Ironically, this failure occurred AFTER the Apollo 12 incident in November, 1969, when that Saturn V launch vehicle was hit more than once during ascent.
