Starbase Sunday #9
Welcome to the 9th edition of Starbase Sunday, our weekly series of articles explaining the main events happening at Starbase and McGregor! As we promised at the end of last week’s article, this week was full of exciting and groundbreaking events, which will blow your mind, so sit back, relax, and enjoy:
July 27th - Sunday - Ship 38 rollout
Let’s start at the production site, where we witnessed the first vehicle move in weeks: after receiving the cryo stand and being lifted onto it, Ship 38 exited Megabay 2 and was rolled to the Massey’s test site!
Here, Ship 38 is set to undergo one or more cryogenic tests, where the tanks will be filled with cryogenic liquid oxygen and liquid nitrogen (LOX and LN2) to verify its structural integrity; cryo tests are the first real form of validation engineers get, the first real results of their months-long hard work, and the first time they can really validate the Ship’s structures and eventually qualify it for further testing.
Like we talked about last week, this also shows SpaceX’s capabilities to rapidly turn around after an anomaly at a test site, with the roll occurring a mere 39 days after Ship 36’s explosion. The tank farms required for cryogenic tests (LOX and LN2) have sustained little to no damage, and nothing was changed, meaning the test site can safely perform cryo tests.
Also at the production site, a Ship transport stand was rolled in and parked in front of Megabay 2, undoubtedly for Ship 37’s roll to the launch site to perform a static fire on the OLM, a time-saving measure taken by the SpaceX team to continue with flight preparations while their usual test site is down.
Additionally, teams continued with the CFA drills for the Gigabay’s foundations! Calculations and research by Ryan Weber (NSF) reveal that each CFA drill uses about 8.4 cubic meters of concrete, and with at least 1000 CFA piles, a total of 8400 cubic meters of concrete will be needed just for the piles.
Going out to the launch site, a small vertical tank was delivered and lifted into position in the afternoon.
July 28th - Monday - Ship 37 rollout and lift
Let’s start at the production site today, where a unique event occurred! This was indeed the long-awaited day of rollout for Ship 37, headed for a record-breaking static fire campaign on the OLM, as part of SpaceX’s recovery plan after the explosion of Ship 36 at Massey’s… the initial road delay indicated a transport window between 00:00 and 04:00 am; however, it was clear this wouldn’t have been used since the transport stand itself went inside Megabay 2 shortly before the end of the road delay. We received some more indication in the early morning, shortly after 6 am, when Ship 37 was lowered on the stand, and the MB2 door was opened, revealing the vehicle in all its beauty: the first thing to catch our eyes was the heatshield, where several spots were still left without tiles, indicating it would take some more work after testing, although not much, to finish the heatshield. For the more trained, we could also see the absence of structural catch pins, which have usually been installed prior to static fire testing until now; however, it won’t take long to mount and secure them, so no worries. Apart from that, there weren’t any major things to notice, and it was clear that if the static fire campaign went well, it wouldn’t be long before we saw a flight.
Later in the morning, as Ship 37 was disconnected from the lift jig and rolled out of the bay, we got an update from the Starbase City website, indicating the new delay was scheduled to start at 10 am and would extend until 4 pm. Although, given the state of readiness, it was pretty clear SpaceX wouldn’t waste time and roll as soon as they could… and that’s what they did: at around 10:30 am, Ship 37 began its journey to the launch site, giving amazing daylight views to all who watched either in person or online. Even if it seemed like another normal rollout, most of those who were watching knew that this was well out of the ordinary, and we all understood its importance; this feeling stayed with all of us during the transport, which lasted a little more than 1 hour, after which Ship 37 was parked inside the chopsticks.
Going into the afternoon, at Pad A, SpaceX didn’t waste time and attached the stabilizer arms to the stabilizer points on the Ship, while teams down on the ground attached the SQD plate adapter to the SQD position: this adapter plate will enable the flowing of propellants from the ground tanks to the rediverted OLM pipes and finally into the Ship.
After a few hours of work, teams were ready: at 16:42 in the afternoon, the chopsticks started going up, bringing the Ship with them; the Ship was left “hovering” above the Starstool for a while, while teams managed to orient it correctly and stabilize it. But in the end, after more than an hour, the Ship gently touched down on the adapter on the OLM, and the clamps were in place… a Ship was now officially on the OLM!
After the chopsticks were opened, work immediately began to inspect the Ship, especially attaching the flexible hoses to the SQD adapter plate, connecting other flexible hoses for the Ship’s engine chill system (whose lines ran from the Booster lines to the OLM table and then into the Ship’s engine bay, instead of passing through the SQD), ensuring the structural stability and correct alignment on Starstool, and a whole bunch of other inspections.
During the lift, the Starbase City website indicated that the beach closures for testing on the 29th and 30th had both been delayed by a day, to the 30th and 31st. This is likely a measure to have more time to work, inspect, and prepare the Ship for its testing, and the 2 closures are likely for a single-engine static fire and a 6-engine static fire. But don’t worry, we will talk about all of those as they come.
Now, let’s do a quick visit at Massey’s, where S38 has been transported there for cryo testing. As I mentioned yesterday, Ship 38 conducted an ambient test and a payload bay door test, and as of today the door was still open. There was also some action on the can crusher stand, where B18.1 is being tested, with some welding ongoing on the test stand.
B18.1 has been in the test stand since May, with the goal of validating the structural performance of the aft section of the new generation Boosters; after conducting 2 cryogenic tests in late May/early June, B18.1 has been relatively quiet and was being prepared for a new test when S36 exploded. It didn’t seem to report any damage, but it hasn’t performed any cryo test yet, although it’s very likely there have been some tests with the actuators (we couldn’t know).
July 29th - Tuesday
Let’s start at Pad A, where most eyes were rightfully pointed as SpaceX was preparing for a groundbreaking static fire of Ship 37 on the OLM. The first of 2 static fires is expected to be a single-engine SF to be performed tomorrow, so SpaceX took today to prepare for it: yesterday they had already performed the major operations, such as checking that the Ship was correctly aligned and set on the stand and connecting the flexible hoses to the SQD adapter plate, so today they performed checks of all the systems, and they worked all day in the engine bay, likely inspecting and working on the engines or related systems. Additionally, they installed and connected additional flexible hoses to the engine chill lines, and they inspected and finalized work and testing on the other main hoses on the BQD.
The transport stand was moved early in the night to the Hopper parking lot, ready to transport the Ship following testing.
At the production site, work continued to drill CFA piles into the ground ahead of placing the Gigabay’s foundations.
Also, a protective “door” was installed on one of the Ship work stands in Megabay 2 to protect its equipment against external elements (such as dust, water, or something else).
At Massey’s, it was yet another day without cryo tests for Ship 38, although the payload bay door test seemed to continue, as it remained open for the whole day.
Also, thanks to Jack Beyer’s images, we can confirm that at least 5 engines seem to have been removed from Booster 13’s aft section, which is located at Massey’s for an unknown reason… however, it’s surely interesting to follow what they will do with this; there may have been up to 8 additional engines removed in the past few days, which may align with weird sightings of damaged Raptors at McGregor (fun fact: our writer Raptor, who is also an NSF Mod, spotted them!).
July 30th - Wednesday - Ship 37 single-engine SF attempt
Today was finally the long-awaited day of testing for Ship 37, which was scheduled to ignite a single center engine to simulate an in-space burn, marking the first of 2 static fires for Ship 37. Now, let’s see and work through every preparation and event that occurred on this exciting day:
- Preparations began that night, when the LR11k crane at Pad B turned its back to protect it from the blast, along with the Raptor work platform (also called the dancefloor) lowered from the OLM, marking the end of work on the Ship’s Raptor engines, with both events occurring at 04:25-05:00 am.
- Following these operations, the beach and road were closed at 07:25, while many cars were still at the pad working on something. Starting at 08:00, the chopsticks opened and were raised to launch position wide open, and after they reached that, the SQD arm swung into its usual position at 08:19, as the pad was cleared.
- At 08:25, we started to see venting from the nitrogen tanks in the tank farm, suggesting that the chilldown process to chill down the ground lines was starting, possibly indicating we were a few hours from the static fire. This venting continued until 09:06 before stopping, suggesting that what happened was in reality an ambient pressure test, where nitrogen is loaded at ambient pressure and temperature inside the vehicle to validate its structural integrity… this might’ve been done to test the structural safety of the vehicle on Starstool.
Venting resumed, though intermittently, at 10:40, suggesting the end of the ambient pressure test; however, it stopped shortly afterwards at 11:00. But why did it stop? Was this planned? What’s going on? We were about to get an answer.
- Ship 37 gifted us with a cool igniter test at 11:43: the igniters are the system in a rocket engine thanks to which the engine is allowed to start… in Raptor, there are torch igniters, which ignite a small amount of LOX and CH4 to create a small flame that makes the exhaust react and combust when it comes in contact with it, ensuring the ignition of the engines; testing them before launches or static fires is essential to see whether they’re operating at the correct and required parameters, allowing engineers to work on them and switch them if needed.
- Following the igniter test, the tank farm remained quiet until we saw 4 pickups running down the road towards the launch site, escorted by a police car. This was the incredible Red Team, which is a small team of engineers that stands ready to go to the launch site to troubleshoot issues when no one else is allowed (i.e., when the road is closed); at least 6-9 engineers drove there and parked near the tank farm at 12:31 before coordinating and going deep inside. It wasn’t long until we saw positive signs, with the pope vent starting at 12:43 and venting resuming a couple of minutes later; even though the pope vent stopped at 13:11, venting continued, and all the cars left the launch site… because that’s how the Red Team works: fast and good. Unfortunately we don’t know what the problem was, because it may have been some troubleshooting for the pope vent or some other system that prevented the countdown from going further. Anyway, the most important thing is that they were proceeding smoothly.
- The final stretch finally began, with a DSS test conducted at 13:21, just a few minutes after the cars left the pad: the DSS (Detonation Suppression System) is composed of nitrogen and water that get sprayed under the OLM from nozzles installed on the OLM ring and is used to prevent explosions during ignition by eliminating hazardous compounds. The DSS is activated roughly 15 seconds prior to ignition, but it’s also tested beforehand to ensure it works; usually this test occurs in the morning, hours before the static fire, but for some reason today it happened much later… so could it have been the reason the Red Team had to go? If we think about it, the conditioning had begun earlier today but quickly stopped; it may have been ambient, but it may have been that teams saw the DSS test fail. It also doesn’t seem a coincidence that the DSS was tested after the cars left the pad, but this is speculation, and they may have repaired something else.
Later, at 13:23, venting resumed, and a few minutes later (at 13:29), the pope vent started, this time indefinitely! The game was on, and SpaceX was proceeding with their attempt at a static fire on the OLM.
- There aren’t a lot of things that happen after the pope vent, but those that do happen are the most important… one of the examples is the OLM vent, which started at 14:27: the OLM vent is a vent that goes out of the OLM, and it means that the chilldown process has shifted from the ground lines to the OLM lines, chilling down the actual lines that will bring propellant to the vehicle. This vent is important, because when it stops, it means propellant is being loaded!
- And that, the end of the OLM vent, came at 14:49, after a “mere” 22 minutes of chilldown. That indicated that propellant loading was beginning, and we saw a frost line appear on the LOX tank at 15:00 on the dot! SpaceX was loading a Ship on the OLM for the first time ever, and we were there to witness it… a small while later, at 15:16, the CH4 tank started loading.
By the quantity of propellant loaded and the timing since loading, it was now confirmed that this was an attempt for a single-engine static fire.
- Now in the final phases before static fire, all 4 flaps were tested at 15:18, meaning the countdown had gone under 10 minutes before the static fire, with a possible T-0 at 15:29/30.
At 15:25 the OLM vent came back, meaning propellant loading had been completed, with 2 rings of LOX and less than half a ring of CH4, and the static fire was possibly under 3 minutes from now.
- But not every day is a good day… after a hold, at 15:37, we saw both the OLM vent and the pope vent starting, and we possibly heard the depress vent; however, the return of those 2 vents indicated a drain of propellants, indicating there had been an abort, and that was confirmed at 15:46 when the frost line started to lower. The reason for the abort may have been a range violation issue at sea, since it looks like a boat was in the vicinity, and the ground and vehicle sides looked to be nominal.
This may not have been a static fire day, but it was for sure a wonderful day, where SpaceX attempted something that only 2 months ago would’ve been deemed never to happen b by themselves.
- Following the detanking operations, ending roughly after 1.5 hours, the chopsticks were lowered to the base of the tower and closed around the vehicle at catch point height, while the dancefloor rolled back in at 19:30, by which time the road had already been opened and cars were allowed to the pad.
So what’s next? Well, it’s likely that the single-engine static fire will take place tomorrow, while the 6-engine static fire will take place the following day.
But the day’s not over yet! You see, SpaceX has a habit of doing incredible things, and today they tested 2 Ships at the same time, with Ship 37 attempting a static fire on the OLM and Ship 38 conducting a successful cryo test at Massey’s! So let’s look at the timeline:
- Venting started in the morning, around 10 am, at Massey's tank farm. This marked the chilldown process, which was completed when loading began at 11:47 in the CH4 tank and at 11:51 in the LOX tank! Like I’ve said before, cryo tests use cryogenic liquid oxygen and nitrogen (LOX and LN2) but don’t use CH4 to avoid possible ignition problems if the structure fails. Both tanks were fully loaded by 12:33 and were held at pressure for some time, during which teams tested pressurization systems, vents, and much more. The frost started lowering on both tanks at 14:10, with the tanks mostly emptied after 2 hours.
Let’s conduct a last stop at the production site where the Ship work stand that received a door yesterday received 2 other protective doors today to shield the equipment from foreign objects.
July 31st - Thursday - Ship 37 single-engine static fire
Today was another action-packed day, with Ship 37 reattempting and succeeding in conducting a static fire of a single Raptor engine.
- Preparations for today’s static fire test began during the night, with the dancefloor being lowered at 04:30 and later brought away. Later at 06:55, as the sky was filled with pink colors from sunrise, the chopsticks began their 10-minute journey to the top of the tower, followed by the SQD arm going into launch configuration. Lastly, at 08:09 the DSS (Detonation Suppression System) was tested, spraying an amount of nitrogen and water under the OLM that will be used to avoid unwanted explosions before the static fire. All of these were signs that SpaceX not only was aiming to test today but also wanted to do it quickly, with the DSS test occurring more than 5 hours earlier than during yesterday’s attempt.
- After the test, the road was closed at 09:03 and the pad was cleared. After a couple of hours of quiet time, the tank farm started to condition at around 11:18, with the pope vent quickly following at 11:20, meaning that the chilldown process was in full swing.
After the chilldown process of the ground tanks was completed, the OLM vent started at 12:31 to chill down the lines that bring propellant to the Ship!
- The OLM vent continued to chill down the lines until 13:10, when it stopped, marking the start of propellant loading: the frost lines appeared at 13:22 for the LOX tank and at 13:36 for the CH4 tank. As expected, at 13:40 all 4 flaps were tested, which usually occurs at T-9 minutes, meaning we were really close to the static fire.
- And then, the final phases came: at 13:47, the OLM vent came back, marking the end of propellant loading. After what looked to be like a brief hold, the DSS activated at 13:52:30, followed by the water deluge system at 13:52:40, and finally the ignition at 13:52:44!
As expected, Ship 37 ignited a single sea-level Raptor engine for 6 seconds, simulating an in-space burn, meaning the propellant was fed from the header tanks… so why load the main tanks? That’s mostly to increase the weight of the Ship and reduce the load on the hold down clamps, as well as to provide propellant to the headers.
The important thing is that SpaceX completed the first-ever Ship static fire on the orbital launch mount, an amazing achievement given the rapidity with which it was developed!
- Following the successful static fire test, Ship 37 started to detank, and given the small amount of propellant loaded (only 2 rings of LOX and less than half a ring of CH4), it detanked rather quickly, allowing for the road to be reopened at just 14:47. Cars immediately went to the pad and got to work, with the dancefloor rolling to the pad at 16:30 for inspections, work, and preparation for tomorrow’s static fire.
Today’s operations wrapped up after a successful single-engine static fire, paving the way for a more complex, 6-engine static fire tomorrow, and marking another step towards Flight 10 readiness. Congratulations to the SpaceX team!
Now let’s do a quick hop at the production site, where the hot staging ring for Flight 10 was rolled inside Megabay 1 ahead of installation atop Booster 16. This is the last thing Booster 16 needs before rolling out to the pad, suggesting that SpaceX is ready to roll it as soon as the OLM modifications are undone.
August 1st - Friday - Ship 37 6-engine static fire & Ship 38 rollback
Today was another action-packed exciting day, starting not at Pad A but rather at Massey’s, where Ship 38 departed the test site at midnight, during a road delay that lasted until 4am, to go back to the production site, which it reached later during the night. I would like to take a moment to recognize that this is the last ever Block 2 Ship to be tested at Massey’s: following her departure, teams will work to configure the Ship cryo station for Block 3 Ship, the first of which to be cryo tested should be Ship 39 sometime in the fall.
Also at the production site, a Starlink loader box (whose purpose remains unknown) got out of Starfactory and was brought into MB2 in the early morning, where it was rigged and lifted somewhere before the door closed.
Now, let’s go out at Pad A, where most eyes were turned ahead of a possible 6-engine static fire:
- It was clear it would’ve been a longer wait than previous tests/attempts, since as of 7 am the dancefloor was still in place, work at Pad B was ongoing, and tankers were still unloading commodities at the tank farm.
- A few hours later, at 09:45, the dancefloor lowered and got transported away, and half an hour later both the road and beach were closed. Then, at 10:46, the DSS got tested: during such a test, the Detonation Suppression System sprayed a bunch of nitrogen and water under the OLM, verifying it was working as intended ahead of use before engine ignition to prevent explosions. Roughly a minute later, the last cars left the pad!
- The tank farm started its conditioning at 12:22, followed by the start of the pope vent at 13:10, meaning the process of chilling down the ground lines was in full swing! However, not everything was going smoothly: in the middle of conditioning the tank farm, the road closure for testing got extended by 2 hours up until 9 PM, and the OLM vent didn’t start when it should’ve, not even with margins… so something was going wrong, and our suspicions got confirmed when we saw the Red Team arrive at the pad at 14:16. The Red Team is a group of engineers that go to the pad during testing closures to troubleshoot issues if they present… the last time we saw this team go to the pad was 2 days ago, during Ship 37’s first attempt to static fire a single engine. This time it was just 2 pickups escorted by a police car, and the engineers went inside the tank farm once again… however, this wasn’t a long stay, as they departed the launch site at 14:57.
- Only a few minutes after the red team left the pad, at 15:00, the OLM vent started, marking the beginning of the chilldown process for the lines that bring propellant to the Ship.
After completing this process, the OLM vent stopped at 15:27. It only took a few minutes before we saw a frost line on the LOX tank, at 15:44, followed by a frost line on the CH4 tank at 15:50.
- The flaps moved at 16:15, making us realize how close we were to the static fire… also, this marked the furthest SpaceX has been in Ship testing since the explosion of Ship 36 at Massey’s. Then, at 16:21, the OLM vent came back on, marking the end of propellant loading with the LOX tank completely full and the CH4 tank loaded with about half a ring of propellant.
After a few minutes of hold, the DSS went off at 16:30:58, followed by the water deluge at 16:31:09, and finally the ignition at 16:31:14! All 6 engines ignited in a timely manner, with the 3 RVacs igniting first, followed by the 3 sea-level engines… they burned for about 10 seconds before shutting down, marking the first Ship 6-engine static fire of “normal” duration since Ship 33 (normal as of a 10s firing duration like it was done for Ships previous to Ship 34, after which the 6-engine SFs targeted 60s of duration, with one attempt from Ship 35 lasting half that before aborting).
- Following the successful static fire, Ship 37 started to detank and had mostly completed this operation by 18:15, when the chopsticks completed their 20-minute journey to the base of the tower and closed around the Ship’s lift points, ready to lift it when given the command.
At that point, the road was reopened, and cars started flowing to the pad like a hive of engineers ready to look at their vehicle after their effort.
In 44 days, SpaceX went from a dooming explosion that made them lose a vehicle and heavily damaged the test site to incredible success by quickly designing, developing, and testing a system that was never meant to exist. This is a testament to SpaceX’s capabilities of flexibility, innovation, and seriousness about time. This mindset and related effort is what will make Starship work, allowing us to become a multiplanetary species.
August 2nd - Saturday
Let’s start at Pad A, where the dancefloor and transport stand were both rolled to the pad during the night to get ready for a transport, which the Starbase City website claimed to be between 21:00 and midnight tonight.
After initially inspecting the Ship, workers disconnected the flexible hoses and the SQD interface from the Ship in the afternoon. Later that night, Ship 37 was lifted and held up in the air for over an hour during sunset before being set down and secured to the transport stand. The road delay window got passed, so the rollback was delayed until August 3rd, meaning it’s a story for a new weekly article.
Now let’s go to Pad B, where the LOX BQD hood was delivered in the morning and lifted later in the day to the LOX BQD system. This system looks to be close to completion, and I think we could expect to see it finished by the end of this month.
And with a quick hop at the production site, the Starlink loader box was rolled out of MB2 and into the Starfactory, following 2 days of unknown testing inside.
This wraps up an exciting week of testing and unprecedented achievements by the SpaceX team… but now, let’s answer a question all of you will be asking:
When is Flight 10?
Officially there isn’t any notice or closure for the flight, but Elon Musk said in a tweet on X after Ship 37’s single-engine static fire that flight 10 was targeting mid-August… this is feasible, and here’s why:
- Booster 16: Booster 16 was static fired on June 6th and has been flight ready since. It received its last piece, the Hot Staging Ring (HSR), this week and has likely already been crowned. This means it will be ready for rollout whenever the pad is.
- Ship 37: as we’ve seen, Ship 37 has just completed its static fire campaign successfully and has rolled to the production site. Now, engineers will complete the missing pieces of its heatshield, add the test tiles, mount the structural catch pins, and verify every system is good for rollout. Yeah, it seems like a lot, but it’s nothing they can’t do in a few days.
-Pad A: the pad is the long pole for this flight, since engineers will have to undo all the modifications done to allow static fires of Ships. That includes removing Starstool, removing the added redirected pipes and the framework, re-welding the OLM pipes correctly, removing the engine chill pipes, and that’s about it. It will likely take the whole next week, and we’ll be here to witness it!
So yeah, Starship can launch in mid-August, and it probably will. We could expect to see some notices (like NOTAMs, NOTMARs, and TFRs) as soon as this week, as well as rollout closures… the fastest SpaceX has completed a launch campaign has been for Flight 6, when there were only 5 days between the rollout of the first of the 2 vehicles and the launch. So we’ll have to see when they will roll it out, but it’s very likely we will see a launch before the 15th, and almost surely we’ll see one before the 20th.
Raptor testing
July 27th
No Raptor tests were conducted today.
July 28th
- Raptor vertical - 10:38:23 - 20s
- Raptor vertical - 10:38:50 - 20s
- Raptor vertical - 18:17:27 - 20s
- Raptor vertical - 18:17:55 - 20s
- Raptor vertical - 18:18:21 - 20s
- Raptor vertical - 18:18:48 - 20s
Total tests: 6
Total fire time: 120s / 2m
-Raptor vertical: 120s / 2m - 6 tests
July 29th
- Raptor vertical - 10:43:16 - 20s
- Raptor vertical - 10:43:43 - 20s
- Raptor vertical - 10:44:10 - 20s
- Raptor vertical - 10:44:37 - 20s
- Raptor vertical - 10:45:05 - 20s
- Raptor vertical - 10:45:29 - 20s
Total tests: 6
Total fire time: 120s / 2m
-Raptor vertical: 120s / 2m - 6 tests
July 30th
- Raptor north - 11:32:14 - 2s - first test at Raptor North
- Raptor vertical - 18:53:06 - 100s / 1m40s
Total tests: 2
Total fire time: 102s / 1m42s
-Raptor vertical: 100s / 1m40s - 1 test
-Raptor north: 2s - 1 test
July 31st
- Raptor vertical - 12:17:26 - 130s / 2m10s
- Raptor south - 14:43:37 - 20s
- Raptor south - 14:44:04 - 20s
- Raptor south - 14:44:31 - 20s
- Raptor south - 14:44:58 - 20s
- Raptor south - 14:45:24 - 20s
- Raptor south - 14:45:51 - 20s
- Raptor vertical - 17:56:30 - 130s / 2m10s
Total tests: 8
Total fire time: 380s / 6m20s
-Raptor vertical: 260s / 4m20s - 2 tests
-Raptor south: 120s / 2m - 6 tests
August 1st
- Raptor vertical - 08:36:07 - 130s / 2m10s
- Raptor south - 10:06:29 - 20s
- Raptor south - 10:06:56 - 20s
- Raptor south - 10:07:22 - 2s
- Raptor vertical - 14:16:43 - 170s / 2m50s
- Raptor vertical - 20:12:19 - 190s / 3m10s
Total tests: 6
Total fire time: 532s / 8m52s
-Raptor vertical: 490s / 8m10s - 3 tests
-Raptor south: 42s - 3 tests
August 2nd
There were no Raptor tests today.
Weekly stats
Total tests: 28
Total fire time: 1254s / 20m54s
-Raptor vertical: 1090s / 18m10s - 18 tests
-Raptor south: 162s / 2m42s - 9 tests
-Raptor north: 2s - 1 test
