SpaceX reinstalling 29 Raptor engines on first orbital-class Starship booster
For the second time this month, SpaceX has begun installing 29 Raptor engines on Starship’s first orbital-class Super Heavy booster, potentially paving the way for several crucial milestones.
On August 1st, around the same time as SpaceX finished installing car-sized grid fins on a Super Heavy for the first time, the company began the process of installing multiple Raptor engines on the booster (#4) that might one day support Starship’s first orbital launch attempt. Not long after it began, it became clear that SpaceX was installing a full 29 Raptor engines on Booster 4 (B4) at a breakneck pace, and less than 24 hours later, all had been attached to Super Heavy’s thrust structure.
Barely a day later, Super Heavy Booster 4 was rolled to the orbital launch pad and installed on a massive ‘launch table’ that was itself installed just a few days prior after months of assembly. Four days after engine installation, Starship S20 and Booster 4 were briefly mated together, forming a full Starship stack – the tallest and most powerful rocket ever built – for about an hour. However, while it did serve as a useful learning experience and pathfinder operation, both stages were demated and returned to the factory soon after.
Since Booster 4’s later August 11th build site return, SpaceX teams have been hard at work fitting the massive 69m (225 ft) tall rocket booster with thousands of feet (if not miles) of secondary plumbing and power and avionics cables. That process effectively began with removing the Super Heavy’s 29 Raptor engines, which finished just a few days after its return to the high bay.
Now, just 12 days after Super Heavy Booster 4 arrived back at the high bay and 11 days after workers briskly removed its Raptors, SpaceX has begun the process of reinstalling those engines – albeit with several new entrants this time around. When SpaceX first fitted B4 with Raptors, it became clear that five or more of had never been tested, making the removal of some of the Super Heavy’s 29 engines more or less inevitable. Indeed, as expected, several new Raptors (engines that weren’t clearly installed the first time around) have joined around two dozen engines that were installed earlier this month.
Given that Booster 4 has already completed a range of fit checks, the implication is that SpaceX is now installing the 29 Raptor engines that will support the first static fire test campaign of a flightworthy Super Heavy. Of course, that testing (likely involving several different static fires of an increasing number of Raptors) could unearth issues or even damage some of those 29 Raptors, so it isn’t quiteaccurate to say that Booster 4 is being fitted with the engines that will help it carry Starship to orbit. Depending on the outcome of those tests, though, most could easily find themselves lifting off on Super Heavy B4 later this year.
For now, though, Super Heavy Booster 4’s next milestone will be its second trip from the build site to the launch pad. That could occur at any point in the next week or two and could find Booster 4 installed beside Ship 20 on the second of two suborbital test stands, though the Super Heavy may instead return to the orbital launch site.
Quelle: TESLARATI
+++
The Boring Company pitches tunnel project for access to Boca Chica during SpaceX launches
The Boring Company (TBC) met with Cameron County officials to discuss the possibility of a tunnel project running from South Padre Island (SPI) to Boca Chica Beach.
The Boring Company pitched the idea of an SPI-Boca Chica tunnel to Cameron County administrator Pete Sepulveda Jr. and county engineer Benjamin Worsham early this summer. Cameron County officials have been thinking of giving people access to part of Boca Chica Beach even during closures.
SpaceX activity has been steadily increasing as it continues to develop the Starship program. In August alone, Cameron County issued at least 13 public notices ordering temporary and intermittent closures due to SpaceX’s activities.
(NASASpaceflight – bocachicagal)
Starship’s flaps practically sit flush with their aerocover heat shielding when installed. (NASASpaceflight – bocachicagal)
Half-covered in heat shield tiles, it’s not clear how SpaceX plans to seal off the more sensitive, exposed components of each flap’s actuation mechanism – including motors, cabling, and the hinge itself. Based on what’s visible, Starship’s flaps and the cradle-like ‘aerosurfaces’ they slot into do have very tight tolerances and may rely on some felt-like ceramic wool or TPS blanket to seal the tiny remaining gaps. With small enough gaps, a hypersonic airstream can behave as if there are no gaps at all, suggesting that that might be SpaceX’s preferred approach to sealing Starship flaps.
Up next on Starship S20’s path to launch is the reinstallation of 3-6 Raptor engines (for the third time) ahead of a crucial static fire test campaign that could begin as early as Thursday, October 7th. Likely beginning with 1-3 Raptors, SpaceX will perform an unknown number of static fire tests, ultimately culminating in the first ignition of 4, 5, and 6 engines on any Starship prototype. If all goes well, that testing will also mark the first time Raptor Vacuum has been ignited on a Starship prototype and the first time SpaceX has ignited multiple Raptor variants (sea level and vacuum, in this case) on the same vehicle. Stay tuned for updates on engine installation.
Quelle: TESLARATI
----
Update: 12.10.2021
.
SpaceX installing Raptors on first orbital-class Starship – third time’s the charm?
For the third time in two months, SpaceX has begun installing Raptor engines on its first orbital-class Starship prototype – hopefully for good.
In no uncertain terms, Starship 20’s (S20) path to what could be its last Raptor installations has been about as windy and mysterious as they come. Starship 20 (S20) left the Starbase factory floor for the first time in early August – all six Raptors installed in another program first – for a brief fit check and photo op. After spending about an hour installed on top of Super Heavy Booster 4 (B4), Ship 20 was removed and returned to the build site, where teams removed all six engines and finished wiring and plumbing the vehicle.
Days before the ship’s long-anticipated trip to Starbase’s suborbital launch site for qualification testing, the mount SpaceX prepared for the process quickly had hydraulic rams – used to safely simulate Raptor thrust – were abruptly removed. Starship S20 was then installed on the Pad B mount, where SpaceX proceeded to reinstall six Raptors. Weeks later, after slow heat shield repairs neared completion, SpaceX again removed Ship 20’s Raptors and reinstalled the hydraulic rams it had removed – unused – the month prior. Finally, on September 30th, some seven weeks after the prototype arrived at the suborbital launch site, SpaceX put Starship S20 through its first major test – a lengthy ‘cryoproof’.
Now, ten days after completing a seemingly flawless cryoproof test on its first try, SpaceX has once again trucked multiple Raptors – at least one sea level and one vacuum engine – from the Starbase build site to Starship S20’s suborbital test stand. From the outside looking in, it’s hard not to view the contradictory path S20 took to its first tests – and is still taking to its first static fire(s) – as an unusually visible sign of some kind of internal tug of war or major communication failure between different SpaceX groups or executives.
It’s impossible to determine anything specific beyond the apparent fact that several of the steps taken from Ship 20’s first factory departure to its first cryoproof and static fire tests could have probably been deleted entirely with no harm done and many dozens of hours of work saved. At the end of the day, Starship S20 completed cryoproof testing without issue on the first try and is now seemingly on track to begin its first static fire test campaign later this month.
At the moment, SpaceX has three possible static fire test windows scheduled from 5pm to midnight CDT on Tuesday, Wednesday, and Thursday (Oct 12-14). A similar Monday window was canceled days ago on October 7th, suggesting that more cancellations are probably on the horizon. For now, there’s a chance that Starship S20 – with anywhere from two to all six Raptor engines installed – will fire up for the first time before next weekend. It’s hard to say how exactly SpaceX will proceed. It’s not inconceivable that SpaceX will install all six engines and gradually ramp up to a full six-engine static fire over several tests.
Raptor Vacuum has identical plumbing but a far larger nozzle than its sea-level-optimized siblings. A larger nozzle boosts engine efficiency in or near vacuum.
Given that SpaceX has already static fired three Raptor Center (RC) engines on multiple Starship and Super Heavy prototypes, odds are good that Starship S20’s test campaign will be similar – beginning with a three-Raptor static fire, in other words. SpaceX could then add one, two, or all three Raptor Vacuum engines into the fray for one or more additional tests with 4-6 engines total. It’s also possible that suborbital launch mount and pad limitations will prevent more than three engines from firing at once, in which case SpaceX would presumably perform two separate tests of Ship 20’s Raptor Center and Raptor Vacuum engines.
Given that two Raptor variants have never been static fired simultaneously on the same vehicle, it’s hard to imagine that SpaceX won’t also want to perform one or several combined static fires with Raptor Vacuum and Raptor Center engines on Ship 20.