Connect with us

News

DeepSpace: Firefly set for smallsat industry’s second place trophy, Rocket Lab leads the pack

Published

on

This is a free preview of DeepSpace, Teslarati’s new member-only weekly newsletter. Each week, I’ll be taking a deep-dive into the most exciting developments in commercial space, from satellites and rockets to everything in between. Sign up for Teslarati’s newsletters here to receive a preview of our membership program.

In the race to a field dedicated smallsat launch vehicles, New Zealand startup Rocket Lab has already won first place, a fact that has been discussed several times in past Deep Space issues. After completing its first launch of 2019 on March 28th, Rocket Lab’s Electron rocket is ready for another mission as early as May 4th, a good sign for the company’s planned monthly launch cadence.

Despite Rocket Lab’s major success, there is plenty of room for additional competitors and/or complementary vehicles. Electron’s maximum payload hovers around ~225 kg (500 lb) to low Earth orbit (LEO), limiting its usefulness for any payloads that are larger than truly tiny satellites or in need of higher orbits. Also discussed on DeepSpace, there are 10+ serious startups with funding and hardware in work attempting to build said smallsat launch vehicles, ranging from the extremely tiny (Vector: 60 kg to LEO) to much larger rockets from companies like Relativity, ABL Space, and more. Firefly Space, however, is the startup that has arguably broken away from the pack in the last few months, firmly setting itself up to be second in line behind Rocket Lab.

Build, test, qualify


  • Firefly’s major leaps forward came in December 2018 and then April 2019, both related to testing the completed upper stage of the company’s Alpha rocket.
  • In December, the upper stage ignited for the first time. In April, the same upper stage successfully performed a mission-duration static fire that lasted a full 300 seconds (five minutes), the same length required for a rocket to reach orbit after separating from Alpha’s first stage.
    • For any launch vehicle development program, the first successful mission-duration test fire of an integrated rocket stage is arguably one of the most important milestones, second only to the same hardware’s inaugural launch.

  • Simultaneously, Firefly began integrated testing of the thrust section and Reaver engines that will be the basis of Alpha’s first stage. The rocket’s Lightning second stage engine has been tested extensively at this point in development, although the stage’s lone engine produces a maximum of ~70 kN (~16,000 lbf) of thrust.
    • The booster’s four Reaver engines will each produce ~170 kN (55,000 lbf) of thrust, around three times as much as Lightning. Alpha’s second stage is critical, but its first stage is arguably far more complex.
    • Despite the relative power differential, it’s still worth noting that Alpha’s entire first stage (736 kN/166,000 lbf) will be significantly less powerful than a single one of Falcon 9’s nine Merlin 1D engines (941 kN/212,000 lbf).
  • Although Alpha is far smaller than rockets like Falcon 9 or Atlas V, it will nominally be capable of launching 1000 kg to an altitude of 200 km (LEO) or ~650 kg to a 500-km sun-synchronous orbit (SSO). This translates to around 4.2X the performance of Rocket Lab’s Electron at 2.5X the cost per launch ($15M vs $6M).
    • Assuming no payload capacity is wasted, Alpha could thus be almost 50% cheaper than Electron when judged by cost per kilogram to orbit.
    • Of course, this comparison ignores the fact that Firefly will have to far more heavily rely on booking co-passenger satellites to keep Alpha launch prices competitive with Electron.
    • If exactly 1000kg or 630kg of cargo can’t be booked each launch, the expendable Alpha’s $15M launch cost will be distributed over less payload, raising costs for each customer. In other words, the competitive advantages of Alpha are almost entirely associated with its ability to launch payloads outside of Electron’s capabilities, as are its potential weaknesses.

Firefly Alpha’s upper stage qualification article (top) and a comparison of a variety of launch vehicles. (Teslarati)

The sweet spot

  • In theory, Firefly Alpha’s could find itself in a relatively sweet spot, where the rocket’s launch costs are not so high that dedicated rideshare missions become intractable (i.e. Spaceflight’s SSO-A launch on Falcon 9) but its payload performance is still good enough to provide access to a huge swath of the space launch market.
  • Firefly also has plans to develop a heavier launch vehicle based on Alpha, known as Beta. Conceptually equivalent to SpaceX’s Falcon Heavy, Beta would use three Alpha boosters and a significantly upgraded second stage and would be able to launch 4000 kg to LEO or 3000 kg to SSO.
  • Regardless of Firefly’s grander aspirations, Alpha is poised to capitalize on the simple fact that it will be the second commercially viable smallsat launch vehicle to begin operations. Alpha’s first orbital launch attempt could occur as early as December 2019, although slips into early 2020 are to be expected.
    • At that point, Rocket Lab’s Electron will be the only serious competition on the market. Relativity’s Terran and ABL Space’s RS-1 rockets plan to offer a competitive ~1250 kg to LEO or ~900 kg to SSO, but their launch debuts are tentatively scheduled no earlier than late 2020.
    • If Alpha’s development continues smoothly, Firefly could easily have a solid 12-month head start over its similarly-sized competitors,
  • Up next for Alpha is a similar campaign of tests focused on the first integrated booster, including tests fires and an eventual mission-duration qualification test.

