Connect with us

News

SpaceX eyes two Falcon 9 launches and a Starship hop in three days (Update: one day!)

All three of these SpaceX rockets could launch between August 29th and 31st. (Richard Angle; NASASpaceflight - bocachicagal)

Published

on

Update: In a surprise twist, SpaceX has confirmed plans to launch SAOCOM 1B, Starlink-11, and hop Starship SN6 in less than ten hours on August 30th.

Contingent upon a ULA Delta IV Heavy launch on August 29th, Starlink-11 is scheduled to lift off on a Falcon 9 rocket no earlier than (NET) 10:12 am EDT (UTC-4), followed by SAOCOM 1B on a separate Falcon 9 NET 7:18 pm EDT (UTC-4). Simultaneously, SpaceX is currently working towards a second full-scale Starship hop test between 8 am and 8 pm CDT (UTC-5) on Sunday, August 30th.

Pending an August 29th mission from competitor ULA, SpaceX aims to attempt two orbital Falcon 9 launches and a Starship hop test over the course of just a few days.

A United Launch Alliance (ULA) Delta IV Heavy rocket was originally scheduled to launch the secretive National Reconnaissance Office 44 (NROL-44) spy satellite on Wednesday before the customer requested a 24-hour delay and technical rocket bugs pushed the mission to no earlier than (NET) August 27th and now August 29th. Delta IV Heavy’s low cadence of one or two annual launches has traditionally made it hard for the rocket to launch on time, offering very few opportunities for the company to work the kinks out of the complex system.

ULA’s NROL-44 launch currently holds precedence over other missions scheduled around the same time, meaning that SpaceX has no choice but to delay its own launches every time the ULA mission slips. SpaceX has two launches currently in queue: Argentinian Earth observation satellite SAOCOM 1B was scheduled to launch NET 7:19 pm EDT (UTC-4) on August 28th, while SpaceX’s 11th Starlink v1.0 launch was expected to lift off NET 10:08 am EDIT (UTC-4) on August 30th. Simultaneously, a SpaceX Starship prototype is tracking towards its first short hop somewhere in between those orbital launches. ULA’s second NROL-44 delay has thrown both SpaceX launch dates somewhat up in the air, however.

SpaceX encapsulated SAOCOM 1B in Falcon 9’s payload fairing earlier this month. (CONAE)

Starship SN6 Flight 1

Recent delays to SpaceX’s East Coast launches have pushed the company’s second full-scale Starship hop test to the front of the line. Starship serial number 6 (SN6) is currently scheduled to attempt its first 150m (~500 ft) hop as early as Saturday, August 29th. Coming less than four weeks after Starship SN5 became the first full-scale prototype to successfully lift off (and land) on August 4th, a second successful hop – with an entirely different Raptor engine and Starship prototype – would be an extraordinary feat.

Meanwhile, SpaceX is simultaneously inspecting and repairing the hop-proven Starship SN5 prototype – most likely with the intention of flying the ship again in the near future. According to CEO Elon Musk, SpaceX’s current goal is to perform “several” fast-paced Starship hop tests to streamline the new rocket’s launch operations. The August 29th window for SN6’s 150m hop lasts from 8am to 8pm and the rocket could attempt to lift off as early as 10am to noon.

Starship SN6 completed a cryo proof test and Raptor static fire on August 16th and August 23rd. (LabPadre)

SAOCOM 1B

Sister to the SAOCOM 1A satellite SpaceX launched from California in October 2018, SAOCOM 1B is more or less identical. Notably, however, it will launch from Florida – the first polar launch planned from the US East Coast in half a century. The reason the United States effectively retired the Eastern polar launch corridor is a bizarre story of Cold War tensions gone awry but the gist is that SpaceX’s Falcon 9 rocket will ‘dogleg’ midflight, changing its trajectory to avoid overflying populated regions.

Originally scheduled to launch as early as March 30th, the Argentinian satellite has been relentlessly delayed by coronavirus-related restrictions and technical delays. SAOCOM 1B’s Falcon 9 booster was even swapped amidst the delays, switching from B1051 to B1059 as SpaceX strove to fill the gap in its manifest with internal Starlink missions. Now, NROL-44’s technical launch delays have pushed the Falcon 9 mission from August 27th to NET 7:19 pm EDT (UTC-4) on Sunday, August 30th.

Advertisement
-
-

SAOCOM 1B will be SpaceX’s first return-to-launch-site (RTLS) booster landing since March 2020.

Falcon 9 B1059 – now scheduled to launch SAOCOM 1B – last returned to port on June 16th after launching Starlink-8. (Richard Angle)

Starlink-11

Finally, prior to NROL-44’s 72-hour slip, SpaceX’s 11th Starlink v1.0 mission and 12th Starlink launch overall was scheduled NET Sunday, August 30th. ULA’s delays have added considerable uncertainty, at one point pushing Starlink-11 to a tentative September 1st NET before the launch date (rather oddly) slipped back into late-August. Assuming SpaceX still has to wait for ULA, the most likely alternative is August 31st, given that August 30th would necessitate two launches in less than ten hours.

SpaceX completed its first operational US military Falcon 9 launch with booster B1060 on June 30th. (Richard Angle)
B1060 completed its first recovery on July 4th. (Richard Angle)

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots

Published

on

Credit: Tesla

Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.

Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.

However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.

With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.

Turning Hesitancy, Inaccuracy

I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.

Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.

I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.

FSD Disregards Manual Turn Signals

This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.

If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.

FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.

This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.

This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.

Bird Braking is a Thing of the Past

The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.

There have been zero issues with this so far in v14.3.6, which is an excellent improvement.

FSD Might Already Be Taking Note of Driver Preferences

Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.

This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.

Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.

Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.

It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.

As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.

Continue Reading

Elon Musk

Musk’s massive Terafab project will get final location soon

Published

on

Credit: SpaceX

Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.

“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.

Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry

Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.

The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.

In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.

However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.

Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.

Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.

“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”

He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”

Continue Reading

News

Elon Musk reveals SpaceX performed secret Starship test on Flight 13

Published

on

Credit: SpaceX

SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.

Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.

All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.

However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.

Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:

SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.

Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.

The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.

Continue Reading