Looking Back At STS-3 With A 30 Year Perspective | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

Airborne Unlimited -- Most Recent Daily Episodes

Episode Date

Airborne-Monday

Airborne-Tuesday

Airborne-Wednesday Airborne-Thursday

Airborne-Friday

Airborne On YouTube

Airborne-Unlimited-04.01.24

Airborne-Unlimited-04.16.24

Airborne-FlightTraining-04.17.24 Airborne-Unlimited-04.11.24

Airborne-Unlimited-04.12.24

Join Us At 0900ET, Friday, 4/10, for the LIVE Morning Brief.
Watch It LIVE at
www.airborne-live.net

Thu, Mar 22, 2012

Looking Back At STS-3 With A 30 Year Perspective

Shuttle Flight Testing, DTOs, And Misconceptions Of The So-Called 'Wheelie Landing'.

By Wes Oleszewski

In looking back over three decades to the flight of STS-3 there is one thing to keep clearly in context; this was a TEST flight. Although the Shuttle had flown two previous times, STS-3 was the next in the series of four flight tests intended to seek out and reveal flaws in the whole system. Some people, especially in today’s Internet, arm-chair, know-it-all breed of self-proclaimed spaceflight “experts” seem to forget or simply ignore the fact that there were four flights that were of a test nature. Out of that confused fog of un-researched and ill-informed opinions there sprouts the myth of the STS-3 “Wheelie Landing” which we will debunk in the end of this article.

Personally I had the great fortune to witness the first several Shuttle launches from a number of different perspectives; STS-1 from the banks of the Indian River and STS-2 from the VIP site. For the launch of STS-3 I was lucky enough to have my parents and younger brother in tow. Venturing down from Michigan in my dad’s second-hand motor home, they were seeking to relieve me of my normal working-your-way-through-college diet of Rice-a-roni and peanut butter for at least a week. As a bonus they had scheduled their visit during the launch of Columbia and we were going to head down and see it.

Freed from my service to the Daytona Beach K-mart’s garden shop at 4:00 pm sharp on March 21st, 1982, I left the loading of pine bark nuggets and cow manure to someone else, boarded the motor home and we set out for the Space Coast. The folks wanted to take the scenic route down US1 and so southbound we rattled toward Titusville. Along the way my dad turned to me and asked, “So, where are ya’ gonna have us park this beast?” I simply shrugged and replied, “I’ll let ya’ know when I see it.” What I knew, that they were not aware of, was that on a launch day- almost anyplace within 25 miles of the Kennedy Space Center becomes a public camp-ground.

Just after US1 turned into the town of Titusville, a vacant piece of open ground caught my eye near the river south of the intersection of the highway and Max Brewer Parkway. “Right there!” I exclaimed, pointing at the open lot. “Just pull in right there!” Dad reluctantly pulled the landboat into the open dirt lot. As we came to a stop it was clear that there were already several campers staked out there. Getting out I did my best Jake Blues arriving at the “Country Bunker” impression. “Yep, this is the place.” Dad was not at all convinced, “What if they come and run us otta here?” he asked doubtfully. “Don’t worry,” I assured him, “on the night before a launch “they” don’t exist.” Dad worried most of the evening. People from the Midwest are very uncomfortable about invading other folk’s space without an invitation or a paid camping spot. But as the evening wore on and the once open lot became packed with campers, my dad turned off his worry switch.

Our little camping spot was almost exactly 12.2 miles west of Launch Complex 39A. As the sun set, the spot lights on the pad turned it rightfully into the center of attention. My mom was absolutely transfixed by the Shuttle illuminated at the pad and simply could not take her attention away from it. She was not alone, as most of the campers there were also first-timers to a space launch. On the other hand, I was kept busy monitoring news reports on launch status as best I could- mainly by way of local AM radio. Unlike STS-1, this time there were plenty of TVs and radios to be found in the area. Much like STS-1, however, very few in the crowd understood the details of the countdown and the massive amount of glitches that could trigger a scrub. For the first time it dawned on me that I sort of wished I was one of those people who did not know how many things could go wrong and delay the launch.

