Recommended Posts

https://twitter.com/larsblackmore/status/503047574710804480

This seems to confirm, that the stage won't land on a barge, so probably no landing legs

I think the barge? landing attempts were scheduled for flights 14/15, so after the next CRS flight.

Judging from the video, you can clearly see the rocket pitch over before the inflight restart. Which makes me think it is either an actuator with the engines or the fins that got stuck. I find it hard to believe that it was an actual engine problem with over 60 Merlin's launched so far.

Basically a blocked sensor port, a harsh test regime to push the flight envelope, and a less constrained software (to allow such maneuvers) than production F9 launchers.

This sometimes happens at the bleeding edge of aerospace testing.

Garrett Reisman of SpaceX gave a presentation to the Future In-Space Operations (FISO) Working Group on August 27. Some interesting stuff....

Q: What can you tell us about the Texas incident?

A: The test was of our three engine variant of Grasshopper, what we call F-9R Dev. It looks like it was a single point failure that existed on that test article, but does not exist on the Falcon 9. We think it was a failure of a single sensor. Falcon 9 has multiple sensors that its algorithm uses, so the same failure on Falcon 9 would not effect the mission in any way. The fact that Falcon 9 had nine engines, even if it had eight engines it could overcome this issue.

We've been taking a lot of risks with Grasshopper. We're flying this in flight regimes and conops that it was not designed for in an effort to learn. One of those risks bit us. One of the single point failures failed which we knew was a possibility. The failure was such that the flight control could not maintain the lateral boundries of its safety zone and so the flight was terminated intentionally upon exceeding that lateral boundry. That's the most we considered definitively right now.

There was no explosive termination device. Instead, the flight termination sequence is thrust termination combined with some valves that are opened. That caused the destructive sequence you saw. There are populated areas not too far away. We also have our own property and infrastructure that we're trying to protect. We set a certain bound and if we exceed that bound either laterally or vertically then the flight computer initiates the sequence that occurred.

Someone at SpaceX said they may try. It depends on how the conversion of Vandenberg SLC-4W from Titan II launch pad to multiple landing pads goes, which has begun, and if the stage breaks up after Dragon V2 bugs out.

Speculation: They're keeping the details close, which makes me think they're working on making the first stage survivable from some launch aborts. That may be the envelope expansion Dev-1 was probing, but ran out of capabilities which the full F9 has.

We'll see.

It's quite possible. NASA has urgent payloads on CRS-4, space suit batteries and other things. A delay could mess with ISS ops and ripple down the Visiting Vehicle schedule.

Because of this CRS-4 may use AsiaSat 6's F9, meaning no landing legs.

Maxime Puteaux of Euroconsult tweeted about F9R Dev-2,

https://twitter.com/maximeputeaux/status/509365783664005120

@maximeputeaux

@SpaceX COO next Falcon9R shall be delivered within 2 months for testing and the sent to New Mexico to fly #WSBW2014 pic.twitter.com/aj8Tl14yzR

This flight has cargo ISS needs NOW - the 2 space suit batteries needed for a critical spacewalk. The last thing they need is distractions for tests that can better be done with a legged launcher.

They're also going to have F9R Dev-2 ready for initial tests at McGregor in a few weeks, then it goes to SPA for reuse tests..

FloatingFatMan, on 15 Sept 2014 - 16:15, said:

Better in this instance to prove fast turnaround capability and get that gear to the ISS.

Can we call this a fast turn around?  They aren't reusing anything correct?  Fast turn around on the employees part I guess, not on the equipment.

Can we call this a fast turn around? They aren't reusing anything correct? Fast turn around on the employees part I guess, not on the equipment.

Fast turnaround of the pad and crew for consecutive launches, one of the fastest in KSC history.

  • Like 1
  • 2 weeks later...

OK kiddies, now it can be reported that F9R Dev-2 is on the McGregor stage test stand being qualified for flights. Been there for several days.

No idea what the test schedule will be. She may do a few short test hops at McGregor then go to SpacePort America in New Mexico, or she may go straight there. Time will tell.

  • Like 1

It may only be a single hop to test its systems, then off to SPA.

Given this one came off the line and will use production engines, it should have the redundant systems that would have saved F9R Dev-1.

(F9R Dev-1 used a qualification tank and preproduction Merlin 1D's which lacked redundant sensors)

The launch pad at SLC-4E needed a lot of fixing after the CASSIOPE launch. The structural engineers misunderestimated just how big a blast that big, white 224 foot blowtorch would cause. Wicked acoustics.

They lost a lot of plumbing, infrastructure and for certain many of the microphones anywhere near it. Lots of upgrades needed so it wouldn't happen again, especially with Falcon Heavy. Those changes had to be incorporated into the rest of their F9R & FH launch pad designs, and the new F9R / FH test stand at McGregor..

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!