Starship Mishap Investigations: COPV Fault and Cruise-Ship Video

Two investigations, one pattern

SpaceX's Starship program has spent much of its life moving fast and breaking hardware, and the paper trail behind those breakages is becoming clearer. Two threads now run side by side. One is SpaceX's own account of what destroyed Ship 36. The other is a set of federal records showing how investigators reconstructed the breakup of Starship Flight 7, partly with the help of vacationers holding phones.

On Ship 36, SpaceX says early analysis points to a failed composite overwrapped pressure vessel, or COPV. The tank held gaseous nitrogen and sat in the vehicle's nosecone area, though the company stresses that its full data review is still underway 1. SpaceX also moved quickly to say that the COPVs flying on Starship share no commonality with those on its Falcon rockets 1. That clarification matters. Falcon 9 carries astronauts to the International Space Station, including a recent four-person crew bound for a stay of up to six months 4.

Vacation footage as forensic evidence

The second thread comes from FAA records that ProPublica obtained through a Freedom of Information Act request. According to those records, SpaceX folded bystander video into its analysis of debris from the Flight 7 breakup over the Caribbean 2. The footage came from three vantage points: a Disney cruise ship, a Royal Caribbean vessel and a Club Med resort. People there were filming what looked like a light show 2.

The FAA ultimately blamed the loss on stronger-than-expected vibrations that stressed propulsion hardware 2. Investigators confirmed one report of minor vehicle damage in the Turks and Caicos Islands, and no public injuries were reported 2.

Gadget Review argues that using tourist footage raises hard questions about how well SpaceX's formal tracking held up at the moment it mattered most 2. That is a fair question. It is also not the same as proof of failure. Once a vehicle breaks apart, telemetry from the vehicle itself naturally stops. Outside observation is then one of the few ways left to map where fragments went. In this reading, the videos signal less a broken system than a gap in tracking. Crowd-sourced imagery is filling that gap, and it should eventually be filled by instruments designed for the job.

The official framing

SpaceX's public account stresses process and coordination. The company says it led investigation work with FAA oversight and with participation from NASA, the National Transportation Safety Board and the U.S. Space Force 1. It also says it submitted a mishap report and received a flight safety determination clearing its next Starship flight 1.

For flights from Florida's Space Coast, SpaceX describes a response plan prepared in advance with the FAA and air traffic control, which took effect right after an anomaly 1. According to the company, all debris fell inside a pre-planned response area, no hazardous materials were present, and no significant harm to marine life or water quality is expected 1.

The two accounts are not contradictory, but they emphasize different things. SpaceX describes a contained, well-rehearsed process. The FOIA records show that improvisation, including cruise-ship video, was part of how that process actually worked over populated Caribbean waters.

Progress keeps outrunning the paperwork

All of this is unfolding as Starship's hardware advances. The V3 generation, powered by Raptor 3 engines, has now flown three times, and each flight brought both milestones and new faults:

• Flight 12 (May 2026): The first V3 flight ended with the ship splashing down in the Indian Ocean. The booster failed to relight for its boostback burn and hit the water hard, which triggered an FAA mishap finding 3.
• Flight 13 (July 2026): All 20 suborbital Starlink V3 satellites were deployed. This came after an earlier attempt was aborted when four Raptors failed to ignite 3.
• Flight 14 (September 2026): Starship reached orbit for the first time, carrying 26 Starlink V3 satellites, but a booster engine and a Raptor Vacuum shut down early 3. The BBC reported that a mission planned for about 10 hours was ended after roughly 90 minutes, finishing in a fiery splashdown 4.

Inside Deep Tech notes that steep cost-reduction claims depend on catching and quickly reflying both stages. As of October 2026, V3 had caught neither 3.

The takeaway

The picture that emerges is a program whose engineering is maturing faster than its accident accounting. Pinning the Ship 36 loss on a nitrogen COPV is a specific, fixable finding, if the data confirms it. The Flight 7 records point to a broader issue. As Starship flies more often and over busier skies and seas, regulators and SpaceX will need debris-tracking systems that do not depend on whoever happens to be filming from a cruise ship deck.