Author Topic: SpaceX Manifest Table Formatting Discussion  (Read 6164 times)

Online gongora

  • Global Moderator
  • Full Member
  • *****
  • Posts: 1807
  • US
  • Liked: 1215
  • Likes Given: 929
SpaceX Manifest Table Formatting Discussion
« on: 06/20/2017 04:11 PM »
It seems that starhawk92 has had other things crop up in his life that are more important than maintaining a launch manifest on an internet forum (hard to believe, but sometimes these things happen).  I'll take over the SpaceX manifest maintenance unless someone else is really eager to do it.

We've been using a fixed width format for the SpaceX manifest, and different people have different opinions on how best to make use of the space in the table.  I have a format that is a little bit different from what starhawk92 has been using, you can see it here:
https://forum.nasaspaceflight.com/index.php?topic=40231.msg1533858#msg1533858

I use one line per mission.  Other information (FH booster serial numbers) goes in the footnotes.

Estimated Local Date and Time:  They usually aren't really NET dates, they're our best guess of when the flight will be.  They could move right, could move left, could go away.  You never really know until it takes off.  This is the date/time at the launch pad (local time).  The number following the time is the UTC offset, so 1200/-4 (local) is 1600 (UTC).  If a flight is scheduled for the second quarter of 2018 I put 2018-Q2, not 2018-04.  If local and UTC date are different I put an asterisk between the date and time.

LV/Mission:  Type of launch vehicle (F9/FH), and the mission numbers from the FCC permits for the launch.  I will probably remove the mission numbers in the future because I can't reliably match them up anymore.

