News
SpaceX settles on Thursday for first Falcon 9 launch of 2021
After a few days of delays, SpaceX appears to have settled on Thursday, January 7th for the first of several dozen Falcon 9 launches planned in 2021.
Originally scheduled to launch as early as January 4th, SpaceX’s Turksat 5A communications satellite launch was “placed TBD due to mission assurance” on January 1st – an unfortunate catch-all euphemism often used by launch providers in lieu of any real explanation for delays. Regardless, Next Spaceflight reports that Turksat 5A will be Falcon 9 B1060’s fourth launch, a milestone the first stage (booster) has reached just six months after its first flight.
Despite the minor delay, SpaceX’s current target of four launches this month is still well within reach even though the slip exemplifies the uphill battle the company will face as it aims to achieve CEO Elon Musk’s goal of 48 launches in 2021. Weather is currently 60% favorable for SpaceX’s first launch of the year and Turksat 5A is scheduled to lift off no earlier than 8:28 pm EST on January 7th (01:28 UTC, 8 Jan).
Good timing, too — the 45th said SpaceX’s next launch of Turksat was “placed TBD due to mission assurance.”— Emre Kelly (@EmreKelly) January 1, 2021
New forecast (60% favorable) and hazard area: pic.twitter.com/cEapdSd2DP— Emre Kelly (@EmreKelly) January 5, 2021
Unfortunately, SpaceX’s first launch of the new year has been steeped in unprecedented controversy for the company, including the first-ever instance of mass-protests at its Hawthorne, California factory and headquarters. The reason: Turksat 5A, while partially meant for civilian communications, will also support the Turkish military, which supported Azerbaijan after the country – unprovoked – reignited a long-simmering conflict in the Nagorno-Karabakh region in September 2020.
Stemming from events that transpired over the last several centuries, Armenian-Azeri conflict and Turkish involvement are extraordinarily complex and messy. In the 1910s and 1920s, Turkey (then the Ottoman Empire) infamously committed atrocities against Armenian, Assyrian, and Greek communities within its occupied territory in a process of “Turkification”, systematically killing 1-3 million people in what would ultimately be labeled genocide. In a separate but related conflict, Turkey eventually chose to support Azerbaijan’s claim to the ethnically (75-90%) and historically Armenian territory, backing the country against Armenia in the first Nagorno-Karabakh War in the 1990s.
Azerbaijan reignited the conflict in 2020, resulting in the deaths of at least 6000 combatants and civilians on both sides and ultimately securing a substantial portion of Nagorno-Karabakh territory as part of a November 2020 ceasefire agreement. To an extent, Nagorno-Karabakh’s borders are now more or less back to where they were before the first war in the 1990s. While an avoidable loss of life is inherently deplorable, it’s extremely difficult to say whether Azerbaijan was justified but it and Turkey’s history of systematic and discriminatory hostility towards Armenians leaves little benefit of the doubt worth giving.
Ultimately, that cloud of ambiguity makes it hard to directly fault SpaceX for choosing to launch Turksat 5A or for its contracts to launch Turksat 5B and future domestically-built satellites. Additionally, if SpaceX should be criticized for willingly launching the satellite, Airbus – contracted by Turkey to build Turksat 5A – is at least as worthy of critique but has yet to be included at all in protest discourse despite the fact that Turkey’s production contract was publicly announced in 2017.
In the history of spaceflight, a satellite that is completed but never launches is all but unheard of, as the inherent bureaucratic and financial inertia behind a launch campaign mere months away from its scheduled liftoff is obviously immense. Even if SpaceX were to accept major financial penalties and back out of its contract, Arianespace, Roscosmos, or ULA would assuredly accept any replacement contract.
For protestors still set on making an impact, the shrewd move would be to redirect attention on future Turkish satellite projects like Turksat 5B, 6A, and beyond with the intention of killing contracts in the cradle – a far more tenable goal.
Stay tuned for more launch details as SpaceX nears its first mission of 2021.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
