AI summary by TwinMind

NASA's 150 Million Dollar Coding Error

Real Engineering

6m 53s

Spaceflight Malfunctions Overview

  • Simple malfunctions have plagued spaceflight from inception
  • Pushing things into space with controlled explosions is treacherous
  • Many rocket launches failed over simple problems
  • Examples of catastrophic failures:
    • Soyuz 11: First and only humans to die in space
      • Explosive bolts designed to fire sequentially fired simultaneously
      • Combined force loosened seal separating crew from vacuum
      • Crew dead within one minute
    • SpaceX first launch failure
      • Rocket exposed to sea air too long, allowing rust
      • Aluminum nut securing fuel pump inlet pressure transducer failed
      • Fuel leaked down engine/thrust chamber, caught fire
      • Fire caused pneumatic pressure loss, valves closed, thrust cut
      • Rocket fell from sky due to aluminum corrosion weakness
      • SpaceX switched to rust-resistant stainless steel fasteners
        • Cheaper but 2.5x heavier

Mariner 1 Mission Details

  • July 22nd, 1962: Intended first successful planetary flyby in human history
  • Launched from Cape Canaveral on mission to Venus
  • Goal: Collect data on Venus temperature and atmosphere
  • Flight duration: 293 seconds before self-destruct
  • Range Safety Officer commanded self-destruct over unpopulated Atlantic
  • Trajectory taking rocket toward crash in shipping lanes or land
  • Booster performing nominally but rocket took erratic left turn
  • Steering commands unresponsive
  • 6 seconds remaining before Mariner 1 probe separation when destroyed

Atlas Agena Rocket Navigation System

  • Used two radar systems for trajectory maintenance:
    • Rate system: Measured velocity using Doppler shift from ground beacon
    • Track system: Measured distance/angle relative to launch site antenna
  • Systems worked together for redundancy and error margin
  • Previous Atlas Agena launches successful with both systems

The Critical Error

  • Rate system failed during launch
  • Track system should have handled navigation alone
  • Code interpreting distance/angle measurements had simple error
  • Missing overbar (hyphen) in mathematical notation
  • Correct notation should have had overbar indicating first derivative (velocity)
  • Overbar meant to average values for smooth velocity reading, removing fluctuations
  • Without overbar: Guidance computer received erratic velocity information
  • Computer tried to compensate, leading to actual erratic flight
  • Range Safety Officer recognized problem and initiated self-destruct

1962 Programming Environment

  • Early days of programming, no fancy computer interfaces
  • No compiling software or error detection
  • Code written in Fortran (Formula Translation)
  • Handwritten or typed on typewriter
  • Required translation to binary machine code via punch cards

Punch Card System Process

  • Thick rectangular paper with rows of numbers 0-9
  • 80 columns, each card = one line of code
  • Each column = one character
  • Numbers: Punch corresponding number
  • Letters/symbols: Required additional hole combinations
  • Manual typing on card punch machine for each code line
  • Cards sent through compiler for binary conversion
  • Hole present = circuit completed = binary signal
  • Compiler produced new cards computer could understand
  • Much more tedious and difficult to fact-check than modern interfaces

Mission Cost and Resolution

  • Mistake cost NASA $18.5 million in 1962 ($150 million today)
  • Code corrected after failure
  • Mariner 2 launched one month later
  • 3.5 month flight to Venus successful
  • Achievements:
    • First detection of solar winds (charged particles from Sun)
    • Measured interplanetary dust levels
    • Venus flyby revealed temperature/atmosphere data
    • Now floating in orbit around Sun

Brilliant Sponsorship Content

  • Learning from mistakes common theme in human history
  • Classical mechanics course example
  • Problem-solving approach: Overview → problem → feedback
  • Correct answer = advance; wrong answer = explanation and teaching
  • Learning by allowing failure and acknowledging it happens
  • Correcting misconceptions furthers understanding
  • Link: brilliant.org/realengineering
  • First 73 people get 20% off annual premium subscription

TwinMind

Get summaries like this for your own meetings

TwinMind takes notes in the background during meetings, lectures, and calls, then writes the summary for you.

Free plan to get started

No bot joins your calls

Phone, desktop & Chrome apps

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome