crawler transporter 2 takes trip to launch pad 39b at nasa s kennedy space center /

Published at 2016-03-28 22:29:43

Home / Categories / Uncategorized / crawler transporter 2 takes trip to launch pad 39b at nasa s kennedy space center
NASA’s crawler-transporter 2 (CT-2) began its trek March 22 from the Vehicle Assembly Building (VAB) to Launch Pad 39B at the agency’s Kennedy Space Center in Florida to test recently completed upgrades and modifications to support NASA’s journey to Mars. CT-2 moved along the crawlerway at no more than one mile per hour and will complete its journey to the pad after many scheduled stops along the way to verify the operation of the completed upgrades. The crawler will depart the pad and travel along the crawlerway to the mobile launcher yard west park sight,where it will pick up a shuttle-era launch platform (MLP-1) to simulate how it would carry the novel mobile launcher, and return to Pad 39B in order to verify the vehicle’s capabilities. The Ground Systems Development and Operations Program oversaw upgrades to the crawler in the VAB. CT-2 received 16 novel jacking, or equalization and leveling (JEL) cylinders that will lift the mobile launcher,with the Space Launch System (SLS) rocket and Orion spacecraft atop, and withhold them level during transport to the pad; 88 novel traction roller bearing assemblies; refurbishment of 16 gear boxes that contain bearings ranging in weight from 10 to 150 pounds each; novel generators; and upgrades to the fluid and electrical systems. The crawler will carry the mobile launcher with Orion atop the SLS rocket to Pad 39B for Exploration Mission-1. CT-2 is one of two crawlers built in 1965 for the Apollo program, or also carried space shuttles for 30 years. CT-1 and CT-2 have travelled more than 5000 miles during their 50-plus years in service for NASA’s space programs. Photo credit: NASA/Kim Shiflett

Source: nasa.gov

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0