Starship Flight 14 - Launch 2026-09-28T12:15:00 UTC (TUTORIAL SATTOOLS for noobs)

update 2026-09-29: for the final result, and update of this post, dont forget to go here

inspired from scott manley post on x, i’m try creating the orbital using sattools..

scott manley version:

what we know:
launchtime: 2026-09-28T12:15:00 UTC (from spacex website)

rocket :
starship-14

inclination (from x scott)
30.3 degree

altitude (from x scott)
307 KM

Launchpad:
starbase, orbital launch pad 2, texas
Latitude, Longitude: 25.997, -97.157

orbital insertion: T+00:25:19 = 1519 s = 2026-09-28T12:40:19 (from nextspaceflight, update on spacex website the insertion is T+00:25:17. just leave it 00:25:19 :laughing:)

how to

  1. follow the instalation instruction as you can read at the github link above
  2. create export.sh file, fill with this:
#!/bin/bash
export ST_DATADIR="$HOME/sattools"
export ST_TLEDIR="$HOME/tle"
export ST_COSPAR="4451"
export ST_OBSDIR="$HOME/satobs"
export ST_LOGIN="identity=your_space-track.org_email_account&password=your_password"

the ST_COSPAR value (in above example 4451) , you can edit and add with your real location. the file name is sites.txt located at ST_DATADIR (folder data)

  1. make it executable:
    chmod 755 export.sh
  2. run it
    . ./export.sh

and finally run this command:

command:
faketle -n 331.9 -m 218.1 -q 306 -Q 308 -I 30.3 -t 2026-09-28T12:15:00 -d 1519 -i 99998U > fake-starship.txt && satorbit -c fake-starship.txt -q -t 2026-09-28T12:40:19 -B 25.997 -L -97.157

-n = raan ascending node (longitude)
-m = mean anomaly (latitude)

if your target orbital altitude is 307 km, put it between -q and -Q, so become -q 306 -Q 308

the first -t = launch time in utc
-d = this is orbital insertion in second since the launch time.
orbital insertion is when the upper stage of rocket fires its engine to reach the required orbital velocity and altitude. For a low Earth orbit, that velocity is roughly 7.8 km/s. this will become the epoch time of TLE

-i = you set the norad id here. you can freely change it with any number

the second -t = orbital insertion in UTC
-B -L = latitude, longitude of the launchpad

you will playing much with -n and -m. use the < and > on keyboard to move the time. use [ and ] , { and } to rotate the globe. press l to adjust the time delay.

for the best result adjust the -m and -n value, then move the time with < to the launch time, so the position of rocket is exactly on launchpad location.

good luck! 73

result:

STARSHIP-14
1 99998U          26271.52799769  .00000000  00000-0  50000-4 0    08
2 99998  30.3000 331.9000 0001496   0.0000 218.1000 15.88318959    07

start and orbital insertion:

no sunlit when enter southeast asia

usa west coast, hawai, and africa. The rocket gets sunlite

starship14.txt (152 Bytes)
launchsites.txt (583 Bytes)

3 Likes

Live:

1 Like

Thanks, at least I now get that the satelites will not show up in the view of my opticals. Aiming at the more southern regions with this launch.

1 Like





comparing official starlink vs sattools

1 Like

update:
launch time 2026-09-28T12:48:58 UTC

altitude: 276 KM

orbital insertion time: 25:16 = 1516 s

update command:
faketle -n 340.6 -m 218.3 -q 275 -Q 277 -I 30.5122 -t 2026-09-28T12:48:58 -d 1516 -i 99998U > fake-starship.txt && satorbit -c fake-starship.txt -q -t 2026-09-28T13:14:14 -B 25.997 -L -97.157

result:

STARSHIP-14
1 99998U          26271.55155093  .00000000  00000-0  50000-4 0    07
2 99998  30.5122 340.6000 0001503   0.0000 218.3000 15.99431098    04

starship14.txt (152 Bytes)

deorbit now

i test and notice this TLE is not good and accurate. comparing with the reality it earlier around 5 minutes. this make me confuse. ussualy i just follow the old tutorial that use -d 300 (5 minutes). but in this post i follow the example from @cbassa sattools github

not satisfy with the result, i try old tutorial with -d 300 , and the result is very good. the ground track and time is accurate than using real orbital insertion .

im confuse. why the result is different. and after meditation 24 hours :laughing: i got conclusion that the sattools (faketle) is pure keplerian, it does not simulate the real powered flight, it only create a perfect coasting orbit and ask you at what moment do you want me to start this perfect orbit, and where should the satellite / rocket be at that moment.

and at same time finally i know what this sentence mean on old tutorial
image

the keyword is accelleration.

In the real world, a rocket launched from a launchpad does not suddenly appear in orbit at orbital velocity—around 27,000 km/h for LEO. It starts from a standstill at 0 km/h, then gradually and steadily accelerates until it reaches orbital velocity.

Therefore, when we set the -d value—for example, to 1,516 seconds, or 25 minutes and 16 seconds—using FakeTLE, since FakeTLE is purely Keplerian, it means that from launch time -t until 25 minutes and 16 seconds later, by faketle the satellite or rocket is assumed to be traveling at the ideal orbital velocity of 27,000 km/h. That is why the resulting TLE makes it appear to travel faster and farther.

So, in the old tutorial, when -d 300 was used and the location was set exactly at the launchpad, it did not literally mean that orbital insertion occurred 300 seconds after launch or that the location was directly above the launchpad. It was simply an attempt to compensate for and reconcile the difference between the ideal orbital velocity and the actual acceleration profile of the rocket.

I also tried using a -d value of 210 seconds, or 3.5 minutes, but the resulting TLE was still two minutes ahead. Worse, its trajectory shifted even farther from the actual one.

Therefore, for LEO orbit, I still stand and believe that -d 300 is the best choice.

finaly this is my command:
faketle -n 340 -m 120.1 -q 275 -Q 277 -I 30.3 -t 2026-09-28T12:48:58 -d 300 -i 99998U > fake-starship.txt && satorbit -c fake-starship.txt -q -t 2026-09-28T12:53:58 -B 25.997 -L -97.157

STARSHIP-14
1 99998U          26271.53747685  .00000000  00000-0  50000-4 0    09
2 99998  30.3000 340.0000 0001503   0.0000 120.1000 15.99431098    01

proof for accuracy, i compare with the starship live streaming

orbital insertion - eastern brazil
T +25:16 = 13:14:14 UTC (blue dot)

above south africa
T+ 37:17:00 = 13:26:15 utc

above central java .yogyakarta , indonesia = T +01:01:08 = 13:50:06 UTC

above surabaya, madura, indonesia = T + 01:01:51 = 13:50:49 UTC