docs: add ThunderHawk Shuttle wiki page (zh + en)
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>
This commit is contained in:
Claude Opus 4.7
@@ -0,0 +1,217 @@
|
||||
<!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>
|
||||
@@ -0,0 +1,217 @@
|
||||
<!doctype html>
|
||||
<html lang="zh-CN">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<title>雷鹰航天飞机（ThunderHawk Shuttle） — 预览</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>雷鹰航天飞机<span>ThunderHawk Shuttle</span></caption>
|
||||
<tbody>
|
||||
<tr><td class="infobox-image"><div class="image-placeholder">[图] 雷鹰航天飞机轨道器侧视图 — 内置储箱 MK4 机身，大型三角翼，翼尖双垂尾，前部鸭翼</div><div class="thumbcaption">ThunderHawk 轨道器方案概念渲染 — 采用 MK4 机身与 Vulture 类似的翼型布局，但机身拉长至 86 米以容纳内置推进剂储箱，无需外挂燃料箱。</div></td></tr>
|
||||
<tr><td><b>类型</b>：完全可重复使用航天飞机系统（方案）</td></tr>
|
||||
<tr><td><b>状态</b>：方案阶段，未立项</td></tr>
|
||||
<tr><td><b>提出时间</b>：2020 年代下半叶</td></tr>
|
||||
<tr><td><b>终止时间</b>：约 2032 年</td></tr>
|
||||
<tr><td><b>世代</b>：第三代航天飞机（竞争方案）</td></tr>
|
||||
<tr><td><b>竞争对手</b>：<a href="/home/Space_Shuttles/Vulture_Shuttle">秃鹫航天飞机</a></td></tr>
|
||||
<tr><td><b>机身构型</b>：MK4</td></tr>
|
||||
<tr><td><b>轨道器长度</b>：86 米</td></tr>
|
||||
<tr><td><b>典型载荷能力</b>：30 吨至 650 km × 650 km、51° 倾角轨道</td></tr>
|
||||
<tr><td><b>轨道器主发动机</b>：3 台 RS-25EX</td></tr>
|
||||
<tr><td><b>助推器</b>：2 枚 4 米液体燃料助推器（CERV 遗产），每枚 9 台 TH-12</td></tr>
|
||||
<tr><td><b>助推器回收方式</b>：Downrange landing，距发射场约 400 km 海上着陆平台</td></tr>
|
||||
<tr><td><b>大气层内发动机</b>：2 台涡喷发动机</td></tr>
|
||||
<tr><td><b>最大乘员</b>：4 人</td></tr>
|
||||
<tr><td><b>主要发射场</b>：文昌 / 卡纳维拉尔角</td></tr>
|
||||
<tr><td><b>预计单次飞行成本</b>：约 3500 万美元</td></tr>
|
||||
</tbody></table>
|
||||
<p><b>雷鹰航天飞机</b>（英语：<b>ThunderHawk Shuttle</b>）是架空时间线中 2020 年代下半叶提出的第三代航天飞机方案，与同期推进的<a href="/home/Space_Shuttles/Vulture_Shuttle">秃鹫航天飞机</a>（Vulture Shuttle）在同一政府招标框架内展开竞争。ThunderHawk 的核心设计理念是实现<b>完全可重复使用</b>——将液氧/液氢储箱集成至轨道器机身内部，从而取消一次性外挂燃料箱。在 MK4 机身约束下，为容纳内置储箱并保底 30 吨有效载荷，机身被拉长至 86 米。作为代价，其单次运力远不及同期竞标的 Vulture 方案，但目标单次飞行成本大幅低于依赖外挂箱的航天飞机体系。</p>
|
||||
<p>ThunderHawk 从未进入立项阶段。约 2032 年，方案正式终止。但其多项设计思路——内置储箱的完全复用理念、机身结构设计、喷气发动机系统及飞行控制系统——被后续吸收至 Vulture 的衍生发展路线中。</p>
|
||||
<nav class="toc" aria-label="目录">
|
||||
<div class="toc-title">目录</div>
|
||||
<ol>
|
||||
<li><a href="#设计理念">设计理念</a></li>
|
||||
<li><a href="#系统组成">系统组成</a></li>
|
||||
<li><a href="#任务剖面">任务剖面</a></li>
|
||||
<li><a href="#与秃鹫航天飞机的竞争">与秃鹫航天飞机的竞争</a></li>
|
||||
<li><a href="#方案终止与遗产">方案终止与遗产</a></li>
|
||||
<li><a href="#技术参数">技术参数</a></li>
|
||||
<li><a href="#图片">图片</a></li>
|
||||
<li><a href="#参见">参见</a></li>
|
||||
</ol>
|
||||
</nav>
|
||||
<h2 id="设计理念">设计理念</h2>
|
||||
<p>ThunderHawk 的提出基于 CERV 航天飞机多年运营暴露出的一个结构性成本问题：外挂燃料箱。CERV 的每次飞行都必须消耗一枚全新制造的大型液氧/液氢储箱，其制造成本在单次飞行总成本中占据最大单一项目份额。无论助推器回收多少次、轨道器复用多少轮，外挂箱这笔开支都无法绕开。ThunderHawk 的设计团队因此判断，下一代航天飞机的经济性突破不能只靠提高复用次数——必须从架构层面消除一次性部件。</p>
|
||||
<p>这一判断驱使 ThunderHawk 做出了与 CERV——以及同期竞标的 Vulture——根本不同的架构选择：</p>
|
||||
<ul>
|
||||
<li><b>内置储箱</b>：将推进剂储箱整合进轨道器机身，发射阶段不再依赖任何一次性部件。在 MK4 横截面的固有空间约束下，为容纳足量推进剂并维持 30 吨有效载荷，机身被拉长至 86 米——大幅超出 CERV 和同期 Vulture 方案的轨道器长度。大部分额外长度即为内置储箱段。</li>
|
||||
<li><b>三台主发动机</b>：仅安装 3 台 RS-25EX。较少的发动机数量降低了采购和维护成本，但单发失效容限相应收窄。</li>
|
||||
<li><b>CERV 遗产助推器</b>：直接沿用已成熟运营的 CERV 4 米液体助推器（每枚 9 台 TH-12），而非像 Vulture 方案那样全新开发 5 米助推器。这一选择降低了研制风险，同时利用了 CERV 机队积累的地面设施和海上回收经验。但在回收模式上，ThunderHawk 无法沿用 CERV 助推器的 RTLS 返场着陆——内置储箱带来的轨道器质量增加要求助推器提供更大速度增量，迫使回收方案改为 downrange landing：分离后沿弹道继续飞行约 400 公里，在海上着陆平台完成反推垂直着陆。这一选择牺牲了陆上回收的便利性，换取了上升段性能。</li>
|
||||
<li><b>双发射场兼容</b>：方案同时考虑从文昌和卡纳维拉尔角发射，海上着陆平台可部署于各自航区内距发射场约 400 公里处。</li>
|
||||
<li><b>窄任务定位</b>：载荷能力定位于 30 吨至 650 km 极轨（51°），而非像 Vulture 方案那样追求百吨级高轨重载。ThunderHawk 的设计不追求包揽所有任务类型，而是专注于中等质量载荷的高频次发射。4 人乘组配置也表明其载人任务面向专业机组，不承担大规模人员运输。</li>
|
||||
</ul>
|
||||
<h2 id="系统组成">系统组成</h2>
|
||||
<figure class="thumb tright"><div class="image-placeholder">[图] ThunderHawk 轨道器三维剖面示意图 — 前部乘员舱和载荷舱、中部内置储箱段、尾部发动机舱</div><figcaption class="thumbcaption">轨道器内部布局：前段为乘员舱与载荷舱，中后段为内置液氧/液氢储箱，尾部安装三台 RS-25EX 与两台涡喷发动机。</figcaption></figure>
|
||||
<h3>轨道器</h3>
|
||||
<p>ThunderHawk 轨道器采用与 Vulture 相同的 MK4 横截面构型，翼型布局类似——大型三角翼、翼尖双垂尾、前部鸭翼。与 Vulture 的 MK4 机身围绕外挂燃料箱供油设计不同，ThunderHawk 的机身本身就是完整的推进剂储存单元。内部布局为：前段乘员舱（4 人）和载荷舱（约 5.4 m × 7.75 m × 20 m），中后段为内置液氧/液氢储箱，尾部为三台 RS-25EX 主发动机、OMS/RCS 舱段和两台涡喷发动机。</p>
|
||||
<p>载荷舱宽度和高度与 Vulture 一致（共享 MK4 横截面的货舱轮廓），但长度缩短约三分之一，足以容纳大多数标准空间站舱段、卫星组网任务载荷和中小型轨道拖船。两台涡喷发动机用于大气层内返航末段的进近、横向机动和复飞。</p>
|
||||
<p>尾部安装 3 台 RS-25EX 主发动机——与 Vulture 同款，但数量减少以匹配内置储箱的推进剂容量。三台发动机呈一字排列，均具备推力矢量控制能力。</p>
|
||||
<h3>液体助推器</h3>
|
||||
<figure class="thumb tright"><div class="image-placeholder">[图] ThunderHawk 起飞构型 — 轨道器 + 两枚 4 米液体助推器，海上着陆平台回收示意</div><figcaption class="thumbcaption">起飞构型：两枚 CERV 遗产 4 米助推器对称布置，分离后执行 downrange 海上平台着陆。</figcaption></figure>
|
||||
<p>ThunderHawk 使用两枚 4 米直径液体燃料助推器，直接继承自 CERV 航天飞机的成熟设计。每枚助推器配备 9 台 TH-12 液氧煤油发动机（CERV 标准配置），在发射初段提供主要起飞推力。</p>
|
||||
<p>与 Vulture 助推器执行 RTLS 返场着陆不同，ThunderHawk 助推器采用 downrange landing 模式：分离后沿弹道继续飞行约 400 公里，在海上着陆平台完成反推垂直着陆，随后由回收船拖回港口整备。这一模式牺牲了陆上回收的便利性，但释放了更多上升段性能，使 3 台 RS-25EX + 4 米助推器的组合仍能将 30 吨载荷送入极轨。助推器配备栅格翼、热燃气姿控系统和着陆腿，回收硬件与 CERV 时代兼容。</p>
|
||||
<h2 id="任务剖面">任务剖面</h2>
|
||||
<figure class="thumb tright"><div class="image-placeholder">[图] ThunderHawk 全任务剖面示意图 — 起飞 → 助推器分离+downrange回收 → 主发动机关机 → OMS入轨 → 在轨操作 → 离轨 → 再入 → 水平着陆</div><figcaption class="thumbcaption">全任务剖面：从文昌或卡纳维拉尔角起飞，至轨道器水平着陆的全流程示意。</figcaption></figure>
|
||||
<h3>发射与上升</h3>
|
||||
<p>起飞时，两枚液体助推器和三台 RS-25EX 同时提供推力。助推器燃烧结束后分离，执行 downrange 海上回收；轨道器依靠内置储箱的推进剂继续上升，三台 RS-25EX 工作至主发动机关机。随后轨道器使用 OMS 完成入轨和圆化。</p>
|
||||
<h3>Engine-Out 容限</h3>
|
||||
<p>三台 RS-25EX 配置下的 Engine-Out 容限显著窄于 Vulture 的五台配置：</p>
|
||||
<ul>
|
||||
<li><b>助推器分离前</b>：失去任何一台 RS-25EX 将立即触发 <b>RTLS Abort</b>。此时飞行器仍处于大气稠密区且推力损失过大，无法继续向轨道推进。</li>
|
||||
<li><b>助推器分离后</b>：失去一台 RS-25EX 的处置取决于失效发生的具体时间和剩余推进剂余量，可能触发从 <b>Trans-Ocean Abort</b> 到 <b>Abort to Orbit</b> 之间的各级中止模式。在任务早期失效更可能触发越洋中止；在上升末段失效则可能仍能进入一个降级但可用的轨道。</li>
|
||||
</ul>
|
||||
<p>完整的容限边界（具体 TWR 节点与时间窗口）因方案未能进入详细设计阶段而未完全确定。</p>
|
||||
<h3>再入与着陆</h3>
|
||||
<p>任务结束后，轨道器关闭载荷舱门，使用 OMS 执行离轨点火。再入剖面与 Vulture 类似——高攻角进入大气层，姿态控制和滚转反转管理热流和横向偏差。下降后段转入进近航线，两台涡喷发动机提供末端能量管理和复飞能力。常规着陆在文昌或卡纳维拉尔角配套跑道完成。</p>
|
||||
<h2 id="与秃鹫航天飞机的竞争">与秃鹫航天飞机的竞争</h2>
|
||||
<p>2020 年代下半叶，ThunderHawk 与 Vulture 在同一个政府招标框架内竞争下一代重型航天飞机合同。两者的核心分歧在于对"航天飞机应该是什么"的根本判断：</p>
|
||||
<table>
|
||||
<thead><tr><th></th><th>ThunderHawk</th><th>Vulture Block 1（同期竞标方案）</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>复用理念</td><td>完全可复用，无一次性部件</td><td>部分复用，外挂燃料箱为消耗品</td></tr>
|
||||
<tr><td>载荷策略</td><td>30 吨中等载荷，高频次发射</td><td>100 吨重载，单次投送最大化</td></tr>
|
||||
<tr><td>成本路线</td><td>消除外挂箱制造成本，降低边际飞行费用</td><td>接受外挂箱消耗，通过大运力摊薄单位载荷成本</td></tr>
|
||||
<tr><td>载荷舱</td><td>5.4 × 7.75 × 20 m</td><td>5.4 × 7.75 × 29.5 m</td></tr>
|
||||
<tr><td>发动机数量</td><td>3 台 RS-25EX</td><td>5 台 RS-25EX</td></tr>
|
||||
<tr><td>助推器</td><td>CERV 遗产 4m，downrange 海上回收</td><td>全新 5m，RTLS 返场回收</td></tr>
|
||||
<tr><td>乘员</td><td>4 人</td><td>19 人</td></tr>
|
||||
<tr><td>发射场</td><td>文昌 / 卡纳维拉尔角</td><td>文昌</td></tr>
|
||||
<tr><td>机身长度</td><td>86 m</td><td>61.5 m</td></tr>
|
||||
<tr><td>研制风险</td><td>较低（继承 CERV 助推器和 RS-25EX）</td><td>中高（全新助推器 + 10m ET）</td></tr>
|
||||
</tbody></table>
|
||||
<p>ThunderHawk 路线的核心优势是运营经济性——完全复用意味着每次飞行的边际成本中不再包含"一次性大件"的开支。但其弱点是 30 吨载荷上限和更短的载荷舱，在可预见的空间站扩建和母舰建造需求面前显得运力不足——这些任务需要一次性投送超大、超重的桁架和推进舱段，更适合大运力方案。</p>
|
||||
<h2 id="方案终止与遗产">方案终止与遗产</h2>
|
||||
<p>约 2032 年，ThunderHawk 方案正式终止，未进入立项阶段。直接原因有三：</p>
|
||||
<ol>
|
||||
<li><b>载荷量不足以应对未来需求</b>：在 MK4 机身横截面的固有约束下，为保底 30 吨有效载荷已将机身拉长至 86 米，助推器也已被迫放弃返场回收转而采用更远的 downrange 海上着陆。继续增加运力几乎没有工程空间。而招标需求中已可预见的空间站扩建和母舰建造任务，明确指向单次百吨级的重载投送能力——ThunderHawk 的架构无法扩展到这一量级。载荷舱长度（20 m）也显著短于竞标对手的方案，进一步限制了大型构件的运输。</li>
|
||||
<li><b>成本优势在重载场景下存疑</b>：ThunderHawk 消除了外挂箱制造成本这一 CERV 时代最大的单一消耗项，预计单次飞行成本约 3500 万美元。但在大型建造任务中，30 吨运力意味着需要数倍于竞标方案的发射次数才能完成同等的总投送质量。其成本结构中，发射运营费用和助推器远洋回收的额外时间/经济开销成为新的负担，低运力带来的发射次数放大效应可能完全侵蚀单次低价的优势。</li>
|
||||
<li><b>可拓展性受限</b>：2030 年代已可预见核推进是下一代航天飞机的演进方向。ThunderHawk 的架构围绕氢氧主发动机深度优化——内置储箱的尺寸、推进剂管理、热环境和重心设计均紧密耦合于 RS-25EX。要改装核气塞或核热推进系统，几乎需要推倒整个机身设计重来。相比之下，采用外挂燃料箱的方案天然地将推进剂储存与轨道器解耦，为后续核推进改装留下了充裕的工程空间。</li>
|
||||
</ol>
|
||||
<p>尽管方案终止，ThunderHawk 的多项核心设计并未完全消失。其内置储箱的完全复用理念、机身结构方案、喷气发动机系统设计和飞行控制系统架构被后续吸收至 Vulture 家族的衍生发展中。尤其是内置储箱思想——让航天飞机不再依赖一次性部件——在 Vulture Block 1.5 和 Block 2 的核气塞 SSTO 构型中以另一种技术路径得以延续。</p>
|
||||
<h2 id="技术参数">技术参数</h2>
|
||||
<p>以下参数基于方案阶段的设计指标；标记 [TBD] 的项目将在后续补充。</p>
|
||||
<h3>总体构型与性能</h3>
|
||||
<table>
|
||||
<thead><tr><th>参数</th><th>数值</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>类型</td><td>完全可重复使用航天飞机系统（方案）</td></tr>
|
||||
<tr><td>状态</td><td>方案阶段，约 2032 年终止</td></tr>
|
||||
<tr><td>机身构型</td><td>MK4</td></tr>
|
||||
<tr><td>轨道器长度</td><td>86 米</td></tr>
|
||||
<tr><td>轨道器翼展</td><td>[TBD]</td></tr>
|
||||
<tr><td>轨道器干重</td><td>[TBD]</td></tr>
|
||||
<tr><td>内置储箱推进剂容量</td><td>[TBD]</td></tr>
|
||||
<tr><td>起飞总推力</td><td>[TBD]</td></tr>
|
||||
<tr><td>发射场</td><td>文昌 / 卡纳维拉尔角</td></tr>
|
||||
<tr><td>典型目标轨道</td><td>650 km × 650 km，51° 倾角</td></tr>
|
||||
<tr><td>典型载荷能力</td><td>30 吨至典型目标轨道</td></tr>
|
||||
</tbody></table>
|
||||
<h3>轨道器参数</h3>
|
||||
<table>
|
||||
<thead><tr><th>参数</th><th>数值</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>机身构型</td><td>MK4</td></tr>
|
||||
<tr><td>轨道器长度</td><td>86 米</td></tr>
|
||||
<tr><td>轨道器翼展</td><td>[TBD]</td></tr>
|
||||
<tr><td>轨道器干重</td><td>[TBD]</td></tr>
|
||||
<tr><td>轨道器主发动机</td><td>3 台 RS-25EX；单台干重 2.88 吨；燃烧室压力 26 MPa；真空推力 2,812 kN；真空比冲 454 s；海平面推力 2,353.7 kN；海平面比冲 380 s</td></tr>
|
||||
<tr><td>主发动机最长点火时间</td><td>[TBD]</td></tr>
|
||||
<tr><td>OMS 发动机</td><td>[TBD]</td></tr>
|
||||
<tr><td>OMS 推进剂</td><td>[TBD]</td></tr>
|
||||
<tr><td>OMS 推进剂装载量</td><td>[TBD]</td></tr>
|
||||
<tr><td>RCS 推进剂</td><td>[TBD]</td></tr>
|
||||
<tr><td>大气层内发动机</td><td>2 台涡喷发动机</td></tr>
|
||||
<tr><td>喷气发动机燃料</td><td>[TBD]</td></tr>
|
||||
<tr><td>喷气发动机推力</td><td>[TBD]</td></tr>
|
||||
<tr><td>载荷舱尺寸</td><td>约 5.4 m × 7.75 m × 20 m</td></tr>
|
||||
<tr><td>最大乘员</td><td>4 人</td></tr>
|
||||
<tr><td>生命支持系统</td><td>[TBD]</td></tr>
|
||||
<tr><td>起落架</td><td>前三点式可收放起落架</td></tr>
|
||||
<tr><td>乘员逃生系统</td><td>[TBD]</td></tr>
|
||||
</tbody></table>
|
||||
<h3>液体助推器参数（单枚）</h3>
|
||||
<table>
|
||||
<thead><tr><th>参数</th><th>数值</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>直径</td><td>4 米</td></tr>
|
||||
<tr><td>发动机</td><td>9 台 TH-12 液氧煤油发动机</td></tr>
|
||||
<tr><td>推进剂</td><td>液氧/煤油</td></tr>
|
||||
<tr><td>干重</td><td>[TBD]</td></tr>
|
||||
<tr><td>推进剂容量</td><td>[TBD]</td></tr>
|
||||
<tr><td>燃烧时间</td><td>[TBD]</td></tr>
|
||||
<tr><td>回收方式</td><td>Downrange landing，距发射场约 400 km 海上着陆平台</td></tr>
|
||||
<tr><td>回收硬件</td><td>栅格翼，热燃气姿控系统，着陆腿</td></tr>
|
||||
</tbody></table>
|
||||
<h3>成本参数</h3>
|
||||
<table>
|
||||
<thead><tr><th>参数</th><th>数值</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>预计单次飞行成本</td><td>约 3500 万美元</td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="图片">图片</h2>
|
||||
<table>
|
||||
<thead><tr><th>图片</th><th>内容</th><th>位置</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>轨道器侧视图</td><td>ThunderHawk 轨道器方案概念渲染 — MK4 机身，86m 全长，大型三角翼，翼尖双垂尾，前部鸭翼。与 Vulture 共享翼型布局风格，但机身明显更长。</td><td>信息框</td></tr>
|
||||
<tr><td>轨道器剖面图</td><td>内部布局示意：前部乘员舱（4 人）和载荷舱（5.4×7.75×20m），中部内置液氧/液氢储箱段，尾部 3×RS-25EX + OMS/RCS + 2×涡喷发动机。</td><td>系统组成 / 轨道器</td></tr>
|
||||
<tr><td>起飞构型 + 助推器回收</td><td>完整发射构型：轨道器 + 两枚 4 米液体助推器。助推器分离后 downrange 海上平台着陆示意。</td><td>系统组成 / 液体助推器</td></tr>
|
||||
<tr><td>全任务剖面</td><td>从发射到着陆的完整任务流程示意：起飞 → 助推器分离+downrange回收 → MECO → OMS入轨 → 在轨操作 → 离轨 → 再入 → 水平着陆。</td><td>任务剖面</td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="参见">参见</h2>
|
||||
<ul>
|
||||
<li><a href="/home/Space_Shuttles/Vulture_Shuttle">秃鹫航天飞机（Vulture Shuttle）</a></li>
|
||||
<li><a href="/home/Space_Shuttles/CERV_Shuttle">CERV 航天飞机</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>
|
||||
Reference in New Issue
Block a user