Following 70 days in the Orbiter Processing Facility after STS-2, Columbia was mated the External Tank (ET) in the VAB on February 3rd, 1982 and rolled out to Pad 39A just 13 days later. STS-3 was the first Shuttle stack to have the now well-known “orange” ET. Even after the ETs were in production, NASA was engaged in the process of weight scrubbing. After some extensive testing, it was decided that the ET’s spray-on CPR-488 foam insulation was strong enough to tolerate the heating of the high-speed airflow during ascent. For that reason the white-colored Fire Retardant Latex (FRL) that was used as an overcoat on the tank was deleted on later tanks, the first of which flew on STS-3. Deletion of the FRL not only saved a small amount of money and man-hours in production, but also saved 595 pounds of weight. Oddly, when a new ET was rolled out of assembly with its fresh CPR-488 coat on, it was not orange- but rather was a greenish yellow color. Solar UV rays caused the foam to turn orange over time and later an orangish brown in color. Doing some announcing for ABC News, Astronaut Gene Cernan speculated that they may later mix a white pigment with the CPR-488 to make the tank white again. Of course that never happened, but that thought illustrates just how odd that orange tank appeared when stacked as a booster in 1982.

 Sporting its orange ET, the countdown for STS-3 was normal up until very late on the night before the launch. A malfunction on a nitrogen gas line in ground support equipment delayed fueling operations and for a short time it looked like a bad glitch to those of us on the outside. Just before dawn, however, NASA PAO announced that the delay would be just one hour in length. Oddly, at our little campsite rumors spread saying everything from “Pack it up and go home” to “Problem? There’s no problem.” At the time, I found it was best to just stay glued to the AM radio.

Following a one hour delay Columbia’s crew, Commander (CDR) Jack Lousma and Pilot (PLT) Gordon Fullerton (pictured) went aboard and were strapped in. Originally, Lousma had been selected as the PLT for STS-3 and went into training with Fred Haise who had been CDR of the Shuttle Enterprise while conducting the Approach and Landing Tests (ALT) back in 1977. Their STS-3 mission was scheduled to be the rescue of Skylab which was why Lousma, a former Skylab astronaut, was selected for it. However, the best laid plans of NASA soon began to fall apart as the Shuttle’s development began to experience delays and the sun’s activity began to grow. The schedule pushed STS-3 back by nearly two years and the increased solar activity caused the earth’s atmosphere to swell. The result was that the atmospheric influence on the Skylab caused its orbit to decay at a far greater rate than expected. Skylab was going to reenter sooner than planned. For that reason the STS-3 crew of Haise and Lousma was moved up to STS-2. The schedule of Shuttle development soon pushed beyond the date of the Skylab’s reentry and the crew was returned to STS-3 and the Skylab rescue mission was canceled. Eventually opportunities motivated Fred Haise to retire from NASA and Jack Lousma was moved into the CDR seat of STS-3 and given Gordon Fullerton as his PLT. Fullerton had actually been Fred Haise’s PLT in the ALT missions. Now he would take that experience and make his first trip into space.

At 11:00:00 am eastern time, the bolts blew, the SRBs ignited and the STS-3 stack lifted off. The burst of sun-bright flame and billows of smoke and steam at Pad 39A set off cheers and screams from every direction around KSC. About 17 seconds later, as the first-timers in our little campsite started to realize that they could not hear the Shuttle, Columbia reached out and took hold of every soul and shook us to our roots. Thrilled screams and cheers reflexively burst from the crowd at a higher pitch. For a moment I could feel the ground actually shake. Looking down I saw a puddle nearby and its water was vibrating. I tapped my mom on the shoulder and pointed down at the reverberating water. She glanced down, squealed with delight and went back to watching Columbia climb. Dad was transfixed and just kept saying, “Man! Look at her go!” There were broken cloud decks in the launch area, but from our location the launch was mostly un-obscured. Following SRB separation the Columbia appeared as a bright star rapidly fading into the morning sky. In a phenomena that would accompany every Shuttle launch for the next three decades, the crowd of spectators broke into spontaneous applause that no one directly involved with the mission could hear. Straining their eyes toward the sky, many tried to watch the Shuttle’s departure for as long as humanly possible before turning away and heading home- I was guilty of that myself.

Of course STS-3 still had a long way to go before insertion into orbit. On the way uphill the Number 3 Auxiliary Power Unit began to show a rising temperature and Mission Control ordered the crew to “secure” it. Although this glitch caught the attention of the news media, it made little difference in the progress of the mission. By the time that the launch spectators finally got their collective breath Main Engine Cutoff had occurred. Shortly thereafter a series of Orbital Maneuvering System engine burns took place and Columbia was in orbit for the third time.

Joining the traffic jam headed away from KSC I found myself riding among a herd of dazzled Americans who were now fully aware of what their tax dollars budgeted to NASA could do. NASA announced that an estimated 1 million people had flooded into the area around KSC to watch the launch. Prior to launch President Reagan had dedicated the flight to the people of Afghanistan who were embroiled in conflict with our Cold War enemies, the Soviet Russians. Looking back across three decades, it is interesting to see how things have changed.

