News
DeepSpace: Firefly set for smallsat industry’s second place trophy, Rocket Lab leads the pack
This is a free preview of DeepSpace, Teslarati’s new member-only weekly newsletter. Each week, I’ll be taking a deep-dive into the most exciting developments in commercial space, from satellites and rockets to everything in between. Sign up for Teslarati’s newsletters here to receive a preview of our membership program.
In the race to a field dedicated smallsat launch vehicles, New Zealand startup Rocket Lab has already won first place, a fact that has been discussed several times in past Deep Space issues. After completing its first launch of 2019 on March 28th, Rocket Lab’s Electron rocket is ready for another mission as early as May 4th, a good sign for the company’s planned monthly launch cadence.
Despite Rocket Lab’s major success, there is plenty of room for additional competitors and/or complementary vehicles. Electron’s maximum payload hovers around ~225 kg (500 lb) to low Earth orbit (LEO), limiting its usefulness for any payloads that are larger than truly tiny satellites or in need of higher orbits. Also discussed on DeepSpace, there are 10+ serious startups with funding and hardware in work attempting to build said smallsat launch vehicles, ranging from the extremely tiny (Vector: 60 kg to LEO) to much larger rockets from companies like Relativity, ABL Space, and more. Firefly Space, however, is the startup that has arguably broken away from the pack in the last few months, firmly setting itself up to be second in line behind Rocket Lab.
Build, test, qualify
- Firefly’s major leaps forward came in December 2018 and then April 2019, both related to testing the completed upper stage of the company’s Alpha rocket.
- In December, the upper stage ignited for the first time. In April, the same upper stage successfully performed a mission-duration static fire that lasted a full 300 seconds (five minutes), the same length required for a rocket to reach orbit after separating from Alpha’s first stage.
- For any launch vehicle development program, the first successful mission-duration test fire of an integrated rocket stage is arguably one of the most important milestones, second only to the same hardware’s inaugural launch.
- Simultaneously, Firefly began integrated testing of the thrust section and Reaver engines that will be the basis of Alpha’s first stage. The rocket’s Lightning second stage engine has been tested extensively at this point in development, although the stage’s lone engine produces a maximum of ~70 kN (~16,000 lbf) of thrust.
- The booster’s four Reaver engines will each produce ~170 kN (55,000 lbf) of thrust, around three times as much as Lightning. Alpha’s second stage is critical, but its first stage is arguably far more complex.
- Despite the relative power differential, it’s still worth noting that Alpha’s entire first stage (736 kN/166,000 lbf) will be significantly less powerful than a single one of Falcon 9’s nine Merlin 1D engines (941 kN/212,000 lbf).
- Although Alpha is far smaller than rockets like Falcon 9 or Atlas V, it will nominally be capable of launching 1000 kg to an altitude of 200 km (LEO) or ~650 kg to a 500-km sun-synchronous orbit (SSO). This translates to around 4.2X the performance of Rocket Lab’s Electron at 2.5X the cost per launch ($15M vs $6M).
- Assuming no payload capacity is wasted, Alpha could thus be almost 50% cheaper than Electron when judged by cost per kilogram to orbit.
- Of course, this comparison ignores the fact that Firefly will have to far more heavily rely on booking co-passenger satellites to keep Alpha launch prices competitive with Electron.
- If exactly 1000kg or 630kg of cargo can’t be booked each launch, the expendable Alpha’s $15M launch cost will be distributed over less payload, raising costs for each customer. In other words, the competitive advantages of Alpha are almost entirely associated with its ability to launch payloads outside of Electron’s capabilities, as are its potential weaknesses.
Firefly Alpha’s upper stage qualification article (top) and a comparison of a variety of launch vehicles. (Teslarati)
The sweet spot
- In theory, Firefly Alpha’s could find itself in a relatively sweet spot, where the rocket’s launch costs are not so high that dedicated rideshare missions become intractable (i.e. Spaceflight’s SSO-A launch on Falcon 9) but its payload performance is still good enough to provide access to a huge swath of the space launch market.
- Firefly also has plans to develop a heavier launch vehicle based on Alpha, known as Beta. Conceptually equivalent to SpaceX’s Falcon Heavy, Beta would use three Alpha boosters and a significantly upgraded second stage and would be able to launch 4000 kg to LEO or 3000 kg to SSO.
- Regardless of Firefly’s grander aspirations, Alpha is poised to capitalize on the simple fact that it will be the second commercially viable smallsat launch vehicle to begin operations. Alpha’s first orbital launch attempt could occur as early as December 2019, although slips into early 2020 are to be expected.
- At that point, Rocket Lab’s Electron will be the only serious competition on the market. Relativity’s Terran and ABL Space’s RS-1 rockets plan to offer a competitive ~1250 kg to LEO or ~900 kg to SSO, but their launch debuts are tentatively scheduled no earlier than late 2020.
- If Alpha’s development continues smoothly, Firefly could easily have a solid 12-month head start over its similarly-sized competitors,
- Up next for Alpha is a similar campaign of tests focused on the first integrated booster, including tests fires and an eventual mission-duration qualification test.
Mission Updates
- SpaceX’s CRS-17 Cargo Dragon resupply mission has slipped an additional four days from April 30th to May 3rd (3:11 am EDT, 07:11 UTC) after the International Space Station (ISS) began suffering serious (but non-threatening) electrical issues. Additional launch delays could follow if the issue is not resolved in the next few days.
- The first operational Starlink launch remains firmly on track for NET mid-May. According to SpaceX, all Flight 1 satellites are already in Florida, while the FCC approved the company’s modified constellation license – permitting Starlink operations after launch – on April 26th.
- Due to CRS-17’s launch delays, the availability of SpaceX’s LC-40 pad will now likely be the main limiting factor for the Starlink-1 launch date.
- SpaceX’s second West Coast launch of 2019 – carrying Canada’s Radarsat Constellation – is now expected to occur no earlier than mid-June and will reuse Falcon 9 B1051.
- SpaceX’s launch of Spacecom’s Amos-17 spacecraft is now scheduled no earlier than July. Falcon Heavy Flight 3 is tentatively scheduled for launch as early as June 22 – all three boosters should be on site in Florida within the next week or two.
Photo of the Week:
(SpaceX)
The third Falcon Heavy center core – believed to be B1057 – was spotted eastbound in Arizona on April 16th. On April 26th, SpaceX confirmed that the booster completed its acceptance static fire test at the company’s McGregor, TX facilities, a sure sign that all of Falcon Heavy Flight 3’s major components should be in Florida within the next few weeks.
We’ll see you next week.
Not a member? Become a member today to receive DeepSpace each week!
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Elon Musk
SpaceX issues statement on Starship V3 Booster 18 anomaly
The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX’s initial comment
As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.
“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X.
Incident and aftermath
Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.
Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
