News
SpaceX a big step closer to orbital Starship launches after passing FAA environmental review
SpaceX has secured environmental approval from the FAA and relevant federal, state, and local stakeholders to conduct orbital Starship launches on the South Texas coast.
After a relatively normal 12 months of work and half a dozen poorly communicated delays, the FAA has ultimately issued SpaceX an extremely favorable “Mitigated Finding of No Significant Impact” or Mitigated FONSI for its plans to conduct a very limited number of orbital Starship launches per year out of Boca Chica, Texas. With the receipt of that final programmatic environmental assessment (PEA), SpaceX has arguably hurdled the most difficult regulatory barrier for Texas orbital Starship launches and secured itself a foundation upon which it should be able to attempt to expand the scope of Starbase’s long-term utility.
To secure that favorable result, however, SpaceX ultimately agreed to dozens upon dozens of “mitigations” that will take a significant amount of work to complete and maintain in order to partially alleviate some of the launch site’s environmental impact. It’s also far from the last regulatory hurdle standing between SpaceX and orbital Starship launches.
In many ways, Starbase’s Final PEA is a bit simpler than what SpaceX initially requested in its September 2021 draft. As previously discussed, it was already known that SpaceX had withdrawn initial plans to build its own dedicated natural gas power plant, desalination plant, and natural gas refinery and liquefaction facilities at or near the launch site before the draft was finalized. The Final PEA goes a bit further, simplifying SpaceX’s initial request for two “phases” of annual Starship launch operations and settling on a single “operational phase” that allows up to five suborbital and five orbital Starship launches per year.
However, aside from the already expected removal of onsite methane fuel production and all associated facilities, the rest of the Final PEA appears to be surprisingly close – if not outright identical – to SpaceX’s Starbase Draft PEA. Crucially, SpaceX was not forced to reduce the number of permitted orbital launches, suborbital launches, or ship/booster static fire tests it originally pursued. While a maximum of five orbital launches will severely limit Starbase’s utility outside of early flight testing, it’s still a big improvement over a compromise for 1-4 annual launches.


