Connect with us

News

US Air Force awards SpaceX $20m contract to support its biggest spy satellites

Published

on

Slipping beneath the watchful eye of many skilled defense journalists, the government contracting database FPDS.gov indicates that the US Air Force awarded SpaceX more than $20 million in November 2017 to conduct a design study of vertical integration capabilities (VIC). Describing what exactly this means first requires some background.

Vertical whaaaat?

The flood of acronyms and technical terminology that often follow activities of the Federal government should not detract from the significance of this contract award. First and foremost, what exactly is “vertical integration” and why is significant for SpaceX? Not to be confused with more abstract descriptions of corporate organization (vertical integration describes one such style), integration here describes the literal process of attaching satellite and spacecraft payloads to the rockets tasked with ferrying them to orbit.

Likely as a result of its relative simplicity, SpaceX has used a system of horizontal integration for as long as they have been in the business of launching rockets, be it Falcon 1, Falcon 9, or Falcon Heavy. In order to integrate payloads to the rocket horizontally, SpaceX has a number of horizontal integration facilities (HIF) directly beside each of their three launch pads – two in Florida, one in California. After being transported from the company’s Hawthorne, CA rocket factory, Falcon 9 and Heavy boosters, second stages, payload fairings, and other miscellaneous components are all brought into a HIF, where they are craned off of their transporters (a semi-trailer in most cases) and placed on horizontal stands inside the building.

While in the HIF, all three main components are eventually attached together (integrated). The booster or first stage (S1) has its landing legs and grid fins installed soon after arrival at the launch site, followed by the mating of the first and second stages. Once these two primary components of the rocket are attached, the entire stack – as the mated vehicle is called – is once again lifted up by cranes inside the facility and placed atop what SpaceX calls the strongback (also known as the Transporter/Launcher/Erector, or TEL). A truly massive steel structure, the TEL is tasked with carrying the rocket to the launch pad, typically a short quarter mile trek from the integration facility. Once it reaches the pad, the TEL uses a powerful hydraulic lift system to rotate itself and its rocket payload from horizontal to vertical. It may look underwhelming, but it serves to remember that a complete Falcon 9/Heavy and its TEL are both considerably more than twice as tall as a basketball court is long.

Advertisement
-

Once at the pad, the TEL serves as the rocket’s connection to the pad’s many different ground systems. Crucially, it is tasked with loading the rocket with at least four different fuels, fluids, and gases at a broad range of temperatures, as well as holding the rocket down with giant clamps at its base, providing connection points to transmit a flood of data back to SpaceX launch control. SpaceX’s relatively unique TEL technology is to some extent the foundation of the company’s horizontal integration capabilities – such a practice would be impossible without reliable systems and methods that allow the rocket to be easily transported about and connected to pad systems.

Still, after the Amos-6 mishap in September 2016, which saw a customer’s payload entirely destroyed by a launch vehicle anomaly ahead of a static fire test, SpaceX has since changed their procedures, and now conducts those static fire tests with just the first and second stages – the payload is no longer attached until after the test is completed. For such a significant decrease in risk, the tradeoff of an additional day or so of work is minimal to SpaceX and its customers. Once completed, the rocket is brought horizontal and rolled back into the HIF, where the rocket’s payload fairing is finally attached to the vehicle while technicians ensure that the rocket is in good health after a routine test-ignition of its first stage engines.

Before being connected to the rocket, the payload itself must also go through its own integration process. Recently demonstrated by a flurry of SpaceX images of Falcon Heavy and its Roadster payload, this involves attaching the payload to a payload adapter, tasked with both securing the payload and fairing to the launch vehicle. Thankfully, the fairing is far smaller than the rocket itself, and this means it can be vertically integrated with the payload and adapter. The final act of joining and bolting together the two fairing halves is known as encapsulation – at which point the payload is now snug inside the fairing and ready for launch. Finally, the integrated payload and fairing are lifted up by cranes, rotated horizontally, and connected to the top of the rocket’s second stage, marking the completion of the integration process.

A different way to integrate