Mission Updates 

  • SpaceX’s CRS-17 Cargo Dragon resupply mission has slipped an additional four days from April 30th to May 3rd (3:11 am EDT, 07:11 UTC) after the International Space Station (ISS) began suffering serious (but non-threatening) electrical issues. Additional launch delays could follow if the issue is not resolved in the next few days.
    • The first operational Starlink launch remains firmly on track for NET mid-May. According to SpaceX, all Flight 1 satellites are already in Florida, while the FCC approved the company’s modified constellation license – permitting Starlink operations after launch – on April 26th.
    • Due to CRS-17’s launch delays, the availability of SpaceX’s LC-40 pad will now likely be the main limiting factor for the Starlink-1 launch date.
  • SpaceX’s second West Coast launch of 2019 – carrying Canada’s Radarsat Constellation – is now expected to occur no earlier than mid-June and will reuse Falcon 9 B1051.
  • SpaceX’s launch of Spacecom’s Amos-17 spacecraft is now scheduled no earlier than July. Falcon Heavy Flight 3 is tentatively scheduled for launch as early as June 22 – all three boosters should be on site in Florida within the next week or two.

Photo of the Week:

(SpaceX)

The third Falcon Heavy center core – believed to be B1057 – was spotted eastbound in Arizona on April 16th. On April 26th, SpaceX confirmed that the booster completed its acceptance static fire test at the company’s McGregor, TX facilities, a sure sign that all of Falcon Heavy Flight 3’s major components should be in Florida within the next few weeks.

We’ll see you next week.

Not a member? Become a member today to receive DeepSpace each week! 

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

Elon Musk

Tesla Full Self-Driving v14.2.1 texting and driving: we tested it

We decided to test it, and our main objective was to try to determine a more definitive label for when it would allow you to grab your phone and look at it without any nudge from the in-car driver monitoring system.

Published

on

Credit: Grok

On Thursday, Tesla CEO Elon Musk said that Full Self-Driving v14.2.1 would enable texting and driving “depending on [the] context of surrounding traffic.”

Tesla CEO Elon Musk announces major update with texting and driving on FSD

We decided to test it, and our main objective was to try to determine a more definitive label for when it would allow you to grab your phone and look at it without any nudge from the in-car driver monitoring system.

I’d also like to add that, while Tesla had said back in early November that it hoped to allow this capability within one to two months, I still would not recommend you do it. Even if Tesla or Musk says it will allow you to do so, you should take into account the fact that many laws do not allow you to look at your phone. Be sure to refer to your local regulations surrounding texting and driving, and stay attentive to the road and its surroundings.

The Process

Based on Musk’s post on X, which said the ability to text and drive would be totally dependent on the “context of surrounding traffic,” I decided to try and find three levels of congestion: low, medium, and high.

Advertisement
-->

I also tried as best as I could to always glance up at the road, a natural reaction, but I spent most of my time, during the spans of when it was in my hand, looking at my phone screen. I limited my time looking at the phone screen to a few seconds, five to seven at most. On local roads, I didn’t go over five seconds; once I got to the highway, I ensured the vehicle had no other cars directly in front of me.

Also, at any time I saw a pedestrian, I put my phone down and was fully attentive to the road. I also made sure there were no law enforcement officers around; I am still very aware of the law, which is why I would never do this myself if I were not testing it.

I also limited the testing to no more than one minute per attempt.

I am fully aware that this test might ruffle some feathers. I’m not one to text and drive, and I tried to keep this test as abbreviated as possible while still getting some insight on how often it would require me to look at the road once again.

The Results

Low Congestion Area

I picked a local road close to where I live at a time when I knew there would be very little traffic. I grabbed my phone and looked at it for no more than five seconds before I would glance up at the road to ensure everything was okay:

Advertisement
-->

Looking up at the road was still regular in frequency; I would glance up at the road after hitting that five-second threshold. Then I would look back down.

I had no nudges during this portion of the test. Traffic was far from even a light volume, and other vehicles around were very infrequently seen.

Medium Congestion Area

This area had significantly more traffic and included a stop at a traffic light. I still kept the consecutive time of looking at my phone to about five seconds.

Advertisement
-->

I would quickly glance at the road to ensure everything was okay, then look back down at my phone, spending enough time looking at a post on Instagram, X, or Facebook to determine what it was about, before then peeking at the road again.

There was once again no alert to look at the road, and I started to question whether I was even looking at my phone long enough to get an alert:

Based on past versions of Full Self-Driving, especially dating back to v13, even looking out the window for too long would get me a nudge, and it was about the same amount of time, sometimes more, sometimes less, I would look out of a window to look at a house or a view.

Advertisement
-->

High Congestion Area

I decided to use the highway as a High Congestion Area, and it finally gave me an alert to look at the road.

As strange as it is, I felt more comfortable looking down at my phone for a longer amount of time on the highway, especially considering there is a lower chance of a sudden stop or a dangerous maneuver by another car, especially as I was traveling just 5 MPH over in the left lane.