Officially NASA's objectives for the STS-3 mission were to "Demonstrate ascent, on orbit, and entry performance under conditions more demanding than STS-2 conditions. Extend orbital flight duration. Conduct long duration thermal soak tests. Conduct scientific and applications research with an attached payload." The crew went directly into the thermal test profile, the first part of which was establishing a baseline by placing Columbia into a slow roll, something that astronauts like to call "rotisserie mode." This "passive thermal control" mode was done for three 10 hour periods. In addition to that the orbiter was placed into a "tail to the sun" attitude which was maintained for a period of 30 hours. Then the orbiter was also placed with its payload bay pointing toward the sun for 26 hours. Finally, Columbia was placed in an attitude with her nose to the sun for an 80 hour period of time. Data from each of these attitudes was collected and transmitted down to Mission Control.

Experiments ranging from “electrophoresis equipment verification testing” and “dynamic acoustic and thermal environment experiments” to an “insect in-flight motion study” were being conducted by the crew as Columbia basked in the sun. The news media gave the most attention to the insects in flight study- because it was easy to understand, especially for TV newsmen.  It was developed by a high school senior, Todd Nelson. When you saw him interviewed, you got the distinct impression that he was far more intelligent than the people interviewing him. Although the news people may have thought that Todd's experiment was something simple enough that they may be able to fully understand it, Todd either proved them wrong or at least made them work for it. Of all the networks, CNN provided the best coverage of STS-3. That was because the toddling two-year-old network was the only one with the new 24 hour news format and they needed content. So, every time the Shuttle down-linked pictures, CNN was there.

Many of the experiments carried aboard STS-3 were listed as Detailed Test Objectives, or DTOs. For the full schedule duration of the mission the two-man crew worked at systematically completing their DTOs. Finally, on the mission’s last scheduled day the two astronauts suited up, closed the payload bay doors and prepared for reentry. Heavy rains in California had wetted the normally dry Lake bed at Edwards Air Force Base until the surface was "the consistency of Cream of Wheat." The flight test nature of the STS-3 mission dictated that the landing was to be conducted on a dry lake if at all possible. At this point in the Shuttle program the runway at KSC was untried, in fact only one Shuttle orbiter, the Enterprise, had made a landing on a concrete runway and that was a single landing made at Edwards back in 1977 during the ALT. NASA was simply not ready to allow the Shuttle to land in the confines of the concrete runway yet. Oddly, that lone runway landing had been made by a two-man crew the PLT of which had been Gordon Fullerton. That fact aside, NASA had elected, two weeks prior to the STS-3 launch, to land on the dry Lake at White Sands, New Mexico. Unfortunately, on the scheduled landing day a rare, but classic sandstorm suddenly blew up and brought with it severe turbulence, low visibility and drifts of gypsum powder across the runway. STS-3’s landing was waved off for 24 hours.

Dawn the following day at White Sands revealed absolutely perfect weather for the landing. This segment of the mission was scheduled to be test piloting to the greatest degree. There were final DTOs to be accomplished. Jack Lousma was required to test the auto-land system to a point far beyond normal operation and far beyond any previous flight. He was to take over manually at scheduled points during the entry and put in some small control inputs such as forward stick to neutral stick  to back stick than to neutral again, all at one second intervals. Then he was to reach up on the glare shield and punch the button that would activate the auto-land. In each of these cases the crew was to note how the auto-land responded. Lousma estimated that he did this procedure about 10 times. Interlaced with that a similar test sequence was performed in the roll axis as well as with the body flap. The same exercise had been performed in the simulator numerous times but what the crew of STS-3 was to discover was that the simulator and the actual orbiter did not perform alike at some points. In addition to the auto-land response DTO, the crew was also scheduled to test the auto-land all the way down the flight path, nearly to the ground. It is worth noting that the computer’s auto-land software had not yet been written for the final flare, touchdown and rollout. The auto-land software had only been written to the point of the inner glide slope. For those of you reading who have not flown high performance or heavy aircraft, that sort of an approach may sound like a milk run, but in fact it is not. Most pilots of such aircraft would rather hand-fly it down. Personally, I prefer to hand-fly a turbo prop from about 10,000 feet down and a jet from 18,000 feet down. Every Shuttle pilot I have talked to feels the same way and would rather hand-fly as much as they can all the way down. But in the case of STS-3, Jack Lousma’s DTO was to ring out the auto-land, and so he did.

