Skip to content
StarshipDesk.

Field Journal / sourced daily

Explore
OverviewHow the ledger works
Feed (Atom)

FIELD JOURNAL / EVIDENCE

How this desk works.

An independent source ledger: what confidence means, how claims combine and where uncertainty stays visible.

FROM THE PHOTOGRAPHIC ARCHIVE

Wide view of the Starbase launch tower beside the water at sunset.
A launch site on the Gulf coastArchive · 15 Apr 2023 · Starship Test Flight Mission · SpaceX · CC BY-NC 2.0. Resized; display crop may apply.

Method

A claim is confirmed when one source is TrackingTheSB or Ringwatchers, an official page from FAA, FCC, NASA, SpaceX, Federal Register, SEC EDGAR, City of Starbase, or when two independent sources agree. Independent sources are X handles and the listed web publishers (FAA, FCC, FCC.report, NASA, SpaceX, NASASpaceflight, Ringwatchers, Federal Register, The Grid Fin, SEC EDGAR, Louisiana Economic Development, WESH, City of Starbase, CADENA). Other web pages can be cited but do not count toward confirmation. Any other single source stays unconfirmed. Hedge words demote a confirmed draft to unconfirmed and the build warns. Unconfirmed claims do not overwrite confirmed state. They are stamped UNCONFIRMED and drawn beside it.

Confirming handles

  • TrackingTheSB
  • Ringwatchers

Hedge words

  • may
  • likely
  • presumably
  • reportedly
  • appears
  • appeared
  • possibly
  • might

Lowercase may is a hedge. Capital May is a month.

Geometry

Rings are slots named by a claim. Empty stations are not drawn. Order is a sourced profile when one exists. Otherwise the tower uses a fixed layout order, which is not a sourced stack order.

A section move does not move the vehicle. The body stands where the latest confirmed whole-vehicle move put it, or where a sourced identify site seeded it. A stacked section follows later whole-vehicle moves. A vehicle with neither is unplaced. An unconfirmed body placement is hatched and stamped UNCONFIRMED. A candidate site stays beside the confirmed location.

Same-day confirmed claims that disagree stay unresolved. A later confirmed claim for that same key clears the active marker and keeps the earlier disagreement in the history. Identity fields use the same rule, and a blocked identify does not change the previous name or block. A sourced identify adds its site or region to the yard. An unconfirmed identity stays provisional.

Cadence keyword method

The cadence chart uses claim dates and only the effect type and that claim's summary to choose one kind. Vehicle anchors come from that effect, never a flight assignment or a name mentioned in passing. Site state and test subtype do not choose a kind.

KindEffect or summary keywords
Stacking / section workstack effect; or section, tank, dome, nosecone, payload bay, flap, raceway, transfer tube, engine, internals or slot code with stacked, received, installed, fitted, gained, sleeved, staged or finishing. A move with section words is section work.
Rollout / test moveA whole vehicle rolled out; or rolled, moved, transported, arrived, lifted, loaded or followed with a destination phrase naming Massey's, a test site or stand, cryo, cryo-proof or cryo / thrust sim stand (including ship or booster stands), or pad in the summary. A section rolling out remains section work.
Cryo / proof testcryo, cryogenic or proof test with test, tested, testing, underwent, completed, concluded or during; a test effect also supplies the test action. Stand, simulator, hardware and equipment mentions are excluded.
Static firestatic fire, static fired or static firing, excluding campaign, stand, pre-flight, hardware and equipment mentions.
Flightflew, launched, lifted off, liftoff, splashdown, splashed down, entered orbit, during ascent or ascent burn. An On Flight number heading also needs a past outcome: lit, relit or started Raptors or engines; completed ascent, boostback, flip or flight; made reentry, landing burn or flip; returned, flipped or initiated with boostback, landing burn or launch site; was or were caught; did not or failed to separate; had Raptors or engines fail; lost a Raptor; or was first to reach outer space.

