Connect with us

News

Astra ‘Rocket 3’ nosecone dooms first Florida launch attempt

Published

on

On Thursday, February 10th, Astra Space’s Rocket 3.3 launch vehicle took off from Cape Canaveral Space Force Station (CCSFS) Launch Complex 46 (LC-46).

Unfortunately, while liftoff and booster ascent appeared to be more or less perfect, Rocket 3’s payload fairing failed to separate, triggering a series of events that caused its upper stage to enter an uncontrolled and unrecoverable spin after burning for just a few seconds. Astra was unable to salvage the spinning rocket, resulting in a mission failure well short of orbit.

“Unfortunately we heard that an issue has been experienced during flight that prevented the delivery of our customer payloads to orbit today. We are deeply sorry to our customers NASA, University of Alabama, the University of Mexico and the University of California Berkeley,” said Astra Space Director of Product Management Carolina Grossman. “More information will be provided as we complete the data review.”

Today’s launch comes after two previous aborted launch attempts. The first attempt on February 5th was delayed due to a CCSFS radar system malfunction. The second launch delay came on February 7th, after the rocket aborted briefly after ignition because of a minor telemetry issue.

The Mission

NASA’s first mission under the agency’s Venture Class Launch Services (VCLS) Demonstration 2 contract hoped to launch four CubeSats to space as early as February 5th, 2022. The satellites, which made up the agency’s 41st Educational Launch of Nano-satellites (ELaNa) mission, were the first VCLS payloads launched – albeit unsuccessfully – from Cape Canaveral’s LC-46 pad, which last supported NASA’s Orion spacecraft Ascent Abort 2 (AA-2) test flight in July 2019.

Advertisement

The satellites onboard the flight were developed by three universities and one NASA center:

  • BAMA 1 (University of Alabama, Tusscolusa)
  • INCA (New Mexico State University, Las Cruces)
  • QubeSat (University of California, Berkeley) 
  • R5-S1 (NASA’s Johnson Space Center, Houston)

The ELaNa 41 mission CubeSats were selected through NASA’s CubeSat Launch Initiative (CSLI) and were assigned to the mission by NASA’s Launch Services Program based at Kennedy. CSLI provides launch opportunities for small satellite payloads built by universities, high schools, NASA Centers, and non-profit organizations.

About Astra

Founded in 2016, Astra Space is an American launch vehicle company based in Alameda, California. Astra’s official vision “is to Improve Life on Earth from Space by creating a healthier and more connected planet.” The company hopes to secure a large portion of the small satellite launch market, stating that it “offers the lowest cost-per-launch dedicated orbital launch service of any operational launch provider in the world.”

As of November 2021, Astra charges around $2.5-3.5M for a dedicated Rocket 3 launch, which can deliver up to 150 kg (330 lb) to low Earth orbit (LEO). In comparison, for a dedicated Electron launch, Rocket Lab charges about $7.5M for 300 kg (660 lb) to LEO. For customers willing to accept a one-size-fits-all rideshare solution, SpaceX charges $1M for 200 kg (440 lb) to LEO or higher sun-synchronous orbits (SSOs).

While the aerospace company is based out of California, its frequent orbital and suborbital test flights have all been conducted at the Pacific Spaceport Complex in Kodiak, Alaska. Prior test flights used Rocket 1, Rocket 2, and Rocket 3 prototypes as Astra refined its design and embraced a hardware-rich development style that didn’t shy away from failure.

Rocket 3.3 reached orbit for the first time – carrying an instrumented boilerplate payload for the United States Space Force – on November 21st, 2021. Less than two months later, Rocket 3.3 (serial number LV08) attempted to carry several NASA-sponsored cubesats into orbit on February 10th, 2022 – also the rocket’s first East Coast launch. Like Rocket 3.3’s predecessors, the two-stage vehicle was fueled with liquid oxygen (LOx) and refined kerosene (RP-1). Powered by five Delphin engines, the first stage produces up to ~145 kilonewtons (32,500 lbf) of thrust at liftoff. The second stage is powered by one pressure-fed Aether engine that delivers about 3.3 kN (740 lbf) of thrust in the vacuum of space.

Advertisement

