NASA Tests RS-25 Engine No. 10001 for 200 Seconds at Stennis
NASA conducted a hot fire test of RS-25 engine No. 10001 on November 18, 2026, at the Fred Haise Test Stand at NASA’s Stennis Space Center near Bay St. Louis, Mississippi.
Test teams fired the developmental engine for the planned duration of three minutes and 20 seconds (200 seconds).
While this developmental engine will not be used in flight, the hot fire test provides NASA and NASA’s prime contractor L3Harris Technologies with the capability to capture critical data to improve engine performance and reliability for future Artemis missions.
For the Artemis IV Moon landing mission in 2028, the SLS rocket will launch astronauts aboard the Orion spacecraft from NASA’s Kennedy Space Center in Florida. This mission will be a key step in the agency’s broader goals to explore the lunar South Pole, establish an enduring human presence on the lunar surface, and build on the agency’s foundation for the first crewed mission to Mars.
For each Artemis mission, four RS-25 engines produce up to 2 million pounds of combined thrust to help launch the SLS rocket.
All RS-25 engines are tested and proven flightworthy at NASA Stennis prior to use. Tests are conducted by a team of operators from NASA, L3Harris, and Nova Space Solutions.
The RS-25 is not a new engine. Its lineage runs back to the Space Shuttle era, when it served as the orbiter’s main engine. NASA later brought the design back for the Space Launch System, the heavy-lift rocket at the center of the Artemis program. The decision reused proven hardware and a deep base of operating experience instead of starting a new engine from nothing.
That heritage cuts two ways. On the plus side, engineers inherit decades of knowledge about how the engine behaves. On the minus side, the engine was designed for a different vehicle and a different mission profile. Adapting it for SLS has required changes and fresh testing. A developmental firing like the one on November 18 is part of that ongoing adaptation.
History also offers a caution. Reusing old hardware does not remove the need for fresh data. Production changes, supplier changes and new operating conditions can all introduce surprises, and the test stand is where those surprises should show up. NASA’s decision to keep running development engines suggests the agency expects to keep learning about the design.
The Fred Haise Test Stand is one of the large engine test facilities at NASA’s Stennis Space Center, the agency’s rocket propulsion testing site on the Mississippi Gulf Coast. NASA used it for this firing. The stand holds an engine in place, feeds it propellant, captures data from instrumentation and absorbs the exhaust plume. Everything about its design serves one purpose, which is to let an engine run hard while staying safely bolted down.
Stennis sits near Bay St. Louis, Mississippi, which makes it a regional anchor for propulsion work. The facility’s role in the Artemis supply chain is real and ongoing, and the November 18 test is a reminder that much of the program’s engineering effort happens on the ground, far from any launch pad.
Engine No. 10001 will not be used in flight, and NASA said so directly. That detail changes how readers should interpret the whole story. This was not a final acceptance test for a specific rocket. It was a development firing meant to feed engineering knowledge back into the program.
Why spend a whole engine on that? Because development hardware can be pushed in ways that flight hardware cannot. Engineers can instrument it more heavily, try off-nominal conditions, and tear it down afterward to inspect parts that would be sealed forever on a flight unit. The engine is, in effect, a research instrument with a nozzle.
The comparison row on instrumentation and teardown reflects general engineering practice, not statements NASA made about this specific engine. NASA has not detailed its inspection plans. We include the row because it explains why a development unit has value even though it never leaves Mississippi.
NASA identified L3Harris Technologies as its prime contractor for the test effort. That matters because the contractor, not the agency, carries day-to-day responsibility for the engine hardware and its production. The agency owns the test objectives and the stand. The company owns the machine under test. When the two sides work well together, a firing like this one produces data that flows straight into design decisions.
The available NASA material gives no thrust figure, no chamber pressure, no temperatures, no cost and no schedule for follow-up tests. It does not say whether the 200-second run met every test objective. It does not name a flight assignment, because none exists for this engine.
Those omissions are not unusual. Agencies often release a short report with imagery after a test and hold the engineering detail for technical reviews. Reporters and analysts can still ask for more. Useful follow-up questions include how many more firings NASA plans for this engine, what instrumentation it carries, and how the findings will feed into production changes.
Until NASA or L3Harris answers, the right approach is to report the confirmed facts, label inference as inference and resist the urge to turn a short release into a long narrative. Ground-test news rewards patience. The most important results often arrive quietly, in program reviews and in the absence of anomalies on later flights.
Sources
- shattered.io: NASA RS-25 Engine Test: 200 Seconds at Stennis
- nasa.gov: NASA Conducts Latest RS-25 Engine Test in Support of Future Artemis Missions - NASA
This article was drafted with AI assistance and checked against the sources above. Company claims are reported as claims. Cover image is AI-generated.


