News
SpaceX’s Crew Dragon settles on Feb 9 launch debut as Falcon 9 nears static fire
Update: NASASpaceflight.com is reporting that ISS planning documents suggest that Crew Dragon’s first launch has slipped into the second half of February, perhaps February 16th.
In the midst of several confusing delays, schedule updates, and official statements, the orbital debut of SpaceX’s Crew Dragon spacecraft has made its way onto the Eastern range’s planning schedule for the first time, placing Falcon 9 B1051’s static fire and Crew Dragons launch no earlier than (NET) January 23rd and February 9th, respectively.
As the brand new spacecraft’s first attempted trip to orbit, the demonstration mission (Demo-1/DM-1) will be performed without crew aboard, allowing SpaceX and NASA an opportunity to fully verify performance and explore Crew Dragon’s capabilities without risking the lives of the astronauts that will step inside a nearly identical vehicle as early as June or July.
Obviously preliminary, but the Eastern Range is now showing the Static Fire for the DM-1 mission's Falcon 9 (B1051.1) as NET January 23, (and still showing NET February 9 as the launch date). As always, but especially this one, all very much subject to change. pic.twitter.com/EWOEpbpI9o
— NSF – NASASpaceflight.com (@NASASpaceflight) January 17, 2019
The US government has been shut down for more than four weeks as a consequence of the inability of elected representatives to pass and sign a funding bill, now the longest shutdown in the country’s history. As a result, more than 95% of NASA’s workforce has been furloughed, leaving around 800 people left working (without pay) across the agency in positions or groups deemed absolutely essential to avoid loss of life or property damage.
How NASA defines “essential” is unknown but it seemed improbable that the Commercial Crew Program – around six months away from actually launching astronauts and presently marked by NASA’s attempts to complete reams of approval and certification paperwork – would fall under that extremely narrow umbrella. Delays to Crew launches are unlikely to harm hardware or directly risk harm to astronauts, although a very tenuous case could be made that delays to the program now would snowball and cause the debut of operational crewed launches to slip so far into 2019 (or even 2020) that NASA could lose assured access to the International Space Station (ISS) for several months. Again, there is no obvious way that a slip like that would actually increase the risk to life or limb for astronauts and hardware/infrastructure.
Apparently, Demo-1 and 2 don't need FAA launch licenses (under auspices of NASA, like TESS launch. Post-certification missions will require FAA license, like CRS flights today
— Irene Klotz (@Free_Space) January 16, 2019
Despite the logical improbability that NASA’s Commercial Crew Program (CCP) would – at this point in time – remain operating at full capacity during an extended government shutdown, NASA provided a statement to The Atlantic earlier this week more or less implying that CCP was deemed essential and has continued to operate for the last several weeks. There is certainly some wiggle room in NASA spokesman Bob Jacobs’ comments, enough to make it ambiguous if they are primarily PR spin, frank honesty, or something in between.
A SpaceX spokesperson added [paraphrased by The Atlantic] that “if NASA made the call, the company would carry out the uncrewed [DM-1] launch”, a tactical nonanswer that redirects the impetus to NASA. It’s not clear if the people at NASA that would ‘make the call’ to launch are furloughed or not – they certainly would not be essential in the sense described by NASA’s own overview of the current shutdown’s impact. Originally targeting a launch sometime in mid to late January, an official NASA update posted on January 10th showed that Crew Dragon’s first launch had slipped into February (on the launch range for February 9th).
- DM-1 and Falcon 9 were greeted by an extraordinary – albeit mildly bittersweet – dawn during their first-ever trip out to Pad 39A. (SpaceX)
- The integrated DM-1 Crew Dragon ‘stack’ rolled out to Pad 39A for the first time in the first few days of 2019. (SpaceX)
- Falcon 9 B1051 and Crew Dragon vertical at Pad 39A. (SpaceX)
- Crew Dragon shows off its conformal (i.e. curved) solar array while connected to SpaceX’s sleek Crew Access Arm (CAA). (SpaceX)
- DM-2 astronauts Bob Behnken and Doug Hurley train for their first flight in Crew Dragon. (NASA)
“NASA and SpaceX are now targeting no earlier than February for the launch of Demo-1 to complete hardware testing and joint reviews.” – NASA, 01/10/2019
“Hardware testing” likely refers to the need for Falcon 9 to complete a static fire at Pad 39A, a test now scheduled for January 23rd. It’s ambiguous whether SpaceX can actually perform a static fire test – a complete launch rehearsal involving full propellant loads and the ignition of all nine Merlin 1D engines – at Kennedy Space Center, a NASA operated with federal funding that does not currently exist. Although the Air Force-helmed range is operating at a normal capacity, KSC must still perform a number of basic tasks ranging from infrastructure maintenance to roadblock setup to allow a static fire test – let alone a launch – to occur. I
f SpaceX completes its NET January 23rd static fire with no problems, then it would appear to be the case that some sort of SpaceX-side delay – perhaps augmented or slowed down by NASA operating at 5% capacity – caused the slip from mid-January to mid-February. Stay tuned to find out!
News
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.
The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.
TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.
Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.
Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.
TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.
This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.
This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.
However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.
Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.
Elon Musk
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.
The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.
A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”
Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.
This functionality will be there in about 3 months or so
— Elon Musk (@elonmusk) June 18, 2026
Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.
This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.
The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.
Musk teased that a similar feature was “coming” back in February:
Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says
It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.
Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.
Here’s an example of that from December:
🚨🏈 I am taking my parents and Fiancee to the @Ravens game next weekend and asked @Grok to help me route my @Tesla through a specific neighborhood to reach the correct Lot we will park in.
This is a great example of the new @grok nav integration with the Tesla Holiday Update: pic.twitter.com/rPp4I7q8Yv
— TESLARATI (@Teslarati) December 13, 2025
Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.
We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.
News
Tesla Cybercab has one important piece that AI4 cars might need for FSD
A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.
This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.
The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.
Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:
Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.
But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:
And this is how the side camera and washer look like on a Cybercab. This is from an Engineering vehicle in Peabody MA. pic.twitter.com/Re8VknpmLM
— Tobias Goebel (Unsupervised) (@tpgoebel) June 17, 2026
This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.
For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.
Without it, even the most advanced neural nets struggle when their “eyes” are compromised.
What Does This Mean for AI4 Cars?
This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:
Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys
As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.
As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.




