---
title: "An 11-Foot Dome in a Minnesota Cornfield Matches a Chinese Rocket, Exactly"
description: "The dimensions, the orbit and the timing all point to LandSpace’s Zhuque-2E — and to nobody claiming it"
author: "Luis Goa"
published: 2026-10-19T14:35:01Z
modified: 2026-10-19T16:07:58Z
url: https://rews.cc/a/an-11-foot-dome-in-a-minnesota-cornfield-matches-a-chinese-r-05372f
language: en
tags: ["space", "china", "debris", "landspace", "zhuque-2e", "tech"]
publisher: "Rews (https://rews.cc)"
---

# An 11-Foot Dome in a Minnesota Cornfield Matches a Chinese Rocket, Exactly

*The dimensions, the orbit and the timing all point to LandSpace’s Zhuque-2E — and to nobody claiming it*

By Luis Goa · October 19, 2026 · https://rews.cc/a/an-11-foot-dome-in-a-minnesota-cornfield-matches-a-chinese-r-05372f

## In brief

- An 11-ft metallic object, matching a Zhuque-2E rocket stage’s exact diameter, was found in a Minnesota cornfield Oct. 14
- The stage launched Sept. 15 from Jiuquan carrying 10 Qianfan satellites, then apparently botched its deorbit burn
- It is the second Zhuque-2E incident in four months after a June breakup scattered 100–150 fragments near Starlink
- Neither LandSpace nor any named federal agency has confirmed the object’s origin or removal
- Under the 1972 Liability Convention China would be strictly liable for ground damage, but no claim has been filed