Return: L=Land, S=Sea, X=Expendable.  This keeps the column small and fits FH flights in 3 characters.  (I haven't decided whether to turn the "X" green when it is successfully expended.)

Site: My personal abbreviations, I think they are fairly easy to understand.  C=Canaveral=KSC/CCAFS, V=Vandenberg, B=Boca Chica.

Footnotes: I update the footnote numbers to match the flight numbers.  I haven't really decided whether to use different numbers for FH flights, but am leaning against doing that.

For anyone who hasn't noticed yet, the payload name is a link to the mission discussion thread.  In flights since JCSAT-16 the discussion thread (and also the update thread) has a section at the top with links to other NSF threads and articles for that mission.
« Last Edit: 06/25/2017 08:05 PM by gongora »

Offline ATPTourFan

  • Member
  • Posts: 23
  • Liked: 2
  • Likes Given: 197
Re: SpaceX Manifest Table Formatting Discussion
« Reply #1 on: 06/20/2017 08:20 PM »
I like all the aspects of your formatting proposal except for the Return column. With 3 characters you can still do something like:

EXP = expendable
LZ1 = LZ1 at CCAFS
JRI = Just Read the Instructions (or whatever 3 characters is best)
OCU = Of course I Still Love You (or whatever 3 characters is best)
LZ? = whatever SpaceX designates the landing pad at SLC-4 in VAFB

Offline Lar

  • Fan boy at large
  • Global Moderator
  • Senior Member
  • *****
  • Posts: 8333
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 5114
  • Likes Given: 3417
Re: SpaceX Manifest Table Formatting Discussion
« Reply #2 on: 06/21/2017 01:21 AM »
Why is the core number column called "reuse" ?? Otherwise I think this is awesome!

A: because it didn't get changed yet.
« Last Edit: 06/21/2017 02:44 AM by Lar »
"I think it would be great to be born on Earth and to die on Mars. Just hopefully not at the point of impact." -Elon Musk
"We're a little bit like the dog who caught the bus" - Musk after CRS-8 S1 successfully landed on ASDS OCISLY

Online rockets4life97

  • Full Member
  • ***
  • Posts: 366
  • Liked: 166
  • Likes Given: 103
Re: SpaceX Manifest Table Formatting Discussion
« Reply #3 on: 06/21/2017 07:53 AM »
Hmmm... Gongora's new version wraps onto two lines on my browser. Not sure why.

Online gongora

  • Global Moderator
  • Full Member
  • *****
  • Posts: 1807
  • US
  • Liked: 1215
  • Likes Given: 929
Re: SpaceX Manifest Table Formatting Discussion
« Reply #4 on: 06/21/2017 05:28 PM »
I've switched the table in the top post to new format.  I've been told it's still a few characters too wide to show up as a single line on some browsers.  If the width is a big problem I could scrunch it down a little more but I like having two spaces between most of the columns so it is easier to read.

I removed the FCC mission numbers from my table, which meant I could no longer spell out FHeavy, and I wanted more visual distinction between F9 and FH, so I ended up just putting "H" for the Falcon Heavy launch vehicle.

(The old table format is backed up in Reply #20 if anyone wants to refer back to it.  I'll only be maintaining the table in the top post.)
« Last Edit: 06/21/2017 05:44 PM by gongora »

Offline Lar

  • Fan boy at large
  • Global Moderator
  • Senior Member
  • *****
  • Posts: 8333
  • Saw Gemini live on TV
  • A large LEGO storage facility ... in Michigan
  • Liked: 5114
  • Likes Given: 3417
Re: SpaceX Manifest Table Formatting Discussion
« Reply #5 on: 06/21/2017 05:46 PM »
I think the subscript tag migthe be helpful to get more characters on?

[ sub ] and [/ sub ]  (minus the spaces)

MY HACKS ARE DESCRIBED IN ALL CAPS...  FROM HERE IS A COPY OF THE HEADER POST... WITH HACKS
++++++++

Discussion of the manifest, and updates. The best guess at the current manifest is in this post. 
This table is now being maintained by gongora

TEXT WITHOUT SUB:
Prior thread 3 : https://forum.nasaspaceflight.com/index.php?topic=40049.0
SAME TEXT WITH SUB:

Prior thread 3 : https://forum.nasaspaceflight.com/index.php?topic=40049.0


TEST PREFACE WITH SUB

Site: C=Canaveral (UTC-4 EDT,UTC-5 EST)
         SLC-40: Damaged by vehicle explosion (no launches until around August 2017)
         LC-39A: Active for F9, will need further work for FH and Commercial Crew
       V=Vandenberg (UTC-7 PDT,UTC-8 PST)
         SLC-4E: Active for F9
       B=Boca Chica (UTC-5 CDT,UTC-6 CST)
         Site preparation work underway

Daylight saving time starts second Sunday in March, ends first Sunday in November,
time changes at 2:00 a.m. local time
Launch Windows, if known, are in the footnotes.


CHUNK OF TABLE WITHOUT SUB FOR COMPARISION


       LOCAL        LV  Core   Ret-                                    MASS         No-
EST. DATE  TIME/UTC     S/N    urn  PAYLOAD(S)                    ORB  (kg)   Site  tes
---------- -------- --- ------ ---  ----------------------------  ---  -----  ----- ---
2015-12-22          F9  1019   L    ORBCOMM OG2 Launch 2          LEO  1892   C-40   20
2016-01-17 1042/-8  F9         S    Jason-3                       LEO  553    V-4E   21
2016-03-04 1835/-5  F9         S    SES-9                         GTO  5271   C-40   22
2016-04-08 1643/-4  F9  1021   S    CRS-8                         LEO  ~9k    C-40   23
2016-05-06 0121/-4  F9  1022   S    JCSAT-14                      GTO  4696   C-40   24
2016-05-27 1740/-4  F9  1023   S    Thaicom 8                     GTO  3025   C-40   25


TABLE AND POSTSCRIPT ITEMS WITH SUB



       LOCAL        LV  Core   Ret-                                    MASS         No-
EST. DATE  TIME/UTC     S/N    urn  PAYLOAD(S)                    ORB  (kg)   Site  tes
---------- -------- --- ------ ---  ----------------------------  ---  -----  ----- ---
2015-12-22          F9  1019   L    ORBCOMM OG2 Launch 2          LEO  1892   C-40   20
2016-01-17 1042/-8  F9         S    Jason-3                       LEO  553    V-4E   21
2016-03-04 1835/-5  F9         S    SES-9                         GTO  5271   C-40   22
2016-04-08 1643/-4  F9  1021   S    CRS-8                         LEO  ~9k    C-40   23
2016-05-06 0121/-4  F9  1022   S    JCSAT-14                      GTO  4696   C-40   24
2016-05-27 1740/-4  F9  1023   S    Thaicom 8                     GTO  3025   C-40   25
2016-06-15 1029/-4  F9         S    Eutelsat 117W B & ABS-2A      GTO  4200   C-40   26
2016-07-18 0045/-4  F9         L    CRS-9                         LEO  ~9k    C-40   27
2016-08-14 0126/-4  F9         S    JCSAT-16                      GTO  ~4600  C-40   28
2016-09-01 0907/-4  F9         N/A  AMOS-6(destroyed in pad test) GTO  5500   C-40   29
2017-01-14 0954/-8  F9  1029   S    Iridium NEXT (Flight 1)       PLR  9600   V-4E   30
2017-02-19 0939/-5  F9  1031   L    CRS 10                        LEO  ~9k    C-39A  31
2017-03-16 0200/-4  F9  1030   X    Echostar 23                   GTO  ~5500  C-39A  32
2017-03-30 1827/-4  F9  1021.2 S    SES-10                        GTO  5282   C-39A  33
2017-05-01 0715/-4  F9  1032   L    NROL-76                       LEO  ?      C-39A  34
2017-05-15 1921/-4  F9  1034   X    Inmarsat 5 F4                 GTO  6086   C-39A  35
2017-06-03 1707/-4  F9  1035   L    CRS 11                        LEO  ~9k    C-39A  36
---------------------------------------------------------------------------------------
2017-06-23 1410/-4  F9  1029.2 S    BulgariaSat-1                 GTO  3669   C-39A  37
2017-06-25 1325/-7  F9  1036   S    Iridium NEXT (Flight 2)       PLR  9600   V-4E   38
2017-07-xx 1935/-4  F9         X    Intelsat 35e                  GTO  ~6k    C-39A  39
2017-07-late        F9         ?    SES-11/Echostar 105           GTO  5400   C-39A  40
2017-08-01          F9         L    CRS 12                        LEO  ~9k    C
2017-08             F9         L    Air Force X-37B OTV-5         LEO  5400   C
2017-08             F9         ?    FORMOSAT-5                    SSO  ~525   V-4E   41
2017-08-24          F9         S    Iridium NEXT (Flight 3)       PLR  9600   V-4E       
2017-Q3             F9         S    Koreasat-5A                   GTO  3500   C
2017-10             F9         S    GovSat-1 (SES-16)             GTO  4000   C
2017                 H         LL?  Falcon Heavy Demo Flight                  C-39A  50
2017-10             F9         S    Iridium NEXT (Flight 4)       PLR  9600   V-4E
2017-10             F9         ?    SAOCOM 1A                     SSO  3000   V-4E
2017-11             F9         L    CRS 13                        LEO  ~9k    C
2017-Q4             F9         S    SES-14 (NASA GOLD payload)    GTO  4200   C
2017-12             F9         S    Iridium NEXT (Flight 5)       PLR  9600   V-4E
2017                 H         LL?  STP-2 (US Air Force)          MEO  ~8k?   C-39A
2017-Q4             F9              Hispasat 1F                   GTO  ~5k    C      60
2017-12             F9              Bangabandhu                   GTO  ~3500  C      61
2017                F9              Paz & co-passenger            SSO  1400   V-4E   62
2018                F9              Spaceflight SSO-A (575km)     SSO         V-4E   70
2018                F9         S    Es'hail 2                     GTO  ~3k    C
2018                F9         ?    PSN-6 and co-passenger        GTO  5000   C
2018-02             F9         L    CRS 14                        LEO  ~9k    C
2018-02             F9              Iridium NEXT (Flight 6)       PLR  9600   V-4E
2018-03             F9         ?    CCtCap DM1                    LEO         C-39A
2018-03-20          F9              NASA (TESS)                   HEO  325    C
2018-04             F9         L    CRS 15                        LEO  ~9k    C
2018-04             F9              Iridium NEXT (Flight 7)       PLR  9600   V-4E
2018-H1             F9              CCiCap In-Flight Abort Test   SUB         C-39A
2018-H1             F9              Telstar 18 Vantage/Apstar-5C  GTO  >5400  C
2018-H1             F9              Telstar 19 Vantage            GTO  >5400  C
2018-05             F9              USAF GPS III A-2              MEO  3880   C
2018-06             F9              Telkom 4                      GTO         C      68
2018                F9              CCtCap DM2 (Crew)             LEO         C-39A
2018-mid            F9              Iridium NEXT 8/GRACE-FO       SSO  ~6000  V     
2018                 H              Arabsat 6A                    GTO  ~6k    C/B
2018-08             F9         L    CRS 16                        LEO  ~9k    C
2018-Q3             F9              RADARSAT Constellation        SSO  1400   V-4E
2018                F9              OHB SARah 1                   SSO  ~2200  V-4E
2018-10             F9         L    CRS 17                        LEO  ~9k    C
2018-Q4             F9              Spaceflight SSO-B (500km)     SSO         V-4E   70
2018-Q4             F9              GiSat-1                       GTO  ~6k    C/B
2018-H2             F9              Spaceflight GTO-1(200x36k/km) GTO         C      70
2018-H2             F9              Spaceflight GTO-2(200x60k/km) GTO         C      70
2018-12             F9         L    CRS 18                        LEO  ~9k    C
2018-end             H         ???  SpaceX Crewed Circumlunar     TLI  ~10k?  C-39A  99
2018                F9              SAOCOM 1B                     SSO  3000   V-4E
2019                F9              CRS 19-20                     LEO         C
2019-02             F9              USAF GPS IIIA-3               MEO  3880   C
2019                F9              OHB SARah 2/3                 SSO  ~3600  V-4E
2019-H2             F9              Spaceflight SSO-C (500km SSO) SSO         V-4E   70
2020                F               Inmarsat 6 F1                 GTO         C/B    65
2020                 H              Red Dragon (Mars Surface)     TMI  ~11k   C/B
2020-H1             F9              Spaceflight GTO-C(200x36k/km) GTO         C/B    70
2020-H1             F9              Spaceflight SSO-D (500km SSO) SSO         V-4E   70
2020-2021            H              ViaSat 3-Americas or 3-EMEA   GTO  6400   C/B    69
2021-04             F9              SWOT                          LEO  2000   V-4E
TBD (NET 2022)       H              ViaSat 3-Asia (maybe)         GTO  6400   C/B    69
TBD                 F               Inmarsat                      GTO         C/B
TBD (2019-2024)     F9              Commercial Crew (6 flights)   LEO         C-39A
TBD (2019-2024)     F9              CRS-2 (6+ flights)            LEO         C
TBD                 F               EutelSat

Return: L=Land,S=Sea,X=Expendable,N/A=Not Applicable
Launch Vehicle: F9=Falcon 9, H=Falcon Heavy, F=Falcon 9 or Heavy
Colors: Successful / Unsuccessful / Mars!!!! / Footnotes

L2 SpaceX CRS External Cargo
L2 Level SpaceX Falcon 9 Stage Watch
SpaceX Launch Log (past launches)
Wikipedia Falcon Launches
Viewing flights from Vandenberg
Upcoming SpaceX Talks

NOTES:
[20] Orbcomm OG2 Launch 2 [FCC F9-21]
[21] Jason-3 [FCC F9-19]
[22] SES-9 [FCC F9-22]
[23] CRS-8 [FCC 23] Discussion / Updates
[24] JCSAT-14 [FCC F9-24] Discussion / Updates / L2 Coverage / Pre-Launch Article /
 Post-Launch Article
[25] Thaicom-8 [FCC F9-25] Discussion / Updates / L2 Coverage / Post-Launch Article
[26] Eutelsat 117 West B & ABS-2A [FCC F9-26] Discussion / Updates / L2 Coverage /
 Pre-Launch Article / Post-Launch Article
[27] CRS-9 [FCC 27] Discussion / Updates / L2 Coverage /
 Return Updates / Static Fire Article / Launch Article
[28] JCSat-16 [FCC F9-28] Discussion
[29] Amos-6 [FCC F9-29] Discussion
[30] Iridium NEXT Flight 1 [FCC F9-30] Discussion
[31] CRS-10 [FCC 32] Discussion
[32] EchoStar 23 [FCC F9-31] Discussion
[33] SES-10 [FCC F9-33] Discussion
[34] NROL-76 [FCC 1363] Discussion
[35] Inmarsat 5 F4 [FCC F9-34] Discussion
[36] CRS-11 Discussion

[37] Bulgariasat-1 Discussion Launch Window 14:10 16:10 (Eastern)
[38] Iridium Next (Flight 2) [FCC 1338] Discussion
[39] Intelsat 35e [FCC 1372] Discussion Launch Window 19:35-20:35 (Eastern)
[40] SES 11/Echostar 105 Discussion
[41] FORMOSAT-5 Discussion
[50] FH Demo - Serial Numbers: Center:1033  Side1:1023.2  Side2: 1025.2
[60] Hispasat 1f also called Hispasat 30W-6
[61] Bangabandhu News Article / Satellite Order Press Release / Gunter's Site
[62] Paz (Hisdesat) post in manifest thread / article in DW
[65] Inmarsat 6 F1 SpaceNews mention / Airbus contract / Gunter / Space Intel mention
[68] Telkom 4 links Gunter
[69] Viasat 3 : one of first two Viasat 3 birds in mid-2019 or early-2020.
  Also third Viasat 3 if it gets built?
  ViaSatellite 2/10/16 SpaceNews 2/10/2016 Gunter
[70] Spaceflight Industries : Upcoming Spaceflight Ind. schedule
[99] SpaceX announcement


END TEXT WITH SUB

[xx] Europasat/HellasSat 3 moved to different launch vehicle
[xx] ABS-8 Satellite build cancelled
[xx] SHERPA cancelled from FORMOSAT-5 flight

Competitions for future payloads:
STP-3
Air Force First 6 EELV

L2 notes on manifest:
https://forum.nasaspaceflight.com/index.php?topic=42937.msg1679127#msg1679127
https://forum.nasaspaceflight.com/index.php?topic=42839.msg1683254#msg1683254

Last 10 Edits:
Jun 17  Changed table format, now being maintained by gongora
Jun 06  edit/gongora: Slipped Bulgariasat 2 days.  Added X-37B in August 2017
Jun 05  edit/gongora: Marked CRS-11 successful.  Removed speculative Mars mission dates.
Jun 02  edit/gongora: Removed Eutelsat Quantum
May 25  edit/gongora: Moved Iridium Flight 2 to June 25 (1325 PDT).  Moved Intelsat 35e to July 1.
May 24  edit/gongora: Moved Koreasat-5A to August (educated guess), CCiCap In-Flight Abort to 2018
         removed estimated launch month from FH Demo and STP-2
May 23  edit/gongora: Moved Eutelsat Quantum to 2019
May 21  edit/gongora: Added Telkom 4, June 2018
May 20  edit/gongora: Moved CCtCap DM-1 to March 2018
May 17  edit/gongora: Moved PSN-6 to 2018
May 14  edit/gongora: updated masses (Telstar, Es'hail-2, Hispasat, GiSat) and core numbers for multiple missions 

All comments and updates are welcomed!  Thank you to all contributors!
« Last Edit: 06/21/2017 05:53 PM by Lar »
"I think it would be great to be born on Earth and to die on Mars. Just hopefully not at the point of impact." -Elon Musk
"We're a little bit like the dog who caught the bus" - Musk after CRS-8 S1 successfully landed on ASDS OCISLY

Online envy887

  • Senior Member
  • *****
  • Posts: 2563
  • Liked: 1144
  • Likes Given: 724
Re: SpaceX Manifest Table Formatting Discussion
« Reply #6 on: 06/21/2017 08:10 PM »
[ pre ] TEXT HERE [ /pre ] Also gives monospace formatting in a smaller font:

 TEXT HERE 


You can also boldface:


 TEXT HERE 

« Last Edit: 06/22/2017 03:33 PM by envy887 »

Offline rosbif73

  • Veteran
  • Full Member
  • **
  • Posts: 204
  • Liked: 8
  • Likes Given: 16
Re: SpaceX Manifest Table Formatting Discussion
« Reply #7 on: 06/22/2017 11:35 AM »
If the width is a big problem I could scrunch it down a little more but I like having two spaces between most of the columns so it is easier to read.

It occurs to me that if you abbreviate the launch site as K for Kennedy (LC39A), C for Canaveral (LC40), V for Vandenberg and B for Boca Chica, you could save three extra characters in width :-)

Online gongora

  • Global Moderator
  • Full Member
  • *****
  • Posts: 1807
  • US
  • Liked: 1215
  • Likes Given: 929
Re: SpaceX Manifest Table Formatting Discussion
« Reply #8 on: 06/22/2017 02:59 PM »
If the width is a big problem I could scrunch it down a little more but I like having two spaces between most of the columns so it is easier to read.

It occurs to me that if you abbreviate the launch site as K for Kennedy (LC39A), C for Canaveral (LC40), V for Vandenberg and B for Boca Chica, you could save three extra characters in width :-)

It doesn't save much because future flights would be listed like K/C, C/B, K/C/B.  Unless you add E for launching East from somewhere.

Online rockets4life97

  • Full Member
  • ***
  • Posts: 366
  • Liked: 166
  • Likes Given: 103
Re: SpaceX Manifest Table Formatting Discussion
« Reply #9 on: 06/22/2017 03:02 PM »
If the width is a big problem I could scrunch it down a little more but I like having two spaces between most of the columns so it is easier to read.

It occurs to me that if you abbreviate the launch site as K for Kennedy (LC39A), C for Canaveral (LC40), V for Vandenberg and B for Boca Chica, you could save three extra characters in width :-)

