Apollo 11 was the historic space mission that first landed people on the moon. On July 20, 1969, the lunar module Eagle touched down in the Sea of Tranquility with Neil Armstrong and Buzz Aldrin aboard, while Michael Collins orbited above. Armstrong stepped onto the surface about six and a half hours later, becoming the first human to walk on another world.

That answer is simple. The mission itself was not. Apollo 11 succeeded because thousands of engineered decisions, timing margins, and human judgments aligned within a narrow window. Understanding how the landing worked explains why it remains the reference point for every crewed lunar attempt since.

Descent engine and guidance mechanism

The lunar module descended using a single throttleable engine, the descent propulsion system. It burned a hypergolic propellant combination: hydrazine fuel mixed with nitrogen tetroxide oxidizer. These chemicals ignite on contact, so the engine needed no spark or ignition sequence. That reliability mattered, because a restart failure at low altitude would have been fatal.

Guidance was split between two computers. The primary guidance, navigation, and control system ran on the lunar module. The Apollo Guidance Computer executed about 2,000 instructions per second with roughly 72 kilobytes of usable memory. An abort guidance computer served as backup, using simpler algorithms to steer the crew back to orbit if the primary failed.

The descent had two phases. The braking phase lasted about eight minutes and removed most of the spacecraft's orbital velocity. The approach phase, beginning around 7,500 feet (2,300 meters) altitude, gave the crew visual control over the final landing. During approach, the commander could take semi-manual control, tilting the lander to fly toward a chosen spot.

Why this architecture? Because mission planners could not guarantee a computer alone would handle every surprise. Splitting authority between automated guidance and a human pilot created redundancy at the moment of highest risk. The computer flew the trajectory; the astronaut judged the terrain.

Quantified context: speed, fuel, and timing

Apollo 11's descent converted enormous kinetic energy into a controlled touchdown. The lunar module entered powered descent at roughly 5,000 feet per second (about 1,500 meters per second) relative to the moon. The descent engine had to shed that velocity while managing propellant reserves.

The numbers were tight. The descent stage carried about 18,000 pounds (8,200 kilograms) of propellant. Planners calculated a reserve margin, but actual consumption depended on how much hovering and maneuvering the crew needed. During Apollo 11, the landing radar and computer exchanged data, and Armstrong flew a semi-manual final approach past a boulder field.

Timing mattered as much as fuel. Each extra second of powered flight consumed propellant. The mission had a defined "landing commit" point; past it, aborting to orbit was no longer feasible, and the crew had to land.

The Apollo Guidance Computer also faced a workload problem. During final descent, alarms code 1202 and 1201 sounded. These indicated executive overflow: the computer was being asked to process more tasks than its cycle time allowed. Engineers at MIT had designed the software to shed low-priority tasks and keep the critical guidance running. The landing continued.

That counterintuitive detail is worth sitting with. The most famous landing in history nearly triggered an abort because of a software overload, and it proceeded because the software was built to degrade gracefully.

Timeline of the landing sequence

Time (UTC), July 20, 1969 Event Approximate altitude
20:05 Powered descent initiation About 50,000 feet
20:10 Braking phase ends About 7,500 feet
20:14 Landing radar updates guidance Low altitude
20:15 Computer alarms 1202, 1201 Approach phase
20:17 Armstrong takes semi-manual control Near surface
20:17:40 Contact light, engine cutoff Surface
02:56 (July 21) Armstrong first step Surface

The gap between touchdown and the first step was deliberate. The crew ran checklists, confirmed the lander was stable, and prepared for extravehicular activity. Rushing would have risked a depressurization or equipment failure before anyone had walked.

Edge cases and near-failures

Apollo 11's success can obscure how many variables had to break correctly.

