Author Topic: STS-124: Rollout and Pad Flow Latest (Read 90470 times)

Chris Bergin · « **Reply #80 on:** 05/08/2008 03:12 pm »

Paul, thanks for sharing. The jealousy stats on this thread are through the roof

TDCT started, we'll keep an eye on it, though it's usually always by the book.

Chris Bergin · « **Reply #81 on:** 05/08/2008 09:25 pm »

From USA:

STS-124 has the fewest maintenance issues before launch than any other shuttle in program history.
It's the most complex vehicle ever built, so engineers routinely tackle hundreds of processing issues before launch. But STS-124 only has 40 issues to date, the lowest number in 27 years of shuttle flights.

To put that in perspective, during the return to flight mission three years ago, there were 473 processing issues that engineers tackled before launch. Last year, engineers worked on 145 issues with Atlantis before its mission in June.
Until now, the lowest ever number of issues was Discovery's launch to the space station in August 2001 which only had 76 problems reported during launch.

United Space Alliance's Program Manager for Ground Operations, Mark Nappi said "The reason the shuttle has fewer maintenance issues is a lot of hard work that has gone into making the hardware, processes, and software better along with a little bit of luck. We are seeing it across the board on all processing. We've made a lot of ground on fixing recurring issues and enhanced the hardware so fewer issues occur."

Namechange User · « **Reply #82 on:** 05/09/2008 01:58 am »

Quote

Chris Bergin - 8/5/2008 4:25 PM

From USA:

United Space Alliance's Program Manager for Ground Operations, Mark Nappi said "The reason the shuttle has fewer maintenance issues is a lot of hard work that has gone into making the hardware, processes, and software better along with a little bit of luck. We are seeing it across the board on all processing. We've made a lot of ground on fixing recurring issues and enhanced the hardware so fewer issues occur."

Mark is correct but I also think it has a lot to do with the fact we have kind of hit our stride again with flows and launches. The vehicles always seem to perform best when they fly as often as possible. There is a lesson to be learned here for discussions that are taking place on within the agency and being discussed on L2.

SimonShuttle · « **Reply #83 on:** 05/09/2008 09:31 am »

That's really good for them to make a point about it. Normally it's just the articles on this site that makes any reference to the good work in the flow.

Chris Bergin · « **Reply #84 on:** 05/10/2008 07:55 am »

On schedule for PLBD closure in three hours (ref: Don't want any of those bendy hoses that don't go back into their boxes).

cb6785 · « **Reply #85 on:** 05/10/2008 01:45 pm »

Anyone knows when the STS-124 Press Kit will be online?

Chris Bergin · « **Reply #86 on:** 05/10/2008 04:06 pm »

Payload Bay Doors closed, no issues. Writing up where things stand shortly.

Chris Bergin · « **Reply #87 on:** 05/12/2008 05:48 am »

