You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Analysis covering all 8,504 entries across every category.
Scope: MBA (1,841), NKO (1,333), Trojan (1,277), Inner (746), KBO (533), Comet(S) (403), Centaur (328), Comet(L) (20), Moonlet (16), Ejected (7).
Scope and Methodology
Source of truth:SMA and Ecc come from the SFS archive and are treated as authoritative for all orbital calculations. Apkelion, Perikelion, and OrbitalPeriod come from the CSV and are checked against SFS-derived values.
Moonlets (16): SFS orbit is relative to the parent body, not Kerbol. Ap/Pe/OrbPeriod checks skipped.
Ejected (7): Hyperbolic escape trajectories. Apkelion should be null; no automated inconsistencies flagged.
Negative TrueAnom: Valid — see Part 4.
MBA note on OrbitalPeriod: The 27 flagged MBA objects were confirmed to have SFS-consistent OrbitalPeriod values (Kepler's third law). The remaining 1,814 MBA entries were not checked for OrbitalPeriod; that cross-check was only performed on non-MBA categories.
Stored Perikelion (~39.67M) close to expected Apkelion; stored Apkelion (~42.45M) deviates ~2.8M from expected
1e. Magnitude Error (×10) — 1 Object
UID
Field
Stored (km)
Expected (km)
Note
TSE-022
Apkelion
470,470,107
~47,047,115
~10× expected — extra digit or decimal point error
Part 2 — Non-MBA: Apkelion / Perikelion Errors — 51 Objects, 65 Field Errors
All errors are in the CSV-sourced fields only unless noted in section 2h. SFS-derived orbital elements are unaffected except for the three SFS-mismatch objects in section 2h.
2a. Single-Field Magnitude Errors (×10 or ×0.1) — 10 Objects
Both fields are wrong: one field holds the value expected for the other, plus an additional independent error in that field.
Group 1 — Swap + ×10 on Apkelion (Inner, 3 objects)
Perikelion slot received the correct Apkelion formula result; Apkelion slot received the correct Perikelion result multiplied by 10.
Verification: Stored Apkelion ÷ Expected Perikelion ≈ 10.000 for all three.
UID
Stored Apkelion
Stored Perikelion
Exp. Apkelion
Exp. Perikelion
XAP-767
149,202,527
34,857,501
~34,857,523
~14,920,410
KEV-561
130,004,442
47,618,095
~47,618,127
~13,000,024
HFR-278
87,814,893
30,560,222
~30,560,224
~8,781,474
Group 2 — Swap + +30M on Apkelion (Trojan, 3 objects)
Perikelion slot holds the correct Apkelion value; Apkelion slot holds the correct Perikelion value plus exactly 30,000,000 km.
Verification: Stored Apkelion − Expected Perikelion ≈ +30,000,000 for all three.
UID
Stored Apkelion
Stored Perikelion
Exp. Apkelion
Exp. Perikelion
KSB-336
95,025,470
71,998,339
~71,998,341
~65,025,467
SCN-418
93,040,350
73,983,461
~73,983,466
~63,040,342
WSN-181
97,919,629
69,404,180
~69,404,181
~67,619,628
Group 3 — Swap + +300M on Apkelion (KBO, 1 object)
Same compound pattern as Group 2 at a larger scale.
Verification: Stored Apkelion − Expected Perikelion ≈ +300,000,000.
UID
Stored Apkelion
Stored Perikelion
Exp. Apkelion
Exp. Perikelion
LPX-089
793,701,689
686,380,110
~686,380,166
~493,701,581
Group 4 — Swap + ×0.1 on Perikelion (KBO, 1 object)
Apkelion slot holds the correct Perikelion value; Perikelion slot holds the correct Apkelion value divided by 10.
Verification: Stored Perikelion × 10 ≈ Expected Apkelion.
UID
Stored Apkelion
Stored Perikelion
Exp. Apkelion
Exp. Perikelion
WZK-880
558,124,437
73,024,562
~730,246,127
~558,124,156
2e. Partial Swap Errors — 4 Objects
One field holds the value expected for the other field; the second field does not match either expected value in a recognisable pattern.
UID
Category
Observation
FUU-512
NKO
Stored Apkelion (~13,465,031) matches expected Perikelion (~13,366,899, within 0.7%); stored Perikelion (~12,308,874) also wrong (~−1.1M from expected Pe) with no clean pattern
ZNA-698
NKO
Stored Perikelion (~13,254,224) matches expected Apkelion (~13,351,107, within 0.7%); stored Apkelion (15,412,604) also wrong (+2.1M from expected Ap) with no clean pattern
RSY-451
Trojan
Stored Apkelion (~73,981,379) is correct; stored Perikelion (~23,967,439) is off by ~−39M with no clean pattern
PAW-520
Trojan
Stored Apkelion (~73,497,719) off by −900,013 from expected; stored Perikelion correct. Sub-1M, no clear pattern
Note: FUU-512 and ZNA-698 also have OrbitalPeriod discrepancies (14% and 16% respectively); see Part 3.
2f. Irregular Overestimates on High-Eccentricity Comets — 5 Objects
All have Ecc ≥ 0.986 (near-parabolic). Perikelion is overestimated by irregular factors — not ×10, not a round offset. Most likely cause: perihelion was computed using a slightly different eccentricity than what is now in the SFS archive, amplified greatly by near-parabolic orbital geometry (a small Ecc difference produces a large Pe difference when Ecc ≈ 1). Apkelion is correct for all five.
UID
Category
Ecc
Stored Perikelion (km)
Expected Perikelion (km)
Ratio
OPZ-847
Comet(S)
0.9896
1,117,763
~335,166
~3.3×
VHW-331
Comet(S)
0.9886
1,258,885
~455,554
~2.8×
KJD-787
Comet(S)
0.9904
3,665,340
~1,087,698
~3.4×
VWP-337
Comet(L)
0.9865
14,699,027
~7,589,102
~1.9×
HSE-776
Comet(L)
0.9946
115,534,140
~21,702,298
~5.3×
2g. Small Irregular Offsets — 1 Object
Both fields wrong by sub-500k amounts in opposite directions; no systematic pattern apparent. Likely independent imprecise values.
Field
Stored (km)
Expected (km)
Error
GLD-754 (NKO) — Apkelion
13,618,166
~13,418,355
+199,811
GLD-754 (NKO) — Perikelion
12,945,404
~13,254,637
−309,233
2h. SFS Orbital Data Inconsistencies — 3 Objects
These objects cannot be resolved by correcting CSV fields alone. The root cause is in the SFS orbital data itself (corrupted, misattributed, or stale vessel record). All three affect orbital trajectory rendering.
49,149 km — the entire orbit lies inside Kerbol's surface (Kerbol radius = 261,600 km)
Expected Apkelion from SFS
−177,496 km (negative — physically impossible)
CSV Apkelion
13,291,723 km (internally plausible for NKO)
CSV Perikelion
12,116,367 km (internally plausible for NKO)
CSV OrbitalPeriod
8,567,332 s (consistent with CSV Ap/Pe)
The SFS vessel matched to ORJ-043 almost certainly contains corrupted or misattributed orbital data. All SFS-derived elements (SMA, Ecc, inc, RAAN, Arg, TrueAnom) are untrustworthy.
QXV-373 (NKO) — SFS/CSV Orbital Regime Mismatch
Source
SMA
Aphelion
Perihelion
SFS
68,773,504 km (Trojan belt region)
~71,092,958 km
~65,930,851 km
CSV
—
13,402,203 km
12,158,239 km
CSV OrbPeriod
implies SMA ~13M km (NKO)
The SFS record places QXV-373 in the Trojan belt; the CSV describes an NKO orbit at ~13M km. Most likely a wrong SFS vessel was matched to this UID. All SFS-derived elements would render this NKO at a Trojan orbit distance.
HII-034 (KBO) — SFS/CSV Orbital Regime Mismatch
Source
SMA
Aphelion
Perihelion
SFS
43,044,501 km (inner belt region)
~47,750,666 km
~37,815,137 km
CSV
—
649,974,639 km
649,974,639 km
CSV OrbPeriod
3,042,714,232 s (consistent with KBO)
The CSV Ap and Pe hold identical values (~650M km circular), consistent with KBO classification. The SFS orbit is in the inner system. The identical Ap=Pe also suggests one CSV field was copied from the other. Neither source can be validated without a third reference. SFS-derived elements would render a non-KBO orbit.
Part 3 — OrbitalPeriod Errors — 15 Objects
Identified via Kepler's third law check. All 15 objects have correct Apkelion/Perikelion values; errors are isolated to the OrbitalPeriod CSV field. OrbitalPeriod is not used in orbital trajectory rendering, so these are display-only errors.
FUU-512 and ZNA-698 also have OrbitalPeriod discrepancies (14% and 16% respectively) but are already counted in Part 2 section 2e; they are not included in this section's 15.
3a. Grossly Wrong OrbitalPeriod — 6 Objects
The stored period implies a completely different SMA from what the SFS archive records. Apkelion and Perikelion are essentially exact for all six (sub-20 km delta), confirming the SFS orbit is valid and OrbitalPeriod alone is wrong.
UID
Category
CSV Period (s)
Kepler Period (s)
SMA (km)
SMA implied by CSV Period (km)
Off by
LBR-888
Inner
80,126,984
5,538,413
9,693,649
~57,554,982
1347%
CMA-235
Inner
128,641,786
17,678,462
21,014,870
~78,913,584
628%
AQH-911
Inner
141,539,025
34,809,761
33,013,970
~84,103,588
307%
YWB-419
Inner
60,914,596
15,701,992
19,417,809
~47,941,465
288%
ORF-959
NKO
18,350,159
8,955,705
13,354,581
~21,543,865
105%
JXP-386
Comet(S)
232,773,625
154,988,207
89,350,330
~117,179,842
50%
The four Inner objects' periods appear to have been calculated from a significantly different (larger) orbit — roughly 2.5–8× the actual SMA — while Ap/Pe were populated correctly from the valid SFS data.
All have Ecc ≈ 0.000; Ap = Pe exactly; both match the SFS SMA. CSV periods are 6–46% above the Kepler prediction with no consistent scale factor. Most probable cause: periods were written before the most recent SFS orbital update which reduced these objects' SMAs, but only the SFS/Ap/Pe fields were refreshed.
UID
CSV Period (s)
Kepler Period (s)
Over by
ZYS-113
4,151,137,600
2,850,365,140
46%
BQD-321
3,686,879,936
2,771,191,780
33%
AIK-169
4,006,213,568
3,190,461,852
26%
XWG-404
3,319,449,895
2,657,516,652
25%
XCX-141
2,831,662,046
2,471,358,232
15%
ULX-497
3,023,540,574
2,643,639,128
14%
FVC-765
3,691,331,018
3,384,082,203
9%
HVH-338
3,194,748,780
2,954,839,977
8%
RIZ-636
3,640,938,966
3,432,240,742
6%
Part 4 — Notes
4a. Negative TrueAnom Values — Not a Bug
Approximately 44% of elliptic-orbit entries across all categories have a negative TrueAnom (range −180° to 0°). These are the valid (−180°, +180°] output of math.atan2() in build_atn_main.py when converting MNA to true anomaly. Every consumer of TrueAnom passes it through toMeanAnomaly() in helpFuncs.js, which handles the (−π, 0) range correctly via Math.atan2() and modular normalization. All call sites in ksaBodyOps.js and ksaSurfaceOps.js use this path with no 0–360° assumption. No change needed.
4b. Moonlets Not Checked
The 16 Moonlet entries were excluded from all Ap/Pe checks. Their SFS orbital elements are relative to the parent body (not Kerbol), so consistency checks require each parent body's gravitational parameter.
4c. Ejected Objects Not Checked
The 7 Ejected entries (all Type = Roaming, Makeup = Comet) are on hyperbolic escape trajectories. Apkelion should be null; Perikelion represents hyperbolic perihelion altitude. No inconsistencies were flagged by automated checks.
4d. Unknown Size Class
One Comet(L) entry has Class = "?". All other 8,503 entries carry a valid class letter (A–E). This is an incomplete record, not a calculation error.
Summary
Apkelion / Perikelion Field Errors
Issue category
Objects
Field errors
Categories
MBA — ±10M offset
15
15
MBA
MBA — ±20–30M offset
4
4
MBA
MBA — ±3M offset
2
2
MBA
MBA — Swapped values
5
10
MBA
MBA — ×10 magnitude
1
1
MBA
MBA subtotal
27
32
Non-MBA — ×10 magnitude
3
3
Centaur, Inner, Comet(S)
Non-MBA — ×0.1 magnitude
7
7
Centaur (×2), NKO (×2), KBO (×2), Comet(S)
Non-MBA — Round-number offset
16
16
Centaur, Comet(S), NKO, Inner, Trojan, KBO
Non-MBA — Sub-round offset
4
4
Trojan (×2), Inner (×2)
Non-MBA — Compound: swap+×10 Ap
3
6
Inner
Non-MBA — Compound: swap+30M Ap
3
6
Trojan
Non-MBA — Compound: swap+300M Ap
1
2
KBO
Non-MBA — Compound: swap+×0.1 Pe
1
2
KBO
Non-MBA — Partial swap
4
6
NKO (×2), Trojan (×2)
Non-MBA — High-Ecc Pe overestimate
5
5
Comet(S) (×3), Comet(L) (×2)
Non-MBA — Small irregular offsets
1
2
NKO
Non-MBA — SFS mismatch
3
6
NKO (×2), KBO
Non-MBA subtotal
51
65
Total Ap/Pe
78
97
OrbitalPeriod Field Errors
Issue category
Objects
Categories
Grossly wrong period (50–1347% off)
6
Inner (×4), NKO, Comet(S)
Circular KBO period 6–46% high
9
KBO
Total OrbPeriod
15
Grand total: 93 unique objects with errors (27 MBA + 51 non-MBA + 15 OrbPeriod-only). Orbital trajectory rendering is not affected for 90 of these — errors are in display fields only. The three SFS-mismatch objects (ORJ-043, QXV-373, HII-034) require investigation as their SFS-derived orbital elements do not represent their true orbits.
Fix Tracker
All corrections to Apkelion and Perikelion should be recomputed as SMA × (1 ± Ecc) − 261,600 from SFS-derived values. The approximate expected values shown below are for reference and verification. All corrections to OrbitalPeriod should use 2π √(SMA³ / μ_Kerbol).
Part 2h — SFS Inconsistencies: Requires Investigation
These cannot be fixed by correcting CSV values. The SFS vessel data itself must be investigated and the correct orbital source located before any fields can be updated.
ORJ-043 (NKO) — Locate a valid SFS vessel for this NKO (SFS SMA = 49,149 km is impossible). Re-derive all orbital elements, then update CSV Ap, Pe, OrbPeriod.
QXV-373 (NKO) — Identify the correct SFS vessel (NKO at ~13M km SMA, not the Trojan-belt vessel currently matched). Re-derive all orbital elements.
HII-034 (KBO) — Locate the correct SFS vessel for this KBO (~650M km SMA). Re-derive all orbital elements; also resolve the Ap = Pe identity in the CSV.
Part 3a — OrbitalPeriod: Grossly Wrong Values
Replace with Kepler-derived period for each object's SFS SMA.
LBR-888 (Inner) — OrbitalPeriod: 80,126,984 s → ~5,538,413 s
CMA-235 (Inner) — OrbitalPeriod: 128,641,786 s → ~17,678,462 s
AQH-911 (Inner) — OrbitalPeriod: 141,539,025 s → ~34,809,761 s
YWB-419 (Inner) — OrbitalPeriod: 60,914,596 s → ~15,701,992 s
ORF-959 (NKO) — OrbitalPeriod: 18,350,159 s → ~8,955,705 s
JXP-386 (Comet(S)) — OrbitalPeriod: 232,773,625 s → ~154,988,207 s
Part 3b — OrbitalPeriod: Circular KBO Discrepancies
ZYS-113 — OrbitalPeriod: 4,151,137,600 s → ~2,850,365,140 s
BQD-321 — OrbitalPeriod: 3,686,879,936 s → ~2,771,191,780 s
AIK-169 — OrbitalPeriod: 4,006,213,568 s → ~3,190,461,852 s
XWG-404 — OrbitalPeriod: 3,319,449,895 s → ~2,657,516,652 s
XCX-141 — OrbitalPeriod: 2,831,662,046 s → ~2,471,358,232 s
ULX-497 — OrbitalPeriod: 3,023,540,574 s → ~2,643,639,128 s
FVC-765 — OrbitalPeriod: 3,691,331,018 s → ~3,384,082,203 s
HVH-338 — OrbitalPeriod: 3,194,748,780 s → ~2,954,839,977 s
RIZ-636 — OrbitalPeriod: 3,640,938,966 s → ~3,432,240,742 s
Additional OrbitalPeriod corrections for objects already tracked under Ap/Pe:
FUU-512 (NKO) — OrbitalPeriod: ~8,749,260 s → ~10,167,482 s (14% off)
ZNA-698 (NKO) — OrbitalPeriod: ~10,232,015 s → ~8,810,666 s (16% off)
Improper SMA
Check the DB for SMA less than Moho, which shouldn't exist. I already know Tantalus (ORJ-043) was added to the DB with an SMA for Kerbin orbit
LPA-951 also has a negative SMA because it needs to be calculated out of Kerbin's SOI
ATN Main Catalog — Data Issues (atn_main_3110300)
Analysis covering all 8,504 entries across every category.
Scope: MBA (1,841), NKO (1,333), Trojan (1,277), Inner (746), KBO (533), Comet(S) (403), Centaur (328), Comet(L) (20), Moonlet (16), Ejected (7).
Scope and Methodology
Source of truth:
SMAandEcccome from the SFS archive and are treated as authoritative for all orbital calculations.Apkelion,Perikelion, andOrbitalPeriodcome from the CSV and are checked against SFS-derived values.Expected formulae (heliocentric altitude above Kerbol's surface; Kerbol radius = 261,600 km):
Apkelion_expected = SMA × (1 + Ecc) − 261,600 kmPerikelion_expected = SMA × (1 − Ecc) − 261,600 kmOrbitalPeriod_expected = 2π √(SMA³ / μ_Kerbol), μ_Kerbol = 1.1723328 × 10¹⁸ m³/s²Exclusions:
Apkelionshould be null; no automated inconsistencies flagged.TrueAnom: Valid — see Part 4.MBA note on OrbitalPeriod: The 27 flagged MBA objects were confirmed to have SFS-consistent OrbitalPeriod values (Kepler's third law). The remaining 1,814 MBA entries were not checked for OrbitalPeriod; that cross-check was only performed on non-MBA categories.
Part 1 — MBA: Apkelion / Perikelion Errors — 27 Objects
All errors are in the CSV-sourced fields only. SFS-derived orbital elements are unaffected for all 27.
1a. Off by ±10,000,000 km — 15 Objects
1b. Off by ±20–30,000,000 km — 4 Objects
1c. Off by ±3,000,000 km — 2 Objects
1d. Swapped / Transposed Values — 5 Objects
The value for one field was entered in the other. The field that received the swapped value matches the other field's expected value.
1e. Magnitude Error (×10) — 1 Object
Part 2 — Non-MBA: Apkelion / Perikelion Errors — 51 Objects, 65 Field Errors
All errors are in the CSV-sourced fields only unless noted in section 2h. SFS-derived orbital elements are unaffected except for the three SFS-mismatch objects in section 2h.
2a. Single-Field Magnitude Errors (×10 or ×0.1) — 10 Objects
×10 (one extra digit or decimal point shift)
×0.1 (one missing digit or decimal point shift)
2b. Single-Field Round-Number Offset Errors — 16 Objects
2c. Sub-Round-Number Offset Errors — 4 Objects
Display-only errors; orbital rendering unaffected.
2d. Compound Errors (Swap + Secondary) — 8 Objects
Both fields are wrong: one field holds the value expected for the other, plus an additional independent error in that field.
Group 1 — Swap + ×10 on Apkelion (Inner, 3 objects)
Perikelionslot received the correct Apkelion formula result;Apkelionslot received the correct Perikelion result multiplied by 10.Verification:
Stored Apkelion ÷ Expected Perikelion ≈ 10.000for all three.Group 2 — Swap + +30M on Apkelion (Trojan, 3 objects)
Perikelionslot holds the correct Apkelion value;Apkelionslot holds the correct Perikelion value plus exactly 30,000,000 km.Verification:
Stored Apkelion − Expected Perikelion ≈ +30,000,000for all three.Group 3 — Swap + +300M on Apkelion (KBO, 1 object)
Same compound pattern as Group 2 at a larger scale.
Verification:
Stored Apkelion − Expected Perikelion ≈ +300,000,000.Group 4 — Swap + ×0.1 on Perikelion (KBO, 1 object)
Apkelionslot holds the correct Perikelion value;Perikelionslot holds the correct Apkelion value divided by 10.Verification:
Stored Perikelion × 10 ≈ Expected Apkelion.2e. Partial Swap Errors — 4 Objects
One field holds the value expected for the other field; the second field does not match either expected value in a recognisable pattern.
15,412,604) also wrong (+2.1M from expected Ap) with no clean patternNote: FUU-512 and ZNA-698 also have OrbitalPeriod discrepancies (14% and 16% respectively); see Part 3.
2f. Irregular Overestimates on High-Eccentricity Comets — 5 Objects
All have Ecc ≥ 0.986 (near-parabolic).
Perikelionis overestimated by irregular factors — not ×10, not a round offset. Most likely cause: perihelion was computed using a slightly different eccentricity than what is now in the SFS archive, amplified greatly by near-parabolic orbital geometry (a small Ecc difference produces a large Pe difference when Ecc ≈ 1).Apkelionis correct for all five.2g. Small Irregular Offsets — 1 Object
Both fields wrong by sub-500k amounts in opposite directions; no systematic pattern apparent. Likely independent imprecise values.
2h. SFS Orbital Data Inconsistencies — 3 Objects
These objects cannot be resolved by correcting CSV fields alone. The root cause is in the SFS orbital data itself (corrupted, misattributed, or stale vessel record). All three affect orbital trajectory rendering.
ORJ-043 (NKO) — Physically Impossible SFS Semi-Major Axis
The SFS vessel matched to ORJ-043 almost certainly contains corrupted or misattributed orbital data. All SFS-derived elements (
SMA,Ecc,inc,RAAN,Arg,TrueAnom) are untrustworthy.QXV-373 (NKO) — SFS/CSV Orbital Regime Mismatch
The SFS record places QXV-373 in the Trojan belt; the CSV describes an NKO orbit at ~13M km. Most likely a wrong SFS vessel was matched to this UID. All SFS-derived elements would render this NKO at a Trojan orbit distance.
HII-034 (KBO) — SFS/CSV Orbital Regime Mismatch
The CSV Ap and Pe hold identical values (~650M km circular), consistent with KBO classification. The SFS orbit is in the inner system. The identical Ap=Pe also suggests one CSV field was copied from the other. Neither source can be validated without a third reference. SFS-derived elements would render a non-KBO orbit.
Part 3 — OrbitalPeriod Errors — 15 Objects
Identified via Kepler's third law check. All 15 objects have correct
Apkelion/Perikelionvalues; errors are isolated to theOrbitalPeriodCSV field.OrbitalPeriodis not used in orbital trajectory rendering, so these are display-only errors.3a. Grossly Wrong OrbitalPeriod — 6 Objects
The stored period implies a completely different SMA from what the SFS archive records.
ApkelionandPerikelionare essentially exact for all six (sub-20 km delta), confirming the SFS orbit is valid and OrbitalPeriod alone is wrong.The four Inner objects' periods appear to have been calculated from a significantly different (larger) orbit — roughly 2.5–8× the actual SMA — while Ap/Pe were populated correctly from the valid SFS data.
3b. Circular KBO OrbitalPeriod Discrepancies — 9 Objects
All have
Ecc ≈ 0.000; Ap = Pe exactly; both match the SFS SMA. CSV periods are 6–46% above the Kepler prediction with no consistent scale factor. Most probable cause: periods were written before the most recent SFS orbital update which reduced these objects' SMAs, but only the SFS/Ap/Pe fields were refreshed.Part 4 — Notes
4a. Negative TrueAnom Values — Not a Bug
Approximately 44% of elliptic-orbit entries across all categories have a negative
TrueAnom(range −180° to 0°). These are the valid (−180°, +180°] output ofmath.atan2()inbuild_atn_main.pywhen converting MNA to true anomaly. Every consumer ofTrueAnompasses it throughtoMeanAnomaly()inhelpFuncs.js, which handles the (−π, 0) range correctly viaMath.atan2()and modular normalization. All call sites inksaBodyOps.jsandksaSurfaceOps.jsuse this path with no 0–360° assumption. No change needed.4b. Moonlets Not Checked
The 16
Moonletentries were excluded from all Ap/Pe checks. Their SFS orbital elements are relative to the parent body (not Kerbol), so consistency checks require each parent body's gravitational parameter.4c. Ejected Objects Not Checked
The 7
Ejectedentries (allType = Roaming,Makeup = Comet) are on hyperbolic escape trajectories.Apkelionshould be null;Perikelionrepresents hyperbolic perihelion altitude. No inconsistencies were flagged by automated checks.4d. Unknown Size Class
One
Comet(L)entry hasClass = "?". All other 8,503 entries carry a valid class letter (A–E). This is an incomplete record, not a calculation error.Summary
Apkelion / Perikelion Field Errors
OrbitalPeriod Field Errors
Grand total: 93 unique objects with errors (27 MBA + 51 non-MBA + 15 OrbPeriod-only). Orbital trajectory rendering is not affected for 90 of these — errors are in display fields only. The three SFS-mismatch objects (ORJ-043, QXV-373, HII-034) require investigation as their SFS-derived orbital elements do not represent their true orbits.
Fix Tracker
All corrections to
ApkelionandPerikelionshould be recomputed asSMA × (1 ± Ecc) − 261,600from SFS-derived values. The approximate expected values shown below are for reference and verification. All corrections toOrbitalPeriodshould use2π √(SMA³ / μ_Kerbol).Part 1 — MBA: Apkelion / Perikelion
±10M offset — Perikelion
±10M offset — Apkelion
±20–30M offset
±3M offset
Swapped values
×10 magnitude error
Part 2a–2b — Non-MBA: Magnitude Errors
×10 → divide by 10
×0.1 → multiply by 10
Part 2b — Non-MBA: Round-Number Offset Errors
Part 2c — Non-MBA: Sub-Round Offset Errors
Part 2d — Non-MBA: Compound Errors
Group 1 — Swap + ×10 Ap (Inner): set both fields from SFS
Group 2 — Swap + +30M Ap (Trojan): set both fields from SFS
Group 3 — Swap + +300M Ap (KBO): set both fields from SFS
Group 4 — Swap + ×0.1 Pe (KBO): set both fields from SFS
Part 2e — Non-MBA: Partial Swap Errors
Part 2f — Non-MBA: High-Eccentricity Comet Pe Overestimates
Recalculate Perikelion as
SMA × (1 − Ecc) − 261,600from SFS-derived values.Part 2g — Non-MBA: Small Irregular Offsets
Part 2h — SFS Inconsistencies: Requires Investigation
These cannot be fixed by correcting CSV values. The SFS vessel data itself must be investigated and the correct orbital source located before any fields can be updated.
Part 3a — OrbitalPeriod: Grossly Wrong Values
Replace with Kepler-derived period for each object's SFS SMA.
Part 3b — OrbitalPeriod: Circular KBO Discrepancies
Additional OrbitalPeriod corrections for objects already tracked under Ap/Pe:
Improper SMA
Check the DB for SMA less than Moho, which shouldn't exist. I already know Tantalus (ORJ-043) was added to the DB with an SMA for Kerbin orbit
LPA-951 also has a negative SMA because it needs to be calculated out of Kerbin's SOI
Orphaned UIDs