Dick Scobee would want to see what you were working on. Not hear about it — see it. Open the hood. Spread the blueprints. Show him the problem. He was a hands-on person in a profession that increasingly rewarded administrators, and the distinction defined him from the moment he enlisted in the Air Force as a mechanic and climbed to the pilot’s seat through sheer persistence.
He grew up in Auburn, Washington. His family didn’t have money. He rebuilt engines as a teenager — not as a hobby but as an economic activity. He could take apart a transmission and reassemble it faster than most certified mechanics. He enlisted at 19, worked as an aircraft mechanic, and then did something that the Air Force didn’t make easy in the 1960s: he earned his college degree while serving, got himself into pilot training, and flew over 6,500 hours in 45 types of aircraft.
He flew combat in Vietnam. He flew test missions at Edwards Air Force Base. He flew the 747 that carried the Space Shuttle on its back during approach and landing tests. Each step was a progression from mechanic to test pilot to astronaut, and each step was earned through the same method: show up, learn the system, fix the part that’s broken.
How He Worked
Scobee ran the Challenger crew the way he ran an engine rebuild: systematically, collaboratively, with the assumption that every person on the team had knowledge he didn’t and that the team’s job was to pool that knowledge into a functioning whole.
His crew was the most diverse in NASA history at that time: Christa McAuliffe, the teacher. Judith Resnik, the electrical engineer. Ronald McNair, the physicist. Ellison Onizuka, the flight test engineer. Gregory Jarvis, the satellite specialist. Mike Smith, the pilot. Scobee integrated them the way he integrated aircraft components: each person in their correct position, each person trusted to perform their function, the commander’s job being coordination rather than control.
He’d want the same from you. Whatever your project, he’d ask: who’s doing what? Are they in the right position? Does each person know what the person next to them is doing? He distrusted hierarchies that prevented information from flowing upward. A mechanic who sees a problem and can’t tell the pilot about it is a design flaw in the organization, not in the mechanic.
The Project
Scobee’s project was always the next flight. The 51-L mission — Challenger’s last — was a Space Shuttle mission carrying the Teacher in Space payload. Scobee had selected the mission profile, trained with the crew for months, and prepared for the launch with the thoroughness of a man who’d spent decades in test aviation and understood that the distance between a successful flight and a catastrophe was measured in the quality of the preparation.
He didn’t know about the O-ring debate. The discussion between Morton Thiokol engineers and NASA management about whether to launch in 36-degree temperatures happened above his operational level. He was the commander of the vehicle. He was not in the room where the decision to launch was made. This fact — that the commander trusted the system he operated within, and the system failed him — is the detail that makes the Challenger disaster a systems failure rather than a human one.
He was 46. He’d spent 27 years building from mechanic to commander. The progression was the kind of story America tells itself about merit — start at the bottom, work hard, reach the top. He reached the top. The top failed.
The Result
June Scobee Rodgers, his wife, founded the Challenger Center for Space Science Education after his death. The center has hosted millions of students in simulated space missions designed to teach teamwork, problem-solving, and the kind of collaborative thinking that Scobee practiced: everyone has a role, everyone’s role matters, the mission succeeds or fails as a group.
Scobee would have wanted the center more than the memorial. The memorial is about the loss. The center is about the method — the mechanic’s approach to complex problems, applied to education. Take the system apart. Understand each component. Put it back together better than you found it. Work with the team. Trust the team.
He started as a mechanic and became a shuttle commander through twenty-seven years of showing up, learning the system, and fixing what was broken. The system he trusted was the one that failed. The teaching method he practiced is the one that survived.
Talk to Dick Scobee — show him the problem. He’ll want to open the hood.