Starlink Satellite 35956 Suffers Anomaly, Releases Trackable Debris

SpaceX reported that Starlink satellite serial 35956 experienced an in orbit anomaly on December 17 while operating at roughly 418 kilometers altitude. The company said communications with the vehicle were lost as the propulsion tank vented, the satellite underwent a rapid decay in its semi major axis by about four kilometers, and a small number of trackable objects were liberated from the parent vehicle. SpaceX said engineers are investigating and that the vehicle will burn up in the atmosphere within weeks.

The satellite had been launched on November 23, placing it on orbit for only a few weeks before the event. SpaceX said it is coordinating with the U.S. Space Force and NASA and that national space tracking authorities are monitoring the pieces. The company also said the anomaly posed no threat to the crew of the International Space Station.

Independent operator LeoLabs reported a different picture from initial company descriptions, detecting what it described as tens of objects in the vicinity of 35956 after the event. LeoLabs assessed that the signatures and motion of the liberated material were consistent with an internal energetic source rather than an orbital collision. That assessment remains preliminary and subject to refinement as radar and optical tracking data are updated.

The discrepancy between SpaceX characterizing the liberated material as a small number and LeoLabs reporting tens of objects is among the primary questions investigators must reconcile. Exact fragment counts and size distributions will determine how persistent the debris will be and the likelihood of future close approaches with other satellites. U.S. space surveillance networks will refine orbital element data over coming days and weeks, improving reentry forecasts and risk modeling.

SpaceX said it is deploying software updates intended to harden the fleet against this class of event while forensic work continues to seek a root cause. The company has previously taken fleet wide measures after earlier anomalies, including retiring or deorbiting satellites when necessary to protect orbital traffic and reduce risk. At present SpaceX has not attributed the failure to a specific hardware fault or operational sequence.

Analysts and space operators view the event as small compared with large breakups that produced hundreds of trackable fragments in recent years, yet the incident underscores the continuing challenge of managing an expanding constellation in low Earth orbit. Low relative velocity fragments that remain near the parent vehicle pose different collision risks than high velocity fragments that can scatter across broad orbital shells. Continued monitoring will be required to determine whether pieces decay rapidly or remain on longer term orbits.

For now the immediate operational priority is tracking and cataloging liberated objects, assessing any near term conjunction threats to crewed missions and critical satellites, and completing a technical investigation. SpaceX and U.S. space authorities expect data updates in the coming days that will narrow the range of possibilities and guide any further mitigation steps.