It doesn't save much because future flights would be listed like K/C, C/B, K/C/B.  Unless you add E for launching East from somewhere.

Or just make an educated guess and adjust the launch pad when new info is available.

Offline Comga

  • Senior Member
  • *****
  • Posts: 3886
  • Liked: 1213
  • Likes Given: 1037
Re: SpaceX Manifest Table Formatting Discussion
« Reply #10 on: 06/23/2017 02:11 AM »
It's still 16 characters too wide for my phone
Wrapping makes it very difficult for me to read
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Online ClayJar

  • Full Member
  • **
  • Posts: 298
  • Baton Rouge, LA, USA
  • Liked: 611
  • Likes Given: 59
Re: SpaceX Manifest Table Formatting Discussion
« Reply #11 on: 06/23/2017 12:49 PM »
Since the manifest table is a table and all, I wondered how it would render on screens large and small if the manifest table were actually posted as a [table].  So, I reworked it (including learning things like [td][hr][/td] won't even preview and plain [hr] between rows actually renders but splits the table into multiple tables, breaking the column alignment).

This is a copy of the current first post, coded as a table.  (I put just the LV column in bold, as I thought as a rendered table it needed something to help visually break up/anchor the line.)  Obviously reposted unquoted for "test as you post" fidelity.  Since the preview is not the same width as a post in thread, and since I can't see what it looks like on my phone without it being posted, here goes nothing.

Any comments, questions, or rapid mod edits/deletion if rendering this post messes up the thread display?  (Hey, it looked great in preview. ;D)



Discussion of the manifest, and updates. The best guess at the current manifest is in this post. 
This table is now being maintained by gongora

Prior thread 3 : https://forum.nasaspaceflight.com/index.php?topic=40049.0

Site: C=Canaveral (UTC-4 EDT,UTC-5 EST)
         SLC-40: Damaged by vehicle explosion (no launches until around August 2017)
         LC-39A: Active for F9, will need further work for FH and Commercial Crew
      V=Vandenberg (UTC-7 PDT,UTC-8 PST)
         SLC-4E: Active for F9
      B=Boca Chica (UTC-5 CDT,UTC-6 CST)
         Site preparation work underway


Daylight saving time starts second Sunday in March, ends first Sunday in November, time changes at 2:00 a.m. local time
Launch Windows, if known, are in the footnotes.

.LOCALLVCoreRet-..MASS.No-
EST. DATETIME/UTC.S/NurnPAYLOAD(S)ORB(kg)Sitetes
------------------------------------------------------
2015-12-22.F91019LORBCOMM OG2 Launch 2LEO1892C-4020
2016-01-171042/-8F9.SJason-3LEO553V-4E21
2016-03-041835/-5F9.SSES-9GTO5271C-4022
2016-04-081643/-4F91021SCRS-8LEO~9kC-4023
2016-05-060121/-4F91022SJCSAT-14GTO4696C-4024
2016-05-271740/-4F91023SThaicom 8GTO3025C-4025
2016-06-151029/-4F9.SEutelsat 117W B & ABS-2AGTO4200C-4026
2016-07-180045/-4F9.LCRS-9LEO~9kC-4027
2016-08-140126/-4F9.SJCSAT-16GTO~4600C-4028
2016-09-010907/-4F9.N/AAMOS-6(destroyed in pad test)GTO5500C-4029
2017-01-140954/-8F91029SIridium NEXT (Flight 1)PLR9600V-4E30
2017-02-190939/-5F91031LCRS 10LEO~9kC-39A31
2017-03-160200/-4F91030XEchostar 23GTO~5500C-39A32
2017-03-301827/-4F91021.2SSES-10GTO5282C-39A33
2017-05-010715/-4F91032LNROL-76LEO?C-39A34
2017-05-151921/-4F91034XInmarsat 5 F4GTO6086C-39A35
2017-06-031707/-4F91035LCRS 11LEO~9kC-39A36
------------------------------------------------------
2017-06-231410/-4F91029.2SBulgariaSat-1GTO3669C-39A37
2017-06-251325/-7F91036SIridium NEXT (Flight 2)PLR9600V-4E38
2017-07-xx1935/-4F9.XIntelsat 35eGTO~6kC-39A39
2017-07-late.F9.?SES-11/Echostar 105GTO5400C-39A40
2017-08-01.F9.LCRS 12LEO~9kC.
2017-08-17.F9.LAir Force X-37B OTV-5LEO5400C.
2017-08.F9.?FORMOSAT-5SSO~525V-4E41
2017-08-24.F9.SIridium NEXT (Flight 3)PLR9600V-4E.
2017-Q3.F9.SKoreasat-5AGTO3500C.
2017-10.F9.SGovSat-1 (SES-16)GTO4000C.
2017-10.F9.SIridium NEXT (Flight 4)PLR9600V-4E.
2017-10.F9.?SAOCOM 1ASSO3000V-4E.
2017.H.LLSFalcon Heavy Demo Flight.C-39A.50
2017-11.F9.LCRS 13LEO~9kC.
2017-Q4.F9.SSES-14 (NASA GOLD payload)GTO4200C.
2017-12.F9.SIridium NEXT (Flight 5)PLR9600V-4E.
2017-Q4.F9..Hispasat 1FGTO~5kC60
2017-12.F9..BangabandhuGTO~3500C61
2017.F9..Paz & co-passengerSSO1400V-4E62
2018.F9..Spaceflight SSO-A (575km)SSO.V-4E70
2018.F9.SEs'hail 2GTO~3kC.
2018.F9.?PSN-6 and co-passengerGTO5000C.
2018-02.F9.LCRS 14LEO~9kC.
2018-02.F9..Iridium NEXT (Flight 6)PLR9600V-4E.
2018-H1.H.LLSArabsat 6AGTO~6kC-39A.
2018-03.F9.?CCtCap DM1LEO.C-39A.
2018-03-20.F9..NASA (TESS)HEO325C.
2018-04.F9.LCRS 15LEO~9kC.
2018-04.F9..Iridium NEXT (Flight 7)PLR9600V-4E.
2018-H1.F9..CCiCap In-Flight Abort TestSUBC-39A.
2018-H1.F9..Telstar 18 Vantage/Apstar-5CGTO>5400C.
2018-H1.F9..Telstar 19 VantageGTO>5400C.
2018-H1.H.LLSSTP-2 (US Air Force)MEO~8k?C-39A.
2018-05.F9..USAF GPS III A-2MEO3880C.
2018-06.F9..Telkom 4GTO.C68
2018.F9..CCtCap DM2 (Crew)LEO.C-39A.
2018-mid.F9..Iridium NEXT 8/GRACE-FOSSO~6000V.
2018-08.F9.LCRS 16LEO~9kC.
2018-Q3.F9..RADARSAT ConstellationSSO1400V-4E.
2018.F9..OHB SARah 1SSO~2200V-4E.
2018-10.F9.LCRS 17LEO~9kC.
2018-Q4.F9..Spaceflight SSO-B (500km)SSO.V-4E70
2018-Q4.F9..GiSat-1GTO~6kC/B.
2018-H2.F9..Spaceflight GTO-1(200x36k/km)GTO.C70
2018-H2.F9..Spaceflight GTO-2(200x60k/km)GTO.C70
2018-12.F9.LCRS 18LEO~9kC.
2018.F9..SAOCOM 1BSSO3000V-4E.
2018-2019.H.??SpaceX Crewed CircumlunarTLI~10k?C-39A99
2019.F9..CRS 19-20LEO.C.
2019-02.F9..USAF GPS IIIA-3MEO3880C.
2019.F9..OHB SARah 2/3SSO~3600V-4E.
2019-H2.F9..Spaceflight SSO-C (500km SSO)SSO.V-4E70
2020.F..Inmarsat 6 F1GTO.C/B65
2020.H..Red Dragon (Mars Surface)TMI~11kC/B
2020-H1.F9..Spaceflight GTO-C(200x36k/km)GTO.C/B70
2020-H1.F9..Spaceflight SSO-D (500km SSO)SSO.V-4E70
2020-2021.H..ViaSat 3-Americas or 3-EMEAGTO6400C/B69
2021-04.F9..SWOTLEO2000V-4E.
TBD (NET 2022).H..ViaSat 3-Asia (maybe)GTO6400C/B69
TBD.F..InmarsatGTO.C/B.
TBD (2019-2024).F9..Commercial Crew (6 flights)LEO.C-39A.
TBD (2019-2024).F9..CRS-2 (6+ flights)LEO.C.
TBD.F..EutelSat

Return: L=Land,S=Sea,X=Expendable,N/A=Not Applicable
Launch Vehicle: F9=Falcon 9, H=Falcon Heavy, F=Falcon 9 or Heavy
Colors: Successful / Unsuccessful / Mars!!!! / Footnotes

L2 SpaceX CRS External Cargo
L2 Level SpaceX Falcon 9 Stage Watch
SpaceX Launch Log (past launches)
Wikipedia Falcon Launches
Viewing flights from Vandenberg
Upcoming SpaceX Talks

NOTES:
[20] Orbcomm OG2 Launch 2 [FCC F9-21]
[21] Jason-3 [FCC F9-19]
[22] SES-9 [FCC F9-22]
[23] CRS-8 [FCC 23] Discussion / Updates
[24] JCSAT-14 [FCC F9-24] Discussion / Updates / L2 Coverage / Pre-Launch Article / Post-Launch Article
[25] Thaicom-8 [FCC F9-25] Discussion / Updates / L2 Coverage / Post-Launch Article
[26] Eutelsat 117 West B & ABS-2A [FCC F9-26] Discussion / Updates / L2 Coverage / Pre-Launch Article / Post-Launch Article
[27] CRS-9 [FCC 27] Discussion / Updates / L2 Coverage / Return Updates / Static Fire Article / Launch Article
[28] JCSat-16 [FCC F9-28] Discussion
[29] Amos-6 [FCC F9-29] Discussion
[30] Iridium NEXT Flight 1 [FCC F9-30] Discussion
[31] CRS-10 [FCC 32] Discussion
[32] EchoStar 23 [FCC F9-31] Discussion
[33] SES-10 [FCC F9-33] Discussion
[34] NROL-76 [FCC 1363] Discussion
[35] Inmarsat 5 F4 [FCC F9-34] Discussion
[36] CRS-11 Discussion

[37] Bulgariasat-1 Discussion Launch Window 14:10 16:10 (Eastern)
[38] Iridium Next (Flight 2) [FCC 1338] Discussion
[39] Intelsat 35e [FCC 1372] Discussion Launch Window 19:35-20:35 (Eastern)
[40] SES 11/Echostar 105 Discussion
[41] FORMOSAT-5 Discussion
[50] FH Demo - Serial Numbers: Center:1033  Side1:1023.2  Side2: 1025.2
[60] Hispasat 1f also called Hispasat 30W-6
[61] Bangabandhu News Article / Satellite Order Press Release / Gunter's Site
[62] Paz (Hisdesat) post in manifest thread / article in DW
[65] Inmarsat 6 F1 SpaceNews mention / Airbus contract / Gunter / Space Intel mention
[68] Telkom 4 links Gunter
[69] Viasat 3 : one of first two Viasat 3 birds in mid-2019 or early-2020.  Also third Viasat 3 if it gets built?
  ViaSatellite 2/10/16 SpaceNews 2/10/2016 Gunter
[70] Spaceflight Industries : Upcoming Spaceflight Ind. schedule
[99] SpaceX announcement

[xx] Europasat/HellasSat 3 moved to different launch vehicle
[xx] ABS-8 Satellite build cancelled
[xx] SHERPA cancelled from FORMOSAT-5 flight

Competitions for future payloads:
STP-3
Air Force First 6 EELV

L2 notes on manifest:
https://forum.nasaspaceflight.com/index.php?topic=42937.msg1679127#msg1679127
https://forum.nasaspaceflight.com/index.php?topic=42839.msg1683254#msg1683254

Last 10 Edits:
Jun 22  Moved Arabsat 6A before STP-2, both early/H1 2018
Jun 17  OTV-5 August 17.  Changed table format, now being maintained by gongora.
Jun 06  edit/gongora: Slipped Bulgariasat 2 days.  Added X-37B in August 2017
Jun 05  edit/gongora: Marked CRS-11 successful.  Removed speculative Mars mission dates.
Jun 02  edit/gongora: Removed Eutelsat Quantum
May 25  edit/gongora: Moved Iridium Flight 2 to June 25 (1325 PDT).  Moved Intelsat 35e to July 1.
May 24  edit/gongora: Moved Koreasat-5A to August (educated guess), CCiCap In-Flight Abort to 2018
         removed estimated launch month from FH Demo and STP-2
May 23  edit/gongora: Moved Eutelsat Quantum to 2019
May 21  edit/gongora: Added Telkom 4, June 2018
May 20  edit/gongora: Moved CCtCap DM-1 to March 2018
May 17  edit/gongora: Moved PSN-6 to 2018

All comments and updates are welcomed!  Thank you to all contributors!

Online ClayJar

  • Full Member
  • **
  • Posts: 298
  • Baton Rouge, LA, USA
  • Liked: 611
  • Likes Given: 59
Re: SpaceX Manifest Table Formatting Discussion
« Reply #12 on: 06/23/2017 01:09 PM »
Okay, looks like it didn't break the forums when I look at the post on Chrome on my desktop.  On my phone, in portrait, the table is cut off on the right (and you can't scroll horizontally).  In landscape, it is quite compressed (lots of line breaking within the columns), but it fits.  (Screenshots attached.)  Of course, in Chrome on my phone, if I hit the menu dots and "Request desktop site..." to get the "full" site instead of the "mobile" site, the [table] form renders as nicely as it does on my desktop.

