Seita Iizuka

SEITA IIZUKA

Creator / Developer
Engineer / Program Manager / Executive. 13+ years in deep tech — from rocket range control to debris removal to laser fusion.
Growing up with a dream of reaching space, I started my career in the space industry at JAXA. While serving as a Range Control Officer for rocket launches, I witnessed firsthand how spent upper stages become orbital debris — sparking a deep awareness of the space debris problem. This led me to join Astroscale, where I gained hands-on engineering experience across multiple subsystems including communications, propulsion, and ground systems, before taking on the role of ELSA-d Program Manager. I led this tri-national project spanning Japan, the UK, and the US to a successful in-orbit demonstration, earning multiple industry awards. Today, I bring my experience managing complex international engineering programs to Blue Laser Fusion, where I serve as VP of Operations, working toward making laser fusion energy a reality. On weekends, you'll find me running around the Imperial Palace.
2023 — PRESENT
VP of Operations / Head of Japan Business
Blue Laser Fusion Inc.
Leading operations and cross-border R&D programs for laser fusion energy technology, with a focus on high-power laser systems. Coordinating between U.S. and Japan entities, engaging with government agencies, universities, and research institutions.
2017 — 2024
VP of Programs / ELSA-d Program Manager
Astroscale Japan Inc.
Directed Program Management, QA, Production, Procurement, and Ground Station teams. Program Manager for ELSA-d — the world's first commercial mission to demonstrate space debris docking and removal in orbit. Led a tri-national team across Japan, the US, and the UK from development through successful in-orbit demonstration.
2013 — 2016
Engineer, Space Transportation Technology Directorate
JAXA — Japan Aerospace Exploration Agency
Range Control Officer for 11 rocket launches, directing 100+ operators during mission-critical tracking operations at Tanegashima and Uchinoura Space Centers. The experience of seeing spent upper stages become orbital debris after every launch was the catalyst for a career dedicated to solving the space debris problem.
2013
B.Eng., Electronics and Information Engineering
The University of Osaka
🏆
Minister of State for Space Policy Award
5th Japan Space Development & Utilization Awards — Cabinet Office, Government of Japan
For "ELSA-d: On-Orbit Demonstration of Space Debris Proximity and Capture"
🏆
Satellite Technology of the Year 2021
Via Satellite — Awarded to ELSA-d at SATELLITE 2022 Conference, Washington D.C.

Data Sources

OrbitSmith integrates data from multiple authoritative public sources. All displayed values that come from these sources are transcribed as-is or presented with minimal formatting.

Orbital catalog & conjunctions (Tracker · Passes · GS Planner · Statistics)

  • Space-Track.org — GP catalog (18th Space Defense Squadron), CDM Public (via CSpOC), TIP predictions, Decay records. Requires account; OrbitSmith fetches hourly via authenticated Worker.
  • CelesTrak — GP and Supplemental GP elements by Dr. T.S. Kelso. SupGP provides operator-supplied ephemerides for major constellations (Starlink, OneWeb, GNSS, etc.), typically more accurate than Space-Track GP.
  • GCAT — General Catalog of Artificial Space Objects by Dr. Jonathan McDowell (CC-BY). Used for operator / country / launch date metadata.
  • ESA DISCOS — Space Debris Office statistics. Static reference for annual object counts in historical charts.
  • McCants visual magnitude database — satellite brightness references for Passes page.

The Tracker catalog (~30,000 objects) is fused from Space-Track GP, CelesTrak GP, and CelesTrak SupGP with SupGP prioritized where available (most recent epoch wins). This fusion is an OrbitSmith aggregation; individual object elements are upstream as-is.

Earth imagery (Imagery page)

  • NASA GIBS — MODIS Terra/Aqua, VIIRS SNPP/NOAA-20/NOAA-21 true color and scientific layers (NDVI, Nighttime Lights, Snow Cover, Aerosol Optical Depth, Sea Surface Temperature, Chlorophyll, Land Surface Temperature, Precipitation Rate) for the Imagery page.
  • NASA FIRMS — Fire Information for Resource Management System. Near-real-time active fire detection from VIIRS and MODIS thermal anomaly data.
  • Sentinel-2 Cloudless by EOX — Annual cloud-free mosaics (2022/2023/2024) derived from ESA Copernicus Sentinel-2 data, served by EOX IT Services.
  • Esri World Imagery — High-resolution satellite and aerial imagery from Esri, Maxar, Earthstar Geographics, and the GIS Community.

Precision ephemerides (Artemis II)

  • JPL Horizons — Precise ephemerides for Artemis II and Moon. OEM-format state vectors.

How We Calculate

Several displays on OrbitSmith are not raw upstream values but computed locally. Each calculation below lists the method, inputs, and assumptions.

Orbit Visualization (3D Globe)

Positions of ~30,000 objects on the 3D globe are propagated client-side using Kepler two-body mechanics. Initial state is computed from TLE mean motion and mean anomaly at epoch; subsequent animation applies a simple Y-axis rotation for visual effect.

For visualization only. Not suitable for collision prediction or precise tracking. Real positions require SGP4 propagation per object with drag and J2 corrections.

Perigee / Apogee / Period

Computed from TLE mean orbital elements: perigee = a(1 − e) − R⊕, apogee = a(1 + e) − R⊕, period = 1440 / n (minutes), where a is semi-major axis from mean motion, e is eccentricity, and n is revolutions per day.