Here lies the point at which the Air Force’s $20m contract with SpaceX comes into play. As a result of certain (highly classified) aspects of some of the largest military satellites, the Department of Defense (DoD) and National Reconnaissance Office (NRO) prefer or sometimes outright require that their payloads remain vertical while being attached to a given rocket. The United Launch Alliance (ULA), SpaceX’s only competition for military launches, almost exclusively utilizes vertical integration for all of their launches, signified by the immense buildings (often themselves capable of rolling on tracks) present at their launch pads. SpaceX has no such capability, at present, and this means that they are effectively prevented from competing for certain military launch contracts – contracts that are often the most demanding and thus lucrative.

It’s clear that the Air Force itself is the main impetus pushing SpaceX to develop vertical integration capabilities, a reasonable continuation of the military’s general desire for assured access to orbit in the event of a vehicle failure grounding flights for the indefinite future. For example, if ULA or SpaceX were to suffer a failure and be forced to ground their rockets for months while investigating the incident, the DoD could choose to transfer time-sensitive payload(s) to the unaffected company for the time being. With vertical integration, this rationale could extend to all military satellites, not simply those that support horizontal integration.

Fittingly, the ability to vertically integrate satellites is likely a necessity if SpaceX hopes to derive the greatest possible value from its recently and successfully introduced Falcon Heavy rocket, a highly capable vehicle that the government is likely very interested in. Although the specific Air Force contract blandly labels it a “Design Study,” (FPDS.gov account required) its hefty $21 million award may well be far more money than SpaceX needs to design a solution. In fact, knowing SpaceX’s famous ability to develop and operate technologies with exceptional cost efficiency, it would not be shocking to discover that the intrepid launch company has accepted the design study grant and instead jumped head-first into prototyping, if not the construction of an operational solution. More likely than not, SpaceX would choose to take advantage of the fixed tower (known as the Fixed Service Structure, FSS) currently present at Pad 39A, atop which a crane and work platforms could presumably be attached

Advertisement
-

Intriguingly, it is a real possibility that Fairing 2.0 – its first launch scheduled to occur as early as Feb. 21 – could have been upgraded in part to support present and future needs of the Department of Defense, among numerous other benefits. Fairing 2.0’s larger size may have even been precipitated by physical requirements for competing for and dealing with the largest spysats operating by the DoD and NRO, although CEO Elon Musk’s characterization of that change as a “slightly larger diameter” could suggest otherwise. On the other hand, Musk’s offhand mention of the possibility of significantly lengthening the payload fairing is likely aimed directly at government customers in both the civil and military spheres of space utilization. Time will tell, and it certainly will not hurt SpaceX or its customers if Fairing 2.0 is also considerably easier to recover and reuse.

Ultimately, it should come as no surprise that SpaceX would attempt to leverage this contract and the DoD’s interest in ways that might also facilitate the development of the company’s futuristic BFR rocket, intended to eventually take humans to the Moon, Mars, and beyond. As shown by both 2016 and 2017 iterations of the vehicle, it appears that SpaceX intends to use vertical integration to attach the spaceship (BFS) to the booster (BFR). While it’s unlikely that this Air Force contract will result in the creation of a vertical integration system that could immediately be applied to or replicated for BFS testing, the experience SpaceX would gain in the process of building something similar for the Air Force would be invaluable and essentially kill two birds with one stone.

While now outdated, SpaceX’s 2016 Mars rocket featured a giant crane used for vertical integration. BFR appears to use the same approach. (SpaceX)

Follow along live as I and launch photographers Tom Cross and Pauline Acalin cover these exciting proceedings live and in person.

Teslarati   –   Instagram – Twitter

Tom Cross – Twitter

Advertisement
-

Pauline Acalin – Twitter

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

Investor's Corner

SpaceX reveals how its 1 Million AI satellite network will work and prevent space collisions

SpaceX reveals plans for one million Starmind AI satellites and calls out operators hiding maneuvers.

Published

on

By

Concept rendering of SpaceX Starmind constellation via Grok
Concept rendering of SpaceX Starmind constellation via Grok

SpaceX has put the largest satellite count it has ever published into writing, and it says that plan only works if every other operator in orbit starts sharing what it knows.

