Connect with us
SpaceX has finally set the date for Crew Dragon's In-Flight Abort test. (Teslarati - Pauline Acalin) SpaceX has finally set the date for Crew Dragon's In-Flight Abort test. (Teslarati - Pauline Acalin)

News

SpaceX Crew Dragon In-Flight Abort test gets its first firm launch date

SpaceX has finally set the date for Crew Dragon's In-Flight Abort test. (Teslarati - Pauline Acalin)

Published

on

The day after questions arose around the targeted launch date of SpaceX’s Crew Dragon In-Flight Abort test (IFA), SpaceX and NASA have officially set the date for the spacecraft’s next major flight test.

On Friday, December 6th, a NASA Commercial Crew Program blog post confirmed a NET date of Saturday, January 4th, 2020 for the IFA test. The IFA test is one of the most notable final steps to be completed by the Crew Dragon capsule prior to supporting crewed astronaut flight to the International Space Station in 2020 as a part of NASA’s Commercial Crew Program.

Following an apparent incorrect statement made during SpaceX’s CRS-19 webcast that identified a February 2020 target date of the IFA test, SpaceX provided re-assurance that teams were very much still working toward a NET December launch date.

The SpaceX Falcon 9 rocket with the company’s Crew Dragon spacecraft onboard is seen on the launch pad at Launch Complex 39A as preparations continue for the Demo-1 mission, Friday, March 1, 2019 at the Kennedy Space Center in Florida. (NASA/Joel Kowsky)

A January 4th date falls just short of SpaceX’s December goal but it still comes as little surprise. In addition to this week’s CRS-19 launch, SpaceX aims to support two more launches prior to year’s end – an internal mission to launch 60 more Starlink satellites and the launch of the JCSAT 18/Kacific 1 communications satellite for customers SKY Perfect JSAT Corp. of Japan and Kacific Broadband Satellites of Singapore. While completing four Falcon 9 launches and landings in a period of less than four weeks is certainly possible for SpaceX, it was rather ambitious, especially given that Crew Dragon’s abort test is almost certainly the company’s preeminent priority.

The targeted January launch date now encroaches into the first quarter of 2020, which SpaceX has adamantly stated is also the goal for Crew Dragon’s first NASA astronaut launch, known as Demo-2. With the IFA test now NET January 4th, it will be a major challenge for NASA and SpaceX to turn around and prepare Crew Dragon and Falcon 9 for Demo-2 just 4-12 weeks later. Of note, Boeing is preparing its own Starliner spacecraft for an uncrewed launch test NET December 20th and has also claimed that it wants to launch a crewed flight test (CFT, akin to SpaceX Demo-2) as early as February 2020, same as SpaceX.

It’s extremely unlikely that NASA will be able to preserve both of those schedules given the Commercial Crew Program’s fixed workforce and the vast quantity of paperwork it must complete before the agency can give the go-ahead for SpaceX and Boeing astronaut launches.

Advertisement
(Pauline Acalin)
Crew Dragon lifts off atop Falcon 9 B1051 for the first time ever on March 2nd, 2019. (Teslarati – Pauline Acalin)

Unsurprisingly, the blog post confirmed that the IFA test would launch from Kennedy Space Center Launch Complex 39A (LC-39A). Pad 39A is the same facility that previously supported Crew Dragon’s March 2019 Demo-1 launch debut and is the only pad SpaceX intends to launch Crew Dragon from.

Interestingly, Pad 39A is also an active construction site – SpaceX is in the midst of building a new launch mount and modifying existing facilities to support future launches of SpaceX’s next-generation Starship vehicle. Construction has been underway for a few months and is situated directly beside Falcon 9 and Falcon Heavy’s exiting launch mount.

Although that construction will not be allowed to interfere with Crew Dragon launch activity, including the IFA test, construction on the Starship mount will likely be impacted. Construction crews will undoubtedly be expected to evacuate the area surrounding the launchpad during any Falcon 9 static fire test or launch, likely translating to a few days to a few weeks of downtime depending on how SpaceX handles the scheduling.

As 2019 comes to a close, SpaceX remains determined to launch Crew Dragon’s IFA test as quickly as is safely possible. If all goes perfectly during the upcoming abort test, SpaceX says it is seriously targeting Crew Dragon’s biggest test yet – its inaugural astronaut launch – less than two months later in February 2020. It should go without saying that that schedule is incredibly ambitious and highly liable to slip in March or Q2, but if the ambition is there, SpaceX believes it is technically possible.

For now, we have less than a month to wait for Crew Dragon’s next launch milestone and perhaps just 2-3 weeks before the spacecraft and its Falcon 9 rocket roll out to Pad 39A to prepare for a routine static fire test.

Advertisement

Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.

Space Reporter.

Advertisement
Comments

Elon Musk

The Boring Company just doubled its tunneling power in Nashville

The Boring Company’s Prufrock MB2 is commissioned and ready to mine beneath Nashville’s streets.

Published

on

By

boring-company-prufrock-1-2

The Boring Company’s second tunnel boring machine, Prufrock MB2, is officially ready to dig in Nashville. The company confirmed the news on X, posting: “Prufrock-MB2 is ready to mine in Nashville! MB2 commissioning is complete, including the brief 11 rpm rotation shown here. Will MB2 catch up to MB1, who had quite the head start? And Prufrock-MB3 ships in August!”

MB2 arrives with meaningful improvements over its predecessor. Lessons learned from the launch and operation of MB1 have already been applied to MB2 to improve efficiency and prepare the machine for launch.

Traditional tunnel boring machines operate in a stop-and-go cycle, digging roughly five feet, halt, erect precast concrete segments to line the tunnel wall, then resume. That repeated interruption is one of the main reasons conventional tunneling is slow and expensive. Prufrock is designed to install the tunnel liner simultaneously with mining, eliminating the need to stop every five feet. The machine also skips the need for excavated launch pits. Prufrock arrives on a truck, tilts down, and launches into the ground within 24 hours. And when the tunnel is complete, it emerges from the ground and drives to its next launch site on a trailer, eliminating the need for expensive cranes or pit excavation. The machine is also fully electric and runs with zero people in the tunnel during normal operations, controlled remotely from a surface operations center.

It won’t be long before we hear of another major update on The Boring Company’s Music City Loop project – a planned underground transit network beneath Nashville that would move passengers in electric vehicles through a series of tunnels at highway speeds, and bypassing surface traffic entirely. Nashville was selected in part because of its strong rock conditions that suits the Prufrock machines well, and relatively less regulatory hurdles.

Progress has been steady on multiple fronts. All 37 permits and approvals required ahead of tunneling have been obtained, out of 45 total. Key wins include a fully executed TDOT tunnel permit authorizing 25 miles of tunnel, unanimous airport authority approval for a Nashville International Airport station, and the city’s first residential station agreement serving downtown tower residents.

With MB1 already tunneling, MB2 now commissioned, and MB3 shipping in August, Nashville is becoming something of a live proving ground for scaled tunnel boring. The broader ambition is not limited to one city. The Boring Company’s stated goal is to make underground transportation a practical alternative to surface roads across major metro areas. Nashville is one of many cities, including a successful Las Vegas tunnel system, where that idea is being put to the test at real speed.

Continue Reading

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.

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.

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.

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

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.

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.

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.

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.

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