ArmorandClaude Opus 4.7
dd5210c203
Third-generation shuttle proposal (late 2020s, cancelled ~2032). MK4 airframe with internal tankage for full reusability; 3× RS-25EX, CERV-heritage 4 m boosters with downrange sea landing; 30 t to 650×650 km 51°; 86 m orbiter; 4 crew; ~$35M/flight target. Competed against Vulture in same government tender. Design elements later absorbed into Vulture Block 1.5/Block 2. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
218 lines
24 KiB
HTML
218 lines
24 KiB
HTML
<!doctype html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
<title>ThunderHawk Shuttle — Preview</title>
|
|
<style>
|
|
.thunderhawk-article { max-width: 1180px; margin: 0 auto; padding: 24px 32px 48px; color: #202122; background: #fff; font-family: sans-serif; font-size: 14px; line-height: 1.65; }
|
|
.thunderhawk-article h1, .thunderhawk-article h2 { font-family: "Linux Libertine", Georgia, "Times New Roman", serif; font-weight: normal; border-bottom: 1px solid #a2a9b1; }
|
|
.thunderhawk-article h1 { margin: 0 0 8px; font-size: 2.15em; line-height: 1.25; }
|
|
.thunderhawk-article h2 { clear: both; margin: 1.35em 0 0.6em; padding-bottom: 0.18em; font-size: 1.55em; }
|
|
.thunderhawk-article h3 { margin: 1.05em 0 0.35em; font-size: 1.18em; font-weight: bold; }
|
|
.thunderhawk-article p { margin: 0.45em 0 0.85em; }
|
|
.thunderhawk-article a { color: #0645ad; text-decoration: none; }
|
|
.thunderhawk-article a:hover { text-decoration: underline; }
|
|
.thunderhawk-article ul, .thunderhawk-article ol { margin: 0.35em 0 0.9em 1.65em; padding: 0; }
|
|
.thunderhawk-article li { margin-bottom: 0.18em; }
|
|
.thunderhawk-article .infobox { float: right; clear: right; width: 330px; margin: 0 0 18px 24px; border: 1px solid #a2a9b1; border-collapse: collapse; background: #f8f9fa; font-size: 88%; line-height: 1.45; }
|
|
.thunderhawk-article .infobox caption { padding: 8px; background: #eaecf0; border: 1px solid #a2a9b1; border-bottom: 0; font-weight: bold; font-size: 1.12em; }
|
|
.thunderhawk-article .infobox caption span { display: block; font-size: 0.92em; font-weight: normal; }
|
|
.thunderhawk-article .infobox td { border: 1px solid #a2a9b1; padding: 6px 8px; vertical-align: top; }
|
|
.thunderhawk-article .infobox-image { text-align: center; }
|
|
.thunderhawk-article .image-placeholder { min-height: 150px; border: 1px dashed #72777d; background: #eaecf0; color: #54595d; display: flex; align-items: center; justify-content: center; padding: 10px; text-align: center; box-sizing: border-box; }
|
|
.thunderhawk-article .infobox .image-placeholder { min-height: 185px; }
|
|
.thunderhawk-article img { max-width: 100%; height: auto; cursor: zoom-in; }
|
|
.thunderhawk-article .infobox-image img { display: block; margin: 0 auto 4px; }
|
|
.thunderhawk-article .thumb { width: 260px; border: 1px solid #c8ccd1; background: #f8f9fa; padding: 3px; font-size: 88%; line-height: 1.4; box-sizing: border-box; }
|
|
.thunderhawk-article .thumb img { display: block; width: 100%; }
|
|
.thunderhawk-article .tright { float: right; clear: right; margin: 0.35em 0 1em 1.4em; }
|
|
.thunderhawk-article .thumbcaption { padding: 4px 3px 2px; text-align: left; color: #202122; }
|
|
.thunderhawk-article .toc { display: inline-block; min-width: 260px; margin: 0.45em 0 1.2em; padding: 8px 12px; border: 1px solid #a2a9b1; background: #f8f9fa; font-size: 92%; }
|
|
.thunderhawk-article .toc-title { text-align: center; font-weight: bold; margin-bottom: 4px; }
|
|
.thunderhawk-article .toc ol { margin: 0 0 0 1.5em; }
|
|
.thunderhawk-article > table:not(.infobox) { width: 100%; margin: 1em 0; border-collapse: collapse; font-size: 92%; background: #fff; }
|
|
.thunderhawk-article > table:not(.infobox) th, .thunderhawk-article > table:not(.infobox) td { border: 1px solid #a2a9b1; padding: 6px 8px; text-align: left; vertical-align: top; }
|
|
.thunderhawk-article > table:not(.infobox) th { background: #eaecf0; font-weight: bold; }
|
|
.thunderhawk-article > table:not(.infobox) tr:nth-child(even) td { background: #f8f9fa; }
|
|
@media (max-width: 820px) { .thunderhawk-article { padding: 18px 16px 36px; } .thunderhawk-article .infobox, .thunderhawk-article .thumb { float: none; width: 100%; margin: 0.75em 0 1em; } .thunderhawk-article .toc { display: block; } }
|
|
</style>
|
|
</head>
|
|
<body>
|
|
<article class="mw-parser-output thunderhawk-article">
|
|
<h1 id="thunderhawk-shuttle">ThunderHawk Shuttle</h1>
|
|
<table class="infobox">
|
|
<caption>ThunderHawk Shuttle<span>雷鹰航天飞机</span></caption>
|
|
<tbody>
|
|
<tr><td class="infobox-image"><div class="image-placeholder">[Image] ThunderHawk orbiter side view — internal-tank MK4 airframe, large delta wing, wingtip vertical tails, forward canards</div><div class="thumbcaption">ThunderHawk orbiter concept render — MK4 airframe with wing layout similar to Vulture, stretched to 86 m to accommodate internal propellant tanks, eliminating the need for an expendable external tank.</div></td></tr>
|
|
<tr><td><b>Type</b>: Fully reusable shuttle system (proposal)</td></tr>
|
|
<tr><td><b>Status</b>: Proposal phase, cancelled</td></tr>
|
|
<tr><td><b>Proposed</b>: Late 2020s</td></tr>
|
|
<tr><td><b>Cancelled</b>: c. 2032</td></tr>
|
|
<tr><td><b>Generation</b>: Third-generation shuttle (competing proposal)</td></tr>
|
|
<tr><td><b>Competitor</b>: <a href="/home/Space_Shuttles/Vulture_Shuttle">Vulture Shuttle</a></td></tr>
|
|
<tr><td><b>Airframe</b>: MK4</td></tr>
|
|
<tr><td><b>Orbiter length</b>: 86 m</td></tr>
|
|
<tr><td><b>Payload</b>: 30 t to 650 km × 650 km, 51° inclination</td></tr>
|
|
<tr><td><b>Main engines</b>: 3 × RS-25EX</td></tr>
|
|
<tr><td><b>Boosters</b>: 2 × 4 m liquid boosters (CERV heritage), 9 × TH-12 each</td></tr>
|
|
<tr><td><b>Booster recovery</b>: Downrange landing, sea platform ~400 km from launch site</td></tr>
|
|
<tr><td><b>Atmospheric engines</b>: 2 × turbojet</td></tr>
|
|
<tr><td><b>Maximum crew</b>: 4</td></tr>
|
|
<tr><td><b>Launch sites</b>: Wenchang / Cape Canaveral</td></tr>
|
|
<tr><td><b>Projected cost per flight</b>: ~$35 million</td></tr>
|
|
</tbody></table>
|
|
<p>The <b>ThunderHawk Shuttle</b> (Chinese: <b>雷鹰航天飞机</b>) was a third-generation space shuttle proposal developed in the late 2020s, competing against the <a href="/home/Space_Shuttles/Vulture_Shuttle">Vulture Shuttle</a> within the same government tender framework. Its defining design philosophy was <b>full reusability</b> — integrating liquid oxygen/liquid hydrogen tanks directly into the orbiter airframe, thereby eliminating the expendable external tank entirely. To accommodate internal tankage within the MK4 cross-section while preserving a 30 t payload floor, the orbiter was stretched to 86 m. The trade-off was a per-flight payload far smaller than the competing Vulture proposal, but with a target per-flight cost substantially lower than any external-tank-dependent shuttle system.</p>
|
|
<p>ThunderHawk never progressed beyond the proposal phase. The program was formally terminated around 2032. However, several of its design concepts — the fully-reusable internal-tank philosophy, airframe structural design, turbojet engine system, and flight control architecture — were absorbed into the Vulture family's subsequent evolution.</p>
|
|
<nav class="toc" aria-label="Contents">
|
|
<div class="toc-title">Contents</div>
|
|
<ol>
|
|
<li><a href="#design-philosophy">Design Philosophy</a></li>
|
|
<li><a href="#system-components">System Components</a></li>
|
|
<li><a href="#mission-profile">Mission Profile</a></li>
|
|
<li><a href="#competition-with-vulture">Competition with Vulture</a></li>
|
|
<li><a href="#cancellation-and-legacy">Cancellation and Legacy</a></li>
|
|
<li><a href="#specifications">Specifications</a></li>
|
|
<li><a href="#images">Images</a></li>
|
|
<li><a href="#see-also">See Also</a></li>
|
|
</ol>
|
|
</nav>
|
|
<h2 id="design-philosophy">Design Philosophy</h2>
|
|
<p>ThunderHawk was predicated on a structural cost problem exposed by years of CERV Shuttle operations: the expendable external tank. Every CERV flight consumed a newly manufactured large LOX/LH2 tank, whose fabrication cost represented the single largest line item in per-flight expenses. No matter how many times the boosters were recovered or the orbiter refurbished, the tank expense was unavoidable. ThunderHawk's design team concluded that the next-generation shuttle's economic breakthrough could not come from incrementally improving reuse rates alone — it required architecturally eliminating the expendable component.</p>
|
|
<p>This judgment drove architectural choices that fundamentally diverged from CERV — and from the competing Vulture proposal:</p>
|
|
<ul>
|
|
<li><b>Internal tankage</b>: Propellant tanks were integrated into the orbiter airframe, eliminating any expendable component from the launch stack. Within the constraints of the MK4 cross-section, the fuselage was stretched to 86 m — substantially longer than the CERV orbiter and the competing Vulture proposal — with most of the additional length dedicated to internal tank volume.</li>
|
|
<li><b>Three main engines</b>: Only 3 RS-25EX engines were fitted. The reduced engine count lowered procurement and maintenance costs, at the expense of narrower engine-out margins.</li>
|
|
<li><b>CERV-heritage boosters</b>: The proposal adopted the proven CERV 4 m liquid booster design (9 × TH-12 each) rather than developing an all-new booster as the Vulture proposal did. This reduced development risk and leveraged existing ground infrastructure and sea-recovery experience from the CERV fleet. However, ThunderHawk could not simply carry over CERV's RTLS return-to-launch-site recovery — the increased orbiter mass from internal tankage demanded greater velocity contribution from the boosters, forcing a switch to downrange landing. After separation, each booster continued ballistically approximately 400 km to a sea platform for propulsive vertical landing, trading recovery convenience for ascent performance.</li>
|
|
<li><b>Dual-launch-site compatibility</b>: The proposal supported operations from both Wenchang and Cape Canaveral, with sea landing platforms deployable approximately 400 km downrange within each launch corridor.</li>
|
|
<li><b>Narrow mission focus</b>: Payload was sized at 30 t to a 650 km polar orbit (51°), rather than pursuing the 100 t heavy-lift class of the Vulture proposal. ThunderHawk targeted medium-mass, high-cadence launches. The 4-person crew configuration reflected a professional flight crew role rather than large-scale personnel transport.</li>
|
|
</ul>
|
|
<h2 id="system-components">System Components</h2>
|
|
<figure class="thumb tright"><div class="image-placeholder">[Image] ThunderHawk orbiter cutaway — forward crew cabin and payload bay, midsection internal tankage, aft engine compartment</div><figcaption class="thumbcaption">Internal layout: forward crew cabin and payload bay, midsection LOX/LH2 tanks, aft section with 3 × RS-25EX and 2 × turbojet engines.</figcaption></figure>
|
|
<h3>Orbiter</h3>
|
|
<p>The ThunderHawk orbiter shared the MK4 cross-section and wing layout with Vulture — large delta wing, wingtip vertical tails, and forward canards. Unlike Vulture's MK4 airframe designed around external tank propellant feed, the ThunderHawk fuselage itself was the complete propellant storage unit. Internal layout: forward crew cabin (4) and payload bay (approx. 5.4 m × 7.75 m × 20 m), midsection LOX/LH2 tanks, aft section housing 3 × RS-25EX main engines, OMS/RCS pods, and 2 × turbojet engines.</p>
|
|
<p>The payload bay shared its width and height with Vulture (common MK4 cross-section cargo envelope), but was roughly one-third shorter. It remained sufficient for most standard station modules, satellite constellation payloads, and small-to-medium orbital tugs. The two turbojet engines provided terminal approach energy management, cross-range maneuvering, and go-around capability during the landing phase.</p>
|
|
<p>Three RS-25EX engines — the same model used on Vulture — were mounted in a single row at the aft end, each with thrust vector control. The reduced engine count was matched to the internal tank's propellant capacity.</p>
|
|
<h3>Liquid Boosters</h3>
|
|
<figure class="thumb tright"><div class="image-placeholder">[Image] ThunderHawk launch stack — orbiter + two 4 m liquid boosters, with downrange sea platform recovery illustration</div><figcaption class="thumbcaption">Launch configuration: two CERV-heritage 4 m boosters flanking the orbiter. After separation, boosters perform a downrange landing on a sea platform.</figcaption></figure>
|
|
<p>ThunderHawk employed two 4 m diameter liquid boosters inherited directly from the mature CERV shuttle design. Each booster carried 9 TH-12 LOX/kerosene engines in the standard CERV configuration, providing the majority of liftoff thrust.</p>
|
|
<p>Unlike Vulture boosters which performed RTLS return-to-launch-site landings, ThunderHawk boosters used a downrange landing profile: after separation, each booster continued ballistically approximately 400 km downrange, performed a propulsive vertical landing on a sea platform, and was subsequently towed back to port for refurbishment. This choice traded land-recovery convenience for additional ascent performance, allowing the 3 × RS-25EX + 4 m booster combination to deliver 30 t to polar orbit. Recovery hardware — grid fins, hot-gas RCS, and landing legs — was compatible with CERV-era equipment.</p>
|
|
<h2 id="mission-profile">Mission Profile</h2>
|
|
<figure class="thumb tright"><div class="image-placeholder">[Image] ThunderHawk full mission profile — liftoff → booster sep + downrange recovery → MECO → OMS insertion → on-orbit ops → deorbit → reentry → horizontal landing</div><figcaption class="thumbcaption">End-to-end mission profile: from launch at Wenchang or Cape Canaveral through to orbiter horizontal landing.</figcaption></figure>
|
|
<h3>Ascent</h3>
|
|
<p>At liftoff, both liquid boosters and all three RS-25EX engines fired together. After booster burnout and separation, the boosters performed downrange sea-platform recovery while the orbiter continued under internal tank propellant feed. Following main engine cutoff, the orbiter used OMS burns to complete orbital insertion and circularization.</p>
|
|
<h3>Engine-Out Capability</h3>
|
|
<p>With only three RS-25EX engines, engine-out margins were significantly narrower than Vulture's five-engine configuration:</p>
|
|
<ul>
|
|
<li><b>Before booster separation</b>: Loss of any single RS-25EX triggered an immediate <b>RTLS Abort</b>. At this stage the vehicle was still in dense atmosphere with insufficient remaining thrust to continue toward orbit.</li>
|
|
<li><b>After booster separation</b>: The response to losing one RS-25EX depended on the specific timing and remaining propellant margin, spanning the range from <b>Trans-Ocean Abort</b> to <b>Abort to Orbit</b>. An early post-separation failure was more likely to trigger a trans-ocean abort; a late-ascent failure could still achieve a degraded but usable orbit.</li>
|
|
</ul>
|
|
<p>Detailed abort boundaries (specific TWR thresholds and time windows) were never fully defined, as the proposal did not proceed to detailed design.</p>
|
|
<h3>Reentry and Landing</h3>
|
|
<p>At end of mission, the orbiter closed its payload bay doors and performed a deorbit burn using the OMS. The reentry profile was similar to Vulture — high angle of attack, bank reversals for thermal and cross-range management. During the terminal phase, the two turbojet engines provided energy management and go-around capability. The orbiter landed horizontally on a dedicated runway at Wenchang or Cape Canaveral.</p>
|
|
<h2 id="competition-with-vulture">Competition with Vulture</h2>
|
|
<p>During the late 2020s, ThunderHawk and Vulture competed within the same government tender for the next-generation heavy shuttle contract. The two proposals represented fundamentally different answers to the question of what a shuttle should be:</p>
|
|
<table>
|
|
<thead><tr><th></th><th>ThunderHawk</th><th>Vulture Block 1 (competing proposal)</th></tr></thead>
|
|
<tbody>
|
|
<tr><td>Reuse philosophy</td><td>Fully reusable; no expendable elements</td><td>Partially reusable; external tank is expendable</td></tr>
|
|
<tr><td>Payload strategy</td><td>30 t medium-lift, high cadence</td><td>100 t heavy-lift, maximize per-launch mass</td></tr>
|
|
<tr><td>Cost approach</td><td>Eliminate tank manufacturing cost, reduce marginal flight expense</td><td>Accept tank as consumable, amortize over large payload mass</td></tr>
|
|
<tr><td>Payload bay</td><td>5.4 × 7.75 × 20 m</td><td>5.4 × 7.75 × 29.5 m</td></tr>
|
|
<tr><td>Engine count</td><td>3 × RS-25EX</td><td>5 × RS-25EX</td></tr>
|
|
<tr><td>Boosters</td><td>CERV-heritage 4 m, downrange sea recovery</td><td>All-new 5 m, RTLS land recovery</td></tr>
|
|
<tr><td>Crew</td><td>4</td><td>19</td></tr>
|
|
<tr><td>Launch sites</td><td>Wenchang / Cape Canaveral</td><td>Wenchang</td></tr>
|
|
<tr><td>Orbiter length</td><td>86 m</td><td>61.5 m</td></tr>
|
|
<tr><td>Development risk</td><td>Lower (CERV booster and RS-25EX inheritance)</td><td>Moderate-high (all-new booster + 10 m ET)</td></tr>
|
|
</tbody></table>
|
|
<p>ThunderHawk's core advantage was operating economics — full reusability meant no "big expendable item" in the per-flight marginal cost. Its weakness was that the 30 t ceiling and shorter payload bay were inadequate for the large station and mothership construction missions already visible in the tender requirements. Those missions demanded single-launch delivery of oversized, massive trusses and propulsion modules, favoring a heavy-lift approach.</p>
|
|
<h2 id="cancellation-and-legacy">Cancellation and Legacy</h2>
|
|
<p>ThunderHawk was formally terminated around 2032 without entering the project establishment phase. Three factors drove the decision:</p>
|
|
<ol>
|
|
<li><b>Payload insufficient for emerging demand</b>: Within the MK4 cross-section constraint, merely preserving 30 t payload had already forced the fuselage to 86 m and pushed the boosters from RTLS to downrange sea recovery. There was essentially no engineering headroom left to grow payload further. The space station expansion and mothership construction requirements already specified in the tender demanded single-launch heavy-lift capability in the 100 t class — a scale ThunderHawk's architecture could not reach. The shorter payload bay (20 m vs. the competing proposal's 29.5 m) further restricted large-component transport.</li>
|
|
<li><b>Cost advantage unproven at heavy-lift scale</b>: ThunderHawk eliminated the external tank manufacturing cost — CERV's single largest per-flight consumable — and targeted approximately $35M per flight. However, its 30 t payload meant that matching the total delivered mass of a heavy-lift competitor would require multiple times as many launches. Launch operations overhead and the additional time and logistics of downrange booster recovery introduced new cost burdens, and the multiplier effect of lower per-flight payload risked eroding ThunderHawk's single-flight price advantage in real construction campaigns.</li>
|
|
<li><b>Limited upgrade path to nuclear propulsion</b>: By the 2030s, nuclear propulsion was already visible as the next evolutionary direction for the shuttle lineage. ThunderHawk's architecture was deeply optimized around hydrolox main engines — internal tank dimensions, propellant management, thermal environment, and center-of-gravity envelope were all tightly coupled to the RS-25EX configuration. Retrofitting a nuclear aerospike or nuclear thermal system would have required effectively redesigning the entire fuselage. By contrast, an external-tank architecture naturally decoupled propellant storage from the orbiter, leaving ample engineering room for future nuclear conversion paths.</li>
|
|
</ol>
|
|
<p>Despite its cancellation, ThunderHawk's core design work did not disappear. Its internal-tank fully-reusable philosophy, airframe structural solutions, turbojet engine system design, and flight control architecture were absorbed into the Vulture family's subsequent development. Most notably, the internal-tank vision — a shuttle that discards nothing — lived on in a different technical form through the nuclear aerospike SSTO configurations of Vulture Block 1.5 and Block 2.</p>
|
|
<h2 id="specifications">Specifications</h2>
|
|
<p>Values below reflect proposal-phase design targets. Items marked [TBD] will be filled in as data becomes available.</p>
|
|
<h3>General Configuration and Performance</h3>
|
|
<table>
|
|
<thead><tr><th>Parameter</th><th>Value</th></tr></thead>
|
|
<tbody>
|
|
<tr><td>Type</td><td>Fully reusable shuttle system (proposal)</td></tr>
|
|
<tr><td>Status</td><td>Proposal phase, cancelled c. 2032</td></tr>
|
|
<tr><td>Airframe</td><td>MK4</td></tr>
|
|
<tr><td>Orbiter length</td><td>86 m</td></tr>
|
|
<tr><td>Orbiter wingspan</td><td>[TBD]</td></tr>
|
|
<tr><td>Orbiter dry mass</td><td>[TBD]</td></tr>
|
|
<tr><td>Internal tank propellant capacity</td><td>[TBD]</td></tr>
|
|
<tr><td>Liftoff thrust</td><td>[TBD]</td></tr>
|
|
<tr><td>Launch sites</td><td>Wenchang / Cape Canaveral</td></tr>
|
|
<tr><td>Typical target orbit</td><td>650 km × 650 km, 51° inclination</td></tr>
|
|
<tr><td>Payload to typical orbit</td><td>30 t</td></tr>
|
|
</tbody></table>
|
|
<h3>Orbiter</h3>
|
|
<table>
|
|
<thead><tr><th>Parameter</th><th>Value</th></tr></thead>
|
|
<tbody>
|
|
<tr><td>Airframe</td><td>MK4</td></tr>
|
|
<tr><td>Length</td><td>86 m</td></tr>
|
|
<tr><td>Wingspan</td><td>[TBD]</td></tr>
|
|
<tr><td>Dry mass</td><td>[TBD]</td></tr>
|
|
<tr><td>Main engines</td><td>3 × RS-25EX; dry mass 2.88 t each; chamber pressure 26 MPa; vacuum thrust 2,812 kN; vacuum Isp 454 s; sea-level thrust 2,353.7 kN; sea-level Isp 380 s</td></tr>
|
|
<tr><td>Main engine max burn time</td><td>[TBD]</td></tr>
|
|
<tr><td>OMS engines</td><td>[TBD]</td></tr>
|
|
<tr><td>OMS propellant</td><td>[TBD]</td></tr>
|
|
<tr><td>OMS propellant load</td><td>[TBD]</td></tr>
|
|
<tr><td>RCS propellant</td><td>[TBD]</td></tr>
|
|
<tr><td>Atmospheric engines</td><td>2 × turbojet</td></tr>
|
|
<tr><td>Jet fuel</td><td>[TBD]</td></tr>
|
|
<tr><td>Jet engine thrust</td><td>[TBD]</td></tr>
|
|
<tr><td>Payload bay</td><td>Approx. 5.4 m × 7.75 m × 20 m</td></tr>
|
|
<tr><td>Maximum crew</td><td>4</td></tr>
|
|
<tr><td>Life support</td><td>[TBD]</td></tr>
|
|
<tr><td>Landing gear</td><td>Tricycle retractable</td></tr>
|
|
<tr><td>Crew escape system</td><td>[TBD]</td></tr>
|
|
</tbody></table>
|
|
<h3>Liquid Boosters (each)</h3>
|
|
<table>
|
|
<thead><tr><th>Parameter</th><th>Value</th></tr></thead>
|
|
<tbody>
|
|
<tr><td>Diameter</td><td>4 m</td></tr>
|
|
<tr><td>Engines</td><td>9 × TH-12 LOX/kerosene</td></tr>
|
|
<tr><td>Propellant</td><td>LOX/kerosene</td></tr>
|
|
<tr><td>Dry mass</td><td>[TBD]</td></tr>
|
|
<tr><td>Propellant capacity</td><td>[TBD]</td></tr>
|
|
<tr><td>Burn time</td><td>[TBD]</td></tr>
|
|
<tr><td>Recovery method</td><td>Downrange landing, sea platform ~400 km from launch site</td></tr>
|
|
<tr><td>Recovery hardware</td><td>Grid fins, hot-gas RCS, landing legs</td></tr>
|
|
</tbody></table>
|
|
<h3>Cost</h3>
|
|
<table>
|
|
<thead><tr><th>Parameter</th><th>Value</th></tr></thead>
|
|
<tbody>
|
|
<tr><td>Projected per-flight cost</td><td>~$35 million</td></tr>
|
|
</tbody></table>
|
|
<h2 id="images">Images</h2>
|
|
<table>
|
|
<thead><tr><th>Image</th><th>Content</th><th>Placement</th></tr></thead>
|
|
<tbody>
|
|
<tr><td>Orbiter side view</td><td>ThunderHawk orbiter concept render — MK4 airframe, 86 m overall length, large delta wing, wingtip vertical tails, forward canards. Shares the Vulture wing layout aesthetic but with a noticeably longer fuselage.</td><td>Infobox</td></tr>
|
|
<tr><td>Orbiter cutaway</td><td>Internal layout: forward crew cabin (4) and payload bay (5.4×7.75×20 m), midsection LOX/LH2 tanks, aft 3×RS-25EX + OMS/RCS + 2×turbojet.</td><td>System Components / Orbiter</td></tr>
|
|
<tr><td>Launch stack + booster recovery</td><td>Full launch configuration: orbiter + two 4 m liquid boosters. Booster downrange sea platform landing illustration after separation.</td><td>System Components / Liquid Boosters</td></tr>
|
|
<tr><td>Full mission profile</td><td>End-to-end mission flow: liftoff → booster sep + downrange recovery → MECO → OMS insertion → on-orbit ops → deorbit → reentry → horizontal landing.</td><td>Mission Profile</td></tr>
|
|
</tbody></table>
|
|
<h2 id="see-also">See Also</h2>
|
|
<ul>
|
|
<li><a href="/home/Space_Shuttles/Vulture_Shuttle">Vulture Shuttle</a></li>
|
|
<li><a href="/home/Space_Shuttles/CERV_Shuttle">CERV Shuttle</a></li>
|
|
<li><a href="/home/Space_Shuttles/Echo_Shuttle">Echo Shuttle</a></li>
|
|
<li><a href="/home/Space_Shuttles/Enterprise_Shuttle">Enterprise Shuttle</a></li>
|
|
<li>RS-25EX</li>
|
|
</ul>
|
|
</article>
|
|
</body>
|
|
</html>
|