News
Firefly launches world’s largest carbon fiber rocket into orbit on second try
Firefly Aerospace’s Alpha rocket has successfully reached orbit on its second try, cementing the company as the victor of a mostly unintentional race between three American NewSpace startups.
After weeks of delays and three aborted launch attempts on September 11th, 12th, and 30th, the second carbon-fiber Alpha rocket lifted off from its Vandenberg Space Force Base (VSFB) SLC-2W launch pad at 12:01 am PDT (07:01 UTC) on October 1st. According to Firefly, the resulting mission was a “100%…success”, indicating that it achieved all of the company’s objectives – an outcome far from guaranteed on the second flight of any orbital rocket.
In a familiar display, Alpha’s suborbital booster lifted the upper stage, fairing, and payload most of the way out of the Earth’s atmosphere within a few minutes. After a mechanical system pushed the two stages apart, the upper stage successfully ignited its lone Lightning engine, ejected the two-piece fairing (nose cone) protecting its payloads, and continued uphill for another five minutes before reaching a stable parking orbit around 250 kilometers (~160 mi) above Earth’s surface.
After successfully reaching orbit, Alpha’s upper stage even made it through a more than 90-minute coast phase and reignited for a brief second burn. Finally, Alpha managed to deploy all seven of the satellites it lifted off with. As a test flight, there was no guarantee that those payloads would end up anywhere other than the Pacific Ocean, so the successful deployment was likely a very pleasant surprise for all satellite operators involved in the mission.
Nicknamed “Into The Black” by Firefly, it was the company’s second Alpha flight and followed an unsuccessful attempt on September 3rd, 2021. During the rocket’s first launch, a loose cable caused one of its booster’s four main Reaver engines to fail almost immediately after liftoff, dooming the attempt. However, the rest of the booster fought for more than two minutes to keep the mission on track before a termination system destroyed the rocket, demonstrating otherwise excellent performance and gathering invaluable data and experience.
Firefly wasted no time putting that experience to good use. Compared to the first vehicle, the booster and upper stage for Alpha’s second flight sailed through preflight testing and completed their respective proof tests (a combined wet dress rehearsal and static fire) on their first tries. That smooth processing bodes well for the timing of Firefly’s third Alpha launch, although the company’s official accounts have strangely been almost silent after Flight 2’s success.
Soon after launch, third-party data showed that Alpha deployed its seven payloads into a 210 x 270 kilometer (130 x 170 mi) orbit. Firefly’s official launch page had stated that the target orbit was 300 kilometers (~185 mi) and called the second ignition of the upper stage a “circularization burn.” Given that the final orbit is far from circular and has an apogee a full 10% below that stated target, it wasn’t clear the rocket had performed exactly as expected. The orbit’s very low perigee means that the customer satellites Alpha deployed could reenter Earth’s atmosphere and burn up after a matter of weeks in space, rather than months or years.
But according to Bill Weber, who became CEO of Firefly less than a month before the launch, Alpha “deployed [Firefly’s] customer payloads at exactly the spot [the company] intended,” strongly implying that the strange final orbit was intentional.
Additionally, official footage Firefly released after the launch suggests that Alpha’s upper stage Lightning engine nozzle narrowly missed the booster’s interstage during stage separation. Had the drifting booster hit that nozzle, it would have likely caused the upper stage to begin tumbling and potentially ended the mission well before orbit. Thankfully, it didn’t, and it should be relatively easy to fix whatever caused the Alpha booster to begin slipping sideways so quickly after separation.
Alpha is the largest all-carbon-fiber rocket ever built. It stands 29.5 meters (~95 ft) tall, 1.8 meters (6 ft) wide, weighs 54 tons (~120,000 lb) fully fueled, and can produce up 81 tons of thrust (~180,000 lbf). Alpha can launch up to 1.17 tons ~(2600 lb) of useful cargo to low Earth orbit (LEO), making it the first successful entrant in a new and rapidly growing field of privately-developed rockets designed to launch 1-2 tons to orbit.
Coincidentally, Firefly found itself neck and neck with two other prospective US providers, Relativity Space and ABL Space. For several months, all three companies were aiming to successfully launch their one-ton-class rockets to orbit sometime in the late summer or early fall. But despite delays, Firefly – already more than a year ahead after its first launch attempt in 2021 – still beat Relativity and ABL Space to flight and did so successfully, securing itself a small but significant milestone in the history of private spaceflight.
The timeline for Relativity’s first 3D-printed Terran-1 rocket launch is no longer clear after a hurricane disrupted its preflight test campaign. ABL Space, meanwhile, has been forced to sit with its first RS1 rocket ready to launch for weeks while waiting on the FAA to complete paperwork and grant it a launch license. Had the FAA moved faster, it’s entirely possible that ABL Space could have launched before Firefly’s Alpha Flight 2, although the odds of success are much lower for RS1 during its debut. Pending that regulatory approval, ABL Space intends to launch RS1 out of Kodiak, Alaska as early as mid-October.
Firefly has yet to offer a substantial statement after the successful launch, which means that the company has provided no information about its next steps or next launch. Per prior statements, the company is working to upgrade its Texas factory to enable up to six Alpha launches in 2023.
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
