| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 27 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 40:18:09 |
| Calls: | 631 |
| Calls today: | 2 |
| Files: | 1,187 |
| D/L today: |
24 files (29,813K bytes) |
| Messages: | 174,391 |
SapceX decided things weren't quite right, and after using a bit of
hold time to thump on things (figuratively speaking), kept Flight 8
unflown.
Elon expects a destack.
This dress rehearsal was going to be the quickest yet launch after
stacking. The extra since Wednesday^W Friday was spent finishing some
of the deharmonizing work on the ship's tail end, it seems, following
the long static fire of S34 and the the update on Flight 7's RUD.
SapceX decided things weren't quite right, and after using a bit of hold time
to thump on things (figuratively speaking), kept Flight 8 unflown.
Elon expects a destack.
This dress rehearsal was going to be the quickest yet launch after stacking.
The extra since Wednesday^W Friday was spent finishing some of the deharmonizing work on the ship's tail end, it seems, following the long static fire of S34 and the the update on Flight 7's RUD.
/dps
Snidely wrote on 3/3/2025 :
SapceX decided things weren't quite right, and after using a bit of hold
time to thump on things (figuratively speaking), kept Flight 8 unflown.
Elon expects a destack.
This dress rehearsal was going to be the quickest yet launch after
stacking. The extra since Wednesday^W Friday was spent finishing some of >> the deharmonizing work on the ship's tail end, it seems, following the long >> static fire of S34 and the the update on Flight 7's RUD.
/dps
Current diagnosis is GSE leaks. New launch time set at 1730 CST Wed Mar 5.
On 04/03/2025 03:44 Snidely <snidely.too@gmail.com> wrote:
SapceX decided things weren't quite right, and after using a bit of
hold time to thump on things (figuratively speaking), kept Flight 8
unflown.
Elon expects a destack.
This dress rehearsal was going to be the quickest yet launch after
stacking. The extra since Wednesday^W Friday was spent finishing some
of the deharmonizing work on the ship's tail end, it seems, following
the long static fire of S34 and the the update on Flight 7's RUD.
It's obvious SpaceX can't afford another RUD of Starship. The development
is costing much more time than they initially expected and NASA is continually breathing down their necks to make Artemis 3 a reality.
on 3/4/2025, The Running Man supposed :
On 04/03/2025 03:44 Snidely <snidely.too@gmail.com> wrote:
SapceX decided things weren't quite right, and after using a bit of
hold time to thump on things (figuratively speaking), kept Flight 8
unflown.
Elon expects a destack.
This dress rehearsal was going to be the quickest yet launch after
stacking.-a The extra since Wednesday^W Friday was spent finishing
some of the deharmonizing work on the ship's tail end, it seems,
following the long static fire of S34 and the the update on Flight
7's RUD.
It's obvious SpaceX can't afford another RUD of Starship. The development
is costing much more time than they initially expected and NASA is
continually breathing down their necks to make Artemis 3 a reality.
Well, they caught a booster, but they lost the ship, with some of it
visible from the Palm Beach area.
/dps
On 2025-03-06 7:16 p.m., Snidely wrote:
on 3/4/2025, The Running Man supposed :
On 04/03/2025 03:44 Snidely <snidely.too@gmail.com> wrote:
SapceX decided things weren't quite right, and after using a bit of
hold time to thump on things (figuratively speaking), kept Flight 8
unflown.
Elon expects a destack.
This dress rehearsal was going to be the quickest yet launch after
stacking.-a The extra since Wednesday^W Friday was spent finishing
some of the deharmonizing work on the ship's tail end, it seems,
following the long static fire of S34 and the the update on Flight
7's RUD.
It's obvious SpaceX can't afford another RUD of Starship. The development >>> is costing much more time than they initially expected and NASA is
continually breathing down their necks to make Artemis 3 a reality.
Well, they caught a booster, but they lost the ship, with some of it
visible from the Palm Beach area.
/dps
Not very different from the previous flight.
On 07/03/2025 01:35 Alain Fournier <alain245@videotron.ca> wrote:
On 2025-03-06 7:16 p.m., Snidely wrote:
on 3/4/2025, The Running Man supposed :
On 04/03/2025 03:44 Snidely <snidely.too@gmail.com> wrote:
SapceX decided things weren't quite right, and after using a bit of >>>>> hold time to thump on things (figuratively speaking), kept Flight 8 >>>>> unflown.
Elon expects a destack.
This dress rehearsal was going to be the quickest yet launch after
stacking.a The extra since Wednesday^W Friday was spent finishing
some of the deharmonizing work on the ship's tail end, it seems,
following the long static fire of S34 and the the update on Flight
7's RUD.
It's obvious SpaceX can't afford another RUD of Starship. The development >>>> is costing much more time than they initially expected and NASA is
continually breathing down their necks to make Artemis 3 a reality.
Well, they caught a booster, but they lost the ship, with some of it
visible from the Palm Beach area.
/dps
Not very different from the previous flight.
No progress made. Modification didn't work as planned.