Connect with us

News

SpaceX Falcon 9 booster spied on highway as triple-satellite launch moves right

Reddit user intamin1 spotted a Falcon 9 booster northbound between Hawthorne and Vandenberg on Jan 22. (Reddit /u/intamin1)

Published

on

A SpaceX Falcon 9 booster was spotted heading north from the company’s Hawthorne, California factory on January 22nd, signifying a likely shipment of the flight-proven rocket that will help launch Canada’s trio of Radarsat Constellation Mission satellites.

Delayed from mid-February to early March 2019 after an unplanned landing anomaly damaged the Falcon 9 originally assigned to the mission, the shipment of a different booster to Vandenberg Air Force Base (VAFB) helps to narrow down the rocket now likeliest to launch the Canadian Space Agency’s (CSA) radar satellite constellation.

https://twitter.com/GoForStaging/status/1088174203298230272

Do the Booster Shuffle!

Thanks to a hydraulic pump failure that led Falcon 9 B1050 to land (albeit softly and in one piece) in the Atlantic Ocean last December, the imminent launch of two booster-dense Falcon Heavy missions, and the thus far schedule-shy orbital launch debut of Crew Dragon, SpaceX’s fleet of available boosters – all flight-proven – can be succinctly summarized as “B1046 thru B1049”.

B1050’s future is uncertain after suffering a smashed interstage and soaking in salt water for several days, while B1051 is definitively assigned to Crew Dragon’s orbital launch debut, known as Demo-1 (DM-1). Falcon 9 B1052 and B1053 are unknown quantities and B1054 was expended after a high-value US Air Force launch, also SpaceX’s final mission of 2018. It’s probably safe to bet that B1052, B1053, and B1055 will be the next three boosters to support a Falcon Heavy launch (or two), currently NET March and April 2019. All three of those Falcon Heavy (FH) boosters have completed static fire tests in Texas and both side boosters arrived at SpaceX’s Florida facilities within the last ~6 weeks.

Advertisement
-->

 

Assuming that Falcon Heavy Flight 2 and 3 use the same exact boosters, SpaceX production technicians and engineers may already be nearing the completion of another Falcon 9 booster (B1056, presumably) at the Hawthorne factory, although they are likely 1-2 weeks away from that milestone. If, Falcon Heavy Flight 3 (presumed to be the USAF’s STP-2 mission) does not reuse all three first stage boosters from Flight 2 (commercial payload Arabsat 6A), then Hawthorne will have to build, ship, and test anywhere from 1-3 additional boosters between now and April 2019. In the latter scenario, all unflown – mid-build or completed – Falcon boosters would be ‘claimed’ between now and March or April.

Put in another way, short of opting for a delay that could stretch 1-4 months or longer, the Canadian Space Agency (CSA) and Radarsat prime contractor MDA will have to accept one of SpaceX’s flight-proven Falcon 9s.

Falcons on wheels

Thanks to SpaceX’s trusty and well-worn method of using good old trucks and roads to transport Falcon 9 and Heavy boosters, upper stages, fairings, landing legs, and much more cross-country, spaceflight fans have long taken advantage of opportunities – rare and fleeting as they might be – to spot and track SpaceX hardware on public roads. Put simply, a lot of people are excited about SpaceX or are at least familiar and curious enough to know someone to share a photo or observation with. As a result, the community averages dozens of ‘core spottings’ per year. With a little intuition, the process of elimination, a few sources, and some wild guesses, this allows unofficial fans to (very roughly) paint a picture of SpaceX’s fleet of rockets.

 

Advertisement
-->

For example, the Falcon 9 spotted in Valencia, CA on January 22nd by Reddit user intamin1 could theoretically be any SpaceX booster currently in existence. By knowing the rough state of SpaceX’s fleet (as described above) and observing that the booster was northbound between Hawthorne, CA (the factory) and Vandenberg Air Force Base (VAFB) on Jan 22, a great deal can be intuited. Bound for SpaceX’s West Coast launch complex (SLC-4), it ought to be flightworthy. Knowing that a Falcon Heavy center booster was on SpaceX’s McGregor, Texas static fire stand on January 10th means that the spotted booster can’t (or at least shouldn’t) be coming from Texas, as Falcon Heavy has no known launches planned from VAFB. The process of testing, inspecting, and preparing Falcon boosters for cross-country shipment is also not easily rushed.

On the East Coast, SpaceX needs to launch communications satellite PSN-6 and Spaceflight rideshare GTO-1 in mid to late February. With no new boosters expected to be easily available for months and PSN-6/GTO-1 already entering into the phases of payload fueling, integration, and fairing encapsulation, it can be all but guaranteed that a flight-proven booster was assigned to the mission months ago and is now nearly ready for its third flight somewhere in Cape Canaveral, FL.

SpaceX manufactures Falcon 9 and Heavy at its Hawthorne, CA factory. (SpaceX)

Given that B1046 and B1049 are on the West Coast after conducting launches from VAFB and that B1050 is out of circulation for the time being, only B1047 and B1048 remain (in theory) on the East Coast, both having flown two missions. B1048 was recently spotted and confirmed in photos of SpaceX’s Pad 39A integration hangar, although Falcon 9 B1051 and the first orbit-ready Crew Dragon were the center of attention.

B1047 completed its second launch in mid-November 2018 and returned to one of SpaceX’s Florida hangars for refurbishment around Nov 21. Unless any number of locals and bystanders somehow missed it, neither booster has left the Cape since arriving. Meanwhile, B1048 is currently the best-known candidate at hand for SpaceX’s Crew Dragon In-Flight Abort (IFA) test, expected to occur no earlier than spring 2019 and entirely dependent upon the successful launch, reentry, recovery, and refurbishment of the DM-1 capsule to proceed. As a result, the only booster that is realistically available for PSN-6/GTO-1 is Falcon 9 B1047 for what would be its third launch.

Assuming B1048 did not manage to make it from Cape Canaveral to Central California without a single spotting, the only rockets available for the RCM mission are B1046 and B1049. B1049 completed its second launch – Iridium-8 – just weeks ago and returned by drone ship to Port of LA on January 13th, whereas Falcon 9 B1046 – after completing its historic third launch – completed recovery and was snug in a Hawthorne, CA refurbishment bay by December 17th, 2018. Going off of Occam’s Razor, B1046 is the clear victor for the launch of RCM, although a ~60-90-day turnaround for the already thrice-flown booster could be a stretch. B1049, however, would have barely a single month for refurbishment and inspections.

In the last week or two, RCM stakeholders were provided an updated launch target, delaying the mission by approximately two weeks to a window that begins February 28th with the implication being that the launch is now expected NET early March. If that date is recent and from SpaceX, B1046 is the most practical option, with B1049 thus filling its refurbishment bay in Hawthorne, CA around the same day. If a risk of a 30-day or greater delay is tolerable for CSA and MDA, then B1049.3 would likely be a more optimal fit for their risk tolerance profile. Time will tell!


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

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