Values reflect the mean orbit at TLE epoch. Actual present-day values drift from the epoch values due to atmospheric drag (LEO) and gravitational perturbations. Typical uncertainty is a few km for low-altitude objects.

Relative Velocity (Shell Risk Indicator)

When two objects are selected in the Shell Risk Indicator, OrbitSmith estimates a representative relative velocity using spherical trigonometry of orbital planes. The crossing angle θ is derived from inclinations and right ascensions: cos(θ) = cos(i₁)cos(i₂) + sin(i₁)sin(i₂)cos(ΔΩ). Then v_rel = √(v₁² + v₂² − 2·v₁·v₂·cos θ), with v₁, v₂ being circular orbital speeds at each object's altitude.

cos(θ) = cos(i₁)cos(i₂) + sin(i₁)sin(i₂)cos(ΔΩ)
Assumes circular orbits and ignores eccentricity, phasing differences, argument of perigee, and J2 drift. Errors of several km/s are possible. Space-Track CDM Public does not include state vectors, so true TCA relative velocities are unavailable without licensed data feeds.

Shell Risk Indicator (Calculator)

A simplified Kessler-style spatial density model is used as a relative shell indicator: P = 1 − exp(−ρ · σ · v_rel · Δt), where ρ is an implied shell density, σ is combined cross-section, v_rel is representative relative velocity, and Δt is the selected time window. This treats each orbital shell as a uniform population.

P = 1 − exp( −ρ · σ · v_rel · Δt )
This is not the same physical quantity as Space-Track CDM Pc and is not a prediction for a specific object pair or TCA. The implementation also applies altitude-difference scaling: 10⁶ for <5 km, 10⁴ for <50 km, and 100 for ≥50 km, with caps/floors to keep the display readable. These factors are empirical OrbitSmith tuning, not part of the Kessler source model and not physically derived. Use this only as an educational relative-risk indicator; operational collision probability requires covariance-based analysis from state vectors.

Orbital Congestion Index

A spatial flux indicator F = ρ · v_rel · σ is computed per regime, where ρ is object density (count / shell volume), v_rel is a regime-typical relative velocity (10 km/s for LEO, 5 for MEO, 0.5 for GEO, 7 for HEO), and σ = 10 m² is a typical combined cross-section. LEO bucket covers 800–1,000 km only (the highest-density band). CRITICAL / HIGH / MODERATE / LOW labels are derived from F relative to LEO's value.

This is an OrbitSmith-defined relative indicator, not an absolute NASA/ESA threshold. Labels indicate "how crowded this regime is compared to LEO 800–1,000 km," not "is this regime operationally dangerous."

Reentry Current Altitude

For objects on reentry watch, current altitude is computed in-browser via SGP4 propagation (satellite.js) from the cached TLE. Recomputed every 10 seconds; the underlying TLE itself is from the daily Space-Track refresh.

SGP4 accuracy degrades rapidly for objects close to reentry due to atmospheric drag sensitivity. Tens-of-km errors are expected within hours of decay.

Visible Pass Prediction

The Passes page uses SGP4 propagation from Space-Track GP TLE lines when available. For catalog objects missing valid GP lines, OrbitSmith generates a synthetic TLE from the current orbital elements as a fallback so the object can still be screened for visibility.

Synthetic TLE fallback is less reliable than upstream GP TLE and is intended for continuity, not mission-critical planning. City search requests on the Passes page go directly from the browser to OSM Nominatim.

CDM Risk Level

OrbitSmith groups Pc values into four display bands. The thresholds are anchored to public NASA CARA and ESA collision-avoidance references, but the band names are OrbitSmith-defined and are not official NASA/ESA categories. Specifically: HIGH (Pc ≥ 10⁻⁴) corresponds to the NASA CARA mitigation threshold (NASA Step 2) and ESA's ~1-in-10,000 maneuver threshold. MODERATE (10⁻⁵ ≤ Pc < 10⁻⁴) corresponds to the ESA SCARF dashboard highlight threshold documented in Merz et al. 2017 (SDC7 paper 1017). LOW (10⁻⁷ ≤ Pc < 10⁻⁵) is above NASA's operational-attention floor (NASA Step 2) but below ESA's escalation-candidate threshold. NEGLIGIBLE (Pc < 10⁻⁷) is below NASA's operational-attention threshold. The Pc value itself is upstream from Space-Track; only the band assignment is made by OrbitSmith. OrbitSmith is not an operational tool.

Limitations & Known Errors

  • OrbitSmith is not an operational SSA tool. It is intended for education, research, and awareness only. All displayed values carry uncertainty.
  • CDM Public data from Space-Track contains no state vectors or covariance matrices — the true TCA relative velocity cannot be retrieved, only approximated locally.
  • TLE-based propagation ignores high-fidelity forces (drag variability, solar radiation pressure, third-body, J₃+ terms). Position errors can accumulate to tens of km within days.
  • Catalog objects without recent epoch updates (>30 days) are excluded from the Tracker display; the "Tracked Objects" count reflects this filtered active set.
  • Orbital Congestion labels are OrbitSmith-internal; they do not correspond to any official SSA classification.
  • For operational decisions — maneuver planning, licensing, insurance — use official CDM from Space-Track or licensed SSA services (LeoLabs, Kayhan Space, ExoAnalytic, etc.).

References