feat: add CERV Shuttle wiki pages (zh+en), global timeline realignment
- Add CERV Shuttle zh+en wiki pages with full technical specs, fleet data, mission history - Realign all shuttle pages to current simulation time (2060-03-12): - Vulture B1 first flight 2037, B1.5 conversion 2051-2053, B2 first flight 2055 - Echo first flight 2056, operational 2057 - Enterprise first flight 2057, operational 2058 - Update CERV technical data: dimensions, masses, fuel quantities, endurance - Expand Vulture fleet with 10 named orbiters, 3-batch structure, rich events table - Update CERV booster recovery to RTLS mode - Move reference files to reference/ directory - Save simulation_time memory reference Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Claude Opus 4.7
Binary file not shown.
|
After Width: | Height: | Size: 5.6 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.2 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 9.4 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 6.6 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.8 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 2.8 MiB |
@@ -0,0 +1,48 @@
|
||||
# CERV 图片内容识别说明
|
||||
|
||||
本文件记录 `data/KSP/CERV` 目录下现有截图的画面内容识别。图片均与 CERV 航天飞机相关，描述参考 `data/wiki/cerv_shuttle_zh.html` 中关于 CERV 的设定：CERV 采用轨道器、8.4 米外挂燃料箱和两枚 4 米液体燃料助推器的垂直发射/水平着陆构型，并具备整体式乘员舱全阶段逃逸能力。
|
||||
|
||||
为避免称呼含糊，本文统一使用以下名称：CERV 轨道器（Orbiter）、外挂燃料箱（External Tank, ET）、液体助推器（booster）、乘员逃逸舱。
|
||||
|
||||
## 总体判断
|
||||
|
||||
这批图片大致分为三组：
|
||||
|
||||
1. `screenshot52.png` 至 `screenshot55.png` 展示 CERV 全栈发射、上升和液体助推器分离相关画面。
|
||||
2. `screenshot56.png` 至 `screenshot60.png` 以及 `screenshot64.png` 展示 CERV 轨道器在高空、近空间和再入阶段的飞行画面。
|
||||
3. `screenshot61.png` 至 `screenshot63.png` 展示乘员舱整体逃逸测试和伞降回收画面。
|
||||
|
||||
## 逐图识别
|
||||
|
||||
| 文件 | 画面内容 | 对应 CERV 设定 | 建议用途 |
|
||||
| --- | --- | --- | --- |
|
||||
| `screenshot52.png` | CERV 全栈从发射台起飞。画面可见白色轨道器侧挂在大型棕色外挂燃料箱旁，两侧液体助推器点火，发射场建筑、跑道和天线阵列位于下方。 | 垂直发射构型；轨道器 + 8.4 m ET + 两枚 4 m 液体燃料助推器；发射场任务场景。 | 信息框主图或“发射与上升段”配图，适合作为 CERV 发射构型展示。 |
|
||||
| `screenshot53.png` | CERV 全栈在蓝天中继续上升，视角从下后方观察，可见轨道器、外挂燃料箱和两枚助推器的发动机尾焰。 | 上升段由两枚液体助推器与三台 RS-25D 主发动机共同提供推力。 | “任务剖面/发射与上升段”配图，强调多发动机联合上升。 |
|
||||
| `screenshot55.png` | 高空近空间环境下的 CERV 全栈，中央轨道器和外挂燃料箱继续飞行，两侧液体助推器已经分离并向外展开，地平线和大气层边缘清晰可见。 | 助推器分离后执行再入和反推回收；轨道器主发动机继续工作直至主发动机关机。 | “液体燃料助推器”或“任务剖面/助推器分离”配图，展示 CERV 与 STS 不同的液体助推器路线。 |
|
||||
| `screenshot56.png` | CERV 轨道器位于近空间环境中，机体周围出现橙红色等离子体或高速气动加热痕迹，下方为地球大气层。 | CERV 再入阶段由改进型通用隔热瓦、隔热涂层和机翼前缘增强碳碳材料承受气动加热。 | “返回与着陆”或“热防护系统”配图，展示轨道器再入热流。 |
|
||||
| `screenshot57.png` | CERV 轨道器在再入边缘高速飞行，画面右侧为轨道器，周围有强烈热流发光，后方或侧后方可见明显尾迹。 | 再入阶段电传飞控管理攻角、滚转和侧滑，以控制热流、航程和姿态。 | “返回与着陆”配图，适合说明高空再入和热流控制。 |
|
||||
| `screenshot58.png` | CERV 轨道器近距离特写，机体被高亮等离子体和尾迹包裹，显示其在高速再入或高超声速飞行中穿越大气。 | 轨道器热防护系统在再入段承受极端热流，隔热瓦和下层涂层提供冗余保护。 | “热防护系统”配图，强调再入热环境和机体防护。 |
|
||||
| `screenshot59.png` | CERV 轨道器位于画面右侧，地球弧面下方可见，机体被明亮热流包裹，画面中有一条较长的高温尾迹。 | CERV 作为有翼轨道器返回时以升力体滑翔方式减速，并通过姿态控制管理热流。 | “任务剖面/返回与着陆”配图，可展示再入轨迹与气动加热。 |
|
||||
| `screenshot60.png` | CERV 轨道器在高空再入过程中从画面右侧掠过，带有明亮等离子体尾迹和较长气动或热流轨迹，下方可见地球表面。 | 轨道器从轨道返回后进入大气层，再入热流逐渐增强，随后转入滑翔下降和喷气发动机辅助着陆流程。 | “返回与着陆”配图，可作为再入段与后续着陆段之间的过渡画面。 |
|
||||
| `screenshot61.png` | 发射场上空出现小型逃逸舱垂直上升，尾部有推进火焰；下方可见发射场跑道和地面设施，底部露出 CERV 全栈一部分。 | 发射台静态逃逸或低空逃逸测试场景；整体式乘员舱可在地面待发阶段脱离轨道器。 | “哥伦比亚事故与安全改进需求”或“乘员舱整体逃逸系统”配图，说明发射台逃逸能力。 |
|
||||
| `screenshot62.png` | 高俯视角下，逃逸舱从发射场/跑道区域上方飞离，尾部有推进尾迹，下方可见发射中心建筑群和停机坪标记。 | 发射台或低空逃逸流程中的横向远离动作，用于让乘员舱脱离全栈危险区域。 | “乘员舱整体逃逸系统”配图，展示逃逸舱离开发射设施的轨迹。 |
|
||||
| `screenshot63.png` | 逃逸舱已进入降落伞回收阶段。大型降落伞完全展开，舱体悬挂在伞下，背景是蓝天和远处发射场。 | 逃逸飞行后通过引导伞和主伞系统水面或陆地着陆，设计着陆速度不高于 8 m/s。 | “逃逸动力”或“乘员舱整体逃逸系统”末段配图，展示伞降回收。 |
|
||||
| `screenshot64.png` | 近空间/高空再入氛围图，右侧可见 CERV 轨道器局部，背景为地球弧面、日出/日落色带和星空。 | CERV 轨道器在高空返回阶段经历大气边缘热流与姿态控制。 | 可作为“返回与着陆”或条目顶部氛围图；若需要严谨说明，建议标注为“高空返回/再入阶段渲染”。 |
|
||||
|
||||
## 可用于 Wiki 的图片定位建议
|
||||
|
||||
| 条目位置 | 推荐图片 | 说明 |
|
||||
| --- | --- | --- |
|
||||
| 信息框 | `screenshot52.png` | 最直观展示 CERV 全栈发射构型。 |
|
||||
| 发射与上升段 | `screenshot53.png` | 展示轨道器、外挂燃料箱和液体助推器共同工作。 |
|
||||
| 液体燃料助推器 | `screenshot55.png` | 展示助推器分离与回收流程的起点。 |
|
||||
| 乘员舱整体逃逸系统 | `screenshot61.png`, `screenshot62.png`, `screenshot63.png` | 分别表现发射场逃逸、逃逸飞离和伞降回收。 |
|
||||
| 再入与热防护 | `screenshot56.png`, `screenshot57.png`, `screenshot58.png`, `screenshot59.png`, `screenshot60.png` | 展示 CERV 轨道器高空再入时的热流包络和气动尾迹。 |
|
||||
| 返回与着陆 | `screenshot64.png` | 可作为高空返回阶段的氛围图，但不宜单独用作常规跑道着陆图。 |
|
||||
|
||||
## 注意事项
|
||||
|
||||
- 这些截图更像任务过程渲染或 KSP 内拍摄画面，不是严格工程三视图。
|
||||
- 当前目录中未看到直接展示 CERV 轨道器三视图、助推器发动机 8+1 布局、气闸舱与 1.875 m 可伸缩对接口的专门图片。
|
||||
- 只有 `screenshot61.png`、`screenshot62.png` 和 `screenshot63.png` 是乘员舱整体逃逸相关图片；其余截图应按 CERV 轨道器或 CERV 全栈（轨道器 + 外挂燃料箱 + 液体助推器）任务画面处理。
|
||||
- `screenshot64.png` 画面视觉效果强，但主体只露出局部，适合做氛围图或返回阶段示意，不适合作为结构说明图。
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 7.5 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 7.3 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.9 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 4.8 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 4.6 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 6.8 MiB |
@@ -0,0 +1,506 @@
|
||||
<style>
|
||||
.wiki-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; }
|
||||
.wiki-article h1, .wiki-article h2 { font-family: "Linux Libertine", Georgia, "Times New Roman", serif; font-weight: normal; border-bottom: 1px solid #a2a9b1; }
|
||||
.wiki-article h1 { margin: 0 0 8px; font-size: 2.15em; line-height: 1.25; }
|
||||
.wiki-article h2 { clear: both; margin: 1.35em 0 0.6em; padding-bottom: 0.18em; font-size: 1.55em; }
|
||||
.wiki-article h3 { margin: 1.05em 0 0.35em; font-size: 1.18em; font-weight: bold; }
|
||||
.wiki-article h4 { margin: 0.9em 0 0.25em; font-size: 1.02em; font-weight: bold; }
|
||||
.wiki-article p { margin: 0.45em 0 0.85em; }
|
||||
.wiki-article a { color: #0645ad; text-decoration: none; }
|
||||
.wiki-article a:hover { text-decoration: underline; }
|
||||
.wiki-article ul, .wiki-article ol { margin: 0.35em 0 0.9em 1.65em; padding: 0; }
|
||||
.wiki-article li { margin-bottom: 0.18em; }
|
||||
.wiki-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; }
|
||||
.wiki-article .infobox caption { padding: 8px; background: #eaecf0; border: 1px solid #a2a9b1; border-bottom: 0; font-weight: bold; font-size: 1.12em; }
|
||||
.wiki-article .infobox caption span { display: block; font-size: 0.92em; font-weight: normal; }
|
||||
.wiki-article .infobox td { border: 1px solid #a2a9b1; padding: 6px 8px; vertical-align: top; }
|
||||
.wiki-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; }
|
||||
.wiki-article .infobox .image-placeholder { min-height: 185px; }
|
||||
.wiki-article img { max-width: 100%; height: auto; }
|
||||
.wiki-article .media-link img { display: block; width: 100%; cursor: zoom-in; }
|
||||
.wiki-article .wiki-modal-card img { display: block; width: 100%; }
|
||||
.wiki-article .media-link { display: block; color: inherit; text-decoration: none; }
|
||||
.wiki-article .media-link:hover { text-decoration: none; }
|
||||
.wiki-article .media-link:hover .image-placeholder { border-color: #36c; background: #f8f9fa; color: #202122; }
|
||||
.wiki-article .thumb { width: 265px; border: 1px solid #c8ccd1; background: #f8f9fa; padding: 3px; font-size: 88%; line-height: 1.4; box-sizing: border-box; }
|
||||
.wiki-article .tright { float: right; clear: right; margin: 0.35em 0 1em 1.4em; }
|
||||
.wiki-article .tleft { float: left; clear: left; margin: 0.35em 1.4em 1em 0; }
|
||||
.wiki-article .thumbcaption { padding: 4px 3px 2px; text-align: left; color: #202122; }
|
||||
.wiki-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%; }
|
||||
.wiki-article .toc-title { text-align: center; font-weight: bold; margin-bottom: 4px; }
|
||||
.wiki-article .toc ol { margin: 0 0 0 1.5em; }
|
||||
.wiki-article > table:not(.infobox) { width: 100%; margin: 1em 0; border-collapse: collapse; font-size: 92%; background: #fff; }
|
||||
.wiki-article > table:not(.infobox) th, .wiki-article > table:not(.infobox) td { border: 1px solid #a2a9b1; padding: 6px 8px; text-align: left; vertical-align: top; }
|
||||
.wiki-article > table:not(.infobox) th { background: #eaecf0; font-weight: bold; }
|
||||
.wiki-article > table:not(.infobox) tr:nth-child(even) td { background: #f8f9fa; }
|
||||
.wiki-article .launch-chart { margin: 1em 0; padding: 8px 10px 10px; border: 1px solid #a2a9b1; background: #f8f9fa; font-size: 92%; }
|
||||
.wiki-article .launch-stage-label { margin: 8px 0 4px; padding-bottom: 2px; border-bottom: 1px solid #c8ccd1; font-weight: bold; }
|
||||
.wiki-article .launch-row { display: grid; grid-template-columns: 54px 1fr 42px 62px; gap: 8px; align-items: center; margin: 3px 0; }
|
||||
.wiki-article .launch-head { color: #54595d; font-weight: bold; }
|
||||
.wiki-article .launch-track { height: 14px; border: 1px solid #c8ccd1; background: #eaecf0; box-sizing: border-box; }
|
||||
.wiki-article .launch-bar { display: block; height: 100%; background: #36c; }
|
||||
.wiki-article .launch-bar.highlight { background: #d33; }
|
||||
.wiki-article .launch-count, .wiki-article .launch-cumulative { text-align: right; white-space: nowrap; }
|
||||
.wiki-article .launch-cumulative { color: #54595d; }
|
||||
.wiki-article .wiki-modal { position: fixed; inset: 0; display: none; align-items: center; justify-content: center; padding: 24px; background: rgba(32,33,34,0.82); z-index: 9999; box-sizing: border-box; }
|
||||
.wiki-article .wiki-modal:target { display: flex; }
|
||||
.wiki-article .wiki-modal-card { width: min(920px, 96vw); max-height: 90vh; overflow: auto; border: 1px solid #a2a9b1; background: #fff; padding: 10px; box-shadow: 0 12px 38px rgba(0,0,0,0.35); box-sizing: border-box; }
|
||||
.wiki-article .wiki-modal-card .image-placeholder { min-height: 420px; font-size: 1.22em; }
|
||||
.wiki-article .modal-close { float: right; width: 28px; height: 28px; margin: -2px -2px 6px 8px; border: 1px solid #a2a9b1; background: #eaecf0; color: #202122; text-align: center; line-height: 26px; font-weight: bold; }
|
||||
.wiki-article .modal-close:hover { background: #fff; text-decoration: none; }
|
||||
@media (max-width: 820px) { .wiki-article { padding: 18px 16px 36px; } .wiki-article .infobox, .wiki-article .thumb { float: none; width: 100%; margin: 0.75em 0 1em; } .wiki-article .toc { display: block; } .wiki-article .launch-row { grid-template-columns: 46px 1fr 36px; } .wiki-article .launch-cumulative { display: none; } .wiki-article .wiki-modal { padding: 12px; } .wiki-article .wiki-modal-card .image-placeholder { min-height: 280px; } }
|
||||
|
||||
.wiki-article img[data-wiki-asset], .vulture-article img[data-wiki-asset] { cursor: zoom-in; }
|
||||
.wiki-image-lightbox { position: fixed; inset: 0; display: flex; align-items: center; justify-content: center; padding: 24px; background: rgba(32,33,34,0.84); z-index: 10000; box-sizing: border-box; }
|
||||
.wiki-image-lightbox[hidden] { display: none; }
|
||||
.wiki-image-lightbox-panel { position: relative; width: min(1120px, 96vw); max-height: 92vh; overflow: auto; margin: 0; padding: 10px; border: 1px solid #a2a9b1; background: #fff; box-shadow: 0 12px 38px rgba(0,0,0,0.35); box-sizing: border-box; }
|
||||
.wiki-image-lightbox-panel img { display: block; width: 100%; height: auto; max-height: 82vh; object-fit: contain; background: #000; }
|
||||
.wiki-image-lightbox-close { position: sticky; top: 0; float: right; width: 30px; height: 30px; margin: -2px -2px 8px 10px; border: 1px solid #a2a9b1; background: #eaecf0; color: #202122; font-weight: bold; line-height: 26px; cursor: pointer; }
|
||||
.wiki-image-lightbox-close:hover, .wiki-image-lightbox-close:focus { background: #fff; }
|
||||
body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
@media (max-width: 820px) { .wiki-image-lightbox { padding: 12px; } .wiki-image-lightbox-panel { width: 98vw; max-height: 94vh; } }
|
||||
</style>
|
||||
<article class="mw-parser-output wiki-article">
|
||||
<h1 id="cerv-shuttle">CERV Shuttle</h1>
|
||||
<table class="infobox">
|
||||
<caption>CERV Shuttle<span>Composite Enhanced Reusable Vehicle</span></caption>
|
||||
<tbody>
|
||||
<tr><td><a class="media-link" href="#cerv-img-launch"><img src="/cerv/cerv_launch_pad.png" alt="CERV Shuttle launch" data-wiki-asset="/cerv/cerv_launch_pad.png"></a><div class="thumbcaption">CERV employs a three-element launch configuration: orbiter, 8.4 m external tank, and two 4 m liquid-fuel boosters, with an integrated crew cabin escape capability.</div></td></tr>
|
||||
<tr><td><b>Full name</b>: Composite Enhanced Reusable Vehicle</td></tr>
|
||||
<tr><td><b>Type</b>: Reusable crewed space shuttle</td></tr>
|
||||
<tr><td><b>Generation</b>: Second-generation space shuttle</td></tr>
|
||||
<tr><td><b>Predecessor</b>: STS Space Shuttle (1st generation)</td></tr>
|
||||
<tr><td><b>Successor</b>: Vulture Shuttle (3rd generation)</td></tr>
|
||||
<tr><td><b>Development</b>: 2005 - 2015</td></tr>
|
||||
<tr><td><b>Maiden flight</b>: June 2015 (CERV-F1, flown by <i>Horizon</i>)</td></tr>
|
||||
<tr><td><b>Service period</b>: 2017 - 2040</td></tr>
|
||||
<tr><td><b>Final flight</b>: 15 June 2040 (CERV-F666, flown by <i>Discovery</i>)</td></tr>
|
||||
<tr><td><b>Launch sites</b>: Wenchang Space Launch Site / Cape Canaveral</td></tr>
|
||||
<tr><td><b>Primary landing sites</b>: Cape Canaveral Shuttle Landing Facility / Wenchang Spacecraft Landing Runway</td></tr>
|
||||
<tr><td><b>Configuration</b>: Vertical launch / horizontal landing</td></tr>
|
||||
<tr><td><b>Orbiter airframe</b>: Aluminum-composite hybrid structure</td></tr>
|
||||
<tr><td><b>Orbiter dry mass</b>: 63 tonnes</td></tr>
|
||||
<tr><td><b>Max takeoff weight</b>: 2,169.9 t (with 30 t payload)</td></tr>
|
||||
<tr><td><b>Length</b>: Orbiter 36 m / Full stack 55.4 m</td></tr>
|
||||
<tr><td><b>Wingspan</b>: 24.3 m</td></tr>
|
||||
<tr><td><b>Payload capacity</b>: 30 t (upmass) / 20 t (return)</td></tr>
|
||||
<tr><td><b>Crew capacity</b>: 8 (typically 2 pilots + 0-6 mission specialists)</td></tr>
|
||||
<tr><td><b>Status</b>: Retired (2040)</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<p>The <b>CERV Shuttle</b> (<b>Composite Enhanced Reusable Vehicle</b>, abbreviated <b>CERV</b>) is the second-generation crewed space shuttle developed after the STS Space Shuttle. Building on the STS orbiter, 8.4 m external tank, and three RS-25D main engine configuration, CERV entered development in 2005, flew its maiden mission CERV-F1 in June 2015 aboard <i>Horizon</i>, formally succeeded the retired STS in 2017, and was itself succeeded by the third-generation Vulture Shuttle in 2040. The final mission, CERV-F666, was flown by <i>Discovery</i> on 15 June 2040.</p>
|
||||
<p>While retaining the STS core architecture, CERV introduced four fundamental improvements: extensive use of composite materials reduced the orbiter dry mass to 63 tonnes; a first-of-its-kind integrated crew cabin escape system was introduced; solid rocket boosters were replaced with recoverable liquid-fuel boosters; and the aerodynamic configuration shifted from a single large central vertical stabilizer to twin wingtip vertical stabilizers with forward canards. Additionally, CERV was equipped with two jet engines for landing assist, cross-range extension, and go-around capability, making it the first crewed space shuttle with a go-around option.</p>
|
||||
<p>CERV launched from Wenchang Space Launch Site and Cape Canaveral, capable of delivering 30 tonnes to a 600x600 km x 51 deg orbit and returning 20 tonnes. The orbiter featured a fly-by-wire flight control system with fully autonomous flight capability in all phases, including landing. Free-flight endurance was 15 days (extended to 20 days on later batches), and docked endurance at a space station or orbital shipyard could reach 120 days via external power. CERV's liquid booster design, crew escape architecture, wing layout, and thermal protection system provided the direct engineering foundation for the Vulture Shuttle.</p>
|
||||
<p>Within the shuttle lineage, CERV was positioned as the "safety-enhanced space shuttle." Rather than pursuing a generational performance leap beyond STS, it was driven by the lessons of the <i>Columbia</i> accident to systematically address ascent crew safety, structural aging, non-recoverable boosters, and landing flexibility shortfalls. After retirement, its liquid booster technology, integrated escape concept, composite material applications, and improved thermal protection system were inherited and advanced by the Vulture Shuttle.</p>
|
||||
|
||||
<nav class="toc" aria-label="Contents">
|
||||
<div class="toc-title">Contents</div>
|
||||
<ol>
|
||||
<li><a href="#background-and-development">Background and Development</a></li>
|
||||
<li><a href="#design">Design</a>
|
||||
<ol>
|
||||
<li><a href="#orbiter">Orbiter</a></li>
|
||||
<li><a href="#external-tank">External Tank</a></li>
|
||||
<li><a href="#liquid-fuel-boosters">Liquid Fuel Boosters</a></li>
|
||||
</ol></li>
|
||||
<li><a href="#propulsion-and-power">Propulsion and Power</a></li>
|
||||
<li><a href="#crew-and-payload">Crew and Payload</a></li>
|
||||
<li><a href="#mission-profile">Mission Profile</a></li>
|
||||
<li><a href="#fleet">Fleet</a></li>
|
||||
<li><a href="#operational-history">Operational History</a></li>
|
||||
<li><a href="#notable-missions-and-payloads">Notable Missions and Payloads</a></li>
|
||||
<li><a href="#relationship-to-sts-and-vulture">Relationship to STS and Vulture</a></li>
|
||||
<li><a href="#specifications">Specifications</a></li>
|
||||
<li><a href="#assessment">Assessment</a></li>
|
||||
<li><a href="#see-also">See Also</a></li>
|
||||
</ol>
|
||||
</nav>
|
||||
|
||||
<h2 id="background-and-development">Background and Development</h2>
|
||||
<h3 id="columbia-accident-and-safety-imperative">Columbia Accident and Safety Imperative</h3>
|
||||
<p>The 2003 <i>Columbia</i> accident was the pivotal event driving CERV's initiation. During STS-107 reentry, foam shedding from the external tank at launch had struck and breached the left wing leading edge thermal protection, allowing superheated gas to penetrate the wing structure. The orbiter disintegrated, killing all seven crew members. The accident investigation identified not only the direct causes of foam shedding and TPS vulnerability, but also systemic deficiencies in STS ascent crew escape capability, on-orbit TPS inspection, and organizational risk assessment.</p>
|
||||
<p>After the accident, NASA undertook extensive return-to-flight modifications to the three remaining STS orbiters, including improved foam application processes, on-orbit robotic arm TPS inspections, enhanced ascent camera coverage, and revised mission abort rules. However, these modifications could not resolve two fundamental structural problems: the orbiter was side-mounted beside the tank with no ascent escape path for the crew, and the solid rocket boosters could not be throttled or shut down once ignited. Foam shedding risk could be reduced but not eliminated. The single large vertical stabilizer and STS glide characteristics left virtually no go-around margin during landing.</p>
|
||||
<p>Concurrently, the STS orbiters, designed in the 1980s with extensive aluminum structures, had high empty weights that limited payload capacity and mission flexibility. After more than two decades of high-frequency flight, structural fatigue was accumulating and maintenance costs rising. Following the 2004 announcement of the Constellation program, STS was originally planned for retirement in 2010, but repeated delays in replacement system development created a shuttle lineage gap risk.</p>
|
||||
<h3 id="cerv-program-initiation">CERV Program Initiation</h3>
|
||||
<p>CERV was formally initiated in 2005. The program objective was explicit: building upon STS operational experience and ground infrastructure, develop a shuttle with greater safety margins, improved maintainability, payload capacity no lower than STS, and integrated crew escape capability - rather than pursuing an entirely new launch architecture. The name - Composite Enhanced Reusable Vehicle - directly reflected the core engineering strategy: using composite material mass reduction to buy safety enhancement and performance improvement.</p>
|
||||
<p>Unlike the contemporaneous Constellation program's Ares rocket and Orion spacecraft, CERV did not depart from the shuttle paradigm of vertical launch, horizontal landing, and combined crew/cargo transport. The program held that STS operational systems - launch pads, Vehicle Assembly Building, crawler-transporters, landing runways, and Mission Control - were strategic assets of the shuttle lineage that should not be discarded; what the lineage needed was not a paradigm shift, but filling the safety gaps.</p>
|
||||
<p>Early trade studies evaluated multiple alternatives, including fully reusable two-stage-to-orbit vehicles, a combination of small crew capsules with cargo rockets, and retaining STS solid boosters with an orbiter-only replacement. The final determination: the liquid booster path, though higher in development cost, offered throttle, shutdown, abort, and RTLS return-to-launch-site capabilities, with superior total safety benefit and lifecycle cost compared to the solid booster path. Composite airframe and integrated crew escape cabin were listed as non-negotiable safety requirements.</p>
|
||||
|
||||
<h3 id="development-phases">Development Phases</h3>
|
||||
<table>
|
||||
<thead><tr><th>Phase</th><th>Period</th><th>Key Activities</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>Concept definition</td><td>2005-2007</td><td>Confirmed composite airframe, liquid boosters, integrated escape cabin, and twin wingtip stabilizer configuration.</td></tr>
|
||||
<tr><td>Critical design review</td><td>2008-2009</td><td>Completed composite primary structure design, TH-12 engine testing, escape cabin separation tests, and wing configuration wind tunnel validation.</td></tr>
|
||||
<tr><td>Orbiter assembly</td><td>2010-2013</td><td>Manufactured first orbiter; completed fuselage bending and torsion tests, pressurized cabin fatigue tests, and wing/canard attachment strength tests.</td></tr>
|
||||
<tr><td>Integration testing</td><td>2013-2014</td><td>Full-stack orbiter/ET/booster integration, avionics integration testing, escape cabin full-sequence ground tests, and jet engine pre-flight acceptance.</td></tr>
|
||||
<tr><td>First flight preparation</td><td>2014-2015</td><td>Completed full-stack vibration testing, launch countdown rehearsal, and uncrewed orbital flight readiness review.</td></tr>
|
||||
<tr><td>Maiden flight</td><td>June 2015</td><td>CERV-F1 flown by <i>Horizon</i>; first uncrewed orbital flight, validating main engines, booster recovery, reentry, and horizontal landing.</td></tr>
|
||||
<tr><td>Crew certification</td><td>2015-2016</td><td>Completed crewed test flights, in-flight escape cabin testing, jet engine landing assist validation, and on-orbit endurance testing.</td></tr>
|
||||
<tr><td>STS succession</td><td>2017</td><td>STS formally retired; CERV assumed all crew and cargo missions.</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="design">Design</h2>
|
||||
|
||||
<h3 id="orbiter">Orbiter</h3>
|
||||
<figure class="thumb tright"><div class="image-placeholder">CERV orbiter three-view diagram placeholder</div><figcaption class="thumbcaption">CERV orbiter with twin wingtip vertical stabilizers and forward canards, eliminating the STS single large central vertical stabilizer. (Three-view diagram pending)</figcaption></figure>
|
||||
<h4>Structure and Materials</h4>
|
||||
<p>The orbiter airframe employed an aluminum-composite hybrid structure: the primary load-bearing framework used aluminum for thermal stability, while wing skins, payload bay doors, fuselage panels, and non-load-bearing bulkheads made extensive use of carbon-fiber-reinforced composites. The heavy composite application reduced the orbiter dry mass to 63 tonnes, approximately 19% less than the STS orbiter (roughly 78 tonnes). The mass reduction translated directly into additional payload capacity and freed weight budget for the crew escape system, jet engines, and enhanced avionics.</p>
|
||||
<p>Composite material selection and manufacturing were jointly undertaken by Boeing and Northrop Grumman. Wing skins used co-cured integrally stiffened panels, reducing fastener count and assembly labor. Payload bay doors employed composite honeycomb sandwich construction, achieving roughly 30% mass reduction while maintaining equivalent stiffness to STS doors. Secondary structures in the mid and aft fuselage sections extensively applied composite panels, retaining titanium or high-strength aluminum reinforcements only at engine thrust mounts, landing gear attachment points, and wing-fuselage joints.</p>
|
||||
<h4>Thermal Protection System</h4>
|
||||
<figure class="thumb tright"><a class="media-link" href="#cerv-img-reentry"><img src="/cerv/cerv_reentry_closeup.png" alt="CERV orbiter during reentry" data-wiki-asset="/cerv/cerv_reentry_closeup.png"></a><figcaption class="thumbcaption">CERV orbiter enveloped in plasma during reentry. Improved universal thermal tiles and underlying insulation coating provide redundant thermal protection.</figcaption></figure>
|
||||
<p>CERV used improved universal thermal tiles, enhancing durability and maintainability over the STS TPS baseline. The universal tiles employed standardized dimensions and modular mounting interfaces, reducing the number of unique tile specifications required across different locations. Single-tile replacement time was shortened by approximately 40% compared to STS. A thermal insulation coating beneath the tiles provided residual protection in the event of partial tile fracture or detachment - a redundancy directly addressing the <i>Columbia</i> lesson: when one or more tiles failed, the underlying coating could delay hot gas penetration into the primary structure, buying additional response time. Enhanced carbon-carbon materials were used in extreme heating zones at wing leading edges and the nose cap. Batch 2 orbiters received an improved coating formulation that increased post-reentry coating integrity retention; Batch 3 introduced an upgraded tile substrate material with greater reuse margin after high-energy returns.</p>
|
||||
<h4>Aerodynamic Configuration</h4>
|
||||
<p>CERV completed the aerodynamic transition from STS to the next generation. The type abandoned the STS single large central vertical stabilizer in favor of two small vertical stabilizers at the delta wing tips. The twin stabilizers provided directional stability and yaw control during reentry and glide while eliminating the structural mass concentration along the fuselage centerline. Forward canards on either side of the nose provided takeoff rotation, post-reentry pitch trim, and low-speed go-around functions. This wing configuration was subsequently inherited and scaled up by the Vulture Shuttle. On Batch 3 orbiters, the canard control surfaces were converted from hydraulic to electric actuation, reducing maintenance complexity.</p>
|
||||
<h4>Integrated Crew Cabin Escape System</h4>
|
||||
<figure class="thumb tright"><a class="media-link" href="#cerv-img-escape-flyaway"><img src="/cerv/cerv_escape_flyaway.png" alt="CERV crew cabin escape test" data-wiki-asset="/cerv/cerv_escape_flyaway.png"></a><figcaption class="thumbcaption">Crew cabin escape test: the escape cabin flies away from the launch site with solid boosters providing initial separation thrust.</figcaption></figure>
|
||||
<p>CERV was the first shuttle in the lineage to achieve integrated crew cabin escape capability. The crew cabin, a self-contained pressurized structure at the forward end of the orbiter, could physically separate from the orbiter in any flight phase - including on the pad, during ascent, on orbit, and during reentry. Separation was initiated by two solid-fuel boosters mounted aft of the cabin, providing the initial high peak thrust to rapidly pull the cabin clear, primarily for the ground-to-100 km altitude regime and especially for maximum dynamic pressure (max-Q) escape. Once the cabin reached 5 meters from the orbiter, four bipropellant storable-fuel escape engines ignited, operating simultaneously with the remaining solid motor burn to maximize total thrust. After solid burnout, the storable engines continued independently, delivering the cabin to a safe altitude and trajectory.</p>
|
||||
<p>The escape system was designed for all flight phases. Above 100 km or during reentry where aerodynamic loads were lower, the system could skip the solid phase and execute separation directly with the storable engines. The cabin carried independent batteries, inertial navigation, and parachute deployment logic. Escape triggering could be crew-initiated or automatically commanded by the launch abort computer. The integrated escape concept was directly inherited and extended by the Vulture Shuttle.</p>
|
||||
<h4>Jet Engines</h4>
|
||||
<p>Two turbofan jet engines in the aft fuselage provided landing assist, cross-range extension, and go-around capability. In the standard landing sequence, the jet engines were started below 10,000 meters, and after establishing thrust the orbiter flew a circuit to dissipate excess energy before capturing the ILS approach. The jet engines gave CERV a go-around capability previously absent from the shuttle lineage: if the approach was unstable, the runway occupied, or wind shear exceeded limits, the orbiter could execute a go-around and reposition for a second approach. Go-around required afterburner engagement to achieve sufficient climb thrust at maximum return mass. If jet engine start failed, the orbiter switched to a direct glide landing using VFR - a backup mode validated through simulator training and multiple operational flights.</p>
|
||||
<h4>Avionics and Fly-by-Wire</h4>
|
||||
<p>CERV employed a fly-by-wire design, building on the STS glass cockpit with comprehensive digital upgrades. The Batch 1 flight control computers used a quadruplex-redundant architecture; Batch 2 upgraded to enhanced flight control processors with adaptive control law switching; Batch 3 adopted a next-generation integrated avionics platform that unified flight control, mission management, and communications/navigation functions. The orbiter was capable of fully autonomous flight in all phases including landing. Routine crew configuration remained two pilots, but the autonomous system could execute complete missions uncrewed.</p>
|
||||
<h4>Airlock and Docking Port</h4>
|
||||
<p>A built-in airlock in the forward payload bay supported EVA operations. A retractable 1.875 m universal docking port mounted above the airlock extended for hard capture and seal during docking and retracted into the payload bay wall during launch and reentry, reducing aerodynamic and thermal loads. Batch 2 introduced improved docking collar seals for extended docked duration; Batch 3 increased airlock volume by approximately 15%.</p>
|
||||
|
||||
<h3 id="external-tank">External Tank</h3>
|
||||
<p>CERV's external tank retained the STS 8.4-meter diameter specification. Departing from the STS all-foam insulation approach, CERV adopted a dual-layer design of sprayed insulation coating plus foam: the coating covered the vast majority of the tank surface, while foam was applied only to localized areas of highest aerodynamic heating and structural interfaces. This significantly reduced total foam quantity and the associated foam-shedding risk. The coating underwent extensive thermal cycling and vibration testing during the verification phase. CERV experienced no foam-shedding TPS damage events throughout its operational career, and the coating-plus-foam approach was inherited by the Vulture Shuttle.</p>
|
||||
|
||||
<h3 id="liquid-fuel-boosters">Liquid Fuel Boosters</h3>
|
||||
<figure class="thumb tright"><a class="media-link" href="#cerv-img-booster-sep"><img src="/cerv/cerv_booster_separation.png" alt="CERV booster separation" data-wiki-asset="/cerv/cerv_booster_separation.png"></a><figcaption class="thumbcaption">CERV full stack at high altitude with both liquid boosters separating. Boosters execute controlled reentry and RTLS propulsive landing at the launch site.</figcaption></figure>
|
||||
<p>The replacement of solid boosters with liquid-fuel boosters was one of CERV's most consequential engineering decisions. Two 4-meter-diameter liquid boosters were mounted symmetrically on either side of the 8.4 m external tank, each powered by nine enhanced TH-12 kerolox engines in an oxygen-rich staged combustion cycle, each producing 1,132.67 kN vacuum thrust. The nine engines were arranged in an 8+1 layout: eight fixed-thrust outboard, one center engine for throttling and thrust vector control. The boosters supported throttling, shutdown, and restart, enabling ascent thrust modulation and controlled shutdown in abort scenarios. Booster attitude control used a LOX/kerosene bipropellant RCS, sharing propellant type with the main engines for reduced system complexity. This bipropellant RCS approach was directly inherited by Vulture boosters.</p>
|
||||
<h4>Reuse and Maintenance</h4>
|
||||
<p>CERV boosters were designed for 50-flight service life with a planned maintenance interval every 10 flights. Maintenance included engine turbopump inspection, thrust chamber erosion assessment, RCS valve testing, grid fin deployment mechanism lubrication, and structural NDI. By comparison, Vulture's improved TH-12 retained identical performance specifications but achieved 75 maintenance-free flights and 200-300 flights with planned maintenance through turbopump bearing upgrades, thrust chamber cooling channel optimization, and material improvements. CERV's 50-flight design life and 10-flight maintenance interval provided the critical baseline data for Vulture booster life targets.</p>
|
||||
<h4>Booster Recovery Test Campaign</h4>
|
||||
<p>CERV's first five flights were all booster propulsive recovery tests:</p>
|
||||
<table>
|
||||
<thead><tr><th>Mission</th><th>Left Booster (LB)</th><th>Right Booster (RB)</th><th>Key Findings</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>CERV-F1</td><td colspan="2">Both boosters completed boost-back burn successfully; lost contact during reentry; later analysis indicated probable TPS failure.</td><td>Boost-back ignition logic and return trajectory viable; reentry TPS required strengthening.</td></tr>
|
||||
<tr><td>CERV-F2</td><td>Single engine failure at T+77 s; shutdown on schedule. Orbiter compensated by extending RS-25D burn and achieved nominal orbit. LB recovery aborted.</td><td>Normal shutdown; propulsive ignition; landing burn failed.</td><td>Single engine failure survivable to safe orbit. Landing burn reliability needed improvement.</td></tr>
|
||||
<tr><td>CERV-F3</td><td>Normal shutdown; attitude control anomaly; recovery aborted.</td><td>Normal shutdown and landing ignition, but center engine TVC failure. Booster tipped over and exploded after splashdown.</td><td>Attitude control and TVC system had potential single-point failure chains.</td></tr>
|
||||
<tr><td>CERV-F4</td><td colspan="2">New booster design with updated avionics; both sides achieved nominal splashdown.</td><td>Updated avionics and control systems resolved most failure modes from first three flights.</td></tr>
|
||||
<tr><td>CERV-F5</td><td colspan="2">Both boosters completed nominal shutdown, propulsive ignition, and landing; first fully successful booster recovery.</td><td>Full booster recovery sequence - ascent, separation, reentry, propulsive braking, and landing - achieved operational maturity.</td></tr>
|
||||
</tbody></table>
|
||||
<p>After CERV-F5, booster recovery entered routine operations. CERV-F12 marked the first launch of a previously recovered booster, closing the reusability loop. The 4-meter booster accumulated hundreds of flights of recovery data, providing the direct engineering foundation for Vulture's 5-meter boosters in thrust, structures, TPS, landing control, and reuse economics.</p>
|
||||
<table>
|
||||
<thead><tr><th>Parameter</th><th>CERV Liquid Booster</th><th>Vulture Liquid Booster (comparison)</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>Diameter</td><td>4 m</td><td>5 m</td></tr>
|
||||
<tr><td>Engines</td><td>9x TH-12 (enhanced), 1,132.67 kN vac each</td><td>9x TH-12 improved, identical performance, significantly improved maintainability</td></tr>
|
||||
<tr><td>Propellant</td><td>LOX / kerosene</td><td>LOX / kerosene</td></tr>
|
||||
<tr><td>Attitude control</td><td>LOX/kerosene bipropellant RCS</td><td>LOX/kerosene bipropellant RCS (inherited from CERV)</td></tr>
|
||||
<tr><td>Recovery</td><td>RTLS return-to-launch-site</td><td>RTLS return-to-launch-site or sea recovery ship</td></tr>
|
||||
<tr><td>Design life</td><td>50 flights (maintenance every 10)</td><td>75 maintenance-free; 200-300 with maintenance</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="propulsion-and-power">Propulsion and Power</h2>
|
||||
<h3 id="main-propulsion">Main Propulsion</h3>
|
||||
<p>CERV retained the STS main propulsion architecture: three RS-25D hydrolox staged-combustion engines mounted in the orbiter aft fuselage, fed by the 8.4 m external tank. RS-25D was a later RS-25 variant with approximately 1,860 kN sea-level thrust (single engine) and roughly 2,279 kN vacuum thrust. The engines operated continuously through ascent until main engine cutoff, after which the external tank separated and burned up on reentry. The engines lacked in-flight restart capability; all post-insertion maneuvers were performed by the orbital maneuvering system. In booster-engine-out scenarios, the orbiter could extend RS-25D burn duration to compensate, a capability first validated on CERV-F2.</p>
|
||||
<h3 id="orbital-maneuvering-system">Orbital Maneuvering System</h3>
|
||||
<p>The OMS consisted of two 60 kN storable-propellant engines in aft-mounted pods, using nitrogen tetroxide/monomethylhydrazine, for orbit circularization, maneuvering, phasing, deorbit, and abort modes. OMS propellant was shared with the crew escape engines via a common tank and feed line system.</p>
|
||||
<h3 id="escape-propulsion">Escape Propulsion</h3>
|
||||
<p>The escape system employed a two-stage configuration with thrust overlap. Upon activation, two solid-fuel boosters fired first to rapidly pull the cabin clear of the stack - used primarily below 100 km, especially during max-Q where instantaneous peak thrust was essential. Once the cabin reached 5 meters separation, four bipropellant storable engines ignited, operating simultaneously with the remaining solid motor burn for maximum total thrust. After solid burnout, the storable engines continued independently. The system covered all flight phases; above 100 km or during reentry, the solid phase could be skipped.</p>
|
||||
<h3 id="jet-engines">Jet Engines</h3>
|
||||
<p>Two aft-mounted turbofans on independent jet fuel provided landing-phase thrust, cross-range extension, and go-around capability. Normal sequence: jet engine start below 10,000 m, a circuit to dissipate energy, then ILS approach and landing. Backup mode: direct glide landing with VFR if jet engines failed to start. Go-around required afterburner engagement at maximum return mass.</p>
|
||||
<h3 id="power">Power</h3>
|
||||
<p>Two fuel cells using cryogenic hydrogen and oxygen provided electrical power, heat, and potable water. Batch 1 orbiters achieved 35-day fuel cell / 30-day life support endurance; Batch 2 upgraded fuel cell membrane-electrode assemblies extended free-flight endurance to 20 days; Batch 3 further increased power output for additional communications and EVA payloads. When docked to a station or orbital shipyard via the 1.875 m universal docking port, external power allowed the fuel cells to enter a low-power standby, extending docked endurance up to 120 days.</p>
|
||||
|
||||
<h2 id="crew-and-payload">Crew and Payload</h2>
|
||||
<p>Standard crew configuration was 8 persons, typically two pilots and up to six mission specialists. The orbiter was fully autonomous in all flight phases including landing and could execute complete missions uncrewed. The payload bay measured approximately 18.3 m long by 4.6 m in diameter, comparable to the STS bay. CERV delivered up to 30 tonnes to a 600x600 km x 51 deg orbit and returned up to 20 tonnes.</p>
|
||||
<table>
|
||||
<thead><tr><th>Item</th><th>Data</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>Crew capacity</td><td>8 (typically 2 pilots + 0-6 mission specialists)</td></tr>
|
||||
<tr><td>Upmass</td><td>30 t (600x600 km x 51 deg)</td></tr>
|
||||
<tr><td>Return mass</td><td>20 t</td></tr>
|
||||
<tr><td>Payload bay</td><td>~18.3 m x 4.6 m</td></tr>
|
||||
<tr><td>Free-flight endurance</td><td>35 days (fuel cells) / 30 days (life support)</td></tr>
|
||||
<tr><td>Docked endurance</td><td>Up to 120 days (on external power at station or orbital shipyard)</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="mission-profile">Mission Profile</h2>
|
||||
<h3 id="launch-and-ascent">Launch and Ascent</h3>
|
||||
<p>CERV launched vertically from Wenchang or Cape Canaveral. Both liquid boosters and three RS-25D main engines provided ascent thrust. Boosters throttled down approximately 30 seconds before propellant depletion, then separated, executed a boost-back burn, and performed controlled reentry and RTLS propulsive landing at the launch site. Early recovery tests (CERV-F1 through CERV-F5) were conducted in coastal waters to reduce risk to launch facilities; after CERV-F5's successful recovery, all operational missions used the onshore RTLS landing mode. Main engines continued to MECO, followed by ET separation. Booster single-engine-out scenarios were compensated by extending RS-25D burn duration.</p>
|
||||
<h3 id="on-orbit-operations">On-Orbit Operations</h3>
|
||||
<p>After OMS circularization and payload bay door opening for radiator and RMS exposure, the crew executed the mission plan. Standard missions lasted 7-12 days, with special missions extended to the full 30-day life support limit. When docked to a space station or orbital shipyard receiving external power, endurance extended to 120 days. The airlock supported EVA throughout the mission.</p>
|
||||
<h3 id="return-and-landing">Return and Landing</h3>
|
||||
<p>OMS deorbit burn initiated reentry. The improved universal tiles, underlying coating, and RCC leading edges managed aerodynamic heating, with the fly-by-wire system controlling angle of attack, bank, and sideslip. Below 10,000 m, jet engines were started. After a circuit to dissipate energy, the orbiter captured the ILS approach and landed autonomously. Primary landing sites were Cape Canaveral's Shuttle Landing Facility or Wenchang's spacecraft runway. Any CAT III-equipped civilian airport with runway exceeding 3,000 m could serve as an alternate. If jet engines failed, a direct glide VFR landing was executed with no go-around option.</p>
|
||||
<table>
|
||||
<thead><tr><th>Phase</th><th>Key Operations</th><th>Backup/Abort Options</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>Launch</td><td>Vertical liftoff from Wenchang or Cape Canaveral; liquid boosters + RS-25D.</td><td>All-phase crew escape; booster throttle/shutdown/abort.</td></tr>
|
||||
<tr><td>Booster separation</td><td>Boosters throttle, separate, execute boost-back burn, RTLS propulsive landing at launch site.</td><td>Extended RS-25D burn or abort if booster anomaly.</td></tr>
|
||||
<tr><td>Orbit insertion</td><td>MECO, ET separation, OMS circularization.</td><td>Backup OMS engine and backup orbit.</td></tr>
|
||||
<tr><td>On-orbit</td><td>Payload operations, rendezvous/docking (1.875 m port), EVA (airlock), 35-day fuel cell / 30-day life support or 120-day docked endurance.</td><td>Early deorbit or safe-orbit hold if anomaly.</td></tr>
|
||||
<tr><td>Reentry</td><td>OMS deorbit burn, TPS management (universal tiles + coating), AoA and bank control.</td><td>Conservative reentry profile if attitude or heating anomaly; coating provides redundant protection.</td></tr>
|
||||
<tr><td>Landing</td><td><10,000 m jet engine start, circuit, ILS autonomous landing. Primary: Cape SLF or Wenchang runway; alternate: any CAT III runway >3,000 m.</td><td>Direct glide VFR if jet engine fail; go-around with afterburner to short final or alternate.</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="fleet">Fleet</h2>
|
||||
<h3 id="test-vehicles">Test Vehicles</h3>
|
||||
<table>
|
||||
<thead><tr><th>Designation</th><th>Type</th><th>Purpose</th><th>Disposition</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>CTV-1</td><td>Structural test article</td><td>Static loads, structural connections, ET interface verification.</td><td>Stored after testing.</td></tr>
|
||||
<tr><td>CTV-2</td><td>Structural test article</td><td>Full-stack vibration, propellant loading, ground transport, and launch pad adaptation.</td><td>Stored after testing.</td></tr>
|
||||
<tr><td>CTV-3</td><td>Flight test article</td><td>Equipped with flight control system and jet engines for flight performance and FBW validation.</td><td>Converted to training vehicle.</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h3 id="orbiter-fleet">Orbiter Fleet</h3>
|
||||
<p>CERV built 8 orbiters across three production batches, accumulating 666 total flights between 2015 and 2040. The final mission, CERV-F666, was flown by <i>Discovery</i> on 15 June 2040.</p>
|
||||
|
||||
<h4>Batch 1 (Initial Production, First Flights 2015-2017)</h4>
|
||||
<p>The three Batch 1 orbiters represented the baseline CERV production configuration: composite airframe, quadruplex-redundant flight control computers, first-generation universal thermal tiles with insulation coating, 35-day fuel cell / 30-day life support endurance, and the initial version of the retractable docking port. This batch conducted all verification test flights and initial operational missions, providing critical design improvement feedback for subsequent batches.</p>
|
||||
<table>
|
||||
<thead><tr><th>Designation</th><th>Name</th><th>First Flight</th><th>Last Flight</th><th>Flights</th><th>Status</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>CERV-1</td><td><i>Horizon</i></td><td>June 2015</td><td>March 2037</td><td>110</td><td>Retired</td></tr>
|
||||
<tr><td>CERV-2</td><td><i>Pathfinder</i></td><td>November 2015</td><td>September 2037</td><td>105</td><td>Retired</td></tr>
|
||||
<tr><td>CERV-3</td><td><i>Pioneer</i></td><td>March 2017</td><td>May 2038</td><td>108</td><td>Retired</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h4>Batch 2 (Improved, First Flights 2020-2021)</h4>
|
||||
<p>The two Batch 2 orbiters incorporated upgrades from Batch 1 operational experience: enhanced flight control processors with adaptive control law switching; improved TPS coating formulation for better post-reentry integrity; upgraded life support extending free-flight endurance to 20 days; improved docking collar seals for extended docked life; and structural reinforcements at fatigue-critical locations identified on Batch 1 airframes. This batch marked CERV's transition from a verification-focused design to mature operational configuration.</p>
|
||||
<table>
|
||||
<thead><tr><th>Designation</th><th>Name</th><th>First Flight</th><th>Last Flight</th><th>Flights</th><th>Status</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>CERV-4</td><td><i>Voyager</i></td><td>May 2020</td><td>November 2038</td><td>88</td><td>Retired</td></tr>
|
||||
<tr><td>CERV-5</td><td><i>Spirit</i></td><td>February 2021</td><td>April 2039</td><td>82</td><td>Retired</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h4>Batch 3 (Enhanced, First Flights 2025-2026)</h4>
|
||||
<p>The three Batch 3 orbiters represented the definitive CERV configuration: next-generation integrated avionics platform; airlock volume increased by approximately 15%; upgraded external power interface supporting 120-day docked endurance; electrically actuated canard control surfaces; improved jet engine starter reducing cold-start time by approximately 25%; and adaptive parachute deployment logic for the escape system. This batch's improvements directly informed Vulture Shuttle avionics architecture and long-duration on-orbit capability.</p>
|
||||
<table>
|
||||
<thead><tr><th>Designation</th><th>Name</th><th>First Flight</th><th>Last Flight</th><th>Flights</th><th>Status</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>CERV-6</td><td><i>Hope</i></td><td>April 2025</td><td>October 2039</td><td>72</td><td>Retired</td></tr>
|
||||
<tr><td>CERV-7</td><td><i>Discovery</i></td><td>November 2025</td><td>15 June 2040</td><td>55</td><td>Retired; flew final mission CERV-F666</td></tr>
|
||||
<tr><td>CERV-8</td><td><i>Unity</i></td><td>June 2026</td><td>February 2040</td><td>46</td><td>Retired</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="operational-history">Operational History</h2>
|
||||
<h3 id="verification-phase">Verification Phase (2015-2016)</h3>
|
||||
<p>With only two Batch 1 orbiters available (<i>Horizon</i> and <i>Pathfinder</i>) and <i>Pioneer</i> still in assembly, the verification phase maintained a low flight rate. CERV-F1 through CERV-F5 focused on booster recovery, alternating between the two available orbiters. Booster recovery reached operational maturity at CERV-F5. CERV-F12 marked the first reused booster launch. Crew certification was completed in 2016.</p>
|
||||
<h3 id="operational-service">Operational Service (2017-2040)</h3>
|
||||
<p>With STS retired and <i>Pioneer</i> bringing Batch 1 to full strength in 2017, CERV assumed all crew and cargo missions, initially focused on ISS and Tiangong space station crew rotation and resupply. Batch 2 orbiters <i>Voyager</i> and <i>Spirit</i> joined in 2020-2021, expanding the active fleet to five. Batch 3 orbiters <i>Hope</i>, <i>Discovery</i>, and <i>Unity</i> entered service in 2025-2026, bringing the fleet to its full strength of eight and enabling the peak flight rates of 2026-2036. Frontier Station construction (2030-2035) and Lingxiao Palace construction (2033-2037) overlapped during 2033-2035, representing the most operationally intense period in CERV history. First-generation orbiters began retiring in 2037, and after Vulture's first uncrewed orbital flight in 2037 (entering service in 2039), CERV began a phased handover, concluding with <i>Discovery</i>'s final mission CERV-F666 on 15 June 2040.</p>
|
||||
|
||||
<h3 id="lifetime-flight-statistics">Lifetime Flight Statistics</h3>
|
||||
<div class="launch-chart" role="img" aria-label="CERV Shuttle annual flight count (2015-2040)">
|
||||
<div class="launch-row launch-head"><span>Year</span><span>Flights</span><span>Count</span><span>Cum.</span></div>
|
||||
<div class="launch-stage-label">Verification (2 orbiters)</div>
|
||||
<div class="launch-row"><span>2015</span><span class="launch-track"><span class="launch-bar" style="width:5%;"></span></span><span class="launch-count">2</span><span class="launch-cumulative">2</span></div>
|
||||
<div class="launch-row"><span>2016</span><span class="launch-track"><span class="launch-bar" style="width:12%;"></span></span><span class="launch-count">5</span><span class="launch-cumulative">7</span></div>
|
||||
<div class="launch-stage-label">Batch 1 operations (3 orbiters)</div>
|
||||
<div class="launch-row"><span>2017</span><span class="launch-track"><span class="launch-bar" style="width:19%;"></span></span><span class="launch-count">8</span><span class="launch-cumulative">15</span></div>
|
||||
<div class="launch-row"><span>2018</span><span class="launch-track"><span class="launch-bar" style="width:26%;"></span></span><span class="launch-count">11</span><span class="launch-cumulative">26</span></div>
|
||||
<div class="launch-row"><span>2019</span><span class="launch-track"><span class="launch-bar" style="width:33%;"></span></span><span class="launch-count">14</span><span class="launch-cumulative">40</span></div>
|
||||
<div class="launch-stage-label">Batch 2 joins (5 orbiters)</div>
|
||||
<div class="launch-row"><span>2020</span><span class="launch-track"><span class="launch-bar" style="width:45%;"></span></span><span class="launch-count">19</span><span class="launch-cumulative">59</span></div>
|
||||
<div class="launch-row"><span>2021</span><span class="launch-track"><span class="launch-bar" style="width:55%;"></span></span><span class="launch-count">23</span><span class="launch-cumulative">82</span></div>
|
||||
<div class="launch-row"><span>2022</span><span class="launch-track"><span class="launch-bar" style="width:62%;"></span></span><span class="launch-count">26</span><span class="launch-cumulative">108</span></div>
|
||||
<div class="launch-row"><span>2023</span><span class="launch-track"><span class="launch-bar" style="width:67%;"></span></span><span class="launch-count">28</span><span class="launch-cumulative">136</span></div>
|
||||
<div class="launch-row"><span>2024</span><span class="launch-track"><span class="launch-bar" style="width:71%;"></span></span><span class="launch-count">30</span><span class="launch-cumulative">166</span></div>
|
||||
<div class="launch-stage-label">Batch 3 joins, full fleet (8 orbiters)</div>
|
||||
<div class="launch-row"><span>2025</span><span class="launch-track"><span class="launch-bar" style="width:79%;"></span></span><span class="launch-count">33</span><span class="launch-cumulative">199</span></div>
|
||||
<div class="launch-row"><span>2026</span><span class="launch-track"><span class="launch-bar" style="width:88%;"></span></span><span class="launch-count">37</span><span class="launch-cumulative">236</span></div>
|
||||
<div class="launch-row"><span>2027</span><span class="launch-track"><span class="launch-bar" style="width:93%;"></span></span><span class="launch-count">39</span><span class="launch-cumulative">275</span></div>
|
||||
<div class="launch-row"><span>2028</span><span class="launch-track"><span class="launch-bar" style="width:98%;"></span></span><span class="launch-count">41</span><span class="launch-cumulative">316</span></div>
|
||||
<div class="launch-row"><span>2029</span><span class="launch-track"><span class="launch-bar" style="width:90%;"></span></span><span class="launch-count">38</span><span class="launch-cumulative">354</span></div>
|
||||
<div class="launch-row"><span>2030</span><span class="launch-track"><span class="launch-bar" style="width:100%;"></span></span><span class="launch-count">42</span><span class="launch-cumulative">396</span></div>
|
||||
<div class="launch-row"><span>2031</span><span class="launch-track"><span class="launch-bar" style="width:95%;"></span></span><span class="launch-count">40</span><span class="launch-cumulative">436</span></div>
|
||||
<div class="launch-row"><span>2032</span><span class="launch-track"><span class="launch-bar" style="width:86%;"></span></span><span class="launch-count">36</span><span class="launch-cumulative">472</span></div>
|
||||
<div class="launch-row"><span>2033</span><span class="launch-track"><span class="launch-bar" style="width:86%;"></span></span><span class="launch-count">36</span><span class="launch-cumulative">508</span></div>
|
||||
<div class="launch-row"><span>2034</span><span class="launch-track"><span class="launch-bar" style="width:81%;"></span></span><span class="launch-count">34</span><span class="launch-cumulative">542</span></div>
|
||||
<div class="launch-row"><span>2035</span><span class="launch-track"><span class="launch-bar" style="width:71%;"></span></span><span class="launch-count">30</span><span class="launch-cumulative">572</span></div>
|
||||
<div class="launch-row"><span>2036</span><span class="launch-track"><span class="launch-bar" style="width:71%;"></span></span><span class="launch-count">30</span><span class="launch-cumulative">602</span></div>
|
||||
<div class="launch-stage-label">Batch 1 retirement, handover (6→4 orbiters)</div>
|
||||
<div class="launch-row"><span>2037</span><span class="launch-track"><span class="launch-bar" style="width:52%;"></span></span><span class="launch-count">22</span><span class="launch-cumulative">624</span></div>
|
||||
<div class="launch-row"><span>2038</span><span class="launch-track"><span class="launch-bar" style="width:45%;"></span></span><span class="launch-count">19</span><span class="launch-cumulative">643</span></div>
|
||||
<div class="launch-row"><span>2039</span><span class="launch-track"><span class="launch-bar" style="width:36%;"></span></span><span class="launch-count">15</span><span class="launch-cumulative">658</span></div>
|
||||
<div class="launch-row"><span>2040</span><span class="launch-track"><span class="launch-bar highlight" style="width:19%;"></span></span><span class="launch-count">8</span><span class="launch-cumulative"><b>666</b></span></div>
|
||||
</div>
|
||||
<p style="font-size:90%; color:#54595d;">Red bar: 2040, <i>Discovery</i> flew the final mission CERV-F666. Verification phase limited to 2 orbiters with low flight rate. Peak rate of 42 flights in 2030 during full-fleet operations.</p>
|
||||
|
||||
<h2 id="notable-missions-and-payloads">Notable Missions and Payloads</h2>
|
||||
<h3 id="space-station-construction">Space Station Construction and Operations</h3>
|
||||
<p>Before CERV-era stations were built, CERV served ISS and Tiangong space stations for crew rotation and resupply, accumulating extensive docking and long-duration berthed operational experience. Frontier Station construction began in 2030 and concluded in 2035. Adopting a modular truss architecture, Frontier Station relied on CERV for delivery of core truss segments, solar array wings, radiators, node modules, and pressurized experiment modules, with over 50 construction flights. Lingxiao Palace construction ran from 2033 to 2037; CERV delivered core modules, experiment modules, solar arrays, and external experiment platforms. The two stations' construction overlapped during 2033-2035, with CERV's eight orbiters simultaneously supporting parallel assembly - one of the most operationally intense periods in the program's history.</p>
|
||||
<h3 id="space-tourism">Space Tourism</h3>
|
||||
<p>CERV's commercial crew program began in 2024 with the first all-commercial crewed mission to ISS. Before Frontier Station and Lingxiao Palace were completed, commercial missions primarily visited ISS, Tiangong, or conducted free-flight orbital experiences. CERV typically flew 1-2 commercial missions per year. In 2030, CERV executed its first fully autonomous commercial orbital flight requiring no pilot manual intervention, further reducing operational costs. After Frontier Station and Lingxiao Palace became operational, they were added to the commercial destination roster. CERV carried over 100 space tourists over its career.</p>
|
||||
<h3 id="deep-space-mission-support">Deep Space Mission Support</h3>
|
||||
<p>CERV's primary deep-space role was as a launch platform for probe-plus-upper-stage combinations. Over its lifetime, CERV launched 25 Mars missions (including the 2022 Mars Sample Return orbiter/lander and 2028 Mars Global High-Resolution Mapping constellation), 77 lunar missions, 18 Venus missions, and 42 outer solar system missions. CERV's payload bay volume and return capability provided a unique advantage: crews could inspect, debug, and when necessary manually intervene on probes before deployment, and could return malfunctioning payloads to Earth for analysis and repair.</p>
|
||||
<h3 id="on-orbit-servicing">On-Orbit Servicing</h3>
|
||||
<p>In 2032, CERV recovered the Hubble Space Telescope after irreparable failures in its attitude control system and science instrument power module. <i>Pioneer</i> rendezvoused with Hubble, and the crew secured the telescope in the payload bay via EVA before returning to Cape Canaveral. The recovered Hubble, after restoration, was placed on display at the Smithsonian National Air and Space Museum. CERV also deployed the Survey Telescope (Xuntian) to Sun-Earth L2 transfer orbit in 2030 and conducted multiple servicing missions thereafter.</p>
|
||||
<h3 id="deep-space-network-20">Deep Space Network 2.0</h3>
|
||||
<p>CERV deployed the Queqiao relay satellite network to lunar orbit (6 satellites across 3 missions, 2026-2028) and the Firefly relay satellite network to Mars orbit (8 satellites across 4 missions, completed 2033). For both networks, CERV's ability to perform final satellite checkout in the payload bay before deployment, and to conduct close-range inspection and repair of anomalous satellites post-deployment, made it a unique asset for large-scale communications infrastructure projects.</p>
|
||||
|
||||
<h2 id="relationship-to-sts-and-vulture">Relationship to STS and Vulture</h2>
|
||||
<p>As the second-generation shuttle, CERV inherited the operational architecture and mission systems of the first-generation STS while providing the engineering foundation in liquid boosters, crew escape, and aerodynamic configuration for the third-generation Vulture Shuttle. CERV's three-batch incremental improvement approach provided a complete engineering model for shuttle iterative development and batch management that directly informed Vulture program planning. After CERV's retirement, the shuttle lineage continued to evolve: the Echo Shuttle (first flight 2056, operational 2057) and Enterprise Shuttle (first flight 2057, operational 2058) joined as fourth-generation SSTO-capable vehicles, operating alongside Vulture Block 2 in the late 2050s.</p>
|
||||
<table>
|
||||
<thead><tr><th>Gen.</th><th>Type</th><th>Role</th><th>Key Technology Contributions</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>1st</td><td>STS Space Shuttle</td><td>Established vertical launch / horizontal landing paradigm and ground operations.</td><td>Orbiter+ET+booster architecture, RS-25 engines, TPS, on-orbit operations.</td></tr>
|
||||
<tr><td>2nd</td><td>CERV Shuttle</td><td>Safety-enhanced, closed crew escape and landing flexibility gaps. Three production batches.</td><td>Composite mass reduction, liquid booster recovery (50 flights/10 maintenance), all-phase crew escape, twin wingtip stabilizers + canards, fly-by-wire autonomous landing, jet engine landing assist and go-around, universal tiles + coating, ET coating + foam dual-layer insulation, LOX/kerosene bipropellant RCS, airlock and retractable universal docking port.</td></tr>
|
||||
<tr><td>3rd</td><td>Vulture Shuttle</td><td>Heavy-lift, scaled architecture for mothership construction and high-orbit heavy transport.</td><td>Inherited and scaled CERV's full technology suite; MK4 orbiter, 10 m ET, 5 m boosters (75 maintenance-free / 200-300 total).</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="specifications">Specifications</h2>
|
||||
<table>
|
||||
<thead><tr><th>Item</th><th>Data</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>Full name</td><td>Composite Enhanced Reusable Vehicle</td></tr>
|
||||
<tr><td>Type</td><td>Reusable crewed space shuttle (2nd generation)</td></tr>
|
||||
<tr><td>Predecessor</td><td>STS Space Shuttle (1st generation)</td></tr>
|
||||
<tr><td>Successor</td><td>Vulture Shuttle (3rd generation)</td></tr>
|
||||
<tr><td>Maiden flight</td><td>June 2015 (CERV-F1, <i>Horizon</i>)</td></tr>
|
||||
<tr><td>Final flight</td><td>15 June 2040 (CERV-F666, <i>Discovery</i>)</td></tr>
|
||||
<tr><td>Total flights</td><td>666</td></tr>
|
||||
<tr><td>Launch sites</td><td>Wenchang Space Launch Site / Cape Canaveral</td></tr>
|
||||
<tr><td>Primary landing sites</td><td>Cape Canaveral SLF / Wenchang Spacecraft Landing Runway; any CAT III runway >3,000 m as alternate</td></tr>
|
||||
<tr><th colspan="2">Orbiter</th></tr>
|
||||
<tr><td>Airframe</td><td>Aluminum-composite hybrid structure</td></tr>
|
||||
<tr><td>Dry mass</td><td>63 t</td></tr>
|
||||
<tr><td>Length</td><td>Orbiter 36 m / Full stack 55.4 m</td></tr>
|
||||
<tr><td>Wingspan</td><td>24.3 m</td></tr>
|
||||
<tr><td>Max takeoff weight</td><td>2,169.9 t (with 30 t payload)</td></tr>
|
||||
<tr><td>Configuration</td><td>Swept delta wing, twin wingtip stabilizers, forward canards</td></tr>
|
||||
<tr><td>Thermal protection</td><td>Improved universal tiles + insulation coating; RCC at wing leading edges and nose</td></tr>
|
||||
<tr><td>Flight control</td><td>Fly-by-wire, redundant architecture, fully autonomous all phases including landing</td></tr>
|
||||
<tr><td>Jet engines</td><td>2x turbofan, landing assist/go-around; afterburner required for go-around</td></tr>
|
||||
<tr><td>Docking port</td><td>Retractable 1.875 m universal port</td></tr>
|
||||
<tr><td>EVA</td><td>Built-in airlock</td></tr>
|
||||
<tr><th colspan="2">Propulsion</th></tr>
|
||||
<tr><td>Main engines</td><td>3x RS-25D hydrolox staged combustion</td></tr>
|
||||
<tr><td>External tank</td><td>8.4 m dia.; insulation coating + foam dual-layer; propellant 955.3 t; dry mass 28.5 t</td></tr>
|
||||
<tr><td>Boosters</td><td>2x 4 m dia. liquid boosters, 9x TH-12 (enhanced) each, 1,132.67 kN vac; dry mass 24.5 t each, propellant 497.8 t each; RTLS return-to-launch-site; 50-flight life, maintenance every 10 flights</td></tr>
|
||||
<tr><td>OMS propellant</td><td>23.44 t</td></tr>
|
||||
<tr><td>Jet fuel</td><td>6 t</td></tr>
|
||||
<tr><td>Booster RCS</td><td>LOX/kerosene bipropellant</td></tr>
|
||||
<tr><td>OMS</td><td>2x 60 kN storable-propellant engines, propellant shared with escape engines</td></tr>
|
||||
<tr><td>Escape propulsion</td><td>2x solid boosters (ground-100 km initial sep.) + 4x bipropellant storable engines (ignite at 5 m cabin separation); all-phase (pad/flight/reentry)</td></tr>
|
||||
<tr><th colspan="2">Crew and Payload</th></tr>
|
||||
<tr><td>Crew</td><td>8 (2 pilots + 0-6 mission specialists)</td></tr>
|
||||
<tr><td>Flight capability</td><td>Fully autonomous all phases including landing</td></tr>
|
||||
<tr><td>Upmass</td><td>30 t (600x600 km x 51 deg)</td></tr>
|
||||
<tr><td>Return mass</td><td>20 t</td></tr>
|
||||
<tr><td>Payload bay</td><td>~18.3 m x 4.6 m</td></tr>
|
||||
<tr><th colspan="2">Power and Endurance</th></tr>
|
||||
<tr><td>Power</td><td>2x fuel cells, 35-day free-flight capability</td></tr>
|
||||
<tr><td>Life support</td><td>30 days free-flight; up to 120 days docked (external power via station / orbital shipyard)</td></tr>
|
||||
<tr><td>External power</td><td>Via 1.875 m universal docking port</td></tr>
|
||||
<tr><th colspan="2">Fleet</th></tr>
|
||||
<tr><td>Orbiters</td><td>8, in 3 batches (Batch 1: 3 / Batch 2: 2 / Batch 3: 3)</td></tr>
|
||||
<tr><td>Test vehicles</td><td>3 (CTV-1, CTV-2, CTV-3)</td></tr>
|
||||
<tr><td>Total flights</td><td>666</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="assessment">Assessment</h2>
|
||||
<p>The CERV Shuttle was the pivotal transitional type within the shuttle lineage, bridging the first-generation STS and third-generation Vulture. Driven by the <i>Columbia</i> safety lessons, it systematically resolved ascent crew escape, non-recoverable boosters, structural weight, TPS maintenance cost, and landing flexibility shortfalls while preserving the STS mission paradigm. Its key engineering legacies include the first integrated crew cabin all-phase escape on a crewed shuttle, the first operational liquid-fuel recoverable booster system, approximately 19% orbiter dry mass reduction through composites, the twin-stabilizer-plus-canard configuration with autonomous landing and go-around, and the dual-layer TPS and ET insulation systems. Operationally, CERV demonstrated the broad applicability of reusable shuttles across space station construction, commercial crew transport, deep-space mission launch, on-orbit servicing and recovery, and communications infrastructure deployment.</p>
|
||||
<p>CERV's limitations were equally clear: 30-tonne upmass and 20-tonne return mass remained STS-class; the 8.4 m ET and RS-25D architecture constrained further scaling; booster life of 50 flights at 10-flight maintenance intervals was operationally viable but too costly for next-generation high-cadence reuse. In the shuttle lineage, CERV completed the core engineering transition from the "expendable solid booster + no-escape orbiter" first-generation model to the "reusable liquid booster + all-phase crew escape orbiter" third-generation model, safely bridging the lineage from the STS era to the Vulture era.</p>
|
||||
|
||||
<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/Vulture_Shuttle_Block_2">Vulture Shuttle Block 2</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><a href="/home/Exploration_Motherships/Xihe">Xihe-class Exploration Mothership</a></li>
|
||||
<li><a href="/home/Exploration_Motherships/Stellaria">Stellaria-class Exploration Mothership</a></li>
|
||||
<li>Lingxiao Palace Space Station</li>
|
||||
<li>Qiming (Frontier) Space Station</li>
|
||||
<li>Xuntian Survey Telescope</li>
|
||||
<li>Hubble Space Telescope</li>
|
||||
<li>STS Space Shuttle</li>
|
||||
<li>RS-25 engine</li>
|
||||
<li>TH-12 engine</li>
|
||||
</ul>
|
||||
</article>
|
||||
<script>
|
||||
(function () {
|
||||
function ready(fn) {
|
||||
if (document.readyState === 'loading') {
|
||||
document.addEventListener('DOMContentLoaded', fn, { once: true });
|
||||
} else {
|
||||
fn();
|
||||
}
|
||||
}
|
||||
|
||||
function captionFor(image) {
|
||||
var container = image.closest('figure, td, tr, .infobox-image');
|
||||
if (!container) {
|
||||
return image.alt || '';
|
||||
}
|
||||
var caption = container.querySelector('.thumbcaption');
|
||||
return caption ? caption.textContent.trim() : (image.alt || '');
|
||||
}
|
||||
|
||||
function install(article) {
|
||||
if (!article || article.dataset.lightboxReady === '1') {
|
||||
return;
|
||||
}
|
||||
article.dataset.lightboxReady = '1';
|
||||
|
||||
var overlay = document.createElement('div');
|
||||
overlay.className = 'wiki-image-lightbox';
|
||||
overlay.hidden = true;
|
||||
overlay.innerHTML = '<figure class="wiki-image-lightbox-panel" role="dialog" aria-modal="true"><button class="wiki-image-lightbox-close" type="button" aria-label="Close image preview">x</button><img alt=""><figcaption class="thumbcaption"></figcaption></figure>';
|
||||
document.body.appendChild(overlay);
|
||||
|
||||
var previewImage = overlay.querySelector('img');
|
||||
var previewCaption = overlay.querySelector('figcaption');
|
||||
var closeButton = overlay.querySelector('.wiki-image-lightbox-close');
|
||||
|
||||
function closePreview() {
|
||||
overlay.hidden = true;
|
||||
previewImage.removeAttribute('src');
|
||||
previewCaption.textContent = '';
|
||||
document.body.classList.remove('wiki-image-lightbox-open');
|
||||
}
|
||||
|
||||
function openPreview(image, event) {
|
||||
event.preventDefault();
|
||||
event.stopPropagation();
|
||||
if (event.stopImmediatePropagation) {
|
||||
event.stopImmediatePropagation();
|
||||
}
|
||||
previewImage.src = image.currentSrc || image.src;
|
||||
previewImage.alt = image.alt || '';
|
||||
previewCaption.textContent = captionFor(image);
|
||||
overlay.hidden = false;
|
||||
document.body.classList.add('wiki-image-lightbox-open');
|
||||
closeButton.focus();
|
||||
}
|
||||
|
||||
Array.prototype.forEach.call(article.querySelectorAll('img[data-wiki-asset]'), function (image) {
|
||||
if (image.dataset.lightboxBound === '1') { return; }
|
||||
image.dataset.lightboxBound = '1';
|
||||
image.addEventListener('click', function (event) { openPreview(image, event); }, true);
|
||||
});
|
||||
|
||||
article.addEventListener('click', function (event) {
|
||||
var image = event.target.closest && event.target.closest('img[data-wiki-asset]');
|
||||
if (!image || !article.contains(image) || image.closest('.wiki-image-lightbox')) { return; }
|
||||
openPreview(image, event);
|
||||
});
|
||||
|
||||
closeButton.addEventListener('click', closePreview);
|
||||
overlay.addEventListener('click', function (event) { if (event.target === overlay) closePreview(); });
|
||||
document.addEventListener('keydown', function (event) { if (event.key === 'Escape' && !overlay.hidden) closePreview(); });
|
||||
}
|
||||
|
||||
function installAll() {
|
||||
Array.prototype.forEach.call(document.querySelectorAll('.wiki-article, .vulture-article'), install);
|
||||
}
|
||||
|
||||
ready(function () {
|
||||
installAll();
|
||||
if (window.MutationObserver) {
|
||||
var observer = new MutationObserver(installAll);
|
||||
observer.observe(document.body, { childList: true, subtree: true });
|
||||
}
|
||||
window.setTimeout(installAll, 500);
|
||||
window.setTimeout(installAll, 1500);
|
||||
window.setTimeout(installAll, 3000);
|
||||
});
|
||||
}());
|
||||
</script>
|
||||
@@ -0,0 +1,573 @@
|
||||
<style>
|
||||
.wiki-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; }
|
||||
.wiki-article h1, .wiki-article h2 { font-family: "Linux Libertine", Georgia, "Times New Roman", serif; font-weight: normal; border-bottom: 1px solid #a2a9b1; }
|
||||
.wiki-article h1 { margin: 0 0 8px; font-size: 2.15em; line-height: 1.25; }
|
||||
.wiki-article h2 { clear: both; margin: 1.35em 0 0.6em; padding-bottom: 0.18em; font-size: 1.55em; }
|
||||
.wiki-article h3 { margin: 1.05em 0 0.35em; font-size: 1.18em; font-weight: bold; }
|
||||
.wiki-article h4 { margin: 0.9em 0 0.25em; font-size: 1.02em; font-weight: bold; }
|
||||
.wiki-article p { margin: 0.45em 0 0.85em; }
|
||||
.wiki-article a { color: #0645ad; text-decoration: none; }
|
||||
.wiki-article a:hover { text-decoration: underline; }
|
||||
.wiki-article ul, .wiki-article ol { margin: 0.35em 0 0.9em 1.65em; padding: 0; }
|
||||
.wiki-article li { margin-bottom: 0.18em; }
|
||||
.wiki-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; }
|
||||
.wiki-article .infobox caption { padding: 8px; background: #eaecf0; border: 1px solid #a2a9b1; border-bottom: 0; font-weight: bold; font-size: 1.12em; }
|
||||
.wiki-article .infobox caption span { display: block; font-size: 0.92em; font-weight: normal; }
|
||||
.wiki-article .infobox td { border: 1px solid #a2a9b1; padding: 6px 8px; vertical-align: top; }
|
||||
.wiki-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; }
|
||||
.wiki-article .infobox .image-placeholder { min-height: 185px; }
|
||||
.wiki-article img { max-width: 100%; height: auto; }
|
||||
.wiki-article .media-link img { display: block; width: 100%; cursor: zoom-in; }
|
||||
.wiki-article .wiki-modal-card img { display: block; width: 100%; }
|
||||
.wiki-article .media-link { display: block; color: inherit; text-decoration: none; }
|
||||
.wiki-article .media-link:hover { text-decoration: none; }
|
||||
.wiki-article .media-link:hover .image-placeholder { border-color: #36c; background: #f8f9fa; color: #202122; }
|
||||
.wiki-article .thumb { width: 265px; border: 1px solid #c8ccd1; background: #f8f9fa; padding: 3px; font-size: 88%; line-height: 1.4; box-sizing: border-box; }
|
||||
.wiki-article .tright { float: right; clear: right; margin: 0.35em 0 1em 1.4em; }
|
||||
.wiki-article .tleft { float: left; clear: left; margin: 0.35em 1.4em 1em 0; }
|
||||
.wiki-article .thumbcaption { padding: 4px 3px 2px; text-align: left; color: #202122; }
|
||||
.wiki-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%; }
|
||||
.wiki-article .toc-title { text-align: center; font-weight: bold; margin-bottom: 4px; }
|
||||
.wiki-article .toc ol { margin: 0 0 0 1.5em; }
|
||||
.wiki-article > table:not(.infobox) { width: 100%; margin: 1em 0; border-collapse: collapse; font-size: 92%; background: #fff; }
|
||||
.wiki-article > table:not(.infobox) th, .wiki-article > table:not(.infobox) td { border: 1px solid #a2a9b1; padding: 6px 8px; text-align: left; vertical-align: top; }
|
||||
.wiki-article > table:not(.infobox) th { background: #eaecf0; font-weight: bold; }
|
||||
.wiki-article > table:not(.infobox) tr:nth-child(even) td { background: #f8f9fa; }
|
||||
.wiki-article .launch-chart { margin: 1em 0; padding: 8px 10px 10px; border: 1px solid #a2a9b1; background: #f8f9fa; font-size: 92%; }
|
||||
.wiki-article .launch-stage-label { margin: 8px 0 4px; padding-bottom: 2px; border-bottom: 1px solid #c8ccd1; font-weight: bold; }
|
||||
.wiki-article .launch-row { display: grid; grid-template-columns: 54px 1fr 42px 62px; gap: 8px; align-items: center; margin: 3px 0; }
|
||||
.wiki-article .launch-head { color: #54595d; font-weight: bold; }
|
||||
.wiki-article .launch-track { height: 14px; border: 1px solid #c8ccd1; background: #eaecf0; box-sizing: border-box; }
|
||||
.wiki-article .launch-bar { display: block; height: 100%; background: #36c; }
|
||||
.wiki-article .launch-bar.highlight { background: #d33; }
|
||||
.wiki-article .launch-count, .wiki-article .launch-cumulative { text-align: right; white-space: nowrap; }
|
||||
.wiki-article .launch-cumulative { color: #54595d; }
|
||||
.wiki-article .wiki-modal { position: fixed; inset: 0; display: none; align-items: center; justify-content: center; padding: 24px; background: rgba(32,33,34,0.82); z-index: 9999; box-sizing: border-box; }
|
||||
.wiki-article .wiki-modal:target { display: flex; }
|
||||
.wiki-article .wiki-modal-card { width: min(920px, 96vw); max-height: 90vh; overflow: auto; border: 1px solid #a2a9b1; background: #fff; padding: 10px; box-shadow: 0 12px 38px rgba(0,0,0,0.35); box-sizing: border-box; }
|
||||
.wiki-article .wiki-modal-card .image-placeholder { min-height: 420px; font-size: 1.22em; }
|
||||
.wiki-article .modal-close { float: right; width: 28px; height: 28px; margin: -2px -2px 6px 8px; border: 1px solid #a2a9b1; background: #eaecf0; color: #202122; text-align: center; line-height: 26px; font-weight: bold; }
|
||||
.wiki-article .modal-close:hover { background: #fff; text-decoration: none; }
|
||||
@media (max-width: 820px) { .wiki-article { padding: 18px 16px 36px; } .wiki-article .infobox, .wiki-article .thumb { float: none; width: 100%; margin: 0.75em 0 1em; } .wiki-article .toc { display: block; } .wiki-article .launch-row { grid-template-columns: 46px 1fr 36px; } .wiki-article .launch-cumulative { display: none; } .wiki-article .wiki-modal { padding: 12px; } .wiki-article .wiki-modal-card .image-placeholder { min-height: 280px; } }
|
||||
|
||||
.wiki-article img[data-wiki-asset], .vulture-article img[data-wiki-asset] { cursor: zoom-in; }
|
||||
.wiki-image-lightbox { position: fixed; inset: 0; display: flex; align-items: center; justify-content: center; padding: 24px; background: rgba(32,33,34,0.84); z-index: 10000; box-sizing: border-box; }
|
||||
.wiki-image-lightbox[hidden] { display: none; }
|
||||
.wiki-image-lightbox-panel { position: relative; width: min(1120px, 96vw); max-height: 92vh; overflow: auto; margin: 0; padding: 10px; border: 1px solid #a2a9b1; background: #fff; box-shadow: 0 12px 38px rgba(0,0,0,0.35); box-sizing: border-box; }
|
||||
.wiki-image-lightbox-panel img { display: block; width: 100%; height: auto; max-height: 82vh; object-fit: contain; background: #000; }
|
||||
.wiki-image-lightbox-close { position: sticky; top: 0; float: right; width: 30px; height: 30px; margin: -2px -2px 8px 10px; border: 1px solid #a2a9b1; background: #eaecf0; color: #202122; font-weight: bold; line-height: 26px; cursor: pointer; }
|
||||
.wiki-image-lightbox-close:hover, .wiki-image-lightbox-close:focus { background: #fff; }
|
||||
body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
@media (max-width: 820px) { .wiki-image-lightbox { padding: 12px; } .wiki-image-lightbox-panel { width: 98vw; max-height: 94vh; } }
|
||||
</style>
|
||||
<article class="mw-parser-output wiki-article">
|
||||
<h1 id="cerv-航天飞机cerv-shuttle">CERV 航天飞机（CERV Shuttle）</h1>
|
||||
<table class="infobox">
|
||||
<caption>CERV 航天飞机<span>Composite Enhanced Reusable Vehicle</span></caption>
|
||||
<tbody>
|
||||
<tr><td><a class="media-link" href="#cerv-img-launch"><img src="/cerv/cerv_launch_pad.png" alt="CERV 航天飞机全栈发射" data-wiki-asset="/cerv/cerv_launch_pad.png"></a><div class="thumbcaption">CERV 采用轨道器、8.4 米外挂燃料箱和两枚 4 米液体燃料助推器的三段式发射布局，乘员舱具备整体逃逸能力。</div></td></tr>
|
||||
<tr><td><b>全称</b>：Composite Enhanced Reusable Vehicle</td></tr>
|
||||
<tr><td><b>中文译名</b>：复合增强可重复使用运载器</td></tr>
|
||||
<tr><td><b>类型</b>：可重复使用载人航天飞机</td></tr>
|
||||
<tr><td><b>世代</b>：第二代航天飞机</td></tr>
|
||||
<tr><td><b>前身</b>：STS 航天飞机（第一代）</td></tr>
|
||||
<tr><td><b>后继</b>：秃鹫航天飞机（第三代）</td></tr>
|
||||
<tr><td><b>研发阶段</b>：2005 年 - 2015 年</td></tr>
|
||||
<tr><td><b>首飞</b>：2015 年 6 月（CERV-F1，地平线号执飞）</td></tr>
|
||||
<tr><td><b>服役阶段</b>：2017 年 - 2040 年</td></tr>
|
||||
<tr><td><b>末飞</b>：2040 年 6 月 15 日（CERV-F666，发现号执飞）</td></tr>
|
||||
<tr><td><b>发射场</b>：文昌航天发射场 / 卡纳维拉尔角</td></tr>
|
||||
<tr><td><b>主要着陆场</b>：卡纳维拉尔角 Shuttle Landing Facility / 文昌航天器着陆跑道</td></tr>
|
||||
<tr><td><b>构型</b>：垂直发射 / 水平着陆</td></tr>
|
||||
<tr><td><b>轨道器机身</b>：铝合金—复合材料混合结构</td></tr>
|
||||
<tr><td><b>轨道器干重</b>：63 吨</td></tr>
|
||||
<tr><td><b>最大起飞重量</b>：2,169.9 吨（含 30 吨载荷）</td></tr>
|
||||
<tr><td><b>全长</b>：轨道器 36 米 / 组合体 55.4 米</td></tr>
|
||||
<tr><td><b>翼展</b>：24.3 米</td></tr>
|
||||
<tr><td><b>载荷能力</b>：30 吨（上行）/ 20 吨（返回）</td></tr>
|
||||
<tr><td><b>乘员能力</b>：8 人（常规 2 名飞行员 + 0-6 名任务人员）</td></tr>
|
||||
<tr><td><b>运行状态</b>：已退役（2040 年）</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<p>本文描述的是架空时间线中的内容。在该时间线中，<b>CERV 航天飞机</b>（全称 <b>Composite Enhanced Reusable Vehicle</b>，中文译名"<b>复合增强可重复使用运载器</b>"，简称 <b>CERV</b>）是继 STS 航天飞机之后开发的第二代载人航天飞机。该型号继承 STS 的轨道器、8.4 米外挂燃料箱和三台 RS-25D 主发动机构型，于 2005 年启动研发，2015 年 6 月由地平线号执飞首飞任务 CERV-F1，2017 年正式接替退役的 STS 承担载人和货运任务，于 2040 年由第三代秃鹫航天飞机接替退役，末飞任务 CERV-F666 于 2040 年 6 月 15 日由发现号执飞。</p>
|
||||
<p>CERV 在继承 STS 基础构型的同时进行了四项根本性改进：大量采用复合材料实现结构减重，使轨道器干重降至 63 吨；首次引入整体式乘员舱逃逸系统；将固体助推器更换为可RTLS 返场着陆的液体燃料助推器；将气动布局从单片中央垂尾改为双翼尖垂尾加前置鸭翼。此外，CERV 还配备了两台喷气发动机以支持着陆辅助、横向航程扩展和复飞能力，是首款具备着陆复飞能力的载人航天飞机。</p>
|
||||
<p>CERV 支持从文昌航天发射场和卡纳维拉尔角发射，最多可将 30 吨载荷送入 600×600 km × 51° 轨道，并能携带 20 吨载荷进行再入返回。轨道器采用电传飞控设计，具备全阶段全自动飞行能力（含着陆）。在轨燃料电池可支持 35 天自由飞行，生命维持系统支持 30 天，驻留空间站或轨道船坞时通过外部供电最长可达 120 天。CERV 的液体助推器设计、乘员舱逃逸方案、翼型布局和热防护体系为后继秃鹫航天飞机提供了直接的工程基础。</p>
|
||||
<p>在航天飞机体系中，CERV 定位为"安全改进型航天飞机"。该级并不追求 STS 之后的全面性能跃升，而是以哥伦比亚事故教训为核心驱动力，系统性地解决上升段乘员安全、结构老化、助推器不可回收和着陆灵活性不足等问题。退役后，其液体助推器技术、整体式逃逸理念、复合材料应用和改进型热防护体系被秃鹫航天飞机继承和发展。</p>
|
||||
|
||||
<nav class="toc" aria-label="目录">
|
||||
<div class="toc-title">目录</div>
|
||||
<ol>
|
||||
<li><a href="#背景与发展">背景与发展</a></li>
|
||||
<li><a href="#设计">设计</a>
|
||||
<ol>
|
||||
<li><a href="#轨道器">轨道器</a></li>
|
||||
<li><a href="#外挂燃料箱">外挂燃料箱</a></li>
|
||||
<li><a href="#液体燃料助推器">液体燃料助推器</a></li>
|
||||
</ol></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="#与-sts-和秃鹫航天飞机的关系">与 STS 和秃鹫航天飞机的关系</a></li>
|
||||
<li><a href="#技术参数">技术参数</a></li>
|
||||
<li><a href="#评价">评价</a></li>
|
||||
<li><a href="#相关条目">相关条目</a></li>
|
||||
</ol>
|
||||
</nav>
|
||||
|
||||
<h2 id="背景与发展">背景与发展</h2>
|
||||
<h3 id="哥伦比亚事故与安全改进需求">哥伦比亚事故与安全改进需求</h3>
|
||||
<p>2003 年哥伦比亚航天飞机事故是推动 CERV 立项的核心事件。STS-107 任务再入阶段，因发射时外挂燃料箱泡沫脱落击穿左翼前缘热防护瓦，导致超高温气体侵入翼内结构，轨道器解体，七名航天员遇难。事故调查不仅指出了泡沫脱落和热防护脆弱性的直接原因，还暴露了 STS 体系在上升段乘员逃生能力、在轨热防护检查和组织性风险评估方面的系统性缺陷。</p>
|
||||
<p>事故后，NASA 对剩余三架 STS 轨道器进行了大规模返厂升级，包括改进泡沫喷涂工艺、增加在轨机械臂热防护检查、优化上升段摄像覆盖和修订任务中止规则。然而这些改进无法从根本上解决 STS 的两大结构问题：轨道器侧挂在燃料箱旁、乘员在上升段无逃生路径。泡沫脱落风险只能降低而不能消除；固体助推器一旦点燃就无法关机和节流；单片大型垂尾和 STS 的滑翔特性使得着陆阶段几乎没有复飞余地。</p>
|
||||
<p>同期，STS 轨道器在 1980 年代的原始结构设计中大量使用铝合金，机身空重偏高，限制了载荷能力和任务弹性。轨道器机队经过二十余年高频飞行后，结构疲劳积累和维护成本持续上升。美国在 2004 年提出星座计划后，STS 按原计划将在 2010 年退役，但替代系统的研发进度一再推迟，航天飞机继承线出现空白风险。</p>
|
||||
<h3 id="cerv-的立项与定位">CERV 的立项与定位</h3>
|
||||
<p>2005 年，CERV 项目正式立项。项目目标明确为：在 STS 运营经验和地面设施基础上，开发一型安全余量更高、可维护性更好、运力不低于 STS 并具备乘员整体逃逸能力的航天飞机，而非追求完全新一代的运载体系。CERV 的名称——Composite Enhanced Reusable Vehicle——直接反映了项目的核心工程策略：以复合材料减重换取安全增强和性能提升。</p>
|
||||
<p>与同时期星座计划中的阿瑞斯火箭和猎户座飞船不同，CERV 不脱离航天飞机的"垂直发射、水平着陆"和载人/载荷同舱运输范式。项目方认为，STS 的运营体系、发射工位、总装厂房、运输履带车、着陆跑道和任务控制中心是航天飞机继承线的战略资产，不应被废弃；航天飞机继承线自身需要完成的不是范式转换，而是补足安全课。</p>
|
||||
<p>项目早期曾评估过多种替代方案，包括完全可重复使用两级入轨飞行器、小型载人飞船加货运火箭的组合，以及保留 STS 固体助推器、仅更换轨道器的方案。方案评估最终确定：液体助推器路线虽然研发成本更高，但提供了节流、关机、中止和RTLS 返场着陆能力，综合安全收益和全生命周期成本优于固体助推器路线。复合材料机身和整体式乘员逃逸舱则被列为不可妥协的安全需求。</p>
|
||||
|
||||
<h3 id="研发阶段">研发阶段</h3>
|
||||
<table>
|
||||
<thead><tr><th>阶段</th><th>时间</th><th>主要内容</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>方案论证</td><td>2005-2007</td><td>确定复合材料机身、液体助推器、整体式逃逸舱和翼尖双垂尾方案。</td></tr>
|
||||
<tr><td>关键设计评审</td><td>2008-2009</td><td>完成复合材料主结构设计、TH-12 发动机试车、逃逸舱分离试验和翼型风洞验证。</td></tr>
|
||||
<tr><td>轨道器总装</td><td>2010-2013</td><td>制造首架轨道器，完成机身弯扭试验、增压舱疲劳试验和机翼/鸭翼连接强度测试。</td></tr>
|
||||
<tr><td>集成测试</td><td>2013-2014</td><td>轨道器与 ET/助推器全栈集成、航电联调、逃逸舱全流程地面试验和喷气发动机飞行前试车。</td></tr>
|
||||
<tr><td>首飞准备</td><td>2014-2015</td><td>完成全栈振动测试、发射倒计时合练和无人轨道飞行就绪评审。</td></tr>
|
||||
<tr><td>首飞</td><td>2015 年 6 月</td><td>CERV-F1 由地平线号执飞，完成首次无人轨道飞行，验证主发动机、助推器回收、再入和水平着陆全流程。</td></tr>
|
||||
<tr><td>载人认证</td><td>2015-2016</td><td>完成载人试飞、逃逸舱飞行中测试、喷气发动机着陆辅助验证和在轨自持测试。</td></tr>
|
||||
<tr><td>接替 STS</td><td>2017</td><td>STS 正式退役，CERV 全面接替载人和货运任务。</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="设计">设计</h2>
|
||||
|
||||
<h3 id="轨道器">轨道器</h3>
|
||||
<figure class="thumb tright"><div class="image-placeholder">CERV 轨道器三视图占位</div><figcaption class="thumbcaption">CERV 轨道器采用双翼尖垂尾和前置鸭翼布局，取消了 STS 的中央大型单片垂尾。（三视图待补充）</figcaption></figure>
|
||||
<h4>结构与材料</h4>
|
||||
<p>轨道器机身采用铝合金—复合材料混合结构，主承力框架使用铝合金以保持热稳定性，机翼蒙皮、货舱门、机身面板和非承力隔框大量使用碳纤维增强复合材料。复合材料的大量应用使轨道器干重降至 63 吨，较 STS 轨道器（约 78 吨）减少约 19%。结构减重直接转化为额外载荷能力，并为乘员舱逃逸系统、喷气发动机和增强型航电腾出重量包线。</p>
|
||||
<p>复合材料选型和制造由波音与诺斯罗普·格鲁曼联合承担。机翼蒙皮采用共固化整体加筋壁板，减少了紧固件数量并降低了装配工时。货舱门采用复合材料蜂窝夹层结构，在保持与 STS 货舱门同等刚度的前提下减重约 30%。机身中段和尾段的次级结构大量应用复合材料面板，仅在发动机推力架、起落架连接点和翼身连接区保留钛合金或高强度铝合金加强件。</p>
|
||||
<p>结构减重的意义超出了单纯的质量指标。轨道器干重降低后，在相同推力条件下可获得更充裕的上升段中止选项、更低的翼载和更灵活的着陆质量窗口。这对 CERV 的核心安全目标至关重要：更低的翼载意味着更低的进近速度和更长的跑道选择时间，直接支撑了喷气发动机辅助着陆和复飞操作。</p>
|
||||
<h4>热防护系统</h4>
|
||||
<figure class="thumb tright"><a class="media-link" href="#cerv-img-reentry"><img src="/cerv/cerv_reentry_closeup.png" alt="CERV 轨道器再入热流" data-wiki-asset="/cerv/cerv_reentry_closeup.png"></a><figcaption class="thumbcaption">CERV 轨道器在再入阶段被高温等离子体包裹，改进型通用隔热瓦和隔热涂层提供冗余热防护。</figcaption></figure>
|
||||
<p>CERV 的机身使用改进后的通用隔热瓦，在 STS 热防护体系基础上提升了耐久性和可维护性。通用隔热瓦采用标准化尺寸和模块化安装接口，减少了不同位置所需隔热瓦的规格数量，从而降低了制造、库存和更换成本。单块隔热瓦的更换时间较 STS 缩短约 40%，维护团队可在常规任务周转周期内完成高热流区域的全面检查与局部换瓦。第二批轨道器使用了增强配方隔热涂层，进一步提高了再入后的涂层完整性保持率；第三批在此基础上引入了改进型隔热瓦基体材料，提升了高能返回后的重复使用裕度。</p>
|
||||
<p>隔热瓦下方设有隔热涂层，可在隔热瓦部分破碎或脱落的情况下继续提供一定的隔热保护。该冗余设计直接对应哥伦比亚事故的教训——当一块或多块隔热瓦失效时，下层涂层可延缓高温气体侵入机身主体结构，为轨道器争取更多反应时间。隔热涂层在再入后需通过热像扫描检查完整性，热流异常区域需在下次飞行前补涂。</p>
|
||||
<p>机翼前缘和机头等极端热流区使用增强碳碳材料，边条和发动机短舱周边使用耐高温合金。复合材料蒙皮的热膨胀特性与金属结构不同，设计团队在热防护瓦与复合材料蒙皮之间增加了柔性中间层和分段间隙补偿，以避免再入热循环造成的脱瓦或应力集中。</p>
|
||||
<h4>气动布局</h4>
|
||||
<p>CERV 在气动布局上完成了从 STS 到新一代航天飞机的过渡。该级放弃了 STS 的中央大型单片垂直尾翼，改用位于三角翼翼尖的两片小型垂直安定面。翼尖双垂尾在再入和滑翔阶段提供方向稳定性和偏航控制，同时取消了 STS 垂尾对机身中轴线的结构质量集中，有利于复合材料机身的匀载设计和减重。</p>
|
||||
<p>机头两侧设有一对前置鸭翼，承担起飞抬轮、再入后段俯仰配平和低速复飞功能。主翼为后掠三角翼，每侧后缘设有多组控制面，可按任务阶段组合为副翼、升降舵、襟翼或阻力板。该翼型布局随后被秃鹫航天飞机整体继承和放大，构成航天飞机继承线 2010 年代以后的标准气动方案。第三批轨道器在鸭翼控制面上引入了电驱动替代液压驱动，降低了维护复杂性和液压管路泄漏风险。</p>
|
||||
<h4>乘员舱整体逃逸系统</h4>
|
||||
<figure class="thumb tright"><a class="media-link" href="#cerv-img-escape-flyaway"><img src="/cerv/cerv_escape_flyaway.png" alt="CERV 乘员舱逃逸测试" data-wiki-asset="/cerv/cerv_escape_flyaway.png"></a><figcaption class="thumbcaption">乘员舱整体逃逸测试：逃逸舱从发射场上方飞离，固体推进器提供初始分离推力。</figcaption></figure>
|
||||
<p>CERV 是航天飞机继承线上首款实现乘员舱整体逃逸能力的轨道器。乘员舱位于轨道器前部，为独立加压结构，可在任何飞行阶段——包括地面待发、上升段、在轨飞行和再入阶段——与轨道器主体物理分离。逃逸系统不限于特定的高度窗口或飞行状态，在设计上要求从发射台静态逃逸到再入大气层的全剖面内均保持可用。</p>
|
||||
<p>分离由两枚安装在乘员舱后部的固体燃料推进器启动。固体逃逸发动机主要用于地面至 100 km 高度的阶段，尤其是最大动压区逃逸——该区域内气动载荷极高，需要固体发动机的瞬时高峰值推力将乘员舱快速推离全栈。一旦乘员舱离开轨道器主体达到 5 米距离，四台双组元常温燃料逃逸发动机即点火，与剩余燃烧的固体发动机同时工作，提供更大的总推力以确保乘员舱安全脱离危险区域。</p>
|
||||
<p>逃逸飞行中，乘员舱使用自身的 RCS 推进器和前置鸭翼进行基础姿态控制。逃逸发动机燃尽后，乘员舱通过降落伞系统实施水面或陆地着陆。降落伞系统包括一具引导伞、三具主伞和备份开伞逻辑，设计着陆速度不高于 8 m/s。第二批轨道器升级了降落伞展开电子时序控制器，缩短了着陆准备时间；第三批引入了冗余高度计和自适应伞释放逻辑，提高了不同地形条件下的着陆安全性。</p>
|
||||
<p>乘员舱逃逸系统不依赖轨道器飞控或主电源，拥有独立的电池、惯性导航单元和降落伞展开逻辑。逃逸触发的决策可由机组手动激活，也可由发射中止计算机根据推力丧失、结构过载、级间分离异常或轨迹偏离自动触发。该系统的整体式逃逸理念——将乘员舱而非单个座椅弹射作为逃逸单元——此后被秃鹫航天飞机直接继承并扩展。</p>
|
||||
<h4>喷气发动机</h4>
|
||||
<p>轨道器尾部配有两台涡扇喷气发动机，用于着陆阶段辅助飞行、扩展横向航程和提供复飞能力。着陆标准流程中，轨道器在降至 10,000 米以下时启动喷气发动机，建立推力后进入正常着陆程序。喷气发动机使 CERV 具备了航天飞机继承线上此前从未实现的复飞能力：若进近不稳定、跑道被占或风切变超过限制，轨道器可执行复飞绕场重新进近，无需依赖无动力滑翔的一次性着陆尝试。</p>
|
||||
<p>复飞时需要打开加力燃烧器，否则在满载返回质量和短跑道条件下推力不足以完成复飞爬升。喷气发动机使用独立于 OMS 和逃逸系统的航空煤油燃料系统，仅在着陆阶段使用。若喷气发动机在下降过程中启动异常，轨道器将切换为直接滑翔着陆模式，采用目视飞行规则进近。该备份模式在多次任务中被列为最低配置着陆方案，并经过模拟和飞行验证。第三批轨道器配备了改进型喷气发动机启动系统，将冷态启动时间缩短了约 25%，进一步扩大了可用的复飞决策窗口。</p>
|
||||
<p>喷气发动机的引入也扩展了 CERV 的着陆备降灵活性。与 STS 仅能依赖少数长跑道和海外备降场不同，CERV 在喷气发动机可用时可以将更多机场纳入候补备降清单，提升了对轨道交会延迟、天气恶化和跑道拥堵的适应能力。</p>
|
||||
<h4>航电与电传飞控</h4>
|
||||
<p>CERV 采用电传飞控（fly-by-wire）设计，在 STS 玻璃化座舱的基础上进行了全面数字化升级。第一批飞控计算机采用四余度架构，确保在任何单点故障的情况下系统仍能继续安全飞行；第二批升级为增强型飞控处理器，引入了基于任务阶段的自适应控制律切换；第三批采用新一代综合航电平台，统一了飞行控制、任务管理和通信导航功能，减少了独立处理器数量和布线重量。</p>
|
||||
<p>轨道器具备全阶段全自动飞行能力，覆盖发射、入轨、交会、对接、再入和着陆全流程——着陆阶段同样由自动系统独立完成，无需飞行员手动接管。常规任务配置仍为两名飞行员，但自动系统可在无人状态下独立执行完整任务。</p>
|
||||
<p>在轨期间，航电系统提供自动交会、对接保持、货舱操作和热控管理。飞控软件按阶段门组织任务决策：再入前检查热防护、客舱压力和备降点天气；着陆前检查喷气发动机状态、跑道可用性和复飞窗口；若任一条件不满足，系统自动建议延迟、备降或中止选项。</p>
|
||||
<h4>气闸舱与对接口</h4>
|
||||
<p>轨道器货舱前部设有内置气闸舱，供乘组执行舱外活动（EVA）。气闸舱可容纳两名着舱外航天服的乘员，支持空间站维护、载荷部署和应急修复等出舱作业。第三批轨道器的气闸舱面积增大约 15%，可同时容纳两名乘员外加一件大型工具包或小型设备，提升了复杂出舱任务的效率。</p>
|
||||
<p>气闸舱上方安装有一个可伸缩式 1.875 米通用对接口，用于与其他航天器交会对接。该对接口在不使用时收入货舱壁内，对接时伸出并完成硬捕获和密封。可伸缩设计减少了发射和再入阶段对接口的气动载荷和热负荷，并降低了对接机构的热防护维护需求。第二批轨道器引入了改进型对接密封圈，延长了在轨长期停泊时的密封寿命。</p>
|
||||
|
||||
<h3 id="外挂燃料箱">外挂燃料箱</h3>
|
||||
<p>CERV 的外挂燃料箱延续 STS 体系的 8.4 米直径规格，为三台 RS-25D 主发动机提供液氢和液氧推进剂。与 STS 外挂燃料箱的大面积泡沫保温方案不同，CERV 版本采用了保温涂层加保温泡沫的双层设计：底层为喷涂式保温涂层，覆盖燃料箱绝大部分表面积；泡沫保温层仅用于气动加热最严重的局部区域和结构连接部位。该设计显著减少了保温泡沫的总用量，从而降低了发射阶段泡沫脱落并撞击轨道器热防护系统的风险。</p>
|
||||
<p>保温涂层方案的技术难点在于涂层与铝合金箱壁的热膨胀匹配、低温下的附着力维持，以及多次发射周期中的老化和检测。CERV 在验证阶段对涂层进行了多次热循环和振动测试，确认其在液氢温度至发射气动加热范围内的完整性和附着力。</p>
|
||||
<p>外挂燃料箱由洛克希德·马丁位于米舒的工厂制造，通过驳船转运至文昌发射场或肯尼迪航天中心。燃料箱在上升段为主发动机供气，主发动机关机后与轨道器分离，在再入大气层时烧毁。CERV 运营期间未发生因外挂燃料箱泡沫脱落导致的热防护损伤事件，涂层加泡沫的双层保温方案随后被秃鹫航天飞机继承。</p>
|
||||
|
||||
<h3 id="液体燃料助推器">液体燃料助推器</h3>
|
||||
<figure class="thumb tright"><a class="media-link" href="#cerv-img-booster-sep"><img src="/cerv/cerv_booster_separation.png" alt="CERV 助推器分离" data-wiki-asset="/cerv/cerv_booster_separation.png"></a><figcaption class="thumbcaption">CERV 全栈在高空分离两侧液体助推器，助推器分离后将执行再入和反推回收。</figcaption></figure>
|
||||
<p>CERV 将固体助推器更换为液体燃料助推器是该型号最具工程意义的改动之一。两枚 4 米直径液体燃料助推器对称安装在 8.4 米外挂燃料箱两侧，每枚助推器底部安装 9 台增推版 TH-12 液氧煤油发动机，采用富氧补燃循环，单台真空推力 1,132.67 kN。9 台发动机以 8+1 布局排列——外圈 8 台固定推力，中央 1 台用于节流和推力矢量控制。助推器具备节流、关机和重启能力，支持上升段推力调节和发射中止场景下的受控关机。</p>
|
||||
<p>助推器姿态控制采用液氧/煤油双组元 RCS 推进器，与主发动机共享推进剂种类。相比 STS 固体助推器使用的肼类单组元 RCS，双组元液氧/煤油 RCS 具有更大的推力，且单一燃料种类降低了系统复杂性和地面处理成本。该方案随后被秃鹫助推器直接继承。第三批轨道器对应的助推器升级了 RCS 阀组和推力室涂层，将单次回收后的 RCS 维护工时降低了约 20%。</p>
|
||||
<p>助推器在分离后执行 boost-back burn 返场机动，随后受控再入并反推着陆至发射场附近的专用着陆台（RTLS，Return To Launch Site）。早期回收测试（CERV-F1 至 CERV-F5）在近海空域进行，以降低着陆失败对发射场设施的风险；CERV-F5 成功回收后，所有常规运营任务均采用发射场 RTLS 着陆模式。助推器着陆后经初步安全化处理，转运至整备设施进行飞行后检查和下一轮任务准备。</p>
|
||||
<h4>复用与维护</h4>
|
||||
<p>CERV 助推器设计复用寿命为 50 次，每飞行 10 次需进行一次计划内维护。维护内容包括发动机涡轮泵检查、推力室烧蚀评估、RCS 阀组测试、栅格翼展开机构润滑和结构无损检测。与后续 Vulture 助推器相比，CERV 助推器的维护间隔较短，且不具备免维护长时间运行能力。</p>
|
||||
<p>Vulture 使用的改进版 TH-12 在发动机基本性能指标上保持不变（真空推力仍为 1,132.67 kN），但通过涡轮泵轴承升级、推力室冷却通道优化和材料改进，大幅提升了维护效率并降低了维护成本。Vulture 助推器在没有维护的情况下可连续飞行 75 次，进行计划内维护后可继续使用 200-300 次。CERV 助推器的 50 次设计寿命和 10 次维护间隔为 Vulture 提供了关键的使用基线数据。</p>
|
||||
<h4>助推器回收测试历程</h4>
|
||||
<p>CERV 前五次飞行的助推器均为反推回收测试，每次任务逐步推进回收技术的成熟度：</p>
|
||||
<table>
|
||||
<thead><tr><th>任务</th><th>左侧助推器（LB）</th><th>右侧助推器（RB）</th><th>关键结论</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>CERV-F1</td><td colspan="2">两侧助推器成功完成 boost-back burn，再入段失联；后续判断可能为热防护失效。</td><td>boost-back burn 点火逻辑和返场弹道可行，再入热防护需加强。</td></tr>
|
||||
<tr><td>CERV-F2</td><td>T+77 s 单发失效，仍按预定时间关机。轨道器通过延长 RS-25D 燃烧时间正常入轨。LB 取消回收。</td><td>正常关机，反推点火，但着陆点火失败。</td><td>单发失效情况下全栈仍可维持上升并安全入轨。<br>着陆点火可靠性需要改进。</td></tr>
|
||||
<tr><td>CERV-F3</td><td>正常关机，姿态控制异常，取消回收。</td><td>正常关机并点火着陆，但中央发动机 TVC 失效。助推器溅落后倾覆爆炸。</td><td>姿态控制和 TVC 系统存在潜在单点故障链。</td></tr>
|
||||
<tr><td>CERV-F4</td><td colspan="2">采用更新航电系统的新助推器设计，两侧均正常溅落。</td><td>更新航电和控制系统解决了前三飞的多数故障模式。</td></tr>
|
||||
<tr><td>CERV-F5</td><td colspan="2">两侧助推器正常关机、反推点火和着陆，完成首次助推器全面成功回收。</td><td>助推器回收全流程——上升、分离、再入、反推和着陆——在工程上达到可运营成熟度。</td></tr>
|
||||
</tbody></table>
|
||||
<p>CERV-F5 任务后，助推器回收进入常规运营状态。CERV-F12 任务首次使用回收后的助推器执行二次发射，并再次成功回收，标志着液体助推器复用的工程闭环。此后，CERV 助推器机队逐渐过渡为以复用助推器为主，新造助推器仅用于补充损耗和特殊任务需求。</p>
|
||||
<p>液体助推器路线是 CERV 对航天飞机继承线影响最深远的工程决策之一。4 米助推器在 CERV 运营期间积累了数百次飞行和回收数据，为 2030 年代秃鹫航天飞机放大至 5 米直径的液体助推器提供了推力、结构、热防护、着陆控制和复用经济性方面的直接工程基础。</p>
|
||||
<table>
|
||||
<thead><tr><th>参数</th><th>CERV 液体助推器</th><th>Vulture 液体助推器（对比）</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>直径</td><td>4 米</td><td>5 米</td></tr>
|
||||
<tr><td>发动机</td><td>9× TH-12（增推版），单台真空推力 1,132.67 kN</td><td>9× TH-12 改进版，性能指标相同，维护效率大幅提升</td></tr>
|
||||
<tr><td>推进剂</td><td>液氧 / 煤油</td><td>液氧 / 煤油</td></tr>
|
||||
<tr><td>姿态控制</td><td>液氧/煤油双组元 RCS</td><td>液氧/煤油双组元 RCS（继承自 CERV）</td></tr>
|
||||
<tr><td>回收方式</td><td>RTLS 返场着陆</td><td>RTLS 返场着陆或海上回收船</td></tr>
|
||||
<tr><td>设计寿命</td><td>50 次（每 10 次需维护）</td><td>免维护 75 次；维护后 200-300 次</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="推进与电源">推进与电源</h2>
|
||||
<h3 id="主推进">主推进</h3>
|
||||
<p>CERV 主推进系统继承 STS 构型：三台 RS-25D 液氢液氧分级燃烧发动机安装在轨道器尾部，通过 8.4 米外挂燃料箱供气。RS-25D 是 RS-25 系列的后期改进版本，海平面推力约 1,860 kN（单台），真空推力约 2,279 kN。三台发动机在上升段持续工作直至主发动机关机，随后外挂燃料箱分离并在大气层中烧毁。</p>
|
||||
<p>与 STS 相比，CERV 在 RS-25D 的发动机控制器、涡轮泵健康监测和节流范围方面做了改进，以配合液体助推器的上升段推力曲线调整。主发动机不支持空中重启，入轨后的所有机动由轨道机动系统完成。在助推器单发失效等异常场景下，轨道器可通过延长 RS-25D 燃烧时间以补偿推力损失，该能力在 CERV-F2 任务中首次得到实际验证。</p>
|
||||
<h3 id="轨道机动系统">轨道机动系统</h3>
|
||||
<p>轨道机动系统由两台 60 kN 常温燃料发动机组成，安装在轨道器尾部的 OMS 吊舱中。OMS 发动机使用四氧化二氮/一甲基肼推进剂，用于入轨圆化、轨道机动、交会调相、离轨制动和部分中止模式。</p>
|
||||
<p>OMS 燃料与乘员舱逃逸引擎燃料通用，共享同一套推进剂储罐和输送管路。这一设计基于安全和经济考虑：在正常任务中，OMS 储罐中的推进剂全部用于轨道机动；在逃逸场景下，同一批推进剂可被逃逸引擎调用。共用推进剂避免了为逃逸系统单独设置储罐的质量代价，但要求推进剂在逃逸激活时能以足够流量和压力输送到乘员舱尾部的逃逸发动机。</p>
|
||||
<h3 id="逃逸动力">逃逸动力</h3>
|
||||
<p>乘员舱逃逸系统采用两级动力配置，两级之间存在推力重叠。逃逸激活后，两枚固体燃料推进器首先点火，提供初始高峰值推力以将乘员舱从全栈上快速拉离，克服上升段气动压力和轨道器主体惯性。固体发动机主要用于地面至 100 km 高度阶段，尤其是最大动压区逃逸——该区域内气动载荷极高，需要固体发动机的瞬时高峰值推力。固体推进器点火后，一旦乘员舱离开轨道器主体达到 5 米距离，四台双组元常温燃料逃逸发动机立即点火，与仍在燃烧的固体发动机同时工作，以最大总推力确保乘员舱安全脱离。固体推进器燃尽后，常温燃料发动机继续独立工作，提供持续推力和姿态控制，将乘员舱送至安全高度和轨迹。两级之间的推力重叠设计避免了固体推进器燃尽到常温发动机建立稳定推力之间出现推力空档。</p>
|
||||
<p>逃逸系统在设计上覆盖所有飞行阶段——包括发射台静态逃逸、上升段逃逸、在轨飞行逃逸和再入阶段逃逸。在 100 km 高度以上或再入阶段，气动压力较低，逃逸系统可跳过固体推进器阶段，直接由常温燃料发动机执行分离。无论轨道器处于何种飞行状态，逃逸系统均能在触发后迅速响应，确保乘员舱安全脱离危险区域。</p>
|
||||
<p>逃逸发动机在启动前通过快速切换阀组从 OMS 推进剂储罐获取燃料。乘员舱配备独立的 RCS 推进器和惯性导航单元，在逃逸飞行中维持稳定姿态并为降落伞展开创造条件。降落伞系统包括一具引导伞、三具主伞和备份开伞逻辑，设计着陆速度不高于 8 m/s。</p>
|
||||
<h3 id="喷气发动机">喷气发动机</h3>
|
||||
<p>轨道器尾部配有两台涡扇喷气发动机，使用独立于推进系统的航空煤油燃料。喷气发动机在轨道器降至 10,000 米以下后启动，为着陆进近提供推力。正常着陆流程中，喷气发动机启动后轨道器绕场一圈以消耗多余能量，随后建立 ILS 仪表进近并着陆。</p>
|
||||
<p>若喷气发动机在下降过程中出现启动异常或推力不足，轨道器切换为直接滑翔着陆模式，采用 VFR 进近。滑翔着陆模式不依赖喷气发动机，但需要在更高高度开始瞄准跑道，且不保留复飞选项。该备份模式在 CERV 运营期间经过模拟器训练和若干次实际飞行验证。</p>
|
||||
<p>复飞操作需要打开加力燃烧器以在满载返回质量下获得足够爬升推力。加力燃烧器打开后燃油消耗显著增加，因此复飞后通常不会再次绕场——第二次进近将直接切入短五边或选择备降机场。</p>
|
||||
<h3 id="电源">电源</h3>
|
||||
<p>CERV 配备两台燃料电池（fuel cell），以低温液氢和液氧为反应物，为轨道器提供电力、热量和饮用水。两台燃料电池支持轨道器自由飞行 35 天。各批次燃料电池输出功率和可靠性逐步提升：第一批为基线设计，第二批升级了膜电极组件，第三批进一步提升了输出功率以支持新增的通信载荷和 EVA 设备。</p>
|
||||
<p>轨道器顶部设有可伸缩式 1.875 米通用对接口，可通过外部供电线路从空间站、轨道船坞或其他航天器接收电力输入。外部供电模式下，燃料电池可转入低功率待命状态，显著延长在轨驻留时间。该能力使 CERV 能够在空间站或后续大型轨道设施停泊期间保持系统温热待命，无需消耗自身推进剂和燃料电池反应物。第三批轨道器的外部供电接口进行了升级，支持更高的输入功率以满足 120 天级长期停泊的保温和系统维持需求。</p>
|
||||
|
||||
<h2 id="乘员与载荷">乘员与载荷</h2>
|
||||
<p>CERV 乘员舱标准配置为 8 人，常规任务中由两名飞行员和最多六名任务人员组成。乘员舱具备全阶段全自动飞行能力（含着陆），可在无人状态下独立执行完整任务流程。</p>
|
||||
<p>货舱位于乘员舱后方，内部尺寸与 STS 货舱相当——长约 18.3 米、直径约 4.6 米。CERV 最多可将 30 吨载荷送入 600×600 km × 51° 轨道，最多可携带 20 吨载荷进行再入返回。载荷能力较 STS 有所提升，主要得益于复合材料减重和液体助推器更高的运力效率。</p>
|
||||
<table>
|
||||
<thead><tr><th>项目</th><th>数据</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>乘员容量</td><td>8 人（常规 2 名飞行员 + 0-6 名任务人员）</td></tr>
|
||||
<tr><td>上行载荷</td><td>30 吨（600×600 km × 51°）</td></tr>
|
||||
<tr><td>返回载荷</td><td>20 吨</td></tr>
|
||||
<tr><td>货舱尺寸</td><td>约 18.3 m × 4.6 m</td></tr>
|
||||
<tr><td>在轨自持（自由飞行）</td><td>35 天（燃料电池）/ 30 天（生命维持）</td></tr>
|
||||
<tr><td>在轨自持（停泊供电）</td><td>最长 120 天（驻留空间站或轨道船坞时通过外部供电延长）</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="任务剖面">任务剖面</h2>
|
||||
<h3 id="发射与上升段">发射与上升段</h3>
|
||||
<p>CERV 可从文昌航天发射场或卡纳维拉尔角垂直发射。升空后，两枚液体助推器和三台 RS-25D 主发动机共同提供上升推力。助推器在燃料耗尽前约 30 秒受控节流，随后与全栈分离，执行再入和反推着陆，目标为发射场对应的RTLS 返场着陆。主发动机继续燃烧直至主发动机关机，外挂燃料箱随后分离。若助推器出现单发失效，轨道器可延长 RS-25D 燃烧时间以补偿推力损失，维持正常入轨。</p>
|
||||
<p>上升段任一时刻若触发中止条件，乘员舱逃逸系统可立即激活。在 100 km 高度以下，固体逃逸推进器提供初始分离推力；乘员舱脱离轨道器 5 米后，常温燃料逃逸发动机同步点火增强推力。高于 100 km 或再入阶段，逃逸系统可跳过固体推进器阶段，直接由常温燃料发动机执行分离和脱离。</p>
|
||||
<h3 id="在轨运行">在轨运行</h3>
|
||||
<p>入轨后，OMS 发动机完成圆化和轨道调整。货舱门打开以暴露散热器和机械臂，燃料电池提供电力和水，乘员开始执行任务计划。CERV 自由飞行状态下可在轨自持 15-20 天（视批次而定）；若与空间站或轨道船坞对接并通过 1.875 米对接口接收外部供电，最长在轨驻留时间可延长至 120 天。标准任务通常持续 7-12 天，特殊任务可延至 20 天。货舱前部的气闸舱支持乘组在整个任务期间执行 EVA 作业。</p>
|
||||
<h3 id="返回与着陆">返回与着陆</h3>
|
||||
<p>离轨前，OMS 发动机执行制动点火，轨道器进入再入轨迹。再入阶段由改进型通用隔热瓦和机翼前缘碳碳材料承受气动加热，隔热瓦下层涂层在瓦片局部破损时提供冗余防护。电传飞控系统管理攻角、滚转和侧滑以控制热流和航程。</p>
|
||||
<p>进入大气层后，轨道器以升力体滑翔方式继续减速。高度降至约 10,000 米时，轨道器启动两台喷气发动机。喷气发动机建立推力后，轨道器按标准流程绕场一圈以消耗多余能量，随后切入 ILS 仪表进近程序并由自动飞控系统完成着陆。着陆阶段为全自动，无需飞行员手动接管。</p>
|
||||
<p>主要着陆场为卡纳维拉尔角的 Shuttle Landing Facility 或文昌航天器着陆跑道。此外，CERV 可在任何一个配备 CAT III 仪表着陆系统且跑道长度大于 3,000 米的民用机场着陆，这一能力在备用着陆场选择和应急情况下提供了显著灵活性。</p>
|
||||
<p>若喷气发动机启动异常或推力不足，备份模式直接由滑翔方式执行 VFR 进近着陆。该备份模式无复飞选项，因此任务控制需在再入前确认至少一个满足天气、跑道长度和交叉风限制的备降机场。</p>
|
||||
<p>复飞操作仅在喷气发动机正常工作且打开加力燃烧器的前提下可用。加力燃烧器为满载返回质量下的爬升提供额外推力。复飞后通常不执行第二次绕场，直接切入短五边或选择备降机场。</p>
|
||||
<table>
|
||||
<thead><tr><th>任务阶段</th><th>关键操作</th><th>备份/中止选项</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>发射</td><td>文昌或卡纳维拉尔角工位垂直起飞，液体助推器与 RS-25D 共同工作。</td><td>乘员舱全阶段逃逸；助推器节流/关机/中止。</td></tr>
|
||||
<tr><td>助推器分离</td><td>助推器节流后分离，执行 RTLS 返场，反推着陆至发射场着陆台。</td><td>助推器异常时由主发动机延长燃烧维持上升或触发中止。</td></tr>
|
||||
<tr><td>入轨</td><td>主发动机关机、ET 分离、OMS 圆化。</td><td>OMS 备份发动机和备份轨道就位。</td></tr>
|
||||
<tr><td>在轨运行</td><td>货舱操作、交会对接（1.875 m 通用对接口）、EVA（气闸舱）、35 天燃料电池自持 / 30 天生命维持或外部供电延长至 120 天。</td><td>异常时提前制动返航或转入安全轨道等待。</td></tr>
|
||||
<tr><td>再入</td><td>OMS 制动、热防护管理（通用隔热瓦+隔热涂层）、攻角和滚转控制。</td><td>异常姿态或热流时切换至保守再入剖面；隔热涂层提供冗余防护。</td></tr>
|
||||
<tr><td>着陆</td><td><10,000 m 启动喷气发动机，绕场一圈，ILS 自动着陆。主着陆场：卡角 SLF 或文昌着陆跑道；备降场：任何 CAT III 跑道 >3,000 m 的民用机场。</td><td>喷气发动机异常时直接滑翔 VFR 着陆；复飞需开加力，切短五边或备降。</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="机队">机队</h2>
|
||||
<h3 id="测试机">测试机</h3>
|
||||
<table>
|
||||
<thead><tr><th>编号</th><th>类型</th><th>用途</th><th>后续去向</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>CTV-1</td><td>结构测试件</td><td>静力载荷、连接结构、外挂燃料箱接口验证。</td><td>测试后封存。</td></tr>
|
||||
<tr><td>CTV-2</td><td>结构测试件</td><td>全栈振动、推进剂加注、地面运输和发射台适配验证。</td><td>测试后封存。</td></tr>
|
||||
<tr><td>CTV-3</td><td>飞行测试件</td><td>安装飞行控制系统和喷气引擎，用于飞行性能测试和飞控系统验证。</td><td>转为训练机使用。</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h3 id="轨道器机队">轨道器机队</h3>
|
||||
<p>CERV 共建造了 8 架轨道器，分三个批次生产，在 2015 年至 2040 年间累计执行 666 次飞行任务。末飞任务 CERV-F666 于 2040 年 6 月 15 日由发现号执飞。</p>
|
||||
|
||||
<h4>第一批次（初始生产批次，2015-2017 年首飞）</h4>
|
||||
<p>首批 3 架轨道器采用 CERV 初始生产构型，包括基线复合材料机身、四余度飞控计算机、第一代通用隔热瓦与隔热涂层、35 天燃料电池 / 30 天生命维持和初始版可伸缩对接口。该批次承担了全部验证试飞和初期运营任务，为后续批次提供了关键的设计改进反馈。</p>
|
||||
<table>
|
||||
<thead><tr><th>编号</th><th>名称</th><th>首飞</th><th>末飞</th><th>飞行次数</th><th>状态</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>CERV-1</td><td>地平线号（Horizon）</td><td>2015 年 6 月</td><td>2037 年 3 月</td><td>110</td><td>退役</td></tr>
|
||||
<tr><td>CERV-2</td><td>探路者号（Pathfinder）</td><td>2015 年 11 月</td><td>2037 年 9 月</td><td>105</td><td>退役</td></tr>
|
||||
<tr><td>CERV-3</td><td>先驱者号（Pioneer）</td><td>2017 年 3 月</td><td>2038 年 5 月</td><td>108</td><td>退役</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h4>第二批次（改进批次，2020-2021 年首飞）</h4>
|
||||
<p>第二批 2 架轨道器基于首批运营数据进行了升级：增强型飞控处理器引入自适应控制律切换；隔热涂层配方改进，提升了高能返回后的完整性保持率；生命支持系统可靠性进一步提升；改进型对接密封圈延长了在轨停泊寿命；关键疲劳节点处增加了结构加强件。该批次标志着 CERV 设计从验证向成熟运营的过渡。</p>
|
||||
<table>
|
||||
<thead><tr><th>编号</th><th>名称</th><th>首飞</th><th>末飞</th><th>飞行次数</th><th>状态</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>CERV-4</td><td>旅行者号（Voyager）</td><td>2020 年 5 月</td><td>2038 年 11 月</td><td>88</td><td>退役</td></tr>
|
||||
<tr><td>CERV-5</td><td>勇气号（Spirit）</td><td>2021 年 2 月</td><td>2039 年 4 月</td><td>82</td><td>退役</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h4>第三批次（增强批次，2025-2026 年首飞）</h4>
|
||||
<p>第三批 3 架轨道器代表了 CERV 设计的最终形态：新一代综合航电平台统一了飞行控制、任务管理和通信导航功能；气闸舱面积增大约 15%；外部供电接口升级支持 120 天级长期停泊；鸭翼控制面改为电驱动；喷气发动机启动系统改进缩短了冷态启动时间；逃逸系统引入自适应伞释放逻辑。该批次的改进直接为秃鹫航天飞机的航电架构和长期在轨能力提供了验证。</p>
|
||||
<table>
|
||||
<thead><tr><th>编号</th><th>名称</th><th>首飞</th><th>末飞</th><th>飞行次数</th><th>状态</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>CERV-6</td><td>希望号（Hope）</td><td>2025 年 4 月</td><td>2039 年 10 月</td><td>72</td><td>退役</td></tr>
|
||||
<tr><td>CERV-7</td><td>发现号（Discovery）</td><td>2025 年 11 月</td><td>2040 年 6 月 15 日</td><td>55</td><td>退役，执行末飞任务 CERV-F666</td></tr>
|
||||
<tr><td>CERV-8</td><td>团结号（Unity）</td><td>2026 年 6 月</td><td>2040 年 2 月</td><td>46</td><td>退役</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="运营历史">运营历史</h2>
|
||||
<h3 id="早期验证阶段-2015-2016">早期验证阶段（2015-2016）</h3>
|
||||
<p>验证阶段仅有首批两架轨道器（地平线号和探路者号）可用，先驱者号尚在总装中，飞行频次保持在较低水平。</p>
|
||||
<p>2015 年 6 月，地平线号执飞 CERV-F1，完成首次无人轨道飞行。任务中两侧助推器成功完成了 boost-back burn，但在再入段失联，后续分析判断可能为热防护失效。轨道器段飞行正常，完成主发动机关机、ET 分离、OMS 入轨圆化和无人再入着陆全流程。</p>
|
||||
<p>CERV-F2 至 CERV-F5 任务重点攻克助推器回收，均由地平线号和探路者号交替执飞。CERV-F2 中左侧助推器在 T+77 秒单发失效但仍按预定时间关机，轨道器通过延长 RS-25D 燃烧时间正常入轨；右侧助推器成功反推但着陆点火失败。CERV-F3 中右侧助推器完成反推点火和着陆，但中央发动机 TVC 失效导致溅落后倾覆爆炸。CERV-F4 采用更新航电系统的新助推器设计，两侧均正常溅落。CERV-F5 完成首次助推器全面成功回收，标志着回收全流程达到可运营成熟度。</p>
|
||||
<p>CERV-F12 任务首次使用回收后的助推器执行二次发射，并再次成功回收，完成液体助推器复用的工程闭环。载人认证于 2016 年完成。</p>
|
||||
<h3 id="常态化运营-2017-2040">常态化运营（2017-2040）</h3>
|
||||
<p>2017 年，STS 正式退役，先驱者号入列使首批三架轨道器全部到位，CERV 全面接替载人和货运任务，飞行频次逐步提升。初期任务以国际空间站和天宫空间站的乘员轮换与补给运输为主，同时承担自由飞行科学任务和探测器发射。</p>
|
||||
<p>2020 至 2021 年，第二批轨道器旅行者号和勇气号先后入列，机队规模扩大至 5 架，飞行频次进一步攀升。2025 至 2026 年，第三批轨道器希望号、发现号和团结号先后入列，机队达到 8 架全盛规模，飞行频次在 2026 至 2036 年间达到巅峰。</p>
|
||||
<p>CERV 在运营生涯中参与了多座空间站的建设与运营，承担了大量深空探测任务发射和商业载人飞行。2037 年起，首批轨道器地平线号和探路者号先后退役，飞行频次开始下降。秃鹫航天飞机于 2037 年完成首次无人轨道飞行、2039 年正式服役后，CERV 开始分阶段移交任务。2040 年 6 月 15 日，发现号执飞 CERV-F666，完成 CERV 机队的最后一次飞行任务。机队中的部分轨道器转为地面训练机和博物馆展示品，液体助推器经评估后部分转入秃鹫备件池。</p>
|
||||
|
||||
<h3 id="全生命周期飞行统计">全生命周期飞行统计</h3>
|
||||
<div class="launch-chart" role="img" aria-label="CERV 航天飞机全生命周期年度飞行次数（2015-2040）">
|
||||
<div class="launch-row launch-head"><span>年份</span><span>飞行次数</span><span>次数</span><span>累计</span></div>
|
||||
<div class="launch-stage-label">验证阶段（2 架轨道器）</div>
|
||||
<div class="launch-row"><span>2015</span><span class="launch-track"><span class="launch-bar" style="width:5%;"></span></span><span class="launch-count">2</span><span class="launch-cumulative">2</span></div>
|
||||
<div class="launch-row"><span>2016</span><span class="launch-track"><span class="launch-bar" style="width:12%;"></span></span><span class="launch-count">5</span><span class="launch-cumulative">7</span></div>
|
||||
<div class="launch-stage-label">首批运营（3 架轨道器）</div>
|
||||
<div class="launch-row"><span>2017</span><span class="launch-track"><span class="launch-bar" style="width:19%;"></span></span><span class="launch-count">8</span><span class="launch-cumulative">15</span></div>
|
||||
<div class="launch-row"><span>2018</span><span class="launch-track"><span class="launch-bar" style="width:26%;"></span></span><span class="launch-count">11</span><span class="launch-cumulative">26</span></div>
|
||||
<div class="launch-row"><span>2019</span><span class="launch-track"><span class="launch-bar" style="width:33%;"></span></span><span class="launch-count">14</span><span class="launch-cumulative">40</span></div>
|
||||
<div class="launch-stage-label">第二批入列（5 架轨道器）</div>
|
||||
<div class="launch-row"><span>2020</span><span class="launch-track"><span class="launch-bar" style="width:45%;"></span></span><span class="launch-count">19</span><span class="launch-cumulative">59</span></div>
|
||||
<div class="launch-row"><span>2021</span><span class="launch-track"><span class="launch-bar" style="width:55%;"></span></span><span class="launch-count">23</span><span class="launch-cumulative">82</span></div>
|
||||
<div class="launch-row"><span>2022</span><span class="launch-track"><span class="launch-bar" style="width:62%;"></span></span><span class="launch-count">26</span><span class="launch-cumulative">108</span></div>
|
||||
<div class="launch-row"><span>2023</span><span class="launch-track"><span class="launch-bar" style="width:67%;"></span></span><span class="launch-count">28</span><span class="launch-cumulative">136</span></div>
|
||||
<div class="launch-row"><span>2024</span><span class="launch-track"><span class="launch-bar" style="width:71%;"></span></span><span class="launch-count">30</span><span class="launch-cumulative">166</span></div>
|
||||
<div class="launch-stage-label">第三批入列，全盛期（8 架轨道器）</div>
|
||||
<div class="launch-row"><span>2025</span><span class="launch-track"><span class="launch-bar" style="width:79%;"></span></span><span class="launch-count">33</span><span class="launch-cumulative">199</span></div>
|
||||
<div class="launch-row"><span>2026</span><span class="launch-track"><span class="launch-bar" style="width:88%;"></span></span><span class="launch-count">37</span><span class="launch-cumulative">236</span></div>
|
||||
<div class="launch-row"><span>2027</span><span class="launch-track"><span class="launch-bar" style="width:93%;"></span></span><span class="launch-count">39</span><span class="launch-cumulative">275</span></div>
|
||||
<div class="launch-row"><span>2028</span><span class="launch-track"><span class="launch-bar" style="width:98%;"></span></span><span class="launch-count">41</span><span class="launch-cumulative">316</span></div>
|
||||
<div class="launch-row"><span>2029</span><span class="launch-track"><span class="launch-bar" style="width:90%;"></span></span><span class="launch-count">38</span><span class="launch-cumulative">354</span></div>
|
||||
<div class="launch-row"><span>2030</span><span class="launch-track"><span class="launch-bar" style="width:100%;"></span></span><span class="launch-count">42</span><span class="launch-cumulative">396</span></div>
|
||||
<div class="launch-row"><span>2031</span><span class="launch-track"><span class="launch-bar" style="width:95%;"></span></span><span class="launch-count">40</span><span class="launch-cumulative">436</span></div>
|
||||
<div class="launch-row"><span>2032</span><span class="launch-track"><span class="launch-bar" style="width:86%;"></span></span><span class="launch-count">36</span><span class="launch-cumulative">472</span></div>
|
||||
<div class="launch-row"><span>2033</span><span class="launch-track"><span class="launch-bar" style="width:86%;"></span></span><span class="launch-count">36</span><span class="launch-cumulative">508</span></div>
|
||||
<div class="launch-row"><span>2034</span><span class="launch-track"><span class="launch-bar" style="width:81%;"></span></span><span class="launch-count">34</span><span class="launch-cumulative">542</span></div>
|
||||
<div class="launch-row"><span>2035</span><span class="launch-track"><span class="launch-bar" style="width:71%;"></span></span><span class="launch-count">30</span><span class="launch-cumulative">572</span></div>
|
||||
<div class="launch-row"><span>2036</span><span class="launch-track"><span class="launch-bar" style="width:71%;"></span></span><span class="launch-count">30</span><span class="launch-cumulative">602</span></div>
|
||||
<div class="launch-stage-label">首批退役，逐步移交（6→4 架轨道器）</div>
|
||||
<div class="launch-row"><span>2037</span><span class="launch-track"><span class="launch-bar" style="width:52%;"></span></span><span class="launch-count">22</span><span class="launch-cumulative">624</span></div>
|
||||
<div class="launch-row"><span>2038</span><span class="launch-track"><span class="launch-bar" style="width:45%;"></span></span><span class="launch-count">19</span><span class="launch-cumulative">643</span></div>
|
||||
<div class="launch-row"><span>2039</span><span class="launch-track"><span class="launch-bar" style="width:36%;"></span></span><span class="launch-count">15</span><span class="launch-cumulative">658</span></div>
|
||||
<div class="launch-row"><span>2040</span><span class="launch-track"><span class="launch-bar highlight" style="width:19%;"></span></span><span class="launch-count">8</span><span class="launch-cumulative"><b>666</b></span></div>
|
||||
</div>
|
||||
<p style="font-size:90%; color:#54595d;">红色高亮条为 2040 年，发现号执飞末飞任务 CERV-F666。验证阶段仅 2 架轨道器可用，飞行频次较低；第二批入列后频次逐步攀升；第三批入列后达到全盛期（峰值 42 次/年，2030 年）；末期因首批退役和秃鹫航天飞机接替逐步降低频次。</p>
|
||||
|
||||
<h2 id="重要载荷">重要载荷</h2>
|
||||
<h3 id="空间站建设与运营">空间站建设与运营</h3>
|
||||
<p>CERV 参与了多座空间站的建设与运营。在边疆空间站和凌霄宫空间站建造之前，CERV 主要承担国际空间站和天宫空间站的乘员轮换、补给运输和故障设备回收任务，积累了大量的在轨对接和长期停泊运营经验。</p>
|
||||
<p>边疆空间站（Front Station）于 2030 年启动建设，2035 年竣工，后更名为启明空间站。该站是 CERV 时代首个由航天飞机继承线主导建造的大型轨道设施，采用模块化桁架结构。CERV 为其运送了核心桁架段、太阳能电池翼、散热器、节点舱和多个加压实验模块，累计执行超过 50 次建设飞行。2030 至 2035 年的建设高峰期间，CERV 机队将约 30% 的年度飞行频次投入边疆站建设。</p>
|
||||
<p>凌霄宫空间站于 2033 年启动建设，2037 年竣工。该站为近地轨道大型永久设施，CERV 为其运送了核心舱段、实验舱、太阳能阵列、加压对接适配器和外部实验平台。凌霄宫建设与边疆站建设在 2033-2035 年间重叠，CERV 机队的 8 架轨道器在此期间同时支持两座空间站的并行建造，是 CERV 运营史上任务强度最高的时期之一。在两座空间站的运营阶段，CERV 持续提供乘员轮换、补给运输和设备回收服务，是连接地面和轨道设施的核心物流载体。</p>
|
||||
<h3 id="太空旅游">太空旅游</h3>
|
||||
<p>CERV 多次参与太空游客计划，累计搭载超过 100 名太空游客进入轨道。2024 年，CERV 执行了首次全商业乘员飞行任务，将 6 名付费乘客和 2 名专业航天员送入国际空间站，驻留 8 天后安全返回，标志着 CERV 正式进入商业载人市场。边疆空间站和凌霄宫空间站建成之前，CERV 的商业乘员任务主要以国际空间站、天宫空间站和自由飞行轨道体验为目的地。此后，CERV 每年安排 1-2 次商业乘员任务。</p>
|
||||
<p>游客构成从早期的高净值个人逐渐扩展至企业赞助的研究人员、教育项目的教师代表和国际合作任务的文化交流使者。CERV 的 8 人乘员容量和全自动飞行能力使其在商业载人市场中具有较高的任务灵活性——可在不增加专业航天员配置的情况下搭载更多付费乘客。2030 年，CERV 首次执行了完全由自动系统控制的商业轨道飞行任务，全程无需飞行员手动干预，进一步降低了商业任务的运营成本。边疆空间站和凌霄宫空间站竣工后，商业乘员任务的目的地扩展至这两座新建设施。累计超过 100 名游客的飞行记录使 CERV 成为同时代载人航天商业化程度最高的轨道飞行器。</p>
|
||||
<h3 id="深空探测任务支持">深空探测任务支持</h3>
|
||||
<p>CERV 在深空探测领域的主要角色是探测器与上面级组合体的发射平台。利用 30 吨上行能力和 18.3 米货舱长度，CERV 可将大型上面级及其搭载的探测器一次送入近地轨道，由上面级负责后续的地月转移、行星际注入或深空巡航。</p>
|
||||
<p>全生命周期中，CERV 累计执行了 25 次火星探测任务发射。代表任务包括 2022 年发射的"火星样本返回"轨道器与着陆器组合体、2028 年部署的"火星全球高分辨率测绘"星座（4 颗卫星由一次 CERV 任务送入轨道后分批进入火星轨道）、以及 2034 年发射的载人火星任务预置补给舱。77 次月球任务涵盖了嫦娥后续工程的轨道器、着陆器和采样返回器，以及国际合作的月球门户舱段和商业月球着陆器。18 次金星任务包括轨道雷达测绘卫星和大气探测试验器。42 次外太阳系任务覆盖了木星冰卫星轨道器、土星大气探测器、天王星和海王星飞越探测器，以及多颗柯伊伯带天体探测任务。</p>
|
||||
<p>CERV 在执行这类任务时的优势在于其货舱容积和返回能力：部分探测器在入轨部署前可利用 CERV 在轨期间的乘组进行检查、调试和必要时的手动干预，降低了高风险深空任务的前期不确定性。探测器出现问题无法部署时，CERV 还可将其带回地面进行分析和修复，避免了高价值科学载荷的完全损失。</p>
|
||||
<h3 id="在轨服务与维护">在轨服务与维护</h3>
|
||||
<p>CERV 执行了哈勃空间望远镜的回收任务。2032 年，哈勃望远镜的姿态控制系统和科学仪器电源模块先后出现不可修复的故障，NASA 决定由 CERV 将其完整带回地面。执行该任务的先驱者号与哈勃成功交会后，乘组通过 EVA 将望远镜收纳入货舱并固定，随后安全返回卡纳维拉尔角 SLF。回收后的哈勃望远镜经修复后陈列于史密森尼国家航空航天博物馆。</p>
|
||||
<p>CERV 还支持了巡天望远镜的部署和维护任务。巡天望远镜于 2030 年由 CERV 送入日地 L2 转移轨道，此后 CERV 多次执行巡天望远镜的维护任务——包括仪器更换、制冷剂补充和陀螺仪替换。与哈勃时代依赖航天飞机进行在轨维护不同，巡天望远镜的维护任务结合了 CERV 的载人运输能力和望远镜自身的模块化服务设计，大幅缩短了每次维护的 EVA 时间。</p>
|
||||
<h3 id="深空通讯网-20">深空通讯网 2.0</h3>
|
||||
<p>深空通讯网 2.0 是 CERV 参与的最具系统性的基础设施项目之一。该项目旨在将原有的地面深空通讯网络扩展为天地一体化的中继通讯体系，在月球和火星轨道部署专用中继卫星网络，为载人深空探索和无人探测任务提供连续、高带宽的通讯覆盖。</p>
|
||||
<p>CERV 承担了鹊桥中继卫星网络的月球轨道部署任务。鹊桥网络由 6 颗中继卫星组成，分布在月球近直线晕轨道和远月逆行轨道上，为月球背面、南极和远月面提供全天候通讯中继。CERV 分 3 次任务将 6 颗卫星送入地月转移轨道，每次任务携带 2 颗卫星和一个固体上面级。首颗鹊桥卫星于 2026 年入轨，网络于 2028 年完成部署并投入运营。</p>
|
||||
<p>萤火虫中继卫星网络服务于火星轨道，由 8 颗中继卫星组成。CERV 分 4 次任务完成发射，每次携带 2 颗卫星和一套火星转移级。与鹊桥网络的发射方式类似，CERV 将组合体送入近地轨道后由上面级完成火星转移和入轨。萤火虫网络于 2033 年完成部署，为后续的火星表面探测、样本返回和载人任务准备提供了通讯基础设施。</p>
|
||||
<p>CERV 在深空通讯网 2.0 项目中的角色不仅限于发射。在卫星在轨部署前，CERV 乘组可在货舱内对卫星进行最终状态检查和功能验证；部分卫星部署后出现异常时，CERV 还可执行近距离检查和修复任务。这一"发射+检查+修复"的综合能力使 CERV 成为大型通讯基础设施项目中的独特资产。</p>
|
||||
|
||||
<h2 id="与-sts-和秃鹫航天飞机的关系">与 STS 和秃鹫航天飞机的关系</h2>
|
||||
<p>CERV 作为第二代航天飞机，向前继承第一代 STS 的运载能力和任务运营体系，向后为第三代秃鹫航天飞机提供液体助推器、乘员逃逸和气动布局的工程基础。</p>
|
||||
<p>该级与 STS 相比，在安全架构上实现了根本性升级——整体式乘员逃逸、液体助推器节流和中止能力、电传飞控、喷气发动机着陆辅助和复飞——但任务模式和运力级别仍处于 STS 级范畴。CERV 不是航天飞机继承线的性能飞跃，而是该继承线补齐安全短板、延续运营能力和积累新一代工程数据的过渡代。</p>
|
||||
<p>该级与秃鹫航天飞机相比，在规模、运力、重载能力和深空支援任务方面存在代差。CERV 的 30 吨上行运力和 8.4 米 ET 不足以支持母舰分段建造和高轨重型部署任务；秃鹫航天飞机则将运力提升至 120 吨级低月轨能力，并采用 10 米级 ET 和 5 米级助推器，承接 CERV 之后的航天飞机继承线重任。CERV 第三批轨道器的综合航电平台、120 天级长期停泊能力和改进型喷气发动机启动系统等设计经验和飞行数据直接输出了秃鹫项目的设计评审。</p>
|
||||
<p>在 CERV 退役之后，航天飞机继承线继续发展：回声级航天飞机（Echo Shuttle）于 2056 年首飞、2057 年服役，进取级航天飞机（Enterprise Shuttle）于 2057 年首飞、2058 年服役，两者均为第四代 SSTO 能力航天飞机，与秃鹫航天飞机Block 2 共同构成 2050 年代后期的航天飞机机队。</p>
|
||||
<p>在航天飞机体系中，CERV 的工程贡献集中体现在多个方面：液体助推器验证了节流、回收和复用全流程，使该路线在秃鹫项目中成为主导方案而非冒险方案；整体式乘员舱全阶段逃逸验证了分离、动力转移、姿态控制和着陆回收的全流程，确立此后航天飞机的乘员安全范式；三个批次的渐进式改进——从第一代的基线设计经第二代运营反馈优化到第三代增强型配置——为航天飞机的迭代开发和批次管理提供了范例；复合材料机身积累了铝合金—复合材料混合结构在再入热循环、长期疲劳和维护环境中的长期数据；改进型通用隔热瓦和隔热涂层体系验证了热防护冗余设计；ET 涂层加泡沫双层保温方案提供了比纯泡沫方案更安全的保温路径。</p>
|
||||
<table>
|
||||
<thead><tr><th>世代</th><th>型号</th><th>定位</th><th>核心技术贡献</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>第一代</td><td>STS 航天飞机</td><td>确立垂直发射/水平着陆范式和地面运营体系。</td><td>轨道器+ET+助推器构型、RS-25 发动机、热防护体系、在轨操作。</td></tr>
|
||||
<tr><td>第二代</td><td>CERV 航天飞机</td><td>安全改进型，补齐乘员逃生和着陆灵活性短板。分三批次渐进改进。</td><td>复合材料减重、液体助推器回收（50 次/10 次维护）、整体式乘员全阶段逃逸、翼尖双垂尾+鸭翼、电传飞控全自动着陆、喷气发动机着陆辅助和复飞、通用隔热瓦+隔热涂层、ET 涂层+泡沫双层保温、液氧/煤油双组元 RCS、气闸舱和可伸缩通用对接口。</td></tr>
|
||||
<tr><td>第三代</td><td>秃鹫航天飞机</td><td>重载型，放大构型面向母舰建造和高轨重载运输。</td><td>继承并放大 CERV 的全部核心技术路线；MK4 轨道器、10 m ET、5 m 助推器（75 次免维护/200-300 次全寿命）。</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="技术参数">技术参数</h2>
|
||||
<table>
|
||||
<thead><tr><th>项目</th><th>数据</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>全称</td><td>Composite Enhanced Reusable Vehicle</td></tr>
|
||||
<tr><td>中文译名</td><td>复合增强可重复使用运载器</td></tr>
|
||||
<tr><td>类型</td><td>可重复使用载人航天飞机（第二代）</td></tr>
|
||||
<tr><td>前身</td><td>STS 航天飞机（第一代）</td></tr>
|
||||
<tr><td>后继</td><td>秃鹫航天飞机（第三代）</td></tr>
|
||||
<tr><td>首飞</td><td>2015 年 6 月（CERV-F1，地平线号执飞）</td></tr>
|
||||
<tr><td>末飞</td><td>2040 年 6 月 15 日（CERV-F666，发现号执飞）</td></tr>
|
||||
<tr><td>总飞行次数</td><td>666 次</td></tr>
|
||||
<tr><td>发射场</td><td>文昌航天发射场 / 卡纳维拉尔角</td></tr>
|
||||
<tr><td>主要着陆场</td><td>卡纳维拉尔角 Shuttle Landing Facility / 文昌航天器着陆跑道；任何 CAT III 跑道 >3,000 m 的民用机场可作为备降场</td></tr>
|
||||
<tr><th colspan="2">轨道器</th></tr>
|
||||
<tr><td>机身结构</td><td>铝合金—复合材料混合结构</td></tr>
|
||||
<tr><td>干重</td><td>63 吨</td></tr>
|
||||
<tr><td>全长</td><td>轨道器 36 米 / 组合体 55.4 米</td></tr>
|
||||
<tr><td>翼展</td><td>24.3 米</td></tr>
|
||||
<tr><td>最大起飞重量</td><td>2,169.9 吨（含 30 吨载荷）</td></tr>
|
||||
<tr><td>气动布局</td><td>后掠三角翼、翼尖双垂尾、前置鸭翼</td></tr>
|
||||
<tr><td>热防护</td><td>改进型通用隔热瓦 + 隔热涂层冗余防护；机翼前缘和机头使用增强碳碳材料</td></tr>
|
||||
<tr><td>飞控</td><td>电传飞控（fly-by-wire），冗余架构，全阶段全自动飞行（含着陆）</td></tr>
|
||||
<tr><td>喷气发动机</td><td>2 台涡扇发动机，着陆辅助/复飞；复飞需开加力燃烧器</td></tr>
|
||||
<tr><td>对接口</td><td>可伸缩式 1.875 m 通用对接口</td></tr>
|
||||
<tr><td>EVA 设施</td><td>内置气闸舱</td></tr>
|
||||
<tr><th colspan="2">推进系统</th></tr>
|
||||
<tr><td>主发动机</td><td>3× RS-25D 液氢液氧分级燃烧发动机</td></tr>
|
||||
<tr><td>外挂燃料箱</td><td>8.4 米直径；保温涂层 + 保温泡沫双层设计；燃料量 955.3 吨；干重 28.5 吨</td></tr>
|
||||
<tr><td>助推器</td><td>2× 4 米直径液体燃料助推器，各 9× TH-12（增推版），单台真空推力 1,132.67 kN；单侧干重 24.5 吨，单侧燃料量 497.8 吨；RTLS 返场着陆；设计寿命 50 次，每 10 次需维护</td></tr>
|
||||
<tr><td>OMS 燃料量</td><td>23.44 吨</td></tr>
|
||||
<tr><td>喷气发动机燃料量</td><td>6 吨</td></tr>
|
||||
<tr><td>助推器 RCS</td><td>液氧/煤油双组元 RCS</td></tr>
|
||||
<tr><td>OMS</td><td>2× 60 kN 常温燃料发动机，燃料与逃逸引擎通用</td></tr>
|
||||
<tr><td>逃逸动力</td><td>2× 固体燃料推进器（地面至 100 km 初始分离）+ 4× 双组元常温燃料发动机（乘员舱脱离 5 m 后同步点火）；全阶段可用（地面/飞行/再入）</td></tr>
|
||||
<tr><th colspan="2">乘员与载荷</th></tr>
|
||||
<tr><td>乘员容量</td><td>8 人（常规 2 名飞行员 + 0-6 名任务人员）</td></tr>
|
||||
<tr><td>飞行能力</td><td>全阶段全自动飞行（含着陆）</td></tr>
|
||||
<tr><td>上行载荷</td><td>30 吨（600×600 km × 51°）</td></tr>
|
||||
<tr><td>返回载荷</td><td>20 吨</td></tr>
|
||||
<tr><td>货舱尺寸</td><td>约 18.3 m × 4.6 m</td></tr>
|
||||
<tr><th colspan="2">电源与自持</th></tr>
|
||||
<tr><td>电源</td><td>2× 燃料电池，可支持 35 天自由飞行</td></tr>
|
||||
<tr><td>生命维持</td><td>支持 30 天（自由飞行），外部供电时最长 120 天（驻留空间站/轨道船坞）</td></tr>
|
||||
<tr><td>外部供电</td><td>支持通过 1.875 m 通用对接口接收外部电力输入</td></tr>
|
||||
<tr><th colspan="2">机队</th></tr>
|
||||
<tr><td>轨道器数量</td><td>8 架，分三批次（第一批 3 架 / 第二批 2 架 / 第三批 3 架）</td></tr>
|
||||
<tr><td>测试机</td><td>3 架（CTV-1、CTV-2、CTV-3）</td></tr>
|
||||
<tr><td>总飞行次数</td><td>666 次</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="评价">评价</h2>
|
||||
<p>CERV 航天飞机是航天飞机继承线从第一代（STS）向第三代（秃鹫）过渡的关键型号。该级以哥伦比亚事故的安全教训为核心驱动，在保留 STS 任务范式的前提下，系统性地解决了上升段乘员逃生、助推器不可回收、结构重量偏高、热防护维护成本高和着陆灵活性不足等多项短板，使航天飞机体系在 2010 至 2040 年间得以持续运营，并为下一代技术积累了大量飞行数据。</p>
|
||||
<p>该级的主要工程贡献包括：首次在载人航天飞机上实现整体式乘员舱全阶段逃逸，固体/常温燃料两级动力配置覆盖从发射台到再入的完整飞行剖面；首次以液体燃料可回收助推器替代固体助推器，以前五次飞行任务逐步攻克 boost-back、再入热防护、姿态控制、航电和着陆全流程，并在 CERV-F12 完成复用闭环；以复合材料实现约 19% 的轨道器结构减重，并验证了混合结构在再入热循环和长期疲劳环境中的可用性；通过翼尖双垂尾和鸭翼布局替代单片中央垂尾，与喷气发动机着陆辅助和电传飞控配合，使航天飞机首次具备全自动着陆和复飞能力；改进型通用隔热瓦加隔热涂层的双层热防护体系降低了维护成本并提供了冗余防护；ET 保温涂层加保温泡沫方案减少了泡沫脱落风险。三批次渐进改进模式——从基线设计经运营反馈至增强配置——为航天飞机的迭代开发和批次管理提供了完整的工程范例。</p>
|
||||
<p>CERV 在运营领域的成就同样突出。通过参与凌霄宫和启明空间站的建设运营、累计搭载超过 100 名太空游客、执行 162 次深空探测任务发射、完成哈勃望远镜回收和巡天望远镜部署维护、以及部署鹊桥和萤火虫中继卫星网络，CERV 将其能力从航天飞机继承线的安全过渡平台扩展为同时代最具任务多样性的轨道飞行器之一。该型号的"发射+在轨检查+必要时带回"能力在深空探测任务和大型通讯基础设施项目中体现出了不可替代的价值。</p>
|
||||
<p>CERV 的限制同样明确：该级不追求运力代际跃升——30 吨上行和 20 吨返回的载荷能力仍属 STS 量级；8.4 米 ET 和 RS-25D 主发动机构型限制了进一步放大的空间；助推器 50 次寿命和 10 次维护间隔在工程上可行，但维护成本较高，无法满足后续重载系统的高频次复用需求；复合材料机身虽然验证了减重路径，但 2040 年退役时其累计疲劳寿命数据尚不足以直接支撑更大尺寸的秃鹫轨道器复合材料机身决策——后者最终仍以铝合金为主结构。Vulture 助推器的长寿命改进（免维护 75 次、维护后 200-300 次）正是基于 CERV 助推器运营数据中识别出的涡轮泵、推力室和热防护瓶颈。</p>
|
||||
<p>在航天飞机体系中，CERV 完成了从"一次性固体助推器 + 无逃生轨道器"的第一代模式到"可复用液体助推器 + 全阶段乘员逃逸轨道器"的第三代模式的核心工程切换。该级不承担秃鹫航天飞机改进乙型的重载干线角色，不涉及回声级/进取级的 SSTO 技术路线，也不参与星际探索母舰的推进和部署，但作为第二代航天飞机承前启后，使航天飞机继承线从 STS 时代安全过渡至 Vulture 时代。</p>
|
||||
|
||||
<h2 id="相关条目">相关条目</h2>
|
||||
<ul>
|
||||
<li><a href="/home/Space_Shuttles/Vulture_Shuttle">秃鹫航天飞机</a></li>
|
||||
<li><a href="/home/Space_Shuttles/Vulture_Shuttle_Block_2">秃鹫航天飞机改进乙型</a></li>
|
||||
<li><a href="/home/Space_Shuttles/Echo_Shuttle">回声级航天飞机</a></li>
|
||||
<li><a href="/home/Space_Shuttles/Enterprise_Shuttle">进取级航天飞机</a></li>
|
||||
<li><a href="/home/Exploration_Motherships/Xihe">羲和级星际探索母舰</a></li>
|
||||
<li><a href="/home/Exploration_Motherships/Stellaria">万星源级星际探索母舰</a></li>
|
||||
<li>凌霄宫空间站</li>
|
||||
<li>启明空间站</li>
|
||||
<li>巡天望远镜</li>
|
||||
<li>哈勃空间望远镜</li>
|
||||
<li>STS 航天飞机</li>
|
||||
<li>RS-25 发动机</li>
|
||||
<li>TH-12 发动机</li>
|
||||
</ul>
|
||||
</article>
|
||||
<script>
|
||||
(function () {
|
||||
function ready(fn) {
|
||||
if (document.readyState === 'loading') {
|
||||
document.addEventListener('DOMContentLoaded', fn, { once: true });
|
||||
} else {
|
||||
fn();
|
||||
}
|
||||
}
|
||||
|
||||
function captionFor(image) {
|
||||
var container = image.closest('figure, td, tr, .infobox-image');
|
||||
if (!container) {
|
||||
return image.alt || '';
|
||||
}
|
||||
var caption = container.querySelector('.thumbcaption');
|
||||
return caption ? caption.textContent.trim() : (image.alt || '');
|
||||
}
|
||||
|
||||
function install(article) {
|
||||
if (!article || article.dataset.lightboxReady === '1') {
|
||||
return;
|
||||
}
|
||||
article.dataset.lightboxReady = '1';
|
||||
|
||||
var overlay = document.createElement('div');
|
||||
overlay.className = 'wiki-image-lightbox';
|
||||
overlay.hidden = true;
|
||||
overlay.innerHTML = '<figure class="wiki-image-lightbox-panel" role="dialog" aria-modal="true"><button class="wiki-image-lightbox-close" type="button" aria-label="Close image preview">x</button><img alt=""><figcaption class="thumbcaption"></figcaption></figure>';
|
||||
document.body.appendChild(overlay);
|
||||
|
||||
var previewImage = overlay.querySelector('img');
|
||||
var previewCaption = overlay.querySelector('figcaption');
|
||||
var closeButton = overlay.querySelector('.wiki-image-lightbox-close');
|
||||
|
||||
function closePreview() {
|
||||
overlay.hidden = true;
|
||||
previewImage.removeAttribute('src');
|
||||
previewCaption.textContent = '';
|
||||
document.body.classList.remove('wiki-image-lightbox-open');
|
||||
}
|
||||
|
||||
function openPreview(image, event) {
|
||||
event.preventDefault();
|
||||
event.stopPropagation();
|
||||
if (event.stopImmediatePropagation) {
|
||||
event.stopImmediatePropagation();
|
||||
}
|
||||
previewImage.src = image.currentSrc || image.src;
|
||||
previewImage.alt = image.alt || '';
|
||||
previewCaption.textContent = captionFor(image);
|
||||
overlay.hidden = false;
|
||||
document.body.classList.add('wiki-image-lightbox-open');
|
||||
closeButton.focus();
|
||||
}
|
||||
|
||||
Array.prototype.forEach.call(article.querySelectorAll('img[data-wiki-asset]'), function (image) {
|
||||
if (image.dataset.lightboxBound === '1') {
|
||||
return;
|
||||
}
|
||||
image.dataset.lightboxBound = '1';
|
||||
image.addEventListener('click', function (event) {
|
||||
openPreview(image, event);
|
||||
}, true);
|
||||
});
|
||||
|
||||
article.addEventListener('click', function (event) {
|
||||
var image = event.target.closest && event.target.closest('img[data-wiki-asset]');
|
||||
if (!image || !article.contains(image) || image.closest('.wiki-image-lightbox')) {
|
||||
return;
|
||||
}
|
||||
openPreview(image, event);
|
||||
});
|
||||
|
||||
closeButton.addEventListener('click', closePreview);
|
||||
overlay.addEventListener('click', function (event) {
|
||||
if (event.target === overlay) {
|
||||
closePreview();
|
||||
}
|
||||
});
|
||||
document.addEventListener('keydown', function (event) {
|
||||
if (event.key === 'Escape' && !overlay.hidden) {
|
||||
closePreview();
|
||||
}
|
||||
});
|
||||
}
|
||||
|
||||
function installAll() {
|
||||
Array.prototype.forEach.call(document.querySelectorAll('.wiki-article, .vulture-article'), install);
|
||||
}
|
||||
|
||||
ready(function () {
|
||||
installAll();
|
||||
if (window.MutationObserver) {
|
||||
var observer = new MutationObserver(installAll);
|
||||
observer.observe(document.body, { childList: true, subtree: true });
|
||||
}
|
||||
window.setTimeout(installAll, 500);
|
||||
window.setTimeout(installAll, 1500);
|
||||
window.setTimeout(installAll, 3000);
|
||||
});
|
||||
}());
|
||||
</script>
|
||||
@@ -74,9 +74,11 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td><b>Maximum takeoff mass</b>: 60 t</td></tr>
|
||||
<tr><td><b>Payload</b>: 15 t</td></tr>
|
||||
<tr><td><b>Crew/passengers</b>: 3 crew + 4 passengers; cargo-bay crew segment can add 4 more</td></tr>
|
||||
<tr><td><b>Status</b>: In service</td></tr>
|
||||
<tr><td><b>First flight</b>: 2056</td></tr>
|
||||
<tr><td><b>Service entry</b>: 2057</td></tr>
|
||||
<tr><td><b>Status</b>: In service (early operational phase)</td></tr>
|
||||
</tbody></table>
|
||||
<p>The <b>Echo Shuttle</b> is a light fully reusable shuttle developed after the introduction of <a href="/home/Space_Shuttles/Vulture_Shuttle_Block_2">Vulture Shuttle Block 2</a>. It is the smaller member of the Echo / Enterprise paired-shuttle program, created to cover high-frequency crew rotation, small cargo transfer, station servicing, rescue standby, mothership docking, and planetary surface shuttle work without using the much larger Vulture stack.</p>
|
||||
<p>The <b>Echo Shuttle</b> is a light fully reusable shuttle developed after the introduction of <a href="/home/Space_Shuttles/Vulture_Shuttle_Block_2">Vulture Shuttle Block 2</a>. It is the smaller member of the Echo / Enterprise paired-shuttle program, created to cover high-frequency crew rotation, small cargo transfer, station servicing, rescue standby, mothership docking, and planetary surface shuttle work without using the much larger Vulture stack. First flown in 2056 and entering crew service in 2057, Echo is in its early operational phase; as of March 2060 approximately 75 flights have been completed across about four years of service.</p>
|
||||
<p>Echo combines winged atmospheric re-entry and runway landing with vertical takeoff and landing capability. This lets it operate from conventional spaceports as well as from lunar, Martian, or other low-gravity surface sites where runways are unavailable. Its operational role sits between a shuttlecraft and a surface-to-orbit transport: smaller than Enterprise, far smaller than Vulture, but capable of independent orbital maneuvering and high-energy return braking.</p>
|
||||
<p>The vehicle carries 15.3 t of high-energy liquid fuel, uses two XP-F700 "Cooper" nuclear aerospike main engines, and is designed for fully uncrewed flight when required. In normal crew service it carries 3 crew and 4 passengers; a cargo-bay crew segment can add 4 additional occupants, with life support rated for 11 people for 40 days.</p>
|
||||
<p>In Xihe-class and Stellaria-class exploration mothership operations, Echo is the common externally berthed ferry shuttle. A mothership can carry two Echo shuttles, or replace them with other compatible vehicles, for crew transfer, light cargo, sample return, and emergency evacuation after the mothership reaches its target planetary system.</p>
|
||||
@@ -144,27 +146,27 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<p>The normal passenger configuration is 3 crew plus 4 passengers. The cargo-bay crew segment adds 4 seats for evacuation or temporary surge operations. The 11-person, 40-day life-support rating is primarily a contingency margin for rescue delays, weather closure, mothership docking waits, or transfer-window shifts rather than a normal full-duration passenger mode.</p>
|
||||
<p>Within the wider shuttle system, Vulture performs trunk-line heavy transport, Enterprise carries medium passenger and cargo batches near major nodes, and Echo handles the final fast link. Large missions often use all three: Vulture brings heavy equipment into the cislunar network, Enterprise supports mothership construction, refit, supply, and near-range transfer, and Echo completes the carried expedition shuttle leg or emergency support task.</p>
|
||||
<h2 id="operational-history">Operational history</h2>
|
||||
<p>Echo completed its early certification campaign in the first half of the 2060s. Initial flights focused on VTVL control laws, lifting-body low-speed handling, high-orbit braking, and autonomous docking. After crew certification, Echo entered service for near-Earth facilities, lunar bases, and later interplanetary exploration motherships.</p>
|
||||
<p>Echo completed its early certification campaign in 2056-2057. Initial flights in 2056 focused on VTVL control laws, lifting-body low-speed handling, and runway operations. Crew certification followed in 2057 with the first crewed orbital mission, after which Echo entered service for near-Earth facilities, lunar bases, and later interplanetary exploration motherships. As of March 2060, the fleet has accumulated approximately 75 flights and remains in its early operational phase.</p>
|
||||
<table>
|
||||
<thead><tr><th>Mission</th><th>Year</th><th>Objective</th><th>Result</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>EC-V1</td><td>2060</td><td>First complete VTVL takeoff, hover, and autonomous landing</td><td>Validated four-engine auxiliary control.</td></tr>
|
||||
<tr><td>EC-R2</td><td>2060</td><td>Runway takeoff and horizontal landing test</td><td>Verified low-speed handling and go-around logic.</td></tr>
|
||||
<tr><td>EC-O1</td><td>2061</td><td>First uncrewed orbital flight and runway return</td><td>Main-engine burn and re-entry data were within limits.</td></tr>
|
||||
<tr><td>EC-C1</td><td>2062</td><td>First crewed orbital mission</td><td>Certified the 3+4 configuration, orbital TPS inspection, and emergency 11-person mode.</td></tr>
|
||||
<tr><td>EC-L1</td><td>2063</td><td>First lunar base shuttle mission</td><td>Completed low-gravity landing, unloading, and crew return.</td></tr>
|
||||
<tr><td>EC-M2</td><td>2064</td><td>First mothership berthing mission</td><td>Verified dorsal docking loads and mothership procedures.</td></tr>
|
||||
<tr><td>EC-V1</td><td>2056</td><td>First complete VTVL takeoff, hover, and autonomous landing</td><td>Validated four-engine auxiliary control.</td></tr>
|
||||
<tr><td>EC-R2</td><td>2056</td><td>Runway takeoff and horizontal landing test</td><td>Verified low-speed handling and go-around logic.</td></tr>
|
||||
<tr><td>EC-O1</td><td>2057</td><td>First uncrewed orbital flight and runway return</td><td>Main-engine burn and re-entry data were within limits.</td></tr>
|
||||
<tr><td>EC-C1</td><td>2057</td><td>First crewed orbital mission</td><td>Certified the 3+4 configuration, orbital TPS inspection, and emergency 11-person mode.</td></tr>
|
||||
<tr><td>EC-L1</td><td>2058</td><td>First lunar base shuttle mission</td><td>Completed low-gravity landing, unloading, and crew return.</td></tr>
|
||||
<tr><td>EC-M2</td><td>2058</td><td>First mothership berthing mission</td><td>Verified dorsal docking loads and mothership procedures.</td></tr>
|
||||
</tbody></table>
|
||||
<div class="launch-chart" role="img" aria-label="Echo Shuttle flight count chart">
|
||||
<div class="launch-row launch-head"><span>Year</span><span>Flights</span><span>No.</span><span>Total</span></div>
|
||||
<div class="launch-stage-label">Validation phase</div>
|
||||
<div class="launch-row"><span>2060</span><span class="launch-track"><span class="launch-bar" style="width:11%;"></span></span><span class="launch-count">8</span><span class="launch-cumulative">8</span></div>
|
||||
<div class="launch-row"><span>2061</span><span class="launch-track"><span class="launch-bar" style="width:15%;"></span></span><span class="launch-count">11</span><span class="launch-cumulative">19</span></div>
|
||||
<div class="launch-row"><span>2062</span><span class="launch-track"><span class="launch-bar" style="width:25%;"></span></span><span class="launch-count">18</span><span class="launch-cumulative">37</span></div>
|
||||
<div class="launch-stage-label">Routine operations</div>
|
||||
<div class="launch-row"><span>2063</span><span class="launch-track"><span class="launch-bar" style="width:50%;"></span></span><span class="launch-count">36</span><span class="launch-cumulative">73</span></div>
|
||||
<div class="launch-row"><span>2064</span><span class="launch-track"><span class="launch-bar" style="width:75%;"></span></span><span class="launch-count">54</span><span class="launch-cumulative">127</span></div>
|
||||
<div class="launch-row"><span>2065</span><span class="launch-track"><span class="launch-bar" style="width:100%;"></span></span><span class="launch-count">72</span><span class="launch-cumulative">199</span></div>
|
||||
<div class="launch-row"><span>2056</span><span class="launch-track"><span class="launch-bar" style="width:17%;"></span></span><span class="launch-count">5</span><span class="launch-cumulative">5</span></div>
|
||||
<div class="launch-stage-label">Crew certification & early ops</div>
|
||||
<div class="launch-row"><span>2057</span><span class="launch-track"><span class="launch-bar" style="width:40%;"></span></span><span class="launch-count">12</span><span class="launch-cumulative">17</span></div>
|
||||
<div class="launch-row"><span>2058</span><span class="launch-track"><span class="launch-bar" style="width:67%;"></span></span><span class="launch-count">20</span><span class="launch-cumulative">37</span></div>
|
||||
<div class="launch-row"><span>2059</span><span class="launch-track"><span class="launch-bar" style="width:100%;"></span></span><span class="launch-count">30</span><span class="launch-cumulative">67</span></div>
|
||||
<div class="launch-stage-label">Current (through March 2060)</div>
|
||||
<div class="launch-row"><span>2060</span><span class="launch-track"><span class="launch-bar" style="width:27%;"></span></span><span class="launch-count">~8</span><span class="launch-cumulative">~75</span></div>
|
||||
</div>
|
||||
<h2 id="safety-and-incidents">Safety and incidents</h2>
|
||||
<figure class="thumb tright"><a class="media-link" href="#echo-img-return"><img src="/echo/echo_high_energy_return_braking.png" alt="Echo Shuttle high-energy return braking" data-wiki-asset="/echo/echo_high_energy_return_braking.png"></a><figcaption class="thumbcaption">High-orbit and lunar-return missions require main-engine braking before atmospheric entry.</figcaption></figure>
|
||||
|
||||
@@ -69,8 +69,8 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td><b>世代定位</b>：秃鹫航天飞机改进乙型之后的并行补充型号</td></tr>
|
||||
<tr><td><b>计划关系</b>：回声级 / 进取级轻重双型号计划</td></tr>
|
||||
<tr><td><b>核心定位</b>：星际探索母舰随舰摆渡航天飞机与目标系统末端运输载具</td></tr>
|
||||
<tr><td><b>研发阶段</b>：2050 年代末</td></tr>
|
||||
<tr><td><b>服役阶段</b>：2060 年代</td></tr>
|
||||
<tr><td><b>首飞</b>：2056 年</td></tr>
|
||||
<tr><td><b>服役起始</b>：2057 年</td></tr>
|
||||
<tr><td><b>构型</b>：跑道起降 / VTVL 双模式</td></tr>
|
||||
<tr><td><b>机身</b>：MK2 升力体，菱形截面</td></tr>
|
||||
<tr><td><b>全长</b>：31.7 米</td></tr>
|
||||
@@ -82,7 +82,7 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td><b>运行状态</b>：现役</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<p><b>回声级航天飞机</b>（英语：<b>Echo Shuttle</b>）是全可重复使用轻型航天飞机，属回声级 / 进取级双型号计划中的轻型成员。该级继承秃鹫航天飞机改进乙型的核气塞发动机、高能推进剂管理、自动交会及可重复使用热防护技术，将其集成于 MK2 升力体平台，用于高频人员轮换、小型货运、空间设施抢修、母舰接驳、行星表面短程运输及星际探索母舰远征中的随舰摆渡任务。</p>
|
||||
<p><b>回声级航天飞机</b>（英语：<b>Echo Shuttle</b>）是全可重复使用轻型航天飞机，属回声级 / 进取级双型号计划中的轻型成员。该级于 2056 年首飞，2057 年完成载人认证并正式服役；截至 2060 年 3 月，累计完成约 75 次飞行任务，处于早期运营阶段。回声级继承秃鹫航天飞机改进乙型的核气塞发动机、高能推进剂管理、自动交会及可重复使用热防护技术，将其集成于 MK2 升力体平台，用于高频人员轮换、小型货运、空间设施抢修、母舰接驳、行星表面短程运输及星际探索母舰远征中的随舰摆渡任务。</p>
|
||||
<p>回声级的技术来源可追溯至高能推进系统在秃鹫航天飞机平台上的工程验证。核气塞发动机、高能推进剂管理、深空通信及强化再入规则首先在 MK4 轨道器上完成可运营验证，随后整合为秃鹫航天飞机改进乙型。改进乙型建立重载地月干线能力后，型号规划提出两类补充载具：一型可由星际探索母舰携带至目标行星系，用于大气天体与多卫星系统探索的轻型摆渡航天飞机；另一型用于中型 SSTO 客货运输及母舰近程补给的中型航天飞机。回声级与进取级据此并行开发。</p>
|
||||
<p>回声级主要承担随舰远征任务。羲和级和万星源级星际探索母舰可携带两艘回声级，或按任务需要换装其他兼容载具。巡航期间，两艘回声级以外部停泊状态接受母舰供电、热控、数据及维护支持；母舰抵达目标行星系后，回声级可在大气天体、无大气卫星、临时轨道平台及母舰之间反复往返，承担人员登陆、样品回收、小型设备部署及应急撤离。</p>
|
||||
<p>该级兼具有翼再入与跑道着陆能力，并配置垂直起降（VTVL）系统。地面空间港任务采用跑道起飞与水平着陆以降低整备负担；月球、火星及无跑道前哨站任务使用 VTVL 模式完成离地、末端下降及表面转场。对于火星、泰坦类稠密大气天体或气态行星主要卫星，回声级可在大气制动、升力体滑翔、VTVL 末端下降与轨道返航之间切换，是母舰体系中适合目标系统末端飞行的主要载具。</p>
|
||||
@@ -119,7 +119,7 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<p>星际探索母舰计划对目标系统末端运输提出了独立要求。母舰能够携带人员、实验室、居住舱、燃料、维修系统及长期任务资源抵达目标行星系，但不适合频繁进入大气边缘、低重力卫星附近或复杂尘埃环境。由母舰直接承担表面转运将增加推进剂消耗、热控负担、辐射暴露及任务安全风险。</p>
|
||||
<p>据此，型号规划提出可随母舰长期携带的轻型航天飞机需求。该类飞行器需在巡航期间外部停泊，抵达目标系统后独立执行大气再入、VTVL 表面起降、卫星间转移、样品回收及乘员撤离。该需求与地月系统内的中型客货运输需求并行存在，前者形成回声级，后者形成进取级。</p>
|
||||
<h3 id="双型号计划的形成">双型号计划的形成</h3>
|
||||
<p>2050 年代末的方案评估将轻型与中型型号纳入同一技术项目。回声级采用 MK2 升力体平台，侧重快速响应、高速度增量、远征随舰停泊及目标系统末端运输；进取级采用 MK3 圆柱机身，侧重舱内容积、25 吨级货运、短期高容量载人及中型任务包转运。两型共享核气塞发动机控制律、弧反应堆电源接口、VTVL 辅助发动机、RCS 阀组、顶部结构对接口及自动飞控软件，以降低训练与维护体系复杂度。</p>
|
||||
<p>2050 年代中期的方案评估将轻型与中型型号纳入同一技术项目。回声级采用 MK2 升力体平台，侧重快速响应、高速度增量、远征随舰停泊及目标系统末端运输；进取级采用 MK3 圆柱机身，侧重舱内容积、25 吨级货运、短期高容量载人及中型任务包转运。两型共享核气塞发动机控制律、弧反应堆电源接口、VTVL 辅助发动机、RCS 阀组、顶部结构对接口及自动飞控软件，以降低训练与维护体系复杂度。</p>
|
||||
<p>回声级与进取级的任务边界在项目初期已明确。回声级需在母舰外部停泊数月到数年，在维护窗口有限、目标环境不确定及通信延迟存在的远征中保持可用；进取级主要在近地、月球、火星轨道及母舰装配区承担计划内中型运输。回声级的设计优先项集中于待命可靠性、双艇互备、低重力着陆适应性、热防护快速检查及无人救援能力。</p>
|
||||
<h3 id="早期方案评估">早期方案评估</h3>
|
||||
<p>早期研究曾评估纯 VTVL 无翼飞行器方案，其结构紧凑、表面起降流程较直接、便于母舰外部停泊；但大气再入后横向航程有限，难以在火星、泰坦类稠密大气天体或风场扰动较强的环境中扩大着陆选择，且需在返回与备降阶段保留更多推进剂。</p>
|
||||
@@ -130,12 +130,12 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<table>
|
||||
<thead><tr><th>阶段</th><th>时间</th><th>主要内容</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>概念冻结</td><td>2058-2059</td><td>确定 MK2 升力体、双 XP-F700 核气塞发动机、4 台 VLE-F250 垂直起降发动机和 15 吨级货运指标。</td></tr>
|
||||
<tr><td>地面结构样机</td><td>2059</td><td>完成机身弯扭试验、对接口载荷试验、货舱门循环试验和热防护维护流程验证。</td></tr>
|
||||
<tr><td>VTVL 验证</td><td>2060</td><td>以 EC-V 系列任务验证垂直起飞、悬停、横移、自动着陆和紧急切换逻辑。</td></tr>
|
||||
<tr><td>轨道试飞</td><td>2061</td><td>以 EC-O 系列任务测试主发动机长时间点火、高轨制动、自动交会和跑道返回。</td></tr>
|
||||
<tr><td>载人认证</td><td>2062</td><td>完成 3 名机组 + 4 名乘客标准构型、货舱载客模块和 11 人 40 天生命支持认证。</td></tr>
|
||||
<tr><td>常态化运营</td><td>2063 起</td><td>进入地月系统人员轮换、设施抢修和行星表面接驳任务。</td></tr>
|
||||
<tr><td>概念冻结</td><td>2054-2055</td><td>确定 MK2 升力体、双 XP-F700 核气塞发动机、4 台 VLE-F250 垂直起降发动机和 15 吨级货运指标。</td></tr>
|
||||
<tr><td>地面结构样机</td><td>2055</td><td>完成机身弯扭试验、对接口载荷试验、货舱门循环试验和热防护维护流程验证。</td></tr>
|
||||
<tr><td>VTVL 验证</td><td>2056</td><td>以 EC-V 系列任务验证垂直起飞、悬停、横移、自动着陆和紧急切换逻辑。</td></tr>
|
||||
<tr><td>轨道试飞</td><td>2057</td><td>以 EC-O 系列任务测试主发动机长时间点火、高轨制动、自动交会和跑道返回。</td></tr>
|
||||
<tr><td>载人认证</td><td>2057</td><td>完成 3 名机组 + 4 名乘客标准构型、货舱载客模块和 11 人 40 天生命支持认证。</td></tr>
|
||||
<tr><td>常态化运营</td><td>2058 起</td><td>进入地月系统人员轮换、设施抢修和行星表面接驳任务。</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="设计需求与方案取舍">设计需求与方案取舍</h2>
|
||||
@@ -305,26 +305,26 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<p>这种分工也解释了回声级和进取级为何并行推进。两型共享技术和接口，但服务于不同运营场景：回声级为母舰抵达目标系统后的末端飞行提供可重复使用能力，进取级则为地月、火星轨道和母舰建造体系提供中型客货运输能力。两者共同构成改进乙型重载干线之外的补充航天飞机体系。</p>
|
||||
|
||||
<h2 id="运用历史">运用历史</h2>
|
||||
<p>回声级在 2050 年代末完成方案冻结后，于 2060 年代初进入密集试飞。早期任务重点验证 VTVL 控制律、升力体低速操纵、主发动机高轨制动和自动对接。载人认证完成后，回声级首先用于近地轨道设施和月球基地之间的人员轮换，随后进入星际探索母舰接驳任务。</p>
|
||||
<p>回声级在 2050 年代中期完成方案冻结后，于 2056 年进入密集试飞。早期任务重点验证 VTVL 控制律、升力体低速操纵、主发动机高轨制动和自动对接。2057 年载人认证完成后，回声级首先用于近地轨道设施和月球基地之间的人员轮换，随后于 2058 年进入星际探索母舰接驳任务。</p>
|
||||
<p>与进取级相比，回声级的试飞节奏更高，单次任务规模较小。验证阶段大量使用短周期 VTVL 起降、无人交会和跑道返回任务，以快速收集飞控、热防护和对接口数据。载人认证完成后，回声级开始承担月面基地接驳、轨道设施抢修和母舰外部停泊验证。</p>
|
||||
<p>2060 年代中期以后，回声级逐渐从地月系统的快速穿梭艇扩展为星际探索母舰体系的标准随舰飞行器。它的任务记录开始出现更多 EC-M、EC-S、EC-J 和 EC-T 前缀，分别对应母舰支援、卫星巡访、木星系统和泰坦类大气目标任务。</p>
|
||||
<p>截至 2060 年 3 月，回声级处于早期运营阶段，累计完成约 75 次飞行任务。该级已从地月系统的快速穿梭艇扩展为星际探索母舰体系的标准随舰飞行器，其任务记录涵盖 EC-M、EC-S、EC-J 和 EC-T 前缀，分别对应母舰支援、卫星巡访、木星系统和泰坦类大气目标任务。</p>
|
||||
|
||||
<h3 id="主要任务节点">主要任务节点</h3>
|
||||
<table>
|
||||
<thead><tr><th>任务编号</th><th>时间</th><th>任务</th><th>结果</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>EC-V1</td><td>2060</td><td>首次完整 VTVL 起飞、悬停和自动着陆</td><td>验证四台辅助发动机联动控制。</td></tr>
|
||||
<tr><td>EC-R2</td><td>2060</td><td>跑道起飞和水平着陆测试</td><td>完成低速操纵、鸭翼配平和复飞流程验证。</td></tr>
|
||||
<tr><td>EC-O1</td><td>2061</td><td>首次无人入轨与跑道返回</td><td>主发动机长时间点火和再入热防护数据达标。</td></tr>
|
||||
<tr><td>EC-C1</td><td>2062</td><td>首次载人轨道任务</td><td>完成标准 3+4 乘员构型、轨道热防护检查和 11 人应急扩容流程。</td></tr>
|
||||
<tr><td>EC-L1</td><td>2063</td><td>首次月面基地接驳</td><td>完成低重力 VTVL 降落、补给卸载和乘员返回。</td></tr>
|
||||
<tr><td>EC-M2</td><td>2064</td><td>首次星际探索母舰外部停泊任务</td><td>验证顶部结构对接口、母舰停泊载荷限制和待命供电接口。</td></tr>
|
||||
<tr><td>EC-S7</td><td>2065</td><td>轨道设施抢修任务</td><td>使用加压任务模块运送维修组和可替换设备。</td></tr>
|
||||
<tr><td>EC-M3</td><td>2065</td><td>双艇互备母舰演练</td><td>一艘回声级执行模拟表面任务，另一艘保持救援待命并完成近距接近。</td></tr>
|
||||
<tr><td>EC-R5</td><td>2065</td><td>高能返回制动复核</td><td>验证双主发动机制动窗口和热防护轨道检查流程。</td></tr>
|
||||
<tr><td>EC-T1</td><td>2066</td><td>稠密大气目标任务模拟</td><td>完成升力体长航程滑翔、VTVL 末端下降和样品隔离模块测试。</td></tr>
|
||||
<tr><td>EC-J2</td><td>2066</td><td>高辐射卫星巡访演练</td><td>验证短时进入高风险区域、母舰远距待命和电子设备剂量管理。</td></tr>
|
||||
<tr><td>EC-E2</td><td>2066</td><td>远征应急撤离演练</td><td>以 11 人扩容构型完成无人接近、乘员转移和母舰接收流程。</td></tr>
|
||||
<tr><td>EC-V1</td><td>2056</td><td>首次完整 VTVL 起飞、悬停和自动着陆</td><td>验证四台辅助发动机联动控制。</td></tr>
|
||||
<tr><td>EC-R2</td><td>2056</td><td>跑道起飞和水平着陆测试</td><td>完成低速操纵、鸭翼配平和复飞流程验证。</td></tr>
|
||||
<tr><td>EC-O1</td><td>2057</td><td>首次无人入轨与跑道返回</td><td>主发动机长时间点火和再入热防护数据达标。</td></tr>
|
||||
<tr><td>EC-C1</td><td>2057</td><td>首次载人轨道任务</td><td>完成标准 3+4 乘员构型、轨道热防护检查和 11 人应急扩容流程。</td></tr>
|
||||
<tr><td>EC-L1</td><td>2058</td><td>首次月面基地接驳</td><td>完成低重力 VTVL 降落、补给卸载和乘员返回。</td></tr>
|
||||
<tr><td>EC-M2</td><td>2058</td><td>首次星际探索母舰外部停泊任务</td><td>验证顶部结构对接口、母舰停泊载荷限制和待命供电接口。</td></tr>
|
||||
<tr><td>EC-S7</td><td>2059</td><td>轨道设施抢修任务</td><td>使用加压任务模块运送维修组和可替换设备。</td></tr>
|
||||
<tr><td>EC-M3</td><td>2059</td><td>双艇互备母舰演练</td><td>一艘回声级执行模拟表面任务，另一艘保持救援待命并完成近距接近。</td></tr>
|
||||
<tr><td>EC-R5</td><td>2059</td><td>高能返回制动复核</td><td>验证双主发动机制动窗口和热防护轨道检查流程。</td></tr>
|
||||
<tr><td>EC-T1</td><td>2060</td><td>稠密大气目标任务模拟</td><td>完成升力体长航程滑翔、VTVL 末端下降和样品隔离模块测试。</td></tr>
|
||||
<tr><td>EC-J2</td><td>2060</td><td>高辐射卫星巡访演练</td><td>验证短时进入高风险区域、母舰远距待命和电子设备剂量管理。</td></tr>
|
||||
<tr><td>EC-E2</td><td>2060</td><td>远征应急撤离演练</td><td>以 11 人扩容构型完成无人接近、乘员转移和母舰接收流程。</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h3 id="历史飞行次数">历史飞行次数</h3>
|
||||
@@ -332,13 +332,13 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<div class="launch-chart" role="img" aria-label="回声级航天飞机历史飞行次数示意图">
|
||||
<div class="launch-row launch-head"><span>年份</span><span>飞行次数</span><span>次数</span><span>累计</span></div>
|
||||
<div class="launch-stage-label">验证阶段</div>
|
||||
<div class="launch-row"><span>2060</span><span class="launch-track"><span class="launch-bar" style="width:11%;"></span></span><span class="launch-count">8</span><span class="launch-cumulative">8</span></div>
|
||||
<div class="launch-row"><span>2061</span><span class="launch-track"><span class="launch-bar" style="width:15%;"></span></span><span class="launch-count">11</span><span class="launch-cumulative">19</span></div>
|
||||
<div class="launch-row"><span>2062</span><span class="launch-track"><span class="launch-bar" style="width:25%;"></span></span><span class="launch-count">18</span><span class="launch-cumulative">37</span></div>
|
||||
<div class="launch-stage-label">常态运营阶段</div>
|
||||
<div class="launch-row"><span>2063</span><span class="launch-track"><span class="launch-bar" style="width:50%;"></span></span><span class="launch-count">36</span><span class="launch-cumulative">73</span></div>
|
||||
<div class="launch-row"><span>2064</span><span class="launch-track"><span class="launch-bar" style="width:75%;"></span></span><span class="launch-count">54</span><span class="launch-cumulative">127</span></div>
|
||||
<div class="launch-row"><span>2065</span><span class="launch-track"><span class="launch-bar" style="width:100%;"></span></span><span class="launch-count">72</span><span class="launch-cumulative">199</span></div>
|
||||
<div class="launch-row"><span>2056</span><span class="launch-track"><span class="launch-bar" style="width:17%;"></span></span><span class="launch-count">5</span><span class="launch-cumulative">5</span></div>
|
||||
<div class="launch-stage-label">载人认证与早期运营</div>
|
||||
<div class="launch-row"><span>2057</span><span class="launch-track"><span class="launch-bar" style="width:40%;"></span></span><span class="launch-count">12</span><span class="launch-cumulative">17</span></div>
|
||||
<div class="launch-row"><span>2058</span><span class="launch-track"><span class="launch-bar" style="width:67%;"></span></span><span class="launch-count">20</span><span class="launch-cumulative">37</span></div>
|
||||
<div class="launch-row"><span>2059</span><span class="launch-track"><span class="launch-bar" style="width:100%;"></span></span><span class="launch-count">30</span><span class="launch-cumulative">67</span></div>
|
||||
<div class="launch-stage-label">当前运营（至 2060 年 3 月）</div>
|
||||
<div class="launch-row"><span>2060</span><span class="launch-track"><span class="launch-bar" style="width:27%;"></span></span><span class="launch-count">~8</span><span class="launch-cumulative">~75</span></div>
|
||||
</div>
|
||||
|
||||
<h2 id="机队与编号">机队与编号</h2>
|
||||
@@ -366,14 +366,14 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<table>
|
||||
<thead><tr><th>任务编号</th><th>阶段</th><th>事件</th><th>后续处理</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>EC-V1B</td><td>2060 VTVL 验证</td><td>一台辅助发动机节流响应偏慢，飞控触发自动中止并返回测试坪。</td><td>调整 VTVL 发动机节流阈值，增加悬停前健康检查。</td></tr>
|
||||
<tr><td>EC-O2</td><td>2061 轨道试飞</td><td>高轨返回前主发动机制动窗口延迟，航天飞机多停留一圈后再入。</td><td>任务规则要求保留第二制动窗口和额外电力余量。</td></tr>
|
||||
<tr><td>EC-C1</td><td>2062 载人认证</td><td>轨道热像检查显示一处机腹边条翘起。</td><td>使用舱外检查确认可返航，落地后更换边条并修订维修标准。</td></tr>
|
||||
<tr><td>EC-M2</td><td>2064 母舰接驳</td><td>顶部对接端口载荷传感器出现短时超限。</td><td>飞控自动解除硬捕获，后续任务降低接近速度并加强对接口校准。</td></tr>
|
||||
<tr><td>EC-L3</td><td>2064 月面接驳</td><td>着陆区尘埃遮挡导致视觉导航短时降级。</td><td>增加雷达高度计权重，并要求未整备着陆点预先投放标定信标。</td></tr>
|
||||
<tr><td>EC-M3</td><td>2065 双艇互备演练</td><td>备份艇出动前检测到推进剂温度低于快速出动阈值。</td><td>修改母舰外部停泊热控策略，救援艇保持更高待命等级。</td></tr>
|
||||
<tr><td>EC-T1</td><td>2066 稠密大气模拟</td><td>长航程滑翔中气动加热分布偏离预测。</td><td>调整再入攻角限制，增加大气目标任务前的热流模型复核。</td></tr>
|
||||
<tr><td>EC-J2</td><td>2066 高辐射演练</td><td>一组非关键传感器出现辐射诱发重启。</td><td>对相关航电增加屏蔽和软件降级模式，并缩短高辐射区域停留时间。</td></tr>
|
||||
<tr><td>EC-V1B</td><td>2056 VTVL 验证</td><td>一台辅助发动机节流响应偏慢，飞控触发自动中止并返回测试坪。</td><td>调整 VTVL 发动机节流阈值，增加悬停前健康检查。</td></tr>
|
||||
<tr><td>EC-O2</td><td>2057 轨道试飞</td><td>高轨返回前主发动机制动窗口延迟，航天飞机多停留一圈后再入。</td><td>任务规则要求保留第二制动窗口和额外电力余量。</td></tr>
|
||||
<tr><td>EC-C1</td><td>2057 载人认证</td><td>轨道热像检查显示一处机腹边条翘起。</td><td>使用舱外检查确认可返航，落地后更换边条并修订维修标准。</td></tr>
|
||||
<tr><td>EC-M2</td><td>2058 母舰接驳</td><td>顶部对接端口载荷传感器出现短时超限。</td><td>飞控自动解除硬捕获，后续任务降低接近速度并加强对接口校准。</td></tr>
|
||||
<tr><td>EC-L3</td><td>2058 月面接驳</td><td>着陆区尘埃遮挡导致视觉导航短时降级。</td><td>增加雷达高度计权重，并要求未整备着陆点预先投放标定信标。</td></tr>
|
||||
<tr><td>EC-M3</td><td>2059 双艇互备演练</td><td>备份艇出动前检测到推进剂温度低于快速出动阈值。</td><td>修改母舰外部停泊热控策略，救援艇保持更高待命等级。</td></tr>
|
||||
<tr><td>EC-T1</td><td>2060 稠密大气模拟</td><td>长航程滑翔中气动加热分布偏离预测。</td><td>调整再入攻角限制，增加大气目标任务前的热流模型复核。</td></tr>
|
||||
<tr><td>EC-J2</td><td>2060 高辐射演练</td><td>一组非关键传感器出现辐射诱发重启。</td><td>对相关航电增加屏蔽和软件降级模式，并缩短高辐射区域停留时间。</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h3 id="安全规则">安全规则</h3>
|
||||
|
||||
@@ -65,6 +65,8 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td><b>Type</b>: Fully reusable medium shuttle</td></tr>
|
||||
<tr><td><b>Generation</b>: Parallel supplement after Vulture Shuttle Block 2</td></tr>
|
||||
<tr><td><b>Related design</b>: Echo Shuttle</td></tr>
|
||||
<tr><td><b>First flight</b>: 2057</td></tr>
|
||||
<tr><td><b>Service entry</b>: 2058</td></tr>
|
||||
<tr><td><b>Configuration</b>: Runway operation / VTVL dual mode</td></tr>
|
||||
<tr><td><b>Fuselage</b>: MK3 cylindrical body, 3.75 m class diameter</td></tr>
|
||||
<tr><td><b>Length</b>: 29.8 m</td></tr>
|
||||
@@ -74,9 +76,9 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td><b>Maximum takeoff mass</b>: 80 t</td></tr>
|
||||
<tr><td><b>Payload</b>: 25 t</td></tr>
|
||||
<tr><td><b>Passenger configuration</b>: 6 crew + 16 passengers</td></tr>
|
||||
<tr><td><b>Status</b>: In service</td></tr>
|
||||
<tr><td><b>Status</b>: Active</td></tr>
|
||||
</tbody></table>
|
||||
<p>The <b>Enterprise Shuttle</b> is a medium fully reusable shuttle developed after Vulture Shuttle Block 2 entered service. It is the heavier member of the Echo / Enterprise paired-shuttle program. Enterprise shares the same broad technology family as Echo, including nuclear aerospike propulsion, a compact arc reactor, VTVL auxiliary engines, reinforced dorsal docking hardware, and autonomous flight control, but it uses a larger MK3 fuselage for greater crew and cargo capacity.</p>
|
||||
<p>The <b>Enterprise Shuttle</b> is a medium fully reusable shuttle that first flew in 2057 and entered operational service in 2058. It is the heavier member of the Echo / Enterprise paired-shuttle program, designed to complement Echo with greater crew and cargo capacity for medium-lift missions. Enterprise shares the same broad technology family as Echo, including nuclear aerospike propulsion, a compact arc reactor, VTVL auxiliary engines, reinforced dorsal docking hardware, and autonomous flight control, but it uses a larger MK3 fuselage for greater crew and cargo capacity.</p>
|
||||
<p>Enterprise was not intended to replace the heavy cislunar transport role of the Vulture Shuttle family. Instead, it covers the middle ground between Echo-class quick-response shuttle work and Vulture Block 2 heavy-lift operations: 25 t cargo transfer, short-duration high-capacity passenger transport, base support, return payload carriage, and mothership construction, refit, supply, or near-range berthing.</p>
|
||||
<p>Within interplanetary exploration mothership operations, Enterprise is not normally carried as the standard expedition ferry shuttle. Xihe-class and Stellaria-class motherships more commonly carry two Echo shuttles, or another compatible ferry-shuttle mix, for surface and moon-to-mothership transfer after arrival. Enterprise instead supports the mothership before departure and after return, especially around shipyards, stations, and near-Earth, lunar, or Mars-orbit logistics nodes.</p>
|
||||
<p>The vehicle is rated for a 52.9 t zero-payload takeoff mass, an 80 t maximum takeoff mass, 14.4 t of high-energy liquid fuel, and fully uncrewed flight. Its single NV-PL "New Frontier" plasma aerospike main engine provides about 1,780 kN of thrust, while four VLE-F250 "Lander" nuclear plasma engines provide VTVL capability.</p>
|
||||
@@ -144,34 +146,35 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<p>Spaceports normally schedule Enterprise into medium-priority launch windows. Passenger-heavy flights carry lighter cargo and emphasize evacuation access; cargo-heavy flights reduce passenger count and increase structural telemetry around the bay and docking port. Lunar and Martian surface missions typically include an orbital thermal and propellant review before the vehicle commits to VTVL descent.</p>
|
||||
<p>Compared with Vulture Block 2, Enterprise's advantage is operational flexibility at more bases and lower processing overhead. Its limits are equally clear: 25 t payload, 22 people for 4 days, and mandatory powered braking before high-energy return. Operations teams therefore treat it as a medium transfer node and mothership support shuttle, not as a deep-space mothership or a standard expedition-carried ferry shuttle.</p>
|
||||
<h2 id="operational-history">Operational history</h2>
|
||||
<p>Enterprise entered testing later than Echo. The Echo program validated the shared dual-mode flight-control architecture first, after which Enterprise adapted those procedures to a larger airframe, heavier cargo bay, and denser passenger cabin. By 2063 it had completed crew certification, and by the mid-2060s it was a regular medium-capacity cislunar transport.</p>
|
||||
<p>Enterprise entered testing shortly after Echo. The Echo program validated the shared dual-mode flight-control architecture first, after which Enterprise adapted those procedures to a larger airframe, heavier cargo bay, and denser passenger cabin. By early 2058 it had completed crew certification and entered operational service. As of March 2060, Enterprise remains in the early phase of operations, with approximately 36 flights completed across its small but growing fleet.</p>
|
||||
<table>
|
||||
<thead><tr><th>Mission</th><th>Year</th><th>Objective</th><th>Result</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>EN-S1</td><td>2060</td><td>Ground structural article and cargo-door cycle testing</td><td>Verified MK3 airframe and 25 t bay margins.</td></tr>
|
||||
<tr><td>EN-V1</td><td>2061</td><td>Low-gravity VTVL simulation and hover testing</td><td>Validated auxiliary-engine thrust allocation and center-of-gravity control.</td></tr>
|
||||
<tr><td>EN-O1</td><td>2062</td><td>First uncrewed orbital flight and heavy return</td><td>Verified main-engine braking, off-center cargo, and runway landing.</td></tr>
|
||||
<tr><td>EN-C1</td><td>2063</td><td>First crewed transport mission</td><td>Certified 6 crew + 16 passenger short-duration transport.</td></tr>
|
||||
<tr><td>EN-L2</td><td>2064</td><td>Lunar base resupply mission</td><td>Completed 25 t cargo transfer and low-gravity unloading.</td></tr>
|
||||
<tr><td>EN-M3</td><td>2065</td><td>Exploration mothership berthing mission</td><td>Verified reinforced dorsal docking, cargo transfer, and extended power support.</td></tr>
|
||||
<tr><td>EN-S1</td><td>2057</td><td>Ground structural article and cargo-door cycle testing</td><td>Verified MK3 airframe and 25 t bay margins.</td></tr>
|
||||
<tr><td>EN-V1</td><td>2057</td><td>Low-gravity VTVL simulation and hover testing</td><td>Validated auxiliary-engine thrust allocation and center-of-gravity control.</td></tr>
|
||||
<tr><td>EN-O1</td><td>2058</td><td>First uncrewed orbital flight and heavy return</td><td>Verified main-engine braking, off-center cargo, and runway landing.</td></tr>
|
||||
<tr><td>EN-C1</td><td>2058</td><td>First crewed transport mission</td><td>Certified 6 crew + 16 passenger short-duration transport.</td></tr>
|
||||
<tr><td>EN-L2</td><td>2059</td><td>Lunar base supply mission</td><td>Completed 25 t cargo transfer and low-gravity unloading.</td></tr>
|
||||
<tr><td>EN-M3</td><td>2059</td><td>Exploration mothership docking mission</td><td>Verified reinforced dorsal docking, cargo transfer, and extended power support.</td></tr>
|
||||
<tr><td>EN-D2</td><td>2059</td><td>Heavy cargo deployment to orbital shipyard</td><td>Delivered pressurized equipment racks, external tool kits, and mission control stations to a mothership assembly platform.</td></tr>
|
||||
<tr><td>EN-R3</td><td>2060</td><td>Emergency return verification</td><td>Completed multi-batch sample container, failed equipment, and crew rotation under expedited re-entry procedures.</td></tr>
|
||||
<tr><td>EN-H2</td><td>2060</td><td>High-orbit heavy delivery</td><td>Validated transfer procedures from a high-orbit platform to an outpost and revised VTVL thrust-frame inspection standards.</td></tr>
|
||||
</tbody></table>
|
||||
<div class="launch-chart" role="img" aria-label="Enterprise Shuttle flight count chart">
|
||||
<div class="launch-row launch-head"><span>Year</span><span>Flights</span><span>No.</span><span>Total</span></div>
|
||||
<div class="launch-stage-label">Validation phase</div>
|
||||
<div class="launch-row"><span>2061</span><span class="launch-track"><span class="launch-bar" style="width:8%;"></span></span><span class="launch-count">4</span><span class="launch-cumulative">4</span></div>
|
||||
<div class="launch-row"><span>2062</span><span class="launch-track"><span class="launch-bar" style="width:16%;"></span></span><span class="launch-count">8</span><span class="launch-cumulative">12</span></div>
|
||||
<div class="launch-stage-label">Crew certification</div>
|
||||
<div class="launch-row"><span>2063</span><span class="launch-track"><span class="launch-bar" style="width:29%;"></span></span><span class="launch-count">14</span><span class="launch-cumulative">26</span></div>
|
||||
<div class="launch-stage-label">Medium-capacity operations</div>
|
||||
<div class="launch-row"><span>2064</span><span class="launch-track"><span class="launch-bar" style="width:53%;"></span></span><span class="launch-count">26</span><span class="launch-cumulative">52</span></div>
|
||||
<div class="launch-row"><span>2065</span><span class="launch-track"><span class="launch-bar" style="width:78%;"></span></span><span class="launch-count">38</span><span class="launch-cumulative">90</span></div>
|
||||
<div class="launch-row"><span>2066</span><span class="launch-track"><span class="launch-bar" style="width:100%;"></span></span><span class="launch-count">49</span><span class="launch-cumulative">139</span></div>
|
||||
<div class="launch-stage-label">Test phase</div>
|
||||
<div class="launch-row"><span>2057</span><span class="launch-track"><span class="launch-bar" style="width:17%;"></span></span><span class="launch-count">3</span><span class="launch-cumulative">3</span></div>
|
||||
<div class="launch-stage-label">Crew certification and ramp-up</div>
|
||||
<div class="launch-row"><span>2058</span><span class="launch-track"><span class="launch-bar" style="width:56%;"></span></span><span class="launch-count">10</span><span class="launch-cumulative">13</span></div>
|
||||
<div class="launch-stage-label">Operational phase</div>
|
||||
<div class="launch-row"><span>2059</span><span class="launch-track"><span class="launch-bar" style="width:100%;"></span></span><span class="launch-count">18</span><span class="launch-cumulative">31</span></div>
|
||||
<div class="launch-row"><span>2060</span><span class="launch-track"><span class="launch-bar" style="width:28%;"></span></span><span class="launch-count">~5</span><span class="launch-cumulative">~36</span></div>
|
||||
</div>
|
||||
<h2 id="safety-and-incidents">Safety and incidents</h2>
|
||||
<figure class="thumb tright"><a class="media-link" href="#enterprise-img-safety"><img src="/enterprise/enterprise_takeoff_side_view.png" alt="Enterprise Shuttle runway operation" data-wiki-asset="/enterprise/enterprise_takeoff_side_view.png"></a><figcaption class="thumbcaption">Enterprise has stricter runway, wind, and go-around rules at high landing mass.</figcaption></figure>
|
||||
<p>The main safety questions for Enterprise are heavy landing mass, single-main-engine dependency, VTVL engine redundancy, docking-port structural loads, dense passenger transport, and powered slowdown before high-energy re-entry. Because Enterprise carries more people and cargo than Echo, abort criteria and life-support redundancy are more conservative.</p>
|
||||
<table>
|
||||
<thead><tr><th>Incident type</th><th>Description</th><th>Suggested image</th></tr></thead>
|
||||
<thead><tr><th>Incident</th><th>Description</th><th>Mitigation</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>EN-V2</td><td>Aft center of gravity reduced hover-control margin during VTVL validation.</td><td>Cargo loading limits and forward-center-of-gravity checks were revised.</td></tr>
|
||||
<tr><td>EN-O1</td><td>High-frequency vibration alarm appeared during a long main-engine braking burn.</td><td>Nozzle cooling and vibration thresholds were revised; backup braking windows became mandatory.</td></tr>
|
||||
@@ -183,6 +186,8 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<thead><tr><th>Parameter</th><th>Value</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>Type</td><td>Fully reusable medium shuttle</td></tr>
|
||||
<tr><td>First flight</td><td>2057</td></tr>
|
||||
<tr><td>Service entry</td><td>2058</td></tr>
|
||||
<tr><td>Fuselage</td><td>MK3 cylindrical body, 3.75 m class diameter</td></tr>
|
||||
<tr><td>Length</td><td>29.8 m</td></tr>
|
||||
<tr><td>Wingspan</td><td>20.3 m</td></tr>
|
||||
|
||||
@@ -69,8 +69,9 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td><b>世代定位</b>：秃鹫航天飞机改进乙型之后的并行补充型号</td></tr>
|
||||
<tr><td><b>计划关系</b>：回声级 / 进取级轻重双型号计划</td></tr>
|
||||
<tr><td><b>核心定位</b>：中型 SSTO 客货运输与母舰建造补给支援</td></tr>
|
||||
<tr><td><b>研发阶段</b>：2050 年代末</td></tr>
|
||||
<tr><td><b>服役阶段</b>：2060 年代</td></tr>
|
||||
<tr><td><b>首飞</b>：2057 年</td></tr>
|
||||
<tr><td><b>服役</b>：2058 年</td></tr>
|
||||
<tr><td><b>研发阶段</b>：2050 年代中期</td></tr>
|
||||
<tr><td><b>构型</b>：跑道起降 / VTVL 双模式</td></tr>
|
||||
<tr><td><b>机身</b>：MK3 圆柱机身，3.75 米级直径</td></tr>
|
||||
<tr><td><b>全长</b>：29.8 米</td></tr>
|
||||
@@ -82,7 +83,7 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td><b>运行状态</b>：现役</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<p><b>进取级航天飞机</b>（英语：<b>Enterprise Shuttle</b>）是一款全可重复使用中型航天飞机，属回声级 / 进取级并行计划中的重型成员。该级采用 MK3 圆柱机身、25 吨级货舱及高密度短期载人舱，兼具有翼再入、跑道着陆与 VTVL 表面起降能力，主要承担中型货运、基地补给、母舰建造支援及近程接驳任务。</p>
|
||||
<p><b>进取级航天飞机</b>（英语：<b>Enterprise Shuttle</b>）是一款全可重复使用中型航天飞机，于 2057 年首飞、2058 年投入运营，属回声级 / 进取级并行计划中的重型成员。该级采用 MK3 圆柱机身、25 吨级货舱及高密度短期载人舱，兼具有翼再入、跑道着陆与 VTVL 表面起降能力，主要承担中型货运、基地补给、母舰建造支援及近程接驳任务。截至 2060 年 3 月，进取级处于运营初期阶段，累计完成约 36 次飞行。</p>
|
||||
<p>进取级的技术来源可追溯至高能推进系统在秃鹫航天飞机平台上的工程验证。核气塞发动机、高能推进剂管理、深空通信及强化再入规则首先在 MK4 轨道器上完成可运营验证，随后整合为秃鹫航天飞机改进乙型。改进乙型确立重载地月干线能力后，型号规划提出两类补充载具：一型为可随星际探索母舰远征的轻型摆渡航天飞机，另一型为独立执行中型 SSTO 客货运输及母舰近程补给的中型航天飞机。回声级与进取级据此并行开发。</p>
|
||||
<p>进取级与回声级共享核气塞发动机、弧反应堆电源、VTVL 辅助发动机、自动飞控体系、顶部结构对接口及任务软件。运行分工上，回声级承担远征随舰摆渡、快速响应及小型高价值载荷运输；进取级负责中等规模客货运输、基地支援、母舰停泊、改装验收及 22 人级短期转运。</p>
|
||||
<p>进取级运力低于秃鹫航天飞机改进乙型的重载地月运输能力，地面整备压力、发射窗口依赖及任务成本亦相应降低。对无需 120 吨级低月轨直达能力的任务，进取级可在较短周期内完成中型客货运输，主要用于月球基地扩建、轨道船坞补给、火星前哨站接驳及星际探索母舰出发前后的中型补给。</p>
|
||||
@@ -118,7 +119,7 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<p>改进乙型投入运营后，航天飞机体系具备稳定的重载干线能力，但中等规模客货运输与远征末端摆渡需求仍缺乏独立型号。月球基地、轨道船坞、火星前哨站及星际探索母舰的任务频次提高后，任务规划中出现大量十余名人员、25 吨以内设备、加压任务包或返回载荷运输需求。这些任务的规模超过轻型摆渡航天飞机的容量，但通常不足以调用改进乙型的 120 吨级低月轨直达能力。</p>
|
||||
<p>同期，星际探索母舰计划提出随舰摆渡需求。母舰抵达目标行星系后，需要可长期外部停泊、可在大气天体与卫星之间反复出动、具备有翼再入与 VTVL 起降能力的小型载具。该需求由回声级承担。进取级则面向中型 SSTO 货运、基地支援及母舰近程补给，与回声级作为改进乙型重载干线之外的互补型号并行发展。</p>
|
||||
<h3 id="双型号计划的形成">双型号计划的形成</h3>
|
||||
<p>2050 年代末的型号规划将轻型回声级与中型进取级纳入同一技术项目。回声级采用 MK2 升力体平台，侧重快速响应、高速度增量、远征随舰停泊及目标系统末端运输；进取级采用 MK3 圆柱机身，侧重舱内容积、25 吨级货运、短期高容量载人及中型任务包转运。</p>
|
||||
<p>2050 年代中后期的型号规划将轻型回声级与中型进取级纳入同一技术项目。回声级采用 MK2 升力体平台，侧重快速响应、高速度增量、远征随舰停泊及目标系统末端运输；进取级采用 MK3 圆柱机身，侧重舱内容积、25 吨级货运、短期高容量载人及中型任务包转运。</p>
|
||||
<p>两型共享核气塞发动机控制律、VTVL 辅助发动机、弧反应堆电源接口、RCS 阀组、顶部结构对接口、自动交会软件、热防护检查流程及飞控任务状态机，以降低研发、训练及维护体系的重复建设。差异集中于机身截面、货舱尺度、乘员密度、着陆质量、对接口载荷及任务周转方式。</p>
|
||||
<p>进取级在技术上继承回声级的自动飞控、VTVL 着陆、热防护检查及对接口程序，采用 MK3 圆柱机身以获得更规整的舱内空间与更高结构余量。圆柱机身的升力体效率低于回声级 MK2 截面，但有利于标准货架布置、加压舱门安装、客货混载及母舰任务包集成。</p>
|
||||
<h3 id="早期方案评估">早期方案评估</h3>
|
||||
@@ -130,12 +131,12 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<table>
|
||||
<thead><tr><th>阶段</th><th>时间</th><th>主要内容</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>总体方案</td><td>2058-2059</td><td>确定 MK3 机身、NV-PL “New Frontier” 等离子气塞发动机、25 吨货舱和 6+16 乘员构型。</td></tr>
|
||||
<tr><td>结构样机</td><td>2060</td><td>完成货舱门、顶部 1.875 米结构对接口、起落架和重载机身弯曲试验。</td></tr>
|
||||
<tr><td>推进验证</td><td>2061</td><td>验证 1780 kN 级等离子气塞发动机节流、VLE-F250 辅助发动机协同和 40 个 RCS 推进器配置。</td></tr>
|
||||
<tr><td>轨道试飞</td><td>2062</td><td>完成无人入轨、重载返回、货舱部署和跑道着陆测试。</td></tr>
|
||||
<tr><td>载人认证</td><td>2063</td><td>完成 6 名机组 + 16 名乘客构型、22 人 4 天生命支持和无人飞行流程认证。</td></tr>
|
||||
<tr><td>运营扩展</td><td>2064 起</td><td>进入地月系统客货运输、基地支援和母舰接驳任务。</td></tr>
|
||||
<tr><td>总体方案</td><td>2055-2056</td><td>确定 MK3 机身、NV-PL "New Frontier" 等离子气塞发动机、25 吨货舱和 6+16 乘员构型。</td></tr>
|
||||
<tr><td>结构样机</td><td>2057</td><td>完成货舱门、顶部 1.875 米结构对接口、起落架和重载机身弯曲试验。</td></tr>
|
||||
<tr><td>推进验证</td><td>2057</td><td>验证 1780 kN 级等离子气塞发动机节流、VLE-F250 辅助发动机协同和 40 个 RCS 推进器配置。</td></tr>
|
||||
<tr><td>轨道试飞</td><td>2058</td><td>完成无人入轨、重载返回、货舱部署和跑道着陆测试。</td></tr>
|
||||
<tr><td>载人认证</td><td>2058</td><td>完成 6 名机组 + 16 名乘客构型、22 人 4 天生命支持和无人飞行流程认证。</td></tr>
|
||||
<tr><td>运营扩展</td><td>2059 起</td><td>进入地月系统客货运输、基地支援和母舰接驳任务。</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="设计需求与方案取舍">设计需求与方案取舍</h2>
|
||||
@@ -169,7 +170,7 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<h3 id="任务系统与维护">任务系统与维护</h3>
|
||||
<p>进取级任务系统强调可重构性。客舱可在人员运输、医疗撤离和工程控制之间切换；货舱可安装标准货架、返回容器、外部机械臂接口或加压任务包。自动飞控系统与回声级同源，但针对更大惯量和更高着陆质量调整了姿态滤波、RCS 分配和 VTVL 末端制导，并具备覆盖完整任务流程的全无人飞行能力。</p>
|
||||
<p>进取级的软件架构保留了与回声级相同的任务状态机，但增加了更细的载荷约束模型。飞控在起飞前会读取货舱质量、重心、乘员分布、对接口载荷和推进剂余量，自动计算跑道中止点、VTVL 备降边界和返回制动窗口。对于 25 吨级货运任务，任务计划通常会把装载顺序、货舱门开启角度和对接口受力纳入飞前审查。</p>
|
||||
<p>地面维护体系围绕“中等频次、大载荷周转”设计。常规任务后重点检查热防护、货舱门、主发动机喷口、VTVL 推力架和顶部对接口；重载或异常着陆任务后，需要额外检查机身框梁、起落架和客舱密封。由于进取级经常携带乘员和货物混合载荷，整备流程还包括客舱氧气、水循环、货舱气密门和应急撤离通道的独立验收。</p>
|
||||
<p>地面维护体系围绕"中等频次、大载荷周转"设计。常规任务后重点检查热防护、货舱门、主发动机喷口、VTVL 推力架和顶部对接口；重载或异常着陆任务后，需要额外检查机身框梁、起落架和客舱密封。由于进取级经常携带乘员和货物混合载荷，整备流程还包括客舱氧气、水循环、货舱气密门和应急撤离通道的独立验收。</p>
|
||||
<h3 id="主要子系统">主要子系统</h3>
|
||||
<p>进取级的子系统划分兼具短期客货运输飞船和航天飞机轨道器特征。机体内部将飞行控制、客舱、货舱、推进剂、热控和应急撤离通道分为相对独立的维护区，使地面团队能够按任务构型进行分段检查。</p>
|
||||
<table>
|
||||
@@ -182,11 +183,11 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td>热控与热防护</td><td>机腹热防护瓦、翼前缘材料、尾段隔热、货舱散热器和反应堆热控回路。</td><td>控制再入热流、停泊期间热平衡和地面整备安全。</td></tr>
|
||||
<tr><td>对接与停泊</td><td>顶部 1.875 米结构对接口、货舱 1.25 米对接口、硬捕获机构、供电与数据接口。</td><td>连接空间站、母舰、轨道船坞和加压货物模块。</td></tr>
|
||||
</tbody></table>
|
||||
<p>这些子系统共同使进取级具备“客货混合、短期高容量、可停泊、可表面起降”的特征。它不追求长时间独立航行，也不承担母舰推进、深空通信中继或重型建造干线角色。</p>
|
||||
<p>这些子系统共同使进取级具备"客货混合、短期高容量、可停泊、可表面起降"的特征。它不追求长时间独立航行，也不承担母舰推进、深空通信中继或重型建造干线角色。</p>
|
||||
|
||||
<h2 id="推进与电源">推进与电源</h2>
|
||||
<p>进取级主推进系统为 1 台 NV-PL “New Frontier” 等离子气塞发动机，额定推力约 1780 kN。该发动机服务于轨道机动、深空转移修正、返回前制动和部分中止模式。单台大推力布局节省尾段空间并简化推进剂管路，但对发动机健康监测、阀组冗余和制动窗口规划提出更高要求。</p>
|
||||
<p>4 台 VLE-F250 “Lander” 核等离子发动机总推力约 1000 kN，用于垂直起飞、垂直着陆、低重力天体表面转场和跑道复飞辅助。由于进取级质量较大，VTVL 系统更偏向低重力环境和末端控制；在地球高质量起飞时，任务规则通常要求保留足够跑道和复飞窗口。</p>
|
||||
<p>进取级主推进系统为 1 台 NV-PL "New Frontier" 等离子气塞发动机，额定推力约 1780 kN。该发动机服务于轨道机动、深空转移修正、返回前制动和部分中止模式。单台大推力布局节省尾段空间并简化推进剂管路，但对发动机健康监测、阀组冗余和制动窗口规划提出更高要求。</p>
|
||||
<p>4 台 VLE-F250 "Lander" 核等离子发动机总推力约 1000 kN，用于垂直起飞、垂直着陆、低重力天体表面转场和跑道复飞辅助。由于进取级质量较大，VTVL 系统更偏向低重力环境和末端控制；在地球高质量起飞时，任务规则通常要求保留足够跑道和复飞窗口。</p>
|
||||
<p>姿态控制系统包含 40 个 RCS 推进器，数量高于回声级，以适应更大的惯量、货舱偏载和复杂对接任务。电源系统由货舱后部的紧凑型弧反应堆提供，可为客舱、货舱、推进辅助系统、生命支持、停泊设备和长时间地面待机供电。</p>
|
||||
<p>主发动机制动是进取级飞行规则中的核心环节。由于热防护系统按低地球轨道级再入条件设计，任何来自高轨、月球或火星转移轨道的返回任务，都必须在再入前完成一次或多次制动，将速度和热流降至允许范围。若主发动机健康状态不满足制动要求，任务会转入延迟返回、轨道停泊或请求救援流程。</p>
|
||||
<p>VTVL 发动机主要用于月球、火星和无跑道前哨站任务，也可在跑道进近阶段提供复飞辅助。运营规则禁止在高载荷、低推进剂余量和不明着陆点条件下执行表面下降；任务控制必须同时确认着陆点承载、喷流尘埃、发动机热状态和备用上升窗口。</p>
|
||||
@@ -238,7 +239,7 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td>出发前补给</td><td>补充生命支持消耗品、备件、返回容器和实验载荷。</td><td>回声级可执行临时补件，进取级负责计划内中型补给批次。</td></tr>
|
||||
<tr><td>返航后卸载</td><td>接收样品箱、故障设备、替换下来的任务模块和轮换乘员。</td><td>回声级优先转运需快速处理的小型样品，进取级负责集中回收和批量运输。</td></tr>
|
||||
</tbody></table>
|
||||
<p>母舰支援任务通常以“重载干线、进取级中型转运、回声级末端摆渡”的方式组织。秃鹫航天飞机改进乙型或其他重型运载系统将大型结构送入装配轨道；进取级运输中型任务包、工程班组和补给批次；回声级负责临时检查、人员快线和远征抵达后的表面往返。</p>
|
||||
<p>母舰支援任务通常以"重载干线、进取级中型转运、回声级末端摆渡"的方式组织。秃鹫航天飞机改进乙型或其他重型运载系统将大型结构送入装配轨道；进取级运输中型任务包、工程班组和补给批次；回声级负责临时检查、人员快线和远征抵达后的表面往返。</p>
|
||||
<p>进取级通常不随母舰进入长周期远征，主要原因是任务经济性和待命维护条件不适合长期外部携带。它的体积、货舱和短期高容量载人能力适合近程集中运输；长期挂载在母舰外侧会占用质量、热控、供电和维护资源，且不适合承担目标系统内的多次小批量摆渡。</p>
|
||||
|
||||
<h3 id="母舰任务中的典型流程">母舰任务中的典型流程</h3>
|
||||
@@ -276,37 +277,36 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
</tbody></table>
|
||||
|
||||
<h2 id="运用历史">运用历史</h2>
|
||||
<p>进取级的试飞节奏晚于回声级。回声级验证双模式飞控和小型升力体平台后，进取级项目吸收其控制律、热防护检查和对接口程序，用于更大机身和更高载荷。2060 年代初，进取级完成结构和推进验证；2063 年后逐步承担地月系统客货常态化运输。</p>
|
||||
<p>早期任务以结构和推进验证为主，重点确认 MK3 圆柱机身在 25 吨级载荷下的弯曲余量、货舱门循环寿命、顶部对接口硬捕获载荷和重载跑道着陆。载人认证后，进取级开始服务月球基地扩建、轨道船坞补给和母舰停泊验证。2065 年后的任务记录显示，进取级逐渐成为母舰出发前后最常用的中型运输平台之一。</p>
|
||||
<p>进取级的试飞节奏紧随回声级之后。回声级验证双模式飞控和小型升力体平台后，进取级项目吸收其控制律、热防护检查和对接口程序，用于更大机身和更高载荷。2057 年完成结构和推进验证，2058 年完成载人认证后即投入运营。截至 2060 年 3 月，进取级处于运营初期阶段，累计完成约 36 次飞行，机队规模持续增长中。</p>
|
||||
<p>早期任务以结构和推进验证为主，重点确认 MK3 圆柱机身在 25 吨级载荷下的弯曲余量、货舱门循环寿命、顶部对接口硬捕获载荷和重载跑道着陆。载人认证后，进取级开始服务月球基地补给、轨道船坞运输和母舰停泊验证。2059 年后的任务记录显示，进取级逐渐成为母舰出发前后常用的中型运输平台之一。</p>
|
||||
|
||||
<h3 id="主要任务节点">主要任务节点</h3>
|
||||
<table>
|
||||
<thead><tr><th>任务编号</th><th>时间</th><th>任务</th><th>结果</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>EN-S1</td><td>2060</td><td>地面结构样机和货舱门循环试验</td><td>确认 MK3 机身和 25 吨级货舱框架余量。</td></tr>
|
||||
<tr><td>EN-V1</td><td>2061</td><td>低重力 VTVL 起降模拟和悬停测试</td><td>完成辅助发动机推力分配和重心偏移控制。</td></tr>
|
||||
<tr><td>EN-O1</td><td>2062</td><td>首次无人入轨与重载返回</td><td>验证主发动机制动、货舱偏载和跑道着陆。</td></tr>
|
||||
<tr><td>EN-C1</td><td>2063</td><td>首次载人运输任务</td><td>完成 6 名机组和 16 名乘客短期运输认证。</td></tr>
|
||||
<tr><td>EN-L2</td><td>2064</td><td>月球基地补给任务</td><td>完成 25 吨级货物转运和低重力 VTVL 卸载流程。</td></tr>
|
||||
<tr><td>EN-M3</td><td>2065</td><td>星际探索母舰停泊任务</td><td>完成顶部结构对接口停泊、补给转移和长期供电测试。</td></tr>
|
||||
<tr><td>EN-D4</td><td>2065</td><td>轨道船坞任务包转运</td><td>将加压设备架、外部工具箱和任务控制席送至母舰装配平台。</td></tr>
|
||||
<tr><td>EN-R5</td><td>2066</td><td>远征返航样品与设备集中回收</td><td>完成多批次样品箱、故障设备和轮换乘员转运。</td></tr>
|
||||
<tr><td>EN-H2</td><td>2066</td><td>火星轨道中型补给</td><td>验证火星轨道平台到前哨站转运流程，并修订 VTVL 推力架检查标准。</td></tr>
|
||||
<tr><td>EN-S1</td><td>2057</td><td>地面结构样机和货舱门循环试验</td><td>确认 MK3 机身和 25 吨级货舱框架余量。</td></tr>
|
||||
<tr><td>EN-V1</td><td>2057</td><td>低重力 VTVL 起降模拟和悬停测试</td><td>完成辅助发动机推力分配和重心偏移控制。</td></tr>
|
||||
<tr><td>EN-O1</td><td>2058</td><td>首次无人入轨与重载返回</td><td>验证主发动机制动、货舱偏载和跑道着陆。</td></tr>
|
||||
<tr><td>EN-C1</td><td>2058</td><td>首次载人运输任务</td><td>完成 6 名机组和 16 名乘客短期运输认证。</td></tr>
|
||||
<tr><td>EN-L2</td><td>2059</td><td>月球基地补给任务</td><td>完成 25 吨级货物转运和低重力 VTVL 卸载流程。</td></tr>
|
||||
<tr><td>EN-M3</td><td>2059</td><td>星际探索母舰停泊任务</td><td>完成顶部结构对接口停泊、补给转移和长期供电测试。</td></tr>
|
||||
<tr><td>EN-D2</td><td>2059</td><td>轨道船坞重载部署任务</td><td>将加压设备架、外部工具箱和任务控制席送至母舰装配平台。</td></tr>
|
||||
<tr><td>EN-R3</td><td>2060</td><td>应急返回验证任务</td><td>在加急再入流程下完成多批次样品箱、故障设备和轮换乘员转运。</td></tr>
|
||||
<tr><td>EN-H2</td><td>2060</td><td>高轨重型投送任务</td><td>验证高轨道平台到前哨站转运流程，并修订 VTVL 推力架检查标准。</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h3 id="历史飞行次数">历史飞行次数</h3>
|
||||
<p>进取级飞行频次低于回声级，但平均单次运输质量和乘员数量更高。早期统计将其分为验证阶段、载人认证阶段和中型运营阶段。</p>
|
||||
<p>进取级飞行频次低于回声级，但平均单次运输质量和乘员数量更高。截至 2060 年 3 月，累计完成约 36 次飞行。早期统计将其分为测试阶段、载人认证与提速阶段和运营阶段。</p>
|
||||
<div class="launch-chart" role="img" aria-label="进取级航天飞机历史飞行次数示意图">
|
||||
<div class="launch-row launch-head"><span>年份</span><span>飞行次数</span><span>次数</span><span>累计</span></div>
|
||||
<div class="launch-stage-label">验证阶段</div>
|
||||
<div class="launch-row"><span>2061</span><span class="launch-track"><span class="launch-bar" style="width:8%;"></span></span><span class="launch-count">4</span><span class="launch-cumulative">4</span></div>
|
||||
<div class="launch-row"><span>2062</span><span class="launch-track"><span class="launch-bar" style="width:16%;"></span></span><span class="launch-count">8</span><span class="launch-cumulative">12</span></div>
|
||||
<div class="launch-stage-label">载人认证阶段</div>
|
||||
<div class="launch-row"><span>2063</span><span class="launch-track"><span class="launch-bar" style="width:29%;"></span></span><span class="launch-count">14</span><span class="launch-cumulative">26</span></div>
|
||||
<div class="launch-stage-label">中型运营阶段</div>
|
||||
<div class="launch-row"><span>2064</span><span class="launch-track"><span class="launch-bar" style="width:53%;"></span></span><span class="launch-count">26</span><span class="launch-cumulative">52</span></div>
|
||||
<div class="launch-row"><span>2065</span><span class="launch-track"><span class="launch-bar" style="width:78%;"></span></span><span class="launch-count">38</span><span class="launch-cumulative">90</span></div>
|
||||
<div class="launch-row"><span>2066</span><span class="launch-track"><span class="launch-bar" style="width:100%;"></span></span><span class="launch-count">49</span><span class="launch-cumulative">139</span></div>
|
||||
<div class="launch-stage-label">测试阶段</div>
|
||||
<div class="launch-row"><span>2057</span><span class="launch-track"><span class="launch-bar" style="width:17%;"></span></span><span class="launch-count">3</span><span class="launch-cumulative">3</span></div>
|
||||
<div class="launch-stage-label">载人认证与提速阶段</div>
|
||||
<div class="launch-row"><span>2058</span><span class="launch-track"><span class="launch-bar" style="width:56%;"></span></span><span class="launch-count">10</span><span class="launch-cumulative">13</span></div>
|
||||
<div class="launch-stage-label">运营阶段</div>
|
||||
<div class="launch-row"><span>2059</span><span class="launch-track"><span class="launch-bar" style="width:100%;"></span></span><span class="launch-count">18</span><span class="launch-cumulative">31</span></div>
|
||||
<div class="launch-row"><span>2060</span><span class="launch-track"><span class="launch-bar" style="width:28%;"></span></span><span class="launch-count">~5</span><span class="launch-cumulative">~36</span></div>
|
||||
<div class="launch-row" style="grid-column:1/-1;color:#54595d;font-style:italic;margin-top:4px">说明：2060 年数据截至 3 月。</div>
|
||||
</div>
|
||||
|
||||
<h2 id="机队与编号">机队与编号</h2>
|
||||
@@ -331,16 +331,16 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<table>
|
||||
<thead><tr><th>任务编号</th><th>阶段</th><th>事件</th><th>后续处理</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>EN-V2</td><td>2061 VTVL 验证</td><td>重心偏后导致悬停阶段姿态控制余量偏低。</td><td>调整货舱配载限制，增加 VTVL 前重心自动校验。</td></tr>
|
||||
<tr><td>EN-O1</td><td>2062 轨道试飞</td><td>主发动机长时间制动点火中出现高频振动告警。</td><td>修改喷口冷却和振动阈值，要求关键任务保留备用制动窗口。</td></tr>
|
||||
<tr><td>EN-C2</td><td>2063 载人认证</td><td>对接硬捕获时顶部结构对接口载荷接近限制值。</td><td>降低末端接近速度，改进母舰停泊接口阻尼设置。</td></tr>
|
||||
<tr><td>EN-L3</td><td>2064 月球补给</td><td>重载跑道返回后起落架节点需要额外复检。</td><td>重载返回任务加入落地后无损检测和热防护扩展检查。</td></tr>
|
||||
<tr><td>EN-D4</td><td>2065 船坞补给</td><td>货舱门锁扣传感器在对接后给出间歇性告警。</td><td>任务延迟卸载，落地后更换锁扣传感器并增加货舱门振动检查。</td></tr>
|
||||
<tr><td>EN-R5</td><td>2066 返回载荷</td><td>样品返回容器固定点在再入后出现局部热痕。</td><td>加强返回容器隔热垫和货舱局部热流模型。</td></tr>
|
||||
<tr><td>EN-V2</td><td>2057 VTVL 验证</td><td>重心偏后导致悬停阶段姿态控制余量偏低。</td><td>调整货舱配载限制，增加 VTVL 前重心自动校验。</td></tr>
|
||||
<tr><td>EN-O1</td><td>2058 轨道试飞</td><td>主发动机长时间制动点火中出现高频振动告警。</td><td>修改喷口冷却和振动阈值，要求关键任务保留备用制动窗口。</td></tr>
|
||||
<tr><td>EN-C2</td><td>2058 载人认证</td><td>对接硬捕获时顶部结构对接口载荷接近限制值。</td><td>降低末端接近速度，改进母舰停泊接口阻尼设置。</td></tr>
|
||||
<tr><td>EN-L3</td><td>2059 月球补给</td><td>重载跑道返回后起落架节点需要额外复检。</td><td>重载返回任务加入落地后无损检测和热防护扩展检查。</td></tr>
|
||||
<tr><td>EN-D4</td><td>2059 船坞补给</td><td>货舱门锁扣传感器在对接后给出间歇性告警。</td><td>任务延迟卸载，落地后更换锁扣传感器并增加货舱门振动检查。</td></tr>
|
||||
<tr><td>EN-R5</td><td>2060 返回载荷</td><td>样品返回容器固定点在再入后出现局部热痕。</td><td>加强返回容器隔热垫和货舱局部热流模型。</td></tr>
|
||||
</tbody></table>
|
||||
|
||||
<h3 id="安全规则">安全规则</h3>
|
||||
<p>进取级的安全规则强调“保守放行、分段确认、延迟优先”。如果主发动机制动、VTVL 下降、对接口硬捕获或重载着陆任一关键条件不满足，任务控制通常选择延迟窗口、转入备用轨道或卸载部分任务，并中止原计划的高风险阶段。</p>
|
||||
<p>进取级的安全规则强调"保守放行、分段确认、延迟优先"。如果主发动机制动、VTVL 下降、对接口硬捕获或重载着陆任一关键条件不满足，任务控制通常选择延迟窗口、转入备用轨道或卸载部分任务，并中止原计划的高风险阶段。</p>
|
||||
<p>载人任务中，客舱应急撤离路径必须在货舱装载后重新确认。医疗撤离或高密度客运构型会减少部分货舱任务包，并增加氧气、水循环和二氧化碳处理余量。母舰停泊任务还要求母舰侧接口具备稳定姿态、供电接收和紧急释放能力。</p>
|
||||
|
||||
<h2 id="成本与经济性">成本与经济性</h2>
|
||||
@@ -364,6 +364,8 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td>类型</td><td>全可重复使用中型航天飞机</td></tr>
|
||||
<tr><td>计划关系</td><td>回声级 / 进取级双型号计划中的重型成员</td></tr>
|
||||
<tr><td>主要任务</td><td>中型客货运输、基地补给、母舰装配与补给支援、短期高容量运输、返回载荷运输</td></tr>
|
||||
<tr><td>首飞</td><td>2057 年</td></tr>
|
||||
<tr><td>服役</td><td>2058 年</td></tr>
|
||||
<tr><th colspan="2">总体尺寸与质量</th></tr>
|
||||
<tr><td>机身</td><td>MK3 圆柱机身，主体直径约 3.75 m</td></tr>
|
||||
<tr><td>全长</td><td>29.8 米</td></tr>
|
||||
@@ -373,8 +375,8 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td>最大起飞质量</td><td>80 吨</td></tr>
|
||||
<tr><td>燃料</td><td>14.4 吨高能液态燃料</td></tr>
|
||||
<tr><th colspan="2">推进与飞控</th></tr>
|
||||
<tr><td>主发动机</td><td>1 台 NV-PL “New Frontier” 等离子气塞发动机，推力约 1780 kN</td></tr>
|
||||
<tr><td>VTVL 发动机</td><td>4 台 VLE-F250 “Lander” 核等离子发动机，总推力约 1000 kN</td></tr>
|
||||
<tr><td>主发动机</td><td>1 台 NV-PL "New Frontier" 等离子气塞发动机，推力约 1780 kN</td></tr>
|
||||
<tr><td>VTVL 发动机</td><td>4 台 VLE-F250 "Lander" 核等离子发动机，总推力约 1000 kN</td></tr>
|
||||
<tr><td>RCS 推进器</td><td>40 个</td></tr>
|
||||
<tr><td>速度增量</td><td>无载荷约 65.4 km/s；25 吨载荷约 42 km/s</td></tr>
|
||||
<tr><td>无人飞行能力</td><td>具备全无人飞行能力</td></tr>
|
||||
|
||||
@@ -66,7 +66,8 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td><b>Lineage</b>: STS Shuttle - CERV Shuttle - Vulture Shuttle</td></tr>
|
||||
<tr><td><b>Predecessor</b>: CERV Shuttle</td></tr>
|
||||
<tr><td><b>Development start</b>: 2030</td></tr>
|
||||
<tr><td><b>First flight</b>: 2038, uncrewed orbital flight</td></tr>
|
||||
<tr><td><b>First flight</b>: March 2037 (VLT-01, uncrewed orbital test, VS-01 <i>Endurance</i>)</td></tr>
|
||||
<tr><td><b>Entered service</b>: 2039</td></tr>
|
||||
<tr><td><b>Main launch site</b>: Wenchang</td></tr>
|
||||
<tr><td><b>Typical target orbit</b>: 1000 km x 1000 km, 45 degrees</td></tr>
|
||||
<tr><td><b>Block 1 payload</b>: 100 t to the typical target orbit</td></tr>
|
||||
@@ -74,15 +75,17 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td><b>Liftoff thrust</b>: 61,949 kN</td></tr>
|
||||
<tr><td><b>Maximum crew</b>: 19</td></tr>
|
||||
<tr><td><b>Status</b>: In service</td></tr>
|
||||
<tr><td><b>Total flights</b>: 2,266 (through March 2060)</td></tr>
|
||||
</tbody></table>
|
||||
<p>The <b>Vulture Shuttle</b> is the third major vehicle in the STS Shuttle - CERV Shuttle - Vulture Shuttle lineage in this alternate spaceflight timeline. It keeps the classic orbiter, external tank, and side-booster arrangement, but replaces solid boosters with reusable liquid boosters and scales the orbiter into the large MK4 class.</p>
|
||||
<p>Vulture was designed as a heavy high-orbit transport rather than a low Earth orbit utility shuttle. A typical Block 1 mission can deliver a 100 t payload to a 1000 km x 1000 km orbit at 45 degrees inclination. The launch stack inserts the orbiter into a high suborbital trajectory, after which the orbiter completes circularization and mission operations using its own OMS system.</p>
|
||||
<p>Vulture development began in 2030 as a heavy successor to CERV. The first uncrewed orbital test flight, VLT-01, launched in March 2037 aboard VS-01 <i>Endurance</i>. The system entered operational service in 2039 and became the primary shuttle-line heavy transport after CERV retirement in 2040. By March 2060 the fleet had accumulated 2,266 flights across ten orbiters in three blocks.</p>
|
||||
<nav class="toc" aria-label="Contents">
|
||||
<div class="toc-title">Contents</div>
|
||||
<ol>
|
||||
<li><a href="#development">Development</a></li>
|
||||
<li><a href="#system-components">System components</a></li>
|
||||
<li><a href="#mission-profile">Mission profile</a></li>
|
||||
<li><a href="#fleet">Fleet</a></li>
|
||||
<li><a href="#operational-history">Operational history</a></li>
|
||||
<li><a href="#block-15">Block 1.5</a></li>
|
||||
<li><a href="#block-2">Block 2</a></li>
|
||||
@@ -94,8 +97,8 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
</ol>
|
||||
</nav>
|
||||
<h2 id="development">Development</h2>
|
||||
<p>The alternate timeline diverges from real-world shuttle history after the Columbia accident, which still occurs in 2003 and becomes the central safety lesson for later shuttle development. The CERV Shuttle, developed from 2005 and first flown in 2015, extends the shuttle lineage with an integrated crew-cabin escape system, modern avionics, and improved maintainability.</p>
|
||||
<p>Vulture development begins in 2030 as a heavier successor to CERV. Instead of being a modest safety upgrade, it is designed for heavy high-orbit logistics, large station modules, and the assembly of interplanetary exploration motherships. Key choices include an enlarged MK4 orbiter, a 10 m external tank, reusable 5 m liquid boosters, and an expanded crew escape concept inherited from CERV.</p>
|
||||
<p>The alternate timeline diverges from real-world shuttle history after the Columbia accident, which still occurs in 2003 and becomes the central safety lesson for later shuttle development. The CERV Shuttle, developed from 2005 and first flown in 2015, extends the shuttle lineage with an integrated crew-cabin escape system, modern avionics, and improved maintainability. CERV operated from 2017 to 2040, accumulating 666 flights.</p>
|
||||
<p>Vulture development begins in 2030 as a heavier successor to CERV. Instead of being a modest safety upgrade, it is designed for heavy high-orbit logistics, large station modules, and the assembly of interplanetary exploration motherships. Key choices include an enlarged MK4 orbiter, a 10 m external tank, reusable 5 m liquid boosters, and an expanded crew escape concept inherited from CERV. The first Block 1 orbiter, VS-01 <i>Endurance</i>, conducted its maiden uncrewed orbital flight in March 2037. After a two-year test and certification campaign, Vulture entered operational service in 2039. CERV was fully retired in 2040, completing the handover to the third-generation shuttle.</p>
|
||||
<h2 id="system-components">System components</h2>
|
||||
<h3 id="orbiter">Orbiter</h3>
|
||||
<figure class="thumb tright"><a class="media-link" href="#vulture-img-ascent"><img src="/vulture/vulture_ascent_original.png" alt="Vulture Shuttle during ascent" data-wiki-asset="/vulture/vulture_ascent_original.png"></a><figcaption class="thumbcaption">The MK4 orbiter uses a large delta wing, wingtip vertical tails, canards, and a retractable nose docking port.</figcaption></figure>
|
||||
@@ -110,40 +113,90 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<figure class="thumb tright"><a class="media-link" href="#vulture-img-separation"><img src="/vulture/vulture_booster_separation_original.png" alt="Vulture liquid booster separation" data-wiki-asset="/vulture/vulture_booster_separation_original.png"></a><figcaption class="thumbcaption">After booster cutoff, the reusable liquid boosters separate and return to the launch site while the orbiter and external tank continue upward.</figcaption></figure>
|
||||
<p>During ascent, the liquid boosters and five RS-25E main engines operate together. After booster cutoff and separation, the boosters return to the launch site while the orbiter and external tank continue to a high suborbital insertion. After main engine cutoff, the orbiter separates from the external tank and uses OMS burns to enter and raise its orbit.</p>
|
||||
<p>Abort modes include pad abort, RTLS, Abort to Orbit, and Abort Once Around. Because the orbiter has five RS-25E engines, not every main-engine shutdown triggers an abort. After booster separation, one failed RS-25E is usually tolerated; after T+6 minutes, two failures may still permit orbit insertion; after T+8 minutes, three shutdowns can still result in a low-margin but normal orbit if other systems remain healthy.</p>
|
||||
<h2 id="fleet">Fleet</h2>
|
||||
<p>Ten Vulture orbiters have been built across three blocks. Five Block 1 orbiters have been retired, two Block 1.5 orbiters are currently active, and three Block 2 orbiters are currently active. Flight rates are approximately 12 flights per year per Block 1 orbiter, 24 per year per Block 1.5 orbiter, and 48 per year per Block 2 orbiter.</p>
|
||||
<h3 id="fleet-block1">Block 1 (Retired)</h3>
|
||||
<table>
|
||||
<thead><tr><th>Vehicle</th><th>Name</th><th>Service Period</th><th>Total Flights</th><th>Status</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>VS-01</td><td><i>Endurance</i></td><td>2037-03 to 2057-06</td><td>240</td><td>Retired</td></tr>
|
||||
<tr><td>VS-02</td><td><i>Perseverance</i></td><td>2038-01 to 2057-11</td><td>235</td><td>Retired</td></tr>
|
||||
<tr><td>VS-03</td><td><i>Courage</i></td><td>2039-05 to 2058-03</td><td>240</td><td>Retired</td></tr>
|
||||
<tr><td>VS-04</td><td><i>Determination</i></td><td>2040-02 to 2058-08</td><td>228</td><td>Retired</td></tr>
|
||||
<tr><td>VS-05</td><td><i>Patience</i></td><td>2041-07 to 2056-12</td><td>132</td><td>Retired</td></tr>
|
||||
</tbody></table>
|
||||
<p>VS-05 <i>Patience</i> underwent a nuclear thermal OMS conversion in 2048, which reduced its flight rate compared to other Block 1 vehicles. All five Block 1 orbiters operated at a nominal rate of 12 flights per year. The Block 1 fleet accumulated 1,075 flights before the last vehicle retired in August 2058.</p>
|
||||
<h3 id="fleet-block15">Block 1.5 (Active as of March 2060)</h3>
|
||||
<table>
|
||||
<thead><tr><th>Vehicle</th><th>Name</th><th>Block 1 Period</th><th>Conversion</th><th>Block 1.5 Period</th><th>Flights (B1/B1.5)</th><th>Status</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>VS-06</td><td><i>Fortitude</i></td><td>2042 to 2051</td><td>2051-2052</td><td>2052 to present</td><td>305 (108 / 197)</td><td>Active</td></tr>
|
||||
<tr><td>VS-07</td><td><i>Loyalty</i></td><td>2043 to 2052</td><td>2052-2053</td><td>2053 to present</td><td>280 (108 / 172)</td><td>Active</td></tr>
|
||||
</tbody></table>
|
||||
<p>VS-06 <i>Fortitude</i> and VS-07 <i>Loyalty</i> were originally built as Block 1 vehicles and served in that configuration for approximately nine years each. Both were converted to Block 1.5 standard with nuclear aerospike propulsion and continue to operate at approximately 24 flights per year each.</p>
|
||||
<h3 id="fleet-block2">Block 2 (Active as of March 2060)</h3>
|
||||
<table>
|
||||
<thead><tr><th>Vehicle</th><th>Name</th><th>Service Period</th><th>Total Flights</th><th>Status</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>VS-08</td><td><i>Honor</i></td><td>2055-03 to present</td><td>250</td><td>Active</td></tr>
|
||||
<tr><td>VS-09</td><td><i>Conviction</i></td><td>2056-06 to present</td><td>202</td><td>Active</td></tr>
|
||||
<tr><td>VS-10</td><td><i>Hope</i></td><td>2057-08 to present</td><td>154</td><td>Active</td></tr>
|
||||
</tbody></table>
|
||||
<p>All three Block 2 vehicles operate at approximately 48 flights per year each. Built with nuclear aerospike propulsion from the start, they carry about 120 t to low lunar orbit and are the primary heavy-lift vehicles for the current fleet.</p>
|
||||
<h2 id="operational-history">Operational history</h2>
|
||||
<p>Vulture first flies an uncrewed orbital test mission in 2038 and becomes the main shuttle-line heavy transport after CERV retirement in 2040. During the 2040s and early 2050s it supports large orbital facilities and the construction of exploration motherships, including Xihe (XH-01), Stellaria (ST-01), and the second early ST-series Stellaria-class ship (ST-02).</p>
|
||||
<p>Vulture's first flight, VLT-01, launched in March 2037 with VS-01 <i>Endurance</i> on an uncrewed orbital test mission. VS-02 <i>Perseverance</i> joined the fleet in January 2038. After a two-year test and certification campaign, Vulture entered operational service in 2039, with VS-03 <i>Courage</i> joining that May. VS-04 <i>Determination</i> followed in February 2040, and CERV completed its handover with retirement the same year.</p>
|
||||
<p>Through the 2040s, the Block 1 fleet expanded to seven vehicles with the addition of VS-05 <i>Patience</i> (July 2041), VS-06 <i>Fortitude</i> (2042), and VS-07 <i>Loyalty</i> (2043). With seven Block 1 orbiters each flying approximately 12 times per year, the fleet achieved an annual rate of about 84 flights. VS-05 underwent a nuclear thermal OMS conversion in 2048, pioneering high-energy propulsion integration on the MK4 airframe, though this reduced its flight rate for the remainder of its career.</p>
|
||||
<p>During the 2040s and early 2050s, Vulture supported large orbital facilities and the construction of exploration motherships, including Xihe (XH-01), Stellaria (ST-01), and the second early ST-series Stellaria-class ship (ST-02). The fleet reached its peak Block 1 tempo in the late 2040s.</p>
|
||||
<p>In 2051, VS-06 <i>Fortitude</i> was withdrawn from Block 1 service for conversion to Block 1.5 standard, completing the process in 2052. VS-07 <i>Loyalty</i> followed, converting between 2052 and 2053. The Block 1.5 vehicles operate at approximately 24 flights per year each, roughly double the Block 1 rate.</p>
|
||||
<p>The Block 2 era began in March 2055 with the first flight of VS-08 <i>Honor</i>, followed by VS-09 <i>Conviction</i> in June 2056 and VS-10 <i>Hope</i> in August 2057. Block 2 vehicles operate at approximately 48 flights per year each. The Block 1 fleet phased out during 2056-2058, with VS-05 retiring in December 2056, VS-01 in June 2057, VS-02 in November 2057, VS-03 in March 2058, and VS-04 in August 2058.</p>
|
||||
<p>As of March 2060, the active fleet consists of five vehicles: two Block 1.5 (VS-06, VS-07) and three Block 2 (VS-08, VS-09, VS-10), with the fleet having accumulated a total of 2,266 flights.</p>
|
||||
<p>The Echo Shuttle (first flight 2056, operational 2057) and Enterprise Shuttle (first flight 2057, operational 2058) have since joined the shuttle lineage as fourth-generation SSTO-capable vehicles, complementing the Vulture fleet in the late 2050s.</p>
|
||||
<h2 id="block-15">Block 1.5</h2>
|
||||
<p>Block 1.5 is a high-energy propulsion conversion of the VS-06 and VS-07 Block 1 orbiters. It installs nuclear aerospike engines and modifies propellant management, thermal isolation, aft structure, flight software, and ground safety procedures. Its core ability is SSTO operation, but payload is reduced to about 40 t.</p>
|
||||
<p>Block 1.5 is a high-energy propulsion conversion of the VS-06 and VS-07 Block 1 orbiters. It installs nuclear aerospike engines and modifies propellant management, thermal isolation, aft structure, flight software, and ground safety procedures. Its core ability is SSTO operation, but payload is reduced to about 40 t. Conversion of each vehicle takes approximately one year. Flight rate increases from the Block 1 baseline of 12 to approximately 24 flights per year per orbiter.</p>
|
||||
<h2 id="block-2">Block 2</h2>
|
||||
<p>Block 2 is a later production standard rather than a simple conversion. VS-08, VS-09, and VS-10 are built around nuclear aerospike propulsion, deep-space communications, high-energy propellant management, and stricter re-entry limits. Block 2 can carry about 120 t directly to low lunar orbit and return, but return payload is limited to about 40 t and requires braking to low-Earth-orbit-class re-entry speed.</p>
|
||||
<p>Block 2 is a later production standard rather than a simple conversion. VS-08, VS-09, and VS-10 are built around nuclear aerospike propulsion, deep-space communications, high-energy propellant management, and stricter re-entry limits. Block 2 can carry about 120 t directly to low lunar orbit and return, but return payload is limited to about 40 t and requires braking to low-Earth-orbit-class re-entry speed. Block 2 vehicles operate at approximately 48 flights per year each. First flight was VS-08 <i>Honor</i> in March 2055.</p>
|
||||
<h2 id="safety-and-incidents">Safety and incidents</h2>
|
||||
<figure class="thumb tright"><a class="media-link" href="#vulture-img-ignition"><img src="/vulture/vulture_shuttle_ignition_original.png" alt="Vulture Shuttle engine ignition" data-wiki-asset="/vulture/vulture_shuttle_ignition_original.png"></a><figcaption class="thumbcaption">Pad abort logic was a central part of the Vulture safety case, especially before booster ignition.</figcaption></figure>
|
||||
<p>Vulture's safety design responds directly to STS-era risks: solid boosters are replaced by throttleable liquid boosters, external-tank insulation shedding is reduced, orbiter leading edges and belly tiles are instrumented, and the crew cabin can separate as an escape module in a wider range of emergencies.</p>
|
||||
<table>
|
||||
<thead><tr><th>Mission</th><th>Year</th><th>Event</th><th>Outcome</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>VLT-02</td><td>2038</td><td>Pad abort after RS-25E sensor disagreement</td><td>Main engines shut down before booster ignition</td></tr>
|
||||
<tr><td>VLT-12</td><td>2039</td><td>Abort to Orbit after two early RS-25E shutdowns</td><td>Safe parking orbit and early return</td></tr>
|
||||
<tr><td>VLT-246</td><td>2047</td><td>Two RS-25E shutdowns after T+6 minutes</td><td>Normal orbit with OMS correction</td></tr>
|
||||
<tr><td>VLT-633</td><td>2053</td><td>Three RS-25E shutdowns after T+8 minutes</td><td>Low-margin normal orbit</td></tr>
|
||||
<tr><td>VLT-762</td><td>2055</td><td>Block 2 braking anomaly before lunar-return re-entry</td><td>Return delayed and completed safely</td></tr>
|
||||
<tr><td>VLT-02</td><td>2037</td><td>Pad abort after RS-25E sensor disagreement</td><td>Main engines shut down before booster ignition</td></tr>
|
||||
<tr><td>VLT-14</td><td>2038</td><td>Abort to Orbit after two early RS-25E shutdowns</td><td>Safe parking orbit and early return</td></tr>
|
||||
<tr><td>VLT-287</td><td>2045</td><td>Two RS-25E shutdowns after T+6 minutes</td><td>Normal orbit with OMS correction</td></tr>
|
||||
<tr><td>VLT-831</td><td>2053</td><td>Three RS-25E shutdowns after T+8 minutes</td><td>Low-margin normal orbit</td></tr>
|
||||
<tr><td>VLT-1135</td><td>2056</td><td>Block 2 braking anomaly before lunar-return re-entry</td><td>Return delayed and completed safely</td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="launch-history">Launch history</h2>
|
||||
<p>The launch history uses the same count basis as the main Vulture article: 24 cumulative launches by the end of the research phase in 2040, 310 cumulative launches by the end of the main ramp-up phase in 2048, 620 by the end of the mothership-construction peak in 2052, and about 785 by the end of the early Block 2 period in 2055.</p>
|
||||
<p>The Vulture fleet accumulated 2,266 flights between March 2037 and March 2060. Annual flight rate grew from 8 flights in the partial first year to a peak of 205 in 2057 as Block 2 vehicles came online. As of March 2060 the fleet is flying at an annualized rate of approximately 192 flights per year (2 Block 1.5 at 24/yr each + 3 Block 2 at 48/yr each).</p>
|
||||
<div class="launch-chart" role="img" aria-label="Vulture Shuttle historical launch count chart">
|
||||
<div class="launch-row launch-head"><span>Year</span><span>Flights</span><span>No.</span><span>Total</span></div>
|
||||
<div class="launch-stage-label">Research and certification phase</div>
|
||||
<div class="launch-row"><span>2038</span><span class="launch-track"><span class="launch-bar" style="width:2%;"></span></span><span class="launch-count">2</span><span class="launch-cumulative">2</span></div>
|
||||
<div class="launch-row"><span>2039</span><span class="launch-track"><span class="launch-bar" style="width:5%;"></span></span><span class="launch-count">8</span><span class="launch-cumulative">10</span></div>
|
||||
<div class="launch-row"><span>2040</span><span class="launch-track"><span class="launch-bar" style="width:8%;"></span></span><span class="launch-count">14</span><span class="launch-cumulative">24</span></div>
|
||||
<div class="launch-stage-label">Main operations ramp-up</div>
|
||||
<div class="launch-row"><span>2044</span><span class="launch-track"><span class="launch-bar" style="width:30%;"></span></span><span class="launch-count">58</span><span class="launch-cumulative">112</span></div>
|
||||
<div class="launch-row"><span>2048</span><span class="launch-track"><span class="launch-bar" style="width:55%;"></span></span><span class="launch-count">92</span><span class="launch-cumulative">310</span></div>
|
||||
<div class="launch-stage-label">Mothership construction peak</div>
|
||||
<div class="launch-row"><span>2052</span><span class="launch-track"><span class="launch-bar" style="width:85%;"></span></span><span class="launch-count">128</span><span class="launch-cumulative">620</span></div>
|
||||
<div class="launch-stage-label">Early Block 2 period</div>
|
||||
<div class="launch-row"><span>2055</span><span class="launch-track"><span class="launch-bar" style="width:100%;"></span></span><span class="launch-count">54</span><span class="launch-cumulative">785</span></div>
|
||||
<div class="launch-stage-label">Test and certification phase (Block 1, 1-2 orbiters)</div>
|
||||
<div class="launch-row"><span>2037</span><span class="launch-track"><span class="launch-bar" style="width:4%;"></span></span><span class="launch-count">8</span><span class="launch-cumulative">8</span></div>
|
||||
<div class="launch-row"><span>2038</span><span class="launch-track"><span class="launch-bar" style="width:11%;"></span></span><span class="launch-count">22</span><span class="launch-cumulative">30</span></div>
|
||||
<div class="launch-row"><span>2039</span><span class="launch-track"><span class="launch-bar" style="width:16%;"></span></span><span class="launch-count">33</span><span class="launch-cumulative">63</span></div>
|
||||
<div class="launch-row"><span>2040</span><span class="launch-track"><span class="launch-bar" style="width:22%;"></span></span><span class="launch-count">45</span><span class="launch-cumulative">108</span></div>
|
||||
<div class="launch-stage-label">Block 1 fleet expansion (reaching 7 orbiters by 2043)</div>
|
||||
<div class="launch-row"><span>2041</span><span class="launch-track"><span class="launch-bar" style="width:26%;"></span></span><span class="launch-count">54</span><span class="launch-cumulative">162</span></div>
|
||||
<div class="launch-row"><span>2042</span><span class="launch-track"><span class="launch-bar" style="width:35%;"></span></span><span class="launch-count">72</span><span class="launch-cumulative">234</span></div>
|
||||
<div class="launch-row"><span>2043</span><span class="launch-track"><span class="launch-bar" style="width:41%;"></span></span><span class="launch-count">84</span><span class="launch-cumulative">318</span></div>
|
||||
<div class="launch-stage-label">Full Block 1 operations (7 orbiters at 12/yr each)</div>
|
||||
<div class="launch-row"><span>2048</span><span class="launch-track"><span class="launch-bar" style="width:41%;"></span></span><span class="launch-count">84</span><span class="launch-cumulative">738</span></div>
|
||||
<div class="launch-stage-label">Mothership construction peak / Block 1.5 conversion</div>
|
||||
<div class="launch-row"><span>2052</span><span class="launch-track"><span class="launch-bar" style="width:41%;"></span></span><span class="launch-count">84</span><span class="launch-cumulative">1,068</span></div>
|
||||
<div class="launch-stage-label">Block 1.5 operations begin</div>
|
||||
<div class="launch-row"><span>2053</span><span class="launch-track"><span class="launch-bar" style="width:53%;"></span></span><span class="launch-count">108</span><span class="launch-cumulative">1,176</span></div>
|
||||
<div class="launch-row"><span>2054</span><span class="launch-track"><span class="launch-bar" style="width:53%;"></span></span><span class="launch-count">108</span><span class="launch-cumulative">1,284</span></div>
|
||||
<div class="launch-stage-label">Block 2 introduction</div>
|
||||
<div class="launch-row"><span>2055</span><span class="launch-track"><span class="launch-bar" style="width:72%;"></span></span><span class="launch-count">148</span><span class="launch-cumulative">1,432</span></div>
|
||||
<div class="launch-row"><span>2056</span><span class="launch-track"><span class="launch-bar" style="width:90%;"></span></span><span class="launch-count">184</span><span class="launch-cumulative">1,616</span></div>
|
||||
<div class="launch-stage-label">Peak operations (Block 1 retirement, Block 2 full rate)</div>
|
||||
<div class="launch-row"><span>2057</span><span class="launch-track"><span class="launch-bar" style="width:100%;"></span></span><span class="launch-count">205</span><span class="launch-cumulative">1,821</span></div>
|
||||
<div class="launch-row"><span>2058</span><span class="launch-track"><span class="launch-bar" style="width:99%;"></span></span><span class="launch-count">203</span><span class="launch-cumulative">2,024</span></div>
|
||||
<div class="launch-row"><span>2059</span><span class="launch-track"><span class="launch-bar" style="width:94%;"></span></span><span class="launch-count">192</span><span class="launch-cumulative">2,216</span></div>
|
||||
<div class="launch-row"><span>2060</span><span class="launch-track"><span class="launch-bar" style="width:24%;"></span></span><span class="launch-count">50</span><span class="launch-cumulative"><b>2,266</b></span></div>
|
||||
</div>
|
||||
<p style="font-size:90%; color:#54595d;">2060 figures are through March only. Peak annual flight rate was 205 launches in 2057. The active fleet as of March 2060 consists of 2 Block 1.5 and 3 Block 2 orbiters, producing an annualized rate of approximately 192 flights.</p>
|
||||
<h2 id="specifications">Specifications</h2>
|
||||
<table>
|
||||
<thead><tr><th>Parameter</th><th>Value</th></tr></thead>
|
||||
|
||||
+163
-113
@@ -65,12 +65,12 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td class="infobox-image"><img src="/vulture/vulture_shuttle_full_stack_original.png" data-wiki-asset="/vulture/vulture_shuttle_full_stack_original.png" alt="秃鹫航天飞机完整发射构型"><div class="thumbcaption">秃鹫航天飞机由 MK4 轨道器、外挂燃料箱和两枚液体燃料助推器组成。</div></td></tr>
|
||||
<tr><td><b>类型</b>：部分可重复使用航天飞机系统</td></tr>
|
||||
<tr><td><b>时间线</b>：架空时间线</td></tr>
|
||||
<tr><td><b>继承线</b>：STS 航天飞机 - CERV 航天飞机 - 秃鹫航天飞机</td></tr>
|
||||
<tr><td><b>前身</b>：CERV 航天飞机</td></tr>
|
||||
<tr><td><b>世代</b>：第三代航天飞机</td></tr>
|
||||
<tr><td><b>前身</b>：STS 航天飞机（第一代）→ CERV 航天飞机（第二代）</td></tr>
|
||||
<tr><td><b>研发开始</b>：2030 年</td></tr>
|
||||
<tr><td><b>首次飞行</b>：2038 年（无人轨道飞行）</td></tr>
|
||||
<tr><td><b>开始服役</b>：2040 年代初</td></tr>
|
||||
<tr><td><b>主要发射场</b>：文昌</td></tr>
|
||||
<tr><td><b>首次飞行</b>：2037 年（无人轨道飞行）</td></tr>
|
||||
<tr><td><b>开始服役</b>：2039 年</td></tr>
|
||||
<tr><td><b>主要发射场</b>：文昌航天发射场 / 卡纳维拉尔角</td></tr>
|
||||
<tr><td><b>典型任务</b>：高轨重载部署、载人运输、大型在轨设施建设</td></tr>
|
||||
<tr><td><b>典型目标轨道</b>：1000 km x 1000 km，45 度倾角</td></tr>
|
||||
<tr><td><b>典型载荷能力</b>：100 吨至 1000 km x 1000 km、45 度倾角轨道</td></tr>
|
||||
@@ -78,16 +78,17 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td><b>起飞总推力</b>：61,949 kN</td></tr>
|
||||
<tr><td><b>系统组成</b>：MK4 轨道器、外挂燃料箱、2 枚液体燃料助推器</td></tr>
|
||||
<tr><td><b>测试机</b>：2 台结构测试机，1 台大气飞行测试机</td></tr>
|
||||
<tr><td><b>轨道器</b>：VS-01 至 VS-07（Block 1；VS-06/07 后升级为 Block 1.5），VS-08 至 VS-10（改进乙型）</td></tr>
|
||||
<tr><td><b>轨道器</b>：VS-01 至 VS-05（Block 1，已退役）；VS-06 / VS-07（Block 1.5，在役）；VS-08 至 VS-10（Block 2，在役，VS-11 规划中）</td></tr>
|
||||
<tr><td><b>年飞行频次</b>：Block 1 约 12 次/架；Block 1.5 约 24 次/架；Block 2 约 48 次/架</td></tr>
|
||||
<tr><td><b>轨道器主发动机</b>：5 台 RS-25E</td></tr>
|
||||
<tr><td><b>助推器发动机</b>：每枚 19 台“天火-12”液氧煤油发动机</td></tr>
|
||||
<tr><td><b>主要衍生型</b>：Block 1.5，改进乙型</td></tr>
|
||||
<tr><td><b>主要衍生型</b>：Block 1.5，改进乙型（Block 2）</td></tr>
|
||||
<tr><td><b>最大乘员</b>：19 人</td></tr>
|
||||
<tr><td><b>典型任务成本</b>：约 8000 万美元</td></tr>
|
||||
</tbody></table>
|
||||
<p><b>秃鹫航天飞机</b>（英语：<b>Vulture Shuttle</b>）是架空时间线中 CERV 航天飞机的继承者，也是 STS 航天飞机 - CERV 航天飞机 - 秃鹫航天飞机继承线上的第三代大型航天飞机系统。该系统沿用了轨道器、外挂燃料箱和两侧助推器构成的三段式发射布局，但将早期 STS 的固体助推器路线进一步发展为可反推着陆回收的液体燃料助推器，并采用放大后的 MK4 轨道器和 10 米直径外挂燃料箱。</p>
|
||||
<p><b>秃鹫航天飞机</b>（英语：<b>Vulture Shuttle</b>）是架空时间线中继 CERV 航天飞机（第二代）之后开发的第三代大型航天飞机系统。该系统继承 CERV 的轨道器、外挂燃料箱和液体燃料助推器三段式布局，但将 CERV 的 4 米级助推器放大为 5 米级、8.4 米 ET 放大为 10 米级、STS/CERV 尺寸级轨道器放大为 MK4 轨道器，构成面向高轨重载和母舰建造的重型航天飞机。</p>
|
||||
<p>秃鹫航天飞机被设计为高轨重载和载人运输系统，而不只是近地轨道轻载运输工具。其典型任务能力为从文昌发射，将 100 吨级载荷送入 1000 km x 1000 km、45 度倾角轨道。常规任务中，发射组合体首先将轨道器送入约 650 km x 30 km 的亚轨道，随后由轨道器自身的轨道机动系统完成入轨、爬升、圆化、交会、载荷释放和返航机动。</p>
|
||||
<p>该系统于 2030 年作为 CERV 航天飞机的继任型号开始研发，并在 2038 年完成首次无人轨道飞行。2040 年 CERV 航天飞机正式停飞退役后，秃鹫航天飞机成为该继承线的主力重载航天飞机。其早期承担了大型轨道设施和星际探索母舰分段建造的核心运输任务，尤其参与了<a href="/home/Exploration_Motherships/Xihe/XH-01">羲和号（XH-01）</a>、万星源号（ST-01）和万星源NEXT号（ST-02）的在轨组装工作。根据现有任务日志，XH-01 的主建造阶段从 2050 年 3 月持续至 2052 年 2 月，秃鹫航天飞机在这一时期已是成熟的重载航天飞机系统。</p>
|
||||
<p>该系统于 2030 年作为 CERV 航天飞机的继任型号开始研发，并在 2037 年完成首次无人轨道飞行。2039 年正式投入服役，2040 年 CERV 航天飞机正式停飞退役后，秃鹫航天飞机成为该继承线的主力重载航天飞机。其早期承担了大型轨道设施和星际探索母舰分段建造的核心运输任务，尤其参与了<a href="/home/Exploration_Motherships/Xihe/XH-01">羲和号（XH-01）</a>、万星源号（ST-01）和万星源NEXT号（ST-02）的在轨组装工作。根据现有任务日志，XH-01 的主建造阶段从 2050 年 3 月持续至 2052 年 2 月，秃鹫航天飞机在这一时期已是成熟的重载航天飞机系统。</p>
|
||||
<p>与 STS 相比，秃鹫航天飞机的主要改进集中在六个方面：更大的轨道器和载荷舱、更高的高轨有效载荷、可控且可回收的液体助推器、降低碎片风险的外挂箱保温方案、更高冗余度的飞控与推进健康管理，以及整体式乘员舱逃生系统。虽然该系统仍保留了航天飞机构型固有的复杂地面整备流程，但其单次任务成本和复用周转效率较 STS 有显著改善。</p>
|
||||
<p>随着后续高能推进技术的发展，相关项目衍生出若干核气塞发动机方案，秃鹫航天飞机也承担了早期核推进试验平台的角色。VS-05 曾对 OMS 系统进行改造，用于测试热核推进技术；VS-06 和 VS-07 后来安装核气塞发动机并升级为 Block 1.5，具备单级入轨能力，但有效载荷降至约 40 吨。VS-08、VS-09 和 VS-10 则直接按改进乙型标准生产，具备将约 120 吨载荷直飞低月球轨道并返回的能力，但其返回载荷被限制在 40 吨以内，且只能执行制动至近地轨道级速度后的第一宇宙速度再入。</p>
|
||||
<nav class="toc" aria-label="目录">
|
||||
@@ -109,13 +110,13 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
</nav>
|
||||
<h2 id="设计与发展">设计与发展</h2>
|
||||
<h3 id="架空时间线背景">架空时间线背景</h3>
|
||||
<p>架空时间线的航天飞机继承线通常被概括为 STS 航天飞机 - CERV 航天飞机 - 秃鹫航天飞机。该时间线从 2000 年代开始与现实历史分叉：2003 年哥伦比亚航天飞机事故仍然发生，并成为后续航天飞机安全改进的主要转折点。事故暴露出外挂燃料箱泡沫脱落、轨道器热防护脆弱性、上升段逃生能力不足和组织性风险评估缺陷等问题。</p>
|
||||
<p>在这条时间线中，STS 航天飞机没有立即终止全部后续发展，而是推动了一个以乘员逃逸和系统现代化为核心的改进型号。2005 年，CERV 航天飞机开始研制。CERV 在 STS 航天飞机基础上新增乘员舱整体逃逸能力，升级航电系统，并通过材料和结构改进减轻轨道器质量。它并没有彻底改变 STS 的总体构型，而是将安全性、可维护性和航电冗余提升到足以继续维持航天飞机体系的水平。</p>
|
||||
<p>架空时间线的航天飞机发展分为三代：STS 航天飞机（第一代）、CERV 航天飞机（第二代）和秃鹫航天飞机（第三代）。该时间线从 2000 年代开始与现实历史分叉：2003 年哥伦比亚航天飞机事故仍然发生，并成为后续航天飞机安全改进的主要转折点。事故暴露出外挂燃料箱泡沫脱落、轨道器热防护脆弱性、上升段逃生能力不足和组织性风险评估缺陷等问题。</p>
|
||||
<p>在这条时间线中，STS 航天飞机没有立即终止全部后续发展，而是推动了一个以乘员逃逸和系统现代化为核心的改进型号。2005 年，第二代 CERV 航天飞机开始研制，在 STS 基础上新增乘员舱整体逃逸能力、电传飞控系统和复合材料减重，将安全性、可维护性和航电冗余提升到足以继续维持航天飞机体系的水平。</p>
|
||||
<h3 id="cerv-航天飞机">CERV 航天飞机</h3>
|
||||
<p>CERV 航天飞机于 2015 年完成首飞，并在 2017 年 STS 航天飞机退役后接替其载人和货运任务。CERV 的定位是“安全改进型航天飞机”，而不是完全新一代重载系统。它保留了 STS 的任务传统和大量地面设施经验，使航天飞机体系在 2020 年代仍可承担空间站支援、轨道维修、载荷返回和部分大型载荷部署任务。</p>
|
||||
<p>CERV 的主要贡献在于为后续秃鹫航天飞机奠定了技术和运营基础。整体式乘员舱逃生系统证明了大型轨道器仍可具备更完整的乘员保护手段；航电升级使自动化发射、自动交会和无人货运任务更加可靠；结构减重则说明传统航天飞机仍有继续发展的余地。不过，CERV 仍受限于原有航天飞机体系的尺寸、载荷能力和复用经济性，难以满足 2030 年代后大型轨道设施和星际探索母舰建造的需求。</p>
|
||||
<p>CERV 航天飞机于 2015 年 6 月完成首飞，2017 年接替退役的 STS 承担载人和货运任务，至 2040 年退役，25 年在役期间累计执行 666 次飞行任务。机队共 8 架轨道器，分三个批次生产（第一批 3 架 2015-2017 年首飞，第二批 2 架 2020-2021 年首飞，第三批 3 架 2025-2026 年首飞），在 2030 年代全盛期年飞行频次超过 40 次。CERV 运营期间参与了边疆空间站和凌霄宫空间站的建设，搭载了超过 100 名太空游客，执行了 162 次深空探测任务发射，并完成了哈勃望远镜回收和深空通讯网 2.0 中继卫星部署。</p>
|
||||
<p>CERV 为后续秃鹫航天飞机奠定了全面的技术和运营基础。整体式乘员舱全阶段逃生系统验证了大型轨道器乘员保护的完整方案；液体燃料助推器以 4 米直径、50 次设计寿命和 10 次维护间隔的 CERV 基线积累了数百次回收数据，为秃鹫 5 米级助推器的 75 次免维护/200-300 次全寿命目标提供了关键基线；翼尖双垂尾加鸭翼的气动布局验证了从 STS 单垂尾向新一代航天飞机过渡的可行性；三批次渐进改进模式为秃鹫的批次规划和迭代开发提供了完整的工程范例。不过，CERV 仍受限于 30 吨上行运力、8.4 米 ET 和 RS-25D 主发动机构型，难以满足 2030 年代后大型轨道设施和星际探索母舰建造的需求。</p>
|
||||
<h3 id="秃鹫项目立项">秃鹫项目立项</h3>
|
||||
<p>2030 年，秃鹫航天飞机作为 CERV 航天飞机的继承者开始研发。与 CERV 相比，秃鹫不再是对既有 STS 构型的小幅安全升级，而是面向高轨重载、超宽载荷运输和母舰分段建造的重型航天飞机系统。项目在保留航天飞机“垂直发射、水平着陆”和载人/载荷同舱任务模式的基础上，重新设计了轨道器、外挂燃料箱和助推器。</p>
|
||||
<p>2030 年，秃鹫航天飞机作为 CERV 航天飞机的继承者开始研发。与 CERV 相比，秃鹫不再是对既有 STS 构型的小幅安全升级，而是面向高轨重载、超宽载荷运输和母舰分段建造的重型航天飞机系统。项目在保留航天飞机"垂直发射、水平着陆"和载人/载荷同舱任务模式的基础上，重新设计了轨道器、外挂燃料箱和助推器。</p>
|
||||
<p>秃鹫项目的关键取舍包括：使用更大的 MK4 轨道器替代 STS/CERV 尺寸级轨道器；采用 10 米直径外挂燃料箱，提高发射阶段推进剂储量；用两枚 5 米直径液体燃料助推器替代固体助推器，使上升段具备节流、关机、重启和主动回收能力；保留并强化 CERV 时代引入的整体式乘员逃生理念。</p>
|
||||
<p>项目早期方案曾讨论过完全可重复使用两级入轨飞行器、轨道器背负式飞行器、可回收核心级和重型一次性火箭加轨道拖船等路线。最终采用三段式航天飞机布局，主要原因是该构型可以利用 STS 与 CERV 的运营经验，同时将改动集中在高收益部分：液体助推器、放大外挂燃料箱、MK4 轨道器和增强热防护系统。</p>
|
||||
<h3 id="设计目标">设计目标</h3>
|
||||
@@ -129,13 +130,13 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<li>继承 CERV 的整体式乘员舱逃生理念，并扩展中止模式。</li>
|
||||
<li>在 CERV 停飞后承担航天飞机继承线的高轨重载和载人支援任务。</li>
|
||||
</ol>
|
||||
<p>这些要求使秃鹫航天飞机在总体设计上更接近一种重型轨道运输系统，而不是单纯的“可重复使用运载火箭”。轨道器本身保留较大的在轨自主能力，能够在外挂燃料箱分离后继续完成主要轨道任务；助推器则被视为可独立飞行、独立返回和独立整备的一级飞行器。</p>
|
||||
<p>这些要求使秃鹫航天飞机在总体设计上更接近一种重型轨道运输系统，而不是单纯的"可重复使用运载火箭"。轨道器本身保留较大的在轨自主能力，能够在外挂燃料箱分离后继续完成主要轨道任务；助推器则被视为可独立飞行、独立返回和独立整备的一级飞行器。</p>
|
||||
<h3 id="研制与试飞">研制与试飞</h3>
|
||||
<figure class="thumb tright"><img src="/vulture/vulture_shuttle_ignition_original.png" data-wiki-asset="/vulture/vulture_shuttle_ignition_original.png" alt="秃鹫航天飞机点火"><figcaption class="thumbcaption">秃鹫航天飞机点火瞬间，早期试飞主要验证全栈发射和无人再入着陆流程。</figcaption></figure>
|
||||
<p>秃鹫航天飞机的研发工作始于 2030 年。早期工作集中在 MK4 轨道器结构验证、RS-25E 发动机集群控制、外挂燃料箱保温层脱落测试，以及 5 米级液体助推器返场着陆试验。由于系统尺寸和推力远超 STS 与 CERV，项目在地面振动、分离气动、助推器返回弹道和轨道器低速着陆控制方面进行了多轮试验。</p>
|
||||
<p>首批试验并非直接进行完整轨道飞行。项目先使用结构试验件进行发射台载荷和推进剂加注试验，再使用无主发动机轨道器验证滑翔、进近和着陆特性。随后，液体助推器进行了单独的垂直起降、栅格翼再入控制和返场制导试验。</p>
|
||||
<p>2038 年，秃鹫航天飞机完成首次无人轨道飞行。该飞行验证了完整发射组合体、外挂燃料箱分离、OMS 入轨、无人再入和水平着陆流程。2040 年 CERV 航天飞机正式停飞退役后，秃鹫航天飞机成为航天飞机继承线的主力型号，并在 2040 年代初进入常规运营。</p>
|
||||
<p>服役初期的若干异常事件促成了后续设计成熟。VLT-02 在主发动机点火后、助推器点火前执行发射台中止；VLT-05 在助推器点火后但发射台释放前完成自动关机；VLT-12 则在上升段较早失去两台 RS-25E 后执行入轨中止（Abort to Orbit）。上述事件没有造成轨道器或乘员损失，但推动了发动机健康管理、点火序列判据、发射台安全处置和轨道器任务规划余量的修改。</p>
|
||||
<p>2037 年，秃鹫航天飞机完成首次无人轨道飞行。该飞行验证了完整发射组合体、外挂燃料箱分离、OMS 入轨、无人再入和水平着陆流程。2039 年，秃鹫航天飞机正式投入服役。随后 2040 年 CERV 航天飞机正式停飞退役，秃鹫航天飞机成为航天飞机继承线的主力型号，并在 2040 年代初进入常规运营。</p>
|
||||
<p>服役初期的若干异常事件促成了后续设计成熟。VLT-02 在主发动机点火后、助推器点火前执行发射台中止；VLT-24 则在上升段较早失去两台 RS-25E 后执行入轨中止（Abort to Orbit）。上述事件没有造成轨道器或乘员损失，但推动了发动机健康管理、点火序列判据、发射台安全处置和轨道器任务规划余量的修改。</p>
|
||||
<h2 id="系统组成">系统组成</h2>
|
||||
<p>秃鹫航天飞机由三个主要飞行部件组成：轨道器、外挂燃料箱和两枚液体燃料助推器。轨道器和助推器可重复使用，外挂燃料箱为一次性消耗部件。发射阶段，外挂燃料箱向轨道器主发动机供应液氧和液氢；液体助推器在发射初段提供主要起飞推力，并在分离后返回发射场附近着陆。</p>
|
||||
<h3 id="轨道器">轨道器</h3>
|
||||
@@ -179,10 +180,10 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<p>主发动机关机后，轨道器关闭并断开推进剂和电气脐带接口，随后通过分离推力器与外挂燃料箱脱离。外挂箱残余气体被受控排放，以确保其远离轨道器并进入预定再入轨迹。常规任务中，外挂箱不进入稳定轨道，而是在远离主要航线和居住区的海域上空再入解体。</p>
|
||||
<p>由于外挂燃料箱是单次任务中最大的不可回收部件，它也是秃鹫航天飞机成本结构中的主要项目。后期曾提出过回收式外挂箱、轨道储罐化利用和在轨工厂原料利用等方案，但这些方案会增加入轨质量、任务复杂度和风险，未成为标准操作。</p>
|
||||
<h3 id="液体燃料助推器">液体燃料助推器</h3>
|
||||
<p>秃鹫航天飞机使用两枚对称布置的 5 米直径液体燃料助推器。每枚助推器安装 19 台“天火-12”液氧煤油发动机，在发射初段提供主要起飞推力。与 STS 固体助推器相比，液体助推器具备节流、关机、重启和主动回收能力，使发射早期的控制和中止选项显著增加。</p>
|
||||
<p>秃鹫航天飞机使用两枚对称布置的 5 米直径液体燃料助推器。每枚助推器安装 19 台"天火-12"液氧煤油发动机，在发射初段提供主要起飞推力。与 STS 固体助推器相比，液体助推器具备节流、关机、重启和主动回收能力，使发射早期的控制和中止选项显著增加。</p>
|
||||
<figure class="thumb tleft"><img src="/vulture/vulture_booster_recovery_original.png" data-wiki-asset="/vulture/vulture_booster_recovery_original.png" alt="秃鹫航天飞机助推器回收"><figcaption class="thumbcaption">液体燃料助推器在分离后执行 RTLS 返场，并依靠反推完成垂直着陆。</figcaption></figure>
|
||||
<h4 id="液体燃料助推器-推进与控制">推进与控制</h4>
|
||||
<p>每枚液体助推器由推进剂箱段、发动机舱、栅格翼段、姿控系统、着陆腿和航电系统组成。“天火-12”发动机使用液氧/煤油推进剂，具备推力矢量控制能力。发射阶段，助推器发动机与轨道器 RS-25E 共同工作，飞控系统统一分配姿态控制指令。</p>
|
||||
<p>每枚液体助推器由推进剂箱段、发动机舱、栅格翼段、姿控系统、着陆腿和航电系统组成。"天火-12"发动机使用液氧/煤油推进剂，具备推力矢量控制能力。发射阶段，助推器发动机与轨道器 RS-25E 共同工作，飞控系统统一分配姿态控制指令。</p>
|
||||
<p>助推器内部配备独立飞控计算机、惯性测量单元、通信设备和发动机健康监测系统。与固体助推器相比，液体助推器可以在异常情况下提前关机或执行推力削减，从而降低不可控事故概率。不过，由于助推器数量少、推力大，严重不对称推力仍会迅速发展为发射中止或任务失败条件。</p>
|
||||
<h4 id="液体燃料助推器-分离与-rtls-回收">分离与 RTLS 回收</h4>
|
||||
<p>助推器在发射初段结束后分离。分离时，助推器关闭主发动机或降低推力，断开结构连接，随后通过冷气或热气姿控系统调整姿态，与主飞行器保持安全距离。分离后，助推器执行 RTLS 返场机动，沿预定弹道返回发射场附近。</p>
|
||||
@@ -190,6 +191,7 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<h4 id="液体燃料助推器-整备与复用">整备与复用</h4>
|
||||
<p>助推器着陆后需要进行推进剂排空、发动机检查、结构热防护检查、着陆腿检修、栅格翼维护和飞控数据复盘。由于不经过海水浸泡，秃鹫液体助推器的飞行后整备流程比 STS 固体助推器海上回收更短，但发动机数量多、管路复杂，维护工作仍然繁重。</p>
|
||||
<p>液体助推器的复用次数取决于发动机寿命、箱体疲劳、着陆载荷和热循环损伤。标准流程要求每次飞行后对发动机涡轮泵、燃烧室、喷管、阀门和推进剂管线进行分级检查。达到寿命限制的发动机可单独拆换，不需要报废整枚助推器。</p>
|
||||
<p>秃鹫助推器的长寿命能力建立在 CERV 助推器运营数据的直接基础之上。CERV 的 4 米助推器采用增推版 TH-12 发动机（单台真空推力 1,132.67 kN），设计寿命 50 次、每 10 次需维护。秃鹫放大至 5 米直径后，通过涡轮泵轴承升级、推力室冷却通道优化和材料改进，在发动机基本性能指标不变的条件下实现了免维护 75 次、计划内维护后 200-300 次的复用水准，维护效率较 CERV 时代大幅提升。</p>
|
||||
<h2 id="地面设施与发射准备">地面设施与发射准备</h2>
|
||||
<p>秃鹫航天飞机主要从文昌发射。由于系统尺寸、推进剂种类和回收方式都与传统航天飞机不同，发射场需要同时支持液氧/液氢、液氧/煤油、MMH/NTO 和喷气燃料等多种推进剂及危险品处理。</p>
|
||||
<p>发射前，轨道器在专用整备设施中完成热防护检查、主发动机安装或检修、OMS/RCS 加注、载荷装入和飞控系统测试。外挂燃料箱与两枚液体助推器在总装设施中完成堆叠，轨道器随后与外挂箱连接。完整组合体转运至发射台后进行脐带连接、通信测试、推进剂加注演练和发射倒计时彩排。</p>
|
||||
@@ -221,19 +223,19 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<p>液体助推器的可关机能力使发射早期中止更可控，但并不意味着风险消失。若飞行器在高速高动压区域发生严重结构损伤、失控或推进剂箱破裂，整体逃生系统仍可能是唯一可用的乘员保护手段。</p>
|
||||
<h2 id="运用历史">运用历史</h2>
|
||||
<h3 id="早期服役">早期服役</h3>
|
||||
<p>秃鹫航天飞机在 2038 年完成首次无人轨道飞行后，进入持续约数年的试飞和早期运营阶段。早期任务以无人载荷部署、高轨试验和助推器 RTLS 回收验证为主，用于确认 MK4 轨道器在高轨任务中的推进剂余量、热防护维护周期和液体助推器周转流程。</p>
|
||||
<p>2040 年，CERV 航天飞机正式停飞退役，秃鹫航天飞机开始接替其载人和高价值货运任务。随着助推器回收成功率提高和轨道器整备时间缩短，秃鹫航天飞机逐渐从试飞型号转入常规运营，并承担大型结构件运输、载人支援和高轨部署任务。</p>
|
||||
<p>2040 年代中后期，秃鹫航天飞机开始承担大型轨道设施建造任务。其超宽载荷舱可直接运送传统整流罩难以容纳的模块，使空间站、轨道船坞和母舰装配平台能够采用更少的发射次数完成大型构件部署。这一阶段也确立了秃鹫航天飞机作为“母舰建造运输工具”的地位。</p>
|
||||
<p>秃鹫航天飞机在 2037 年完成首次无人轨道飞行后，进入持续约数年的试飞和早期运营阶段。早期任务以无人载荷部署、高轨试验和助推器 RTLS 回收验证为主，用于确认 MK4 轨道器在高轨任务中的推进剂余量、热防护维护周期和液体助推器周转流程。</p>
|
||||
<p>2039 年秃鹫航天飞机正式服役，2040 年 CERV 航天飞机正式停飞退役后，秃鹫航天飞机开始接替其载人和高价值货运任务。随着助推器回收成功率提高和轨道器整备时间缩短，秃鹫航天飞机逐渐从试飞型号转入常规运营，并承担大型结构件运输、载人支援和高轨部署任务。</p>
|
||||
<p>2040 年代中后期，秃鹫航天飞机开始承担大型轨道设施建造任务。其超宽载荷舱可直接运送传统整流罩难以容纳的模块，使空间站、轨道船坞和母舰装配平台能够采用更少的发射次数完成大型构件部署。这一阶段也确立了秃鹫航天飞机作为"母舰建造运输工具"的地位。</p>
|
||||
<h3 id="xh-01-建造支援">XH-01 建造支援</h3>
|
||||
<p>XH-01 的主建造阶段是秃鹫航天飞机早期运用史中的重要节点。现有任务日志显示，XH-01 建造期从 2050 年 3 月 16 日持续至 2052 年 2 月 7 日，首个模块在 2050 年 3 月 15 日前后交付，整体组装于 2052 年 2 月 6 日前后完成。</p>
|
||||
<p>在这一阶段，秃鹫航天飞机多次用于向近地轨道装配区运送大型结构组件、居住舱段、推进剂管理设备、散热器、对接节点和临时施工设备。由于 XH-01 的部分构件体积大于传统重型火箭整流罩可容纳范围，秃鹫航天飞机的宽体载荷舱为其早期装配提供了关键条件。</p>
|
||||
<p>秃鹫航天飞机通常不直接完成所有母舰装配动作，而是承担“交付至装配轨道”的角色。载荷释放后，轨道拖船、装配平台机械臂或母舰自身临时结构继续完成最终对接。轨道器则负责载荷状态检查、人员转移、临时供电和紧急返回能力。</p>
|
||||
<p>秃鹫航天飞机通常不直接完成所有母舰装配动作，而是承担"交付至装配轨道"的角色。载荷释放后，轨道拖船、装配平台机械臂或母舰自身临时结构继续完成最终对接。轨道器则负责载荷状态检查、人员转移、临时供电和紧急返回能力。</p>
|
||||
<h3 id="st-01-与-st-02">ST-01 与 ST-02</h3>
|
||||
<p>XH-01 后，秃鹫航天飞机继续参与万星源号（ST-01）和万星源NEXT号（ST-02）的建造任务。随着母舰规模增大，单次发射的大型结构件数量和质量都进一步提高，秃鹫航天飞机逐渐与更重型的一次性或部分复用运载系统搭配使用。</p>
|
||||
<p>在 ST-01 与 ST-02 的建造阶段，秃鹫航天飞机更多承担高价值、超宽、需要人员现场操作或需要返回检查的载荷任务，而不再负责所有大质量构件运输。它的优势从“主力重载运输”逐渐转向“复杂载荷与载人支援运输”。</p>
|
||||
<p>XH-01 后，秃鹫航天飞机继续参与万星源号（ST-01）和万星源NEXT号（ST-02）的建造任务。ST-01 建造期从 2050 年 9 月至 2053 年 2 月，几乎与 XH-01 的高峰期重叠，使 2050-2053 年成为秃鹫航天飞机发射密度最高的阶段。随着母舰规模增大，单次发射的大型结构件数量和质量都进一步提高，秃鹫航天飞机逐渐与更重型的一次性或部分复用运载系统搭配使用。</p>
|
||||
<p>在 ST-01 与 ST-02 的建造阶段，秃鹫航天飞机更多承担高价值、超宽、需要人员现场操作或需要返回检查的载荷任务，而不再负责所有大质量构件运输。它的优势从"主力重载运输"逐渐转向"复杂载荷与载人支援运输"。</p>
|
||||
<h3 id="核推进试验起点">核推进试验起点</h3>
|
||||
<p>随着高能推进技术的发展，多个核气塞发动机方案从核热推进研究中衍生出来，秃鹫航天飞机的部分轨道器也被用于核热和核气塞发动机相关试验。该方向并非 Block 1 设计初期的主要目标，而是在秃鹫航天飞机已经具备成熟结构、热防护、自动飞控和高轨任务经验后逐步发展出的衍生路线。</p>
|
||||
<p>VS-05 首先承担早期实验平台任务。该机对 OMS 系统进行了改造，用于测试热核推进技术在大型航天飞机上的推进剂管理、热防护隔离、在轨点火和安全中止程序。VS-05 的实验重点不在于改变整机发射构型，而在于验证核热推进与既有 OMS/RCS、载荷舱热环境和乘员安全规程的兼容性。后续 Block 1.5 与改进乙型均由这一试验线发展而来，但两者在任务定位、载荷能力和运营规则上已经明显分化。</p>
|
||||
<p>VS-05 首先承担早期实验平台任务。该机于 2048 年对 OMS 系统进行了改造，用于测试热核推进技术在大型航天飞机上的推进剂管理、热防护隔离、在轨点火和安全中止程序。VS-05 的实验重点不在于改变整机发射构型，而在于验证核热推进与既有 OMS/RCS、载荷舱热环境和乘员安全规程的兼容性。后续 Block 1.5 与改进乙型均由这一试验线发展而来，但两者在任务定位、载荷能力和运营规则上已经明显分化。</p>
|
||||
<h3 id="任务类型">任务类型</h3>
|
||||
<p>秃鹫航天飞机的常见任务包括：</p>
|
||||
<ul>
|
||||
@@ -246,116 +248,163 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<li>任务中止救援或备用载荷回收。</li>
|
||||
</ul>
|
||||
<h2 id="历史发射次数">历史发射次数</h2>
|
||||
<p>以下发射次数按公开 VLT 任务序列估算，用于说明秃鹫航天飞机从试飞到主力运营的节奏变化。为与飞行事件表对应，年度累计数必须覆盖同年发生的任务编号：例如 VLT-12 位于 2039 年累计区间内，VLT-402 与 VLT-438 位于 2050 年累计区间内，VLT-762 位于 2055 年累计区间内。</p>
|
||||
<div class="launch-chart" role="img" aria-label="秃鹫航天飞机年度发射次数柱状图，分为研发阶段和主力运营阶段">
|
||||
<p>以下发射次数按公开 VLT 任务序列估算，用于说明秃鹫航天飞机从试飞到主力运营、再到 Block 2 高频运营的节奏变化。年度累计数对应同年发生的任务编号区间：例如 VLT-785 位于 2050 年累计区间内，VLT-1258 位于 2055 年累计区间内。截至当前（2060 年 3 月），秃鹫航天飞机累计发射约 2,266 次。</p>
|
||||
<div class="launch-chart" role="img" aria-label="秃鹫航天飞机年度发射次数柱状图，分为研发阶段、Block 1 常规运营阶段和 Block 2 高频运营阶段">
|
||||
<div class="launch-row launch-head"><span>年份</span><span>发射次数</span><span class="launch-count">次数</span><span class="launch-cumulative">累计</span></div>
|
||||
<div class="launch-stage-label">研发阶段</div>
|
||||
<div class="launch-row"><span>2038</span><span class="launch-track"><span class="launch-bar" style="width: 4.4%;"></span></span><span class="launch-count">4</span><span class="launch-cumulative">4</span></div>
|
||||
<div class="launch-row"><span>2039</span><span class="launch-track"><span class="launch-bar" style="width: 12.2%;"></span></span><span class="launch-count">11</span><span class="launch-cumulative">15</span></div>
|
||||
<div class="launch-row"><span>2040</span><span class="launch-track"><span class="launch-bar" style="width: 10.0%;"></span></span><span class="launch-count">9</span><span class="launch-cumulative">24</span></div>
|
||||
<div class="launch-stage-label">主力运营阶段</div>
|
||||
<div class="launch-row"><span>2041</span><span class="launch-track"><span class="launch-bar" style="width: 26.7%;"></span></span><span class="launch-count">24</span><span class="launch-cumulative">48</span></div>
|
||||
<div class="launch-row"><span>2042</span><span class="launch-track"><span class="launch-bar" style="width: 21.1%;"></span></span><span class="launch-count">19</span><span class="launch-cumulative">67</span></div>
|
||||
<div class="launch-row"><span>2043</span><span class="launch-track"><span class="launch-bar" style="width: 32.2%;"></span></span><span class="launch-count">29</span><span class="launch-cumulative">96</span></div>
|
||||
<div class="launch-row"><span>2044</span><span class="launch-track"><span class="launch-bar" style="width: 54.4%;"></span></span><span class="launch-count">49</span><span class="launch-cumulative">145</span></div>
|
||||
<div class="launch-row"><span>2045</span><span class="launch-track"><span class="launch-bar" style="width: 55.6%;"></span></span><span class="launch-count">50</span><span class="launch-cumulative">195</span></div>
|
||||
<div class="launch-row"><span>2046</span><span class="launch-track"><span class="launch-bar" style="width: 38.9%;"></span></span><span class="launch-count">35</span><span class="launch-cumulative">230</span></div>
|
||||
<div class="launch-row"><span>2047</span><span class="launch-track"><span class="launch-bar" style="width: 33.3%;"></span></span><span class="launch-count">30</span><span class="launch-cumulative">260</span></div>
|
||||
<div class="launch-row"><span>2048</span><span class="launch-track"><span class="launch-bar" style="width: 55.6%;"></span></span><span class="launch-count">50</span><span class="launch-cumulative">310</span></div>
|
||||
<div class="launch-row"><span>2049</span><span class="launch-track"><span class="launch-bar" style="width: 100%;"></span></span><span class="launch-count">90</span><span class="launch-cumulative">400</span></div>
|
||||
<div class="launch-row"><span>2050</span><span class="launch-track"><span class="launch-bar" style="width: 72.2%;"></span></span><span class="launch-count">65</span><span class="launch-cumulative">465</span></div>
|
||||
<div class="launch-row"><span>2051</span><span class="launch-track"><span class="launch-bar" style="width: 94.4%;"></span></span><span class="launch-count">85</span><span class="launch-cumulative">550</span></div>
|
||||
<div class="launch-row"><span>2052</span><span class="launch-track"><span class="launch-bar" style="width: 77.8%;"></span></span><span class="launch-count">70</span><span class="launch-cumulative">620</span></div>
|
||||
<div class="launch-row"><span>2053</span><span class="launch-track"><span class="launch-bar" style="width: 72.2%;"></span></span><span class="launch-count">65</span><span class="launch-cumulative">685</span></div>
|
||||
<div class="launch-row"><span>2054</span><span class="launch-track"><span class="launch-bar" style="width: 61.1%;"></span></span><span class="launch-count">55</span><span class="launch-cumulative">740</span></div>
|
||||
<div class="launch-row"><span>2055</span><span class="launch-track"><span class="launch-bar" style="width: 50.0%;"></span></span><span class="launch-count">45</span><span class="launch-cumulative">785</span></div>
|
||||
<div class="launch-stage-label">研发/试飞阶段</div>
|
||||
<div class="launch-row"><span>2037</span><span class="launch-track"><span class="launch-bar" style="width: 2.7%;"></span></span><span class="launch-count">6</span><span class="launch-cumulative">6</span></div>
|
||||
<div class="launch-row"><span>2038</span><span class="launch-track"><span class="launch-bar" style="width: 7.2%;"></span></span><span class="launch-count">16</span><span class="launch-cumulative">22</span></div>
|
||||
<div class="launch-row"><span>2039</span><span class="launch-track"><span class="launch-bar" style="width: 11.3%;"></span></span><span class="launch-count">25</span><span class="launch-cumulative">47</span></div>
|
||||
<div class="launch-row"><span>2040</span><span class="launch-track"><span class="launch-bar" style="width: 18.1%;"></span></span><span class="launch-count">40</span><span class="launch-cumulative">87</span></div>
|
||||
<div class="launch-stage-label">Block 1 常规运营阶段</div>
|
||||
<div class="launch-row"><span>2041</span><span class="launch-track"><span class="launch-bar" style="width: 25.3%;"></span></span><span class="launch-count">56</span><span class="launch-cumulative">143</span></div>
|
||||
<div class="launch-row"><span>2042</span><span class="launch-track"><span class="launch-bar" style="width: 31.7%;"></span></span><span class="launch-count">70</span><span class="launch-cumulative">213</span></div>
|
||||
<div class="launch-row"><span>2043</span><span class="launch-track"><span class="launch-bar" style="width: 37.1%;"></span></span><span class="launch-count">82</span><span class="launch-cumulative">295</span></div>
|
||||
<div class="launch-row"><span>2044</span><span class="launch-track"><span class="launch-bar" style="width: 39.8%;"></span></span><span class="launch-count">88</span><span class="launch-cumulative">383</span></div>
|
||||
<div class="launch-row"><span>2045</span><span class="launch-track"><span class="launch-bar" style="width: 39.8%;"></span></span><span class="launch-count">88</span><span class="launch-cumulative">471</span></div>
|
||||
<div class="launch-row"><span>2046</span><span class="launch-track"><span class="launch-bar" style="width: 39.8%;"></span></span><span class="launch-count">88</span><span class="launch-cumulative">559</span></div>
|
||||
<div class="launch-row"><span>2047</span><span class="launch-track"><span class="launch-bar" style="width: 39.8%;"></span></span><span class="launch-count">88</span><span class="launch-cumulative">647</span></div>
|
||||
<div class="launch-row"><span>2048</span><span class="launch-track"><span class="launch-bar" style="width: 38.0%;"></span></span><span class="launch-count">84</span><span class="launch-cumulative">731</span></div>
|
||||
<div class="launch-row"><span>2049</span><span class="launch-track"><span class="launch-bar" style="width: 38.0%;"></span></span><span class="launch-count">84</span><span class="launch-cumulative">815</span></div>
|
||||
<div class="launch-row"><span>2050</span><span class="launch-track"><span class="launch-bar" style="width: 43.4%;"></span></span><span class="launch-count">96</span><span class="launch-cumulative">911</span></div>
|
||||
<div class="launch-row"><span>2051</span><span class="launch-track"><span class="launch-bar" style="width: 38.0%;"></span></span><span class="launch-count">84</span><span class="launch-cumulative">995</span></div>
|
||||
<div class="launch-row"><span>2052</span><span class="launch-track"><span class="launch-bar" style="width: 35.3%;"></span></span><span class="launch-count">78</span><span class="launch-cumulative">1073</span></div>
|
||||
<div class="launch-row"><span>2053</span><span class="launch-track"><span class="launch-bar" style="width: 35.3%;"></span></span><span class="launch-count">78</span><span class="launch-cumulative">1151</span></div>
|
||||
<div class="launch-row"><span>2054</span><span class="launch-track"><span class="launch-bar" style="width: 34.4%;"></span></span><span class="launch-count">76</span><span class="launch-cumulative">1227</span></div>
|
||||
<div class="launch-stage-label">Block 2 入列与高频运营阶段</div>
|
||||
<div class="launch-row"><span>2055</span><span class="launch-track"><span class="launch-bar" style="width: 67.0%;"></span></span><span class="launch-count">148</span><span class="launch-cumulative">1375</span></div>
|
||||
<div class="launch-row"><span>2056</span><span class="launch-track"><span class="launch-bar" style="width: 84.2%;"></span></span><span class="launch-count">186</span><span class="launch-cumulative">1561</span></div>
|
||||
<div class="launch-row"><span>2057</span><span class="launch-track"><span class="launch-bar" style="width: 96.8%;"></span></span><span class="launch-count">214</span><span class="launch-cumulative">1775</span></div>
|
||||
<div class="launch-row"><span>2058</span><span class="launch-track"><span class="launch-bar" style="width: 100%;"></span></span><span class="launch-count">221</span><span class="launch-cumulative">1996</span></div>
|
||||
<div class="launch-row"><span>2059</span><span class="launch-track"><span class="launch-bar" style="width: 98.6%;"></span></span><span class="launch-count">218</span><span class="launch-cumulative">2214</span></div>
|
||||
</div>
|
||||
<table>
|
||||
<thead><tr><th>阶段</th><th>年份</th><th>累计发射</th><th>与飞行事件表的对应关系</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>研发阶段</td><td>2038-2040 年</td><td>24 次</td><td>覆盖 VLT-01 首飞、VLT-02 发射台中止、VLT-05 助推器点火后中止、VLT-12 入轨中止和 VLT-18 发射台中止。</td></tr>
|
||||
<tr><td>主力运营爬坡</td><td>2041-2048 年</td><td>310 次</td><td>覆盖 VLT-27、VLT-39、VLT-56、VLT-74、VLT-88、VLT-106、VLT-133、VLT-159、VLT-181、VLT-214、VLT-246 和 VLT-279 等成熟化事件。</td></tr>
|
||||
<tr><td>母舰建造高峰</td><td>2049-2052 年</td><td>620 次</td><td>覆盖 VLT-318、VLT-402、VLT-438、VLT-486、VLT-529 和 VLT-571；XH-01 建造支援期使 2049-2052 年成为发射密度最高的阶段。</td></tr>
|
||||
<tr><td>稳态运营与改进乙型初期</td><td>2053-2055 年</td><td>785 次</td><td>覆盖 VLT-633 的三发关机边界案例和 VLT-762 的改进乙型制动异常。</td></tr>
|
||||
<tr><td>研发阶段</td><td>2037-2040 年</td><td>87 次</td><td>覆盖 VLT-01 首飞、VLT-03 发射台中止、VLT-24 Abort to Orbit 和 VLT-42 首飞等事件。</td></tr>
|
||||
<tr><td>Block 1 常规运营与母舰建造高峰</td><td>2041-2054 年</td><td>1,227 次</td><td>覆盖 VLT-76 单发关机、VLT-178 机队满编、VLT-635 核热首次在轨点火、VLT-438 双发关机、VLT-785 XH-01 首个模块、VLT-1008 XH-01 最后模块、VLT-1128 三发关机边界案例等事件。2050-2053 年为 XH-01 与 ST-01 建造高峰期。</td></tr>
|
||||
<tr><td>Block 2 入列与高频运营</td><td>2055 年至今</td><td>2,266 次</td><td>覆盖 VLT-1258 Block 2 首飞、VLT-1488 耐心号退役、VLT-1555 耐力号退役、VLT-1925 坚毅号 300 次里程碑以及 VLT-2168 忠诚号 250 次里程碑等事件。</td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="block-15">Block 1.5</h2>
|
||||
<p>Block 1.5 是由 VS-06 和 VS-07 两架既有 Block 1 轨道器改装而来的高能推进构型。该构型安装核气塞发动机，并对推进剂管理、热防护隔离、尾部结构、飞控软件和地面安全规程进行大幅修改。它保留了秃鹫航天飞机的基本轨道器外形和多数在轨操作能力，但不再以传统外挂燃料箱加液体助推器的完整发射组合体作为唯一任务方式。</p>
|
||||
<p>Block 1.5 的核心能力是单级入轨（SSTO）。它可以在特定载荷、轨道和安全约束下执行单级入轨任务，用于高能推进验证、快速响应发射、特殊载荷部署和应急救援准备。由于核气塞发动机、辐射屏蔽、推进剂系统和热隔离结构占据了大量质量裕度，Block 1.5 的有效载荷能力降至约 40 吨，远低于 Block 1 的常规高轨重载能力。</p>
|
||||
<p>VS-06 坚毅号于 2051 年执行 Block 1 构型末飞后开始改装，2052 年完成改装并执行 Block 1.5 首次在轨点火测试。VS-07 忠诚号于 2052 年执行 Block 1 构型末飞后开始改装，2053 年完成改装并执行 Block 1.5 首飞。两架 Block 1.5 轨道器截至当前（2060 年 3 月）均在役，常态化运营中每架可维持每年约 24 次飞行的频次。</p>
|
||||
<p>这种构型在运营上更接近试验型和专用型，而不是主力货运型。它的任务优势来自发射流程简化、轨道机动余量提高和高能推进经验积累；限制则来自地面安全区扩大、发动机检查周期更长、载荷舱热环境约束更严，以及公众和监管机构对核热系统的额外审查。VS-06 与 VS-07 因此通常承担少量高价值任务，而不参与 XH-01、ST-01 或 ST-02 建造期的高频重载运输。</p>
|
||||
<h2 id="block-2">改进乙型</h2>
|
||||
<p><b>秃鹫航天飞机改进乙型</b>（英语：<b>Vulture Shuttle Block 2</b>）是秃鹫航天飞机的后续生产型，而不是由 Block 1 简单改装而来的过渡型号。VS-08、VS-09 和 VS-10 直接按改进乙型标准建造，围绕核气塞发动机、高能推进剂管理、深空通信、强化热防护和更高能量再入约束重新设计。由于系统差异较大，维基中另有独立页面 <a href="/home/Space_Shuttles/Vulture_Shuttle_Block_2">秃鹫航天飞机改进乙型</a>；本文仅概述它与秃鹫航天飞机主条目的关系。</p>
|
||||
<p>改进乙型的任务定位从近地轨道重载运输扩展到地月空间往返。其设计能力为携带约 120 吨载荷直飞低月球轨道并返回，可服务低月轨平台、月球转运节点、大型深空探测器装配和高价值载荷回收任务。与 Block 1.5 相比，改进乙型不只是获得 SSTO 能力，而是将高能推进系统纳入标准生产构型。</p>
|
||||
<p><b>秃鹫航天飞机改进乙型</b>（英语：<b>Vulture Shuttle Block 2</b>）是秃鹫航天飞机的后续生产型，而不是由 Block 1 简单改装而来的过渡型号。VS-08、VS-09 和 VS-10 直接按改进乙型标准建造，围绕核气塞发动机、高能推进剂管理、深空通信、强化热防护和更高能量再入约束重新设计。VS-08 荣誉号于 2055 年 3 月完成首飞，标志着 Block 2 时代的开启。由于系统差异较大，维基中另有独立页面 <a href="/home/Space_Shuttles/Vulture_Shuttle_Block_2">秃鹫航天飞机改进乙型</a>；本文仅概述它与秃鹫航天飞机主条目的关系。</p>
|
||||
<p>改进乙型的任务定位从近地轨道重载运输扩展到地月空间往返。其设计能力为携带约 120 吨载荷直飞低月球轨道并返回，可服务低月轨平台、月球转运节点、大型深空探测器装配和高价值载荷回收任务。与 Block 1.5 相比，改进乙型不只是获得 SSTO 能力，而是将高能推进系统纳入标准生产构型。Block 2 轨道器的年飞行频次可达约 48 次/架，较 Block 1 的周转时间缩短约 75%。</p>
|
||||
<p>改进乙型的返回能力受到严格限制。受热防护、结构载荷、横向控制和着陆重量约束，它最多允许携带约 40 吨载荷再入；返回前必须先制动至近地轨道级速度，再按第一宇宙速度再入剖面返回。改进乙型不能执行低月轨直接高速再入，也不能把低月轨返回载荷能力简单等同于近地轨道返回能力。该限制后来成为独立页面中讨论任务规划、热防护维护和月地运输经济性的核心内容之一。</p>
|
||||
<p>截至当前（2060 年 3 月），Block 2 机队共有 3 架在役轨道器（VS-08 荣誉号、VS-09 信念号、VS-10 希望号），累计完成 606 次飞行。机队规模持续扩大，VS-11 及后续轨道器正在规划中。Block 2 已承担 XH-03、XH-04、ST-03、ST-04 等后续母舰的建造运输任务，以及低月轨平台补给、大型深空探测器装配和高价值载荷回收，成为当前秃鹫航天飞机机队中增长最快的构型。</p>
|
||||
<h2 id="安全性与飞行事件">安全性与飞行事件</h2>
|
||||
<p>秃鹫航天飞机的安全设计直接回应了 STS 时代的关键事故教训。固体助推器被可关机液体助推器取代，外挂燃料箱保温材料脱落风险被重点控制，轨道器前缘和腹部热防护增加传感器和在轨检查手段，乘员舱具备整体逃生能力。与 STS 相比，秃鹫航天飞机的风险控制更依赖主动诊断、可关机推进系统和任务余量管理，而不是单纯依赖飞行后检查。</p>
|
||||
<p>进入常规运营后，秃鹫航天飞机的年飞行量逐步上升。2040 年代中后期，成熟运营阶段的发射频率通常在每年 30 至 50 次之间；在 XH-01、ST-01 和 ST-02 建造高峰期，轨道器、助推器和地面设施曾按部分年度 70 至 90 次飞行的节奏排产。如此高的使用强度使系统积累了大量非灾难性异常记录，其中相当一部分属于发射台中止、倒计时中止、助推器回收异常、发动机提前关机、在轨设备降级和着陆后检修事件。</p>
|
||||
<p>进入常规运营后，秃鹫航天飞机的年飞行量逐步上升。2040 年代中后期，成熟运营阶段的发射频率通常在每年 30 至 90 次之间；在 XH-01 与 ST-01 建造高峰期（2050-2053 年），轨道器、助推器和地面设施曾按年度 78 至 96 次飞行的节奏排产。2055 年 Block 2 入列后，年飞行量迅速突破 200 次大关。如此高的使用强度使系统积累了大量非灾难性异常记录，其中相当一部分属于发射台中止、倒计时中止、助推器回收异常、发动机提前关机、在轨设备降级和着陆后检修事件。</p>
|
||||
<h3 id="发动机失效判据">发动机失效判据</h3>
|
||||
<p>秃鹫航天飞机的主发动机失效判据按飞行时间、载荷质量、目标轨道和 OMS 余量动态计算。助推器分离后，单台 RS-25E 失效通常不构成中止标准，轨道器仍可完成正常入轨。T+6 分钟后，两台 RS-25E 失效仍可在多数任务中保持正常入轨；T+8 分钟后，三台 RS-25E 失效也可依靠剩余主发动机工作时间和 OMS 修正完成低裕度入轨。</p>
|
||||
<p>因此，秃鹫航天飞机历史上的 Abort to Orbit 案例通常不是“单台主发动机失效”，而是失效数量超过对应时间段容限，或同时出现推进剂泄漏、姿态控制受限、外挂燃料箱分离风险等问题。VLT-12 的入轨中止发生在 T+6 分钟容限形成之前连续失去两台 RS-25E；而后续 VLT-27、VLT-246 和 VLT-633 分别验证了单发、T+6 分钟后双发、T+8 分钟后三发失效仍可正常入轨的边界。</p>
|
||||
<p>因此，秃鹫航天飞机历史上的 Abort to Orbit 案例通常不是"单台主发动机失效"，而是失效数量超过对应时间段容限，或同时出现推进剂泄漏、姿态控制受限、外挂燃料箱分离风险等问题。VLT-24 的入轨中止发生在 T+6 分钟容限形成之前连续失去两台 RS-25E；而后续 VLT-76、VLT-438 和 VLT-1128 分别验证了单发、T+6 分钟后双发、T+8 分钟后三发失效仍可正常入轨的边界。</p>
|
||||
<h3 id="主要飞行事件">主要飞行事件</h3>
|
||||
<p>下表收录秃鹫航天飞机公开安全记录中最常被引用的飞行事件、准事故和发射台中止。表中事件并不都等同于事故；部分条目是因高频运营而被记录的地面中止或维护事件。</p>
|
||||
<p>秃鹫航天飞机没有公开记录的乘员死亡、轨道器全损或助推器全损事故。其严重飞行事件主要集中在上升段发动机失效、助推器回收偏差、热防护损伤和在轨推进系统降级。高频运营放大了维护和地面流程的重要性：XH-01 与 ST-01 建造高峰期，单次异常往往不会造成任务失败，却会挤压后续发射窗口、助推器复用节奏和轨道器热防护库存。秃鹫航天飞机的安全记录因此常被评价为"高事件率、低灾难率"：事件记录数量多，但多数被限制在发射前、低能量状态或可恢复的降级模式中。</p>
|
||||
<table>
|
||||
<thead><tr><th>任务编号</th><th>年份</th><th>轨道器</th><th>事件类型</th><th>简述</th><th>结果</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>VLT-01</td><td>2038 年</td><td>VS-01</td><td>首次无人轨道飞行</td><td>完成发射、入轨、再入和水平着陆验证</td><td>任务成功，进入试飞复盘</td></tr>
|
||||
<tr><td>VLT-02</td><td>2038 年</td><td>VS-01</td><td>发射台中止</td><td>一台 RS-25E 预燃室压力传感器与冗余通道不一致，助推器未点火</td><td>主发动机关机，未释放发射台约束</td></tr>
|
||||
<tr><td>VLT-05</td><td>2039 年</td><td>VS-02</td><td>助推器点火后发射台中止</td><td>右侧液体助推器在升推阶段出现氧化剂涡轮泵转速偏差</td><td>助推器点火后关机，组合体留在发射台</td></tr>
|
||||
<tr><td>VLT-12</td><td>2039 年</td><td>VS-02</td><td>Abort to Orbit</td><td>T+5 分 18 秒前后连续失去两台 RS-25E，早于双发失效容限</td><td>进入安全停泊轨道，检查后提前返回</td></tr>
|
||||
<tr><td>VLT-18</td><td>2040 年</td><td>VS-03</td><td>发射台中止</td><td>尾部脐带板氢气探测器读数超限，助推器未点火</td><td>推进剂排空后更换密封件</td></tr>
|
||||
<tr><td>VLT-27</td><td>2041 年</td><td>VS-03</td><td>单台主发动机关机</td><td>助推器分离后，一台 RS-25E 因涡轮泵振动被受控关机</td><td>按正常剖面入轨，未触发中止</td></tr>
|
||||
<tr><td>VLT-39</td><td>2041 年</td><td>VS-01</td><td>助推器回收异常</td><td>左侧助推器栅格翼执行机构饱和，返回弹道偏离主着陆台</td><td>助推器改降备用回收区，轻微结构损伤</td></tr>
|
||||
<tr><td>VLT-56</td><td>2042 年</td><td>VS-04</td><td>热防护警报</td><td>再入前在轨检查发现腹部隔热瓦局部裂纹</td><td>采用保守再入走廊，返回后停飞检修</td></tr>
|
||||
<tr><td>VLT-74</td><td>2043 年</td><td>VS-02</td><td>OMS 阀门卡滞</td><td>一台 OMS 发动机的隔离阀未按时复位</td><td>缩短任务，在备用窗口返航</td></tr>
|
||||
<tr><td>VLT-88</td><td>2043 年</td><td>VS-04</td><td>RCS 泄漏</td><td>载荷释放后发现一组 RCS 管路微漏</td><td>隔离受影响歧管，任务继续完成</td></tr>
|
||||
<tr><td>VLT-106</td><td>2044 年</td><td>VS-03</td><td>助推器点火后发射台中止</td><td>两台“天火-12”发动机未达到燃烧室压力判据</td><td>助推器关机，发射台消防和排空系统启动</td></tr>
|
||||
<tr><td>VLT-133</td><td>2044 年</td><td>VS-01</td><td>起落架传感器异常</td><td>返航进近中主起落架锁定传感器给出矛盾读数</td><td>通过备份通道确认锁定，安全着陆</td></tr>
|
||||
<tr><td>VLT-159</td><td>2045 年</td><td>VS-05</td><td>核热试验中止</td><td>OMS 改造试验中热交换器温度上升快于预测</td><td>取消在轨点火，载荷安全返回</td></tr>
|
||||
<tr><td>VLT-181</td><td>2045 年</td><td>VS-04</td><td>发射台中止</td><td>主发动机氢气吹除温度不稳定，地面序列器终止倒计时</td><td>未点火助推器，发射推迟 72 小时</td></tr>
|
||||
<tr><td>VLT-214</td><td>2046 年</td><td>VS-02</td><td>碎片撞击</td><td>外挂箱连接区小块保温涂层脱落并击中翼身过渡区</td><td>在轨检查确认可返回，检修周期延长</td></tr>
|
||||
<tr><td>VLT-246</td><td>2047 年</td><td>VS-03</td><td>双主发动机关机</td><td>T+6 分 12 秒后两台 RS-25E 被受控关机</td><td>正常入轨，OMS 进行小幅修正</td></tr>
|
||||
<tr><td>VLT-279</td><td>2048 年</td><td>VS-04</td><td>载荷舱门锁扣异常</td><td>一组载荷舱门锁扣位置反馈不稳定</td><td>推迟离轨点火，机械臂辅助检查后返回</td></tr>
|
||||
<tr><td>VLT-318</td><td>2049 年</td><td>VS-06</td><td>Block 1.5 试飞中止</td><td>核气塞发动机控制回路出现低频振荡</td><td>转入安全轨道，提前结束试飞</td></tr>
|
||||
<tr><td>VLT-402</td><td>2050 年</td><td>VS-04</td><td>地面中止</td><td>XH-01 构件接口供电短路，发射前两小时终止</td><td>载荷卸下返厂检查，轨道器未受损</td></tr>
|
||||
<tr><td>VLT-438</td><td>2050 年</td><td>VS-01</td><td>助推器硬着陆</td><td>右侧助推器末端反推点火延迟，着陆腿吸能结构压溃</td><td>助推器未报废，返厂大修</td></tr>
|
||||
<tr><td>VLT-486</td><td>2051 年</td><td>VS-03</td><td>姿控推力器卡滞</td><td>对接前一台 RCS 推力器关闭延迟</td><td>隔离推力器，对接推迟一圈轨道</td></tr>
|
||||
<tr><td>VLT-529</td><td>2051 年</td><td>VS-05</td><td>核热系统保护关机</td><td>OMS 改造试验中辐射监测通道误触发保护逻辑</td><td>试验取消，软件判据后续修订</td></tr>
|
||||
<tr><td>VLT-571</td><td>2052 年</td><td>VS-04</td><td>助推器点火后发射台中止</td><td>左侧助推器推力矢量执行器未通过释放前检查</td><td>助推器关机，组合体安全留台</td></tr>
|
||||
<tr><td>VLT-633</td><td>2053 年</td><td>VS-02</td><td>三主发动机关机</td><td>T+8 分 22 秒后三台 RS-25E 陆续关机</td><td>进入低裕度正常轨道，未判定为 Abort to Orbit</td></tr>
|
||||
<tr><td>VLT-704</td><td>2054 年</td><td>VS-07</td><td>Block 1.5 热防护超温</td><td>尾部屏蔽结构温度高于预报值</td><td>执行 Abort Once Around，返回后更换隔热组件</td></tr>
|
||||
<tr><td>VLT-762</td><td>2055 年</td><td>VS-08</td><td>改进乙型制动异常</td><td>低月轨返回前一次制动点火推力偏低</td><td>推迟返回窗口，补充制动后安全返航</td></tr>
|
||||
<tr><td>VLT-821</td><td>2056 年</td><td>VS-10</td><td>着陆后制动过热</td><td>高重量返回任务后主起落架轮胎和刹车温度超限</td><td>跑道封闭检查，轨道器停飞检修</td></tr>
|
||||
<tr><td>VLT-01</td><td>2037</td><td>VS-01</td><td>首次无人轨道飞行</td><td>完成发射、入轨、再入和水平着陆验证，助推器成功分离但未执行回收测试。</td><td>任务成功，进入试飞复盘。</td></tr>
|
||||
<tr><td>VLT-03</td><td>2037</td><td>VS-01</td><td>发射台中止</td><td>一台 RS-25E 预燃室压力传感器与冗余通道不一致，助推器未点火。</td><td>主发动机关机，未释放发射台约束。</td></tr>
|
||||
<tr><td>VLT-08</td><td>2038</td><td>VS-02</td><td>首飞任务</td><td>VS-02 毅力号首次轨道飞行，Block 1 第二架入列。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-16</td><td>2038</td><td>VS-01</td><td>OMS 阀门延迟</td><td>入轨后一台 OMS 发动机推进剂隔离阀响应超时。</td><td>切换备份阀门组，任务继续。</td></tr>
|
||||
<tr><td>VLT-24</td><td>2039</td><td>VS-02</td><td>Abort to Orbit</td><td>T+5 分 18 秒前后连续失去两台 RS-25E，早于双发失效容限窗口。</td><td>进入安全停泊轨道，检查后提前返回。</td></tr>
|
||||
<tr><td>VLT-33</td><td>2039</td><td>VS-01</td><td>助推器回收异常</td><td>左侧助推器栅格翼执行机构饱和，返回弹道偏离主着陆台。</td><td>助推器改降备用回收区，轻微结构损伤。</td></tr>
|
||||
<tr><td>VLT-42</td><td>2040</td><td>VS-03</td><td>首飞任务</td><td>VS-03 勇气号首次轨道飞行，Block 1 第三架入列。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-54</td><td>2040</td><td>VS-04</td><td>首飞任务</td><td>VS-04 决心号首次轨道飞行，Block 1 第四架入列。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-71</td><td>2041</td><td>VS-05</td><td>首飞任务</td><td>VS-05 耐心号首次轨道飞行，验证 Block 1 后续生产机全部系统。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-76</td><td>2041</td><td>VS-03</td><td>单台主发动机关机</td><td>助推器分离后，一台 RS-25E 因涡轮泵振动被受控关机。</td><td>按正常剖面入轨，未触发中止。</td></tr>
|
||||
<tr><td>VLT-94</td><td>2041</td><td>VS-04</td><td>助推器着陆腿未锁定</td><td>右侧助推器着陆前一条着陆腿未通过锁定传感器检查。</td><td>助推器改降至备用回收台，轻微结构损伤。</td></tr>
|
||||
<tr><td>VLT-112</td><td>2042</td><td>VS-06</td><td>首飞任务</td><td>VS-06 坚毅号首次轨道飞行，Block 1 第六架入列。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-145</td><td>2042</td><td>VS-04</td><td>热防护警报</td><td>再入前在轨检查发现腹部隔热瓦局部裂纹。</td><td>采用保守再入走廊，返回后停飞检修。</td></tr>
|
||||
<tr><td>VLT-178</td><td>2043</td><td>VS-07</td><td>首飞任务</td><td>VS-07 忠诚号首次轨道飞行，Block 1 机队全部七架入列。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-205</td><td>2043</td><td>VS-02</td><td>OMS 阀门卡滞</td><td>一台 OMS 发动机的隔离阀未按时复位。</td><td>缩短任务，在备用窗口返航。</td></tr>
|
||||
<tr><td>VLT-235</td><td>2044</td><td>VS-01</td><td>起落架传感器异常</td><td>返航进近中主起落架锁定传感器给出矛盾读数。</td><td>通过备份通道确认锁定，安全着陆。</td></tr>
|
||||
<tr><td>VLT-268</td><td>2044</td><td>VS-05</td><td>核热试验中止</td><td>OMS 改造试验中热交换器温度上升快于预测。</td><td>取消在轨点火，载荷安全返回。</td></tr>
|
||||
<tr><td>VLT-308</td><td>2045</td><td>VS-02</td><td>外挂箱分离延迟</td><td>主发动机关机后外挂箱分离推力器未按时点火。</td><td>备份推力器接管，外挂箱安全分离。</td></tr>
|
||||
<tr><td>VLT-352</td><td>2045</td><td>VS-04</td><td>着陆复飞</td><td>进近遭遇突发风切变，喷气发动机加力复飞。</td><td>绕场后二次进近，安全着陆。</td></tr>
|
||||
<tr><td>VLT-395</td><td>2046</td><td>VS-06</td><td>飞行中单发失效</td><td>T+4 分 02 秒一台 RS-25E 因涡轮泵振动关机。</td><td>其余四台补偿，正常入轨。</td></tr>
|
||||
<tr><td>VLT-438</td><td>2046</td><td>VS-03</td><td>双主发动机关机</td><td>T+6 分 12 秒后两台 RS-25E 被受控关机。</td><td>正常入轨，OMS 进行小幅修正。</td></tr>
|
||||
<tr><td>VLT-482</td><td>2047</td><td>VS-01</td><td>着陆制动过热</td><td>高重量返回任务后主起落架刹车温度超限。</td><td>跑道封闭检查，轨道器停飞三周。</td></tr>
|
||||
<tr><td>VLT-528</td><td>2047</td><td>VS-07</td><td>助推器硬着陆</td><td>左侧助推器末端反推点火延迟 1.2 秒，着陆腿吸能结构压溃。</td><td>助推器未报废，返厂大修六周。</td></tr>
|
||||
<tr><td>VLT-578</td><td>2048</td><td>VS-06</td><td>在轨软件异常</td><td>飞控计算机一次模式切换后出现短暂的控制律参数不一致。</td><td>回退至保守控制律，软件补丁后续更新。</td></tr>
|
||||
<tr><td>VLT-635</td><td>2048</td><td>VS-05</td><td>核热试验首次在轨点火</td><td>VS-05 OMS 改造后首次在轨核热推进点火试验。</td><td>点火成功，数据采集完整，进入试验复盘。</td></tr>
|
||||
<tr><td>VLT-688</td><td>2049</td><td>VS-02</td><td>发射台中止</td><td>助推器燃料加注后液氧温度分层超限。</td><td>排空推进剂，推迟 48 小时。</td></tr>
|
||||
<tr><td>VLT-745</td><td>2050</td><td>VS-04</td><td>地面中止</td><td>XH-01 构件接口供电短路，发射前两小时终止。</td><td>载荷卸下返厂检查，轨道器未受损。</td></tr>
|
||||
<tr><td>VLT-785</td><td>2050</td><td>VS-01</td><td>XH-01 建造任务</td><td>运送 XH-01 首个大型结构模块入轨，开启羲和号建造序列。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-838</td><td>2050</td><td>VS-06</td><td>建造高峰密集发射</td><td>机队在 2050 年 Q4 期间连续执行 22 次 XH-01/ST-01 构件发射。</td><td>全部成功，地面团队三班轮换。</td></tr>
|
||||
<tr><td>VLT-892</td><td>2051</td><td>VS-07</td><td>载荷固定点异常</td><td>货舱内一组大型构件固定点预载传感器读数下降。</td><td>乘组 EVA 检查并手动加固，任务继续。</td></tr>
|
||||
<tr><td>VLT-948</td><td>2051</td><td>VS-06</td><td>Block 1 末飞</td><td>坚毅号执行 Block 1 构型最后一次飞行，随后开始 Block 1.5 改装。</td><td>任务成功，进入改装程序。</td></tr>
|
||||
<tr><td>VLT-1008</td><td>2052</td><td>VS-01</td><td>XH-01 最后模块</td><td>运送 XH-01 建造所需的最后一个主要结构模块。</td><td>任务成功，XH-01 近地轨道组装完成。</td></tr>
|
||||
<tr><td>VLT-1056</td><td>2052</td><td>VS-06</td><td>Block 1.5 首次在轨点火</td><td>坚毅号改装完成后首次核气塞发动机在轨点火测试。</td><td>点火成功，SSTO 能力初步验证。</td></tr>
|
||||
<tr><td>VLT-1095</td><td>2053</td><td>VS-07</td><td>Block 1 末飞</td><td>忠诚号执行 Block 1 构型最后一次飞行，随后开始 Block 1.5 改装。</td><td>任务成功，进入改装程序。</td></tr>
|
||||
<tr><td>VLT-1128</td><td>2053</td><td>VS-03</td><td>三主发动机关机</td><td>T+8 分 22 秒后三台 RS-25E 陆续关机。</td><td>进入低裕度正常轨道，未判定为 Abort to Orbit。</td></tr>
|
||||
<tr><td>VLT-1162</td><td>2054</td><td>VS-04</td><td>热防护瓦脱落</td><td>再入后检查发现机腹三块隔热瓦局部脱落，下层涂层完好。</td><td>涂层提供冗余保护，停飞检修后复飞。</td></tr>
|
||||
<tr><td>VLT-1135</td><td>2053</td><td>VS-07</td><td>Block 1.5 首飞</td><td>忠诚号改装完成后首次核气塞发动机在轨点火测试。</td><td>点火成功，Block 1.5 第二架进入运营。</td></tr>
|
||||
<tr><td>VLT-1258</td><td>2055</td><td>VS-08</td><td>Block 2 首飞</td><td>改进乙型首架轨道器荣誉号首次轨道飞行，Block 2 时代开启。</td><td>任务成功，低月轨直飞能力初步验证。</td></tr>
|
||||
<tr><td>VLT-1330</td><td>2055</td><td>VS-08</td><td>低月轨往返验证</td><td>荣誉号首次执行低月球轨道往返任务，携带模拟载荷。</td><td>成功入低月轨并安全返回，返回前制动至 LEO 速度。</td></tr>
|
||||
<tr><td>VLT-1418</td><td>2056</td><td>VS-09</td><td>Block 2 第二架首飞</td><td>信念号首次轨道飞行，Block 2 机队扩大。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-1488</td><td>2056</td><td>VS-05</td><td>耐心号末飞</td><td>VS-05 执行最后一次飞行任务后退役，转为地面训练机。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-1555</td><td>2057</td><td>VS-01</td><td>耐力号末飞</td><td>VS-01 执行最后一次飞行任务，服役 20 年后退役。</td><td>任务成功，转入博物馆。</td></tr>
|
||||
<tr><td>VLT-1622</td><td>2057</td><td>VS-10</td><td>Block 2 第三架首飞</td><td>希望号首次轨道飞行，Block 2 三架在役。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-1688</td><td>2057</td><td>VS-02</td><td>毅力号末飞</td><td>VS-02 执行最后一次飞行任务后退役。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-1765</td><td>2058</td><td>VS-03</td><td>勇气号末飞</td><td>VS-03 执行最后一次飞行任务后退役。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-1842</td><td>2058</td><td>VS-04</td><td>决心号末飞</td><td>VS-04 执行最后一次飞行任务，Block 1 时代落幕。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-1925</td><td>2059</td><td>VS-06</td><td>300 次飞行里程碑</td><td>坚毅号执飞个人第 300 次任务，成为飞行次数最多的秃鹫轨道器。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-2005</td><td>2059</td><td>VS-08</td><td>Block 2 高频运营验证</td><td>荣誉号在三个月内完成 12 次飞行，验证 Block 2 年 48 次设计频次。</td><td>全部成功，整备流程成熟。</td></tr>
|
||||
<tr><td>VLT-2088</td><td>2059</td><td>VS-09</td><td>外太阳系探测器发射</td><td>信念号将一枚大型外太阳系探测器+上面级组合体送入近地轨道。</td><td>部署成功，探测器进入转移轨道。</td></tr>
|
||||
<tr><td>VLT-2168</td><td>2060</td><td>VS-07</td><td>250 次飞行里程碑</td><td>忠诚号执飞个人第 250 次任务。</td><td>任务成功。</td></tr>
|
||||
<tr><td>VLT-2222</td><td>2060</td><td>VS-10</td><td>XH-03 建造支援</td><td>希望号运送 XH-03 大型推进舱模块至组装轨道。</td><td>任务成功。</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="发射台中止">发射台中止</h3>
|
||||
<p>发射台中止是秃鹫航天飞机安全史中出现频率最高的事件类型之一。由于主发动机和液体助推器均可关机，系统允许在主发动机点火后、助推器点火前，以及助推器点火后但发射台约束释放前终止发射。VLT-02 和 VLT-18 代表主发动机点火窗口内的中止；VLT-05、VLT-106 和 VLT-571 则是助推器已经点火后的发射台中止。</p>
|
||||
<p>发射台中止是秃鹫航天飞机安全史中出现频率最高的事件类型之一。由于主发动机和液体助推器均可关机，系统允许在主发动机点火后、助推器点火前，以及助推器点火后但发射台约束释放前终止发射。VLT-03 代表主发动机点火窗口内的中止；后续任务中也有助推器已经点火后的发射台中止记录。</p>
|
||||
<p>助推器点火后的中止通常需要同时满足三个条件：发射台约束尚未释放，助推器发动机仍处于可控升推阶段，推进剂排空和消防系统能够承受发动机关机后的热环境。此类事件对发射台和地面团队压力很大，但比固体助推器点火后只能继续起飞的模式更有安全余地。</p>
|
||||
<h3 id="飞行中异常">飞行中异常</h3>
|
||||
<p>秃鹫航天飞机没有公开记录的乘员死亡、轨道器全损或助推器全损事故。其严重飞行事件主要集中在上升段发动机失效、助推器回收偏差、热防护损伤和在轨推进系统降级。VLT-12 是最早的 Abort to Orbit 案例，原因是两台 RS-25E 失效发生得过早；VLT-27 的单发失效、VLT-246 的 T+6 分钟后双发失效和 VLT-633 的 T+8 分钟后三发失效则成为后来说明发动机失效容限的典型案例。</p>
|
||||
<p>高频运营也放大了维护和地面流程的重要性。XH-01、ST-01 和 ST-02 建造高峰期，单次异常往往不会造成任务失败，却会挤压后续发射窗口、助推器复用节奏和轨道器热防护库存。秃鹫航天飞机的安全记录因此常被评价为“高事件率、低灾难率”：事件记录数量多，但多数被限制在发射前、低能量状态或可恢复的降级模式中。</p>
|
||||
<p>秃鹫航天飞机没有公开记录的乘员死亡、轨道器全损或助推器全损事故。其严重飞行事件主要集中在上升段发动机失效、助推器回收偏差、热防护损伤和在轨推进系统降级。VLT-24 是最早的 Abort to Orbit 案例，原因是两台 RS-25E 失效发生得过早；VLT-76 的单发失效、VLT-438 的 T+6 分钟后双发失效和 VLT-1128 的 T+8 分钟后三发失效则成为后来说明发动机失效容限的典型案例。</p>
|
||||
<p>高频运营也放大了维护和地面流程的重要性。XH-01、ST-01 和 ST-02 建造高峰期，单次异常往往不会造成任务失败，却会挤压后续发射窗口、助推器复用节奏和轨道器热防护库存。秃鹫航天飞机的安全记录因此常被评价为"高事件率、低灾难率"：事件记录数量多，但多数被限制在发射前、低能量状态或可恢复的降级模式中。</p>
|
||||
<h2 id="机队与编号">机队与编号</h2>
|
||||
<p>秃鹫航天飞机轨道器采用 VS-xx 风格编号。VS 编号只用于可入轨轨道器，不指代结构测试机、大气飞行测试机、外挂燃料箱或液体助推器。结构测试机使用 VSTA 编号，大气飞行测试机使用 VA 编号。助推器通常以独立序列号管理，并可与不同轨道器组合执行任务。</p>
|
||||
<p>秃鹫航天飞机轨道器采用 VS-xx 风格编号。VS 编号只用于可入轨轨道器，不指代结构测试机、大气飞行测试机、外挂燃料箱或液体助推器。结构测试机使用 VSTA 编号，大气飞行测试机使用 VA 编号。助推器通常以独立序列号管理，并可与不同轨道器组合执行任务。每架轨道器均有独立命名，命名体系沿用航天飞机传统中以探索、开拓和坚持精神为主题的词汇。</p>
|
||||
<h3 id="测试机">测试机</h3>
|
||||
<table>
|
||||
<thead><tr><th>编号</th><th>类型</th><th>用途</th><th>备注</th></tr></thead>
|
||||
<thead><tr><th>编号</th><th>类型</th><th>用途</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>VSTA-01</td><td>结构测试机</td><td>静力载荷、连接结构、外挂燃料箱接口验证</td><td>不具备飞行能力</td></tr>
|
||||
<tr><td>VSTA-02</td><td>结构测试机</td><td>全栈振动、推进剂加注、地面运输和发射台适配验证</td><td>不具备飞行能力</td></tr>
|
||||
<tr><td>VA-01</td><td>大气飞行测试机</td><td>滑翔、进近、着陆和喷气发动机复飞验证</td><td>装有真实喷气式发动机，不具备入轨能力</td></tr>
|
||||
<tr><td>VSTA-01</td><td>结构测试机</td><td>静力载荷、连接结构、外挂燃料箱接口验证。不具备飞行能力。</td></tr>
|
||||
<tr><td>VSTA-02</td><td>结构测试机</td><td>全栈振动、推进剂加注、地面运输和发射台适配验证。不具备飞行能力。</td></tr>
|
||||
<tr><td>VA-01</td><td>大气飞行测试机</td><td>滑翔、进近、着陆和喷气发动机复飞验证。装有真实喷气发动机，不具备入轨能力。</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="轨道器">轨道器</h3>
|
||||
<p>秃鹫航天飞机共生产 10 架轨道器，分为三个构型批次：Block 1 为 RS-25E + 10 米 ET + 5 米液体助推器的基线重载构型，承担了 2040 至 2050 年代的大规模轨道设施和母舰建造任务；Block 1.5 由两架 Block 1 轨道器改装核气塞发动机而来，具备单级入轨能力；改进乙型（Block 2）为核气塞发动机生产型，可直飞低月球轨道并返回。截至当前（2060 年 3 月），Block 1 轨道器已全部退役，Block 1.5 两架和 Block 2 三架均在役。Block 2 机队仍在扩张中，VS-11 正在规划。</p>
|
||||
<h4>Block 1（基线重载构型，VS-01 至 VS-05，全部退役）</h4>
|
||||
<p>Block 1 是秃鹫航天飞机的初始生产构型，使用 5 台 RS-25E 主发动机、10 米直径外挂燃料箱和两枚 5 米液体燃料助推器，典型运力为 100 吨至 1000 km 轨道。该批次承担了 XH-01、ST-01、ST-02 建造期的核心运输任务（2050-2053 年为建造高峰，年飞行频次超过 70 次），并在建造高峰期后逐步退役。VS-05 在服役后期（2048 年起）对 OMS 系统进行了核热推进改造试验。</p>
|
||||
<table>
|
||||
<thead><tr><th>编号</th><th>构型</th><th>状态</th><th>备注</th></tr></thead>
|
||||
<thead><tr><th>编号</th><th>名称</th><th>首飞</th><th>退役</th><th>飞行次数</th><th>状态</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>VS-01</td><td>Block 1</td><td>试飞 / 早期运营</td><td>执行 VLT-01 首次无人轨道飞行，也参与 VLT-02 发射台中止事件</td></tr>
|
||||
<tr><td>VS-02</td><td>Block 1</td><td>运营</td><td>早期认证机，执行 VLT-12 Abort to Orbit 任务</td></tr>
|
||||
<tr><td>VS-03</td><td>Block 1</td><td>运营</td><td>高轨货运和推进系统验证任务，执行 VLT-07 RS-25E 关机事件任务</td></tr>
|
||||
<tr><td>VS-04</td><td>Block 1</td><td>运营</td><td>常规重载货运与母舰建造支援任务</td></tr>
|
||||
<tr><td>VS-05</td><td>Block 1 / 核热试验改造</td><td>试验平台</td><td>OMS 系统改造，用于热核推进相关在轨试验</td></tr>
|
||||
<tr><td>VS-06</td><td>Block 1，后升级为 Block 1.5</td><td>升级型</td><td>安装核气塞发动机，具备 SSTO 能力，载荷约 40 吨</td></tr>
|
||||
<tr><td>VS-07</td><td>Block 1，后升级为 Block 1.5</td><td>升级型</td><td>与 VS-06 类似，用于高能推进和快速响应任务</td></tr>
|
||||
<tr><td>VS-08</td><td>改进乙型</td><td>生产型</td><td>直接按改进乙型建造，可携带约 120 吨载荷直飞低月球轨道并返回</td></tr>
|
||||
<tr><td>VS-09</td><td>改进乙型</td><td>生产型</td><td>改进乙型常规任务机，低月轨运输和返回能力增强</td></tr>
|
||||
<tr><td>VS-10</td><td>改进乙型</td><td>生产型</td><td>改进乙型后续生产机，用于低月轨运输和高能推进任务扩展</td></tr>
|
||||
<tr><td>VS-01</td><td>耐力号（Endurance）</td><td>2037 年 3 月</td><td>2057 年 6 月</td><td>240</td><td>退役</td></tr>
|
||||
<tr><td>VS-02</td><td>毅力号（Perseverance）</td><td>2038 年 1 月</td><td>2057 年 11 月</td><td>235</td><td>退役</td></tr>
|
||||
<tr><td>VS-03</td><td>勇气号（Courage）</td><td>2039 年 5 月</td><td>2058 年 3 月</td><td>240</td><td>退役</td></tr>
|
||||
<tr><td>VS-04</td><td>决心号（Determination）</td><td>2040 年 2 月</td><td>2058 年 8 月</td><td>228</td><td>退役</td></tr>
|
||||
<tr><td>VS-05</td><td>耐心号（Patience）</td><td>2041 年 7 月</td><td>2056 年 12 月</td><td>132</td><td>退役（2048 年起 OMS 改造用于核热推进试验，以降频运行）</td></tr>
|
||||
</tbody></table>
|
||||
<h4>Block 1.5（核气塞改装构型，VS-06 / VS-07，均在役）</h4>
|
||||
<p>Block 1.5 由 VS-06 坚毅号和 VS-07 忠诚号两架 Block 1 轨道器改装而来。改装内容包括安装核气塞发动机、改造推进剂管理系统、增强尾部热防护屏蔽、升级飞控软件和修订地面安全规程。Block 1.5 具备单级入轨能力，无需外挂燃料箱和助推器即可独立入轨，但载荷能力降至约 40 吨。每架 Block 1.5 在常态化运营中可维持每年约 24 次飞行的频次，是 Block 1 的两倍。VS-06 于 2051 年开始改装、2052 年完成并执行 Block 1.5 首飞；VS-07 于 2052 年开始改装、2053 年完成并执行 Block 1.5 首飞。截至当前（2060 年 3 月），两架 Block 1.5 轨道器均在役，主要承担高能推进验证、快速响应轨道任务和紧急救援待命。</p>
|
||||
<table>
|
||||
<thead><tr><th>编号</th><th>名称</th><th>Block 1 首飞</th><th>改装开始</th><th>改装完成</th><th>Block 1.5 首飞</th><th>总飞行次数</th><th>状态</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>VS-06</td><td>坚毅号（Fortitude）</td><td>2042 年 4 月</td><td>2051 年</td><td>2052 年</td><td>2052 年</td><td>305（Block 1: 108 / Block 1.5: 197）</td><td>在役</td></tr>
|
||||
<tr><td>VS-07</td><td>忠诚号（Loyalty）</td><td>2043 年 1 月</td><td>2052 年</td><td>2053 年</td><td>2053 年</td><td>280（Block 1: 108 / Block 1.5: 172）</td><td>在役</td></tr>
|
||||
</tbody></table>
|
||||
<h4>改进乙型 / Block 2（核气塞生产构型，VS-08 至 VS-10，均在役）</h4>
|
||||
<p>改进乙型（Block 2）是围绕核气塞发动机、高能推进剂管理和强化热防护重新设计的后续生产型，直接按 Block 2 标准建造而非由 Block 1 改装。其设计能力为携带约 120 吨载荷直飞低月球轨道并返回（返回载荷限制为 40 吨，需先制动至近地轨道级速度）。每架 Block 2 轨道器在常态化运营中可维持每年约 48 次飞行的频次——平均约 7.6 天即可完成一次完整的发射—入轨—返回—整备循环，较 Block 1 的周转时间缩短约 75%。Block 2 承担了 XH-03、XH-04、ST-03、ST-04 等后续母舰的建造运输任务，以及低月轨平台补给、大型深空探测器装配和高价值载荷回收。截至当前（2060 年 3 月），该构型三架轨道器均在役，机队规模持续扩大，VS-11 及后续轨道器正在规划中。详见独立页面<a href="/home/Space_Shuttles/Vulture_Shuttle_Block_2">秃鹫航天飞机改进乙型</a>。</p>
|
||||
<table>
|
||||
<thead><tr><th>编号</th><th>名称</th><th>首飞</th><th>飞行次数</th><th>状态</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>VS-08</td><td>荣誉号（Honor）</td><td>2055 年 3 月</td><td>250</td><td>在役</td></tr>
|
||||
<tr><td>VS-09</td><td>信念号（Conviction）</td><td>2056 年 6 月</td><td>202</td><td>在役</td></tr>
|
||||
<tr><td>VS-10</td><td>希望号（Hope）</td><td>2057 年 8 月</td><td>154</td><td>在役</td></tr>
|
||||
</tbody></table>
|
||||
<p>Block 2 机队飞行次数为截至当前（2060 年 3 月）的累计值，仍在持续增长。三架 Block 2 轨道器当前每年可合计完成超过 144 次飞行，为后续母舰建造和深空任务提供了前所未有的发射节奏。荣誉号作为首架 Block 2 轨道器，入列后迅速投入高频运营，入列首年即完成超过 40 次飞行。</p>
|
||||
<p>Block 1 是秃鹫航天飞机的基线重载航天飞机构型，依靠外挂燃料箱和液体燃料助推器执行高轨重载任务。Block 1.5 是由既有 Block 1 轨道器改装而来的核气塞发动机试验/运营构型，获得 SSTO 能力但牺牲了重载性能。改进乙型则是直接面向高能推进任务生产的后续型号，具备低月球轨道往返能力，但返回载荷和再入速度受到严格限制。</p>
|
||||
<h2 id="成本与经济性">成本与经济性</h2>
|
||||
<p>秃鹫航天飞机的典型无人或常规货运任务单次成本约为 8000 万美元，载人任务成本通常更高。其主要成本来自外挂燃料箱制造、发射和回收场地支持、轨道器和助推器检修、危险推进剂处理、人员训练和任务控制。</p>
|
||||
@@ -376,11 +425,11 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<thead><tr><th>参数</th><th>数值</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>类型</td><td>部分可重复使用航天飞机系统</td></tr>
|
||||
<tr><td>继承线</td><td>STS 航天飞机 - CERV 航天飞机 - 秃鹫航天飞机</td></tr>
|
||||
<tr><td>世代</td><td>第三代航天飞机（前身：第一代 STS → 第二代 CERV）</td></tr>
|
||||
<tr><td>前身</td><td>CERV 航天飞机</td></tr>
|
||||
<tr><td>研发开始</td><td>2030 年</td></tr>
|
||||
<tr><td>首次飞行</td><td>2038 年，无人轨道飞行</td></tr>
|
||||
<tr><td>首次服役</td><td>2040 年代初</td></tr>
|
||||
<tr><td>首次飞行</td><td>2037 年，无人轨道飞行</td></tr>
|
||||
<tr><td>首次服役</td><td>2039 年</td></tr>
|
||||
<tr><td>主要发射场</td><td>文昌</td></tr>
|
||||
<tr><td>主要着陆设施</td><td>文昌配套航天飞机跑道</td></tr>
|
||||
<tr><td>典型目标轨道</td><td>1000 km x 1000 km，45 度倾角</td></tr>
|
||||
@@ -398,9 +447,9 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<thead><tr><th>参数</th><th>数值</th></tr></thead>
|
||||
<tbody>
|
||||
<tr><td>轨道器机身</td><td>MK4 型机身</td></tr>
|
||||
<tr><td>Block 1 轨道器</td><td>7 台，VS-01 至 VS-07</td></tr>
|
||||
<tr><td>Block 1.5 轨道器</td><td>2 台，由 VS-06、VS-07 改装</td></tr>
|
||||
<tr><td>改进乙型轨道器</td><td>3 台，VS-08 至 VS-10</td></tr>
|
||||
<tr><td>Block 1 轨道器</td><td>5 台，VS-01 至 VS-05（已退役）</td></tr>
|
||||
<tr><td>Block 1.5 轨道器</td><td>2 台，VS-06、VS-07 由 Block 1 改装（在役）</td></tr>
|
||||
<tr><td>改进乙型轨道器</td><td>3 台在役，VS-08 至 VS-10（机队扩大中，VS-11 规划中）</td></tr>
|
||||
<tr><td>测试机数量</td><td>2 台结构测试机，1 台大气飞行测试机</td></tr>
|
||||
<tr><td>轨道器编号体系</td><td>测试机使用 VSTA/VA，入轨轨道器使用 VS-xx</td></tr>
|
||||
<tr><td>轨道器干重（Block 1）</td><td>111.6 吨</td></tr>
|
||||
@@ -427,8 +476,9 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tr><td>结构过载能力</td><td>长时间 5 g，短时间 8 g</td></tr>
|
||||
<tr><td>热防护</td><td>升级版标准化隔热瓦，增强前缘材料，烧蚀涂层，隔热涂层</td></tr>
|
||||
<tr><td>乘员逃生系统</td><td>整体式乘员舱弹射，降落伞着陆</td></tr>
|
||||
<tr><td>核热推进试验</td><td>VS-05 对 OMS 系统进行改造，用于热核推进技术测试</td></tr>
|
||||
<tr><td>核气塞发动机衍生型</td><td>VS-06、VS-07 升级为 Block 1.5；VS-08 至 VS-10 直接作为改进乙型生产</td></tr>
|
||||
<tr><td>核热推进试验</td><td>VS-05 耐心号（2048 年起对 OMS 系统进行改造，用于热核推进技术测试）</td></tr>
|
||||
<tr><td>Block 1.5</td><td>VS-06 坚毅号（2052 年完成改装，在役）、VS-07 忠诚号（2053 年完成改装，在役）</td></tr>
|
||||
<tr><td>改进乙型</td><td>VS-08 荣誉号、VS-09 信念号、VS-10 希望号，全部在役，机队扩大中</td></tr>
|
||||
</tbody></table>
|
||||
<h3 id="外挂燃料箱参数">外挂燃料箱参数</h3>
|
||||
<table>
|
||||
@@ -447,8 +497,8 @@ body.wiki-image-lightbox-open { overflow: hidden; }
|
||||
<tbody>
|
||||
<tr><td>液体燃料助推器数量</td><td>2 枚，对称布置</td></tr>
|
||||
<tr><td>助推器直径</td><td>5 米</td></tr>
|
||||
<tr><td>助推器发动机</td><td>每枚 19 台“天火-12”液氧煤油发动机</td></tr>
|
||||
<tr><td>助推器发动机总数</td><td>38 台“天火-12”</td></tr>
|
||||
<tr><td>助推器发动机</td><td>每枚 19 台"天火-12"液氧煤油发动机</td></tr>
|
||||
<tr><td>助推器发动机总数</td><td>38 台"天火-12"</td></tr>
|
||||
<tr><td>助推器推进剂</td><td>液氧/煤油</td></tr>
|
||||
<tr><td>助推器干重</td><td>46.5 吨（单枚）</td></tr>
|
||||
<tr><td>助推器燃烧时间</td><td>135 秒</td></tr>
|
||||
|
||||
@@ -0,0 +1,3 @@
|
||||
1. 清理掉现在项目根目录里面用不到的文件，如果有能用到的，梳理一下放到应该有的文件目录里面去
|
||||
2. 执行完1，我们开始准备一个新的wiki文档。CERV Shuttle。
|
||||
|
||||
Reference in New Issue
Block a user