Not expecting any concerns for the first FRR this week (article based on the previous flight's IFAs...and any related constriants):

http://www.nasaspaceflight.com/content/?cid=5421

Ford Mustang · « **Reply #88 on:** 05/12/2008 05:05 pm »

Pictures of Discovery's Payload Bay Doors closing have been uploaded to the Kennedy Media Gallery.

Chris Bergin · « **Reply #89 on:** 05/12/2008 05:17 pm »

Usual for after the Agency FRR next Monday:

NASA Announces News Conference on Status of Next Shuttle Launch

CAPE CANAVERAL, Fla., May 12 /PRNewswire-USNewswire/ -- NASA managers have scheduled a news conference at the Kennedy Space Center in Florida for no earlier than 4 p.m. EDT on Monday, May 19, to discuss the status of the next space shuttle launch. The news conference will begin after the conclusion of the Flight Readiness Review, a meeting to assess preparations for shuttle Discovery's STS-124 mission to the International Space Station.

The review is expected to include the selection of an official launch date. Discovery is targeted to launch May 31 at 5:02 p.m.

The briefing participants are:
- Associate Administrator for Space Operations Bill Gerstenmaier
- Space Shuttle Program Manager John Shannon
- International Space Station Program Manager Mike Suffredini
- STS-124 Assistant Launch Director Ed Mango

Chris Bergin · « **Reply #90 on:** 05/12/2008 06:09 pm »

Rev. A; May 12, 2008

STS-124 COUNTDOWN HIGHLIGHTS (countdown events are
targeted for the in-plane, or, preferred launch time of 4:02pm CDT on
May 31; all times are CDT)

Wednesday, May 28:
8:00am….Crew departs Ellington Field, Houston via Shuttle Training
Aircraft for the Shuttle Landing Facility at the Kennedy Space Center
11:00am...Crew arrives at the Shuttle Landing Facility at the Kennedy
Space Center and makes statements for the media
1:15pm….Crew checks its launch and entry suits and reviews its flight data file
2:00pm….Countdown begins at the T-43 hour mark
5:45pm….Kelly and Ham conduct a suited Shuttle Training Aircraft flight
9:30pm….Crew sleep begins

Thursday, May 29:
5:30am.…Crew wake up
6:00am.…Countdown enters a 4-hour built-in hold at the T-27 hour mark
6:30am….Crew conducts medical exams
8:00am….The crew conducts T-38 training jet flights; Mission
Management Team (MMT) meets at KSC to review Discovery's readiness for
launch
10:00am...Countdown resumes at the T-27 hour mark with the PRSD
loading of liquid hydrogen and liquid oxygen into Discovery's three
power-producing fuel cells
6:00pm.…Countdown enters a 8-hour built-in hold at the T-19-hour mark;
OMBUU securing begins
7:45pm….Kelly and Ham conduct an unsuited Shuttle Training Aircraft flight
9:30pm….Crew sleep begins

Friday, May 30:
2:00am….Countdown resumes at the T-19 hour mark
5:30am.…Crew wake up
10:00am…Countdown enters a 13-hour, 37-minute built-in hold at the
T-11 hour mark
11:15am…Astronauts receive payload, systems and weather briefing from
the Ascent Team of flight controllers at Mission Control, Houston
2:30pm….Comm activation begins
7:30pm….RSS retraction
9:30pm….Crew sleep begins
11:37pm…Countdown resumes at the T-11 hour mark

erioladastra · « **Reply #91 on:** 05/13/2008 02:39 am »

"Not expecting any concerns for the first FRR this week "

Except the Soyuz problem is still gaining momentum and is an ever growing concern for launching on time.

rdale · « **Reply #92 on:** 05/13/2008 04:41 am »

Fill us in - how would the Soyuz issue delay launch? Everything publicly says that the Russian report will take months to complete - are you talking about that long of a hold on 124?

DaveS · « **Reply #93 on:** 05/13/2008 09:44 am »

Quote

rdale - 13/5/2008 6:41 AM

Fill us in - how would the Soyuz issue delay launch? Everything publicly says that the Russian report will take months to complete - are you talking about that long of a hold on 124?

It's probably due to Chamitoff, remember he's only an up passenger while the down passenger is Reisman. I guess they don't want to launch Chamitoff as his only ride down after Discovery leaves is the Soyuz which may or may not be safe anymore.

If it is workmanship problem that led to two most recent ballistical entries, then who knows what other problems that TMA up there might have besides a potential of a ballistical entry.

This also comes at a rather bad time as the Russians are supposed to ramp up the Soyuz production and if they can't handle the current production rate, then the 6-person ISS crew capability is danger.

So it all comes down to basically to a STS-51L situation: Knowing full well that the flight might end tragically and launching despite of it or standing down until you get data that tells you otherwise, that it is safe to launch.

I guess they're leaning against the latter for now.

Chris Bergin · « **Reply #94 on:** 05/13/2008 09:46 am »

Quote

erioladastra - 13/5/2008 3:39 AM

"Not expecting any concerns for the first FRR this week "

Except the Soyuz problem is still gaining momentum and is an ever growing concern for launching on time.

Wouldn't that be more the SOMD/Agency FRR next Monday? Made the above comment in relation to the SSP FRR, as in the vehicle's looking good.

Regardless, didn't know the Soyuz issue had potential of getting in the way of 124's launch date!

ANDY_WALLACEGROVE · « **Reply #95 on:** 05/13/2008 12:24 pm »

Chris,
I guess I had read the 8th floor update.

....as meaning Soyuz could be a barrier to launch. But that may have been a too literal assumption.

Chris Bergin · « **Reply #96 on:** 05/13/2008 01:00 pm »

In which case it's relating to a multiple serious emergancy. One where they need to evac the station, and the orbiter is also out of action.

John2375 · « **Reply #97 on:** 05/13/2008 05:20 pm »

Clearly they need to retain the shuttle's services for even 2 launches a year, to rotate crews, until Ares is ready.
I know the funding isn't there; They need to GET the funding then. Retire Atlantis as planned, or an orbiter of your choosing, to use as spare-parts for the other two if needed. Launch 2 flights/year for crew rotation until not needed anymore. This 'deadline' is killing them.

Chris Bergin · « **Reply #98 on:** 05/13/2008 05:38 pm »

Back on topic. A GPC split this morning appears to be related to a faulty MDM FA2 card. S0024 Operations haulted, card R&R then re-test.

psloss · « **Reply #99 on:** 05/13/2008 05:40 pm »

Quote

John2375 - 13/5/2008 1:20 PM

Clearly they need to retain the shuttle's services for even 2 launches a year, to rotate crews, until Ares is ready.

You still need a Soyuz at the station. The shuttle orbiters don't stay long enough and their visits don't overlap like Soyuz. Without the Soyuz, everyone would have to leave with the shuttle.