NASASpaceFlight.com Forum
SpaceX Vehicles and Missions => SpaceX Falcon Missions Section => Topic started by: gongora on 09/08/2020 11:12 pm
-
Discussion thread for SpaceX's Transporter-2, the June 2021 dedicated rideshare flight to SSO.
NSF Threads for SpaceX Transporter-2 : Discussion (https://forum.nasaspaceflight.com/index.php?topic=51898.0)
Discussion thread for SpaceX Rideshare Program (https://forum.nasaspaceflight.com/index.php?topic=48741.0)
Successful launch June 30, 2021 at 3:31pm EDT (19:31 UTC) on Falcon 9 B1060-8 from SLC-40 to ~525km SSO. Sucessful RTLS booster return to LZ-1. HOS Briarwood dispatched to collect fairing halves from water.
Falcon 9’s first stage booster previously supported launch of GPS III Space Vehicle 03, Turksat 5A, and five Starlink missions. Following stage separation, SpaceX will land Falcon 9’s first stage on Landing Zone 1 (LZ-1) at Cape Canaveral Space Force Station. One half of Falcon 9’s fairing previously supported Transporter-1 and a Starlink mission, and the other previously flew on SAOCOM 1B and a Starlink mission.
On board this launch are 85 commercial and government spacecraft (including CubeSats, microsats, and orbital transfer vehicles) and 3 Starlink satellites. While there are fewer spacecraft on board compared to Transporter-1, this mission is actually launching more mass to orbit for SpaceX’s customers.
Payloads:
Spaceflight Inc. (https://forum.nasaspaceflight.com/index.php?topic=51898.msg2189821#msg2189821) SXRS-5 (https://spaceflight.com/mission-sxrs-5/) (36 sats plus two separating deployers)
Sherpa-FX2 (295kg, 128kg after deploying customers)
Astrocast (x5) (3U cubesat, prop)
Spire LEMUR (x3) (3U cubesat, no prop)
CISESE PAINANI-II (cubesat, no prop)
Hawkeye 360 Hawk (x3) (microsatellite, prop)
Lynk Lynk-06 (https://apps.fcc.gov/oetcf/els/reports/ViewExhibitReport.cfm?id_file_num=0088-EX-CN-2021&application_seq=105182) "Shannon" (microsatellite, no prop)
Swarm SpaceBEE (x12) (.25U cubesat, four have prop)
(hosted payload) TagSat-2 (NearSpace Launch)
(hosted payload) SOARS (KeplarianTech, Tiger Innovations)
(hosted payload) NFB-4 (Stellar Exploration)
Sherpa-LTE1 (335kg, 203kg after deploying customers) SXRS-5
AstroDigital Shasta (Orbital Sidekick Aurora) (https://forum.nasaspaceflight.com/index.php?topic=51898.msg2208545#msg2208545) (microsatellite, no prop, 22.5kg)
Kleos KSM-2 (x4) (6U cubesat, prop)
InSpace Faraday Phoenix (6U cubesat, no prop)
Spire LEMUR (x1) (3U cubesat, no prop)
OQTech Tiger-2 (AYAN-21) (6U cubesat, no prop)
Aerospacelab ARTHUR-1 (12U? cubesat, prop)
Orbit Fab Tenzing (microsatellite, 35kg, Astro Digital, prop)
Hawkeye 360 Hawk (x3) (microsatellite, prop)
U. of Toronto HERON MkII (cubesat, no prop)
Port 3
Loft Orbital YAM-2
Exolaunch Fingerspitzengefühl Mission (10 microsats, 19 cubesats, 4 24" ports)
(port assignments are guesses)
Port 1
ICEye
TUBIN (https://forum.nasaspaceflight.com/index.php?topic=51898.msg2250328#msg2250328) [~20kg microsat, TU Berlin)
Cubesat deployer (6U)
Swarm SpaceBEE (x16)
Port 2
Satellogic (x4)
Port 3
ICEye (x2)
Quadpack
D2/AtlaCom-1 (6U, built by NanoAvionics) (https://forum.nasaspaceflight.com/index.php?topic=51898.msg2209822#msg2209822)
Spire (x2)
Port 4
ICEye
Loft Orbital YAM-3 (https://fcc.report/IBFS/SAT-LOA-20200907-00105) (microsat, ~83kg)
D-Orbit ION SCV-003 "Wild Ride": 7 6 satellites, 1 separating deployer, 3 hosted payloads
Cubesats
Neptuno (Deimos) - from Vigoride-2
Spartan (Endurosat) - from Vigoride-2
QMR-KWT (Orbital Space) - from Vigoride-2
ISILaunch35 (3 cubesats in one quadpack)
W-Cube (3U, Reaktor Space, Finland)
Ghalib (2U, Marshall Intech)
NAPA 2 / RTAF-SAT 2 (6U Royal Thai Air Force)
Hosted payloads:
LaserCube
Nebula
Worldfloods
SpaceX Starlink (3x, ~260kg)
Maverick dual-plate adapter
Mandrake 2A/2B (2 microsats by Astro Digital for DARPA/SDA/AFRL)
Maverick Space deploys two payloads from the aft end of Stage 2.
NASA PACE-1
NASA TROPICS Pathfinder
port unknown:
Centauri 4/Tyvak-0211 (6U?, Fleet)
EG-3 (https://forum.nasaspaceflight.com/index.php?topic=51898.msg2219028#msg2219028)/Tyvak-0173 (Echostar Global, 6U?)
LINCS A/B (2x 12U from GA-EMS for SDA)
PlanetIQ GNOMES-2 (30kg? microsat)
Capella 5 (microsat ~100kg)
Umbra-2001 (microsat 65kg)
Removed:
SAI-2 (https://forum.nasaspaceflight.com/index.php?topic=51898.msg2200556#msg2200556) (6U)
Nanoracks
Outpost tech demo
Momentus
Vigoride-1 (https://forum.nasaspaceflight.com/index.php?topic=51898.msg2190832#msg2190832) (161kg wet, 155kg dry)
AURORASAT (1.5U Cubesat, 2kg) (Aurora Propulsion Technologies, Finland)
LABSAT (3U Cubesat, 4kg) (SatRevolution, Poland)
STEAMSAT (1.5U Cubesat, 1.8kg) (Steamjet Space Systems, UK)
SWIFTVISION (3U Cubesat, 4kg) (SatRevolution, Poland)
VZLUSAT-2 (3U Cubesat, 4.4kg) (SpaceManic CZ, Czech Republic)
Plaza Deck (Vigoride-1 port)
ISILaunch Quadpack
NUTSAT-0 (2U Cubesat) (Gran Systems Co., Taiwan)
Alba PocketQube deployer (x3, 18P total capacity)
DelfiPQ (3P)
Grizu-263a (1p)
TRSI-2 (1P)
Hades & EASat-2 (2x 1.5P)
SATTLA-2 (2P)
Unicorn 1 (2P)
Unicorn 2A & 2D (2x 3P)
Vigoride-2 (http://licensing.fcc.gov/cgi-bin/ws.exe/prod/ib/forms/reports/swr031b.hts?q_set=V_SITE_ANTENNA_FREQ.file_numberC/File+Number/%3D/SATSTA2020083100102&prepare=&column=V_SITE_ANTENNA_FREQ.file_numberC/File+Number) (481kg wet, 361kg dry)
ISIS Quadpack #1
Broncosat-1 (1.5U, Bronco Space, US, no prop)
Guardian-Alpha (3U, Orbital Astronautics, UK, prop)
Oresat0 (1U, Portland State Aerospace Society, US, no prop)
Gossamer (1U, LunaSonde, UK, no prop)
FEES-2 (0.3U, GP Advanced Projects, Italy, no prop)
Iris-A (2U, Odysseus, Taiwan)
ISIS Quadpack #2
Kepler-16,-17 (2x 6U, Kepler, Canada)
ISIS Quadpack #3
Steamsat-2 (3U, SteamJet, Poland)
ISIS Quadpack #4
Stork-1,-2,-3 (3x 3U, SatRevolution, Poland)
Neptuno (3U, Deimos Engineering, Spain, prop)
Dodona (3U, Lockheed Martin, US, no prop, 550km)
QMR-QWT (1U, Solar Space, Bulgaria, no prop)
Revela (1U, ARCA Dynamics, Italy, no prop, 550km)
Bhaarathiya-Sat (SpaceKidz India, India, no prop)
SPARTAN (6U, EnduroSat, Bulgaria, )
3U deployer from Planetary Systems Corp., USA New Production Concept, Italy
TROPICS Pathfinder (3U, NASA)
Fossa (2x 8P PocketQube deployer)
Challenger (3P) (Mini-Cubes, US)
SanoSat-1 (1P) (ORIONSpace, Nepal)
TRSI3 (1P)
CSHARKPILOT-1(FOSSASAT-2E) (2P) (CShark, Italy)
LAIKA(FOSSASAT-2B) (2P) (porkchop, Sweden)
Canary Hatchling (1P) (Care Weather, US)
FOSSASAT-2C,2D,2F (3x 2P)
Mass simulator for removed Fossa PocketQube deployer
Other SpaceX resources on NASASpaceflight:
SpaceX News Articles (Recent) (http://www.nasaspaceflight.com/tag/spacex/) / SpaceX News Articles from 2006 (Including numerous exclusive Elon interviews) (http://forum.nasaspaceflight.com/index.php?topic=21862.0)
SpaceX Dragon Articles (http://www.nasaspaceflight.com/tag/dragon/) / SpaceX Missions Section (with Launch Manifest and info on past and future missions) (https://forum.nasaspaceflight.com/index.php?board=55.0)
L2 SpaceX Section (https://forum.nasaspaceflight.com/index.php?board=60.0)
-
Loft Orbital YAM-3
https://fcc.report/IBFS/SAT-LOA-20200907-00105
-
I thought YAM-3 was launching in December 2020: https://spacenews.com/exolaunch-loft-orbital-contract/
-
Other announced payloads on this launch include
-Sen EarthTV (https://spacenews.com/exolaunch-loft-orbital-contract/) (with Momentus)
-Polar Vigilance (https://smallcaps.com.au/spacex-falcon-9-rocket-launch-kleos-space-satellite-cluster-orbit/) (with Spaceflight)
-
I thought YAM-3 was launching in December 2020: https://spacenews.com/exolaunch-loft-orbital-contract/
I guess it was delayed
-
[Space News] Exolaunch signs pact with SpaceX and scouts U.S. location (https://spacenews.com/exolaunch/)
Under the agreement announced Oct. 8, Germany’s Exolaunch plans to integrate 30 U.S. and European cubesats and microsatellites on Falcon 9 rideshare flights to sun-synchronous orbit scheduled to launch in December. Exolaunch plans to integrate roughly the same number of satellites on a SpaceX rideshare flight in mid-2021.
-
0022-EX-ST-2021
Nanoracks has refiled their FCC experimental permit request for the Mars Outpost Demonstration (cutting a piece of metal in orbit) for the June flight. Their application says it's from Vandenberg, but others have said Florida, so who knows. Florida is probably more likely.
https://apps.fcc.gov/oetcf/els/reports/ViewExhibitReport.cfm?id_file_num=0022-EX-ST-2021&application_seq=104757
-
https://www.businesswire.com/news/home/20210119005117/en/Satellogic-and-SpaceX-Announce-Multiple-Launch-Agreement
Satellogic and SpaceX Announce Multiple Launch Agreement
First mission, scheduled for mid-2021, will further expand Satellogic’s industry-leading in-orbit capacity
January 19, 2021 08:00 AM Eastern Standard Time
MONTEVIDEO, Uruguay--(BUSINESS WIRE)--Satellogic, the first company to develop a scalable Earth observation platform with the ability to remap the entire planet at both high-frequency and high-resolution, today announced a Multiple Launch Services Agreement (MLA) with SpaceX. Through the agreement, SpaceX becomes Satellogic’s preferred vendor for rideshare missions. The first launch, scheduled for June 2021, will deliver Satellogic satellites to Low Earth Orbit on a Falcon 9 rocket.
...
https://twitter.com/pbdes/status/1351514779811278859
Geospatial analytics provider @Satellogic selects @SpaceX for multiple ride-share LEO missions, starting w/ 4 sats in June. Deal covers SSO & mid-inclination orbits carrying @SpaceXStarlink sats. Like SpaceX, Satellogic is vertically integrated. Wants >300 sats by 2025.
-
From Reddit: (https://www.reddit.com/r/spacex/comments/l210i3/rspacex_transporter1_official_launch_discussion/gkd79qh/?context=3)
u/Straumli_Blight
ExoLaunch are manifested on several Falcon 9 rideshares, will they launch on SpaceX's June 2021 Smallsat mission?
u/exo_connor
We'll be there, and with more ports and payload mass than this mission!
-
0130-EX-CN-2021
Mini-Cubes, LLC overall goal for the Challenger mission, is to develop a space based method to
distribute secure system keys (SSH keys) for Internet of Things devices.
The satellite will be launched as a secondary payload carried by the Momentus Vigoride vehicle
aboard SpaceX Falcon 9, from Vandenburg AFB, currently scheduled for June 2021. It will be
deployed from the Momentus Vigoride into a Sun-synchronous orbit with a roughly circular orbit,
altitude between 450km and 550 km. Orbital inclination from the equator is about 97 degrees.
Transmission will begin upon deploy into orbit, and cease 2 years later. Atmospheric friction will
slow the satellite and reduce the altitude of the orbit, until de-orbiting occurs much less than 25
years after launch. See the Orbital Debris Assessment Report for details.
The spacecraft is a 3p pocketqube with deployable elements. Measurements after deployment of
the solar panels and antennas are 19.2 cm X 14.5 cm X 24.4 cm. The total mass is about 0.75 Kg.
-
Spaceflight Inc. submitted FCC paperwork for this flight. They have two Sherpas, Sherpa-FX2 and Sherpa-LTE1. Both will deploy their customer payloads shortly after separating from the second stage. LTE-1 will then test the new attitude control, UHF communications, power, and electric propulsion systems over the next several months while lowering its orbit to 350km.
SAT-STA-20210205-00017 (https://licensing.fcc.gov/cgi-bin/ws.exe/prod/ib/forms/reports/swr031b.hts?q_set=V_SITE_ANTENNA_FREQ.file_numberC/File+Number/%3D/SATSTA2021020500017&prepare=&column=V_SITE_ANTENNA_FREQ.file_numberC/File+Number)
Sherpa-FX2
Astrocast (x5) (cubesat, prop)
Spire LEMUR (x4) (cubesat, no prop)
Hawkeye 360 Hawk (x3) (microsatellite, prop)
Lynk Lynk-06 (microsatellite, no prop)
Swarm SpaceBEE (x12) (.25U cubesat, four have prop)
(hosted payload) SOARS (KeplarianTech, Tiger Innovations)
(hosted payload) TagSat-2 (NearSpace Launch)
(hosted payload) NFB-4 (Stellar Exploration)
Sherpa-LTE1
AstroDigital Shasta (microsatellite, no prop)
Kleos KSM-2 (x5) (cubesat, prop)
InSpace Faraday Phoenix (cubesat, no prop)
OQTech Tiger-2 (cubesat, no prop)
U. of Toronto HERON MkII (cubesat, no prop)
CISESE PAINANI-II (cubesat, no prop)
Aerospacelab ARTHUR-1 (cubesat, prop)
Hawkeye 360 Hawk (x3) (microsatellite, prop)
Backup payload: Orbit Fab Tenzing (microsatellite)
-
Is there a change in the Vigoride mission and what number it will be? What's the next opportunity for a Momentus Vigoride rideshare? I understand that it Vigoride-1 wasn't able to fly on Transporter-1.
-
Is there a change in the Vigoride mission and what number it will be? What's the next opportunity for a Momentus Vigoride rideshare? I understand that it Vigoride-1 wasn't able to fly on Transporter-1.
Vigoride-1 is the first mission. They will continue in order once the issues with the government have been resolved.
-
Is there a change in the Vigoride mission and what number it will be? What's the next opportunity for a Momentus Vigoride rideshare? I understand that it Vigoride-1 wasn't able to fly on Transporter-1.
It's not really clear to me yet if the Vigoride from Transporter-1 is going to be on this flight. There was another rideshare before June (we don't know the primary payload) that was going to be the second Vigoride flight, so the first Vigoride could be on that one instead (if that mission is still happening).
edit: I'm guessing Transporter 2 will be the next SSO launch, and therefore would probably have Vigoride-1. I'm just not 100% certain of that yet. I'm also not sure if having Vigoride-1 on this flight would preclude also having Vigoride-2 on this flight.
-
Is there a change in the Vigoride mission and what number it will be? What's the next opportunity for a Momentus Vigoride rideshare? I understand that it Vigoride-1 wasn't able to fly on Transporter-1.
It's not really clear to me yet if the Vigoride from Transporter-1 is going to be on this flight. There was another rideshare before June (we don't know the primary payload) that was going to be the second Vigoride flight, so the first Vigoride could be on that one instead (if that mission is still happening).
edit: I'm guessing Transporter 2 will be the next SSO launch, and therefore would probably have Vigoride-1. I'm just not 100% certain of that yet. I'm also not sure if having Vigoride-1 on this flight would preclude also having Vigoride-2 on this flight.
NUTSAT was supposed to launch on Transporter-1 but has since been reported to launch on Transporter-2 instead. So I suspect most, if not all, of the Transporter-1 payloads were moved to Transporter-2.
https://taronews.tw/2021/01/22/717656/
-
These are satellites on Scr00chy's page that had been manifested for Vigoride-1:
- Alba Cluster 3 (https://www.albaorbital.com/launch) (9 pocketqubes)
- AuroraSat 1 (https://spacenews.com/aurora-momentus-plasma-brake/)
- Challenger (https://www.tesmanian.com/blogs/tesmanian-blog/falcon-9-vigoride) (pocketqube)
- LabSat (https://spacenews.com/momentus-three-contracts/)
- NutSat (https://momentus.space/2020/10/26/momentus-and-gran-systems-announce-service-agreement-for-nutsat/)
- OrbAstro (https://momentus.space/2020/06/04/orbastro/)
- Quadpack (https://forum.nasaspaceflight.com/index.php?topic=8184.msg2175621#msg2175621)
- SteamSat (https://steamjet.space/steamjet-is-looking-for-commercial-partners-for-their-next-in-orbit-demonstrations/)
- SW1FT/SEZ (https://forum.nasaspaceflight.com/index.php?topic=8184.msg2175621#msg2175621)
- VZLUSat-2 (https://www.vzlusat2.cz/2021/01/08/vzlusat-2-start-postponed-again/)
At least the Alba Cluster, Challenger, Nut Sat and SteamSat have been confirmed for Transporter-2; VZLUSat-2 also was expected to shift to Transporter-2.
There were eight more pocketqubes co-manifested with Challenger (source (https://fossa.systems/2020/09/02/fossa-systems-and-momentus-announce-launch-of-nine-pocketqube-satellites/)):
- Canary Hatchling
- CSharkPilot-1 (FossaSat-2E)
- FossaSat-2C, -2D, -2F
- Laika (FossSat-2B)
- SanoSat-1
- TRSI3
So far these are 26 satellites. 23 satellites were integrated on Vigoride for the launch in January 2021 (source (https://momentus.space/2020/12/23/narsai-announcing-complete-integration-of-all-customer-satellites-2/)). Assuming that they counted Alba Cluster 3 as 9 sats (and not as 3 PQ deployers (http://www.albaorbital.com/integration)), this would mean that not all of those 26 were actually included for Transporter-1.
-
Also, the Fossa pocketqubes were originally supposed to launch with Momentus in February (presumably with SARah 1) but since at least one of these is now manifested for Transporter-2, other Momentus payloads from that February launch could have been moved to Transporter-2. These include:
NuX-1
SPARTAN
QMR-KWT
Dodona
REVELA
Gossamer
BroncoSat-1
FEES-2
ORESAT0
BHAARATHIYA-SAT
Neptuno
SMPOD-03
And finally, some payloads were scheduled to launch on Transporter-1 but didn't make it in the end. So some of those could have been moved to Transporter-2 also:
GNOMES-2
CPOD A+B
LINCS A+B
ADELIS-SAMSON (3 sats)
Landmapper-Demo6+Demo7
Umbra-2001
-
Momentus refiled the FCC paperwork for Vigoride-1, on this flight.
SAT-STA-20210210-00020 (https://licensing.fcc.gov/cgi-bin/ws.exe/prod/ib/forms/reports/swr031b.hts?q_set=V_SITE_ANTENNA_FREQ.file_numberC/File+Number/%3D/SATSTA2021021000020&prepare=&column=V_SITE_ANTENNA_FREQ.file_numberC/File+Number)
Vigoride-1 (161kg wet, 155kg dry)
AURORASAT (1.5U Cubesat, 2kg) (Aurora Poprulsion Technologies, Finland)
LABSAT (3U Cubesat, 4kg) (SatRevolution, Poland)
STEAMSAT (1.5U Cubesat, 1.8kg) (Steamjet Space Systems, UK)
SWIFTVISION (3U Cubesat, 4kg) (SatRevolution, Poland)
VZLUSAT-2 (3U Cubesat, 4.4kg) (SpaceManic CZ, Czech Republic)
Plaza Deck
NUTSAT-0 (2U Cubesat) (Gran Systems Co., Taiwan)
ISILaunch Quadpack
Alba PocketQube deployer (x3, 18P total capacity)
Challenger (3P)
-
https://twitter.com/Lork89/status/1359540520951898123
Not sure I will ever got used to the feeling of having years of life riding on top of a rocket. Thanks for the passage! #ION #SCV002 #transporter1 @SpaceX @elonmusk See you in June! @D_Orbit #pulse #feelthepulse
-
Update: Space Development Agency director Derek Tournear says the damaged satellites that were supposed to fly on SpaceX rideshare Transporter-1 will be repaired and will launch in the next rideshare Transporter-2 https://spacenews.com/darpa-satellites-damaged-at-processing-facility-ahead-of-spacex-launch/
https://twitter.com/Sandra_I_Erwin/status/1359931198223642627
-
[Space News] DoD space agency launching experiments in preparation for 2022 satellite deployments (https://spacenews.com/dod-space-agency-launching-experiments-in-preparation-for-2022-satellite-deployments/)
One of those experiments is Mandrake 2 — a pair of small spacecraft equipped with optical crosslinks that was scheduled to launch Jan. 24 on SpaceX’s massive rideshare Transporter-1. The satellites were accidentally damaged during payload processing and didn’t make the launch. They are now being repaired and will fly to orbit this summer on SpaceX’s next rideshare mission Transporter-2, said Derek Tournear, director of the Defense Department’s Space Development Agency
....
Also expected to ride to space on Transporter-2 is an SDA optical crosslink demonstration with two satellites made by General Atomics, Tournear said.
There is a picture of the Mandrake sats in the article.
-
The 9 Alba PocketQubes are:
DelfiPQ
Grizu-263a
TRSI-2
Hades
EASat-2
SATTLA-2
Unicorn 1, 2A, & 2D
According to https://www.albaorbital.com/integration
-
The 9 Alba PocketQubes are:
DelfiPQ
Grizu-263a
TRSI-2
Hades
EASat-2
SATTLA-2
Unicorn 1, 2A, & 2D
According to https://www.albaorbital.com/integration
Let the fun begin. Those listed sats would fill three of Alba Orbital's 6P PocketQube deployers. They don't include Challenger, the paperwork for which mentioned being on the Momentus port for this launch. The Momentus ODAR for Vigoride-1 says there are no PocketQubes on the Vigoride and there are three PocketQube deployers on the Plaza Deck.
edit: If Vigoride-2 is also on this flight then it would solve the problem.
-
The 9 Alba PocketQubes are:
DelfiPQ
Grizu-263a
TRSI-2
Hades
EASat-2
SATTLA-2
Unicorn 1, 2A, & 2D
According to https://www.albaorbital.com/integration
Let the fun begin. Those listed sats would fill three PocketQube deployers. They don't include Challenger, the paperwork for which mentioned being on the Momentus port for this launch. The Momentus ODAR says there are no PocketQubes on the Vigoride and there are three PocketQube deployers on the Plaza Deck.
Challenger is one of the FOSSA deployed PocketQube, not an Alba deployed one. https://fossa.systems/2020/09/02/fossa-systems-and-momentus-announce-launch-of-nine-pocketqube-satellites/
edit: If Vigoride-2 is also on this flight then it would solve the problem.
Yeah, the Alba ones are part of Momentus 1 and FOSSA was AFAIK Momentus 2.
-
and so it is...
Momentus Inc. (“Momentus”) submits an updated orbital debris assessment report (“ODAR”) and ownership exhibit. In relevant part, the ODAR reflects changes in:
• VR-2’s scheduled launch date from February 2021 to June 2021;
VR-2 includes a primary and a secondary structural assembly with: Propellant Tanks, MET, Reaction Control System thrusters, Solar Array Assemblies, a launch vehicle separation ring, two ISIS 12U cubesat deployers, three 12U cubesat deployer mass dummies, one 3U cubesat deployer, and two PocketPod deployers.
-
The 9 Alba PocketQubes are:
DelfiPQ
Grizu-263a
TRSI-2
Hades
EASat-2
SATTLA-2
Unicorn 1, 2A, & 2D
According to https://www.albaorbital.com/integration (https://www.albaorbital.com/integration)
Let the fun begin. Those listed sats would fill three of Alba Orbital's 6P PocketQube deployers. They don't include Challenger, the paperwork for which mentioned being on the Momentus port for this launch. The Momentus ODAR for Vigoride-1 says there are no PocketQubes on the Vigoride and there are three PocketQube deployers on the Plaza Deck.
edit: If Vigoride-2 is also on this flight then it would solve the problem.
all i have found so far is Vigoride-2 hasn't slipped to the right though to throw a spanner in the works the Vigoride supposedly flying on CAS-500-1 launch hasnt been numbered yet so may have decided to distinguish launch providers.
-
I'm not so sure about this launching from Vandenberg.
With Transporter-1, I remember there was some documentation mentioning Vandenberg also, but then it launched from SLC-40. I think it's the same here. For example, the Momentus PDF above says:
Expected Launch Site: Cape Canaveral Space Launch Complex (SLC-40 or SLCE-4E).
I suspect VAFB might be more of a backup launch site for the Transporter missions.
-
Vigoride-2 (http://licensing.fcc.gov/cgi-bin/ws.exe/prod/ib/forms/reports/swr031b.hts?q_set=V_SITE_ANTENNA_FREQ.file_numberC/File+Number/%3D/SATSTA2020083100102&prepare=&column=V_SITE_ANTENNA_FREQ.file_numberC/File+Number)
Two ISIS 12U quadpack deployers used for 10 Momentus payloads
-
3U deployer from New Production Concept, Italy
?
Fossa (2x 8P PocketQube deployers)
CSHARKPILOT-1(FOSSASAT-2E) (2P) (CShark, Italy)
LAIKA(FOSSASAT-2B) (2P) (porkchop, Sweden)
Challenger (3P) (Mini-Cubes, US)
SanoSat-1 (1P) (ORIONSpace, Nepal)
TRSI3 (1P)
Canary Hatchling (1P) (Care Weather, US)
FOSSASAT-2C,2D,2F (3x 2P)
As they have re-manifested VR-2 to Transporter-2 (see post #24), this would also include from page 3-4 of https://licensing.fcc.gov/myibfs/download.do?attachment_key=2692615:
Broncosat-1 (1,5U, Bronco Space)
Dodona (3U, Lockheed Martin)
Guardian-Alpha (3U, Orbital Astronautics)
Neptuno (3U, Deimos)
Oresat 0 (1U, Portland State Aerospace Society)
QMR-QWT (1U, Solar Space)
Gossamer (1U, LunaSonde)
Revela (1U, ARCA Dynamics)
FEES-2 (0.5U, GP Advanced Projects)
Bhaarathiya-Sat (SpaceKidz India)
Exolaunch (~30 sats)
...
Loft Orbital YAM-3 satellite
YAM-3 is with Exolaunch (https://fcc.report/IBFS/SAT-LOA-20200907-00105/2702543)
Satellogic (x4)
"at least four" (Spacenews (https://spacenews.com/satellogic-signs-multi-launch-contract-with-spacex/))
Assuming 20 sats on ION, I now count a minimum of 135 manifested satellites on this launch (including 2 Sherpa, 2 Vigoride, 1 ION), with a good chance to break the Transporter-1 record of 143.
-
One of the VR-2 payloads mentioned in the previous post:
Kuwait’s first nanosatellite – QMR-KWT – is currently undergoing functional tests in Sofia, Bulgaria, overseen by mission contractor Dubai-based Orbital Space, ahead of the nanosatellite’s scheduled launch later this year.
...
The 1U CubeSat is due to launch into space from the United States as part of a second Momentus Vigoride demo mission payload aboard a SpaceX Falcon 9 rocket in June 2021.
https://arabspacenews.com/qmr-kwt-nanosatellite/ - 7 February 2021
-
The Orbit Fab Tenzing sat listed as a backup payload for the Spaceflight Inc. Sherpas. First demo of an on-orbit refueling station in SSO, holding some green propellant. Satellite built by Astro Digital, will also demo Accion Systems TILE thrusters, and there is a satellite observation/inspection vision system hosted payload from SCOUT. I guess this could end up on the December flight if they don't find room for it in June.
https://spacenews.com/orbit-fab-to-launch-with-spaceflight/
http://spaceref.com/news/viewpr.html?pid=56799
https://www.orbitfab.space/products
-
ICEYE US applied for a license to launch six satellites, with the first scheduled to ride on this flight.
SAT-LOA-20210212-00021 (https://licensing.fcc.gov/cgi-bin/ws.exe/prod/ib/forms/reports/swr031b.hts?q_set=V_SITE_ANTENNA_FREQ.file_numberC/File+Number/%3D/SATLOA2021021200021&prepare=&column=V_SITE_ANTENNA_FREQ.file_numberC/File+Number)
This application mentions a Florida launch. Most earlier indications were Vandenberg. We'll see where it ends up.
-
June is not far away at all. Shouldn't they be firming up the date and location very soon?
-
[ISISPACE] Kleos completes key satellite development milestone for mid-year SpaceX launch (https://www.isispace.nl/news/kleos-completes-key-satellite-development-milestone-for-mid-year-spacex-launch/)
Andreia March 2, 2021
Polar Vigilance Mission (KSF1) satellites have passed a hardware critical design review milestone with satellite builder ISISPACE
Satellites now enter Assembly Phase with ISISPACE for a mid-2021 launch onboard a SpaceX Falcon 9 vehicle
Kleos’ Scouting Mission satellites (KSM1) in commission and test phase
Luxembourg – Kleos Space S.A. (ASX: KSS, Frankfurt: KS1,) a space-powered Radio Frequency Reconnaissance data-as-a-service (DaaS) company, confirms its second satellite cluster, the Polar Vigilance Mission (KSF1), has successfully completed a hardware critical design review milestone for a launch mid-year onboard a SpaceX Falcon 9. Conducted, in the Netherlands, by satellite developer ISISPACE, passing the milestone ensures that Kleos’ Polar Vigilance Mission satellites can enter the assembly and verification phase – an exciting stage leads to final integration, testing and delivery of the satellites for launch.
The KSF1 Polar Vigilance Mission satellites are scheduled for a mid-2021 launch onboard a SpaceX Falcon 9, under a rideshare contract with Spaceflight Inc. The satellites will be launched into a 500-600km Sun Synchronous Orbit, complementing Kleos’ Scouting Mission 37o orbit, which successfully launched in early November 2020 and is in the commission and test phase.
Kleos’ satellites will detect and geolocate radio frequency transmissions to provide global activity-based intelligence, enhancing the intelligence, surveillance and reconnaissance (ISR) capabilities of governments and commercial entities when tracking systems are defeated, imagery unclear or targets out of patrol range.
Kleos Space CEO Andy Bowyer said: “We are excited to be progressing our second satellite cluster with ISISPACE – a leader in the small satellite market. Entering the assembly and verification phase of the satellites is a crucial developmental milestone and ensures we are on schedule to launch in mid-2021. The KSF1 satellite cluster will complement our Scouting Mission satellites, improving the value of our geolocation maritime intelligence data.”
ISISPACE’s CEO Jeroen Rotteveel states: “We are pleased to design and build this second satellite cluster for Kleos, to be completed on a fast-track schedule made possible by building on our extensive nanosatellite expertise and heritage. Despite the challenging timeline given the current global situation, we are keen to enter this next crucial phase of satellite assembly and validation and bringing our design to reality.”
As a strategic partner, ISISPACE further supports Kleos with its knowledge and experience to provide review and inputs for Kleos’ future needs and capabilities.
Figure 1 – The 6U CubeSat Platform rendering.
-
Space AI SAI-2 6U cubesat
0173-EX-CN-2021
-
Space AI SAI-2 6U cubesat
0173-EX-CN-2021
Nice find! From the PDF:
The experimental SAI-2 mission are free flying mission and is schedule to flight by end of June 2021
-
In a "State of Vandenberg" address this flight was shown on their 2021 manifest.
-
https://redwirespace.com/2021/03/09/redwire-selected-as-solar-array-supplier-for-planetiq-constellation-spacecraft/
In June 2021, PlanetiQ launches their next GNSS Navigation and Occultation Measurement Satellite (GNOMES) on the Transporter 2 launch out of Cape Canaveral.
-
There's no doubt this was scheduled for Vandenberg. With the move of the only booster that was on the west coast, I'm not so sure that it is still scheduled for Vandenberg.
-
And finally, some payloads were scheduled to launch on Transporter-1 but didn't make it in the end. So some of those could have been moved to Transporter-2 also:
GNOMES-2
CPOD A+B
LINCS A+B
ADELIS-SAMSON (3 sats)
Landmapper-Demo6+Demo7
Umbra-2001
ADELIS_SAMSON moved to the March Soyuz launch.
-
You can remove U. of Toronto HERON MkII. They ran into some radio licensing issues and have told me their looking at a launch later in the year now.
Spaceflight Inc. submitted FCC paperwork for this flight. They have two Sherpas, Sherpa-FX2 and Sherpa-LTE1. Both will deploy their customer payloads shortly after separating from the second stage. LTE-1 will then test the new attitude control, UHF communications, power, and electric propulsion systems over the next several months while lowering its orbit to 350km.
SAT-STA-20210205-00017 (https://licensing.fcc.gov/cgi-bin/ws.exe/prod/ib/forms/reports/swr031b.hts?q_set=V_SITE_ANTENNA_FREQ.file_numberC/File+Number/%3D/SATSTA2021020500017&prepare=&column=V_SITE_ANTENNA_FREQ.file_numberC/File+Number)
Sherpa-FX2
Astrocast (x5) (cubesat, prop)
Spire LEMUR (x4) (cubesat, no prop)
Hawkeye 360 Hawk (x3) (microsatellite, prop)
Lynk Lynk-06 (microsatellite, no prop)
Swarm SpaceBEE (x12) (.25U cubesat, four have prop)
(hosted payload) SOARS (KeplarianTech, Tiger Innovations)
(hosted payload) TagSat-2 (NearSpace Launch)
(hosted payload) NFB-4 (Stellar Exploration)
Sherpa-LTE1
AstroDigital Shasta (microsatellite, no prop)
Kleos KSM-2 (x5) (cubesat, prop)
InSpace Faraday Phoenix (cubesat, no prop)
OQTech Tiger-2 (cubesat, no prop)
U. of Toronto HERON MkII (cubesat, no prop)
CISESE PAINANI-II (cubesat, no prop)
Aerospacelab ARTHUR-1 (cubesat, prop)
Hawkeye 360 Hawk (x3) (microsatellite, prop)
Backup payload: Orbit Fab Tenzing (microsatellite)
-
FCC filing for Astro Digital Demo8 (Tenzing, 35kg) and Demo9 (Shasta, 22kg) (on Spaceflight Sherpas)
SAT-MOD-20210319-00036 (https://licensing.fcc.gov/cgi-bin/ws.exe/prod/ib/forms/reports/swr031b.hts?q_set=V_SITE_ANTENNA_FREQ.file_numberC/File+Number/%3D/SATMOD2021031900036&prepare=&column=V_SITE_ANTENNA_FREQ.file_numberC/File+Number)
-
This one may be on Transporter 2? A launch the first week of July is mentioned, which is well within the Transporter 2 launch window.
[NanoAvionics Press Release] International consortium adds hyperspectral imaging and communication payloads to NanoAvionics’ rideshare mission named D-2/AtlaCom-1 (https://nanoavionics.com/news/international-consortium-adds-hyperspectral-imaging-and-communication-payloads-to-nanoavionics-rideshare-mission-named-d-2-atlacom-1/)
NanoAvionics, a leading nanosatellite bus manufacturer and mission integrator, has revealed the remaining three payloads of its ‘D-2/AtlaCom-1’ rideshare mission hosted on board its M6P 6U nanosatellite bus. The additional payloads, a camera for hyperspectral remote sensing, a new high-gain X-band antenna and an upgraded X-Band downlink transmitter, are all part of an international collaboration by an international consortium and its partners called “HyperActive”.
https://www.gob.mx/sct/prensa/lanzara-space-x-mision-satelital-internacional-d2-atlacom-1
[Google Translate] The Nanosatellite "D2 / AtlaCom-1" will be launched by Space X from the NASA facilities in Cape Canaveral, with which it is programmed by the company in charge of Elon Musk, that this international satellite mission will be in space the first week of July of this 2021.
-
This one may be on Transporter 2? A launch the first week of July is mentioned, which is well within the Transporter 2 launch window.
[NanoAvionics Press Release] International consortium adds hyperspectral imaging and communication payloads to NanoAvionics’ rideshare mission named D-2/AtlaCom-1 (https://nanoavionics.com/news/international-consortium-adds-hyperspectral-imaging-and-communication-payloads-to-nanoavionics-rideshare-mission-named-d-2-atlacom-1/)
NanoAvionics, a leading nanosatellite bus manufacturer and mission integrator, has revealed the remaining three payloads of its ‘D-2/AtlaCom-1’ rideshare mission hosted on board its M6P 6U nanosatellite bus. The additional payloads, a camera for hyperspectral remote sensing, a new high-gain X-band antenna and an upgraded X-Band downlink transmitter, are all part of an international collaboration by an international consortium and its partners called “HyperActive”.
https://www.gob.mx/sct/prensa/lanzara-space-x-mision-satelital-internacional-d2-atlacom-1
[Google Translate] The Nanosatellite "D2 / AtlaCom-1" will be launched by Space X from the NASA facilities in Cape Canaveral, with which it is programmed by the company in charge of Elon Musk, that this international satellite mission will be in space the first week of July of this 2021.
Transporter 2 is said to be from Vandenberg, not Cape Canaveral.
-
TUBIN is to launch in June on Falcon 9, probably on Transporter-2:
TUBIN
Erdbeobachtung im thermalen Infrarot (Bild) - earth observation in thermal infrared (optical)
23 kg
Falcon 9
06/2021
in Vorbereitung - in prepration
https://www.raumfahrttechnik.tu-berlin.de/tubsat/
This is the first time that TU Berlin launches as satellite from the U.S., likely through Exolaunch.
-
Momentus adjusted their payload list for Vigoride-2.
--Dodona (3U, Lockheed Martin, US, no prop, 550km)
--Revela (1U, ARCA Dynamics, Italy, no prop, 550km)
--Bhaarathiya-Sat (SpaceKidz India, India, no prop)
++SPARTAN (6U, EnduroSat, Bulgaria, )
++Stork-1,-2,-3 (3x 3U, SatRevolution, Poland)
++Steamsat-2 (3U, SteamJet, Poland)
++Iris-A (2U, Odysseus, Taiwan)
++TROPICS Pathfinder (3U, NASA)
++Kepler-16,-17 (2x 6U, Kepler, Canada)
All Vigoride-2 payloads except Kepler should be released in the insertion orbit. Kepler may be released at up to 550km. All Vigoride-1 payloads will be released in the insertion orbit.
-
For those not familiar with programming languages, "--" means the payload is removed and "++" means the payload is added.
-
https://spaceflightnow.com/launch-schedule/
SFN is reporting a delay to July.
-
SpaceX’s second dedicated small satellite rideshare mission, known as Transporter-2, was previously slated to launch in June from Vandenberg. Officials with payloads on that mission have said in recent weeks that SpaceX moved Transporter-2 launch to Cape Canaveral.
https://spaceflightnow.com/2021/04/06/spacex-to-ramp-up-vandenberg-launch-cadence-with-starlink-missions/
-
Astro Digital US, Inc. (“Astro Digital”) requests special temporary authority (“STA”) for 180 days to communicate with the Sherpa-LTE1 spacecraft (SAT-STA-20210205-00017), which is owned and controlled by Spaceflight Inc. (“Spaceflight”), commencing on the deployment of the spacecraft, which is presently scheduled to occur between June 24, 2021 and July 31, 2021
-
Next SpaceFlight is confirming NET July.
https://nextspaceflight.com/launches/details/2404
-
0295-EX-CN-2021
Introduction. Pursuant to 47 C.F.R. § 5.54(a)(1), EchoStar Global Australia Pty Ltd
(“EchoStar Global”), a wholly owned subsidiary of EchoStar Corporation, requests a two-year
conventional experimental license to operate a gateway earth station in Germantown, MD, for
feeder link communications with its Australian-licensed non-geostationary orbit (“NGSO”)
mobile satellite service (“MSS”) system (“EG System” or “System”). Grant of this application
will serve the public interest by facilitating testing and development of new MSS equipment and
technology that ultimately will be deployed to support mobile communications, public safety,
and other services worldwide.
Background. With its parent company’s extensive experience in the satellite industry,
EchoStar Global is in the process of designing, constructing, and launching a new NGSO MSS
system to provide narrowband data services, including machine-to-machine and Internet of
things communications, throughout the globe. Pursuant to Australian authorization and
International Telecommunication Union (“ITU”) filings for the SIRION-1 network, the EG
System is licensed to provide MSS on S-band frequencies at 2000-2020 MHz (uplink) and 2180-
2200 MHz (downlink). The System will consist of a constellation of approximately 28 satellites
in low Earth orbit, including EG-1, which was successfully launched in August 2020, and EG-3,
scheduled for launch June 2021. Additionally, EchoStar Global has acquired ownership of
Pathfinder II, launched in December 2018, for operations under the SIRION-1 ITU filings.
-
[Space News] Exolaunch entering orbital debris market with eco-friendly space tugs (https://spacenews.com/exolaunch-entering-orbital-debris-market-with-eco-friendly-space-tugs/)
Medvedeva said it is coordinating about 30 of the satellites slated for SpaceX’s next dedicated rideshare mission, Transporter-2, around June.
-
TUBIN is to launch in June on Falcon 9, probably on Transporter-2:
TUBIN
Erdbeobachtung im thermalen Infrarot (Bild) - earth observation in thermal infrared (optical)
23 kg
Falcon 9
06/2021
in Vorbereitung - in prepration
https://www.raumfahrttechnik.tu-berlin.de/tubsat/
Surprise: Launch month of TUBIN - on the above linked website - today was changed to May 2021. TUBIN is intended to launch to ~ 550 km SSO (source (https://link.springer.com/content/pdf/10.1007/s12567-019-00295-3.pdf)), so it rather will not go on a Starlink launch in May. This leaves two explanations:
- May 2021 is an error, it launches on Transporter-2
- There will be an SSO Falcon 9 launch in May. German TUBIN would nicely fit to German SARah ....
-
Well, the Starlink launches to 53° inclination are about to end (for a time being).
It is likely after that they are going to launch Starlinks to polar orbit.
Late May seems doable for the first polar launch of Starlinks.
-
Until the Starlink modification request is dealt with, we don't really know when/where the next set of Starlinks will be going. Spaceflight was listing 70 degree flights later in the year. There will still be 53.(2/8) degree flights, as well as the polar shells. It would be odd for a polar launch from the Cape to be happening in May and not hear anything about it yet. I don't think SpaceX is going to do a launch from Vandenberg in May. Also, didn't Gwynne say July for polar Starlinks?
I wouldn't assume anything about the TUBIN launch until there is more information. Could be a typo, could be when they send it off to the rideshare integrator.
-
Updated VR-2 list.
-
Updated VR-2 list.
So looks like a number of the FOSSA brokered PocketQubes have been removed.
-
Updated VR-2 list.
So looks like a number of the FOSSA brokered PocketQubes have been removed.
Some should be flying on VR-1.
-
-
"Currently, the propulsion system is on track for integration to Sherpa-LTE1. However, should unforeseen issues prevent it from making the mission, Spaceflight would install a mass model to simulate the mass properties of the propulsion system."
PAINANI-2 and a Lemur swapped places.
The SOARS and NFB-4 hosted payloads on FX2 seem to have gone away.
The number of sats from Kleos dropped from 5 to 4
There are no longer any Hawkeye 360 sats on LTE-1
Tenzing is now on LTE-1
(this also specifies the launch site as CCAFS)
-
STA application for Transporter-2
0677-EX-ST-2021 (https://apps.fcc.gov/oetcf/els/reports/STA_Print.cfm?mode=initial&application_seq=107323)
Operation Start Date: 06/17/2021
Operation End Date: 12/17/2021
This application uses information from previous grant 1705-EX-ST-2020. This STA is necessary to authorize launch vehicle communications for SpaceX Mission 1573 from Cape Canaveral FL at LC-40 CCAFS or LC-39A KSC, and the experimental recovery following the Falcon 9 launch. Includes sub-orbital first stage, and orbital second stage. Trajectory data will be provided directly to NTIA, USAF, and NASA. All downrange Earth stations are receive-only. All operations are pre-coordinated with the Launch Range. Launch licensing authority is FAA Office of Commercial Space Transportation
-
https://spaceflight.com/mission-sxrs-5/
MISSION: SXRS-5
By Hilary Meyerson
MAY 11, 2021
We are in the final preparations for our SXRS-5 mission, called Transporter-2 by SpaceX, and wanted to share our latest assets about the upcoming launch. You can read the press release and discover our customers’ missions, as well as check out the infographic, a video of the deployment scenario, and the mission patch below — all which showcase how unique this mission is.
As an overview, we’ll be launching 36 customer payloads, including six microsatellites, 29 cubesats and one hosted payload to Sun Synchronous orbit no earlier than June 2021. We’re especially excited about this mission as it will be the first time we will fly two different orbital transportation vehicles (OTVs) and it’s the launch of the industry’s first-ever electric propulsion vehicle, Sherpa-LTE1. You may recall an earlier mission, SXRS-3, flew in January of 2021 and was the debut of Spaceflight’s first next-gen OTV, Sherpa-FX1.
The video below is a quick overview of the highlights of this mission.
https://spaceflight.com/wp-content/uploads/2021/05/SXRS5_V4.mov.mp4
Sherpa-LTE1 features an electric propulsion system from Apollo Fusion. After all payloads are deployed for this mission, our team will test some maneuvers of the Sherpa-LTE1 in preparation for a future mission. Our sights are already looking ahead: Spaceflight’s Sherpa-LTC, which features chemical propulsion from Benchmark Space Systems, will fly on another SpaceX mission later this year.
Stay tuned for photos of our customer payload integration campaign from our facilities in Auburn WA, a deeper technical dive on the Sherpa-NG program, and details on how to watch this important mission.
-
https://www.businesswire.com/news/home/20210511005295/en/Spaceflight-Inc.-Readies-36-Customer-Spacecraft-and-Two-OTVs-for-Launch-on-SpaceX’s-Transporter-2-Mission
Spaceflight is managing the launch for 14 organizations’ spacecraft from seven countries, including:
Aerospacelab’s Arthur
Astrocast's IoT Nanosatellites
HawkEye 360 Inc.’s HawkEye Cluster 3
In-Space Missions Limited’s Faraday Phoenix
Kleos Space’s Polar Vigilance Mission cluster of four satellites
Loft Orbital’s YAM-2
Lynk Global Inc.’s Shannon
NearSpace Launch Inc.’s TagSat-2
OQ Technology’s TIGER-2 5G IoT
Orbit Fab’s Tanker-001 Tenzing
Orbital Sidekick Inc.’s Aurora
Spire Global’s LEMUR-2
Swarm Technologies’ SpaceBEES
An undisclosed spacecraft
“This mission represents a significant milestone for Spaceflight’s next-gen OTV program and doubles down on our commitment to offer the most solutions to meet our customer’s needs for reaching unique orbital destinations,” said Tony Frego, mission director for Spaceflight’s SXRS-5 mission. “We knew we needed to utilize two Sherpa OTVs to support the customer demand and saw a unique opportunity to fly Sherpa-LTE for the first time. After all customer deployments are complete, we’ll run a series of maneuver tests with the electric propulsion OTV, which will provide valuable insights before Sherpa-LTC, our chemical propulsion OTV, launches later this year.”
Spaceflight’s first next-gen OTV, Sherpa-FX1, debuted in January and successfully deployed 15 spacecraft from SpaceX’s Transporter-1 launch. The Transporter-2 mission will feature another Sherpa-FX (Sherpa-FX2), as well as debut Sherpa-LTE (Sherpa-LTE1), which features electric propulsion from Apollo Fusion. Spaceflight’s Sherpa-LTC, which features chemical propulsion from Benchmark Space Systems, will fly on another SpaceX mission later this year.
-
Stable Road, which is trying to close its merger with Momentus, says that the FAA yesterday denied the space company's license request to launch its Vigoride payload on a SpaceX mission in June https://www.sec.gov/Archives/edgar/data/0001781162/000121390021025530/ea140644-8k_stableroad.htm
https://twitter.com/thesheetztweetz/status/1392151454849380362
-
On May 10, 2021, Momentus received a letter from the U.S. Federal Aviation Administration (“FAA”) denying Momentus’ application for a payload review based on the FAA’s finding that its launch would jeopardize U.S. national security. According to the letter, during an interagency consultation, the FAA was informed that the launch of Momentus’ payload poses national security concerns associated with Momentus’ current corporate structure. The letter further states that the FAA understands that Momentus is undergoing a process that may resolve the national security concerns, and that the FAA can reconsider a payload application when that process has been completed. The payload review relates to Momentus’ planned mission in June 2021 on a SpaceX rocket. As a result, Parent expects that Momentus will not be able to fly its inaugural mission as planned on the June 2021 launch and will be required to remanifest Vigoride 1 and Vigoride 2 to a later launch.
-
https://twitter.com/EXOLAUNCH/status/1392217177290387461
The 10 cases contain 10 #CarboNIX shock-free separation systems for our customers’ #microsats, ready to be shipped to the launch site for our next Falcon 9 mission! Stay tuned!
-
https://spaceflight.com/mission-sxrs-5/
-
I wonder if Momentus dropping out will mean we'll see SpaceX adding polar Starlinks again.
-
I wonder if Momentus dropping out will mean we'll see SpaceX adding polar Starlinks again.
My opinion is most likely.
-
I wonder if any Momentus customers can switch this late.
https://twitter.com/EXOLAUNCH/status/1392442780908130311
Exolaunch offers last-minute launch opportunities to SSO on #Falcon9. Please get in touch for all information at: [email protected]
-
Mission Overview:Capella 6 will be launched in May 2021, on a 53deg orbit at analtitude between 550km and 600km. For the purpose of this document, the worst case alti-tude in terms of lifetime of 600 km will be used for C-6. Capella 5 will be launched in June2021, on a sun-synchronous orbit at an altitude between 500km and 550km. For the purposeof this document, the worst case altitude in terms of lifetime of 550 km will be used for C-5.
-
Spaceflight has a third port, which seems to contain YAM-2. Their count seems to be off by one to me, looks like it should be 7 microsats? Maybe they didn't add in YAM-2.
This post has a lot of info on the payloads. One of the previously known payloads isn't listed (PAINANI II).
https://spaceflight.com/whos-onboard-sxrs-5-spacex-transporter-2/
(The big flat satellite on top of the SHERPA in this render from the previous Spaceflight post should be Lynk-06 "Shannon")
-
Belated cross-post re: Transporter-2 launch scheduling:
There are still up-to-date sources saying June-July:
https://licensing.fcc.gov/myibfs/download.do?attachment_key=6764705.
We're assuming NET late June because of the other three scheduled Falcon 9 launches in June?
***
Belated cross-post re: RTLS of same:
STA application for Transporter-2
0677-EX-ST-2021 (https://apps.fcc.gov/oetcf/els/reports/STA_Print.cfm?mode=initial&application_seq=107323)
Operation Start Date: 06/17/2021
Operation End Date: 12/17/2021
This application uses information from previous grant 1705-EX-ST-2020. This STA is necessary to authorize launch vehicle communications for SpaceX Mission 1573 from Cape Canaveral FL at LC-40 CCAFS or LC-39A KSC, and the experimental recovery following the Falcon 9 launch. Includes sub-orbital first stage, and orbital second stage. Trajectory data will be provided directly to NTIA, USAF, and NASA. All downrange Earth stations are receive-only. All operations are pre-coordinated with the Launch Range. Launch licensing authority is FAA Office of Commercial Space Transportation.
Hmmm. Hopefully this gets amended to add some more information.
What kind of info would you like?
ASDS location
I’m thinking it might be RTLS.
North 28 29 11, West 80 32 51 is the location usually listed for LZ-1 RTLS and appears on this application.
Not only on RTLS applications, but sometimes is the only transmitter listed for RTLS.
-
On October 30, 2020, Spire had provided its immediate launch schedule through 2Q 2021. Due to contract commitments and scheduling issues, Spire has an additional two (2) satellites that will be launched in June 2021 and are currently scheduled to launch on the SpaceX Transporter-1 launch. Of the 6 satellites to be launched in June 2021, five (5) of the satellites will be U.S. licensed LEMUR satellites and one (1) of the satellites will be Luxembourg licensed MINAS satellite.
-
On October 30, 2020, Spire had provided its immediate launch schedule through 2Q 2021. Due to contract commitments and scheduling issues, Spire has an additional two (2) satellites that will be launched in June 2021 and are currently scheduled to launch on the SpaceX Transporter-1 launch. Of the 6 satellites to be launched in June 2021, five (5) of the satellites will be U.S. licensed LEMUR satellites and one (1) of the satellites will be Luxembourg licensed MINAS satellite.
Not true : Transporter-1 was in January and launched 8 LEMURs.
-
It's a typo, get over it.
-
In a presentation by satellite manufacturer Nanoavionics they said Transporter 2 is currently targeting late June.
-
SFN Launch Schedule, updated May 20, now lists Transporter-2 launching in late June, and still from SLC-40. "Moved up from July." (https://spaceflightnow.com/launch-schedule/)
-
STA application for Transporter-2
0677-EX-ST-2021 (https://apps.fcc.gov/oetcf/els/reports/STA_Print.cfm?mode=initial&application_seq=107323)
Operation Start Date: 06/17/2021
Operation End Date: 12/17/2021
This application uses information from previous grant 1705-EX-ST-2020. This STA is necessary to authorize launch vehicle communications for SpaceX Mission 1573 from Cape Canaveral FL at LC-40 CCAFS or LC-39A KSC, and the experimental recovery following the Falcon 9 launch. Includes sub-orbital first stage, and orbital second stage. Trajectory data will be provided directly to NTIA, USAF, and NASA. All downrange Earth stations are receive-only. All operations are pre-coordinated with the Launch Range. Launch licensing authority is FAA Office of Commercial Space Transportation
Granted
https://apps.fcc.gov/els/GetAtt.html?id=274361
-
https://twitter.com/SpaceflightInc/status/1397935887581855747
We've completed the integration of Apollo Fusion EP system onto #SherpaLTE1. Want to know more about this mission? #SXRS5 #Transporter2 https://bit.ly/3oxGfRp
-
Slightly more clarity re: Transporter-2 launch; my bold:
SFN, Five launches planned from Florida’s Space Coast in June (https://spaceflightnow.com/2021/05/28/five-launches-planned-from-floridas-space-coast-in-june/), May 28
Another SpaceX launch will close out the month, when a Falcon 9 rocket fires into orbit on a rideshare mission with numerous small satellites from U.S. and international customers. The mission, known as Transporter 2 and expected in the last week of June,...
Last 8 days of June = Sunday, June 23 through Sunday, June 30
-
Spaceflight got their FCC approval for the two SHERPAs today.
edit: Loft Orbital also got the license for YAM-3
edit: Astro Digital also got the license mod for Demo 8 and Demo 9 (Shasta and Tenzing)
-
Do we know pricing info for cubesat rides via nanoracks on the transporter missions? the website only says that they offer 1-3, 6, and 12 U and to contact for pricing.
-
Do we know pricing info for cubesat rides via nanoracks on the transporter missions? the website only says that they offer 1-3, 6, and 12 U and to contact for pricing.
Most companies don't post their pricing. Spaceflight does post some pricing but have an asterisk below saying it can vary by orbit and launch provider. https://spaceflight.com/pricing/
There are quite a few launch integrators now so I would guess the prices would be similar between them. It may depend a lot on how much hand-holding the payload provider needs, whether they need help with government paperwork, transportation, testing, etc.
-
https://twitter.com/SpaceflightInc/status/1399458989381853184
Sweet fit! Sherpa-LTE1 is loaded and on the way to the Cape!! #SXRS5 #Transporter2
-
https://www.ipresslive.it/comunicates/47616/d-orbit-annuncia-wild-ride-la-nuova-missione-di-ion-satellite-carrier
https://news.satnews.com/2021/05/31/d-orbits-coming-up-with-a-wild-ride-via-their-ion-satellite-carrier/
https://www.isispace.nl/news/d-orbit-announces-wild-ride-the-upcoming-mission-of-its-ion-satellite-carrier/
Scheduled to lift-off in June of 2021, the vehicle, called ION SCV Dauntless David, will deploy six satellites into distinct orbits and perform the on-orbit demonstration of three payloads. This mission, which serves clients from 12 different nationalities, will increase the total number of payloads launched by D-Orbit to 54.
...
The mission manifest includes international clients, such as the Spanish Elecnor Deimos, the Bulgarian EnduroSat, and the Kuwaiti Orbital Space, which will launch the country’s first radio amateur satellite. Also on board, under contract with ISILAUNCH and integrated into a QuadPack from Dutch satellite manufacturer ISISPACE, are Finnish Reaktor Space, Marshall Intech Technology from UAE, and the Royal Thai Air Force.
...
During the fourth and final phase, decommissioning, D-Orbit’s operations team will deploy ADEO. Developed by the German HPS, ADEO is a small, 1U-size, de-orbit sail subsystem that will be deployed to 3.6 m2 at the end of the mission to accelerate the decommissioning phase by passive means, using the air drag of the upper atmosphere. This will lead leading to a faster, residue-free incineration of ION.
...
Hosted payloads:
- LaserCube
- Nebula
- Worldfloods
Deployed payloads according to skyrocket.de:
- Neptuno (Deimos) - from Vigoride-2
- Spartan (Endurosat) - from Vigoride-2
- QMR-KWT (Orbital Space) - from Vigoride-2
- W-Cube (Reactor Space)
- Ghalib (Marshall Space)
- NAPA 2 / RTAF-SAT 2 (Royal Thai Air Force)
Other payloads:
- ADEO (HPS)
-
Two 12U cubesats built by General Atomics to test laser communications with MQ-9 Reaper drones, will be on board the launch.
https://spacenews.com/dod-space-agency-to-launch-laser-communications-experiments-on-spacex-rideshare/
-
Scheduled to lift-off in June of 2021, the vehicle, called ION SCV Dauntless David, will deploy six satellites into distinct orbits and perform the on-orbit demonstration of three payloads.
Dauntless David = Wild Ride ?
-
Scheduled to lift-off in June of 2021, the vehicle, called ION SCV Dauntless David, will deploy six satellites into distinct orbits and perform the on-orbit demonstration of three payloads.
Dauntless David = Wild Ride ?
Wild Ride is the mission, Dauntless David is the spacecraft. Too many cutesy names on the same mission.
-
NearSpace Launch's TagSat-2 cubesat has been renamed to TROOP-2 (Train-Rapid on Orbit Payload).
https://spaceflight.com/customer-profile-nearspace-launch/
-
https://nextspaceflight.com/launches/details/2404
NET 24 June 2021
B1060.8
-
NearSpace Launch's TagSat-2 cubesat has been renamed to TROOP-2 (Train-Rapid on Orbit Payload).
https://spaceflight.com/customer-profile-nearspace-launch/
This is not a freeflying cubesat, but a hosted payload.
-
Cross-post:
Multiple USA launch updates from SFN Launch Schedule (https://spaceflightnow.com/launch-schedule/), updated June 7
Falcon 9 / Transporter-2
Launch date: June 24
Launch time: TBD
Launch site: SLC-40, Cape Canaveral Space Force Station, Florida
-
https://twitter.com/exolaunch/status/1402206900331106305
A sneak peek from Cape Canaveral, where the Exolaunch team integrates one ton of #smallsats with #Falcon9 for the #Transporter2 launch!
Stay tuned for more news on mission #Fingerspitzengefühl soon!
#NewSpace #LaunchServices
-
twitter.com/nanoavionics/status/1402215467343876101
The 2nd NanoAvionics #satellite to fly on the upcoming SpaceX Transporter-2 mission is successfully integrated into its deployer!
"D2/AtlaCom-1" is a high-performance nanosatellite, packing rideshare payloads in its 6U volume from @dragonfly_space, @SpaceJltz, & @AccionSystems
https://twitter.com/nanoavionics/status/1402216018693570562
Getting D2/Atlacom-1 on to, and later off of the Falcon 9 rocket in orbit wouldn't be easy without our launch partner @EXOLAUNCH which we are grateful for for the smooth integration.
Expect to hear more on the "D2/AtlaCom-1" & "Tiger-2" satellites flying with Transporter-2 soon.
-
https://twitter.com/spaceflightinc/status/1402327658722213892
-
https://twitter.com/D_Orbit/status/1402620044400529409
ION SCV Dauntless David is the latest vehicle of D-Orbit’s ION Satellite Carrier fleet! ION will lift off from Cape CanaveralRocketat the end of this month carrying to space 6 #satellites and 3 hosted payloads,serving clients from 11 different nationalities. Stay tuned! #wildride
-
https://twitter.com/EXOLAUNCH/status/1402961724966309891
We are very happy to be the launch partner for the @TUBerlin@TUBSpace #TUBIN satellite, as an important part of our upcoming #Falcon9 #Transporter2 mission! This launch marks the continued relationship of #Exolaunch with German university satellites! #Fingerspitzengefühl
https://twitter.com/TUBspace/status/1392484716058710016
https://www.raumfahrttechnik.tu-berlin.de/menue/research/current_projects/tubin/parameter/en/
-
https://twitter.com/hawkeye360/status/1402990685892988930
HawkEye 360’s Launch Integration Team with the unpacked #HawkEyeCluster3 spacecraft as they prepare for launch aboard @SpaceflightInc's #SXRS5 mission.
-
https://twitter.com/exolaunch/status/1403376471243165697
Our launch team just finished integration of the @nanoavionics #D2Atlacom1 satellite on the #Falcon9 #Transporter2 mission.
Check out this high-performance nanosatellite, packing rideshare payloads from @dragonfly_space, @SpaceJltz
& @AccionSystems: https://nanoavionics.com/news/international-consortium-adds-hyperspectral-imaging-and-communication-payloads-to-nanoavionics-rideshare-mission-named-d-2-atlacom-1/
-
https://nextspaceflight.com/launches/details/2404
Confirming recovery at LZ-1
-
Exolaunch has published an illustration of the payload stack.
-
Exolaunch has published an illustration of the payload stack.
Note: Seeing as Transporter-2 will now be an RTLS, it's unlikely there'll be any Starlink payloads as depicted here.
-
Exolaunch has published an illustration of the payload stack.
That isn't the payload stack, just an illustration of a generic stack.
-
How can we NOT know the launch time, at least approximately?
Hasn't at least one of the multitudinous payloads discussed the equator crossing time for the sun synchronous orbit?
-
How can we NOT know the launch time, at least approximately?
Hasn't at least one of the multitudinous payloads discussed the equator crossing time for the sun synchronous orbit?
Ben Cooper says "mid-afternoon EDT". http://www.launchphotography.com/Launch_Viewing_Guide.html
-
Exolaunch confirms that it will launch 29 satellites with a mass of almost one ton.
https://twitter.com/EXOLAUNCH/status/1404520240122404864
-
Exolaunch has published an illustration of the payload stack.
The above image is the final image in the press release. I've attached the other six images here.
Exolaunch to Send its Largest Mission of One Ton of Smallsats into Orbit via SpaceX's Transporter-2 Rideshare Mission
Company Finishes “Fingerspitzengefühl” Launch Campaign at Cape Canaveral for its International Customers Flying Aboard Falcon 9 (https://exolaunch.com/news-block-31.html)
Cape Canaveral, Florida, USA, June 14, 2021 – Exolaunch, the leading launch, deployment and in-space transportation services provider in the NewSpace sector, has just completed its launch campaign named ‘Fingerspitzengefühl’* by integrating 29 small satellites from the USA, Europe and South America aboard SpaceX’s Falcon 9 rideshare mission scheduled for June 2021. With a combined mass of close to one ton, Exolaunch doubles its mass capacity from SpaceX’s previous rideshare for small satellites, making ‘Fingerspitzengefühl’ its largest mission in terms of payload mass to date. This will also be one of the most diverse rideshare missions for the company bringing the total number of satellites launched by Exolaunch to 170.
EXOLAUNCH
An artist's impression of the Exolaunch's Fingerspitzengefühl satellites deployment into orbit
IMAGE CREDITS © 2021 EXOLAUNCH
Exolaunch’s rideshare cluster includes payloads with cutting-edge technologies for IoT, Earth Observation and scientific applications, and satellites from its international customers such as Loft Orbital, NanoAvionics, ICEYE, and the TU Berlin. Exolaunch is also providing flight hardware, separation systems and integration services to support Satellogic's four microsatellites on this mission.
EXOLAUNCH
Satellogic's satellites integration with EXOport
IMAGE CREDITS © 2021 EXOLAUNCH
This is the second dedicated rideshare mission of SpaceX’s SmallSat Rideshare Program and also the second of a series of rideshares Exolaunch is manifesting on Falcon 9 as part of a Multi-Launch Agreement the company signed with SpaceX in 2020. On SpaceX’s first record-breaking dedicated rideshare mission Transporter-1 earlier this year Exolaunch launched 30 contracted satellites. For every Falcon 9 launch procured through the Multi-Launch Agreement with SpaceX, Exolaunch ensures comprehensive rideshare mission management, satellite integration and deployment services for its customers.
EXOLAUNCH
TUBIN satellite integration with EXOport
IMAGE CREDITS © 2021 EXOLAUNCH
“This is a powerful NewSpace transatlantic partnership between SpaceX and Exolaunch,” said Jeanne Medvedeva, Vice President of Launch Services at Exolaunch. “Being an integrator for Falcon 9 launches, with the advanced flight hardware and deployment technologies in our product portfolio, allows us to serve even the most demanding NewSpace customers who prioritize performance, reliability and innovation to procured launch services. This latest mission shows the trust our customers have in our vast experience in rideshare launches and ability to perform skillfully and professionally.”
EXOLAUNCH
ICEYE's satellites integration with EXOport
IMAGE CREDITS © 2021 EXOLAUNCH
Connor Jonas, Exolaunch’s Program Manager said: “This has been Exolaunch’s most demanding and technically sophisticated mission. For this mission we are using the full range of our product line: four EXOport adapters, ten CarboNIX, separation systems and two EXOpod cubesat deployers. We have worked with the entire capacity of a SpaceX ESPA Ring to deploy one ton of customers’ payloads using only Exolaunch technology. This mission was challenging as we had to develop new technical solutions for such a large and diverse cluster, and find a way to deliver twice the hardware in half the time. Despite these challenges, our expert team delivered on time and pulled off an exceptionally smooth integration campaign at Cape Canaveral.”
EXOLAUNCH
Exolaunch integration - Die Maschine
IMAGE CREDITS © 2021 EXOLAUNCH
To maximize payload capacity and cost-effectiveness for its customers of this mission, Exolaunch will use its recent product addition, EXOport, a flexible multi-satellite adapter designed to optimally accommodate microsatellites and cubesats on a single Falcon 9 ESPA port. The company will also utilize its proprietary flight-proven separation systems – CarboNIX, the next generation shock-free separation system for microsatellites, and the EXOpod, Exolaunch’s upgraded cubesat deployer with half a decade of flight heritage, to flawlessly deploy its customers’ satellites into the target orbit.
EXOLAUNCH
Exolaunch ground support equipment set-up at SpaceX facilities
IMAGE CREDITS © 2021 EXOLAUNCH
“‘Fingerspitzengefühl’ on Transporter-2 symbolizes Exolaunch’s vast experience in successfully deploying our customers’ satellites into orbit,” said Medvedeva. “It's also a continuation of the individual mission names that started with ‘Zeitgeist’, literally ‘Spirit of the Time’, Exolaunch’s previous rideshare launch aboard SpaceX's Falcon 9 in January 2021.”
EXOLAUNCH
Exolaunch‘s Fingerspitzengefühl Transporter-2 infographic
IMAGE CREDITS © 2021 EXOLAUNCH
Starting next year, due to entry of the Reliant orbital transfer vehicle into the space tug market, Exolaunch will be able to meet the most ambitious requirements of its customers wishing to deploy satellite constellations to custom orbits by adjusting altitude, inclination, LTAN/LTDN, and performing orbital phasing. It is designed to deorbit shortly after deployment completion, minimizing the risks of space collisions and reducing orbital debris. Future generations of Reliant will also be able to perform on-demand active debris removal.
ENDS
Note to editors
* ‘Fingerspitzengefühl’ – a German term, literally "finger tips feeling"; meaning intuitive flair/instinct.
-
EXOLAUNCH
ICEYE's satellites integration with EXOport
IMAGE CREDITS © 2021 EXOLAUNCH
Photo news52_b6.jpg shows 2 satellites for ICEYE, so maybe XR-2 and Iceye X-10 (if XR-1 wasn't also called X-10, X-11 otherwise).
-
Orbital Sidekick Announces Upcoming Launch... (https://www.prnewswire.com/news-releases/orbital-sidekick-announces-upcoming-launch-of-its-most-powerful-satellite-aurora-expanding-the-companys-focus-to-promote-sustainability-efforts-across-multiple-industries-301312423.html)
The Orbital Sidekick Aurora Satellite is a 30-kilogram precursor to the six 100-kilogram ESPA class GHOSt satellites scheduled for launch in 2022. Seattle-based launch services provider Spaceflight will be coordinating the launch with a total of 36 payloads onboard the SpaceX Transporter-2 rideshare mission, taking place June 25, 2021 at Cape Canaveral Air Force Base in Florida.
-
EXOLAUNCH
ICEYE's satellites integration with EXOport
IMAGE CREDITS © 2021 EXOLAUNCH
Photo news52_b6.jpg shows 2 satellites for ICEYE, so maybe XR-2 and Iceye X-10 (if XR-1 wasn't also called X-10, X-11 otherwise).
There are four ICEYE satellites on this launch - one of them is XR-2.
-
ICEYE US will not be launching its first satellite in June 2021. ICEYE has not yet completed its Mission Operations Center in Irvine. As a result, the satellite (which has already been constructed) will be launched and operated by ICEYE OY, ICEYE’s parent company, pursuant to authorization issued by the Finnish telecom authority.
ICEYE US will have its MOC completed by the end of the summer, and is moving full speed ahead to launch its first satellite in December 2021. ICEYE will continue to work closely with FCC staff toward expeditious grant of its pending application.
-
There are four ICEYE satellites on this launch - one of them is XR-2.
So would that put YAM-3, TUBIN, and the two quadpacks on one port?
edit: I'm guessing there may be another dozen Swarm sats to get the number of satellites listed
-
Cross-post; Alba Orbital Cluster 3 back aboard Transporter-2?
http://www.albaorbital.com/launch
Name: Cluster 3 "That Time of Year"
Slots available: Sold Out
Launch: June 2021
Launch Vehicle: Falcon 9
Orbit: 500-600 km, SSO
-
https://umbra.space/umbra-releases-aerial-test-data/
But most importantly, we are launching a satellite. Umbra’s inaugural commercial satellite will leave Earth aboard a Falcon 9 departing from Cape Canaveral during the SpaceX Transporter-2 dedicated rideshare mission. Stay tuned for updates!
-
Cross-post; Alba Orbital Cluster 3 back aboard Transporter-2?
http://www.albaorbital.com/launch
Name: Cluster 3 "That Time of Year"
Slots available: Sold Out
Launch: June 2021
Launch Vehicle: Falcon 9
Orbit: 500-600 km, SSO
I don't think this confirms Cluster 3 is still manifested on this flight. I used the Wayback Machine and the table was exactly the same in early May, which was before Momentus cancelled all their 2021 missions. I think Alba simply hasn't updated the table yet.
-
Ben Cooper:
Falcon 9 will launch the Transporter-2 small satellite rideshare mission from pad 40 on June 24, in the mid-afternoon EDT. The first stage will land back at Cape Canaveral about eight minutes after launch.
-
-
Launch Photography (http://www.launchphotography.com/Transporter-2.html) has an updated launch time:
6/25/21 ~ 2:56pm
-
PlantSat is a 3U CubeSat satellite, built by students and engineers of the University of Chile. Its main mission is to monitor the behavior of a plant in a microgravity environment and in extreme conditions of solar radiation. One of the main goals is to train students about satellite technologies in order to develop advanced human capital. Proposing a UHF downlink using 4k8 GMSK and a S Band downlink using BPSK with Conv. R=1/2,K=7 & R.S. (255,223),115kbps. Planning a SpaceX launch on 24th June 2021 from Cape Canaveral into a 550km polar orbit. More info at https://spel.cl/
http://www.amsatuk.me.uk/iaru/formal_detail.php?serialnum=814
-
PlantSat is a 3U CubeSat satellite, built by students and engineers of the University of Chile. Its main mission is to monitor the behavior of a plant in a microgravity environment and in extreme conditions of solar radiation. One of the main goals is to train students about satellite technologies in order to develop advanced human capital. Proposing a UHF downlink using 4k8 GMSK and a S Band downlink using BPSK with Conv. R=1/2,K=7 & R.S. (255,223),115kbps. Planning a SpaceX launch on 24th June 2021 from Cape Canaveral into a 550km polar orbit. More info at https://spel.cl/
http://www.amsatuk.me.uk/iaru/formal_detail.php?serialnum=814
PlantSat has been dropped from this flight as it is not ready in time.
-
SFN confirming
June 25 • Transporter 2
Launch time: 1856-1954 GMT (2:56-3:54 p.m. EDT)
Launch site: SLC-40, Cape Canaveral Space Force Station, Florida
-
200311Z JUN 21
NAVAREA IV 514/21(11,26,27).
WESTERN NORTH ATLANTIC.
STRAITS OF FLORIDA.
OLD BAHAMA CHANNEL.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
251856Z TO 252044Z JUN, ALTERNATES
261856Z TO 262044Z, 271856Z TO 272044Z,
281856Z TO 802044Z AND 291856Z TO 292044Z JUN
IN AREAS BOUND BY:
A. 28-36-58N 80-36-03W, 28-39-00N 80-32-00W,
28-03-00N 80-13-00W, 27-59-00N 80-20-00W.
B. 25-53-00N 79-17-00W, 25-57-00N 79-07-00W,
25-15-00N 78-44-00W, 25-08-00N 79-00-00W,
25-36-00N 79-13-00W, 25-41-00N 79-14-00W,
25-44-00N 79-14-00W, 25-47-00N 79-15-00W.
C. 23-28-00N 79-32-00W, 23-44-00N 78-50-00W,
23-17-00N 78-35-00W, 22-57-00N 79-19-00W.
2. CANCEL THIS MSG 292144Z JUN 21.
-
Here's the associated "Space Debris" notice that just came out.
200346Z JUN 21
HYDROPAC 1819/21(61).
INDIAN OCEAN.
ILES OF KERGUELEN.
DNC 03.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
252114Z TO 252221Z JUN, ALTERNATES
262114Z TO 262221Z, 272114Z TO 272221Z,
282114Z TO 282221Z AND 292114Z TO 292221Z JUN
IN AREA BOUND BY
26-05S 066-11E, 25-53S 066-48E,
27-50S 067-48E, 33-01S 069-17E,
43-44S 072-10E, 49-49S 073-21E,
50-21S 073-03E, 50-09S 071-55E,
45-42S 069-31E, 30-36S 066-11E.
2. CANCEL THIS MSG 292321Z JUN 21.
-
I haven't seen anything about the launch trajectory. This being an SSO launch, is the launch profile going to be similar to a Polar launch - where it will head south from the cape?
-
yes
-
I haven't seen anything about the launch trajectory. This being an SSO launch, is the launch profile going to be similar to a Polar launch - where it will head south from the cape?
I have a feeling it'll start out going southeast, do a dogleg so that it's going due south once over the water, and after stage separation and fairing deploy, the second stage will do a final dogleg to the southwest.
-
https://twitter.com/OQTEC/status/1406852188048084994
-
Map visualization of Transporter-2 Launch Hazard Areas (https://www.google.com/maps/d/viewer?hl=en&mid=1ttdICaDzms7ltRa8IlxFXgbUCtZxIDmW&ll=25.749763793749587%2C-80.00558368369776&z=7) based on issued NGA-NOTMAR and FAA-NOTAM messages, valid for NET 25 Jun in window between 18:56-20:44 UTC, alternatively 26-29 Jun.
LZ1 landing for B1060.8 booster.
Extra drop area in Nassau information region (red) in case of boostback burn failure or second stage startup failure.
Estimated fairing recovery position 605km downrange in southern (orange) area north of Cuba (Havana/ACC).
Groundtrack raw estimation of Stage2 dogleg maneuver to polar orbit azimuth.
Stage2 debris reentry during second orbit in area north of Kerguelen Islands.
-
Article by Spaceflight Inc listing who is on their manifest:
https://spaceflight.com/whos-onboard-sxrs-5-spacex-transporter-2/ (https://spaceflight.com/whos-onboard-sxrs-5-spacex-transporter-2/)
-
Map visualization of Transporter-2 Launch Hazard Areas (https://www.google.com/maps/d/viewer?hl=en&mid=1ttdICaDzms7ltRa8IlxFXgbUCtZxIDmW&ll=25.749763793749587%2C-80.00558368369776&z=7) based on issued NGA-NOTMAR and FAA-NOTAM messages, valid for NET 25 Jun in window between 18:56-20:44 UTC, alternatively 26-29 Jun.
LZ1 landing for B1060.8 booster.
Extra drop area in Nassau information region (red) in case of boostback burn failure or second stage startup failure.
Estimated fairing recovery position 605km downrange in southern (orange) area north of Cuba (Havana/ACC).
Groundtrack raw estimation of Stage2 dogleg maneuver to polar orbit azimuth.
Stage2 debris reentry during second orbit in area north of Kerguelen Islands.
Is anyone able to add to this great map the location of staging and the boostback burn?
That might help people trying to see it from the shore.
-
https://twitter.com/flightclubio/status/1407009484032020480
Transporter-2's crazy RTLS trajectory down the Florida coast this week 🤯 Falcon 9 is truly a beast of a vehicle
#SpaceX #Transporter2 #SSO
-
Is anyone able to add to this great map the location of staging and the boostback burn?
That might help people trying to see it from the shore.
Here's my best guess. If the sky is clear, you should see the second stage due east, at increasing elevation, at the following times after launch.
Place | Downrange | Time |
Melbourne | 52km | T+02:26 |
Vero Beach | 102km | T+02:57 |
Port St Lucie | 142km | T+03:20 |
West Palm Beach | 210km | T+03:54 |
Fort Lauderdale | 280km | T+04:25 |
Miami | 320km | T+04:42 |
Staging is between Melbourne and Vero Beach.
-
Article by Spaceflight Inc listing who is on their manifest:
https://spaceflight.com/whos-onboard-sxrs-5-spacex-transporter-2/ (https://spaceflight.com/whos-onboard-sxrs-5-spacex-transporter-2/)
Shasta (Demo9) is not in the list.
-
Article by Spaceflight Inc listing who is on their manifest:
https://spaceflight.com/whos-onboard-sxrs-5-spacex-transporter-2/ (https://spaceflight.com/whos-onboard-sxrs-5-spacex-transporter-2/)
Shasta (Demo9) is not in the list.
"AstroDigital Shasta - Orbital Sidekick Aurora"
-
60% GO on primary, 70% on backup day. Additional risks rated low.
-
Launch hazard and airspace closure areas, courtesy of the 45th
-
https://youtu.be/jKO0_wvTLI8
Possible static fire at 15:45 EDT (1945 UTC)
-
Strongback retract on schedule
-
Looks good
Edit: estimated 10 second duration
-
Screen captures from above SFN livestream
-
https://twitter.com/SpaceflightNow/status/1407425671236837377
-
https://twitter.com/spacex/status/1407434307640070146
Static fire test of Falcon 9 complete – targeting launch of SpaceX’s second dedicated rideshare mission, Transporter-2, on Friday, June 25
-
https://twitter.com/isis_space/status/1407240121682890753
-
https://twitter.com/exolaunch/status/1407672406408368130
A smooth integration of four @Satellogic #NewSat satellites for the @SpaceX #Transporter2 mission, scheduled for launch from the Cape this Friday!
We are grateful to the Satellogic team for the fruitful partnership and look forward to a successful launch!
#Fingerspitzengefühl
-
L-2 Weather Forecast (https://www.patrick.spaceforce.mil/Portals/14/Weather/Falcon%209%20Transporter-2%20L-2%20Forecast%20-%2025%20Jun%20Launch.pdf?ver=S_f8CCdSxL5A8gQ7eV-wuA%3d%3d): Unchanged at 60% GO on primary, 70% on backup day.
-
https://spacenews.com/space-development-agency-to-launch-five-satellites-aboard-spacex-rideshare/
Transporter-2 is expected to carry as many as 88 small satellites from commercial and government customers to a sun synchronous polar orbit.
-
https://spacenews.com/space-development-agency-to-launch-five-satellites-aboard-spacex-rideshare/
Transporter-2 is expected to carry as many as 88 small satellites from commercial and government customers to a sun synchronous polar orbit.
The list in the first page of the thread includes 48 payloads so far (plus the Sherpa FX2, Sherpa LTE1, Exolaunch and ION SLV-003 dispensers). Still more or less 40 unidentified payloads, this will be a mess.
-
The list in the first page of the thread includes 48 payloads so far (plus the Sherpa FX2, Sherpa LTE1, Exolaunch and ION SLV-003 dispensers). Still more or less 40 unidentified payloads, this will be a mess.
The list on the first page has about 60 so far, it just doesn't have the launch integrator for some of them.
https://twitter.com/isis_space/status/1407600938425192449
The four 6U satellites we designed, built, and integrated for our customer Kleos will also be on board @SpaceX's rocket Falcon 9 launch mission. So glad to see them waiting to be launched after so many weeks of intensive teamwork!
https://twitter.com/iceyefi/status/1407720242130964482
Confirmation: SatelliteSatelliteSatelliteSatelliteFour ICEYE #SAR satellites are targeted for launch on this week's Friday, June 25, with @SpaceX rideshare mission! Static fire test completed yesterday. Stay tuned and follow @iceyefi for more updates as we get closer to liftoff!
-
There are four ICEYE satellites on this launch - one of them is XR-2.
So would that put YAM-3, TUBIN, and the two quadpacks on one port?
edit: I'm guessing there may be another dozen Swarm sats to get the number of satellites listed
The picture of them integrating TUBIN shows a cubesat deployer with the Swarm logo
-
Fairing recovery ship HOS Briarwood has departed Port Canaveral for the Transporter-2 mission.
This is the only fleet deployment for the mission. The booster will return and land at LZ-1.
https://twitter.com/SpaceXFleet/status/1407736260962275333
-
The list in the first page of the thread includes 48 payloads so far (plus the Sherpa FX2, Sherpa LTE1, Exolaunch and ION SLV-003 dispensers). Still more or less 40 unidentified payloads, this will be a mess.
The list on the first page has about 60 so far, it just doesn't have the launch integrator for some of them.
Shame on me, I just noticed that I completely forgot the 12 SpaceBEEs while doing the math, sorry
-
Here's my best guess. If the sky is clear, you should see the second stage due east, at increasing elevation, pass directly overhead at the following times after launch.
I hesitate to post this because normally you should know this kind of thing better than me, but "fixed that for you" :)
Once it gets past staging, it's going to be not much east and a whole lot UP. Most people can't tell the difference between looking 70-80 degrees up and looking 90 degrees straight up, so I have told my Florida coast peeps to face east but then look straight up. Actually I've told them to take binoculars and look for the rocket rising from the Cape, and then as they track it (assuming they stay with the second stage) it'll go pretty much right over their heads. See also the renderings from flightclub.io below:
https://twitter.com/flightclubio/status/1407009484032020480
https://twitter.com/BeckePhysics/status/1407300816407613452
-
A smooth integration of four @Satellogic #NewSat satellites for the @SpaceX #Transporter2 mission, scheduled for launch from the Cape this Friday!
I believe these are ÑuSat satellites.
https://en.wikipedia.org/wiki/%C3%91uSat
In other news, it looks like Centauri 4 from Fleet Space is also onboard.
https://news.satnews.com/2021/06/21/complete-with-beamforming-tech-fleet-space-to-launch-centauri-4-via-spacex-falcon-9-on-june-26/
-
Looks like there will be a 3-day delay.
https://twitter.com/TUBspace/status/1407983098218926086
-
More confirmation of delay on twitter:
https://twitter.com/GildasSeimbille/status/1407997933463744517
HOS Briarwood hasn't altered course (https://www.marinetraffic.com/en/ais/home/shipid:3279102/zoom:10), so maybe it will dock in Miami.
-
Official confirmation.
https://twitter.com/SpaceX/status/1408057032188469248
Geekwire article about YAM-3. (https://www.geekwire.com/2021/leostella-delivers-first-loft-orbital-satellite-spacexs-jam-packed-rideshare-mission/)
-
https://twitter.com/exolaunch/status/1408072178696802310
🚀Careful integration of the #TUBIN satellite with the @SpaceX #Falcon9 #Transporter2 payload stack at Cape Canaveral, using one of our #CarboNIX shock-free separation systems. We are pleased to support the advanced space research and development of our Alma Mater @TUBerlin!
-
Do these prelaunch checkouts refer to some of the planned satellites not being ready in time?
-
Do these prelaunch checkouts refer to some of the planned satellites not being ready in time?
From SpaceX that usually means the launch vehicle or GSE.
-
Someone on Reddit (https://www.reddit.com/comments/nz7rai/-/h2v505j), claiming to be one of the customers, says the reason for the delay is the need to reinspect/fix the fairing.
-
Do these prelaunch checkouts refer to some of the planned satellites not being ready in time?
From SpaceX that usually means the launch vehicle or GSE.
Not sure what you mean by 'From SpaceX'? like if there was an issue with a payload do you expect that customer to announce the delay and not SpaceX?
-
Do these prelaunch checkouts refer to some of the planned satellites not being ready in time?
If they are in the fairing, the payloads were checked out
-
Will there be any Starlink satellites aboard?
I remember there was an FCC filing approved for a similar situation aboard Transporter-1.
-
Will there be any Starlink satellites aboard?
I remember there was an FCC filing approved for a similar situation aboard Transporter-1.
The extra FCC waiver was only needed then because the Commission hadn't yet approved the license change to lower the Starlink orbits from 1000+ km to ~550 km. So SpaceX needed to request special permission to operate the 10 polar Starlinks at the 540 km altitude. Now they have the blanket license sorted, so they can operate hundreds of polar Starlinks at these lower altitudes, no additional waivers needed.
-
https://twitter.com/julia_bergeron/status/1408404391523127304
Meanwhile, in Port Canaveral, HOSS Briarwood has returned to wait out the Transporter-2 delay. Just Read the Instructions also received an AC delivery from the port crane.
#SpaceXFleet
#Fleetcam: youtu.be/gnt2wZBg89g
-
Targeting Tuesday, June 29 for launch of Transporter-2. This mission will launch 88 spacecraft to orbit and more customer mass than SpaceX’s previous dedicated rideshare mission
https://twitter.com/SpaceX/status/1408438784824279042
-
This mission will launch 88 spacecraft to orbit and more customer mass than SpaceX’s previous dedicated rideshare mission
More customer mass and still RTLS indicates no Starlink satellites on Transporter-2.
-
This mission will launch 88 spacecraft to orbit and more customer mass than SpaceX’s previous dedicated rideshare mission
More customer mass and still RTLS indicates no Starlink satellites on Transporter-2.
not necessarily
edit: The 88 satellite total probably precludes Starlinks, but the mass may not.
-
New notices from the NGA for Primary Day June 29 and Backup Day June 30.
251707Z JUN 21
NAVAREA IV 530/21(11,26,27).
WESTERN NORTH ATLANTIC.
STRAITS OF FLORIDA.
OLD BAHAMA CHANNEL.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
291856Z TO 292044Z JUN, ALTERNATE
301856Z TO 302044Z JUN
IN AREAS BOUND BY:
A. 28-36-58N 080-36-03W, 28-39-00N 080-32-00W,
28-03-00N 080-13-00W, 27-59-00N 080-20-00W.
B. 25-53-00N 079-17-00W, 25-57-00N 079-07-00W,
25-15-00N 078-44-00W, 25-08-00N 079-00-00W,
25-36-00N 079-13-00W, 25-41-00N 079-14-00W,
25-44-00N 079-14-00W, 25-47-00N 079-15-00W.
C. 23-28-00N 079-32-00W, 23-44-00N 078-50-00W,
23-17-00N 078-35-00W, 22-57-00N 079-19-00W.
2. CANCEL NAVAREA IV 515/21.
3. CANCEL THIS MSG 302144Z JUN 21.
251721Z JUN 21
HYDROPAC 1878/21(61).
INDIAN OCEAN.
ILES OF KERGUELEN.
DNC 03.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
292114Z TO 292221Z JUN, ALTERNATE
302114Z TO 302221Z JUN
IN AREA BOUND BY
26-05S 066-11E, 25-53S 066-48E,
27-50S 067-48E, 33-01S 069-17E,
43-44S 072-10E, 49-49S 073-21E,
50-21S 073-03E, 50-09S 071-55E,
45-42S 069-31E, 30-36S 066-11E.
2. CANCEL HYDROPAC 1819/21.
3. CANCEL THIS MSG 302321Z JUN 21.
-
Cross-post; no change to launch window on a particular date:
http://www.launchphotography.com/Launch_Viewing_Guide.html
The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the Transporter-2 small satellite rideshare mission from pad 40 on June 29 at 2:56pm EDT. The launch window stretches to 3:54pm. The first stage will land back at Cape Canaveral about eight minutes after launch.
-
All new L-3 is 70% GO on primary and backup days, with low additional risk factors.
-
https://twitter.com/hawkeye360/status/1408507471799500824
Members of the HawkEye Launch Integration Team hoist the #HawkEyeCluster3 spacecraft to integrate to @SpaceflightInc's Sherpa launch vehicle in preparation for the #SXRS5 mission.
-
L-2 launch weather forecast still 70% GO
-
https://twitter.com/jansenspace/status/1409210599578509315
Edit: The destination is a Star Wars reference, in case you’re not nerdy enough
-
Fairing recovery ship HOS Briarwood departed for Transporter-2 this morning.
I wonder what the in-cruise movie is...
https://twitter.com/SpaceXFleet/status/1409220189506445314
-
L-1 Primary improves to 80% GO
-
https://twitter.com/TSKelso/status/1409567520177070091
CelesTrak has pre-launch SupTLEs for 33 objects from the #Transporter2 launch scheduled for Jun 29 at 1856 UTC. SupTLEs assume a launch at the beginning of the planned launch window. I will update these if anything changes: https://celestrak.com/NORAD/elements/supplemental/.
This shows Starlinks on board
-
This shows Starlinks on board.
2x Maverick Surfboard = 2x ?
4x Newsat = ÑuSat no. 19-22 (https://space.skyrocket.de/doc_sdat/nusat-1.htm)
2x Tyvak = EG-3 = Tyvak 0173 ?
= ?
Exoport3 1 = ?
Exoport3 2 = ?
Exoport3 3 = ?
Exoport3 4 = ?
Exoport3 5 = ?
Exoport4 1 = ?
Exoport4 2 = ?
Exoport4 3 = ?
Exoport4 4 = ?
Exoport5 2 = ?
-
I'm guessing Exoport 3 is Iceye x2 and a quadpack, Exoport 4 would be YAM-3, TUBIN, and two cubesat deploys, Exoport 5 the other Iceye sats. Not entirely sure that's correct. No idea what Maverick is launching or what the other Tyvak sat is (or even if EG-3 is one of those two listed Tyvak sat deploys, there could be others).
edit: Maverick should be on the aft end of the second stage again
-
Based on various sources (companies Twitter accounts and websites, Gunter's Space Page, ElonX.net, T.S. Kelso's sup-TLEs, this thread), this is the list I've got right now:
TOTAL: 88 (with or without Starlink?)
-------------------------------------------------------------------------
Spaceflight: 2 tugs, 6 microsats, 29 cubesats (37)
tugs:
(1) SHERPA-FX2
(1) SHERPA-LTE1
microsats:
(3) Hawk 3A, 3B, 3C / Cluster 3 (HawkEye 360)
(1) YAM-2 (Loft Orbital)
(1) Tanker-001 / Tenzing (Orbit Fab)
(1) Aurora (Orbital Sidekick)
cubesats:
(1) Arthur (Aerospacelab)
(5) Astrocast 1.x1-1.x5
(1) Faraday Phoenix (In-Space)
(4) KSF1 Polar Vigilance Mission (Kleos Space)
(1) TIGER-2 5G IoT (OQ Technology)
(1) Lynk 06 / Shannon (Lynk Global)
(3) LEMUR-2 (Spire Global)
(12) SpaceBEE (Swarm Technologies)
(1) unknown
-------------------------------------------------------------------------
Exolaunch: 10 microsats, 19 cubesats (29)
microsats:
(1) YAM-3 (Loft Orbital)
(1) TUBIN (TU Berlin)
(4) ICEYE X11, X12, X13, XR2/X14
(4) NuSat 19-22
cubesats:
(1) D-2/AtlaCom-1 (NanoAvionics)
(?) SpaceBEE (Swarm Technologies)
(?) others
-------------------------------------------------------------------------
D-Orbit: 1 tug, 6 cubesats (7)
tugs:
(1) ION SCV 003 Dauntless David
cubesats:
(1) Ghalib
(1) Neptuno (DEIMOS)
(1) SPARTAN (EnduroSat)
(1) QMR-KWT (Orbital Space)
(1) W-Cube (Reactor Space)
(1) NAPA 2 / RTAF-SAT 2 (Royal Thai Air Force)
-------------------------------------------------------------------------
Starlink: ? sats (?)
-------------------------------------------------------------------------
Other: (11)?
microsats:
(1) GNOMES 2
(1) Umbra-SAR 2001
(1) Capella 5
(2) Mandrake 2
cubesats:
(2) LINCS1, LINCS2 (SDA)
?:
(2) Maverick Surfboard (?)
(2) Tyvak (?)
I'm not sure everything is 100% right and there are still unknowns, these dedicated rideshare missions seem to be a mess every time.
-
This mission will launch 88 spacecraft to orbit and more customer mass than SpaceX’s previous dedicated rideshare mission
More customer mass and still RTLS indicates no Starlink satellites on Transporter-2.
not necessarily
edit: The 88 satellite total probably precludes Starlinks, but the mass may not.
Was Transporter-1 (with apparently less total mass) performance constrained from RTLS?
-
Overview!
https://www.nasaspaceflight.com/2021/06/spacex-f9-transporter-2-rideshare/
https://twitter.com/NASASpaceflight/status/1409864222683676674
-
Y’all ready for a launch AND landing?
SpaceX is set to launch 88 satellites into a polar orbit in a rideshare mission dubbed Transporter-2.
Falcon 9 B1060 will embark on its 8th flight, and return to LZ-1 at the Cape.
Live coverage starts at 18:00 UTC:
https://twitter.com/spacecoast_stve/status/1409864205847744514
-
https://www.youtube.com/watch?v=5WE-nD_gozw
-
https://twitter.com/spacecoast_stve/status/1409868010177839112
-
This mission will launch 88 spacecraft to orbit and more customer mass than SpaceX’s previous dedicated rideshare mission
More customer mass and still RTLS indicates no Starlink satellites on Transporter-2.
not necessarily
edit: The 88 satellite total probably precludes Starlinks, but the mass may not.
Was Transporter-1 (with apparently less total mass) performance constrained from RTLS?
Transporter-1 was switched from RTLS to ASDS to launch Starlink satellites. They prob would have put in more Starlinks if they could have.
-
This mission will launch 88 spacecraft to orbit and more customer mass than SpaceX’s previous dedicated rideshare mission
More customer mass and still RTLS indicates no Starlink satellites on Transporter-2.
not necessarily
edit: The 88 satellite total probably precludes Starlinks, but the mass may not.
Was Transporter-1 (with apparently less total mass) performance constrained from RTLS?
Transporter-1 was switched from RTLS to ASDS to launch Starlink satellites. They prob would have put in more Starlinks if they could have.
That is an assumption. We don't know for sure if Transporter 1 could have done RTLS.
-
I think I've gotten most of the typos in here, but let me know if you see any more bad ones. This will be updated once or twice during the day.
-
SpaceX's page has been updated. (https://www.spacex.com/launches/) Only 3 Starlink satellites on this flight.
-
SpaceX is targeting Tuesday, June 29 for launch of Transporter-2, SpaceX’s second dedicated SmallSat Rideshare Program mission, from Space Launch Complex 40 (SLC-40) at Cape Canaveral Space Force Station in Florida. The 58-minute launch window opens at 2:56 p.m. EDT, or 18:56 UTC, and there is a backup opportunity available on Wednesday, June 30 with the same 58-minute window.
Falcon 9’s first stage booster previously supported launch of GPS III Space Vehicle 03, Turksat 5A, and five Starlink missions. Following stage separation, SpaceX will land Falcon 9’s first stage on Landing Zone 1 (LZ-1) at Cape Canaveral Space Force Station. One half of Falcon 9’s fairing previously supported Transporter-1 and a Starlink mission, and the other previously flew on SAOCOM 1B and a Starlink mission.
On board this launch are 85 commercial and government spacecraft (including CubeSats, microsats, and orbital transfer vehicles) and 3 Starlink satellites. While there are fewer spacecraft on board compared to Transporter-1, this mission is actually launching more mass to orbit for SpaceX’s customers.
-
https://youtu.be/_qnD0bgjGOk
-
SpaceX is reusing the patch
-
LAUNCH, LANDING, AND DEPLOYMENT
All Times Approximate
HR/MIN/SEC EVENT
00:01:12 Max Q (moment of peak mechanical stress on the rocket)
00:02:15 1st stage main engine cutoff (MECO)
00:02:18 1st and 2nd stages separate
00:02:26 2nd stage engine starts
00:02:32 Boostback burn begins
00:03:42 Fairing deployment
00:06:34 1st stage entry burn begins
00:08:24 2nd stage engine cutoff (SECO)
00:08:24 1st stage landing
00:54:13 2nd stage engine restarts
00:54:15 2nd stage engine cutoff (SECO-2)
00:57:50 NASA's PACE-1 deploys
00:57:57 Satellogic's NewSat-19 deploys
00:58:04 The 1st ICEYE satellite deploys from EXOPort-5
00:58:32 NASA's TROPICS Pathfinder deploys
00:58:37 PlanetiQ's GNOMES-2 deploys
00:58:44 Tyvak-0173 deploys
00:59:47 The 2nd ICEYE satellite deploys from EXOPort-3
01:00:00 Tyvak-0211 deploys
01:00:08 Loft Orbital’s YAM-3 deploys from EXOPort-5
01:00:18 TU Berlin’s TUBIN deploys from EXOPort-4
01:00:23 UmbraSAR deploys
01:00:33 D-Orbit's ION satellite carrier deploys
01:01:50 Space Development Agency/General Atomics/Peraton's LINCS-2 deploys
01:02:16 Satellogic's NewSat-20 deploys
01:02:30 Satellogic's NewSat-21 deploys
01:02:40 Capella SAR satellite deploys
01:02:46 The 3rd ICEYE satellite deploys from EXOPort-4
01:04:12 Space Development Agency/General Atomics/Peraton's LINCS-1 deploys
01:04:29 DARPA/Space Development Agency/Air Force Research Laboratory's Mandrake-2 Able deploys
01:05:33 The 4th ICEYE satellite deploys from EXOPort-3
01:06:48 Swarm’s 1st SpaceBEE cluster deploys from EXOPort-4
01:07:10 Swarm’s 2nd SpaceBEE cluster deploys from EXOPort-4
01:07:17 NanoAvionics’ D2/AtlaCom-1 deploys from EXOPort-3
01:07:24 Spire’s LEMUR number 1 deploys from EXOPort-3
01:07:47 Satellogic's NewSat-22 deploys
01:07:56 Loft Orbital's YAM-2 deploys
01:09:51 Spires’s LEMUR number 2 deploys from EXOPort-3
01:09:58 DARPA/Space Development Agency/Air Force Research Laboratory's Mandrake-2 Baker deploys
01:21:10 Spaceflight Inc.'s Sherpa-FX2 deploys
01:21:14 Spaceflight Inc.'s Sherpa-LTE1 deploys
01:27:35 Starlink satellites deploy
-
A bit different from usual
-
SpaceX photos
-
Transporter-1 was switched from RTLS to ASDS to launch Starlink satellites. They prob would have put in more Starlinks if they could have.
That is an assumption. We don't know for sure if Transporter 1 could have done RTLS.
If they could’ve RTLS, they would have.
The original profile was for RTLS, they switched to ASDS when they got approval for the 10 Starlink satellites.
-
"Press kit" capture with OCR.
-
Based on various sources (companies Twitter accounts and websites, Gunter's Space Page, ElonX.net, T.S. Kelso's sup-TLEs, this thread), this is the list I've got right now:
TOTAL: 88 (with or without Starlink?)
-------------------------------------------------------------------------
Spaceflight: 2 tugs, 6 microsats, 29 cubesats (37)
tugs:
(1) SHERPA-FX2
(1) SHERPA-LTE1
microsats:
(3) Hawk 3A, 3B, 3C / Cluster 3 (HawkEye 360)
(1) YAM-2 (Loft Orbital)
(1) Tanker-001 / Tenzing (Orbit Fab)
(1) Aurora (Orbital Sidekick)
cubesats:
(1) Arthur (Aerospacelab)
(5) Astrocast 1.x1-1.x5
(1) Faraday Phoenix (In-Space)
(4) KSF1 Polar Vigilance Mission (Kleos Space)
(1) TIGER-2 5G IoT (OQ Technology)
(1) Lynk 06 / Shannon (Lynk Global)
(3) LEMUR-2 (Spire Global)
(12) SpaceBEE (Swarm Technologies)
(1) unknown
-------------------------------------------------------------------------
Exolaunch: 10 microsats, 19 cubesats (29)
microsats:
(1) YAM-3 (Loft Orbital)
(1) TUBIN (TU Berlin)
(4) ICEYE X11, X12, X13, XR2/X14
(4) NuSat 19-22
cubesats:
(1) D-2/AtlaCom-1 (NanoAvionics)
(?) SpaceBEE (Swarm Technologies)
(?) others
-------------------------------------------------------------------------
D-Orbit: 1 tug, 6 cubesats (7)
tugs:
(1) ION SCV 003 Dauntless David
cubesats:
(1) Ghalib
(1) Neptuno (DEIMOS)
(1) SPARTAN (EnduroSat)
(1) QMR-KWT (Orbital Space)
(1) W-Cube (Reactor Space)
(1) NAPA 2 / RTAF-SAT 2 (Royal Thai Air Force)
-------------------------------------------------------------------------
Starlink: ? sats (?)
-------------------------------------------------------------------------
Other: (11)?
microsats:
(1) GNOMES 2
(1) Umbra-SAR 2001
(1) Capella 5
(2) Mandrake 2
cubesats:
(2) LINCS1, LINCS2 (SDA)
?:
(2) Maverick Surfboard (?)
(2) Tyvak (?)
I'm not sure everything is 100% right and there are still unknowns, these dedicated rideshare missions seem to be a mess every time.
Thanks to the launch timeline some more payloads can be identified:
- NASA's PACE-1 (this one (https://space.skyrocket.de/doc_sdat/pace_nasa.htm)?)
- NASA's TROPICS Pathfinder (https://essp.nasa.gov/earth-pathfinder-quests/projects/tropics/), originally intended to fly on Vigoride-2
- Tyvak-0211 (I have no idea of what it could be)
- 2 Spire Global's Lemur on Exolaunch mission
- 2 batches of Swarm Technologies SpaceBEE on Exolaunch mission (should be 16 if I did the math right according to the Exoport capacity indicated above, so I suppose 8 per batch)
- an unidentified number of Starlink satellites
This means that if all the payloads indicated on the quoted comment are actually onboard we should be at 86 spacecrafts (tugs + microsats + cubesats), with a payload on one of the SHERPAs still unidentified and WITHOUT counting the Starlinks, so I think that there's something wrong. Can someone double check my counts?
-
https://twitter.com/spacex/status/1409888591099142149
-
This isn't completely adding up for me. I wonder if Centauri 4 replaced something on one of the OTVs. Also not sure about SAI-2.
-
Transporter-1 was switched from RTLS to ASDS to launch Starlink satellites. They prob would have put in more Starlinks if they could have.
That is an assumption. We don't know for sure if Transporter 1 could have done RTLS.
If they could’ve RTLS, they would have.
The original profile was for RTLS, they switched to ASDS when they got approval for the 10 Starlink satellites.
Again, you're stating assumption as if it's fact.
-
Transporter-1 was switched from RTLS to ASDS to launch Starlink satellites. They prob would have put in more Starlinks if they could have.
That is an assumption. We don't know for sure if Transporter 1 could have done RTLS.
If they could’ve RTLS, they would have.
The original profile was for RTLS, they switched to ASDS when they got approval for the 10 Starlink satellites.
Again, you're stating assumption as if it's fact.
Cross-post; my bold:
Ben Cooper/Launch Photography (http://www.launchphotography.com/Delta_4_Atlas_5_Falcon_9_Launch_Viewing.html)
FALCON 9
The next SpaceX Falcon 9 rocket from Cape Canaveral will launch the sixteenth batch of Starlink satellites on November 21 at 10:17pm EST. A Falcon 9 will launch the first cargo Dragon 2 to the ISS, CRS-21, from pad 39A on December 2 at 12:50pm EST. The launch time gets 22-26 min. earlier each day. Other upcoming Falcon 9 launches are TBA. A Falcon 9 will launch NROL-108 for the National Reconnaissance Office from pad 40 on TBD. The first stage will land back at the Cape about eight minutes after launch. A Falcon 9 will launch the SiriusXM-7 communications satellite from pad 40 on December TBD, likely in the middle of the night EST. A Falcon 9 will launch the Turksat 5A communication satellite on December TBD. And a Falcon 9 will launch a smallsat rideshare mission into polar orbit on late December TBD. The first stage should land back at the Cape around eight minutes after launch.
-
This isn't completely adding up for me. I wonder if Centauri 4 replaced something on one of the OTVs. Also not sure about SAI-2.
This sum up to 88 spacefrafts without the Starlinks. Is that right? Shouldn't they be included in the "88 spacefrafts" count?
-
Visual mission profile by ElonX.net
-
This isn't completely adding up for me. I wonder if Centauri 4 replaced something on one of the OTVs. Also not sure about SAI-2.
This sum up to 88 spacefrafts without the Starlinks. Is that right? Shouldn't they be included in the "88 spacefrafts" count?
Starlinks should be included. I'm counting 90 with the Starlinks and separable deployers. That would mean two things on my list didn't make it. Fleet seems to think Centauri 4 is on there, so that leaves SAI-2 and the stuff on the separable deployers as candidates for not making the flight.
-
- NASA's PACE-1 (this one (https://space.skyrocket.de/doc_sdat/pace_nasa.htm)?)
The PACE mentioned above will launch no earlier than November 30, 2023. But I have no idea what this PACE-1 on the Transporter-2 mission is.
- Tyvak-0211 (I have no idea of what it could be)
This one is Centauri-4
-
- Tyvak-0211 (I have no idea of what it could be)
This one is Centauri-4
Thank you
-
- NASA's PACE-1
https://www.nasa.gov/ames/pace/
NASA’s Payload Accelerator for CubeSat Endeavors Initiative
ADP’s platform is a modular, low-cost avionics architecture paired with commercial off-the-shelf CubeSat components. PACE’s second orbital flight mission, PACE-1, will perform a set of experiments to demonstrate the ADP technology, kicking off a series of flights to follow. The PACE team will develop, test, and operate the projects, each utilizing the ADP platform. Payloads for PACE missions come from within NASA or other US Government agencies, small businesses and other industry, academic institutions, and research laboratories. In addition to demonstrating the ADP architecture, PACE-1 also supports four technology payloads.
ADP’s avionics core is currently built into a six-unit CubeSat form but can adapt to other form factors. The core provides the supporting systems to operate the spacecraft and the payloads it carries. The satellite is roughly the size of two large loaves of bread, stacked side-by-side. The avionics core occupies a third of the spacecraft’s interior, leaving plenty of room to integrate various payloads.
A lot more in depth information if you follow the link.
-
- NASA's PACE-1
https://www.nasa.gov/ames/pace/
NASA’s Payload Accelerator for CubeSat Endeavors Initiative
6U cubesat
PACE’s second orbital flight will host payloads on NASA's ADP avionics system platform.
ADP’s platform is a modular, low-cost avionics architecture paired with commercial off-the-shelf CubeSat components. PACE’s second orbital flight mission, PACE-1, will perform a set of experiments to demonstrate the ADP technology, kicking off a series of flights to follow. The PACE team will develop, test, and operate the projects, each utilizing the ADP platform. Payloads for PACE missions come from within NASA or other US Government agencies, small businesses and other industry, academic institutions, and research laboratories. In addition to demonstrating the ADP architecture, PACE-1 also supports four technology payloads.
ADP’s avionics core is currently built into a six-unit CubeSat form but can adapt to other form factors. The core provides the supporting systems to operate the spacecraft and the payloads it carries. The satellite is roughly the size of two large loaves of bread, stacked side-by-side. The avionics core occupies a third of the spacecraft’s interior, leaving plenty of room to integrate various payloads.
ADP first flight will demonstrate a switching capability that allows multiple GPS and radio communications systems to “take turns” receiving signals. These systems use a single antenna attached to the spacecraft rather than using multiple dedicated antennas, as it’s typically done. For the PACE-1 spacecraft, this means that the amount of surface space needed for antennas is cut in half, freeing up space for surface-mounted payloads such as an attached radio frequency tag and optical experiments hardware.
Components of ADP’s supporting avionics can be configured for use in earlier-stage tests, such as benchtop lab tests or suborbital flights. This flexible approach simplifies the logistics of testing payloads in different test environments, helping researchers speed their technologies through the maturation process.
-
Per Chris G., there are apparently three Starlink satellites onboard.
-
SAR image of the vertical Falcon 9 at SLC-40.
https://twitter.com/iceyefi/status/1409903986807820295
-
https://youtu.be/ikxG5U4Oucw
-
https://youtu.be/5WE-nD_gozw
NSF feed is live
-
https://twitter.com/emrekelly/status/1409939724236640258
SpaceX launch director is GO to start fueling Falcon 9 ahead of 1456 ET liftoff of Transporter-2.
-
T-20 venting
-
https://twitter.com/nasaspaceflight/status/1409943844913926149
T-20 minute vent. A nominal indicator of the countdown proceeding on the timeline.
➡️youtube.com/watch?v=5WE-nD…
-
https://youtu.be/_qnD0bgjGOk
SpaceX feed is now live, with Andy Tran hosting.
-
Good shot of LZ-1
-
Range and weather still Green
-
Stage 1 fuel load complete
-
Strongback retract
-
Hold
-
https://twitter.com/emrekelly/status/1409948754116026370
HOLD! Range is no-go for Transporter-2 launch.
-
Scrubbed due to a plane violating the range.
-
Range no go, recycling for tomorrow
-
So frustrating! We don't get treated to a RTLS too often.
Oh well. Better luck tomorrow, guys!
-
Weather system moving in, possibly why they can’t recycle today
-
Scrubbed due to a plane violating the range.
Is this confirmed, or just based on what the presenter said?
-
At least one reason for the scrub: the super chilled LOX only remains in spec for several minutes and a one hour launch window is insufficient to detank and refill the LOX.
-
https://twitter.com/spacex/status/1409951149910683648
-
In a way, this abort was good news. Visibility would have been horrible from the space coast. We'd barely have a view of the liftoff and maybe none of the landing. Crossing fingers that tomorrow's weather is better.
-
https://twitter.com/elonmusk/status/1409951549988782087
-
FYI
https://jrupprechtlaw.com/tfr-violation/
What Type of Criminal Punishment (Prison Time) or Fines can Result for a TFR Violation?
Depending on the type of TFR, you can get punished in three different ways for a TFR violation: (1) you can be criminally punished up to a maximum of 1 year in federal prison and a $100,000 fine, (2) you can have your pilot license suspended or revoked, and/or (3) receive a civil penalty by itself or on-top of the $100,000 fine.
They really need to prosecute boaters and pilots who violate range restrictions.
-
FYI
https://jrupprechtlaw.com/tfr-violation/
What Type of Criminal Punishment (Prison Time) or Fines can Result for a TFR Violation?
Depending on the type of TFR, you can get punished in three different ways for a TFR violation: (1) you can be criminally punished up to a maximum of 1 year in federal prison and a $100,000 fine, (2) you can have your pilot license suspended or revoked, and/or (3) receive a civil penalty by itself or on-top of the $100,000 fine.
They really need to prosecute boaters and pilots who violate range restrictions.
Was it even inside US airspace?
-
Did anyone look at flight radar to see what plane it was?
-
Question:
We know the first and second stages frost up because of the LOX super-chills the aluminum tank walls.
This photo shows something like that happening up near the top of the fairing just after the abort.
Is this just condensation because of the chilled air fed to the fairing volume?
Could it be frost?
-
Can the offending party be sued by SpaceX for the cost of recycling a launch, and can they be sued by the satellite providers for any costs they incur due to a launch delay?
-
Did anyone look at flight radar to see what plane it was?
https://media.discordapp.net/attachments/705847506227036271/859510000384737360/unknown.png
Landed at Merritt Island at 15:08.
-
Did anyone look at flight radar to see what plane it was?
It appears to have been a Southwest flight. SWA906 going from Baltimore to Montego Bay.
But that is speculative at the moment. Assuming that it was that aircraft that caused it.
That aircraft didn't enter the TFR.
-
Did anyone look at flight radar to see what plane it was?
https://media.discordapp.net/attachments/705847506227036271/859510000384737360/unknown.png
They also did not enter the TFR.
-
Hold
https://twitter.com/NASASpaceflight/status/1409948918637633538
Holding at T-30 seconds. Range is no go.
At least one reason for the scrub: the super chilled LOX only remains in spec for several minutes and a one hour launch window is insufficient to detank and refill the LOX.
https://twitter.com/NASASpaceflight/status/1409951717681213448
SpaceX confirm they are setting up for another attempt tomorrow. Some questions if the one hour window was enough for a recycle. Clock goes back to T-15 mins, but densified propellant....drain and refill. Very tight on the timeline. Thus scrub.
Launch window tomorrow, June 30, should have the same start time and duration?--appears to from the NGA:
New notices from the NGA for Primary Day June 29 and Backup Day June 30.
Edit: yes, same start time and duration
-
Here a Link to the TFR: https://tfr.faa.gov/save_pages/detail_1_0500.html
-
A bit different from usual
Is this launch trajectory illustration from an online contributor?
It shows the boostback burn with the rocket pointing down and firing upwards.
This is different than what we have seen, as in NROL-108. (https://forum.nasaspaceflight.com/index.php?topic=52045.msg2170789#msg2170789)
-
Did anyone look at flight radar to see what plane it was?
https://media.discordapp.net/attachments/705847506227036271/859510000384737360/unknown.png
They also did not enter the TFR.
Since Flightradar24 shows no aircraft inside the TFR, doesn't that mean that it wasn't broadcasting ADS-B? And doesn't that mean it may have been military or experimental/ultra-light?
-
Did anyone look at flight radar to see what plane it was?
https://media.discordapp.net/attachments/705847506227036271/859510000384737360/unknown.png
They also did not enter the TFR.
Since Flightradar24 shows no aircraft inside the TFR, doesn't that mean that it wasn't broadcasting ADS-B? And doesn't that mean it may have been military or experimental/ultra-light?
Would a drone cause a range violation and be picked up by range radar? Technically an aircraft as well, right?
-
New SpaceX webcast:
https://www.youtube.com/watch?v=sSiuW1HcGjA (https://www.youtube.com/watch?v=sSiuW1HcGjA)
-
New L-1 weather forecast: 70% 'Go' for Wednesday, 60% 'Go' for Thursday. All additional risk criteria are Low for both days.
-
Did anyone look at flight radar to see what plane it was?
https://media.discordapp.net/attachments/705847506227036271/859510000384737360/unknown.png
They also did not enter the TFR.
Since Flightradar24 shows no aircraft inside the TFR, doesn't that mean that it wasn't broadcasting ADS-B? And doesn't that mean it may have been military or experimental/ultra-light?
Is the "keep out zone" larger than the TFR? Is there a buffer around the TFR that can cause a scrub?
-
A bit different from usual
Is this launch trajectory illustration from an online contributor?
The source is SpaceX
https://www.spacex.com/static/images/infographics/F9_LANDING_ZONE_MOBILE.jpg
-
Question:
We know the first and second stages frost up because of the LOX super-chills the aluminum tank walls.
This photo shows something like that happening up near the top of the fairing just after the abort.
Is this just condensation because of the chilled air fed to the fairing volume?
Could it be frost?
It's not frost, you can see it in the pre-tanking photos, too. I think it's just the result of the refurbishment process. Maybe they had to patch/clean/fix certain areas after previous launch, leading to the color differences.
-
Since Flightradar24 shows no aircraft inside the TFR, doesn't that mean that it wasn't broadcasting ADS-B? And doesn't that mean it may have been military or experimental/ultra-light?
We've had a Cape or KSC launch delayed or scrubbed in recent times by a plane belonging to another executive agency.
-
FAA statement in this article (https://www.clickorlando.com/news/local/2021/06/29/sonic-booms-spacex-to-launch-rocket-return-booster-to-cape-canaveral/).
“The system worked and kept people safe, A privately operated helicopter violated a restricted area in the final seconds before a scheduled launch from Cape Canaveral Space Force Station in Florida this afternoon. Air traffic controllers immediately directed the pilot to leave the area. For safety and security reasons, the launch was scrubbed until tomorrow.”
-
https://twitter.com/dandickson24/status/1409951725679792132
-
Space AI SAI-2 6U cubesat
0173-EX-CN-2021
This permit is still pending and I don't see any other information on it. I'm going to drop this one from the manifest, which will make the numbers work out nicely.
-
What the FAA SHOULD do is have a do-not-enter area, and an inner "scrub" area. If you enter the do-not-enter area, you get the same punishments as you get now. It would be very bad if you entered it, but it shouldn't cause a scrub. If a plane or boat enters the inner scrub area, then the mission should scrub. Seems rather silly to scrub it because a helicopter was hovering a few hundred feet above where PEOPLE were standing and pretend its a safety issue.
-
updated "press kit" capture
-
What the FAA SHOULD do is have a do-not-enter area, and an inner "scrub" area. If you enter the do-not-enter area, you get the same punishments as you get now. It would be very bad if you entered it, but it shouldn't cause a scrub. If a plane or boat enters the inner scrub area, then the mission should scrub. Seems rather silly to scrub it because a helicopter was hovering a few hundred feet above where PEOPLE were standing and pretend its a safety issue.
Absolutely! Please contact your THREE congresspeople and tell THEM that. Don't know who they are? Enter your zip code: https://openstates.org/find_your_legislator/
-
Updated notices from the NGA. Primary Day = June 30 with Backup Days each day July 1 through July 5. All days have the same launch window as today.
292300Z JUN 21
NAVAREA IV 540/21(11,26,27).
WESTERN NORTH ATLANTIC.
STRAITS OF FLORIDA.
OLD BAHAMA CHANNEL.
FLORIDA.
1. HAZARDOUS OPERATIONS, ROCKET LAUNCHING
301856Z TO 302044Z JUN, ALTERNATE
011856Z TO 012044Z, 021856Z TO 022044Z,
031856Z TO 032044Z, 041856Z TO 042044Z AND
051856Z TO 052044Z JUL
IN AREAS BOUND BY:
A. 28-36-58N 080-36-03W, 28-39-00N 080-32-00W,
28-03-00N 080-13-00W, 27-59-00N 080-20-00W.
B. 25-53-00N 079-17-00W, 25-57-00N 079-07-00W,
25-15-00N 078-44-00W, 25-08-00N 079-00-00W,
25-36-00N 079-13-00W, 25-41-00N 079-14-00W,
25-44-00N 079-14-00W, 25-47-00N 079-15-00W.
C. 23-28-00N 079-32-00W, 23-44-00N 078-50-00W,
23-17-00N 078-35-00W, 22-57-00N 079-19-00W.
2. CANCEL NAVAREA IV 530/21.
3. CANCEL THIS MSG 052144Z JUL 21.
292315Z JUN 21
HYDROPAC 1918/21(61).
INDIAN OCEAN.
ILES OF KERGUELEN.
DNC 03.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
302114Z TO 302221Z JUN, ALTERNATE
012114Z TO 012221Z, 022114Z TO 022221Z,
032114Z TO 032221Z, 042114Z TO 042221Z AND
052114Z TO 052221Z JUL
IN AREA BOUND BY
26-05S 066-11E, 25-53S 066-48E,
27-50S 067-48E, 33-01S 069-17E,
43-44S 072-10E, 49-49S 073-21E,
50-21S 073-03E, 50-09S 071-55E,
45-42S 069-31E, 30-36S 066-11E.
2. CANCEL HYDROPAC 1878/21.
3. CANCEL THIS MSG 052321Z JUL 21.
-
And doesn't that mean it may have been military or experimental/ultra-light?
Experimental aircraft are not exempt from ADSB regulations. Both certified and experimentals can fly without ADSB in certain airspace. The airspace involved here would require ADSB-Out.
-
Falcon 9 launch scrub highlights airspace integration problems (https://spacenews.com/falcon-9-launch-scrub-highlights-airspace-integration-problems/)
One of the critics of current approaches to restrict airspace for launches has been the Air Line Pilots Association (ALPA). At the hearing, Capt. Joe Depete, president of ALPA, called for “collaboration by the aviation and aerospace sectors” to develop an airspace integration strategy.
“We agree that there is a better way,” DePete tweeted in response to Musk after the launch scrub, offering to work with SpaceX, the FAA and others “to support the safe integration of all national airspace users.”
-
The first call was to hold at 30 seconds, but the countdown kept going and no one called the hold. LD only calls it at 00:13 after a repeated announcement by RC.
https://www.youtube.com/watch?v=XeLlR_XRm_k
-
The airspace involved here would require ADSB-Out.
What airspace is involved? This would be outside the Orlando 30NM limit. Is there something nearby that triggers the requirement?
-
The airspace involved here would require ADSB-Out.
What airspace is involved? This would be outside the Orlando 30NM limit. Is there something nearby that triggers the requirement?
KSC and CCSFB.
-
The airspace involved here would require ADSB-Out.
What airspace is involved? This would be outside the Orlando 30NM limit. Is there something nearby that triggers the requirement?
The channel is outside the TFR (barely) but inside the CCAFS class D airspace, so the copter should have been talking to that tower controller. However there is no ADSB requirement there.
-
Here’s an illustration. The red X marks Jetty Park.
-
https://m.youtube.com/watch?v=MwJVJU2RAEY
New NSF link
-
Weather update:
https://twitter.com/trevormahlmann/status/1410269965639356416
sitrep: some holes but not many
#transportertoo
https://twitter.com/johnpisaniphoto/status/1410269662793932803
I heard there was a launch today. Weather is looking similar to yesterday’s.
Transporter-2, take 2, aiming for a 2:56pm EDT liftoff.
-
https://twitter.com/SpaceX/status/1410297096675028993
Targeting 3:11 p.m. EDT for today’s smallsat rideshare mission due to weather. The webcast will go live ~15 minutes ahead of liftoff → http://spacex.com/launches
-
https://twitter.com/SpaceX/status/1410299468558204931
Now targeting 3:31 p.m. EDT for launch due to weather
-
https://m.youtube.com/watch?v=MwJVJU2RAEY
NSF feed is live while we’re waiting
-
https://m.youtube.com/watch?v=d5iV2mQgIr0
Mission Control audio feed
-
Weather is holding so far
-
LD is go for prop load
-
T-20 venting
-
https://twitter.com/nasaspaceflight/status/1410315008320413698
T-20 minute vent. Everyone keep your fingers and toes crossed on the weather and keep your helicopters on the ground.
➡️youtube.com/watch?v=MwJVJU…
-
SpaceX.com (https://www.spacex.com/launches/) is live.
-
https://youtu.be/sSiuW1HcGjA
SpaceX stream is live, with Andy Tran back hosting
-
Strongback retracted
-
Liftoff!
-
https://twitter.com/spacex/status/1410320177699328000
Edit to add:
https://twitter.com/nasaspaceflight/status/1410320468649955332
-
MECO and stage separation
-
Fairing separation
-
https://twitter.com/nasaspaceflight/status/1410321177818640388
-
Entry burn with three engines
-
Four rings, so they didn't ditch one after Momentus dropped out. Starlinks are on top?
-
https://twitter.com/spacex/status/1410322285077012481
Edit to add:
https://twitter.com/nasaspaceflight/status/1410322664699346949
-
Stuck the landing
-
Geez that landing burn startup scared me, but I guess it was just an odd camera angle. :o Nice landing!
-
Four rings, so they didn't ditch one after Momentus dropped out. Starlinks are on top?
Starlinks are on the bottom, they are deploying last
-
Coverage resumes at T+53 for SES-2, followed shortly by deployment of PACE-1
-
Four rings, so they didn't ditch one after Momentus dropped out. Starlinks are on top?
Starlinks are on the bottom, they are deploying last
Look at the payload stack
-
Coverage resumes at T+53 for SECO-2, followed shortly by deployment of PACE-1
For SES-2, not SECO-2.
00:54:13 2nd stage engine restarts
00:54:15 2nd stage engine cutoff (SECO-2)
00:57:50 NASA's PACE-1 deploys
-
https://twitter.com/TSKelso/status/1409978206996680704
Updated TLEs, more updates expected
-
At T+2:18 on the SpaceX webcast, we get a look at someone's desktop showing the trajectory?
-
At T+2:18 on the SpaceX webcast, we get a look at someone's desktop showing the trajectory?
There is a parallel SpaceX stream for "mission control audio" which showed that for the entire launch. (they do that for most missions)
You can see this view for the whole mission (updated every second), rewind if you want:
https://www.youtube.com/watch?v=d5iV2mQgIr0&ab_channel=SpaceX
-
https://twitter.com/tgmetsfan98/status/1410328198760611846
What goes up, must come down.
Visibility wasn’t perfect today, but still caught a glimpse of Falcon 9 heard those awesome sonic booms.
nasaspaceflight.com/2021/06/spacex…
-
https://twitter.com/TSKelso/status/1409978206996680704
Updated TLEs, more updates expected
These TLE sets are based on 18:56 UTC launch time. Until there is an update, based on these TLE sets, I have generated new ones for the new launch time (19:31), they can be found in this post (https://community.libre.space/t/spacex-f9-transporter-2-2021-06-30-19-31-utc/8115/6?u=fredy).
-
https://twitter.com/hawkeye360/status/1410327651609362432
One hawk of #HawkEyeCluster3 was spotted at T+3:58 minutes!
-
https://twitter.com/mdcainjr/status/1410325567191269377
#SpaceX launches Transporter-2 after several delays due to weather. 8 minutes after launch the booster returns to the Space Coast to land at LZ-1!
Congrats @SpaceX team!
📸 me for @SpaceflightNow
#Transporter2
-
Four rings, so they didn't ditch one after Momentus dropped out. Starlinks are on top?
Starlinks are on the bottom, they are deploying last
Look at the payload stack
I would love to, if we actually had a decent image of the whole thing
-
SES-2 and SECO-2, no video but nominal orbit insertion
-
Andy Tran just confirmed 3x Transporter launches per year
-
Deployment order
-
https://twitter.com/nasaspaceflight/status/1410334912079708172
-
https://twitter.com/starfleettours/status/1410334552007102464
A "Rapidly Reusable Rockets, R R R🏴☠️" has landed at LZ-1.
This is B1060’s 8th landing and the 89th successfully recovered Falcon 9 rocket for @SpaceX!
📸: @Ktaylor46927775
-
https://twitter.com/nextspaceflight/status/1410335912949547008
No callout for the deployment of Tyvak-0173 as expected. Status unclear. Other deployments expected so far were confirmed.
-
No video for most deployments
-
No video for most deployments
Some production effort is being made; the web cast producers are switching between two different camera views up the stack.
***
Also noting that the Moon (I think) has appeared in most of those shots--with frame position slowly shifting as the second stage rotates or shifts attitude.
***
A deployment interval successfully completed over Siberia--no video coverage. There was video shortly thereafter with a second stage camera pointed aft, with the Sun over an arctic horizon (24 hours of sunlight every day currently in the Arctic).
-
Sherpa deployments up next in a few minutes
-
Four rings, so they didn't ditch one after Momentus dropped out. Starlinks are on top?
Starlinks are on the bottom, they are deploying last
The footage suggests that the Starlinks are actually on TOP.
-
Sherpa FX2 and LTE-1 deployment
-
In the immediate aftermath of the Sherpa deploys, it looks like there is one or two objects still on the stack. This is between the camera and the Starlinks, nearer to the far end of the stack.
Tyvak-173 deploy finally confirmed.
-
Starlink deployment confirmed, all payloads confirmed deployed
-
In the immediate aftermath of the Sherpa deploys, it looks like there is one or two objects still on the stack. This is between the camera and the Starlinks, nearer to the far end of the stack.
Tyvak-173 deploy finally confirmed.
They may just be dispensers.
Anyway, the 3 Starlinks have been deployed!
-
In the immediate aftermath of the Sherpa deploys, it looks like there is one or two objects still on the stack. This is between the camera and the Starlinks, nearer to the far end of the stack.
Tyvak-173 deploy finally confirmed.
Those are cubesat deployers
-
https://twitter.com/spacex/status/1410342602893791234
-
Rideshare deployment sequence complete
https://twitter.com/SpaceX/status/1410342522820300802
-
No video for most deployments
Some production effort is being made; the web cast producers are switching between two different camera views up the stack.
Highly unlikely to have been ground-controlled as there's only a single downlink feed from each stage. More like autonomous camera switching based on current deployment sequence timings.
I can't believe that even after what, 8 years of F9 v1.1 launches some people still think that the camera switching is being done from the ground.
-
Having those three Starlinks on top saved releasing a massive amount of debris. I'm glad they did it that way.
-
No video for most deployments
Some production effort is being made; the web cast producers are switching between two different camera views up the stack.
Highly unlikely to have been ground-controlled as there's only a single downlink feed from each stage. More like autonomous camera switching based on current deployment sequence timings.
I can't believe that even after what, 8 years of F9 v1.1 launches some people still think that the camera switching is being done from the ground.
Couldn't that single feed contain multiple camera feeds? And someone on the ground could decide which one to broadcast? This is how security camera recordings work.
-
No video for most deployments
Some production effort is being made; the web cast producers are switching between two different camera views up the stack.
Highly unlikely to have been ground-controlled as there's only a single downlink feed from each stage. More like autonomous camera switching based on current deployment sequence timings.
I can't believe that even after what, 8 years of F9 v1.1 launches some people still think that the camera switching is being done from the ground.
I believe there are at least four camera video channels continuously broadcast from the second stage on this flight that the web cast producers can choose from:
Internal LOX tank view,
External aft (pointing past the Merlin Vacuum engine bell),
External forward no. 1,
External forward no. 2, probably 180 deg. around the stack from the other external forward camera.
The editorial choices switching between available channels would be made from the ground in the studio. We don't get to see all the camera views all the time on the public web cast.
-
https://twitter.com/spaceflightinc/status/1410345892733800448
Happy to report we're receiving data from both #SherpaFX2 and #SherpaLTE. Everything looks great from here! A little refresher on our OTVs below.
https://twitter.com/satellogic/status/1410344950194216960
Launch Update: Each satellite has made contact with our ground station network with good health reports. Rosalind, Grace, Elisa, and Sofya--may you continue to inspire new innovations and collaborations across STEM here on Earth from your new home in space🛰️
-
The usual second stage de-orbit burn should be happening soon? (not broadcasted)
292315Z JUN 21
HYDROPAC 1918/21(61).
INDIAN OCEAN.
ILES OF KERGUELEN.
DNC 03.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
302114Z TO 302221Z JUN, ALTERNATE
012114Z TO 012221Z, 022114Z TO 022221Z,
032114Z TO 032221Z, 042114Z TO 042221Z AND
052114Z TO 052221Z JUL
IN AREA BOUND BY
26-05S 066-11E, 25-53S 066-48E,
27-50S 067-48E, 33-01S 069-17E,
43-44S 072-10E, 49-49S 073-21E,
50-21S 073-03E, 50-09S 071-55E,
45-42S 069-31E, 30-36S 066-11E.
2. CANCEL HYDROPAC 1878/21.
3. CANCEL THIS MSG 052321Z JUL 21.
-
No video for most deployments
Some production effort is being made; the web cast producers are switching between two different camera views up the stack.
Highly unlikely to have been ground-controlled as there's only a single downlink feed from each stage. More like autonomous camera switching based on current deployment sequence timings.
I can't believe that even after what, 8 years of F9 v1.1 launches some people still think that the camera switching is being done from the ground.
I believe there are at least four camera video channels continuously broadcast from the second stage on this flight that the web cast producers can choose from:
Internal LOX tank view,
External aft (pointing past the Merlin Vacuum engine bell),
External forward no. 1,
External forward no. 2, probably 180 deg. around the stack from the other external forward camera.
The editorial choices switching between available channels would be made from the ground in the studio. We don't get to see all the camera views all the time on the public web cast.
I'm countering your belief with facts over the last 7-8 years.
Point #1: Video is expensive to downlink, that fact should NOT be underestimated.
Point #2: The fact the LOX tank view is ITAR-sensitive (or whatever), according to your logic would just make it being downlinked on channel #N, whereas in the "real" world we get glimpses of the tank and then immediate switches to something like a groundtrack sim (NOT one of the other "available" camera downlinks according to you) to hide the tank views. This is a sure point that the view is not controlled live from the ground, otherwise there wouldn't be those ITAR whoopses.
There is no editorial choice, the camera view logic is programmed into the flight SW before the flight. And that is EXACTLY the way I would have done it as well. Onboard SW timings by the GNC driving deployment events and timelines. Command logic circuitry from the ground to receive on the stage is just a ludicrous idea. That's the sort of thing the FTS command destruct required. Meanwhile, SpX went with autonomous AFTS, that should tell you something about live commanding of an vehicle in ascent.
Do you not think that if SpaceX had say 4x the video bandwidth capacity during launch that they would not instead opt to downlink a single HD feed instead of DLing 4 or more simultaneous SD feeds, where N-1 of them would be wasted at any given point in time, AND after a point in time they moved toward 4K launch webcasts?
-
https://twitter.com/spacex/status/1410323594710716416
Anniversary of first launch!
-
....
Point #2: The fact the LOX tank view is ITAR-sensitive (or whatever), according to your logic would just make it being downlinked on channel #N, whereas in the "real" world we get glimpses of the tank and then immediate switches to something like a groundtrack sim (NOT one of the other "available" camera downlinks according to you) to hide the tank views. This is a sure point that the view is not controlled live from the ground, otherwise there wouldn't be those ITAR whoopses.
...
Do you not think that if SpaceX had say 4x the video bandwidth capacity during launch that they would not instead opt to downlink a single HD feed instead of DLing 4 or more simultaneous SD feeds, where N-1 of them would be wasted at any given point in time
A. I would have thought that a human is far more likely to do a whoopsy than a computer?
B: While SpaceX will only show one camera angle, they could still want 4 for engineering purposes?
-
This is a boring discussion. We know from the amateur-captured video streams from a few months back that the stream keeps switching between cameras at the second stage. Only one stream comes down. And I'm 99.99% sure that the switches are not commanded from the ground. On a general level everything about the mission is pre-programmed.
-
Both Spacecraft and Rocket stages operate autonomously, controlled by their on board computers.
The difference between Spacecraft (such as starlink sats, or Dragon) and a rocket upper stage (such as Falcon9 Stage 2) - the latter two actually sharing the same avionics computers, is that the spacecraft has an uplink channel through which the computer can be reprogrammed in flight, while rocket stages typically have no uplink channel and can no longer be reprogrammed once the vehicle leaves the pad.
You can verify that with SpaceX FCC applications for launch. Spacecraft such as Dragon have frequency allocation for telemetry down and uplink, while the rocket has only downlink channels allocated.
This does not mean that it's physically impossible to control a stage - all you'd have to do is add a receiver, license the frequencies with the FCC and start updating its programs in flight using any tracking station that has a lock on the vehicle.
In fact this is likely being done with some hybrid upper stages that also act as spacecraft, such as Rocket Lab's Photon upper stage that also is a sat bus. (And of course Dragon)
Licensing for a spacecraft is more hazzle than licensing for an upper stage. That, along with the fact there is typically not enough time to troubleshoot a problem and update the program during a regular upper stage flight, makes it not worthwhile unless there would be very specific mission requirements. Switching camera feeds is certainly not one of them, as that can be perfectly preprogrammed to be in sync with maneuvers and events such as payload deployments.
Now what would be more interesting is what happened with Tyvak-0173
It was supposed to deploy early in the sequence, but was only confirmed right before Starlink deployment.
Deployment typically works by sending a computer commanded deployment signal that triggers the deployment actuators (pyro on frangible nuts or actuated latches, plus a spring or additional separation pyros) which in turn physically separate the payload, which in turn separates a breakwire contact.
The separation of this breakwire then is reported via telemetry, thus confirming successful deployment (it also signals to the deployed payload that separation has occured and the payload is allowed to start its own activation sequence, which previously typically is inhibited) - having visual confirmation through video feed is a nice bonus but typically not required (and not available on all missions, see "secret" NRO missions)
lack of confirmation means no telemetry conformation which means the breakwire was not broken, which means the payload had not physically separated, even though it's attachment mechanism might have been loosened.
just prior to Starlink separation however the stage did start its not insignificant spin (which in fact provides the separation force for Starlink, as opposed to springs or pyros) - if Tyvak-0173 had been unlatched or its nuts blown, but the actual separation mechanism had failed (gotten stuck) then there was insufficient force to push the payload away and sever the connection. The centrifugal forces for Starlink deployment might as well have provided the necessary force to get Tyvak-173 "unstuck" - which would have broken the wire and thus confirm its deployment over Telemetry.
This of course would send Tyvak-0173 in a slightly different direction and - tumbling (it would inherit the fast stage rotation from Starlink deployment) but it should allow the sat to start its post-deployment sequence - although half an hour and half an orbit later than planned.
This is a lucky coincidence, it might allow the sat to recover (with the spin, its solar panels should generate some electricity) but whatever dispenser mechanism was used needs to be looked into.
Although making aggressive upper stage maneuvers to shake stuck payloads loose is certainly a great contingency maneuver by SpaceX, whether intended to do so or just a lucky side effect.
"Final destination, Starlink deployment. All passengers disembark at this station! This bus will now de-orbit and re-enter the atmosphere..." ;)
-
These payload stack camera views are driving me nuts. I think I have the A, B, C rings mapped out (although I don't know the port numbering). D ring is harder. Were Lincs or the Tyvak sats on the same port as GNOMES-2? There are deployers on the port above Sherpa-LTE1 but I don't know which they are. The Tyvaks are a pair of 6U and the Lincs are a pair of 12U.
-
Swarm confirms 28 Spacebees.
https://twitter.com/SwarmInternet/status/1410376759401353216
"We launched and made contact with 28 more satellites today, bringing our total to 120!"
-
-
Both Spacecraft and Rocket stages operate autonomously, controlled by their on board computers.
...
Agreed, with one tiny caveat: the F9 first stage does have a receiver aboard: it's commanded from the support ship during recovery operations. This is part of the FCC application IIRC.
But as you point out, the FCC app would have to flag it specially if uplink were to be done in flight, as opposed to pre-flight and post-landing.
-
The usual second stage de-orbit burn should be happening soon? (not broadcasted)
292315Z JUN 21
HYDROPAC 1918/21(61).
INDIAN OCEAN.
ILES OF KERGUELEN.
DNC 03.
1. HAZARDOUS OPERATIONS, SPACE DEBRIS
302114Z TO 302221Z JUN, ALTERNATE
012114Z TO 012221Z, 022114Z TO 022221Z,
032114Z TO 032221Z, 042114Z TO 042221Z AND
052114Z TO 052221Z JUL
IN AREA BOUND BY
26-05S 066-11E, 25-53S 066-48E,
27-50S 067-48E, 33-01S 069-17E,
43-44S 072-10E, 49-49S 073-21E,
50-21S 073-03E, 50-09S 071-55E,
45-42S 069-31E, 30-36S 066-11E.
2. CANCEL HYDROPAC 1878/21.
3. CANCEL THIS MSG 052321Z JUL 21.
I don't bother to post these, and they generally aren't even issued if there are no future backup days, but here is the Operations Completed notice for the Space Debris second stage reentry.
302225Z JUN 21
HYDROPAC 1923/21(61).
INDIAN OCEAN.
ILES OF KERGUELEN.
DNC 03.
CANCEL HYDROPAC 1918/21 AND THIS MSG, OPERATIONS
COMPLETED.
FYI, there was also an Operations Completed notice issued for the Rocket Launching notice, but I think we're all pretty clear that that took place! ;D
-
https://twitter.com/SpaceflightInc/status/1410384022685949952
Most awesome news: We can confirm separation of all spacecraft from Sherpa-LTE1!
-
https://twitter.com/SpaceflightInc/status/1410387247178780674
Are you sitting down? We can now confirm separation of all spacecraft from Sherpa-FX2 AND Sherpa-LTE1! That's 100% of payloads deployed successfully. Cheers everyone, and thanks for the ride as always @SpaceX. #SXRS5 #Transporter2
-
https://twitter.com/spacex/status/1410392725996904448
Tracking footage of Falcon 9 landing on LZ-1
-
Watching the landing one thing struck me.
Being as the boosters end up that way anyway, shouldn't they just paint them black initially, rather than white? Then they'd always look about the same...
-
https://twitter.com/julia_bergeron/status/1410397686906433539
Falcon 9 launching 88 payloads into orbit for the Transporter-2 mission. Moments after landing, the clouds unleashed the rain.
@NASASpaceflight replay: youtu.be/MwJVJU2RAEY
Recap: nasaspaceflight.com/2021/06/spacex…
https://twitter.com/mdcainjr/status/1410392015561498624
SpaceX launched 88 satellites this afternoon in a sun synchronous orbit. The Falcon 9 flew down the Florida coast and after booster separation the 1st stage returned minutes later!
📸 me for @SpaceflightNow
#SpaceX #Transporter2
Edit to add:
https://twitter.com/zshauladventure/status/1410384613457924098
Up close w/ #transporter2 #Falcon9 this was way better than the movie that shares the same name. Don't you agree?
@SpaceX
📷: Me - @NextHorizonsSF
-
Watching the landing one thing struck me.
Being as the boosters end up that way anyway, shouldn't they just paint them black initially, rather than white? Then they'd always look about the same...
If you notice, some parts are indeed left black now. Early Falcons had white interstages and white legs (at least in renders).
The parts that are still nominally white have a functional purpose: white absorbs much less of the Florida sun and lets the propellants stay cooler -- even if the white is a bit smudged. (Again, early Falcons were washed after landing to restore the albedo, but the present state is an engineering compromise: "white enough".)
-
Correct me if I'm wrong but is that the Launch/Service tower for Blue Origin's launch pad haha
-
No video for most deployments
Some production effort is being made; the web cast producers are switching between two different camera views up the stack.
Highly unlikely to have been ground-controlled as there's only a single downlink feed from each stage. More like autonomous camera switching based on current deployment sequence timings.
I can't believe that even after what, 8 years of F9 v1.1 launches some people still think that the camera switching is being done from the ground.
I believe there are at least four camera video channels continuously broadcast from the second stage on this flight that the web cast producers can choose from:
Internal LOX tank view,
External aft (pointing past the Merlin Vacuum engine bell),
External forward no. 1,
External forward no. 2, probably 180 deg. around the stack from the other external forward camera.
The editorial choices switching between available channels would be made from the ground in the studio. We don't get to see all the camera views all the time on the public web cast.
I'm countering your belief with facts over the last 7-8 years.
Point #1: Video is expensive to downlink, that fact should NOT be underestimated.
Point #2: The fact the LOX tank view is ITAR-sensitive (or whatever), according to your logic would just make it being downlinked on channel #N, whereas in the "real" world we get glimpses of the tank and then immediate switches to something like a groundtrack sim (NOT one of the other "available" camera downlinks according to you) to hide the tank views. This is a sure point that the view is not controlled live from the ground, otherwise there wouldn't be those ITAR whoopses.
There is no editorial choice, the camera view logic is programmed into the flight SW before the flight. And that is EXACTLY the way I would have done it as well. Onboard SW timings by the GNC driving deployment events and timelines. Command logic circuitry from the ground to receive on the stage is just a ludicrous idea. That's the sort of thing the FTS command destruct required. Meanwhile, SpX went with autonomous AFTS, that should tell you something about live commanding of an vehicle in ascent.
Do you not think that if SpaceX had say 4x the video bandwidth capacity during launch that they would not instead opt to downlink a single HD feed instead of DLing 4 or more simultaneous SD feeds, where N-1 of them would be wasted at any given point in time, AND after a point in time they moved toward 4K launch webcasts?
Your "Facts" are impressions unless you have links that confirm, particularly "the camera view logic is programmed into the flight SW before the flight". You may be correct, but your reply seems unnecessarily condescending, given that you've not really confirmed your argument with any real evidence. Can you provide a link to the fact (from SpaceX or other reputable source) that the camera views are preprogrammed, versus all sent concurrently and chosen on the ground for the live feed?
-
Your "Facts" are impressions unless you have links that confirm, particularly "the camera view logic is programmed into the flight SW before the flight".
See:
We know from the amateur-captured video streams from a few months back that the stream keeps switching between cameras at the second stage. Only one stream comes down.
Only one stream comes down, coupled with lack of FCC license for an uplink to the stage = preprogrammed.
You can verify that with SpaceX FCC applications for launch. Spacecraft such as Dragon have frequency allocation for telemetry down and uplink, while the rocket has only downlink channels allocated.
-
twitter.com/spacecoast_stve/status/1410414002895790081
Liftoff of #Falcon9 carrying 88 satellites to a sun-synchronous orbit!
The #Transporter2 mission is in the books, and boy, did it produce some beautiful imagery!
Read more about this mission: nasaspaceflight.com/2021/06/spacex…
https://twitter.com/spacecoast_stve/status/1410414011217330177
Curious about those things falling away? No, it’s not ice. Look closely. Those are the weather covers from the fairings. I’ve never caught them in a photo before. Pretty cool!
-
Your "Facts" are impressions unless you have links that confirm, particularly "the camera view logic is programmed into the flight SW before the flight". You may be correct, but your reply seems unnecessarily condescending, given that you've not really confirmed your argument with any real evidence. Can you provide a link to the fact (from SpaceX or other reputable source) that the camera views are preprogrammed, versus all sent concurrently and chosen on the ground for the live feed?
Evidence : The telemetry stream itself. I couldn't find the original posts on twitter anymore, but conveniently, Scott Manley did a nice summary video on youtube:
https://www.youtube.com/watch?v=74_N163HyhA
TL;DR; Falcon 9 2nd stage telemetry feed is broadcasted by the stage an not encrypted (at least not the video feed part of it) Although there is an encoding used to modulate a binary stream in radio waves, this is using an industry standard pattern for different byte values.
From this stream the video can be extracted - even at times when the stage is not in range of one of SpaceX ground stations (as the signal is intercepted using an independent tracking antenna, directly from the stage )
The video from Falcon9 uses a single feed, which auto cycles through the different camera views on a preprogrammed pattern which changes depending on the phase of flight, showing both external (engine, payload) and internal (tank) views. This stream stops a while after the deorbit burn, when the stage safes itself and shuts goes "dark" (transmitter shutdown, no more carier signal) prior to deorbit
During misison life streams SpaceX shows exactly this video feed as long as they have a telemetry downlink established, although they typically switch to an orbit visualization animation (which is generated on the ground based on telemetry data) whenever internal tank views are being broadcasted by the stage. Sometimes they miss the switch by a second and a few of these meanwhile well known tank views make it on the stream.
You can find videos on Youtube showing these internal tank views for several minutes, as decoded by amateur radio enthusiasts, also during flight phases not covered by SpaceX official public streams (such as after deorbit burn )
Edit: Reverse engineered details about the telemetry stream can be found here https://www.r00t.cz/Sats/Falcon9
including not only video but also GPS position and debugging information
Edit Edit: In response to the media going crazy about that, SpaceX later started encrypting the Falcon9 data, however since there were no changes in total bandwidth, there is no reason to assume that anything the way the cameras work ever changed:
https://twitter.com/r2x0t/status/1379843322152431622
-
Here is a peek above the clouds at three Transporter-2 telemetry comparisons:
1. Transporter-1 and Transporter-2 second stage.
2. NROL-108 and Transporter-2 first stage.
3. Zuma and Transporter-2 first stage.
The second stage telemetry is a good example of the difference between RTLS and ASDS mission profiles.
1. The Transporter-2 S1 burn is about 11 seconds shorter, in order to preserve propellant for boostback.
2. Both S2 burns are of the same length, but the lighter payload of Transporter-2 enables it to make up for the ΔV deficit.
There was no S1 specific telemetry for Transporter-1 post MECO, so I took the most recent example, being NROL-108.
I was puzzled by the circled differences. During the boostback burn, Transporter-2 acceleration goes positive just before engine cut-off, and velocity increases, but NROL-108 doesn't. I don't know exactly what SpaceX's reference system is for velocity, but the telemetry for both NROL-108 and Transporter-2 should be similar, and they aren't.
So, I looked for another example of RTLS telemetry, and happened upon Zuma, from way back in January 2018. Zuma is a much closer match for Transporter-2, but I'll end with a question rather than an answer.
Why doesn't the NROL-108 boostback burn go to positive acceleration at any point? How has it (nearly) returned to the launch site without doing so?
-
Why doesn't the NROL-108 boostback burn go to positive acceleration at any point? How has it (nearly) returned to the launch site without doing so?
Positive in what frame of reference? Also the boostback burn could simply rotate the velocity vector back toward the launch site without actually reducing the velocity and it would still reach back to the land while the acceleration calculated off of a scalar speed would leave you scrathing your head.
-
Why doesn't the NROL-108 boostback burn go to positive acceleration at any point? How has it (nearly) returned to the launch site without doing so?
Positive in what frame of reference? Also the boostback burn could simply rotate the velocity vector back toward the launch site without actually reducing the velocity and it would still reach back to the land while the acceleration calculated off of a scalar speed would leave you scrathing your head.
Sure, but why would the frame of reference be different for NROL-108?
-
https://twitter.com/TSKelso/status/1410504699820736515
CelesTrak has ephemeris-based SupTLEs for 3 #Starlink satellites from the Transporter-2 launch (2021-059) of 88 small satellites on a Falcon 9 from Cape Canaveral on Jun 30 at 1931 UTC:
This shows the Starlinks in 536 x 515km, 97.5 degree orbit
-
All subsats confirmed separated from Sherpa-LTE1 by 2345 UTC and from Sherpa-FX2 by 2358 UTC.
https://twitter.com/planet4589/status/1410444032380227586
-
Why doesn't the NROL-108 boostback burn go to positive acceleration at any point? How has it (nearly) returned to the launch site without doing so?
Positive in what frame of reference? Also the boostback burn could simply rotate the velocity vector back toward the launch site without actually reducing the velocity and it would still reach back to the land while the acceleration calculated off of a scalar speed would leave you scrathing your head.
Sure, but why would the frame of reference be different for NROL-108?
The difference is one launch was more lofted than the other and so the boostback burns had slightly different velocity vectors to start with. Also the downrange distances were probably slightly different due to yaw steering on ascent on this launch.
The aim of the boostback burn is obviously to rotate the velocity vector back such that the ballistic trajectory takes it back to the LZ. This can be done in principle without actually changing the magnitude of the velocity vector, i.e. a literal rotation of the velocity vector. This would show as 0 acceleration in your graph as SpaceX is only giving us the magnitude, while the vehicle would clearly be changing direction substantially. Admittedly, that kind of boostback approach is clearly not optimal, but it should illustrate my point that there's nothing weird in acceleration derived from the velocity magnitude not being positive, yet the vehicle being able to come back.
-
Mission integrator for LINCS
Peraton Supports Successful Launch of Space Development Agency Satellites on SpaceX Mission (https://www.prnewswire.com/news-releases/peraton-supports-successful-launch-of-space-development-agency-satellites-on-spacex-mission-301323771.html)
(PRNewsfoto/Peraton)
NEWS PROVIDED BY
Peraton
Jul 01, 2021, 08:00 ET
HERNDON, Va., July 1, 2021 /PRNewswire/ -- Two Space Development Agency (SDA) prototype satellites are now in orbit as a result of Peraton's work to secure rideshare space on the SpaceX Transporter-2 mission and performance of launch integration activities.
When the Transporter-2 mission departed the atmosphere on June 30, it took with it two SDA 12U Laser Interconnect & Communications System (LINCS) satellites launched aboard SpaceX's Falcon 9.
Peraton's support for SDA fell under its Mission Systems Engineering and Integration (MSE&I) indefinite delivery/indefinite quantity (IDIQ) contract which calls for Peraton—among other responsibilities—to help fill gaps where SDA lacks necessary in-agency capabilities. It illustrates one of Peraton's unique strengths, which is to help customers close mission gaps when delay or failure is not an option.
Peraton identified rideshare opportunities, procured the rideshare slot on Transporter-2 and provided integration services required to deliver the LINCS satellites into orbit. This work included manifesting, mission management, interface definition and production, spacecraft-to-launch vehicle integration at the launch site, and flight safety certification. Peraton, along with teammates TZero and Maverick Space Systems, played a critical role in maintaining the aggressive schedule to launch, and delivering these critical capabilities to orbit.
"We are privileged to help SDA accelerate the development and fielding of new capabilities necessary to ensure our technological and military advantage in space for national defense," said Roger Mason, president, Space & Intelligence sector. "When asked to fill a gap for SDA and quickly acquire commercial launch services, we secured the rideshare and took full responsibility for the launch integration activities. These LINCS experiments will provide data to advance the national defense space architecture."
Under the SDA MSE&I IDIQ contract, Peraton also provides full-lifecycle Systems Engineering and Integration services to support development, fielding and operations for SDA's Tranche 0 system – a constellation of 28 spacecraft, ground segments, mission planning and command and control capabilities supporting advanced warfighter mission scenarios and experiments.
About Peraton
Peraton drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world's leading mission capability integrator and transformative enterprise IT provider, we deliver trusted and highly differentiated national security solutions and technologies that keep people safe and secure. Peraton serves as a valued partner to essential government agencies across the intelligence, space, cyber, defense, civilian, health, and state and local markets. Every day, our 22,000 employees do the can't be done, solving the most daunting challenges facing our customers. Visit Peraton.com/News and follow Peraton on LinkedIn for news and updates.
SOURCE Peraton
https://www.peraton.com
-
ICEYE Launches Four New Radar Imaging Satellites, Taking a Further Leap Forward in Persistent Monitoring Capabilities (https://www.iceye.com/press/press-releases/iceye-launches-four-new-radar-imaging-satellites-taking-a-further-leap-forward-in-persistent-monitoring-capabilities?utm_content=171558470&utm_medium=social&utm_source=twitter&hss_channel=tw-2876294235)
Press Release 01 July 2021
ICEYE continues to grow the World’s largest synthetic-aperture radar (SAR) satellite constellation, which is used for persistent monitoring. This launch from SpaceX included three satellites intended for customer access and a next-generation demonstrator spacecraft.
Helsinki, FINLAND – July 1, 2021 – ICEYE, the global leader in persistent monitoring with radar satellite imaging, announces today the successful launch of four ICEYE SAR satellites. They were launched into orbit on a SpaceX’s Falcon 9 smallsat rideshare mission via EXOLAUNCH. Three satellites of the latest technology generation will be added to the ICEYE constellation after a commissioning phase. The fourth satellite of this launch will be operated as a demonstration mission for the company’s next-generation spacecraft. With this launch, ICEYE has successfully brought 14 satellites into orbit, including both commercial and dedicated customer missions.
With the launch of multiple satellites, ICEYE continues to grow and operate the world’s largest constellation of agile SAR satellites with the purpose of further developing and optimizing persistent monitoring capabilities. ICEYE’s constellation is designed to reliably provide imagery of customers’ areas of interest with a very short revisit time to enable the detection and tracking of rapid changes on the Earth’s surface, regardless of time of day, or weather conditions.
“ICEYE provides the world’s leading persistent monitoring services based on data collected from orbit,” said Rafal Modrzewski, CEO and Co-founder of ICEYE . “If you need to know what is happening in the world, ICEYE is your choice for persistent monitoring.”
The launched next-generation demonstration mission is equipped with the newest SAR satellite technology from ICEYE, allowing new and innovative capabilities in SAR imaging. These improvements include a factor two improvement in ground resolution, and the capability to simultaneously image and downlink data for near-immediate data delivery.
“The growth of ICEYE’s radar imaging satellite constellation is unprecedented, and as a result, our customers enjoy the most actionable set of capabilities in the world for persistent monitoring,” said Steve Young, Vice President of Business Development and Sales at ICEYE . “Not only the quantity, but also the consistent push for what’s possible with the latest technology keeps ICEYE at the forefront of radar satellite imaging.”
ICEYE serves SAR data to a global customer base in three imaging modes: Spot, Strip, and Scan, each with optimized resolution and coverage, all the way to 10,000 km2 with individual acquisitions. ICEYE is set to announce further radar satellite data capabilities in July, with additional launches set for later in the year.
# # #
Media Contact:
[email protected]
-
https://twitter.com/LeoLabs_Space/status/1410677211766702083
We've collected some great tracking data over the past day for the # Transporter2 payloads! The first pass was over the city of Midland, Texas just 1.5 hours after liftoff. We see all deployments as expected and are actively working with operators to provide support as needed.
-
Fairing recover ship HOS Briarwood is due to return from the Transporter-2 mission after midnight tonight.
https://twitter.com/SpaceXFleet/status/1410682033261715464
-
SpaceX photos
-
Why doesn't the NROL-108 boostback burn go to positive acceleration at any point? How has it (nearly) returned to the launch site without doing so?
Positive in what frame of reference? Also the boostback burn could simply rotate the velocity vector back toward the launch site without actually reducing the velocity and it would still reach back to the land while the acceleration calculated off of a scalar speed would leave you scratching your head.
Sure, but why would the frame of reference be different for NROL-108?
The difference is one launch was more lofted than the other and so the boostback burns had slightly different velocity vectors to start with. Also the downrange distances were probably slightly different due to yaw steering on ascent on this launch.
The aim of the boostback burn is obviously to rotate the velocity vector back such that the ballistic trajectory takes it back to the LZ. This can be done in principle without actually changing the magnitude of the velocity vector, i.e. a literal rotation of the velocity vector. This would show as 0 acceleration in your graph as SpaceX is only giving us the magnitude, while the vehicle would clearly be changing direction substantially. Admittedly, that kind of boostback approach is clearly not optimal, but it should illustrate my point that there's nothing weird in acceleration derived from the velocity magnitude not being positive, yet the vehicle being able to come back.
This is a fascinating question, and instructive on several levels.
On the first level, it is, as discussed, the definition of "velocity" as displayed.
It appears to be the speed, the scalar value, along the direction of motion.
Therefore, the "acceleration" is actually the change in that projected speed.
This gets farther from the physical acceleration felt by the stage with increases in the angle between the velocity vector and the direction of thrust.
My guess would be that near the end of the boostback burn, where the stage's trajectory is already headed back towards the coast, countering of the downrange velocity is complete, or nearly complete, and the end of the burn just increases the lofting.
The limited (~1/2g for T2, ~1g for Zuma) acceleration of the nearly empty stage says that this is not fully the case, but it was getting close.
On the second level, it shows how we tend to hold on to concepts and formalisms even as the world evolves around them.
A pure scalar "velocity" display was conceptually adequate when the early Falcons (and all other rockets) launched and all the acceleration was pretty much along a path from ground to orbit.
Even for most of the ASDS landings it wasn't too far from simple.
But with RTLS the vectors run all over the place.
Yet the display persists, even when close examination shows it results in questionable results.
What "we" could do (hint, hint, OneSpeed, please) is to run the same derivative (finite difference) calculation on the altitude display as was run on the velocity display. (Fortunately, the altitude value is less ambiguous, although not totally so.)
The vector difference between the velocity and the rate of change in the altitude would be the velocity parallel to the ground,
and the ratio between the velocities relates to the vector velocity angle with respect to the local horizontal.
Everyone who has read this far probably agrees that this is indeed fascinating.
-
SpaceX is reusing the patch
Destroying the one-to-one correspondence of missions and emblems is not to be approved! Astronautics historians are against!
-
SpaceX is walking the walk. Reuse of patch designs is the future. Will begin tracking turnaround times.
-
Welcome back to port Hoss Briarwood. #Fleetcam view thanks to @SpaceXFleet up in the wee hours operating and @Kyle_M_Photo stalking ships before sunrise.
https://twitter.com/julia_bergeron/status/1410893520139960322
-
Another view from the PTZ. Staying in bed sounded like a better option this morning.
https://twitter.com/julia_bergeron/status/1410895426266480641
-
4/4 for HOS so far.
https://twitter.com/SpaceXFleet/status/1410892193347350530
-
One leg has been folded.
https://twitter.com/SuperclusterHQ/status/1411005840434286594
-
2 missions and 100% success rate. HOS has finished work with SpaceX and is heading home.
There is a gap in East Coast launches so no need to keep this ship around.
https://twitter.com/SpaceXFleet/status/1410983483770540040
-
SpaceX booster B1060-8 stands at Landing Zone-1 after Transporter-2 mission.
https://twitter.com/JennyHPhoto/status/1411014207085191173
-
Why doesn't the NROL-108 boostback burn go to positive acceleration at any point? How has it (nearly) returned to the launch site without doing so?
Positive in what frame of reference? Also the boostback burn could simply rotate the velocity vector back toward the launch site without actually reducing the velocity and it would still reach back to the land while the acceleration calculated off of a scalar speed would leave you scratching your head.
Sure, but why would the frame of reference be different for NROL-108?
The difference is one launch was more lofted than the other and so the boostback burns had slightly different velocity vectors to start with. Also the downrange distances were probably slightly different due to yaw steering on ascent on this launch.
The aim of the boostback burn is obviously to rotate the velocity vector back such that the ballistic trajectory takes it back to the LZ. This can be done in principle without actually changing the magnitude of the velocity vector, i.e. a literal rotation of the velocity vector. This would show as 0 acceleration in your graph as SpaceX is only giving us the magnitude, while the vehicle would clearly be changing direction substantially. Admittedly, that kind of boostback approach is clearly not optimal, but it should illustrate my point that there's nothing weird in acceleration derived from the velocity magnitude not being positive, yet the vehicle being able to come back.
This is a fascinating question, and instructive on several levels.
On the first level, it is, as discussed, the definition of "velocity" as displayed.
It appears to be the speed, the scalar value, along the direction of motion.
Therefore, the "acceleration" is actually the change in that projected speed.
This gets farther from the physical acceleration felt by the stage with increases in the angle between the velocity vector and the direction of thrust.
My guess would be that near the end of the boostback burn, where the stage's trajectory is already headed back towards the coast, countering of the downrange velocity is complete, or nearly complete, and the end of the burn just increases the lofting.
The limited (~1/2g for T2, ~1g for Zuma) acceleration of the nearly empty stage says that this is not fully the case, but it was getting close.
On the second level, it shows how we tend to hold on to concepts and formalisms even as the world evolves around them.
A pure scalar "velocity" display was conceptually adequate when the early Falcons (and all other rockets) launched and all the acceleration was pretty much along a path from ground to orbit.
Even for most of the ASDS landings it wasn't too far from simple.
But with RTLS the vectors run all over the place.
Yet the display persists, even when close examination shows it results in questionable results.
What "we" could do (hint, hint, OneSpeed, please) is to run the same derivative (finite difference) calculation on the altitude display as was run on the velocity display. (Fortunately, the altitude value is less ambiguous, although not totally so.)
The vector difference between the velocity and the rate of change in the altitude would be the velocity parallel to the ground,
and the ratio between the velocities relates to the vector velocity angle with respect to the local horizontal.
Everyone who has read this far probably agrees that this is indeed fascinating.
Even that is missing components.
First complication:
1. The velocity displayed is in a rotating reference frame, matching earth rotation. However once out of the atmosphere the vehicle is measuring and experiencing its acceleration in the stationary earth centered coordinate frame.
That means, on a perfectly circular polar orbit you would still see velocity changes, with the velocity highest over the equator and lowest over the poles, with no actual acceleration or deceleration taking place.
Second complication:
2. The vehicle moves in the earth gravity field. The velocity goes up as the vehicle descends and gets reduced as the vehicle ascents - with no actual acceleration or decelaration taking place.
Third complication:
3. Acceleration components perpendicular to the motion component can not be observed directly, due to the scalar nature of the velocity displayed. But this again can be split into two components, corresponding to the 2 axis that are both perpendicular to the motion vector and perpendicular to each other:
1. The "upwards" axis - pointing 90° to the motion vector and in plane with the orbital plane. This can be inferred from changes in the vertical speed, which can be inferred again from changes in the rate of change of displayed altitude (after compensating for all other factors) Because the orbital parameters (periapsis, apoapsis) can be calculated completely at any time when knowing both altitude, speed, and climb/sinkrate
2. The "horizontal" axis - pointing 90° to the motion vector and perpendicular to the orbital plane. This "plane change" component, which plays a big role for example in launches to geostationary orbit (plane change during GTO burn) can not be observed at all. It does not show up as a change in velocity, and it also does not show up as a change in vertical velocity. And it also does not change the orbital parameters except inclination
That being said, SpaceX displays a visualization of the current vehicle trajectory whenever the on board camera displays the internal tanks, or when theres no camera feed. it is sometimes buggy, but almost always the current trajectory is displayed as a thin blue line based on real-time telemetry.
although it would be hard to read complete orbital parameters from this 3d display, it should be possible to read the inclination (angle between this line and equator or meridian) using OCR-ish techniques. this would allow to infer the plane change components and as such reconstruct the complete vehicle state at least during times where this is displayed.
sadly that is typically not the case during burns (but might be available in the mission control audio webcast!)
-
https://twitter.com/julia_bergeron/status/1411299592868597762
My remote camera took 1000+ photos. So many that it made another file on the SD card. I thought my camera missed the engine shot, but no, it was hidden waiting for me to back up my card. Enjoy one more view of Falcon 9 launching 88 payloads to orbit. #Transporter2
https://twitter.com/julia_bergeron/status/1411303902956433408
By request: A Falcon 9 GIF
-
I just rewatched this launch, what epic video of the booster landing.
The grid fins cutting through the water vapor approaching the landing zone then the divert to the LZ.
It’s routine now, but it is still visually spectacular seeing a large tube flying through the sky and nailing the center of the bullseye.
Just bananas!
-
Source is SpaceX
-
Source is SpaceX
And what does that have to do with this flight?
-
Source is SpaceX
And what does that have to do with this flight?
Since we don’t have a picture of the stack in profile, this is a good illustration of how different it is from the Transporter-1 stack. Specifically, you can see the designated volume for Starlink at the top.
-
That's a generic picture of a Transporter payload stack, not the Transporter 2 stack. They have always shown a payload space on top of the rings.
-
https://twitter.com/capellaspace/status/1411519682667032576
“First Light” images from our newest #SAR satellite have been released! #Giza #Ijen #BocaChica
The team is delighted with the 50cm resolution quality data. We look forward to providing even more imaging capacity from the Capella Constellation after final calibrations.
-
Repost and now public:
I did a mash-up of the SpaceX landing coverage with the recent video Elon supplied.
Credit Space.com and SpaceX
SpaceX landing with tracking cam video
https://youtu.be/oy2sYes0bAA
-
https://twitter.com/D_Orbit/status/1412031072544727043
SPARTAN by @EnduroSat will be the first satellite to be deployed by ION and we look forward to it!
-
Maverick Space Systems also did launch integration for the Mandrake 2 sats.
Blackjack Program Successfully Deploys Two Mandrake 2 Satellites (https://www.darpa.mil/news-events/2021-07-07)
DARPA successfully deployed two satellites on June 30 as part of the SpaceX Transporter 2 launch. Both Mandrake 2 spacecraft, Able and Baker, are functioning well and progressing through checkout and commissioning. Conceived as an early risk-reduction flight for DARPA’s Blackjack program, the Mandrake 2 mission will prove out advanced laser communications technologies for a broad government stakeholder team that includes DARPA, Space Development Agency (SDA), Air Force Research Laboratory Space Vehicles Directorate (AFRL/RV), and Office of the Secretary of Defense’s (OSD) Joint Capability Technology Demonstration (JCTD) office.
During its on-orbit mission, Mandrake 2 will demonstrate the viability of low size, weight, power, and cost laser communications terminals that are interoperable. “This constitutes a game-changing advancement and a critical enabler for proliferated space architectures,” said Stephen Forbes who is program manager of the Blackjack program in DARPA’s Tactical Technology Office. “Mandrake 2 has already successfully demonstrated a rapid satellite development timeline, since the Blackjack program moved from contract award to delivery of space vehicles at the launch site in less than nine months.”
The successful launch of Mandrake 2 represents the culmination of a rapid design and development effort by a large team of industry performers led by SEAKR Engineering, as the prime contractor. Astro Digital built the satellite buses for Mandrake 2. Advanced Solutions (ASI) wrote the Mandrake 2 flight software and is supporting mission operations. Maverick Space Systems performed integration and test analysis, as well as launch integration services. Lockheed Martin provided integration support and launch procurement. SA Photonics developed the optical inter-satellite link (OISL) hardware demonstrated as part of the Mandrake 2 mission, and SpaceX provided launch services as part of its SmallSat Rideshare Program.
-
83 objects now cataloged from the Transporter 2 launch in 523 x 536 km x 97.5 deg sun-synch orbit. I was actually only expecting 82 (with 6 more yet to be deployed from ION), but maybe there was an adapter that separated with the Starlinks.
https://twitter.com/planet4589/status/1412970588105318406
-
83 objects now cataloged from the Transporter 2 launch in 523 x 536 km x 97.5 deg sun-synch orbit. I was actually only expecting 82 (with 6 more yet to be deployed from ION), but maybe there was an adapter that separated with the Starlinks.
https://twitter.com/planet4589/status/1412970588105318406
So far the SpaceBEE and Starlink sats are identified by name on space-track.org
-
48900 2021-059X TUBIN
48931 2021-059BE Hawk-3B
48938 2021-059BM Shannon
48957 2021-059CG Hawk-3A
-
https://twitter.com/D_Orbit/status/1416055786179121154
QMR-QWT by @orbital_space and Ghalib by Marshall Intech Technologies have been successfully deployed into space by ION Satellite Carrier. Both clients confirmed the acquisition of the signal from the #satellites.
Good luck with your missions and thanks for flying with ION
-
48953 2021-059CC ARTHUR-1
48954 2021-059CD ASTROCAST-0201
48961 2021-059CL ASTROCAST-0202
48955 2021-059CE ASTROCAST-0203
48960 2021-059CK ASTROCAST-0205
48898 2021-059V CENTAURI-4 (TYVAK-0211)
48910 2021-059AH GNOMES-2
48957 2021-059CG HAWK-3A
48931 2021-059BE HAWK-3B
48948 2021-059BX HAWK-3C
48912 2021-059AK ION SCV-003
48905 2021-059AC NUSAT-19 (ROSALIND)
48921 2021-059AU NUSAT-20 (GRACE)
48920 2021-059AT NUSAT-21 (ELISA)
48919 2021-059AS NUSAT-22 (SOFYA)
48938 2021-059BM SHANNON
48883 2021-059E SPACEBEE-100
48884 2021-059F SPACEBEE-101
48886 2021-059H SPACEBEE-102
48888 2021-059K SPACEBEE-103
48890 2021-059M SPACEBEE-104
48896 2021-059T SPACEBEE-105
48893 2021-059Q SPACEBEE-106
48894 2021-059R SPACEBEE-107
48895 2021-059S SPACEBEE-108
48897 2021-059U SPACEBEE-109
48899 2021-059W SPACEBEE-110
48904 2021-059AB SPACEBEE-111
48935 2021-059BJ SPACEBEE-88
48947 2021-059BW SPACEBEE-90
48940 2021-059BP SPACEBEE-91
48939 2021-059BN SPACEBEE-93
48937 2021-059BL SPACEBEE-94
48945 2021-059BU SPACEBEE-95
48934 2021-059BH SPACEBEE-96
48936 2021-059BK SPACEBEE-97
48949 2021-059BY SPACEBEE-98
48946 2021-059BV SPACEBEE-99
48882 2021-059D SPACEBEENZ-10
48889 2021-059L SPACEBEENZ-7
48891 2021-059N SPACEBEENZ-8
48887 2021-059J SPACEBEENZ-9
48879 2021-059A STARLINK-3003
48880 2021-059B STARLINK-3004
48881 2021-059C STARLINK-3005
48900 2021-059X TUBIN
48892 2021-059P TYVAK-0173
48906 2021-059AD UMBRA-2001
48915 2021-059AN YAM-3
-
48959 2021-059CJ LEMUR 2 CARLSANTAMARI
48885 2021-059G LEMUR 2 JACKSON
48925 2021-059AY LEMUR 2 JOHN-TREIRES
48929 2021-059BC LEMUR 2 MERIMA
48907 2021-059AE MANDRAKE 2 ABLE
48908 2021-059AF MANDRAKE 2 BAKER
48941 2021-059BQ SHERPA-LTE1
48933 2021-059BG SPACEBEE-89
48932 2021-059BF SPACEBEE-92
48901 2021-059Y TROPICS PATHFINDER
-
By this letter, Spire Global, Inc. (“Spire”) provides notification to the Federal Communications
Commission that on June 30, 2021, six (6) LEMUR-2 satellites, including five (5)
Luxembourg-licensed MINAS satellites (part of the LEMUR-2 system) were deployed into an altitude
of approximately 550km, with orbit of SSO (13:30 LTDN) from a SpaceX Falcon 9 vehicle, which was
launched from the Space Launch Complex 40 (SLC-40) at Cape Canaveral Space Force Station,
Florida.
Spire has now deployed thirty-two (34) of its seventy-two (72) Phase IC, twelve (12) of its two
hundred and thirty-six (236) Phase II and twenty-two (22) Luxembourg-licensed LEMUR-2 satellites,
and those satellites are operating consistent with Spire’s license authorization.
-
https://twitter.com/planet4589/status/1417672513451175937
The Echostar Australia EG-3 (Tyvak-0173) satellite launched aboard SpaceX's Transporter 2 on Jun 30 has raised its orbit from 540 to 650 km.
-
https://twitter.com/D_Orbit/status/1418186644881092608
Mission Update! On July 21th, ION Dauntless David successfully deployed SPARTAN into its operational orbit. SPARTAN is a software-defined 6U CubeSat platform carrying 7 payloads on a single bus and the first of many upcoming Shared Satellite Missions by @EnduroSat
https://twitter.com/D_Orbit/status/1417133707870212111
On July 18th, ION Dauntless David successfully deployed Napa-2 satellite by @ThaiAirForce into its operational orbit. Acquisition of the signal confirmed by the client. NAPA-2 is a 6U designed for monitoring and responding to natural disasters.
Thanks for flying with IONSatellite
-
48952 2021-059CB ASTROCAST-0204
48944 2021-059BT AYAN-21
48913 2021-059AL CAPELLA-5 (WHITNEY)
48951 2021-059CA DEMO8(TENZING)
48956 2021-059CF DEMO9(AURORA)
48918 2021-059AR ICEYE-X11
48914 2021-059AM ICEYE-X12
48916 2021-059AP ICEYE-X13
48917 2021-059AQ ICEYE-X15
48927 2021-059BA LEMUR 2 AC-CUBED
48923 2021-059AW LEMUR 2 ANNABANANA
Not sure if Ayan-21 is an unknown payload or just an unknown name for one of the payloads
edit: Ayan-21 is Tiger-2, h/t to jcm
-
https://twitter.com/planet4589/status/1418777707844833289
While we're waiting for more Nauka tracking data, I decided to take a look at the Transporter-2 mission launched on June 30 and make some height-vs-time plots. Here's an overview: the biggest orbit maneuvers have been by the Starlinks and the EG-3 satellite
twitter.com/planet4589/status/1418778254475989004
Let's zoom in a bit on the rest of the satellites. SpaceBEEs in yellow, Lemurs in magenta. Unidentified sats in red. Height dispersion is about 10 km. You can see the orbit changes of the 4 Satellogic Nusat satellites (blue). Let's zoom in in tiny chunks from bottom to top
https://twitter.com/planet4589/status/1418778616410820611
In the lower tier we see the Swiss Astrocast sats in cyan, a clump of the SpaceBEEs in yellow, and a few others
twitter.com/planet4589/status/1418779109275090945
Notable in the next tier are the three Hawkeye360 Hawk-3 satellites, which are adjusting their orbits to fly in formation. Again, red lines are so-far-unidentified objects. Note the SHERPA-LTE1 dispenser sat in black; SHERPA-FX2 has not yet been identified.
https://twitter.com/planet4589/status/1418779488729673731
Moving up in altitude, tier 3 has the initial positions of the Nusats before they lowered altitude, and the four Finnish ICEYE radar sats, as well as two Spire Lemurs and a couple of unidentifieds
twitter.com/planet4589/status/1418779907145019392
Moving toward the top of the pack note the high drag of the Capella 5 radar sat with its big antenna, and the small orbit adjustments being made by the ION SVC03 satellite dispenser
https://twitter.com/planet4589/status/1418780362134675456
And at the top tier we see mostly the small SpaceBEEs, the initial height of EG-3 before it raised orbit, a Lemur, and the mysterious object cataloged as SpaceBEE-105 which seems to be raising orbit, something that the SpaceBEEs have not done in the past. (could be a mistag)
twitter.com/planet4589/status/1418780904407896066
Zooming out again, here are the 12 unidentified objects and the 12 sats they are thought to correspond to. Not yet ready to guess which is which! Hunch that the two very close pairs might be the Kleos KSM sats, though
https://twitter.com/planet4589/status/1418781159136313351
And the three cubesats dispensed from ION on Jul 16-18 have not yet been tracked.
-
https://twitter.com/D_Orbit/status/1419589245455507456
On July 24th, ION successfully deployed NEPTUNO, the 6th and last #satellite, into its operational orbit.
NEPTUNO, by @ElecnorDeimos, is the prototype satellite for a LEO #CubeSat constellation dedicated to maritime surveillance.
Acquisition of the signal [White heavy check] mark A PR will follow
-
48930 2021-059BD KSF1-A
48926 2021-059AZ KSF1-B
48942 2021-059BR KSF1-C
Not yet identified on Space-track.org: D2/AtlaCom-1, Faraday Phoenix, Ghalib, Kleos (x1), LINCS A/B, NAPA 2, Neptuno, PACE-1, Painani-II, QMR-KWT, Sherpa-FX2, Spartan, W-Cube, YAM-2
-
48922 2021-059AV D2/ATLACOM-1
48902 2021-059Z LINCS1
48903 2021-059AA LINCS2
48963 2021-059CN NAPA-2
48966 2021-059CR NEPT-1 (Neptuno?)
48958 2021-059CG SHERPA-FX2/TAGSAT-2
48965 2021-059CQ W-CUBE
48911 2021-059AH YAM-2
Not yet identified on Space-track.org: Faraday Phoenix, Ghalib, KSF-1D, PACE-1, Painani-II, QMR-KWT, Spartan
Space-Track.org lists 7 unassigned objects, so everything seem to match. Assuming the F9 second stage deorbited before being detected.
-
48950 KSF-1D 2021-059BZ
Not yet identified on Space-track.org: Faraday Phoenix (6U), Ghalib (2U), PACE-1 (6U), Painani-II (3U), QMR-KWT (1U), Spartan (6U)
-
48924 FARADAY_PHOENIX 2021-059AX
Not yet identified on Space-track.org: Ghalib (2U), PACE-1 (6U), Painani-II (3U), QMR-KWT (1U), Spartan (6U)
-
LINCS A/B were deployed from the Surfboard. They are alive but tumbling, activities underway to try and recover them. Mandrake sats are doing good so far, as is the SDA payload on YAM-3. (from Space Symposium press briefing)
(Surfboard deployments don't seem to have a great success rate on these missions for some reason)
-
https://twitter.com/isis_space/status/1431288719823327234
Last week, our team worked with @Marco_Langbroek, from @UniLeidenNews. He has been supporting us in tracking the LED payload of our Napa-2 satellite to capture the LED payload activation from the ground. Thank you, Marco, for the nice pictures!
-
48964 SPARTAN 2021-059CP
Not yet identified on Space-track.org: Ghalib (2U), PACE-1 (6U), Painani-II (3U), QMR-KWT (1U)
-
I might have missed it earlier in this thread but are the three Starlink satellites launched on this mission v1.0 or v1.5?
-
I might have missed it earlier in this thread but are the three Starlink satellites launched on this mission v1.0 or v1.5?
They had laser ISL. Whether they were the actual v1.5 spec or some test configuration I don't know.
-
Yeah, they might have been some kind of hybrid/Frankensatellites. Impossible to say which generation they belonged to, unless SpaceX chimes in.
-
Yeah, they might have been some kind of hybrid/Frankensatellites. Impossible to say which generation they belonged to, unless SpaceX chimes in.
These three satellites were Starlink 3003, 3004 and 3005. The highest Starlink number of known v1.0 satellites was Starlink 2763. So this large gap might hint to a generation change.
-
These three satellites were Starlink 3003, 3004 and 3005. The highest Starlink number of known v1.0 satellites was Starlink 2763. So this large gap might hint to a generation change.
That's what I was thinking, v1.0 satellites are in the 1000s and 2000s while v1.5 satellites are in the 3000s.
-
48962 GHALIB 2021-059CM
48943 QMR-KWT 2021-059BS
Not yet identified on Space-track.org: PACE-1 (6U), Painani-II (3U)
-
https://twitter.com/isis_space/status/1456279180404998149
We've completed the platform commissioning of the #GHALIB satellite, a 2U built, designed and integrated by us, and our customer Marshall Intech has supplied the #RadioFrequency payload. We're now ready to support payload commissioning operations! #CubeSats #pioneerforchange
-
48909 PACE-1 2021-059AG
48928 PAINANI-2 2021-059BB
-
LINCS A/B were deployed from the Surfboard. They are alive but tumbling, activities underway to try and recover them. Mandrake sats are doing good so far, as is the SDA payload on YAM-3. (from Space Symposium press briefing)
(Surfboard deployments don't seem to have a great success rate on these missions for some reason)
Space Development Agency, General Atomics eye options after setback in laser comms experiment (https://spacenews.com/space-development-agency-general-atomics-eye-options-after-setback-in-laser-comms-experiment/)
SDA said in a statement Feb. 4 that there were “challenges communicating with the LINCS sats. However, SDA is still working in partnership with the performer General Atomics on the way ahead.”
[...]
Gregg Burgess, vice president of space systems at General Atomics, said a problem occurred at launch. “Unfortunately, there was an issue with the launch vehicle,” Burgess said on a Mitchell Institute for Aerospace Studies podcast that aired Feb. 5.
I'm assuming "launch vehicle" in this case is the Surfboard aggregator rather than the Falcon 9, but that's just a guess.
-
LINCS A/B were deployed from the Surfboard. They are alive but tumbling, activities underway to try and recover them. Mandrake sats are doing good so far, as is the SDA payload on YAM-3. (from Space Symposium press briefing)
(Surfboard deployments don't seem to have a great success rate on these missions for some reason)
Space Development Agency, General Atomics eye options after setback in laser comms experiment (https://spacenews.com/space-development-agency-general-atomics-eye-options-after-setback-in-laser-comms-experiment/)
SDA said in a statement Feb. 4 that there were “challenges communicating with the LINCS sats. However, SDA is still working in partnership with the performer General Atomics on the way ahead.”
[...]
Gregg Burgess, vice president of space systems at General Atomics, said a problem occurred at launch. “Unfortunately, there was an issue with the launch vehicle,” Burgess said on a Mitchell Institute for Aerospace Studies podcast that aired Feb. 5.
I'm assuming "launch vehicle" in this case is the Surfboard aggregator rather than the Falcon 9, but that's just a guess.
Launch vehicle is Falcon 9. He could be referring to the issue with the high helium concentration for payloads mounted in that area, which some of the passengers don't seem to have realized would be a problem until it was too late.
-
LINCS A/B were deployed from the Surfboard. They are alive but tumbling, activities underway to try and recover them. Mandrake sats are doing good so far, as is the SDA payload on YAM-3. (from Space Symposium press briefing)
(Surfboard deployments don't seem to have a great success rate on these missions for some reason.
Space Development Agency, General Atomics eye options after setback in laser comms experiment (https://spacenews.com/space-development-agency-general-atomics-eye-options-after-setback-in-laser-comms-experiment/)
SDA said in a statement Feb. 4 that there were “challenges communicating with the LINCS sats. However, SDA is still working in partnership with the performer General Atomics on the way ahead.”
[...]
Gregg Burgess, vice president of space systems at General Atomics, said a problem occurred at launch. “Unfortunately, there was an issue with the launch vehicle,” Burgess said on a Mitchell Institute for Aerospace Studies podcast that aired Feb. 5.
I'm assuming "launch vehicle" in this case is the Surfboard aggregator rather than the Falcon 9, but that's just a guess.
Launch vehicle is Falcon 9. He could be referring to the issue with the high helium concentration for payloads mounted in that area, which some of the passengers don't seem to have realized would be a problem until it was too late.
gongora lead me to some posts that explained this thoroughly.
The “Surfboard” cubesat launcher sits on the aft end of Stage 2. As such it inside the interstage, which fills with vented helium at some low partial pressure. The helium diffuses into components, particularly MEMS, which fail at remarkably low levels.
This post from Almoturg links to a marvelous video showing this in great detail.
Apparently some sensors and materials are sensitive to helium in particular. It was noted by some people at the symposium that MEMS sensors can be a problem with helium, and other materials could change properties if saturated with helium.
MEMS oscillators in particular are affected by helium: https://youtu.be/vvzWaVvB908 (https://youtu.be/vvzWaVvB908)
There was a case of a bunch of iPhones in a hospital shutting down when an MRI magnet was cooled down with liquid helium.
Edit: It’s no more “an issue with the launcher” than if the cubesats succumbed to the launch vibration or decompression rate. The helium is in the environmental specifications and the cubesat designers overlooked it. This stuff happens, but it isn’t right to try and shift the blame.
-
Can't help but wonder if over time the Helium will diffuse back out and restore functionality. It is a hard vacuum.
-
Those devices often do restore themselves. Unfortunately if they needed the MEMS devices for things like attitude control and stationkeeping, you might wonder what the software might end up doing if all the IMUs are reading crazy values for a few days.
-
CACI Announces Successful Demonstration of Optical Intersatellite Links in Low Earth Orbit (https://investor.caci.com/news/news-details/2022/CACI-Announces-Successful-Demonstration-of-Optical-Intersatellite-Links-in-Low-Earth-Orbit/default.aspx)
Company Release - 5/17/2022
Industry first for new technology designed to support the National Defense Space Architecture
RESTON, Va.--(BUSINESS WIRE)-- CACI International Inc (NYSE: CACI) announced today it successfully demonstrated space to space optical communications links in low earth orbit (LEO) in partnership with the Defense Advanced Research Projects Agency (DARPA) and the Space Development Agency (SDA) as part of the Mandrake II program.
Mandrake II is a joint risk-reduction program with DARPA, SDA and the Air Force Research Laboratory’s Space Vehicles Directorate (AFRL/RV) to evaluate the pointing, acquisition, and tracking algorithms that allow for optical communication terminals to establish and maintain high-speed communication links in the upcoming Blackjack and SDA Transport and Tracking Layer constellations. This successful test, completed using CACI’s CrossBeam free-space optical terminals, is the first step in establishing more secure, space-based communications networks for defense agencies using more powerful, efficient technology that can transmit more data, faster.
In December 2021, CACI acquired California-based SA Photonics to address a broader market spanning high-end manned flight programs to the proliferated LEO market. The combined companies offer the most advanced photonics engineering and manufacturing capabilities in the U.S. with three major manufacturing facilities in California, Florida, and New Jersey.
John Mengucci, CACI President and Chief Executive Officer, said, “Our national security depends on advanced, secure technology that enables modernized networks and enhanced intelligence systems for our warfighters using small satellites to operate at the speed of relevance. Through the acquisition of SA Photonics, our joint technology and manufacturing capabilities have enabled this successful milestone. In partnership with our mission customers, we are on the path to supporting the contested space domain with faster, more secure satellites.
The Optical InterSatellite Links (OISLs) were established using CrossBeam free-space optical terminals currently on orbit, developed by SA Photonics, with satellites that are specifically aimed at demonstrating and supporting a communication capability for the Department of Defense’s proliferated LEO (p-LEO) National Defense Space Architecture (NDSA).
The CrossBeam OISLs on Mandrake II successfully established an optical link during a 40+ minute test on April 14. The link demonstrated closed loop tracking and data transfer over a 100+ km link distance, with more than 200 gigabits (Gb) of data transmitted and received.
-
SAT-STA-20230810-00200
During the initial portion of this period, Spaceflight actively lowered the altitude of the spacecraft from its deployment altitude of ~522 km to ~445 km and also engaged with NASA to physically coordinate the transit of the Sherpa-LTE1 through the ISS orbit. Spaceflight learned that actively transiting through the ISS orbit would be more complicated and demanding than Spaceflight had anticipated, and Spaceflight would not have on call sufficient operational resources during the transit period to meet NASA standards.
As a result, and consistent with NASA recommendations, Spaceflight has decided not to actively de-orbit Sherpa-LTE1 through the ISS orbit. Instead, the company will allow the spacecraft to passively de-orbit through the ISS orbit down to approximately 410 km....
Once at the 410 km orbital altitude, Spaceflight will commence actively de-orbiting the Sherpa-LTE1 in coordination with NASA.