The unsuccessful launch attempt occurred just three months after Astra applied for their Federal Aviation Administration (FAA) launch license and less than one day after receiving that license.

Monica Pappas is a space flight enthusiast living on Florida's Space Coast. As a spaceflight reporter, her goal is to share stories about established and upcoming spaceflight companies. She hopes to share her excitement for the tremendous changes coming in the next few years for human spaceflight.

Comments

News

Tesla Full Self-Driving (Supervised) v14.1.7 real-world drive and review

On an hour-long drive, we tested v14.1.7 and tested its new capabilities, which are mostly overall performance and smoothness fixes rather than integrations of new features that are unknown to routine FSD users.

Published

on

tesla interior operating on full self driving
Credit: TESLARATI

Tesla started rolling out its Full Self-Driving (Supervised) v14.1.7 suite last night to owners, and there are several improvements to note within the new update that are at least the start of fixes to highly-mentioned issues.

On an hour-long drive, we tested v14.1.7 and tested its new capabilities, which are mostly overall performance and smoothness fixes rather than integrations of new features that are unknown to routine FSD users. However, there are a handful of shortcomings that are still present within the suite, which are not something that will be fixed within the span of a single update.

For what it is, Full Self-Driving does an excellent job of navigating — once you get it on its correct path. Our issues tend to be confined to navigation, routing, and the decision-making process that has to do with the way the car wants to get you to your destination. There were five things that happened on our first drive with v14.1.7 that are worth mentioning. The full drive will be available at the bottom of this article.

Navigation and Routing Still Seems to Be a Major Challenge

In past content, we’ve discussed the issues with routing and navigation, and how a Tesla chooses its path. Most noticeably, these issues occur in the same areas; for me, it’s my local Supercharger. My 2026 Model Y with AI4 continues to pick less-than-optimal routes out of the Supercharger, and in this instance, it actually chose to turn down a road, pull over, and give me the wheel, essentially asking, “Hey, can you get me on the right track here?”

This is still my biggest bone to pick with FSD, even more so than some of the bonehead moves it’s made in tougher scenarios (mostly parking lots with very limited visibility due to shrubs being planted in the worst possible locations). It’s rare that it happens, but this particular Supercharger has been a true thorn in the side of my Tesla.

This is not an issue that is confined to v14.1.7, or even v14 in general. Unfortunately, it is an issue that has persisted throughout my ownership experience, as well as during Demo Drives.

Stuttering and Hesitation at Intersections was Non-Existent

There was some confusion regarding my language in a recent article where I stated Tesla is confronting the issues that have been reported regarding the “stabbing” with braking.

“Tesla began the v14.1.4 launch last night, which included minor improvements and addressed brake-stabbing issues many owners have reported. In my personal experience, the stabbing has been awful on v14.1.3, and is a major concern.

However, many things have improved, and only a couple of minor issues have been recurring. Many of the issues v13 addressed are no longer an issue, so Tesla has made significant progress.”
It has undoubtedly improved, but it is not resolved.

With that being said, I did not feel a single example of hesitation, stabbing, or stuttering at a single intersection or instance when it has been present in the past. CEO Elon Musk said it would be fixed with v14.2, so it seems like Tesla is well on its way to resolving it.

Proper Handling of Crosswalks

It’s crazy how many people still do not stop for pedestrians at clearly-marked crosswalks. I had two instances of it happen during the drive, with FSD stopping for those pedestrians both times.

Human drivers did not stop either time:

Handled Merging onto a Highway with an Inconsiderate Driver Well

Routinely, drivers will get over into the left lane, if they are able, to allow merging traffic to safely enter the freeway. It does not always happen this way, and it’s not required by law.

Not exclusive to v14.1.7, as many past iterations would have done this as well, but it was nice to watch the vehicle slow down to let that traffic pass. It then entered the freeway safely, and the entire maneuver was well done.

Took an Appropriate Move with Oncoming Foot Traffic and Debris in a Tight Alleyway

This was probably the most on-edge I was during the drive because: 1) FSD chose to take an unnecessary alleyway, and 2) there was a box and oncoming pedestrians.

The car was aware of everything that was going on. In order to avoid the box, it would have had to turn toward the pedestrians, and in order to avoid the pedestrians, it would have had to turn into the box.