I now leave the rest of you to discuss the merits of one or the other format, [table] or fixed-width text.  Unsurprisingly, I think I prefer the [table]-based format, but perhaps there are easy improvements to it, too.

Offline mme

  • Full Member
  • ****
  • Posts: 1018
  • Santa Barbara, CA, USA, Earth, Solar System, Milky Way Galaxy, Virgo Supercluster
  • Liked: 1232
  • Likes Given: 3075
Re: SpaceX Manifest Table Formatting Discussion
« Reply #13 on: 06/23/2017 08:37 PM »
...
I now leave the rest of you to discuss the merits of one or the other format, [table] or fixed-width text.  Unsurprisingly, I think I prefer the [table]-based format, but perhaps there are easy improvements to it, too.
I much prefer the use of the table. But not scrolling on the phone may be an issue for some (seems like an SMF bug.) For me it's worth it because it renders well at different zoom levels and window sizes. (I have old eyes that get tired at night.)
Space is not Highlander.  There can, and will, be more than one.

Offline Comga

  • Senior Member
  • *****
  • Posts: 3886
  • Liked: 1213
  • Likes Given: 1037
Re: SpaceX Manifest Table Formatting Discussion
« Reply #14 on: 06/24/2017 12:35 PM »
That works great on my phone
(I use the 'full' option)
But now Bulgariasat is on the wrong side of the line and in the wrong color. Keep up!  Keep up! 😉
What kind of wastrels would dump a perfectly good booster in the ocean after just one use?

