News
Musk shares timelapse of SpaceX Falcon Heavy being raised for launch prep
Elon Musk reiterated SpaceX’s commitment to completing the inaugural launch of Falcon Heavy before the end of January 2018 in a series of Instagram and Twitter posts. Delays with the companies commercial launch of the secretive Zuma payload will likely push Heavy back a similar number of days, but SpaceX still has a solid four weeks until February to prepare the vehicle and complete its more pressing commercial queue of launches.
Up next for Falcon Heavy will be the massive rocket’s first-ever integrated static fire, which will see all 27 of its Merlin 1D engines ignite for a brief several seconds in order to test a number of procedures and validate models of the rocket’s design and operations. Most importantly, in order to counteract the immense and potentially destructive torque produced by the simultaneous startup of 27 rocket engines, the first static fire will test a staggered ignition of all first stage engines, so as to spread out the force exerted upon the vehicle’s octawebs and booster connections. Musk’ Jan. 4 Instagram post points towards a static fire “next week,” sometime between January 8-15. The launch of Zuma is clearly the company’s main priority, at the moment.
https://www.instagram.com/p/BdjBHqdAIzs/?taken-by=elonmusk
- Falcon Heavy’s three boosters and 27 Merlin 1D engines on full display. (SpaceX)
- Falcon 9’s octaweb is shown exposed here in all its hunk-of-raw-metal glory. Falcon Heavy’s center octaweb is even beefier. (SpaceX)
- Elon Musk’s Roadster seen before being encapsulated in Falcon Heavy’s massive payload fairing. Below the Tesla is the payload adapter, which connects it to the rocket. (SpaceX)
Preceding this static fire, SpaceX will necessarily conduct a wet dress rehearsal (WDR) in which Falcon Heavy’s three first stages and single second stage will be fully loaded with supercooled high-grade kerosene (known as RP-1) and liquid oxygen. If this procedure fails to produce any unwanted surprises or insurmountable bugs, it’s probable that the WDR flow will transfer smoothly into static fire procedures. If bugs are found, the vehicle may instead be detanked of its propellant load and rolled back to LC-39A’s integration facilities in order to analyze those issues and ensure vehicle safety and readiness. Similar analysis will undoubtedly occur after the first static fire to verify that Falcon Heavy is still flight-worthy and its Tesla Roadster payload is in good condition.
After several barrages of thorough tests, the launch pad and vehicle will be ready for Falcon Heavy’s inaugural launch, no earlier than late January 2018. In the meantime, antsy fans can bask in the beauty of a timelapse Elon Musk recently posted, showing Falcon Heavy being lifted into a vertical orientation during its first pad-fit checks several days ago.
Falcon Heavy goes vertical pic.twitter.com/uG1k0WISv1
— Elon Musk (@elonmusk) January 5, 2018
Meanwhile, SpaceX is still tracking towards the imminent launch of Zuma, a secretive satellite payload that will see Falcon 9 return to Landing Zone 1 at Cape Canaveral. The mission has been delayed 48 hours from its original NET, and is now tentatively aiming to launch no earlier than (NET) January 6, but as of just a few minutes ago, SpaceX officially confirmed that additional propellant loading tests had been conducted with Zuma’s Falcon 9 booster earlier today, pushing the launch to NET January 7th, 8pm EST.
Team at the Cape completed additional propellant loading tests today. Extreme weather slowed operations but Falcon 9 and the Zuma spacecraft are healthy and go for launch—now targeting January 7 from Pad 40 in Florida.
— SpaceX (@SpaceX) January 5, 2018
Follow along live as our launch photographer Tom Cross braves the Florida cold and launch delays in pursuit of glorious rocket pics over the next several days.
News
Tesla Robotaxi will be a 24/7 service: here’s when
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.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
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.
News
Tesla Cybercab launch catches NHTSA’s attention who wants to know more
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.

Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.