Perhaps even more notably, the Final PEA also includes permission for up to 500 hours of highway closures for nominal operations and up to 300 hours of closures for emergency anomaly response per year – exactly what SpaceX requested in its Draft PEA. In 2014, SpaceX completed an even more thorough environmental impact statement (EIS) for Falcon rocket launches out of Boca Chica and received approval for no more than 180 hours of annual closures – a restriction that could have made Starbase virtually unusable as a hub for Starship development.
Of the dozens of mitigations SpaceX will have to implement to conduct Starship launches under its new Starbase PEA, a majority appear to be normal and reasonable. Most focus on specific aspects of things already discussed, like protecting turtles (lighting, beach cleanup, education, nest scouting and monitoring, etc.), safeguarding other protected species, respecting impacted areas of historical importance; ensuring that road closures avoid certain holidays and periods to limit Starbase’s impact on local use of public parks and beaches; and other common-sense extensions of existing rules and regulations. In a few cases, SpaceX has even agreed to deploy solar-powered Starlink internet terminals to enable “enhanced satellite monitoring” of wildlife for the US Fish and Wildlife Service and Peregrine Fund.
Others are oddly specific and read a bit more like local and state agencies taking advantage of their leverage to get SpaceX to manage and pay for basic infrastructure maintenance and improvement that any functional government should already be doing. The lengthy list of odd “mitigations” includes the following:
- Quarterly beach and highway cleanups
- Construct at least one highway wildlife crossing
- Construct a wildlife viewing platform along Highway 4
- Complete and maintain traffic control fencing demarcating the boundaries of TPWD land along said public highway
- $5,000 per year to “enhance” the Texas Parks and Wildlife Department’s (TPWD) fishing “Tackle Loaner Program”
- Prepare a history report on any events and activities of the Mexican War and Civil War that took place in all affected areas of historical importance
- Fund the development of five signs explaining the “history and significance” of those areas
- “[Replicate and install] the missing stars and wreaths on the Palmetto Pilings Historical Marker”
Ultimately, the Final PEA SpaceX received is an extremely positive outcome, and there should be little doubt that SpaceX will complete all mitigations requested of it and help improve aspects of Boca Chica, Texas as a result. Up next, SpaceX will need to secure an orbital Starship launch license from the FAA by demonstrating, to the agency’s satisfaction, that it meets “safety, risk, and financial responsibility requirements” in addition to all environmental requirements. The company has already begun that process with the FAA, but it could still take weeks or months after the Final PEA to secure an operator license or experimental permit. Any such license or permit will be conditional upon the completion of all mitigation requirements established by the PEA.
News
Tesla Full Self-Driving release in the EU gets delayed
Tesla Full Self-Driving’s release in Europe is set to be delayed by at least a few months.
The European Union will not vote on Tesla’s Full Self-Driving (Supervised) on October 6. The draft agenda for the 119th meeting of the Technical Committee on Motor Vehicles lists only a 25-minute “continuation of discussions” on the Netherlands’ Article 39 request, not a decision. The next scheduled TCMV session is in December, which is now the earliest date a bloc-wide vote could occur.
Tesla Europe had pointed to October 6 as a possible EU-wide vote after the Dutch vehicle authority RDW granted the first European type approval on April 10.
That approval, under UN Regulation 171 plus an Article 39 exemption in EU Regulation 2018/858, is the legal file other member states have been recognizing one by one. The same committee has already discussed the request twice without voting.
Elon Musk’s reply to the delay was a single word: “Sigh.”
Sigh
— Elon Musk (@elonmusk) September 25, 2026
Seven EU countries have now cleared FSD Supervised on their own roads: the Netherlands, Lithuania, Estonia, Denmark, Belgium, Slovenia, and Czechia. Those seven states represent about 53 million people, or roughly 12 percent of the EU population. An EU-wide authorization still needs a qualified majority: at least 15 of 27 member states representing 65 percent of the bloc’s population, about 292 million people.
Germany, France, Italy, and Spain remain the decisive markets. France has already rejected the current system; several other governments have flagged speed-limit compliance as the main sticking point.
The safety case Tesla is putting in front of those governments is now public. On September 1, Tesla Europe said FSD Supervised was in use by more than 70,000 customers, covering over 1 million kilometers a day, and was 4.1 times less likely to be involved in a crash than manual driving across 100 million kilometers on EU public roads.
An earlier mid-year cut of the same fleet data, covering 65 million kilometers in five approved countries, put the collision advantage at 5.2 times, with zero highway collisions over 41.9 million kilometers. Tesla also reported far fewer automatic emergency braking events, harsh accelerations, and hard swerves than in comparable manual Tesla driving. Those figures are company-reported, not independently audited.
Tesla Full Self-Driving is taking over Europe: fourth country gets FSD approval
The public-health backdrop is harder to dispute. European countries recorded about 19,400 road deaths in 2025, or roughly 53 a day, most of them attributed to human error. FSD Supervised is not unsupervised autonomy; the driver remains legally responsible. But the software is already legal and in daily use across seven member states.
Until TCMV votes, the rest of the EU remains a patchwork: available in Prague and Amsterdam, locked behind review in Paris and Berlin. December is now the next chance to close that gap.
News
SpaceX readies Starship Flight 14 for a historic journey into uncharted territory
SpaceX finished Starship’s Flight 14 rehearsal, clearing the way for its first orbital flight Monday.
SpaceX has cleared one of the last hurdles before Starship’s first trip to orbit. The company posted on X Thursday afternoon that its launch rehearsal for Flight 14 was complete, keeping the mission on track for Monday, September 28. The launch window opens at 7:15 a.m. CT at Starbase, Texas, and runs for 75 minutes.
A wet dress rehearsal is essentially launch day without the launch. Crews fill Booster 21 and Ship 41 with thousands of tons of extremely cold propellant, run the countdown nearly to ignition, then drain everything back out. It lets engineers catch leaks or equipment problems before anything leaves the pad. SpaceX still needs a launch license from the FAA before the stack, which stands 407 feet tall, can fly.
Flight 14 matters because of where it is going. All 13 previous Starship flights followed a suborbital path, which works like throwing a ball extremely high and far: the vehicle reaches space, but it is always on a course that brings it back down within about an hour. This time, Ship 41 will perform a short engine firing called an orbital insertion burn roughly 25 minutes after liftoff, giving it enough speed to keep falling around Earth instead of back into it. SpaceX plans about six laps at an altitude near 275 kilometers (171 miles) over nearly 10 hours, as Teslarati detailed when the mission was first announced.
Launch rehearsal complete ahead of Starship Flight 14 pic.twitter.com/h5LBYyBqi4
— SpaceX (@SpaceX) September 24, 2026
Getting into orbit also means Starship has to prove it can get back out. The ship must relight a single Raptor engine in space to slow down for reentry. SpaceX says it will only attempt the orbital insertion burn after flight controllers confirm the hardware needed for that return burn has enough backup, and its flight plan includes health checks that could shorten the mission to two or five orbits.
Flight 14 is also the first to put working satellites into service. Flight 13 carried 20 Starlink V3 satellites in July, but they came back down with the ship because that mission never reached orbit. This time, 26 V3 satellites are meant to stay up and join the constellation within a few weeks. Together they add about 26 terabits per second of network capacity, which SpaceX says is roughly 10 times what a single Falcon 9 launch of older V2 Mini satellites adds. Three of them carry cameras that will photograph Starship’s heat shield in orbit to check for tile damage before reentry.
The hardware has changed too. Ship 41 flies with extra fasteners on tiles in the most vulnerable areas, fixes for gaps where superheated plasma slipped behind tiles, and curved tiles designed to reduce heating between them. Two tiles recovered from Ship 40 will fly again, the first reuse of any part of a Starship heat shield. Booster 21 carries better engine filtering and new relight software after ice clogged three center engines on the previous booster, leaving only eight of 13 engines to restart for its landing burn.
Ship 41 is targeting a splashdown in the Pacific Ocean west of Chile, a new recovery zone after several Indian Ocean landings, while Booster 21 aims for the Gulf. Neither will be caught by the tower on this flight. Elon Musk said in August that a ship catch was likely “in a few months.”
Elon Musk
Google just picked SpaceX for its first step into orbital AI
Google will launch its first Project Suncatcher AI satellite on SpaceX’s Transporter-18 rideshare next week.
Google is about to put its own AI chips into orbit for the first time, and it is paying SpaceX to get them there.
The company said Thursday that the first in-orbit test of Project Suncatcher, its research effort to find out whether space can host large-scale AI computing, will fly next week on SpaceX’s Transporter-18 rideshare mission.
The satellite, called MVP, is about the size of a refrigerator and carries four of Google’s Tensor Processing Units, the same chips Google runs in its ground data centers. Google originally planned to launch two custom satellites in 2027, but chose to move faster by integrating its chips into a satellite.
MVP’s solar panels supply about one kilowatt of power, and Google will run Gemini models on the TPUs only in bursts of roughly 15 minutes before the chips shut down so the radiators can shed heat. In a blog post, Google said its Trillium TPUs survived vibration testing that mimicked sustained launch loads of up to 10g, with individual components seeing 50 to 100g, and handled a radiation dose greater than a five year mission would deliver.
SpaceX and Google mull massive partnership on Musk’s orbital data dream: report
Next week’s flight, slated for October 1, follows a relationship that became public in May, when Teslarati reported that Google was in talks with SpaceX for a launch deal tied to orbital data centers. Google also holds a stake of roughly 6% in SpaceX.
The two companies are chasing the same idea from very different starting points. SpaceX’s own orbital compute program is built around the AI1 satellite, a roughly 70 meter structure derived from Starlink V3 hardware that is designed for 150 kW of peak compute, about 150 times the power MVP will draw. Elon Musk has brushed off concerns about crowding orbit with those satellites, and SpaceX is building its Gigasat factory in Bastrop, Texas, to produce them, targeting an annualized rate of about 1 GW of space compute by the end of 2027.
Musk also posted on X on Thursday that “the amount of compute in space will obviously round up to 100% of all compute.”
Google has been more cautious in public. Its research estimates that launch prices need to fall below about $200 per kilogram before an orbital data center can compete with a ground facility on energy cost, a threshold the company believes could be reached around the mid 2030s. The Suncatcher team has said it expects the effort to remain a project rather than a product for years, which leaves the first real test of its hardware riding on a rocket from the company with the most aggressive timeline in the field.