Offline CraigLieb

  • Full Member
  • ****
  • Posts: 745
  • Dallas Fort Worth
  • Liked: 651
  • Likes Given: 718
Re: SpaceX Manifest Table Formatting Discussion
« Reply #15 on: 06/24/2017 06:01 PM »
Love seeing the table on my phone I use chrome and view full site.
Colonize Mars!

Offline mnelson

  • Member
  • Posts: 35
  • Salt Lake City, Utah
  • Liked: 52
  • Likes Given: 103
Re: SpaceX Manifest Table Formatting Discussion
« Reply #16 on: 06/24/2017 06:30 PM »
I'm not sure how to say this as respectfully as possible: bleck! It is now much less readable for me. On my laptop (Chrome on a MacBook) I have plenty of screen width and it only uses a very little of the space. The font is very small and blocky. When I enlarge the page the font is large and blocky.

I very much appreciate all the great work on maintaining this list. I'm trying to provide feedback on the new format. Please, please, don't take this as a lack of gratitude for the diligent and consistent effort!

Offline beancounter

  • Full Member
  • ****
  • Posts: 1251
  • Perth, Western Australia
  • Liked: 105
  • Likes Given: 162
Re: SpaceX Manifest Table Formatting Discussion
« Reply #17 on: 06/25/2017 01:02 PM »
I'm not sure how to say this as respectfully as possible: bleck! It is now much less readable for me. On my laptop (Chrome on a MacBook) I have plenty of screen width and it only uses a very little of the space. The font is very small and blocky. When I enlarge the page the font is large and blocky.

I very much appreciate all the great work on maintaining this list. I'm trying to provide feedback on the new format. Please, please, don't take this as a lack of gratitude for the diligent and consistent effort!

Fine on an iPad or iPad mini.
Beancounter from DownUnder

Offline Star One

  • Senior Member
  • *****
  • Posts: 7995
  • UK
  • Liked: 1278
  • Likes Given: 168
Re: SpaceX Manifest Table Formatting Discussion
« Reply #18 on: 06/25/2017 10:11 PM »
I can tell you one thing it looks terrible on Tapatalk on my iPhone 6S+. The text looks far too big and even somewhat hard to look at when colours are used.
« Last Edit: 06/25/2017 10:13 PM by Star One »

Offline yokem55

  • Full Member
  • ****
  • Posts: 432
  • Oregon (Ore-uh-gun dammit)
  • Liked: 234
  • Likes Given: 12
Re: SpaceX Manifest Table Formatting Discussion
« Reply #19 on: 06/25/2017 10:24 PM »
I can tell you one thing it looks terrible on Tapatalk on my iPhone 6S+. The text looks far too big and even somewhat hard to look at when colours are used.
The manifest has never worked in Tapatalk. Previously I had to load up the non mobile web view to make sense of it. Now the mobile view just works.

Tags: