Incoprea research · H203 re-analysis · 3 November 2026

H203 re-analysed from live catalogue data

This page uses real measured catalogue data, not a simulation. The NASA/JPL CNEOS fireball catalogue was fetched live on 3 November 2026 (602 events) and re-analysed independently of the hub's H203 record. One of H203's two claims replicates and the other does not. The tail-index claim is not reproduced: my estimates are 2–5× lower and strongly threshold-dependent.

1. The data

Source: ssd-api.jpl.nasa.gov/fireball.api, fields energy (radiated, kt) and impact-e (estimated impact energy, kt), plus date, location, altitude and velocity. Saved locally as data/fireballs.json (44 KB).

QuantityValue
Events602
Radiated energy range1.24 – 37,500 kt
Impact energy range0.048 – 441 kt
Date coverage1997 – 2026

This is a real catalogue, and it is not volume-complete. Its lower cut-off is set by detection, so no statement here is about the true impact rate — only about what this catalogue contains.

2. Claim 1 — "impact energy is a deterministic recalibration of radiated energy" — REPLICATED

The hub's H203 record concluded that the impact energy is a deterministic function of the radiated energy (reported r = −0.995), which is why the result was not promoted. That is confirmed here, and more sharply than reported.

StatisticValue
Pearson r, log₁₀ energy vs log₁₀ impact energy0.99992
Spearman ρ0.99950
Residual sd about a straight log–log line0.0064 dex
Median ratio impact/radiated0.03154
Ratio range0.0118 – 0.0387 (3.29×)

Interpretation. Over four and a half decades of energy, the two columns agree to 0.0064 dex — about 1.5%. The impact energy carries almost no information independent of the radiated energy. Any analysis that treats them as two measurements is using one measurement twice.

The 3.29× ratio spread is the one caveat: the relation is tight but not exactly proportional, so "deterministic" is right to a few per cent, not to machine precision. The hub's own conclusion — that this makes H203's tail result conditional rather than physical — stands and is strengthened.

3. Claim 2 — the tail index — NOT REPRODUCED

Hill estimator of the tail index above several thresholds:

Threshold (kt)ExceedancesHill α
0.26020.257
0.56020.337
1.06020.440
2.05900.619
5.03690.722

The hub reports b = 2.65–2.82 and α = 1.33–1.41 for thresholds 0.2–2 kt. This re-analysis gives α = 0.26–0.62 over the same thresholds — a factor of two to five lower, and in the opposite direction from the reported range.

A 40-point threshold sweep gives α from 0.24 to 0.69, median 0.37, a spread of 2.86×. The estimate is strongly threshold-dependent, which is the usual signature of a Hill estimator applied below its valid region.

Why this is a failure and not a refutation

Three explanations are possible, and I cannot separate them with this data alone:

  1. Estimator mismatch. The hub's b may be a Pareto exponent fitted to the cumulative distribution or by maximum likelihood, not a Hill estimate. Hill and MLE differ systematically at small samples, and the hub's α = b/(3γ) conversion implies a different parameterisation.
  2. Catalogue cut-off. At threshold 0.2 kt, all 602 events exceed — the Hill estimator is being asked to describe the whole catalogue, not a tail. Its value there is not meaningful.
  3. Catalogue drift. The API returns a limited set and the catalogue grows with time; the hub's 1,074-event analysis used more events than the 602 returned today.
The honest statement: the tail-index number in H203 does not reproduce from the current catalogue under a Hill estimator, and the discrepancy is large enough that the number should not be quoted until the estimator and the catalogue cut are both specified.

4. What this changes

H203 elementStatus after re-analysis
Impact energy is a recalibration of radiated energyReplicated, and sharper (r = 0.99992, 0.0064 dex)
"Not promoted until a second catalogue exists"Correct call — the dependency is confirmed
b ≈ 2.65–2.82, α ≈ 1.33–1.41Not reproduced; α = 0.26–0.62 here
α = b/(3γ) with predicted 1.35Cannot be tested until b is re-derived consistently

5. The decisive next step

  1. Specify the estimator. Refit the tail with maximum likelihood (Pareto) and with a probability-weighted moment estimator, on the same catalogue, and report all three. If they agree, the hub's number has an estimator problem; if they disagree, no single number should be quoted.
  2. Fix the threshold by a stability criterion — choose u where the Hill estimate is locally flat, not by convention.
  3. Record the catalogue snapshot (count and date) with every published tail index. Today's is 602 events on 2026-11-03.

6. New hypotheses from this page

#HypothesisDisposition
N-20Published impact-loss tail indices are estimator-dependent, and the spread across estimators exceeds the difference between competing physical models.test now — three estimators on this catalogue
N-21A catalogue whose impact energy is calibrated from radiated energy cannot test a hypothesis about impact energy, because the two are one measurement. This applies to any catalogue with a derived column.test now — check other catalogues for derived columns
N-22The 3.29× ratio spread is not noise but encodes the velocity and altitude dependence, so the residual of the energy relation recovers the entry parameters.test now — regress the residual on velocity and altitude

7. Limits

If one sentence survives: the deterministic-recalibration objection to H203 is confirmed at 0.0064 dex, and the tail-index number does not reproduce from the current catalogue — so the record should keep the objection and withdraw the number until the estimator is specified.

Back to the research hub · CNEOS fireball API