Update: SpaceX says it and NASA are moving forward with plans to launch a Crew Dragon carrying US, Japanese, and Russian astronauts as early as noon EDT (16:00 UTC) on Wednesday, October 5th.
Concurring with a statement made on October 3rd, SpaceX has also called off a planned October 4th launch of its Starlink 4-29 mission. However, the company has delayed Starlink 4-29 just 24 hours and says that Falcon 9 will launch the latest batch of internet satellites out of California no earlier than (NET) 4:10 pm PDT (23:10 UTC) on October 5th. Intelsat has also confirmed that its Galaxy 33 and Galaxy 34 geostationary communications satellites are scheduled to launch on a Falcon 9 rocket as early as 7:07 pm EDT (23:07 UTC) on October 6th, leaving SpaceX on track to launch three Falcon 9 rockets from three launch pads in 31 hours.
The company achieved a similar feat earlier this year when it launched three Falcon 9 rockets in 36 hours. Three launches in 31 hours would break that record.
SpaceX is on the cusp of launching three Falcon 9 rockets in a handful of days. Minor issues with two of the three missions, however, have complicated the already hard process of coordinating so many launches at the same time.
For many reasons, rocket launches are an inherently difficult thing to schedule, and that difficulty only gets magnified when attempting to launch rockets as quickly as possible for customers with very different needs while using a fixed number of launch pads. SpaceX’s upcoming series of launches demonstrates the slippery nature of high-cadence rocket launch scheduling better than most.
Last month, SpaceX ran into issues (mainly bad weather) that delayed its Starlink 4-34, 4-35, and 4-36 missions by varying degrees. Before those delays, SpaceX had intended to break its LC-40 pad turnaround record with Starlink 4-35 and then repeat the feat with Starlink 4-36, but that opportunity closed when Starlink 4-34’s several weather delays pushed Starlink 4-35 from September 19th to the 24th and raised the risk of the next launch, Starlink 4-36, interfering with customer missions planned in the first half of October.
That burst of customer missions, all of which take priority over SpaceX’s own Starlink missions, meant that a few-day delay for a mission two launches prior ultimately pushed Starlink 4-36 from the end of September to no earlier than October 20th. It will launch out of Cape Canaveral Space Force Station’s (CCSFS) LC-40, the same pad that launched Starlink 4-35 on September 24th and will launch Intelsat’s Galaxy 33 and 34 satellites no earlier than (NET) October 6th and Eutelsat’s Hotbird 13F satellite NET October 13th. All four launches (including Starlink 4-36) are thus contingent upon each other, so a delay with one mission would likely delay each subsequent mission to leave enough time for pad turnaround and rocket processing.
Date Mission Rocket Location Pad 10/04/22 Starlink 4-29 Falcon 9 California VSFB SLC-4E 10/04/22 SES-20/21 Atlas V Florida CCSFS LC-41 10/05/22 Crew-5 Falcon 9 Florida KSC LC-39A 10/06/22 Galaxy 33/34 Falcon 9 Florida CCSFS LC-40 10/13/22 Hotbird 13F Falcon 9 Florida CCSFS LC-40 10/20/22 Starlink 4-36 Falcon 9 Florida CCSFS LC-40
SpaceX isn’t the only company that launches out of Cape Canaveral, Florida. Originally scheduled in late September, the United Launch Alliance’s (ULA) Atlas V launch of the SES-20 and SES-21 geostationary communication satellites was delayed by the same weather system that indirectly hampered Starlink 4-35 and 4-36. That mission is now set to launch NET 5:36 pm EDT (21:36 UTC) on October 4th.
Up first, however, is SpaceX’s Starlink 4-29 mission out of California’s Vandenberg Space Force Base (VSFB). Delayed to October 4th hours before its October 3rd target, the new schedule will give SpaceX “more time for pre-launch checkouts,” Falcon 9 will now lift off as early as 4:48 pm PDT (23:48 UTC), a little over two hours after Atlas V. However, making the whole situation even more interlinked, SpaceX says it will stand down from its October 4th Starlink launch attempt if its next Florida mission – Crew Dragon’s fifth operational NASA astronaut launch – remains on track for its current noon EDT (16:00 UTC), October 5th launch target.
In an October 3rd briefing following a mostly clean launch readiness review (LRR), NASA and SpaceX officials revealed that three new minor issues – “not showstoppers” – had appeared after a busy period of ground testing. An otherwise successful astronaut dry dress rehearsal and a subsequent wet dress rehearsal and static fire uncovered a possible fire extinguisher leak in the Dragon spacecraft and a minor issue with one of the Falcon 9 rocket booster’s nine Merlin 1D engines. A communications issue was also discovered on the SpaceX drone ship Crew-5’s rocket booster is meant to land on in the Atlantic Ocean.
SpaceX and NASA officials weren’t especially worried about the issues and were confident they would be resolved in time for an October 5th launch. If they aren’t and Crew-5 slips to October 6th, SpaceX should be able to launch Starlink 4-29 on October 4th, but then it’s unclear if the company will also be able to launch Intelsat’s Galaxy 33 and Galaxy 34 geostationary communications satellites on the same day as Crew-5. Galaxy 33/34 is scheduled to launch NET 7:07 pm EDT on October 6th, likely ~6 hours after Crew-5’s own October 6th launch window.
If Crew-5 slips and Galaxy 33/34 can’t launch on the same day, it would likely delay both Hotbird 13F and Starlink 4-36. It’s also unclear if Starlink 4-29 can launch on the same day as Crew-5 if it flies after Dragon. Either way, SpaceX could potentially end up launching Crew-5, Galaxy 33/34, and Starlink 4-29 on October 5th and 6th – potentially less than a day and a half apart.
As SpaceX continues to push the limits of what is possible with its existing Falcon launch and landing infrastructure, chaotic scheduling situations like this, where small issues impact large strings of launches, will become the norm instead of the exception
Elon Musk shed more details on the upcoming improvements to Tesla’s Full Self-Driving suite, specifically one that the CEO mentioned last week, which should help owners see fewer interventions.
Last week, Musk hinted that one major improvement that Tesla planned to roll out to Full Self-Driving users was the car’s ability “to remember your specific interventions and match each person’s individual preferences.”
Elon Musk says your Tesla will start to learn your individual preferences
This small bit of detail was linked to a post from Tesla community member Whole Mars, who said that FSD’s tendency to exit the carpool lane, a feature that owners can turn on but at times the car will disregard.
It sounds like, based on Musk’s two responses since that original post, it is safe to say the things FSD will start to remember are wide-ranging. However, it seems the biggest differences will be noticed with parking performance, which Musk continues to mention.
Highway Lane Preferences
The initial post Musk mentioned, with these new remembered preferences soon to arrive for Tesla owners everywhere, was the Carpool/Express Lane.
Tesla has a setting in the FSD menu that lets drivers enable HOV Lane travel. However, the car won’t always stay in that suggested or preferred lane.
The car will start to remember your specific interventions and match each person’s individual preferences
— Elon Musk (@elonmusk) July 18, 2026
Some owners have also complained of left lane camping, an illegal maneuver in at least some states. Cruising in the passing lane has resulted in tickets for some, as it is illegal in over 30 states in the U.S.
Tesla did not confirm if these preferences would also be included in new FSD behaviors, but it would certainly help move the company toward fewer interventions.
Parking Preferences
This seems to be the real focus of the entire operation, as Musk stated several weeks ago that parking was overwhelmingly the most frequent reason for interventions.
The major issue with parking is not necessarily the parking “performance,” as FSD is generally good at parking. It definitely has its issues; we’ve recorded plenty of them, including this one as recent as last week:
Yeah it seems like FSD v14.3.5 is having some issues with parking early on https://t.co/Bw5ULfVmDq pic.twitter.com/RHdpjOEpIo
— TESLARATI (@Teslarati) July 13, 2026
However, the changes coming are more about preferences, meaning where you park and how your car enters the spot, either pulling in or backing in. Owners have also reported that pulling into the correct driveway is a relatively rare thing for FSD, something else that needs to be confronted.
Musk basically confirmed that all of these things would be part of Tesla’s plan to address driver preferences with FSD:
Yes
— Elon Musk (@elonmusk) July 20, 2026
It’s obvious there is something big coming with FSD, and the company’s focus seems to be eliminating any intervention that would be related to preferences. This is probably the biggest bottleneck between Tesla and being fully autonomous. Critical interventions do occur, but they are much less frequent.
The only time a driver should be taking over is because of a critical intervention; this seems to be the goal of Tesla right now.
This all seems to be a priority as Tesla continues to move closer to the prospect of unsupervised driving.
Elon Musk said today on X that Teslas will start to learn your individual preferences. This is something that he seemed to hint toward earlier this month when he said parking was by far the biggest reason drivers intervene with Full Self-Driving.
Musk made the comment in response to notable Tesla influencer Whole Mars, who said that his vehicle will sometimes disobey the settings he has enabled for his car. He responded to the post, stating that “The car will start to remember your specific interventions and match each person’s individual preferences.”
The car will start to remember your specific interventions and match each person’s individual preferences
— Elon Musk (@elonmusk) July 18, 2026
This is something that could be perhaps one of the biggest ways Tesla could minimize or even work closer toward eliminating interventions altogether. While FSD does a lot of things really well, many people intervene a vast majority of the time not due to major or critical safety errors.
Instead, many take over because the car is doing something that they do not like as a preference; it might park in a parking spot that is not preferred by the driver, it might linger too long in the left lane on the highway (a personal favorite), or it could even take a route that the driver does not like.
These all lead to interventions, but they are not triggered by a major safety issue. Instead, it’s just preference.
READ OUR REVIEW OF TESLA’S LATEST FSD VERSION:
Tesla Full Self-Driving v14.3.5 Early Impressions: new features and early performance
If Teslas could start to learn the personal preferences of the person who owns them, interventions will truly begin to be less frequent. Some of this is already pretty evident, in my opinion. Teslas use a neural network to learn behaviors and accumulate data to improve performance.
For months now, we’ve tracked FSD’s performance at “Except Right Turn” stop signs, something that is very common in Pennsylvania, but many of our readers located in other parts of the U.S. have never heard of. FSD handles one Except Right Turn stop sign very well, one that I travel past frequently. Others that I do not navigate through as often do not have as confident a performance. It seems like the cars might already be doing this to an extent.
🚨 Tesla Full Self-Driving v14.3 proceeds through an Except Right Turn Stop Sign pic.twitter.com/YemRSlens7
— TESLARATI (@Teslarati) April 8, 2026
That example is also for something that is a street sign and not necessarily a driver preference; however, I still feel it is worth mentioning because it only handles that commonly passed Except Right Turn stop sign with true confidence. Others it still seems to struggle with.
This could be one of Tesla’s big moves toward full autonomy, and it could be a pathway to truly unsupervised driving. Every day, millions of cars on the road travel at a human driver’s personal preferences with no incident. Why can’t autonomous vehicles still cater to a passenger’s preferences while being autonomous? Tesla seems to have the idea that it would be possible.
Florida Governor Ron DeSantis has sharply criticized legacy media outlets for what he describes as selective and biased reporting on vehicle accidents involving Tesla. In a recent X post, DeSantis questioned why headlines routinely spotlight the Tesla brand in crash stories, even when human error is the clear cause, while similar incidents with other automakers often receive generic treatment.
A prime example is the June 19, 2026, fatal crash in Katy, Texas. A Tesla Model 3 driven by Michael Butler struck a brick home at high speed, killing 76-year-old Martha Avila inside. Initial reports and headlines prominently featured “Tesla crash” and referenced the driver’s claim that an automated driving-assistance system was engaged.
Many outlets quickly speculated that Full Self-Driving or Autopilot were the cause of the crash, immediately blaming the suites for the accident shortly after it happened.
However, Tesla responded shortly after the accident with vehicle data that showed Butler manually overrode the system by pressing the accelerator to 100 percent, reaching 73 MPH in a residential area, more than double the speed limit. The accelerator remained floored after impact.
Tesla finally clarifies fatal Texas crash, confirms driver manually overrode acceleration
The National Transportation Safety Board (NTSB) later confirmed these findings, and Butler now faces manslaughter charges. His phone searches also included queries like “Tesla FSD too timid,” suggesting he may have intervened aggressively. Despite this, many headlines continued to center Tesla’s technology rather than the driver’s actions.
DeSantis highlighted a Washington Post headline, which was labeled, “Newly released photo shows wreckage of Tesla crash that killed grandmother.”
Do legacy media outlets typically use headlines involving the make of a car in a crash or is that only for Tesla?
It would be one thing if the self-driving malfunctioned but the crash was purely human-induced.
Seems like these outlets want to associate Tesla with crashes as… pic.twitter.com/EmfyeYiuv6
— Ron DeSantis (@RonDeSantis) July 17, 2026
The subheadline noted the driver overrode assistance and floored the accelerator, yet the brand name dominated the framing. He asked whether legacy outlets typically name the make of a car in routine crashes or reserve that treatment for Tesla to push a narrative.
This pattern appears widespread. Crashes involving Ford, Chevrolet, or Toyota vehicles frequently appear as “pickup truck slams into home” or “fatal car crash kills pedestrian” without brand specifics, especially absent new technology angles.
High-profile Ford F-150 or Chevy Silverado incidents tied to large sales volumes often escape brand-callout scrutiny. In contrast, Tesla stories consistently lead with the manufacturer, amplifying perceptions of risk despite data showing strong overall safety performance:
🚨 Why do Tesla Owners get so defensive over the narrative of crashes involving Teslas? https://t.co/aX7ogtjTCR pic.twitter.com/KO4QWaLOKl
— TESLARATI (@Teslarati) June 24, 2026
Tesla’s own 2025 Impact Report indicates vehicles using FSD logged 0.19 major incidents per million miles, roughly eight times fewer than the U.S. average. Models like the Model Y also rank among the safest in IIHS and NHTSA testing for occupant protection. Critics argue disproportionate coverage ignores these statistics and driver behavior factors, such as younger or more aggressive Tesla owners in some studies.
DeSantis frames this as part of a broader political agenda against innovative American companies like Tesla. By consistently naming Tesla while downplaying others, media outlets risk eroding public trust and shaping perceptions detached from the evidence of human error in most cases.
As autonomous technology evolves across the industry, consistent and factual reporting will be essential to separate real safety concerns from narrative-driven coverage.
Elon Musk sheds details on Tesla FSD’s upcoming improvements
Tesla Diner is throwing a birthday party with a Franz-signed special treat
