Connect with us

News

SpaceX’s Crew Dragon spaceship marches towards launch with vacuum chamber test

Published

on

SpaceX has published the latest photo of its next-generation Crew Dragon spacecraft, showing the crewed vehicle preparing to be put through its paces inside a NASA thermal vacuum chamber located in Cleveland, Ohio. If the tests are completed without issue, the Dragon’s next destination will be Cape Canaveral, Florida, where it will prepare for an inaugural launch targeted for the fourth quarter of 2018.

In the photo released on June 20th, SpaceX’s DM-1 Crew Dragon capsule (C202 in shorthand: [C]apsule, Dragon [2], serial number [02]) is seen being craned by SpaceX technicians into the thermal vacuum chamber at NASA’s Plum Brook testing facilities. Located in Ohio, Plum Brook’s vacuum chamber is unique because of both its size and its ability to fairly accurate replicate the actual environment faced by satellites and spacecraft once in space. Most importantly, this includes the extreme thermal conditions those vehicles are subjected to by constant ~90-minute day-night cycles in low Earth orbit (LEO).

Without Earth’s cozy atmosphere to act as both a heat sink and insulating blanket once on orbit, there is simply nothing there to protect spacecraft like Crew Dragon from the absolute extremes of direct solar radiation (sunlight), total darkness, and a complete lack of cooling by conduction and convection. In order to avoid overheating, Crew Dragon thus needs to bring along its own means of cooling in the form of onboard radiators to shed excess heat. The use of white paint on spacecraft further aids this process by selectively preventing the absorption of solar radiation while simultaneously efficiently emitting in infrared wavelengths.

How to prep your Dragon

Crew Dragon’s primary radiators are elegantly integrated into vertical panels installed on the cylindrical bottom segment, known as the trunk, while the craft’s power source – solar panels in this case – are installed in a curved array on the opposite side of the trunk. Intriguingly, the trunks displayed in the two most recent photos of the DM-1 Crew Dragon appear to be almost completely different, and the trunk at Plum Brook does not appear to have its solar arrays or radiators installed. Nominally, SpaceX would use the thermal vacuum capabilities of the Ohio facility to fully vet Crew Dragon’s ability to maintain optimal temperatures on orbit, but the particularly tests planned for the DM-1 capsule and trunk may be of a slightly different type.

Advertisement

Regardless, after testing at Plum Brook is completed, the DM-1 Crew Dragon capsule will be shipped to a newly-constructed processing facility in Cape Canaveral, Florida, while it’s understood that the trunk installed in SpaceX’s June 20th photo will be returned to the Hawthorne, CA factory to be outfitted with flight hardware (presumably including cameras, radiators, solar arrays, and a healthy amount of insulation). It’s unclear when the two segments of DM-1 will part ways and head on to their next destinations, but it’s likely that testing at Plum Brook will last for at least a handful of weeks.

Birds of a feather

In the meantime, several additional Crew Dragon capsules/trunks and the Falcon 9 Block 5 rockets that will launch them are in a variety of states of fabrication and assembly at SpaceX’s Hawthorne factory. B1051, the Block 5 booster assigned to the first uncrewed Demo-1 launch of Crew Dragon, was reported by NASA to be undergoing propellant tank integration in March 2018, implying that the rocket should be at or near the final stages of integration, and will likely ship to McGregor, Texas for static fire testing late this summer.

As of June 15th, SpaceX’s third Falcon 9 Block 5 booster was vertical on the Texas test stand, likely nearing its own static fire test before being shipped to SpaceX’s Vandenberg Air Force Base launch facilities for the July 20th launch of Iridium-7. While possible that a booster slipped past the watchful eyes and ears of SpaceX enthusiast observers, it’s probable that the rocket currently in McGregor is B1048, implying that a minimum of two additional booster shipments and Texas test programs remain before B1051 can be prepped to launch SpaceX’s first Crew Dragon mission. At the current marginally accelerated booster production and shipment schedule (~ 30-day cadence), B1051 would be expected to leave Hawthorne for Texas no earlier than (NET) late August or early September. This meshes with a recent comment from Commercial Crew astronaut Suni Williams:

“I think we’re going to get the [uncrewed[ demo flights probably by the end of the year, maybe a little after that . . . and then the crew demo missions next year.”

 

Advertisement

Anticipating acceptance and prelaunch testing that is far more extensive and time-consuming than typically seen with SpaceX’s commercial missions, it’s safe to bet that the first uncrewed Crew Dragon mission – DM-1 – will launch from Kennedy Space Center in November or December 2018. While those operations proceed over the course of the rest of this year, SpaceX expects roughly 10 additional Falcon 9 and Falcon Heavy launches to occur. It’s gonna be a busy H2.

Follow us for live updates, peeks behind the scenes, and photos from Teslarati’s East and West Coast photographers.

Teslarati   –   Instagram Twitter

Tom CrossTwitter

Advertisement

Pauline Acalin  Twitter

Eric Ralph Twitter

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla urges New Jersey owners to oppose new bill that could block Robotaxi

Published

on

Credit: Grok

Tesla has launched a direct campaign targeting its customers in New Jersey, sending emails that warn of pending legislation that could effectively block true driverless technology in the state.

The email focuses on Senate Bill S.1677 and Assembly Bill A.3968, measures intended to create a three-year autonomous vehicle pilot program but laden with requirements that Tesla argues make unsupervised Robotaxis impossible.

According to the email, the bills impose “restrictions so severe that true driverless deployment would remain illegal.” Specific hurdles include mandates for human safety drivers during operations, multimillion-dollar insurance minimums, reportedly $5 million, and thresholds like 100,000 miles of demonstrated safe autonomous driving before any driverless approval.

Tesla contends these are arbitrary barriers that ignore real-world performance data and favor entrenched competitors over innovative technologies like its Full Self-Driving (FSD) system.

The push comes as Tesla has started expanding Robotaxi operations in states like Texas, where unsupervised vehicles are already providing rides in several cities. New Jersey, by contrast, risks falling behind. The company highlights in the email communication that more than 94 percent of serious crashes result from human error, meaning impairment, distraction, or fatigue. These are all problems that Robotaxis eliminate entirely.

Advertisement

In 2025, New Jersey recorded 582 traffic deaths, underscoring the human cost of delayed adoption.

Tesla’s outreach stresses the transformative potential of robotaxis. For families, they could offer safer school runs without drowsy or distracted drivers. For seniors and people with disabilities, robotaxis promise independence and reliable mobility.

In areas with limited public transit, they could deliver affordable, on-demand transportation, reducing congestion, emissions, and overall transportation costs. Economically, the company warns that restrictive rules could cost New Jersey jobs, innovation investment, and billions in potential growth as autonomous ride-hailing scales elsewhere.

Supporters of the legislation, including Sen. Andrew Zwicker, describe the pilot as a cautious framework with strong safety oversight, including incident reporting, expert task forces, and restrictions in sensitive zones like school areas. They view it as balancing innovation with public protection.

Advertisement

Tesla and pro-AV advocates counter that the bill lacks technology neutrality, creates insurmountable entry barriers for commercial deployment, and prioritizes process over outcomes — effectively functioning as a de facto ban on services like Robotaxi.

This latest clash echoes Tesla’s past battles in New Jersey over direct vehicle sales. The email directs owners to Tesla’s advocacy platform, where they can send customized messages to legislators calling for amendments: outcome-based safety standards, open competition, and clear pathways for fully driverless commercial operations.

As hearings approach, Tesla’s campaign frames the issue as a choice between protecting the status quo and embracing life-saving progress. With robotaxi technology already proving itself in permissive states, New Jersey owners are being asked to ensure their state doesn’t lock out the future of transportation.

Advertisement
Continue Reading

News

Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest

Published

on

Credit: TESLARATI

Turn-by-turn navigation is not new technology.

For over two decades, drivers have relied on Garmin, TomTom, and later smartphone apps like Google Maps and Waze to receive precise, reliable directions. These systems have guided millions safely through unfamiliar cities, highways, and backroads with remarkable effectiveness. They handle real-time traffic, construction detours, and complex intersections with minimal fuss.

Yet Tesla, the company that promised revolutionary Full Self-Driving (FSD), continues to struggle with this foundational capability. As FSD (Supervised) v14.3.4 has started rolling out to cars this week, navigation remains its glaring Achilles’ heel, undermining the entire autonomous vision.

Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much

Advertisement

Tesla’s FSD excels in many driving behaviors—smooth acceleration, confident lane changes in ideal conditions, and responsive handling of visible obstacles. However, when it comes to following a route accurately, the system falters repeatedly.

Owners report wrong turns, missed exits, inefficient routing through local roads instead of highways, phantom speed limit errors, and even directing vehicles to building rear entrances. Interventions for navigation issues often outnumber those for core driving maneuvers. Tesla has begun surveying owners specifically about these errors, acknowledging the problem after years of complaints.

Navigation is perhaps my biggest complaint when it comes to FSD, because sometimes, we do know better. Some of us have been living in our areas for our entire lives, but even those who have not have years or even decades of experience driving on local roads. We might know a little better about routing.

But the navigation mistakes are more than just FSD potentially taking a slightly different route that may or may not save you a few minutes. Sometimes, they’re genuinely mind-boggling.

Advertisement

This isn’t just annoying; it cascades into broader failures. A flawed route plan confuses the AI’s decision-making, leading to hesitant behavior, unnecessary disengagements, or dangerous maneuvers like attempting impossible U-turns or ignoring clear ramps. In a system meant to operate with minimal supervision, unreliable navigation erodes trust.

More often than not, false or plain incorrect navigation is what causes me to interrupt FSD operation. Unfortunately, I believe the latest FSD version is the worst example of it, and it leads me to believe that Tesla might be making some changes; they’ve just made them in the wrong direction.

It makes you wonder: Why is a company that has done so much with the progress of FSD and autonomy struggling so much with navigation, something that is not new and has been around a long time?

Multiple Data Sources

First, Tesla’s navigation relies on a fragile patchwork of multiple data sources—Google Maps, TomTom, OpenStreetMap, Valhalla, and its own fleet-derived data—stitched together rather than a single authoritative map. When these conflict on lane geometry, road status, or turn details, the system hesitates or chooses incorrectly.

Advertisement

Traditional GPS providers maintain centralized, regularly validated databases with professional curation and rapid updates. Tesla’s hybrid approach, while innovative in crowdsourcing, introduces inconsistencies that a purely vision-based or end-to-end AI approach may not easily reconcile in real time.

Persistent Learning

FSD seems to struggle with persistent learning from driver interventions.

Unlike consumer apps that quickly adapt to repeated corrections or user preferences (e.g., avoiding certain routes or remembering habitual detours), Tesla’s FSD often fails to internalize fixes on the same trip or across similar scenarios. Owners note making the same manual override multiple times without the routing engine updating its behavior meaningfully.

This stems from the neural architecture prioritizing real-time perception and control over long-term route memory and personalization, making navigation feel rigid and “opinionated” compared to the adaptive logic in Waze or Google Maps.

Advertisement

I noticed that when I asked Grok to try and get me home a certain way (a way that FSD routinely took in the past because it was the most efficient), it had to place a waypoint between my location at the time and my house. When I went to edit the waypoint out, as Grok had placed it for a way to get FSD to get off the highway at the right exit, it was stumped again, rerouted, and took a longer way home.

Reasoning, Scaling, and Intuition

Third, scaling navigation for unsupervised or robotaxi ambitions requires not just accuracy but adaptability and user-like reasoning. Current FSD often defaults to single routes that ignore driver preferences or real-world nuances like time-of-day traffic patterns. It fails to match the intuitive, context-aware planning that traditional systems have refined over the years.

Resolving navigation is critical for several reasons. Practically, it is the backbone of any autonomous journey: without trustworthy routing, the car cannot reliably reach destinations, rendering FSD useless for robotaxis or hands-free commutes. Safety depends on it—mismatched plans create hesitation in merges or intersections, increasing accident risk.

Economically, Tesla’s valuation and future hinge on FSD delivering unsupervised driving; persistent navigation flaws delay regulatory approval and erode consumer confidence. For owners who paid premiums for FSD, these issues represent unfulfilled promises. While it is unlikely Tesla will lose too many customers due to bad navigation, some will be frustrated with the constant need for human input.

Advertisement

Tesla has achieved miracles in electric vehicles and battery tech. Mastering turn-by-turn—technology Garmin nailed in the early 2000s—should not be this hard. By investing in tighter data integration, faster learning loops from interventions, and more intuitive routing algorithms, Tesla could close this gap.

Until then, FSD’s navigation struggles highlight a humbling truth: even the most ambitious innovator must sometimes master the basics before conquering the future.

Continue Reading

Cybertruck

Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK

Published

on

A Tesla Cybertruck driver in the United Kingdom had their all-electric pickup seized by local police in the Greater Manchester area after the department cited “legitimate concerns.”

Last Thursday, police saw the pickup on the roads and decided to pull the driver over. Greater Manchester Police said:

“Whilst this may seem trivial to some, legitimate concerns exist around the safety of other road users or pedestrians if they were involved in a collision with the Cybertruck.”

The Cybertruck in question was, according to the BBC, registered and insured abroad and was confiscated. The driver, who is a UK resident, was reported.

The Greater Manchester Police Department then added:

Advertisement

“The Tesla Cybertruck is not road-legal in the UK and does not hold a certificate of conformity.”

The Cybertruck cannot be legally driven in the UK because it has no UK Type Approval for operation in the country. This is due to some safety concerns, which are related to its angular shape and design. The stainless steel exoskeleton has sharp edges and projections that violate UK/EU rules on pedestrian protection.

Tesla has considered creating what it referred to as an “international version” that would be approved for operation in Europe. However, there has been no real movement on that front by the company, as it has been focused on the Robotaxi rollout primarily.

Advertisement
Continue Reading