The object that turned up in a Stevens County cornfield on October 14 is 11 feet across. The upper stage of China’s Zhuque-2E rocket is 11 feet across. That is not a coincidence of rounding: the stage measures between 25 and 30 feet long and roughly 11 feet (3.35 meters) in diameter, a figure the orbital-intelligence firm LeoLabs gave Ars Technica after a separate Zhuque-2E breakup in June. The match is why [Ars Technica](https://arstechnica.com/space/2026/10/a-chinese-rocket-deorbited-over-minnesota-and-left-this-in-a-farmers-cornfield/), whose reporting anchors this account, concludes the debris is almost certainly the spent upper stage of the Zhuque-2E that launched from Jiuquan on September 15 — a month before anyone in Minnesota found it.

Nobody official has confirmed that. The Stevens County Sheriff’s Office, which got a call around 3:30 p.m. on October 14 about a large metallic object in a Scott Township field, described it only as “presumably a space object” and said it posed no danger to the public, according to [MPR News](https://www.mprnews.org/story/2026/10/15/space-debris-possibly-found-in-stevens-county-minnesota-cornfield). A Minnesota duty officer notified unnamed federal agencies, who are working to identify the object and its owner. No agency — not NASA, not the FAA, not the Space Force — has put its name on a statement. LandSpace, the Chinese company that builds and flies Zhuque-2E, has not publicly acknowledged the incident either. The case for Chinese origin is circumstantial, built from orbital mechanics rather than an admission, but it is a strong circumstantial case.

## What the rocket was doing

The Zhuque-2E that lifted off on September 15 at 14:26 Beijing time (06:26 UTC) from Jiuquan’s Launch Area 96A carried 10 satellites for Qianfan, China’s answer to Starlink, built by the Innovation Academy for Microsatellites at the Chinese Academy of Sciences, according to [China in Space](https://www.china-in-space.com/p/qianfan-reaches-space-via-landspace). It was LandSpace’s seventh Zhuque-2E flight and the constellation’s fifteenth launch overall, bringing Qianfan’s deployed total to 248 satellites at the time; by October 19, after further launches, Ars Technica put the cumulative count at 258. Qianfan’s near-term target is 1,296 satellites; the longer-term ambition, per Ars Technica, is more than 15,000 — two and three orders of magnitude past what has flown so far.

**Qianfan's gap between flown and planned** Satellites deployed vs. constellation targets

|  | Qianfan satellites (satellites) |
| --- | --- |
| Deployed by Oct. 2026 | 258 |
| Initial constellation target | 1,296 |
| Long-term ambition | 15,000 |

Source: [Ars Technica / China in Space](https://arstechnica.com/space/2026/10/a-chinese-rocket-deorbited-over-minnesota-and-left-this-in-a-farmers-cornfield/)

About 30 minutes after liftoff, the rocket released its 10 satellites into a circular polar orbit roughly 560 miles (900 kilometers) up, after a flight path that ran south over Antarctica and then north over the Americas. Having done its job, the upper stage was supposed to fire its engines again to slow down and drop out of orbit — deorbiting a spent stage on purpose, rather than letting it tumble indefinitely, is standard practice and generally a responsible one. The usual target for that kind of burn is open ocean. Instead, something that matches the stage’s exact dimensions came down over farmland in the upper Midwest, the same day it launched. LandSpace has not said why.

## A rocket with a recent habit

This would be the second time in four months a Zhuque-2E upper stage has made news for the wrong reasons. The previous flight, on June 9, broke apart in orbit instead of deorbiting cleanly, scattering debris between roughly 208 and 263 miles up — a band shared with the International Space Station and a large share of Starlink. LeoLabs’ Darren McKnight told Ars Technica at the time that the breakup likely generated 100 to 150 new trackable fragments, and the U.S. Space Force logged the event on Space-Track.org, noting no threat to human spaceflight but ongoing analysis, as [FOD News reported](https://fodnews.com/zhuque-2e-upper-stage-breakup-starlink-iss-debris/). McKnight’s broader point was a ranking, not a one-off: three of the top four LEO breakup events by debris count are of Chinese origin, two of them rocket-body explosions within the last four years.

![A broken rocket stage scatters debris along an orbital path between two satellites above Earth, illustrated in a textured retro style.](https://rews.cc/img/c1e3c4b2d0bad670d801b3b922d3b7b968f4e438.webp)

Those two aren’t the only recent entries. A Long March 6C upper stage broke apart on August 27 less than two days after deploying seven satellites, at an altitude of 396 to 482 kilometers — LeoLabs clocked the event but could only estimate “tens to hundreds” of new fragments, since the Space Force catalog hadn’t caught up yet. Separately, a Chinese reconnaissance satellite, Yaogan-50 (02), fragmented in September into at least 43 tracked pieces at a much higher, longer-lived altitude band of 600 to 1,100 kilometers, according to [The Space Review](https://www.thespacereview.com/article/5321/1). Debris that high can persist for decades; the June and August fragments, low enough to feel atmospheric drag, mostly reenter within months. The Space Review’s analysis goes on to ask whether a pattern across three separate Chinese breakups clustering in U.S.-satellite-dense orbital shells could be more than engineering failure — a hypothesis it explicitly can’t prove and partly walks back, since garden-variety hardware failure remains the simpler explanation and China’s own rockets are also exposed to the same congested shells.

Each of those three events happened in orbit, where nobody on the ground gets hurt and nobody owns the sky underneath. A Zhuque-2E stage landing in a Minnesota cornfield is a different category of event, because it triggers a body of law that orbital breakups mostly don’t.

## Who owes whom, if anyone files

The relevant instrument is the 1972 Convention on International Liability for Damage Caused by Space Objects, which fleshes out Article VII of the 1967 Outer Space Treaty. Article II of the Liability Convention makes the launching state — defined broadly enough to include the state from whose territory the object launched — absolutely liable for damage its space object causes on the ground or to aircraft in flight, no fault required, as laid out in [the convention’s text](https://treaties.un.org/doc/Publication/UNTS/Volume%20961/volume-961-I-13810-English.pdf). “Space object” explicitly covers “component parts of a space object as well as its launch vehicle and parts thereof,” which is exactly the category an upper stage falls into. The logic, per legal scholarship on the convention, is that people on the ground didn’t choose to be underneath a rocket’s path and shouldn’t have to prove negligence to be made whole.

**From launch pad to liability claim** How a Zhuque-2E stage ends up over Stevens County, and who would be on the hook

| From | To | How |
| --- | --- | --- |
| China / LandSpace *(launching state & operator)* | Zhuque-2E launch, Jiuquan *(Sept. 15, 06:26 UTC)* |  |
| Zhuque-2E launch, Jiuquan *(Sept. 15, 06:26 UTC)* | 10 Qianfan satellites deployed *(~900 km polar orbit)* | ~30 min after liftoff |
| 10 Qianfan satellites deployed *(~900 km polar orbit)* | Upper-stage deorbit burn |  |
| Upper-stage deorbit burn | Uncontrolled reentry over North America | burn apparently mistargeted |
| Uncontrolled reentry over North America | 11-ft fragment lands in cornfield *(Stevens County, Oct. 14)* |  |
| 11-ft fragment lands in cornfield *(Stevens County, Oct. 14)* | Federal agencies investigate origin |  |
| Federal agencies investigate origin | Absolute liability, 1972 Convention Art. II *(only if a claim is filed)* | if origin confirmed |
| China / LandSpace *(launching state & operator)* | Absolute liability, 1972 Convention Art. II *(only if a claim is filed)* | strict liability regardless of fault |

![From launch pad to liability claim. How a Zhuque-2E stage ends up over Stevens County, and who would be on the hook](https://rews.cc/img/94af9ea4dee5b7c8439dc7ac72b1062c51fae6c3.webp)

Based on [UN Liability Convention; Ars Technica reporting](https://treaties.un.org/doc/Publication/UNTS/Volume%20961/volume-961-I-13810-English.pdf)

The convention has only been formally invoked once. When the Soviet nuclear-powered satellite Cosmos 954 broke up over Canada’s Northwest Territories in January 1978, scattering radioactive fragments across tens of thousands of square kilometers, Canada billed the USSR for the cleanup under the absolute-liability clause. Moscow settled in 1981 for C$3 million against a claim of C$6 million, as detailed in [an overview of the convention](https://orbitalradar.com/glossary/liability-convention). Nothing close to that scale applies here: no injuries, no contamination, a sheriff’s office calling it harmless. The convention requires actual damage before a claim exists, and a dented cornfield with the harvest presumably already run through it doesn’t obviously produce any. Scholars writing in the *University of Chicago Journal of International Law* have also flagged a structural gap the Minnesota case sits right on top of: the entire liability regime assumes the launching state is identifiable, and a government on the receiving end of debris with no confirmed origin has no clear path to a claim at all, as [the journal’s analysis](https://cjil.uchicago.edu/print-archive/its-raining-rockets-heightening-state-liability-space-pollution) lays out.

That leaves the Minnesota object in a kind of jurisdictional limbo: a piece of hardware whose dimensions match a specific Chinese rocket stage to the foot, sitting in an undisclosed secure location while unnamed federal agencies work out who owns it, under a treaty regime that has produced exactly one settled claim in more than fifty years. The precedent that regime does offer — strict liability, no fault needed — only matters once someone actually files. Whether the United States does, and whether LandSpace or Beijing ever says anything about September 15 at all, is the next thing to watch.