CDR Lousma executed the testing through reentry and the switch-overs appeared to be normal. Than as directed by the profile he engaged the auto-land at 12,000 feet on the outer glide slope. At that time the Shuttle approach PAPI indicated two red and two white on a 19° glide slope and on center line. "That was the last time I saw a stabilized airspeed,” Lousma recalled, “although the automatic system controlled OGS (Outer Glide Slope) well, including the transition from OGS to IGS (Inner Glide Slope)." Unexpectedly the auto-land system made slight right roll correction probably to nullify the effect of a right crosswind at that altitude. Then the crew felt the speed brakes close immediately. This was abnormal and allowed the orbiter to accelerate to 285 knots. Normally in a hand-flown approach the Shuttle pilots use the speed brakes in degrees to manage the orbiter’s energy and blend airspeed and altitude. As the auto-land computer sensed the speed increase, it opened the speed brakes again to a greater than normal degree. Now the airspeed slowed to a speed which was below a software set-switch that would automatically fully close the speed brakes at 4000 feet if the speed was too low. The speed brakes were not designed to move suddenly from highly open to fully closed and then back again. In this critical portion of the approach the auto-land was over-correcting the travel of the speed brakes. On a manual approach the crew would have closed the speed brakes at 2,500 feet to prevent them from cross-coupling with the pre-flare pull-up at 1,750 feet. On the STS-3 auto-land approach the speed brakes closed 1,500 feet early which caused an acceleration prior to entering the pre-flare that was carried to the end of the pre-flare. In short the auto-land system was causing wide swings of the speed brakes during the most critical portion of the landing rather than mimicking the inputs of a manual approach. It was later discovered that the software in the simulator that everyone had considered to be the mirror image of the software in the orbiter, was not that at all.

As directed in the flight plan, Lousma took over manual control when the orbiter was stabilized on IGS. This took place between 200 and 150 feet AGL. As he took control he noted that the controls “felt different” than they should at that point. The vehicle was carrying more airspeed than normal at that phase of flight. Although he was 5 knots over the gear deploy speed he called for the gear and Fullerton lowered the landing gear. It is important to note here, again for any non-pilots who may be reading this, that deployment of landing gear is normally dependent on speed and not the observations of persons on the ground or the proximity of the aircraft to that ground. In the case of STS-3, to people on the ground it appeared as if the gear had come down low and late. In fact it was deployed somewhat early as the vehicle was 5 knots too fast.

Another result of the higher speed was that the touchdown point was now farther down the runway when desired. Like any good test pilot Lousma negated the error by simply planting the aircraft on the runway. Important here to also note one thing about the Shuttle that a lot of people do not understand. When rolling  with their wheels on the ground the Shuttle orbiters have a negative Angle Of Attack (AOA). Thus during the landing rollout after the main gear is on the ground as the vehicle begins to slow the nose will drop through from a positive AOA, to a neutral and then to a negative AOA very rapidly. The pilot is required to compensate by consciously "flying" the nose down to the ground. Originally the orbiter’s nose gear had been designed with a longer strut to compensate for this characteristic, but a subsequent weight scrub had negated that idea. Lousma was well-prepared for this characteristic, but as Columbia's main gear contacted the runway the nose immediately began to go down. The plan, however, had been for the CDR to hold nose up and perform aerodynamic braking from the point of touchdown until slowing to 165 knots. Instead, the Columbia's nose gear was now headed toward the runway at 220 knots. Instinctively, Lousma made a quick pitch-up input with the rotational hand controller, but the nose continued down. He immediately entered a second input which was greeted with a rapid nose up response. He corrected by putting an additional nose down response and this time regained authority and the nose wheels were placed on the runway. The orbiter rolled to a stop 13,723 feet down the runway. It was later discovered that there was a divergence in the longitudinal contrast software for the Shuttle’s landing configuration. That, combined with the additional speed that the auto-land system had left the orbiter with, conflicted with the gain setting in the software. This caused the fly-by-wire system to impose an abnormal delay between the pilot’s inputs into the hand controller and the movement of the control surfaces. In simpler terms, (engineers please forgive me for this simplification) the first stick input to counter the dropping of the nose was delayed because the software sensed that the orbiter was going too fast for such a command to be executed. Then when the second input was made the software added it to the first command and then that total was transmitted to the control surface which responded in kind. Lousma had nothing to do with this process other than making intuitive corrections. Had he done nothing, the nose gear would have hit the runway at 220 knots and may very well have been damaged or sheared off.

