Members Can Post Anonymously On This Site
First all-new MetOp complete and sibling in testing
-
Similar Topics
-
By European Space Agency
The European Space Agency (ESA) has signed a contract with Thales Alenia Space in Italy to lead European aerospace companies in building the Argonaut Lunar Descent Element, ESA’s first lunar lander.
View the full article
-
By NASA
On Jan. 24, 1985, space shuttle Discovery took off from NASA’s Kennedy Space Center (KSC) in Florida on STS-51C, the first space shuttle mission entirely dedicated to the Department of Defense (DOD). As such, many of the details of the flight remain classified. Discovery’s crew of Commander Thomas “T.K.” Mattingly, Pilot Loren Shriver, Mission Specialists Ellison Onizuka and James Buchli, and Payload Specialist Gary Payton deployed a classified satellite that used an Inertial Upper Stage (IUS) to reach its final geostationary orbit. The three-day mission ended with a landing at KSC. Postflight inspection of the Solid Rocket Boosters (SRBs) revealed the most significant erosion of O-ring seals seen in the shuttle program up to that time, attributed to unusually cold weather before and during launch.
The STS-51C crew of Pilot Loren Shriver, seated left, and Commander Thomas “T.K.” Mattingly; Payload Specialist Gary Payton, standing left, and Mission Specialists James Buchli and Ellison Onizuka. The STS-51C crew patch. In October 1982, NASA assigned astronauts Mattingly, Shriver, Onizuka, and Buchli as the STS-10 crew for a dedicated DOD flight aboard Challenger then scheduled for September 1983. Payton joined the crew as a payload specialist in the summer of 1983 with Keith Wright assigned as his backup. The failure of the IUS on STS-6 in April 1983 delayed the STS-10 mission, that also used the IUS, until engineers could identify and fix the cause of the problem. By September 1983, NASA had remanifested the crew and the payload on STS-41F with a July 1984 launch, that changed to STS-41E by November 1983. Additional delays in fixing the IUS delayed the mission yet again, by June 1984 redesignated as STS-51C and slated for December 1984 aboard Challenger.
STS-51C marked the third spaceflight for Mattingly, selected in 1966 as part of NASA’s fifth group of astronauts. He served on the prime crew for Apollo 13 until exposure to German measles forced his last-minute replacement by his backup. He then flew on Apollo 16 and STS-4. For Shriver, Onizuka, and Buchli, all three selected as astronauts in the class of 1978, STS-51C marked their first trip into space. The U.S. Air Force selected Payton and Wright in August 1979 in its first class of Manned Spaceflight Engineers, and STS-51C marked Payton’s first and only space mission.
In November 1984, NASA decided to delay STS-51C from December 1984 to January 1985 and swap orbiters from Challenger to Discovery. Postflight inspections following Challenger’s STS-41G mission in October 1984 revealed degradation of the bonding materials holding thermal protection system tiles onto the orbiter, requiring the replacement of 4,000 tiles. The time required to complete the work precluded a December launch. Tests conducted on Discovery prior to its November STS-51A mission revealed the bonding material to be sound.
Space shuttle Discovery rolls out to Launch Pad 39A. The STS-51C crew poses during launch pad evacuation drills associated with the Terminal Countdown Demonstration Test. The STS-51C crew exits crew quarters for the ride to Launch Pad 39A. On Jan. 5, 1985, Discovery rolled out from KSC’s Vehicle Assembly Building, where workers mated it with its External Tank (ET) and SRBs, to Launch Pad 39A. There, engineers conducted the Terminal Countdown Demonstration Test, essentially a dress rehearsal for the actual countdown, on Jan. 6-7, with the crew participating in the final few hours much as they would on launch day. The astronauts returned to KSC on Jan. 20 to prepare for the planned launch on Jan. 23. The day before, NASA managers decided to delay the launch by one day due to unseasonably cold weather, with concern about sub-freezing temperatures causing ice to form on the ET and possibly coming loose during ascent and damaging the vehicle. The DOD had requested that NASA keep the actual launch time secret until T minus nine minutes, with most of the countdown taking place hidden from public view.
Liftoff of space shuttle Discovery on STS-51C. Liftoff of Discovery on its third mission, STS-51C, came at 2:50 p.m. EST on Jan. 24, beginning the 15th space shuttle flight. Eight and a half minutes later, Discovery and its five-man crew had reached orbit. And, at the DOD customer’s request, all public coverage of the mission ended. Although NASA could not reveal the spacecraft’s orbital parameters, trade publications calculated that Discovery first entered an elliptical orbit, circularized over the next few revolutions, prior to Onizuka deploying the IUS and payload combination on the seventh orbit. Neither NASA nor the DOD have released any imagery of the deployment or even of the payload bay, with only a limited number of in-cabin and Earth observation photographs made public.
STS-51C Commander Thomas “T.K.” Mattingly films the Earth from Discovery’s overhead flight deck window. STS-51C crew members Loren Shriver, left, Ellison Onizuka, and James Buchli on Discovery’s flight deck. STS-51C Payload Specialist Gary Payton on Discovery’s flight deck. Sunlight streams through Earth’s upper atmosphere, with Discovery’s tail and Orbital Maneuvering Engine pods outlined by sunlight. The Pacific coast of Guatemala and southern Mexico. New Orleans and the Mississippi River delta. Discovery touches down at NASA’s Kennedy Space Center in Florida. The STS-51C astronauts are greeted by NASA officials as they exit Discovery. To maintain the mission’s secrecy, NASA could reveal the touchdown time only 16 hours prior to the event. On Jan. 27, Mattingly and Shriver brought Discovery to a smooth landing at KSC’s Shuttle Landing Facility after a flight of three days one hour 33 minutes, the shortest space shuttle mission except for the first two orbital test flights. The astronauts orbited the Earth 49 times. About an hour after touchdown, the astronaut crew exited Discovery and boarded the Astrovan for the ride back to crew quarters. Neither NASA management nor the astronauts held a post mission press conference. The U.S. Air Force announced only that the “IUS aboard STS-51C was deployed from the shuttle Discovery and successfully met its mission objectives.” Later in the day, ground crews towed Discovery to the Orbiter Processing Facility to begin preparing it for its next planned mission, STS-51D in March.
Postscript
Following the recovery of SRBs after each shuttle mission, engineers conducted detailed inspections before clearing them for reuse. After STS-51C, inspections of the critical O-ring seals that prevented hot gases from escaping from the SRB field joints revealed significant erosion and “blow-by” between the primary and secondary O-rings. Both left and right hand SRBs showed this erosion, the most significant of the program up to that time. Importantly, these O-rings experienced weather colder than any previous shuttle mission, with overnight ambient temperatures in the teens and twenties. Even at launch time, the O-rings had reached only 60 degrees. Engineers believed that these cold temperatures made the O-rings brittle and more susceptible to erosion. One year later, space shuttle Challenger launched after similarly cold overnight temperatures, with O-rings at 57 degrees at launch time. The Rogers Commission report laid the blame of the STS-51L accident on the failure of O-rings that allowed super-hot gases to escape from the SRB and impinge on the hydrogen tank in the ET, resulting in the explosion that destroyed the orbiter and claimed the lives of seven astronauts. The commission also faulted NASA’s safety culture for not adequately addressing the issue of O-ring erosion, a phenomenon first observed on STS-2 and to varying degrees on several subsequent missions.
View the full article
-
By European Space Agency
The European Space Agency (ESA) and the Estonian Space Office have set out to develop Europe's newest space cyber range that aims to make space technology more secure and accessible for companies across Europe. Last year, Estonian industry was invited to submit proposals for concepts, and today the contract has been signed with a consortium led by Spaceit to begin development.
View the full article
-
By NASA
On Jan. 19, 1965, Gemini 2 successfully completed the second of two uncrewed test flights of the spacecraft and its Titan II booster, clearing the way for the first crewed mission. The 18-minute suborbital mission achieved the primary goals of flight qualifying the Gemini spacecraft, especially its heat shield during a stressful reentry. Recovery forces retrieved the capsule following its splashdown, allowing engineers to evaluate how its systems fared during the flight. The success of Gemini 2 enabled the first crewed mission to fly two months later, beginning a series of 10 flights over the following 20 months. The astronauts who flew these missions demonstrated the rendezvous and docking techniques necessary to implement the Lunar Orbit Rendezvous method NASA chose for the Moon landing mission. They also proved that astronauts could work outside their spacecraft during spacewalks and that spacecraft and astronauts could function for at least eight days, the minimum time for a roundtrip lunar mission. The Gemini program proved critical to fulfill President John F. Kennedy’s goal of landing a man on the Moon and returning him safely to Earth before the end of the 1960s.
Cutaway diagram of the Gemini spacecraft. Workers at Launch Pad 19 lift Gemini 2 to mate it with its Titan II rocket. At Pad 19, engineers verify the flight simulators inside Gemini 2. Following the success of Gemini 1 in April 1964, NASA had hoped to fly the second mission before the end of the year and the first crewed mission by January 1965. The two stages of the Titan II rocket arrived at Cape Kennedy from the Martin Marietta factory in Baltimore on July 11, and workers erected it on Launch Pad 19 five days later. A lightning strike at the pad on Aug. 17 invalidated all previous testing and required replacement of some pad equipment. A series of three hurricanes in August and September forced workers to partially or totally unstack the vehicle before stacking it for the final time on Sept. 14. The Gemini 2 spacecraft arrived at Cape Kennedy from its builder, the McDonnell Company in St. Louis, on Sept. 21, and workers hoisted it to the top of the Titan II on Oct. 18. Technical issues delayed the spacecraft’s physical mating to the rocket until Nov. 5. These accumulated delays pushed the launch date back to Dec. 9.
The launch abort on Dec. 9, 1964. Liftoff of Gemini 2 from Launch Pad 19 on Jan. 19, 1965. Engineers in the blockhouse monitor the progress of the Titan II during the ascent. Fueling of the rocket began late on Dec. 8, and following three brief holds in the countdown, the Titan’s two first stage engines ignited at 11:41 a.m. EST on Dec. 9. and promptly shut down one second later. Engineers later determined that a cracked valve resulted in loss of hydraulic pressure, causing the malfunction detection system to switch to its backup mode, forcing a shutdown of the engines. Repairs meant a delay into the new year. On Jan. 19, 1965, following a mostly smooth countdown, Gemini 2 lifted off from Pad 19 at 9:04 a.m. EST.
The Mission Control Center (MCC) at NASA’s Kennedy Space Center in Florida. In the MCC, astronauts Eugene Cernan, left, Walter Schirra, Gordon Cooper, Donald “Deke” Slayton, and Virgil “Gus” Grissom monitor the Gemini 2 flight. In the Gemini Mission Control Center at NASA’s Kennedy Space Center in Florida, Flight Director Christopher C. Kraft led a team of flight controllers that monitored all aspects of the flight. At the Manned Spacecraft Center (MSC), now NASA’s Johnson Space Center in Houston, a team of controllers led by Flight Director John Hodge passively monitored the flight from the newly built Mission Control Center. They would act as observers for this flight and Gemini 3, the first crewed mission, before taking over full control with Gemini IV, and control all subsequent American human spaceflights. The Titan rocket’s two stages placed Gemini 2 into a suborbital trajectory, reaching a maximum altitude of 98.9 miles, with the vehicle attaining a maximum velocity of 16,709 miles per hour. Within a minute after separating from the Titan’s second stage, Gemini 2 executed a maneuver to orient its heat shield in the direction of flight to prepare for reentry. Flight simulators installed where the astronauts normally would sit controlled the maneuvers. About seven minutes after liftoff, Gemini 2 jettisoned its equipment section, followed by firing of the retrorockets, and then separation of the retrorocket section, exposing the spacecraft’s heat shield.
View from a camera mounted on a cockpit window during Gemini 2’s reentry. View from the cockpit window during Gemini 2’s descent on its parachute. Gemini 2 then began its reentry, the heat shield protecting the spacecraft from the 2,000-degree heat generated by friction with the Earth’s upper atmosphere. A pilot parachute pulled away the rendezvous and recovery section. At 10,000 feet, the main parachute deployed, and Gemini 2 descended to a splashdown 2,127 miles from its launch pad, after a flight of 18 minutes 16 seconds. The splashdown took place in the Atlantic Ocean about 800 miles east of San Juan, Puerto Rico, and 25 miles from the prime recovery ship, the U.S.S. Lake Champlain (CVS-39).
A U.S. Navy helicopter hovers over the Gemini 2 capsule following its splashdown as a diver jumps into the water. Sailors hoist Gemini 2 aboard the U.S.S. Lake Champlain. U.S. Navy helicopters delivered divers to the splashdown area, who installed a flotation collar around the spacecraft. The Lake Champlain pulled alongside, and sailors hoisted the capsule onto the carrier, securing it on deck one hour forty minutes after liftoff. The spacecraft appeared to be in good condition and arrived back at Cape Kennedy on Jan. 22 for a thorough inspection. As an added bonus, sailors recovered the rendezvous and recovery section. Astronaut Virgil “Gus” Grissom, whom along with John Young NASA had selected to fly the first crewed Gemini mission, said after the splashdown, “We now see the road clear to our flight, and we’re looking forward to it.” Flight Director Kraft called it “very successful.” Gemini Program Manager Charles Matthews predicted the first crewed mission could occur within three months. Gemini 3 actually launched on March 23.
Enjoy this NASA video of the Gemini 2 mission.
Postscript
The Gemini-B capsule and a Manned Orbiting Laboratory (MOL) mockup atop a Titan-IIIC rocket in 1966. The flown Gemini-B capsule on display at the Cape Canaveral Space Force Museum in Florida. Former MOL and NASA astronaut Robert Crippen stands beside the only flown Gemini-B capsule – note the hatch in the heat shield at top. Gemini 2 not only cleared the way for the first crewed Gemini mission and the rest of the program, it also took on a second life as a test vehicle for the U.S. Air Force’s Manned Orbiting Laboratory (MOL). The Air Force modified the spacecraft, including cutting a hatch through its heat shield, renamed it Gemini-B, and launched it on Nov. 3, 1966, atop a Titan IIIC rocket. The test flight successfully demonstrated the hatch in the heat shield design during the capsule’s reentry after a 33-minute suborbital flight. Recovery forces retrieved the Gemini-B capsule in the South Atlantic Ocean and returned it to the Air Force for postflight inspection. This marked the only repeat flight of an American spacecraft intended for human spaceflight until the advent of the space shuttle. Visitors can view Gemini 2/Gemini-B on display at the Cape Canaveral Space Force Museum.
View the full article
-
By NASA
4 min read
Preparations for Next Moonwalk Simulations Underway (and Underwater)
Danah Tommalieh, commercial pilot and engineer at Reliable Robotics, inputs a flight plan at the control center in Mountain View, California, ahead of remotely operating a Cessna 208 aircraft at Hollister municipal airport in Hollister, California.NASA/Don Richey NASA recently began a series of flight tests with partners to answer an important aviation question: What will it take to integrate remotely piloted or autonomous planes carrying large packages and cargo safely into the U.S. airspace? Researchers tested new technologies in Hollister, California, that are helping to investigate what tools and capabilities are needed to make these kinds of flights routine.
The commercial industry continues to make advancements in autonomous aircraft systems aimed at making it possible for remotely operated aircraft to fly over communities – transforming the way we will transport people and goods. As the Federal Aviation Administration (FAA) develops standards for this new type of air transportation, NASA is working to ensure these uncrewed flights are safe by creating the required technological tools and infrastructure. These solutions could be scaled to support many different remotely piloted aircraft – including air taxis and package delivery drones – in a shared airspace with traditional crewed aircraft.
“Remotely piloted aircraft systems could eventually deliver cargo and people to rural areas with limited access to commercial transportation and delivery services,” said Shivanjli Sharma, aerospace engineer at NASA’s Ames Research Center in California’s Silicon Valley. “We’re aiming to create a healthy ecosystem of many different kinds of remotely piloted operations. They will fly in a shared airspace to provide communities with better access to goods and services, like medical supply deliveries and more efficient transportation.”
During a flight test in November, Reliable Robotics, a company developing an autonomous flight system, remotely flew its Cessna 208 Caravan aircraft through pre-approved flight paths in Hollister, California.
Although a safety pilot was aboard, a Reliable Robotics remote pilot directed the flight from their control center in Mountain View, more than 50 miles away.
Cockpit of Reliable Robotics’ Cessna 208 aircraft outfitted with autonomous technology for remotely-piloted operations.NASA/Brandon Torres Navarrete Congressional staffers from the United States House and Senate’s California delegation joined NASA Deputy Associate Administrator for Aeronautics Research Mission Directorate, Carol Caroll, Ames Aeronautics Director, Huy Tran, and other Ames leadership at Reliable Robotics Headquarters to view the live remote flight.
Researchers evaluated a Collins Aerospace ground-based surveillance system’s ability to detect nearby air traffic and provide the remote pilot with information in order to stay safely separated from other aircraft in the future.
Initial analysis shows the ground-based radar actively surveilled the airspace during the aircraft’s taxi, takeoff, and landing. The data was transmitted from the radar system to the remote pilot at Reliable Robotics. In the future, this capability could help ensure aircraft remain safely separated across all phases of fight.
A Reliable Robotics’ modified Cessna 208 aircraft flies near Hollister Airport. A Reliable Robotics pilot operated the aircraft remotely from the control center in Mountain View.NASA/Brandon Torres Naverrete While current FAA operating rules require pilots to physically see and avoid other aircraft from inside the cockpit, routine remotely piloted aircraft will require a suite of integrated technologies to avoid hazards and coordinate with other aircraft in the airspace.
A radar system for ground-based surveillance offers one method for detecting other traffic in the airspace and at the airport, providing one part of the capability to ensure pilots can avoid collision and accomplish their desired missions. Data analysis from this testing will help researchers understand if ground-based surveillance radar can be used to satisfy FAA safety rules for remotely piloted flights.
NASA will provide analysis and reports of this flight test to the FAA and standards bodies.
“This is an exciting time for the remotely piloted aviation community,” Sharma said. “Among other benefits, remote operations could provide better access to healthcare, bolster natural disaster response efforts, and offer more sustainable and effective transportation to both rural and urban communities. We’re thrilled to provide valuable data to the industry and the FAA to help make remote operations a reality in the near future.”
Over the next year, NASA will work with additional aviation partners on test flights and simulations to test weather services, communications systems, and other autonomous capabilities for remotely piloted flights. NASA researchers will analyze data from these tests to provide a comprehensive report to the FAA and the community on what minimum technologies and capabilities are needed to enable and scale remotely piloted operations.
This flight test data analysis is led out of NASA Ames under the agency’s Air Traffic Management Exploration project. This effort supports the agency’s Advanced Air Mobility mission research, ensuring the United States stays at the forefront of aviation innovation.
Share
Details
Last Updated Jan 07, 2025 Related Terms
Ames Research Center Advanced Air Mobility Aeronautics Aeronautics Research Mission Directorate Air Traffic Management – Exploration Airspace Operations and Safety Program Drones & You Explore More
3 min read How a NASA Senior Database Administrator Manifested her Dream Job
Article 2 weeks ago 16 min read NASA Ames Astrogram – December 2024
Article 3 weeks ago 5 min read NASA’s Ames Research Center Celebrates 85 Years of Innovation
Article 3 weeks ago Keep Exploring Discover More Topics From NASA
Missions
Humans in Space
Climate Change
Solar System
View the full article
-
-
Check out these Videos
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.