The Apollo Knowledge Trap
AEROSPACE INDUSTRY ANALYSIS / KNOWLEDGE PRESERVATION
Why Video May Be the Cure
By Pseudo Publius | Aerospace Industry Analysis | 25 April 2026
BLUF — BOTTOM LINE UP FRONT
The most expensive lesson of the Apollo program was not technical but institutional: the United States lost the ability to build the F-1 engine within a generation of its retirement, and the same pattern is now visible in the Avcoat heat shield reformulation that drove the Artemis I char-loss anomaly. NASA's own knowledge-management apparatus — the Lessons Learned Information System and APPEL Knowledge Services — captures decisions and outcomes in text, but not the embodied manufacturing skill that determines whether complex hardware actually works. Meanwhile, the U.S. Army, Air Force, and commercial aerospace primes are quietly converting to augmented-reality and video-based work instruction, with measured error reductions of 36 to 100 percent in maintenance tasks. As DoD and NASA prepare for sustained lunar operations and a workforce transition in which 25 percent of aerospace employees are at or beyond retirement eligibility, the question is no longer whether video and AR-based capture should supplement engineering drawings and text procedures, but whether the institutions can adopt them fast enough to preserve the manufacturing capability the next generation of programs will require.
The Engine We Cannot Rebuild
In January 2013, a small team of NASA engineers at Marshall Space Flight Center wheeled a 50-year-old artifact onto Test Stand 116 in the East Test Area and lit it. The artifact was the gas generator from F-1 serial number F-6049 — an engine originally manifested for Apollo 11, pulled before flight due to a glitch, and stored at the Smithsonian for four decades. For roughly twenty seconds it produced about 31,000 pounds of force, the small piece of the larger 1.5-million-pound-thrust machine that once powered the Saturn V first stage.
The hot fire was not a celebration. It was an audit. NASA was evaluating Pratt & Whitney Rocketdyne and Dynetics' proposed F-1B booster for the Space Launch System, and the engineers needed to understand what they actually had. Marshall propulsion engineer Nick Case told Aviation Week's contemporaries at the time that his team had "pulled F-1 engine drawings and data packages and studied an F-1 engine that we had on hand at Marshall." The team used structured-light 3-D scanning to produce CAD models of the gas generator and selective laser melting to fabricate test parts. The original drawings, in other words, were not sufficient to build the part. The component had to be reverse-engineered from a museum piece.
This is the central, embarrassing fact of post-Apollo American aerospace: the F-1 cannot be built today, even though the blueprints survive. Industry observers and NASA engineers attribute this to a combination of retired and deceased craftsmen who held the manufacturing know-how, hand-fabrication techniques no longer in routine practice, materials such as the original Inconel X-750 forging stock that are no longer produced in identical specification, and design notes that were kept on scraps of paper or in the heads of engineers under deadline pressure during the 1960s. The F-1B that ultimately competed for the SLS Advanced Booster contract in 2015 was — in the candid assessment of engineers involved — less a rebuilt F-1 than a new engine inspired by it, using modern manufacturing techniques because the originals could not be replicated. The F-1B lost the competition to a five-segment derivative of the Shuttle Solid Rocket Booster, and the question became academic. The capability remained lost.
"The original drawings were not sufficient to build the part. The component had to be reverse-engineered from a museum piece."
The Avcoat Sequel
If the F-1 case were unique, it might be dismissed as a Cold War curiosity. It is not unique. The Artemis I heat-shield investigation, formally closed by NASA in December 2024, makes the institutional pattern unmistakable.
Avcoat 5026-39 is the ablative material developed by Avco Corporation for the Apollo Command Module heat shield. Composed of silica fibers in an epoxy-novolac resin, it performed flawlessly across Apollo's lunar-return reentries. When NASA selected Avcoat for Orion, the formulation had to be modified to comply with environmental legislation enacted after Apollo, and the manufacturing approach was redesigned: instead of hand-filling more than 300,000 honeycomb cells as Apollo had done, Lockheed Martin's process at Michoud Assembly Facility produced fewer than 200 pre-machined Avcoat blocks bonded to a titanium-and-composite substrate.
On 11 December 2022, Orion returned from its uncrewed lunar flyby and made the fastest, hottest reentry of any human-rated capsule. Internal temperatures remained safe; the vehicle splashed down on schedule. But post-flight inspection revealed something engineers had not predicted. More than 100 locations on the heat shield had shed charred material in chunks rather than ablating uniformly. The trail of debris was visible in entry imagery.
Two years of investigation, more than 100 arc-jet tests at NASA Ames, and detailed sampling of approximately 200 Avcoat specimens at Marshall produced a specific technical answer. During Artemis I's skip-entry profile, Orion dipped into the upper atmosphere, climbed back out, and reentered. Between dips, the outer surface cooled but the underlying material was still hot, undergoing pyrolysis and producing gas. The reformulated Avcoat lacked sufficient permeability for the gas to escape through the char layer, so internal pressure built up and blew chunks of material away — a phenomenon engineers call spallation.
The most striking sentence in the public record is the one engineers familiar with the investigation have made repeatedly: Apollo engineers were aware of the permeability issue and designed around it. Apollo capsules used skip-reentry profiles without trouble. The Artemis Avcoat reformulation, undertaken decades later for legitimate environmental-compliance reasons, altered permeability in ways the ground-test program — which used heating rates higher than Orion actually experienced — failed to surface. NASA elected to fly Artemis II with the already-installed heat shield using a modified, steeper, lofted reentry trajectory; former NASA astronaut and heat-shield specialist Charles Camarda publicly disputed that decision, arguing in The New York Times that engineers do not fully understand the root cause. Artemis II returned successfully in April 2026, but the dispute illustrates the deeper problem: a working capability had been silently degraded across a generational handoff, and nobody knew until the artifact was used in flight.
A Pattern, Not an Accident
The literature on tribal-knowledge loss in U.S. aerospace and defense manufacturing is now extensive, and the pattern is consistent. Per Aspera, an industrial-policy organization that has documented several cases, cites the Fogbank example: in the early 2000s, the United States found it could not reproduce a classified interstage material used in nuclear warheads, because veteran staff had retired without recording the manufacturing process. Re-learning the lost knowledge cost roughly 5 years and $69 million, and delayed a warhead refurbishment program. The plutonium-pit case is similar: large-scale production halted in 1989, and the United States has struggled for more than three decades to restart the manufacturing line.
The aerospace workforce numbers underscore the urgency. PwC's analysis of Aerospace Industries Association data finds that 25 percent of A&D workers are aged 56 or older. Deloitte's 2025 industry outlook reports that 25 percent of the workforce has more than 20 years of experience and is at or beyond retirement eligibility. The Manufacturing Institute projects 2.1 to 4 million unfilled manufacturing positions by 2030. An IEEE GlobalSpec survey found that more than 60 percent of engineers view loss of tribal knowledge as extremely or very important — the fourth-ranked concern in the profession.
Apple CEO Tim Cook captured the macro picture in a widely reported 2024 remark: in the United States, a meeting of tooling engineers might not fill a room; in China, multiple football fields. The observation is anecdotal, but the structural data align. America has lost more than four million manufacturing jobs since 2000. Roughly a quarter of U.S. machinists and tool-and-die makers are over 55. The institutional muscle memory required to build complex, low-volume, high-precision hardware is atrophying at the same time the country is contemplating a sustained lunar presence and a contested Pacific.
What NASA's Knowledge System Actually Captures
NASA is not unaware of the problem. NASA Procedural Directive 7120.6A, revalidated with Change 1 in July 2024, establishes the agency's Lessons Learned Process, and the Office of the Chief Knowledge Officer operates a federated system that includes the Lessons Learned Information System (LLIS), the NASA Engineering Network, the APPEL Academy of Program/Project & Engineering Leadership, and ASK Magazine. The 2012 NASA Office of Inspector General audit (IG-12-012) found that the agency was spending roughly $750,000 annually on LLIS alone, and that JPL was the only NASA Center consistently contributing.
The deeper finding from both the OIG audit and the earlier 2002 GAO report (GAO-02-195) is that NASA's lessons-learned culture captures decisions and outcomes — what was done, what went wrong, what was concluded — but is poorly structured to capture process knowledge. The GAO noted "cultural barriers to the sharing of lessons learned, such as the lack of time to capture or submit lessons and a perception of intolerance for mistakes." The OIG noted that 6 of 10 NASA Centers did not cross-reference lessons to their engineering standards. The system records that the F-1 used a particular injector pattern; it does not record the welder's hand motion, the visual cue that distinguishes a sound braze from a marginal one, the cure-rate variability that depends on humidity and ambient temperature, or the dozens of small craft decisions that determine whether the artifact actually works.
This is the gap your retired senior engineer corps is pointing at, and it is the gap that text-based documentation systems — however well-administered — cannot fill on their own.
The YouTube Generation
Outside formal aerospace, an entirely different documentation regime has emerged in the past fifteen years, built almost without aerospace's participation. iFixit's photographic and video disassembly guides for thousands of consumer products have become the de facto repair documentation for most devices made in the past decade. YouTube has displaced manufacturer manuals as the primary technical reference for everything from automotive repair to surgical technique. Modern surgical training has institutionalized recorded procedures with expert commentary as a primary teaching modality, on the explicit recognition that surgical skill cannot be transmitted through text alone.
The reason is straightforward. Spatial relationships, hand motions, sequence dependencies, and the visual cues that distinguish correct work from incorrect work are tacit knowledge categories that text struggles with. A photograph captures static geometry; video captures motion, timing, and the auditory and visual feedback signals that experienced craftsmen use to know when something is right. The consumer-electronics workforce that grew up with these documentation forms now expects them as the default. The aerospace workforce that came up through engineering drawings and text procedures is retiring.
The Military Has Started to Move
The most aggressive institutional adopters of video and augmented-reality work instruction are not the prime contractors but the U.S. military services and the commercial firms that train them. The pattern is now well-documented and is accelerating.
On 14 April 2026 — eleven days before this report — the U.S. Army staged a public demonstration at the 4th Battalion, 27th Field Artillery Regiment motor pool at Fort Bliss, Texas, in which Bradley Fighting Vehicle maintainers and self-propelled artillery mechanics tested AR headsets that overlay maintenance procedures on the actual vehicle. The Army Combat Capabilities Development Command Armaments Center deployed the systems with tablets linked to the headsets. The DVIDS imagery release described the program in operational rather than experimental terms: "Innovation in maintenance means giving Soldiers the right information at the right time to keep systems operational and units mission capable."
The U.S. Air Force has taken the same direction further. The Air Force Institute of Technology conducted a structured study of the Manifest AR platform from Taqtile, used to train jet-engine mechanics. The published results found that technicians using traditional paper Technical Orders installed parts incorrectly 57 percent more often than technicians using the AR-based work instruction. Other military studies of AR maintenance documentation have reported error reductions in the range of 36 to 100 percent across various tasks. Booz Allen Hamilton, working with the Army, deployed a 5G-networked wireless XR training system at Fort Cavazos that allows subject-matter experts in remote locations to observe and coach trainees through AR headsets in real time — a capability the firm describes as a U.S. military first.
Microsoft's Integrated Visual Augmentation System (IVAS), built on a ruggedized HoloLens 2 derivative under a 10-year Army contract, has had a troubled development history but has shifted toward maintenance and training applications where its capabilities are better matched to the use case. Commercial defense training firms — DiSTI's VE Studio, Manifest, and others — now serve as primary contractors or major subcontractors on essentially every U.S. service maintenance-trainer program. The technical maturity is no longer in dispute. The institutional question is integration.
"Technicians using traditional methods installed parts incorrectly 57 percent more times than technicians using AR-based work instruction."
The Commercial Aerospace Lag
On the commercial-aerospace side, video-and-AR adoption is more uneven. Boeing has used video work instruction for major-assembly procedures since the 787 program, partly because distributed manufacturing across multiple countries and language groups required visual references that transcended text. Airbus pursues similar practices. Hexagon's Manufacturing Intelligence business has deployed laser-guided inspection systems for aircraft assembly that automate quality verification in ways that paper-based first-article inspection cannot match. AkzoNobel Aerospace Coatings announced drone-enabled inspection capabilities for fleet-wide coating maintenance at MRO Americas earlier this month.
But the documentation standards that govern aerospace certification — FAA, DoD, AS9100 — remain text-and-drawing-centered. Industry analyses of U.S. aerospace operational excellence in 2026 (TeepTrak's published OEE benchmarking) note that aerospace suppliers typically operate at 50 to 65 percent OEE, against 70 to 80 percent in automotive, with the structural drag attributed in significant part to documentation overhead: paper-based SPC, manual quality transcription, and certification-driven stoppages. The same analysis identifies real-time digital SPC and tablet-based digital work instruction as the practical path to capturing more of the improvable operational loss without compromising traceability.
Configuration management for video documentation remains an unsolved aerospace problem at scale. When a design changes, text and drawings update through formal change control. Video updates require re-shooting on a manufacturing floor that may no longer be configured for the original task, with workers who may no longer be qualified to perform it. Stale video showing superseded procedures could be more dangerous than no video at all. The aerospace primes have not yet collectively committed to solving these problems, and the certification authorities have not yet collectively required them to.
What a New Standard Would Look Like
A multi-modal documentation standard adequate to preserve manufacturing capability across generations would combine three representations:
CAD and engineering drawings as the geometric ground truth — what the artifact is supposed to be, with full dimensional and tolerance specification.
Text documentation for procedural logic, design rationale, requirements traceability, and the analytical reasoning that explains why the design is as it is.
Video documentation for the embodied skill — what proper manufacturing technique looks like, what failure modes look like, how skilled inspectors recognize problems before instruments confirm them, and the auditory and visual feedback signals that experienced craftsmen rely on.
Each form captures information the others cannot. CAD without text is geometry without rationale; text without CAD is interpretation without ground truth; both without video lose the embodied knowledge that distinguishes a working artifact from a nominally compliant one. The Department of Energy's Stockpile Stewardship Program — funded at roughly $15 billion annually — has been pursuing a version of this standard for nuclear-weapons manufacturing capability since the 1992 testing moratorium, including aggressive video documentation of retiring technicians explaining their craft. The Naval Reactors program, which has preserved deep technical capability across 70 years of the Navy's nuclear-propulsion fleet, achieves a similar result through extreme standardization, formal apprenticeship, and an explicit person-to-person knowledge-transfer pipeline. Both models are institutionally expensive. Both demonstrate that the problem is solvable when an organization treats long-term capability preservation as a first-class budget line.
A more bounded near-term proposal — and the one most likely to achieve traction in the current NASA and DoD acquisition environment — is preservation video. When a major manufacturing line is set up, dedicate explicit resources to systematic video capture of the actual processes, the inspection criteria, the failure modes, and the tribal-knowledge commentary that workers express when explaining their craft. Index this material against the formal documentation. Store it in long-term archives at appropriate classification levels. Make it available to future programs that may need to reconstitute the capability. The cost is modest relative to program development cost. The value is preserved against precisely the institutional decay patterns that destroyed Apollo's manufacturing base.
The Lunar Base Forcing Function
None of this is academic. The Artemis program is in the middle of a reformulated Avcoat campaign for Artemis III and beyond. The U.S. Army is fielding AR maintenance systems at Fort Bliss this month. China's lunar-program timeline — crewed landing by 2030, International Lunar Research Station partnership growing — is pacing competitive pressure on a U.S. infrastructure that has already demonstrated, twice, that it cannot reliably reconstitute capability across a generational gap.
A sustained lunar presence cannot be built on the documentation standards that built Apollo. The math of expendable architecture does not close at base scale, and the institutional knowledge required to support reusable cislunar transport, in-situ resource utilization, and surface infrastructure cannot be allowed to dissipate between programs the way F-1 and Avcoat capability dissipated. The aerospace-and-defense workforce that will operate that base in 2040 is the workforce that grew up watching YouTube tutorials. The documentation standard they need is the one this generation is now building, in fragments, across the U.S. Army motor pools, the Air Force jet-engine training schoolhouses, and the commercial aerospace shop floors that have already begun the transition.
The most important industrial lesson of Apollo was not how to build a Saturn V. It was that we did not know how to keep knowing. The technology to fix that problem now exists. The institutional commitment is the variable.
"The most important industrial lesson of Apollo was not how to build a Saturn V. It was that we did not know how to keep knowing."
Sources
All sources accessed 25 April 2026. URLs verified at time of publication.
NASA Official Releases & Documentation
[1] NASA. "NASA Identifies Cause of Artemis I Orion Heat Shield Char Loss." Press release, 5 December 2024. https://www.nasa.gov/missions/artemis/nasa-identifies-cause-of-artemis-i-orion-heat-shield-char-loss/
[2] NASA. "NASA Shares Orion Heat Shield Findings, Updates Artemis Moon Missions." Press release, 5 December 2024. https://www.nasa.gov/news-release/nasa-shares-orion-heat-shield-findings-updates-artemis-moon-missions/
[3] NASA. "F-1 Engine Gas Generator Test at Marshall." Marshall Space Flight Center, 24 January 2013. https://www.nasa.gov/exploration/systems/sls/multimedia/gallery/f1test_1.html
[4] NASA. "F-1 Gas Generator at Marshall's Test Stand 116." Marshall Space Flight Center image release. https://www.nasa.gov/image-article/f-1-gas-generator-marshalls-test-stand-116/
[5] NASA. NPD 7120.6A, "Knowledge Policy on Programs and Projects." Revalidated with Change 1, 10 July 2024. https://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPD&c=7120&s=6
[6] NASA. NPR 7120.6, "NASA Lessons Learned Process," Chapter 1. https://nodis3.gsfc.nasa.gov/displayCA.cfm?Internal_ID=N_PR_7120_0006_&page_name=Chapter1
[7] NASA APPEL Knowledge Services. "Lessons Learned Lifecycle and Highlights." https://appel.nasa.gov/lessons-learned/lessons-learned-lifecycle-and-highlights/
[8] NASA. "Knowledge Management (KM) Resources." NASA HQ Library bibliography. https://www.nasa.gov/general/knowledge-management-km-resources/
Government Audits & Investigations
[9] NASA Office of Inspector General. "NASA's Process for Acquiring Information Technology Security Assessment and Monitoring Tools." Report IG-12-012, 6 March 2012 (lessons-learned audit findings). https://oig.nasa.gov/wp-content/uploads/2024/02/IG-12-012.pdf
[10] U.S. Government Accountability Office. "NASA: Better Mechanisms Needed for Sharing Lessons Learned." GAO-02-195, January 2002. https://www.gao.gov/products/gao-02-195
Defense & Military AR/Maintenance Documentation
[11] U.S. Army / DVIDS. "Augmented Reality Transforms Army Maintenance and Training." Image series from Fort Bliss, Texas, 14 April 2026 (4th Battalion, 27th Field Artillery Regiment). https://www.dvidshub.net/image/9634766/augmented-reality-transforms-army-maintenance-and-training
[12] U.S. Army. "Improving Warfighter Readiness Using Augmented Reality." Army.mil article, 25 March 2025. https://www.army.mil/article/283803/improving_warfighter_readiness_using_augmented_reality
[13] Booz Allen Hamilton. "Developing a Military First for AR and VR Training." Case study, 17 July 2025 (Fort Cavazos 5G XR system). https://www.boozallen.com/insights/defense/developing-a-military-first-for-ar-and-vr-training.html
[14] Taqtile. "Military Aircraft Maintenance Training with Augmented Reality." Manifest AR platform case study referencing AFIT study of jet-engine mechanic training. https://taqtile.com/case-studies/jet-engine-maintenance/
[15] U.S. Army SBIR/STTR Program. "Augmented Reality/Virtual Reality (AR/VR) for Railroad Inspection and Maintenance." Topic announcement. https://armysbir.army.mil/topics/augmented-reality-virtual-reality-ar-vr-for-railroad-inspection-and-maintenance/
[16] DiSTI Corporation. "VR Military Training & Simulation Solutions." Defense industry portfolio. https://www.disti.com/marketing-solutions/defense
Aerospace Workforce & Knowledge-Transfer Analyses
[17] Society of Manufacturing Engineers / advancedmanufacturing.org. "The $10M Knowledge Gap: When Your Experienced Supervisors Can't Transfer What They Know." 3 March 2026. https://www.advancedmanufacturing.org/industries/aerospace-defense/the-10m-knowledge-gap-when-your-experienced-supervisors-can-t-transfer-what-they-know/article_9bce7393-744e-4c7c-b4a8-0050909329cd.html
[18] Per Aspera. "Tribal Knowledge's Comeback." Industrial-policy analysis, June 2025 (Fogbank, plutonium-pit, F-1 cases). https://www.peraspera.us/tribal-knowledges-comeback/
[19] Siemens Digital Industries Software. "Workers Are Departing and It's Rattling the Aerospace Industry." 10 April 2020 (citing IEEE GlobalSpec 2019 Pulse of Engineering survey on tribal-knowledge concerns). https://blogs.sw.siemens.com/ee-systems/2020/04/10/workers-are-departing-and-its-rattling-the-aerospace-industry/
Artemis I/II Heat-Shield Coverage
[20] Space.com. "The Artemis 1 Moon Mission Had a Heat Shield Issue. Here's Why NASA Doesn't Think It Will Happen Again on Artemis 2." February 2026. https://www.space.com/space-exploration/artemis/the-artemis-1-moon-mission-had-a-heat-shield-issue-heres-why-nasa-doesnt-think-it-will-happen-again-on-artemis-2
[21] CBS News. "As Artemis II Heads Back to Earth, Crew Stakes Their Lives on the Heat Shield." April 2026. https://www.cbsnews.com/news/artemis-ii-return-earth-heat-shield-reentry/
[22] Spaceflight Now. "NASA Confident Artemis 2 Heat Shield Will Protect Crew During Re-entry." 10 April 2026. https://spaceflightnow.com/2026/04/10/nasa-confident-artemis-ii-heat-shield-will-protect-crew-during-re-entry/
[23] R&D World. "How NASA Engineered Around an Avcoat Failure for Artemis II." April 2026. https://www.rdworldonline.com/how-nasa-engineered-around-a-known-avcoat-failure-mode-to-fly-artemis-iis-crew-safely-home/
[24] New Space Economy. "The Orion Heat Shield: Description, Problems, Current Status, and What It Means for Artemis II." 3 April 2026 (citing NASA OIG January 2026 report). https://newspaceeconomy.ca/2026/04/03/the-orion-heat-shield-description-problems-current-status-and-what-it-means-for-artemis-ii/
[25] Live Science. "There's an Issue with the Artemis II Heat Shield, but NASA Isn't Worried. Here's Why." April 2026. https://www.livescience.com/space/space-exploration/theres-an-issue-with-the-artemis-ii-heat-shield-but-nasa-isnt-worried-heres-why
F-1 Engine Reconstruction
[26] SpaceRef. "NASA Engineers Resurrect and Test Mighty F-1 Engine Gas Generator." 24 May 2013 (interviews with Marshall propulsion engineers Nick Case, Kate Estes, Ryan Wall). https://spaceref.com/science-and-exploration/nasa-engineers-resurrect-and-test-mighty-f-1-engine-gas-generator-3/
[27] Space.com. "Blast from the Past: NASA Fires Historic Engine Parts for New Rocket." 22 January 2013. https://www.space.com/19379-saturn-5-f1-engines-test-firing.html
[28] The Space Review. "A Mighty Thunderous Silence: The Saturn F-1 Engine after Apollo." 3 June 2019 (history of F-1 Production Knowledge Retention program). https://www.thespacereview.com/article/3724/1
[29] Heroic Relics. "F-1 Rocket Engine Gas Generator." Reference compendium with 1961 Rocketdyne design documentation. http://heroicrelics.org/info/f-1/f-1-gas-generator.html
[30] Apollo11Space. "Why Can't We Remake the Rocketdyne F1 Engine?" 15 November 2024. https://apollo11space.com/why-cant-we-remake-the-rocketdyne-f1-engine/
Industry & Manufacturing Context
[31] Aerospace Manufacturing magazine. Latest industry news, April 2026 (B-21 Raider flight test, NASA X-59 progress, Hexagon laser-guided inspection systems). https://www.aero-mag.com/
[32] Orcalean. "Aerospace Manufacturing Strategies: How to Improve Performance in 2025 and 2026." 29 May 2025. https://www.orcalean.com/article/aerospace-manufacturing-strategies:-how-to-improve-performance-in-2025-and-2026
[33] TeepTrak. "US Aerospace Manufacturing OEE 2026 Guide." April 2026 (aerospace OEE benchmarks, documentation-burden analysis). https://teeptrak.com/en/us-aerospace-manufacturing-oee-2026-guide/
Reference
[34] Wikipedia. "AVCOAT." Composition history and Apollo-to-Orion reformulation. https://en.wikipedia.org/wiki/AVCOAT
[35] Wikipedia. "Rocketdyne F-1." Engine history including F-6049 serial-number reference and 2013 Marshall test campaign. https://en.wikipedia.org/wiki/Rocketdyne_F-1
ABOUT THE BYLINE Pseudo Publius is the byline used for civic and industrial-policy analysis directed at general aerospace and defense readership. The byline preserves the nonpartisan posture of affiliated nonprofit publications.
No comments:
Post a Comment