In a new Space Safety page highlighted Tuesday morning by Sawyer Merritt on X, SpaceX said it “plans to operate up to 100,000 Starlink satellites and up to 1 million Starmind AI satellites to meet the growing demand for broadband and supercompute.” Starlink has a little over 11,000 satellites in orbit today, so the target alone implies roughly a ninefold expansion of the broadband network.

Starmind is SpaceX’s orbital AI compute constellation. Elon Musk confirmed the Starmind name in June after an xAI trademark filing surfaced, and in August SpaceX said it was working with Nvidia on the compute payload. The FCC accepted the filing for up to one million satellites back in February.

FCC accepts SpaceX filing for 1 million orbital data center plan

SpaceX also released a new render of what a full Starmind constellation could look like. Alongside it, SpaceX VP Michael Nicolls explained why the satellites will not operate on their own. “We need to operate clusters of satellites in tight formation to get enough coherent compute to run AI models efficiently,” Nicolls said. “A cluster will be 10-ish satellites connected with 10 terabits or so of bandwidth between them, and interconnected to the broader constellation.”

That is the most specific detail SpaceX has given on how Starmind will be built. Instead of a million independent servers, the network would work as tightly packed groups of about 10 satellites acting as one compute unit, with Starlink’s laser links carrying results back to Earth.

Advertisement
-


Packing satellites that close together, at that scale, makes collision avoidance the central problem, and most of the Space Safety page is aimed at other operators. SpaceX said Starlink encountered collision risks with about 650 unique maneuvering third party satellites in 2026, and only about half of them shared data. Over six months, Starlink recorded roughly 164,000 more collision risks where the closest approach came within four hours of an unannounced maneuver.

Some operators keep maneuver plans private over proprietary concerns, while others cannot get government permission to share them. SpaceX called those policies “counterproductive,” saying they “largely only serve to create preventable collision risk between satellites.” Starlink is also offering a free ephemeris sharing and screening platform that returns risk results within a minute, backed by its Stargaze network of 30,000 optical sensors.

The push comes as the Starmind application draws opposition from astronomers and environmental groups. In a September filing with the FCC, SpaceX said each Starmind satellite could weigh up to 4,000 kg, nearly seven times the mass of a Starlink V2 Mini. Musk has brushed off crowding concerns before, telling viewers in June that “space is enormous” and that SpaceX already knows how to run very large constellations safely.

SpaceX’s Starmind page says its Gigasat factory in Bastrop, Texas, is designed to produce AI satellites at scale, with deployment of thousands of units starting as soon as late 2027.

Advertisement
-
Continue Reading

News

Five things that are keeping Tesla Full Self-Driving supervised

Published

on

Credit: Tesla

Tesla Full Self-Driving is really good. I have used it for over 76 percent of my driving since FSD v14 launched around this time last year, equating to about 76 percent of my miles using the suite. It’s truly the only way I prefer to travel, but admittedly I save some of the more fun drives for myself.

Even with all of the great things it has done for me, including saving me from being involved in an accident, there are still a handful of things that it needs to improve on. These issues recur from update to update, and while there have been some improvements, they still give me reasons to either soft or hard intervene.

A soft intervention means an adjustment that is needed without disengaging the suite, like manually using a turn signal to change lanes while the car still operates on FSD. What I’d consider to be a “hard intervention” is anything that requires me to disengage the suite altogether, like missing a turn or performing a maneuver I’m uncomfortable with. Of course, some hard interventions will be subjective.

Here are the five things I’d like to see Tesla really focus on through the final versions of v14 and hope to see completely improved with v15.

Speed Limit Recognition and Adjustment

There are entirely too many instances of FSD traveling at a speed that is just totally outrageous. While some of these events can occur on Hurry Mode, I’ve even had issues with it on Standard from time to time, and despite wanting more aggressive maneuvers or a slight bit of urgency, I don’t want to worry about getting a ticket while doing it.

The two areas I notice it the most are in school zones and on local roads. When a Speed Limit changes from 45 to 35, FSD does not always slow down in a way that would appease local law enforcement. On Hurry, 52-55 is pretty standard for a rate of travel in a 45 MPH zone. When it changes to 35, FSD shows zero urgency to slow down to an appropriate speed.