It chose to wait patiently, and after the pedestrians were past the car, FSD chose to proceed.

Closing Thoughts

Overall, we’re very impressed with v14.1.7, and we think this is Tesla’s best iteration of the FSD suite yet, as it should be since it’s the newest version available. Tesla’s attention to detail regarding the brake stabbing is really well done, and it seems evident that a complete fix is on its way.

Other than the navigation issue at the very beginning, which was not an intervention, at least in my opinion, this was a really successful drive.

Continue Reading

Elon Musk

Elon Musk debunks report claiming xAI raised $15 billion in funding round

xAI also responded with what appeared to be an automated reply, stating, “Legacy Media Lies.”

Published

on

Credit: xAI

Elon Musk has debunked a report claiming his AI startup xAI had raised $15 billion from a funding round. Reports of the alleged funding round were initially reported by CNBC, which cited sources reportedly familiar with the matter.

CNBC’s report

The CNBC story cited unnamed sources that claimed that the new capital injection would help fund GPUs that xAI needs to train its large language model, Grok. The news outlet noted that following the funding round, xAI was valued at $200 billion. 

Artificial intelligence startups have been raising funds from investors as of late. OpenAI raised $6.6 billion in October, valuing the startup at a staggering $500 billion. Reuters also reported last month that OpenAI was preparing for an IPO with a valuation of $1 trillion. Elon Musk’s xAI is looking to catch up and disrupt OpenAI, as well as its large language model, ChatGPT, which has become ubiquitous.

Elon Musk and xAI’s responses

In his response on X, Elon Musk simply stated that the CNBC story was “false.” He did not, however, explain if the whole premise of the publication’s article was fallacious, or if only parts of it were inaccurate. 

Amusingly enough, xAI also issued a response when asked about the matter by Reuters, which also reported on the story. The artificial intelligence startup responded with what appeared to be an automated reply, which read, “Legacy Media Lies.”

Advertisement

xAI, founded in July 2023 as an alternative to OpenAI and Anthropic, has aggressively built out infrastructure to support its flagship products, including Grok and its recently launched Grokipedia platform. The company is developing its Colossus supercomputer in Memphis, which is heralded as one of the world’s largest supercomputer clusters.

Continue Reading

News

Tesla reportedly testing Apple CarPlay integration: report

Citing insiders reportedly familiar with the matter, Bloomberg News claimed that CarPlay is being trialed by the EV maker internally.

Published

on

Credit: Tesla

Tesla is reportedly testing Apple’s CarPlay software for its vehicles, marking a major shift after years of resisting the tech giant’s ecosystem. 

Citing insiders reportedly familiar with the matter, Bloomberg News claimed that CarPlay is being trialed by the EV maker internally. The move could help Tesla gain more market share, as surveys have shown many buyers consider CarPlay as an essential feature when choosing a car.

Not the usual CarPlay experience

Bloomberg claimed that Tesla’s tests involve a rather unique way to integrate CarPlay. Instead of replacing the vehicle’s entire infotainment display, Tesla’s integration will reportedly feature a CarPlay window on the infotainment system. This limited approach will ensure that Tesla’s own software, such as Full Self-Driving’s visuals, remains dominant. 

The feature is expected to support wireless connectivity as well, bringing Tesla in line with other luxury automakers that already offer CarPlay. While plans remain fluid and may change before public release, the publication’s sources claimed that the rollout could happen within months. 

A change of heart

Tesla has been reluctant to grant Apple access to its in-car systems, partly due to Elon Musk’s past criticism of the tech giant’s App Store policies and its poaching of Tesla engineers during the failed Apple Car project. Tesla’s in-house software is also deemed by numerous owners as a superior option to CarPlay, thanks to its sleek design and rich feature set.

Advertisement

With Apple’s retreat from building cars and Elon Musk’s relationship with Apple for X and Grok, however, the CEO’s stance on the tech giant seems to be improving. Overall, Tesla’s potential CarPlay integration would likely be appreciated by owners, as a McKinsey & Co. survey last year found that roughly one-third of buyers considered the lack of such systems a deal-breaker.

Continue Reading

Trending