Clauses naming future, waiting, planned, pending, potential, postponed, delayed, deferred, scrubbed, due, cancelled or negated activity are skipped. Due to and planned engines in a past engine-count outcome do not themselves mean future activity. An action following another vehicle's name does not apply to the anchor, except for simple coordinated subjects. Relative clauses beginning which or who retain their preceding vehicle. An On Flight heading stays with its following clause, including future or negated launch words. A heading alone never counts. Cancellation or negation directly after a flight, launch, liftoff or splashdown assertion also excludes it; a failed catch or separation does not deny a stated flight. Purpose text after for a test, ahead of or before does not state that test occurred. An explicit earlier clause can still qualify. Unmatched claims are omitted. When several kinds match, section moves and completed test moves come first, then static fire, proof, flight, rollout and section work. A stack effect comes first.

One mark represents one claim and vehicle. Repeated sections in one effect are deduplicated. Nearby marks are spread vertically inside their vehicle row without changing their date position. First claims include both confidence lanes. Comparisons require consecutive integer serials of the same class and the same kind; they measure days between claims. Test articles are excluded.

Pipeline

The pipeline and each vehicle page show seven build stages for ships and boosters. A cell is the earliest claim whose effect states that stage. The classifier does not read summaries. A note never fills a stage. A later stage never fills an earlier one.

  1. First section: First section seen is the earliest move, stack, or unstack whose effect names a slot of this vehicle. A whole-vehicle move does not count. A profile does not count. A note does not count.
  2. First stack: First stack is the earliest stack effect for this vehicle. That effect states one named slot was stacked onto another, not that the vehicle is fully stacked, so the cell never reads as stacking complete. A later section move does not clear it or fill it. A slot move is a first section, not a stack.
  3. Cryo or proof: Cryo or proof is the earliest test effect on this vehicle whose test kind is cryo or proof. A static fire does not count. A note does not count. Summary wording does not count.
  4. Engines installed: Engines installed has no effect field. A note, a summary, a static fire, a cryo test, or a later launch does not install engines. The cell stays no claim yet.
  5. Static fire: Static fire is the earliest test effect on this vehicle whose test kind is static-fire. A cryo or proof test does not count. A note does not count.
  6. Rollout to a pad: Rollout to a pad is the earliest move that carries this vehicle body, a vehicle piece and not a section, to a launch pad. A launch pad is a site whose role names a launch pad, launch tower, or launch complex, the same test as the pad board. A move to a bay or a test site does not count. A test at a pad does not count. A section moving to a pad does not roll the vehicle out.
  7. Launch: Launch is the earliest assign of this vehicle to a flight that has a flight-result schedule. A schedule is a flight result when its net is a date on or before that schedule claim date. A later net is a plan, not a liftoff. The cell cites the assign, because that claim names the vehicle, and it keeps the assign date and confidence. An assign with no result schedule does not count. Another vehicle does not count.

Who feeds the ledger

Each publisher or X handle cited by at least one claim, by claims citing it. Confirmed counts the claims that met the rule above, whichever source tipped them.

SourceTypeClaimsConfirmedNewest
@VickiCocks15X131492026-11-15
NASASpaceflightweb10552026-10-30
@TrackingTheSBX85602026-11-16
SpaceXweb79522026-11-07
@BlobifieX57312026-11-16
@NASASpaceflightX50272026-11-15
@LabPadreX47302026-11-15
@RGVaerialphotosX40232026-11-15
@FelixSchlangX29122026-11-05
@SpaceXX21212026-11-14
@lewisknaggs42X1662026-11-10
FAAweb16162026-11-12
City of Starbaseweb15142026-11-15
@AshleyKillipX842026-11-15
@elonmuskX882026-11-16
@StarshipGazerX872026-11-10
@RoughRidersShowX752026-10-30
SEC EDGARweb442026-10-20
@CeaserG33X332026-10-27
@NASAArtemisX332026-10-23
Louisiana Economic Developmentweb322026-08-25
NASAweb332026-09-23
FCC.reportweb202026-09-20
@Flight2StarshipX102026-11-04
@INiallAndersonX102026-11-03
@LunarCitizensX102026-10-19
@SERobinsonJrX102026-11-04
@TheHarnessLabX102026-10-19
CADENAweb102026-10-29
Federal Registerweb112026-10-14
Gateway to Marsweb102026-11-04
The 956 Reportweb102026-11-04
The Grid Finweb102026-10-15
WESHweb102026-10-23