Advertisement
-

School Zones have been a true pain point, and as recently as last week, I had an issue with it:

Realistically, most Speed Limit issues are a soft intervention, as I simply scroll into a slower Speed Profile to get the car to slow down. School Zones are a hard intervention, as they require me to completely take over and travel at the posted 15 MPH limit. Even on Sloth, it simply does not get down to a low enough speed.

Advertisement
-

Parking

Parking is one thing that has really improved over time, but there are still some pretty considerable hoops Tesla needs to jump through to get it to a point where it can be unsupervised.

Parking preferences seem to be where a lot of these issues will be resolved, as most of my complaints come from the fact that the place FSD chooses to park are usually not where I would personally choose to park. This morning, for example, when I arrived at the gym, FSD chose to park next to a vehicle that was parked with its two tires in the spot that FSD picked.

There were three spots in between that car and the nearest car, so FSD could have chosen the spot that would have given a one-spot buffer between the two vehicles. In a parking lot full of empty spots, don’t be that guy who parks next to a car.

Advertisement
-

Generally, parking performance is vastly improved from where it was a year ago; I rarely am adjusting how it pulls or backs into a spot on v14.3.10, but in earlier versions, I definitely had my problems. It’s gotten really good since, and this version has been the best in terms of parking performance. It’s more about the places FSD choose to park, and not necessarily the parking itself.

There are also no options or map data to allow you to choose a charger at a place like a grocery store if it offers charging. These are things that are a bit more complex, but they will be needed for unsupervised FSD operation.

Navigation

Navigation was always going to be on this list, simply because it is one of the most inconsistent and mind-boggling things about FSD. Even after a year of intervening, sending voice notes, and overriding decisions, FSD still tries to take me out of my neighborhood the wrong way. You cannot turn left out of my neighborhood’s main entrance and exit, only right. Navigation still prompts a left turn out of my neighborhood’s main entrance and exit, instead of going around the neighborhood and exiting where a left turn is legal.

Tesla rolled out Preferred Routes with the Summer Update, and this has resolved some of the issues. I also found my own personal workaround:

Some of the more mind-boggling things that FSD used to do with Navigation have been remedied, but it is still a frequent complaint for me and many other owners. I’d just like to see it adopt those preferred routes more frequently and maybe learn them a little faster.

Certain Highway Behaviors

Highway travel is the most consistent and perhaps FSD’s best use case. There is nothing better than having FSD handle busy highway traffic or just long, monotonous, and boring drives. I love to use it for my trips to the Flight 93 Memorial where I volunteer. When I drove manually, I chose to get a hotel and stay overnight because it’s about a 2.5 hour drive. FSD lets me make the drive, put in a volunteering shift, and drive home, without much fatigue. I have found that this is where FSD is most valuable for me, personally.

However, there are a few things FSD does on the highway that are just weird.

One thing I’ve had issues with as of late is that there will be times when I’m about a mile from my exit, the car is in the left lane and is traveling faster than the traffic in the cruising late. Instead of completing a pass and then getting over with no traffic ahead, the car will sometimes drastically and suddenly slow down, switch to the slow lane, and get behind a vehicle — all with a mile until the exit. On average, I’ll have around one minute from the time I get to my exit if it’s a mile away, because in most cases, I’m traveling somewhere around 60 MPH on the highway.

There is no reason to not complete that last pass, then get into the right lane, and have an unobstructed path to the exit. This is one of the more strange behaviors I’ve seen it do, and it really does feel like a bug. Here’s an example of it from FSD v14.3.7:

Advertisement
-

I ended up overriding the turn signal and using the accelerator to nudge the car to do what I wanted it to do. There was no reason to get in the left lane and add to the congestion in that lane.

Another thing that FSD does frequently is camps in the left lane, especially on Hurry. Cruising in the passing lane is illegal in Pennsylvania, and I know it is not a crime to do that everywhere. However, it is here, and I really wish the car was a little quicker to get over in the left lane when it’s cruising.