This is where I finally got an alert from the driver monitoring system, and I immediately put my phone down and returned to looking at the road:

Advertisement
-->

Once I was able to trigger an alert, I considered the testing over with. I think in the future I’d like to try this again with someone else in the car to keep their eyes on the road, but I’m more than aware that we can’t always have company while driving.

My True Thoughts

Although this is apparently enabled based on what was said, I still do not feel totally comfortable with it. I would not ever consider shooting a text or responding to messages because Full Self-Driving is enabled, and there are two reasons for that.

The first is the fact that if an accident were to happen, it would be my fault. Although it would be my fault, people would take it as Tesla’s fault, just based on what media headlines usually are with accidents involving these cars.

Secondly, I am still well aware that it’s against the law to use your phone while driving. In Pennsylvania, we have the Paul Miller Law, which prohibits people from even holding their phones, even at stop lights.

I’d feel much more comfortable using my phone if liability were taken off of me in case of an accident. I trust FSD, but I am still erring on the side of caution, especially considering Tesla’s website still indicates vehicle operators have to remain attentive while using either FSD or Autopilot.

Advertisement
-->

Check out our full test below:

Continue Reading

Elon Musk

Tesla CEO Elon Musk announces major update with texting and driving on FSD

“Depending on context of surrounding traffic, yes,” Musk said in regards to FSD v14.2.1 allowing texting and driving.

Published

on

Credit: carwow/YouTube

Tesla CEO Elon Musk has announced a major update with texting and driving capabilities on Full Self-Driving v14.2.1, the company’s latest version of the FSD suite.

Tesla Full Self-Driving, even in its most mature and capable versions, is still a Level 2 autonomous driving suite, meaning it requires attention from the vehicle operator.

You cannot sleep, and you should not take attention away from driving; ultimately, you are still solely responsible for what happens with the car.

The vehicles utilize a cabin-facing camera to enable attention monitoring, and if you take your eyes off the road for too long, you will be admonished and advised to pay attention. After five strikes, FSD and Autopilot will be disabled.

However, Musk announced at the Annual Shareholder Meeting in early November that the company would look at the statistics, but it aimed to allow people to text and drive “within the next month or two.”

Advertisement
-->

He said:

“I am confident that, within the next month or two, we’re gonna look at the safety statistics, but we will allow you to text and drive.”

Advertisement
-->

Today, Musk confirmed that the current version of Full Self-Driving, which is FSD v14.2.1, does allow for texting and driving “depending on context of surrounding traffic.”

There are some legitimate questions with this capability, especially as laws in all 50 U.S. states specifically prohibit texting and driving. It will be interesting to see the legality of it, because if a police officer sees you texting, they won’t know that you’re on Full Self-Driving, and you’ll likely be pulled over.

Some states prohibit drivers from even holding a phone when the car is in motion.

Advertisement
-->

It is certainly a move toward unsupervised Full Self-Driving operation, but it is worth noting that Musk’s words state it will only allow the vehicle operator to do it depending on the context of surrounding traffic.

He did not outline any specific conditions that FSD would allow a driver to text and drive.

Continue Reading

News

Tesla Semi just got a huge vote of confidence from 300-truck fleet

The confidential meeting marks a major step for the mid-sized carrier in evaluating the electric truck for its regional routes.

Published

on

Credit: Tesla

The Tesla Semi is moving closer to broader fleet adoption, with Keller Logistics Group wrapping up a key pre-production planning session with the electric vehicle maker’s team this week. 

The confidential meeting marks a major step for the mid-sized carrier in evaluating the electric truck for its regional routes.

Keller’s pre-production Tesla Semi sessions

Keller Logistics Group, a family-owned carrier with over 300 tractors and 1,000 trailers operating in the Midwest and Southeast, completed the session to assess the Tesla Semi’s fit for its operations. The company’s routes typically span 500-600 miles per day, positioning it as an ideal tester for the Semi’s day cab configuration in standard logistics scenarios. 

Details remain under mutual NDA, but the meeting reportedly focused on matching the truck to yard, shuttle and regional applications while scrutinizing economics like infrastructure, maintenance and incentives.

What Keller’s executives are saying

CEO Bryan Keller described the approach as methodical. “For us, staying ahead isn’t a headline, it’s a habit. From electrification and yard automation to digital visibility and warehouse technology, our teams are continually pressure-testing what’s next. The Tesla Semi discussion is one more way we evaluate new tools against our standards for safety, uptime, and customer ROI. We don’t chase trends, we pressure-test what works,” Keller said. 

Advertisement
-->

Benjamin Pierce, Chief Strategy Officer, echoed these sentiments. “Electrification and next-generation powertrains are part of a much broader transformation. Whether it’s proprietary yard systems like YardLink™, solar and renewable logistics solutions, or real-time vehicle intelligence, Keller’s approach stays the same, test it, prove it, and deploy it only when it strengthens service and total cost for our customers,” Pierce said. 

Continue Reading