Sources

Kinds

identify

Fields: subject

Required: subject

Records a vehicle, site, region, flight, hardware item, or slot name. A vehicle subject may carry a sourced site. That site seeds the body only when no whole-vehicle move has placed it. Identity does not draw a ring. Same-day disagreements on name, block, or other identity fields stay unresolved and keep the previous identity.

{"type":"identify","subject":{"type":"hardware","id":"og-can-crusher","name":"OG can crusher"}}

move

Fields: how, pieces, from, to

Required: how, pieces, to

Moves the named pieces. A slot piece changes that section only. A vehicle piece changes the body. A hardware piece changes that hardware. A section move never moves the vehicle. The example is the migrated Booster 24 A5:4 roll.

{"type":"move","how":"roll","pieces":[{"type":"slot","vehicle":"B24","slot":"A5:4"}],"from":"sfc","to":"mb1"}

stack

Fields: vehicle, slot, at

Required: vehicle, slot, at

Example shape, not a sourced claim. Marks one slot stacked at a site. After this date, a later whole-vehicle move carries the slot. The same calendar day does not, because order inside the day is not known.

{"type":"stack","vehicle":"B24","slot":"A5:4","at":"mb1"}

unstack

Fields: vehicle, slot, at

Required: vehicle, slot, at

Example shape, not a sourced claim. Returns a slot to crib at a site and stops it following the vehicle.

{"type":"unstack","vehicle":"B24","slot":"A5:4","at":"mb1"}

test

Fields: vehicle, test, at, result

Required: vehicle, test, at

Records a test. It does not move the vehicle or a section. The example matches the migrated Ship 42 cryo at Massey's.

{"type":"test","vehicle":"S42","test":"cryo","at":"masseys"}

schedule

Fields: flight, name, net, site

Required: flight, net, site

Sets a flight NET and site. name is required when the flight is new and must match the catalog name when the flight already has one. A later schedule can omit name. The example matches the migrated Flight 15 advisory.

{"type":"schedule","flight":"F15","name":"Flight 15","net":"2026-11-08","site":"pad2"}

assign

Fields: flight, vehicle, role

Required: flight, vehicle, role

Example shape, not a sourced claim. Assigns a booster or ship to a flight. It does not move hardware. A later assign of the same vehicle replaces the role.

{"type":"assign","flight":"F15","vehicle":"S42","role":"ship"}

outcome

Fields: flight, booster, ship, boosterCatch, shipCatch, orbit, payload

Required: flight, booster, ship, boosterCatch, shipCatch

Records the completed result of one flight. It does not move a vehicle, set a NET, or assign a vehicle. booster and ship are caught, splashdown, lost, or terminated. boosterCatch is true only when booster is caught, and shipCatch is true only when ship is caught. orbit is an optional boolean, set only when the source says the flight entered orbit or says it did not. payload is optional: none, data, simulators, starlink, or simulators-and-starlink, and only when the source names it. A later agreed outcome replaces the earlier one. Same-day disagreements stay unresolved. An unconfirmed outcome does not count. Plan wording is rejected because this is a completed event. The example is a shape, not a sourced claim.

{"type":"outcome","flight":"F5","booster":"caught","ship":"splashdown","boosterCatch":true,"shipCatch":false}

note

Fields: at, about

Required: (none)

A sourced sentence. It does not move a vehicle or a section. about may name a vehicle, a hardware item, a slot, or a flight. When about is hardware and at is a site, the hardware is placed there. A flight about does not set a NET or an outcome. At least one of at or about is required.

{"type":"note","about":{"type":"flight","flight":"F15"}}

filing

Fields: agency, filing, at, flight, ref

Required: agency, filing