Of course to the uninformed observer, such as some in the media and some present-day Internet "experts," it appeared as if Lousma had botched the landing. In one good example of this CBS news’ reporter Terry Drinkwater hyperbolized on the evening news that day that this was; "The Shuttle’s least perfect landing." He then went on to further exaggerate; "The landing gear is programmed to come down when the spacecraft slows to 311 miles per hour, (270 knots,) but when the speed finally dropped to that, the Columbia was extremely low. There were only 5 seconds between wheels down and touchdown. Close! Next, as the nose seemed to be gently settling- suddenly it lifted again. Then apparent control, but the force of the forward speed and the weight on the nose gear was close to its tolerance." He added that this was likely caused by of a gust of wind or more likely a computer error, or "pilot mistake."

Thus began the myth of the "wheelie landing."

Some people then and now picture Jack Lousma in a state of embarrassment immediately after the landing of STS-3. In fact quite the opposite is true. He was happy and excited and somewhat tickled that on this test flight, during the entry, approach and landing the crew had uncovered a series of flaws in the auto-land system as well as their impact on the software for the fly-by-wire system. Those problems could now be corrected so that future Shuttle pilots would not experience the same problems. That was the purpose of his flight- to test. It is also worth denoting the fact that on the previous two flights, as well as all of the ALT flights, the crews had only tested the auto-land for very brief periods of flight and no one prior to STS-3 had tested it all the way down to the IGS, let alone exercised it as had been done by the STS-3 crew. This was flight test at its best and the results improved future missions.

Yet, even today, three decades after STS-3 you can look on YouTube and find videos of the “wheelie landing.” And if you have a strong stomach, you can read moronic comments about it left by people whose total flight experience extends no farther than their keyboard and whose research into the event goes no farther than repeating the quips that others have posted. The same is sadly true of most Internet spaceflight forums.

Jack Lousma retired from NASA in 1983 and went to serve as the President of CAMUS Inc. Gordon Fullerton went on to the CDR’s seat on the 19th Shuttle mission, STS-51F. Interestingly, unlike many other astronauts, Fullerton’s pilot roots are not in fighter planes- rather he is a bomber pilot who started out in the B-47 with SAC. He flew the retirement flight of the famed 008 B-52 “Balls 8” mother ship.

As a post script, in the autumn of 1982 I had been hired to be an “enhancement speaker and guide” on the Great Lakes aboard the cruise ship C. COLUMBUS. When I was hired they informed me that the other speaker would be Astronaut Jack Lousma. At the time they asked if I knew who he was. I played it cool, “Oh, yeah- I know who he is.” Of course I could hardly wait to get aboard the boat. Unfortunately, my duties aboard the vessel left very little time to just hang out with Mr. Lousma. We did get a couple of chances to just stand and talk, however. On the other hand, my mom, who I had taken along as my guest since my wife refused to go along on “another cruise,” became pals with Mrs. Lousma. One day, after Mr. Lousma and I had each finished our individual presentations we were standing there chatting about the Shuttle and mom spoke up; “Ya’ know,” she boasted in the best of mid-western manners, “I was down there and saw one of those Shuttles take off.” I placed my hand on her shoulder and broke the news to her, “Mom… you saw HIS Shuttle launch.” We all had a good laugh at her expense.

FMI: www.nasa.gov

Advertisement

More News

ANN's Daily Aero-Linx (04.15.24)

Aero Linx: International Flying Farmers IFF is a not-for-profit organization started in 1944 by farmers who were also private pilots. We have members all across the United States a>[...]

Classic Aero-TV: 'No Other Options' -- The Israeli Air Force's Danny Shapira

From 2017 (YouTube Version): Remembrances Of An Israeli Air Force Test Pilot Early in 2016, ANN contributor Maxine Scheer traveled to Israel, where she had the opportunity to sit d>[...]

Aero-News: Quote of the Day (04.15.24)

"We renegotiated what our debt restructuring is on a lot of our debts, mostly with the family. Those debts are going to be converted into equity..." Source: Excerpts from a short v>[...]

Airborne 04.16.24: RV Update, Affordable Flying Expo, Diamond Lil

Also: B-29 Superfortress Reunion, FAA Wants Controllers, Spirit Airlines Pulls Back, Gogo Galileo Van's Aircraft posted a short video recapping the goings-on around their reorganiz>[...]

ANN's Daily Aero-Term (04.16.24): Chart Supplement US

Chart Supplement US A flight information publication designed for use with appropriate IFR or VFR charts which contains data on all airports, seaplane bases, and heliports open to >[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2024 Web Development & Design by Pauli Systems, LC