Connect with us

News

SpaceX’s Crew Dragon settles on Feb 9 launch debut as Falcon 9 nears static fire

DM-1 and Falcon 9 were greeted by an extraordinary - albeit bittersweet - dawn during their first-ever trip out to Pad 39A. (SpaceX)

Published

on

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.

Advertisement

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.

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.

Advertisement

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).

 

“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!


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

Advertisement

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

SpaceX Starship Flight 13 faces wrath of the Texas skies

SpaceX pushed Starship Flight 13 to Friday, blaming weather instead of the previous engine issues.

Published

on

By

SpaceX called off Thursday’s launch attempt of Starship Flight 13, pushing the mission to Friday because of weather tied to Tropical Storm Bertha. The company confirmed the delay on X, noting “Now targeting Friday, July 24 for Starship’s thirteenth flight test, due to weather. A key objective for the flight test is to get clear imagery from the ground of Starship’s heatshield as it flies at a higher dynamic pressure during ascent, which won’t be possible with today’s weather conditions.”

This is the second delay for Flight 13 in two weeks. SpaceX first tried to launch the mission on July 16, but the countdown ended in an automated abort at T-0 when four of Super Heavy Booster 20’s 33 Raptor engines failed to ignite. Musk said at the time that two Raptors would need to be removed and replaced, as Teslarati reported. The company spent the following week destacking Ship 40 and Booster 20, swapping engines, and running leak checks before restacking the vehicle on Pad 2 Wednesday night, according to Spaceflight Now’s live coverage.

Elon Musk debunks $52 billion SpaceX-NVIDIA GPU deal

 

Unlike the engine problem, Thursday’s delay has nothing to do with the hardware. SpaceX wants clean footage of Starship’s heat shield captured from the ground as the vehicle flies through max dynamic pressure, something the storm’s cloud cover over South Texas would not allow. The company said visibility should improve for Friday’s attempt, with the same 90 minute window opening at 5:45 p.m. CT.

Advertisement

Flight 13 will be the second outing for the V3 versions of Starship and Super Heavy, following their debut on Flight 12 in May. The mission carries 20 production Starlink V3 satellites, the first time SpaceX has flown operational satellites rather than mass simulators on Starship. Six of those satellites are fitted with cameras to inspect the heat shield from a different angle during ascent, giving engineers a second data source beyond the ground imagery the weather is currently blocking.

Booster 20 will attempt a boostback burn and a splashdown landing burn in the Gulf of America, while Ship 40 follows a suborbital trajectory toward a landing in the Indian Ocean. The flight plan largely mirrors Flight 12, though the booster will run a more aggressive ascent burn after max Q this time, and the ship’s heat shield includes load sensing tiles meant to measure stress at the higher dynamic pressure SpaceX is targeting.

If Friday’s attempt succeeds, Flight 13 could be the last suborbital test in the program. SpaceX is already looking to push for an orbital flight on Flight 14.

Continue Reading

Investor's Corner

Tesla stock tumbles after earnings, one of its sharpest single-day declines

Published

on

Credit: Tesla

Tesla stock (NASDAQ: TSLA) endured one of its sharpest single-day declines in years on July 23, tumbling approximately 14.5 percent and closing near $320 after opening the session around $374. The drop erased more than $140 billion in market value amid heavy trading volume and left the shares at multi-week lows.

The sell-off followed the company’s second-quarter 2026 results, released the previous evening. Tesla reported record revenue of $28.2 billion, up 26 percent year over year, driven by a Q2-record 480,126 vehicle deliveries. Energy storage deployments also rose strongly.

Tesla (TSLA) Q2 2026 earnings results: miss on EPS, beat on revenue

Yet profitability disappointed sharply. Operating income fell 57 percent to $398 million, compressing the operating margin to just 1.4 percent. Non-GAAP earnings per share came in at $0.33, well below the roughly $0.53 analysts had expected. Free cash flow turned negative by $1.1 billion as capital expenditures surged 142 percent to $5.8 billion, largely tied to accelerated spending on artificial intelligence, robotics, and autonomous systems.

The losses on capex were expected, as Tesla said it would be spending heavily in 2026.

Advertisement

Investors also reacted to lingering uncertainty surrounding key product timelines. During the Earnings Call, management reiterated ambitions for Robotaxi deployment and the Optimus humanoid robot, but offered limited new concrete milestones, renewing questions about execution pace that have long accompanied Tesla’s ambitious roadmap.

The magnitude of the decline places it among Tesla’s more severe one-day percentage losses since its 2010 initial public offering. Historically, the two largest single-day drops (split-adjusted) remain September 8, 2020, when shares fell 21.1 percent amid broader market volatility and valuation concerns, and January 13, 2012, with a 19.3 percent plunge during the company’s early growth struggles.

Other notable declines include an 18.6 percent drop on March 16, 2020, at the onset of pandemic-related market turmoil. Thursday’s move ranks roughly ninth on the all-time list but stands out as the steepest in more than a year.

Despite the short-term pain, Tesla’s long-term trajectory has repeatedly recovered from such volatility. The latest results underscore both the strength of its core automotive and energy businesses and the near-term costs of heavy investment in next-generation technologies.

Advertisement
Continue Reading

Elon Musk

Elon Musk is not happy about this Tesla Full Self-Driving approval delay

Published

on

Credit: Tesla

Elon Musk clapped back at France’s decision to withhold the approval for Tesla’s Full Self-Driving (FSD) Supervised system, projecting a clear and blunt message to French Transport Minister Phillippe Tabarot, after he publicly rejected the technology in its current form.

Tabarot outlines several concerns with Tesla Full Self-Driving in a detailed video statement, where he said, “The safety trade-offs are not yet sufficient to authorize it as it currently stands,” he said. He emphasized that FSD is not a true self-driving system and that the driver remains fully responsible.

Key issues Tabarot also brought up included allowing speeding when surrounding traffic exceeds limits and what he believes are insufficient guarantees of driver attention during complex urban maneuvers such as lane changes, intersections, and roundabouts.

Advertisement

While acknowledging technological progress and France’s support for autonomous innovation, Tabarot stressed that deployment must prioritize road safety. He noted ongoing technical discussions with Tesla, the Netherlands, and other European partners, with further ecosystem meetings planned for the fall.

Musk’s rebuke highlights the human cost of regulatory caution. Tesla’s latest safety reports provide compelling data supporting accelerated adoption. In the most recent 12-month period, vehicles using FSD (Supervised) recorded one major collision per approximately 5.1 million miles driven, dramatically better than the U.S. national average of one crash per 698,000 miles.

Even Tesla vehicles driven manually with active safety features outperform the average by a wide margin. These figures come from billions of real-world miles of telemetry, showing FSD vehicles involved in far fewer incidents than both manual Teslas and the broader U.S. fleet.

Critics argue Tesla’s comparisons require careful scrutiny regarding reporting thresholds and fleet demographics, yet the data consistently positions FSD as a potential lifesaver. With road fatalities remaining a leading cause of death worldwide, Musk contends that proven safer technology should not face prolonged bureaucratic hurdles.

France’s measured approach reflects the broader European regulatory caution, which many, especially Musk, have been critical of in the past. However, as autonomous systems from Tesla and competitors like Waymo demonstrate superior safety in independent studies, pressure is mounting for harmonized approvals.

Advertisement

Musk’s warning carries the belief that every month of delay may equate to avoidable tragedies on European roads.

Continue Reading