Records a regulatory filing. It does not move a vehicle, a section, or hardware. agency is the regulator. filing is the document type: notice, eis, ea, licence (an FAA launch or reentry license), experimental, notam, marine, airspace, or closure. at and flight are optional, so a filing that names no site and no flight still has a claim. ref is an optional docket or document id when the source states one. The example names no site.

{"type":"filing","agency":"FAA","filing":"ea"}

profile

Fields: vehicle, slots

Required: vehicle, slots

Example shape, not a sourced claim. Sourced stack order for one vehicle. Rings are still only slots with a move, stack, or unstack. Without a profile, towers use layout order and the legend says so.

{"type":"profile","vehicle":"B24","slots":[{"slot":"A5:4","order":40},{"slot":"A6:4","order":50}]}

Archived v1 fields

These values were on the v1 cards and have no source of their own. They are not derived state.

OwnerFieldDispositionValue
vehicle:B23statusarchived-only"testing"
vehicle:B23locationarchived-only"masseys"
vehicle:B23notesarchived-only"Rolled to Massey's for its initial cryo proof campaign on 13 Oct 2026."
vehicle:B24statusarchived-only"stacking"
vehicle:B24locationarchived-only"mb1"
vehicle:B24sectionsarchived-only["A5:4","A6:4","CH4 landing tank","Transfer tube","LOX landing tank"]
vehicle:B24notesarchived-only"Described by StarshipTracking as the sixth Block 3 Super Heavy. A few sections left to stack as of 14 Oct 2026."
vehicle:S40statusarchived-only"recovered"
vehicle:S40locationarchived-only"mb2"
vehicle:S40notesarchived-only"First Starship upper stage brought home intact, after an Indian Ocean splashdown and return via Christmas Island on the ship Forte. Its flight number is not yet recorded here (unconfirmed)."
vehicle:S42statusarchived-only"testing"
vehicle:S42locationarchived-only"mb2"
vehicle:S42notesarchived-only"Completed a third round of testing at Massey's and returned to MB2 on 10 Oct 2026. Engines had been removed before this cryo round."
vehicle:S42flightarchived-only"Flight 15 (per Starship Gazer)"
vehicle:S43statusarchived-only"stacking"
vehicle:S43locationarchived-only"mb2"
vehicle:S43notesarchived-only"Seen standing in MB2 behind Ship 40 on 12 Oct 2026."
vehicle:S44statusarchived-only"stacking"
vehicle:S44locationarchived-only"mb2"
vehicle:S44sectionsarchived-only["A2:4"]
vehicle:S44notesarchived-only"A2:4 rolled into MB2 on 5 Oct 2026."
vehicle:S39.1statusarchived-only"testing"
vehicle:S39.1locationarchived-only"masseys"
vehicle:S39.1notesarchived-only"Rolled back to Massey's on 4 Oct 2026. Reason unclear."
vehicle:S43.1statusarchived-only"testing"
vehicle:S43.1locationarchived-only"masseys"
vehicle:S43.1notesarchived-only"Tested inside the Supercrusher at Massey's overnight 13 to 14 Oct 2026."
vehicle:BLT-TAstatusarchived-only"tested"
vehicle:BLT-TAlocationarchived-only"masseys"
vehicle:BLT-TAnotesarchived-only"Appeared to burst near its base during a cryo test on 6 Oct 2026. Whether this was intentional is unconfirmed."
flight:F15vehiclesarchived-only["S42"]
flight:F15notesarchived-only"NET per a CADENA advisory. Booster and Ship catch hoped for (NSF). Booster assignment not recorded here."
flight:F16vehiclesarchived-only[]
flight:F16notesarchived-only"NET per CADENA. Launch site likely LC-39A."
region:starbasestatusarchived-only"active"
region:floridastatusarchived-only"active"
region:mcgregorstatusarchived-only"active"
event:ev-2026-10-07-007subject-leftoverarchived-only"lower transfer tube"
event:ev-2026-10-14-024fromarchived-only"port-bro"
event:ev-2026-10-14-024toarchived-only"ksc-turn-basin"