Here’s a pretty drastic example I had just a couple weeks back:

Advertisement
-

Recognizing Drastic Changes in Road Condition

I think anyone who has ever used FSD knows that potholes are a huge issue, but so are large bumps or sudden changes in road condition. At the intersection of Kreutz Creek Rd. and Rt. 462 in Hellam, PA the roads are nearly set up as a ramp, and going over it at a speed of over 35 MPH can send your head into the glass roof, your butt off your seat, and a brace for the sudden thud that is inevitably coming when you finally touch back down again.

You can see here I tried to change Speed Profiles quickly, but I did it a tad too late:

Advertisement
-

There are other roads in my area that should not be taken at even the posted Speed Limit because of the damage it could do to your car. Here’s another, where I disengaged FSD altogether:

The recognition of these bumps is so crucial for two main reasons: they can cause injury, and they can cause damage to the car. These are reasons why the suite is supervised and drivers should remain attentive. I could not imagine going over that bump at an excessive speed if I had back issues, or if I were older.

Potholes are rarely recognized and usually require a lead car to avoid them. I had FSD use a lead car to avoid a pretty sizeable manhole cover a few weeks back:

Advertisement
-

Tesla says that there are improvements coming for potholes, so hopefully that means these bumps will also be recognized consistently.

Advertisement
-
Continue Reading

News

SpaceX just locked up a NASA record no other U.S. spacecraft can touch

SpaceX’s Crew-13 Dragon reached the ISS in under eight hours, and NASA confirmed a record.

Published

on

By

spacex-dragon-axiom-ax-4-mission-iss

SpaceX now owns every spot on the list of the five fastest trips a U.S. spacecraft has ever made to the International Space Station, and its newest entry beat the old mark by more than four hours.

Crew Dragon Grace docked to the forward port of the station’s Harmony module at 7:05 p.m. ET on October 1, just 7 hours and 55 minutes after lifting off from Space Launch Complex 40 at Cape Canaveral. NASA confirmed the milestone in a space station blog update, writing that the flight “marked the fastest launch‑to‑docking of a U.S. spacecraft in the history of the International Space Station.”

The previous U.S. record also belonged to Dragon. SpaceX’s uncrewed CRS-31 cargo mission reached the station in a little over 12 hours in November 2024. The fastest crewed trip before last week was Crew-11, which took 14 hours and 43 minutes in August 2025, according to Space.com.

A post that Elon Musk reposted on Monday filled out the rest of the ranking. Behind Crew-13, CRS-31 and Crew-11 sit Axiom’s Ax-2 mission at 15 hours and 35 minutes and NASA’s Crew-4 at 15 hours and 44 minutes. All five flew on Dragon.

SpaceX turned a heralding moment for Starship into its greatest

Crew-13 carried NASA astronauts Jessica Watkins and Luke Delaney, Canadian Space Agency astronaut Joshua Kutryk, and Roscosmos cosmonaut Sergey Teteryatnikov. NASA had projected a docking around 8 p.m. ET, as Teslarati reported the day before launch, and Dragon arrived nearly an hour early. Our launch day coverage noted that the flight was lined up to be the quickest Crew Dragon transit yet.

Advertisement
-

The speed came from timing more than hardware. SpaceX’s Julianna Scheiman said the station “was in an opportune spot in space,” which let Dragon start closing the gap almost immediately after reaching orbit. “This is close to the fastest it could be,” she added. Most Crew Dragon flights still take close to a day, using a series of Draco thruster burns to raise and phase their orbit before arrival.

Dragon’s next job at the station is a departure. NASA said Monday it is targeting 8:05 a.m. ET on Wednesday, October 7, for Crew-12 to undock, setting up a splashdown off the coast of California around 11:34 a.m. on Thursday. Clearing that port makes room for CRS-35, a cargo Dragon carrying the final set of iROSA solar arrays.

Dragon remains NASA’s only operational ride to the station while Boeing’s Starliner stays grounded, and the agency recently added Crew-15, Crew-16 and Crew-17 to SpaceX’s contract in a $946 million modification.

Continue Reading