The landing site was chosen partly for safety, but the actual approach carried the crew over a crater and boulder field, forcing Armstrong to fly farther downrange than planned. The primary guidance computer's rendezvous radar was left on during descent, feeding unnecessary data into the computer and contributing to the overload alarms. A procedural choice, not a hardware fault, created the stress. Propellant margins were thinner than nominal. Post-mission analysis suggested the descent stage had roughly 20 seconds of hover fuel remaining at touchdown, depending on the accounting method used. The lunar module's engine had no throttle-up capability beyond its design range; if the crew needed more thrust, they could not get it. Communication delays and limited bandwidth meant mission control could not see everything the crew saw; decisions rested heavily on Armstrong's judgment.

A professional caveat: the "20 seconds remaining" figure circulates widely, but different sources count propellant reserves differently. Treat exact residual-fuel numbers as reconstruction, not as a live gauge reading.

Misconceptions about the first moon landing

Several persistent misunderstandings distort the story.

First, Armstrong did not manually fly the entire descent. The computer guided most of it, and he took partial control near the end to avoid hazards. The popular image of a pilot "landing by hand" oversimplifies the division of labor.

Second, the landing was not a single continuous broadcast moment. The descent took about 12 minutes of powered flight, and the first step came hours later. Treating July 20, 1969 as one instantaneous event flattens the sequence.

Third, the alarms did not mean the computer failed. The 1202 and 1201 codes signaled task overload, and the software's priority scheduling kept guidance alive. A system that crashed would have forced an abort.

Fourth, Apollo 11 was not the only mission capable of a first landing. Apollo 10 flew a full dress rehearsal in May 1969, descending to about 50,000 feet before returning to orbit. Apollo 11 was the first attempt with landing as the objective.

Comparison with other crewed lunar landings

Mission Landing date Site Notable characteristic
Apollo 11 July 20, 1969 Sea of Tranquility First crewed landing; computer alarms
Apollo 12 November 19, 1969 Ocean of Storms Precision landing near Surveyor 3
Apollo 14 February 5, 1971 Fra Mauro Landing after Apollo 13 abort
Apollo 15 July 30, 1971 Hadley-Apennine First lunar rover use
Apollo 16 April 21, 1972 Descartes Highlands Highlands sampling
Apollo 17 December 11, 1972 Taurus-Littrow Last crewed landing; geologist aboard

The comparison shows a pattern. Later missions improved precision, added surface mobility, and extended science time. Apollo 11 proved the basic capability under the tightest uncertainty.

Practical actions for verifying the claim

If you want to confirm the first landing independently, use primary sources rather than summaries.

Check NASA's Apollo 11 mission report and the Apollo Lunar Surface Journal, which transcribe the actual air-to-ground communications. Compare the timeline against the published descent transcript, noting the alarm codes and the altitude callouts. Verify the landing site coordinates (roughly 0.67 degrees north, 23.47 degrees east) against lunar mapping data. Distinguish "first landing" from "first step" and "first mission": Apollo 11 satisfies all three, but the terms are not interchangeable. Cross-check any fuel-margin claim against the mission report, and treat rounded figures as estimates.

These steps matter because secondary accounts often compress the sequence or drop the alarm episode entirely.

Limitations of what the record can tell us

The Apollo record is well documented, but some details remain reconstructed. Propellant residuals, exact altitudes at each second, and the computer's internal task scheduling are inferred from telemetry and post-flight analysis, not from a perfect continuous log. The transcripts capture what was said, not every thought or instrument reading.

A second limit is interpretive. Historians debate how much credit belongs to the guidance software versus Armstrong's piloting. Both were necessary; assigning percentages is not a scientific question.

A third limit is scope. Apollo 11 answers which mission first landed people on the moon, but it does not answer whether the program was worth its cost, which is a policy and historical judgment.

For ordinary science reading, no medical, legal, or financial disclaimer applies here. The evidence is archival and engineering-based, and the main caution is to prefer primary mission documents over condensed retellings when precision matters.

The core answer stands: Apollo 11, July 20, 1969, Armstrong and Aldrin on the surface, Collins above. Everything else is the mechanism behind that sentence.