Connect with us

News

SpaceX Falcon Heavy testing delayed after government shutdown

Published

on

As the U.S. Senate’s majority party searches for ten additional votes in order to end a federal government shutdown that began late Saturday, all “non-essential” activities at the country’s numerous government-operated space launch facilities have ground to an immediate halt and will remain in limbo until a funding bill compromise is hammered out.

While SpaceX is a wholly private space launch company, it relies almost unilaterally upon launch support and range expertise provided by NASA and the US Air Force, both in Cape Canaveral, FL and Vandenberg, CA. Sadly, the Air Force personnel SpaceX depend upon to conduct launches, static fires, and other ignition tests at its launch pads are not considered “essential” under regulations that prevent the federal government from coming to a complete halt in the event of a funding-related shutdown.

SpaceX did appear to complete the most thorough round of Falcon Heavy testing yet late Saturday evening, the US Senate’s failure to either pass a continuing resolution or a new funding bill for the fiscal year led to a complete federal government shutdown soon after. As a result, nearly all of the US Air Force’s 45th Space Wing – a crucial backbone of East coast range and launch operations – was furloughed indefinitely, pending new funding from Congress. SpaceX had previously requested a new static fire date for Falcon Heavy on Monday, January 22 (today), a date that is now clearly going to move right for at least as long as the government lacks funding for basic launch operations.

Advertisement
-->

Thankfully, activities like the extensive propellant loading tests that occurred on Saturday night do not technically require range support, so long as no engine ignition or static fire components are included. In the event of a catastrophic failure, the government-run range would be tasked with ensuring the safety of those in the vicinity and coordinating the emergency response that would immediately follow. This policy is brought somewhat into question by the failure of Amos-6 – although that Falcon 9 was being prepared for a static fire test, its highly-destructive failure is understood to have occurred at least five or more minutes before the planned point of ignition. Nevertheless, SpaceX will be able to continue some level of testing with Falcon Heavy, if needed.

Elsewhere, instability

While SpaceX’s Falcon Heavy has undoubtedly garnered magnitudes more eyeballs than the company’s Falcon 9 activities, the government shutdown could be far more consequential for SpaceX’s customers if it cannot be halted within a handful of days. A federal shutdown lasting several days is a hugely disruptive and damaging event on its own, lack of range support on the East coast could quickly begin to eat into SpaceX’s GovSat-1 preparations, the launch of which is targeting NET late January/January 30. For GovSat-1’s flight-proven booster, a static fire at the launch site is unlikely to be bypassed (SpaceX has never skipped a prelaunch static fire), and would typically occur no fewer than four or five days before launch. As a result, in the somewhat unlikely event that the shutdown stretches beyond the next several days, SpaceX customers SES and GovSat could see their launch delayed, an event that would likely bring financial consequences to the public-private satellite venture.

Looking slightly farther into the future, SpaceX’s flight-proven launch of PAZ and two of its own prototype communications satellites is just about two weeks away from its own static fire test, this time at the West Coast’s Vandenberg Air Force Base. Such an extended shutdown would be utterly unprecedented, but if 2017 and 2018 have done anything at all, they’ve tempered tendencies towards knee-jerk claims of “that’ll never happen!”

Here’s to hoping that Congress can get their act together and return to those they represent the bare minimum of federal stability, for both federal employees and those that depend upon them.

Advertisement
-->

Update: After a solid two days of shutdown, the Senate has apparently reached an agreement to pass a continuing resolution that will maintain funding for another three weeks, after which a new FY2018 budget must be passed to avoid another shutdown. While this thankfully means that the impact to the Space Coast and the Air Force’s 45th Space Wing should be relatively small, I have left my above thoughts on the potential impacts of a longer shutdown untouched for posterity. 

Follow along live as launch photographer Tom Cross and I cover these exciting proceedings as close to live as possible.

Teslarati   –   Instagram Twitter

Advertisement
-->

Tom CrossInstagram

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 Full Self-Driving v14.2 – Full Review, the Good and the Bad

Published

on

Credit: Teslarati

Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.

With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.

While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.

With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.

However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.

Advertisement
-->

The Good

Lack of Brake Stabbing and Hesitation

Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.

This was a major problem.

However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.

This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.

Speed Profiles Seem to Be More Reasonable

There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.

Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.

It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.

Advertisement
-->

Better Overall Operation

I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.

v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.

The Bad

Parking

It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.

This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.

However, this was truly my only complaint about v14.2.

You can check out our full 62-minute ride-along below:

Advertisement
-->
Continue Reading

Elon Musk

SpaceX issues statement on Starship V3 Booster 18 anomaly

The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas. 

Published

on

Credit: SpaceX/X

SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas. 

SpaceX’s initial comment

As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.

“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X. 

Incident and aftermath

Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.

Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.

Advertisement
-->
Continue Reading

Investor's Corner

Tesla analyst maintains $500 PT, says FSD drives better than humans now

The team also met with Tesla leaders for more than an hour to discuss autonomy, chip development, and upcoming deployment plans.

Published

on

Credit: Tesla

Tesla (NASDAQ:TSLA) received fresh support from Piper Sandler this week after analysts toured the Fremont Factory and tested the company’s latest Full Self-Driving software. The firm reaffirmed its $500 price target, stating that FSD V14 delivered a notably smooth robotaxi demonstration and may already perform at levels comparable to, if not better than, average human drivers. 

The team also met with Tesla leaders for more than an hour to discuss autonomy, chip development, and upcoming deployment plans.

Analysts highlight autonomy progress

During more than 75 minutes of focused discussions, analysts reportedly focused on FSD v14’s updates. Piper Sandler’s team pointed to meaningful strides in perception, object handling, and overall ride smoothness during the robotaxi demo.

The visit also included discussions on updates to Tesla’s in-house chip initiatives, its Optimus program, and the growth of the company’s battery storage business. Analysts noted that Tesla continues refining cost structures and capital expenditure expectations, which are key elements in future margin recovery, as noted in a Yahoo Finance report. 

Analyst Alexander Potter noted that “we think FSD is a truly impressive product that is (probably) already better at driving than the average American.” This conclusion was strengthened by what he described as a “flawless robotaxi ride to the hotel.”

Advertisement
-->

Street targets diverge on TSLA

While Piper Sandler stands by its $500 target, it is not the highest estimate on the Street. Wedbush, for one, has a $600 per share price target for TSLA stock.

Other institutions have also weighed in on TSLA stock as of late. HSBC reiterated a Reduce rating with a $131 target, citing a gap between earnings fundamentals and the company’s market value. By contrast, TD Cowen maintained a Buy rating and a $509 target, pointing to strong autonomous driving demonstrations in Austin and the pace of software-driven improvements. 

Stifel analysts also lifted their price target for Tesla to $508 per share over the company’s ongoing robotaxi and FSD programs. 

Continue Reading