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
Tesla brought its innovative Cybercab robotaxi to the National Federation of the Blind (NFB) Annual Convention in Austin, Texas, on July 3 at the JW Marriott Austin.
The hands-on demonstration highlighted the vehicle’s thoughtful design for blind and visually impaired users, underscoring Tesla’s commitment to inclusive autonomous mobility. Attendees, many using white canes or accompanied by service dogs, experienced the steering-wheel-free Cybercab firsthand.
Cybercab at the National Federation of the Blind’s Annual Convention in Austin for a hands-on experience of its accessibility features for blind or visually impaired customers⁰⁰For example:⁰– Braille lettering on physical controls
– Space for service animals & assistive… pic.twitter.com/8wrJcDHkw7— Tesla Robotaxi (@robotaxi) July 6, 2026
The showcase emphasized practical features tailored to the needs of the blind community. Braille lettering appears on physical controls, including door releases and emergency buttons, allowing users to navigate interfaces independently through touch. Generous interior space accommodates service animals and assistive devices such as canes, guide dogs, or mobility aids without compromising comfort.
Wheelchair-height seating facilitates easier transfers for users with additional mobility challenges. Photos from the event captured blind attendees approaching the vehicle confidently, service dogs relaxing inside, and hands exploring Braille-equipped handles.
Tesla Robotaxi’s official account detailed these elements, noting the Cybercab’s focus on accessibility, especially noting the Braille lettering and additional space for service animals.
How Tesla Will Transform Mobility for the Blind
Autonomous vehicles like the Cybercab promise revolutionary independence for the roughly 2.2 million visually impaired Americans. Traditional barriers—reliance on sighted drivers, costly paratransit, or limited public transit—often restrict spontaneous travel. Tesla Full Self-Driving aims to eliminate the need for a human operator, enabling on-demand, door-to-door rides via simple app hailing with voice guidance.
Users gain freedom to work, socialize, shop, or attend events anytime without scheduling hassles or safety concerns. This reduces isolation, boosts employment opportunities, and enhances quality of life, turning mobility from a dependency into true personal autonomy.
The NFB demonstration not only gathered valuable feedback but also generated excitement about a future where technology levels the playing field. By prioritizing inclusive design, Tesla advances a vision of transportation that serves everyone, potentially reshaping daily life for blind individuals and setting a standard for the autonomous industry.
As Cybercab deployment scales, these accessibility innovations could mark a significant step toward equitable mobility.
Investor's Corner
Tesla challenges startups to score a gig inside its most advanced European factory
Tesla is challenging startups to bring their best battery tech directly to Gigafactory Berlin.
Tesla has issued an open challenge to startups across Europe, inviting them to bring their best battery technology directly to the floor of Gigafactory Berlin. The program, called the JUNI x Tesla Battery Cell Giga Challenge, opened applications this month with a deadline of July 24, 2026, and is targeting startups with solutions that can make battery cell manufacturing faster, cheaper, safer, and more scalable at an industrial level.
The timing of the challenge is directly tied to Tesla’s most aggressive European battery investment yet. On May 12, 2026, Giga Berlin plant manager André Thierig announced a $250 million investment to scale the factory’s annual 4680 cell production capacity from 8 GWh to 18 GWh, more than doubling the previous target set just months earlier in December 2025. Thierig confirmed the expansion on X, saying the investment “will enable 18 GWh of annual 4680 cell production and create more than 1,500 new jobs.” Combined with a previously announced battery investment at the Grunheide site now approaches $1.2 billion.
Today, we announced a $ 250m investment for our Giga Berlin Cell factory. This will enable 18GWh of annual 4680 cell production and create more than 1500 new jobs. Good news during challenging times for the German industry. pic.twitter.com/ou4SWMfWh9
— André Thierig (@AndrThie) May 12, 2026
The challenge is looking specifically for startups with proven solutions across five categories: materials, equipment, operations, automation, and artificial intelligence. Applications are screened directly by Tesla’s cell manufacturing team in Grunheide, and the strongest submissions move through technical discussions, a pitch day in front of Tesla stakeholders, and potentially a paid pilot project with the cell team. Tesla is not looking for ideas at concept stage. The program requires applicants to demonstrate working prototypes, test data, or prior pilots before being considered.
The historical context matters here. Elon Musk first announced plans for what he called the world’s largest battery cell production facility alongside the Giga Berlin car factory back in 2020, targeting up to 250 GWh of annual capacity. Those plans were shelved in 2022 when Tesla shifted its battery investment focus to the United States to take advantage of Inflation Reduction Act incentives. The revival of cell production at Giga Berlin, now backed by over $1 billion in committed capital, represents a return to an ambition that was set aside for three years. As Teslarati has reported, the 4680 format is central to Tesla’s long-term cost reduction strategy across vehicles, energy storage, including the Tesla Semi and Cybercab.
By opening the challenge to outside startups, Tesla is acknowledging that reaching 18 GWh at Grunheide will require technology it does not currently have in-house, and it is willing to pay for the right solutions. For a startup in the battery supply chain, a paid pilot with Tesla’s European cell team is as close to a direct commercial path as the industry offers.
A Texas man has been arrested and charged with manslaughter after his Tesla crashed into a home last month, striking a woman inside and killing her. The driver, Michael Butler, claimed the vehicle was in self-driving mode, but information from Tesla shows that Butler overrode the system.
Butler was arrested on Wednesday and booked at the Harris County, Texas, jail. He remained in custody through Thursday and Friday; he did not enter a plea, and his next court hearing is scheduled for Monday.
Tesla finally clarifies fatal Texas crash, confirms driver manually overrode acceleration
There are a handful of new clues in the case that could clear Tesla of any wrongdoing, especially as the woman who was killed’s family, the Avilas, filed a wrongful death lawsuit against Tesla and Butler, seeking at least $1 million in damages.
Charging documents from the Harris County prosecutor now show that Butler, who was working DoorDash the evening of the accident, had been using Full Self-Driving mode without incident through the duration of multiple deliveries that evening.
In the moments leading up to the crash, while in FSD and approaching a left turn, Butler pressed the accelerator pedal, overriding FSD’s speed control, and continued to push it until it reached 100 percent. This caused rapid acceleration; the brake pedal was never pressed, and there is no data to show that Butler aimed to turn away from the curb or house.
The charging documents state:
“I noted that the brake pedal was never pressed in the final minute before the crash. I also did not see any data to indicate that the driver attempted to turn away from the curb that he eventually struck. Further, I observed that no mechanical error was detected or recorded by the vehicle before BUTLER and the Tesla struck the curb.”
Additionally, a forensic analysis of Butler’s phone showed that he searched Google around the time of the crash with queries questioning why FSD was “too timid,” “not aggressive enough,” and even searched, “FSD is not aggressive enough for city driving.”
The documents outlined this:
“Investigator Veal also informed me that he had received BUTLER’s cell phone from Deputy Amad and that HDAO digital forensics team had completed a data extraction and download of the phone. Multiple Google searches related to Tesla had been made from BUTLER’s phone in the months leading up the crash. I noted multiple searches in May of 2026 indicating an apparent frustration with Tesla’s FSD mode, including the following searches: “Tesla fsd not aggressive enough 2026 model,” “Tesla fsd not [sic) aggressive enough 2026,” “FSD is not aggressive enough for city driving,” and “tesla fsd too timid.”‘
Tesla had claimed just after the crash that its internal data showed Butler had overridden the system’s speed control and pressed the accelerator completely, causing the vehicle to travel at an excessive rate of speed. Eventually, the car slammed into Avila’s house, killing her.
Butler has now been formally charged with Manslaughter, a felony.
Tesla flexes how it will help the blind with Cybercab
Tesla challenges startups to score a gig inside its most advanced European factory
