Updates Orbital Sciences' Cygnus CRS Flight 1 through Flight 8 updates.

[boogabooga]

Here is the ULA press release:

http://www.ulalaunch.com/ula-signs-contract-with-orbital-sciences.aspx

Interestingly enough, despite all the politics and push for "commercial" spaceflight, it looks like the Atlas V continues to be America's go-to launch vehicle.

 

[Cosmic Penguin]

Uh, what rumor? That article was about secondary payloads on Antares switching providers from Orbital, not Cygnus launching on a Falcon 9. The decision for Orbital to purchase an Atlas V was pretty predictable.

My bad - that's what happen when you are reading at 4 am..... :facepalm:

However at least 2 sources (including here) once reported that SpaceX was in the lead to get the 2 contracts. :shifty:

 

[boogabooga]

Well this rumor turns out to be untrue - Cygnus CRS-4 will instead launch on an Atlas V 401 in 4Q 2015! :hotcool:

According to Orbital the use of the Atlas V will mean that CRS-4 can carry 30% more cargo than the originally planned cargo for CRS-4 and CRS-5 combined (=what they planned to fly in 2015)! Afterwards "Antares II" will come back to Wallops for a hot firing in late 2015 with RTF in 1Q 2016 on CRS-5 (which could be moved to a 2nd Atlas V if Antares II falls behind schedule).

The new 1st stage engines (rumored to be the RD-193 engine derived from Atlas V's RD-180 and Angara's RD-191) means that "Antares II" will provide 20% more cargo capability on the Cygnus than on the original Antares 130 series, which means that Orbital can cut 1 of its 8 CRS flights and still be able to finish the contract (with CRS-5 in 1Q 2016, CRS-6 in 2Q 2016 and CRS-7 in 4Q 2016).

And....of course I have already made an Atlas V/Cygnus launch scenario! (requires LRO, Cygnus/Antares and ISS AtoZ add-ons, plus the configuration files attached below that should be put in the /Config/Beta directory)

BEGIN_DESC
Atlas V contingency flight launching a Cygnus logistics craft to the ISS at 18:21 UTC. Press P for autopilot at T-10 sec.
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 57147.725
END_ENVIRONMENT

BEGIN_FOCUS
  AtlasV_Cygnus
END_FOCUS

BEGIN_CAMERA
  TARGET AtlasV_Cygnus
  MODE Extern
  POS 5.62 -86.04 52.84
  TRACKMODE TargetRelative
  FOV 40.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE Surface
  SPDMODE 1
END_MFD

BEGIN_MFD Right
  TARGET AtlasV_Cygnus
  MODE Extern
  POS 5.62 -86.04 52.84
  TRACKMODE Ground Earth
  GROUNDLOCATION -80.58341 28.58224 15.92
  FOV 40.00
END_MFD

BEGIN_SHIPS
ISS:ProjectAlpha_ISS
  STATUS Orbiting Earth
  RPOS 1352306.82 2068948.73 6318518.70
  RVEL -6794.811 3541.516 288.853
  AROT 100.26 45.81 167.82
  VROT -0.06 0.00 0.00
  AFCMODE 7
  PRPLEVEL 0:1.000000
  IDS 0:588 10 1:586 10 2:584 10 3:582 10 4:580 10
  NAVFREQ 0 0
  XPDR 466
END
AtlasV_Cygnus:Vessels/LRO/AV020
  STATUS Landed Earth
  POS -80.5828310 28.5834560
  HEADING 100
  FUEL 1.000
  CONFIG_FILE Config\Beta\AtlasV_Cygnus.ini
  GUIDANCE_FILE Config\Beta\AV_guidance_ISS.txt
  CONFIGURATION 0
  CURRENT_BOOSTER 1
  CURRENT_STAGE 1
  CURRENT_PAYLOAD 1
  FAIRING 1
END
LC41:Vessels/B_SLC41/b_slc41
  STATUS Landed Earth
  POS -80.5828310 28.5834560
  HEADING 180.00
  PRPLEVEL 0:1.000
  THLEVEL 0:1.000 3:1.000
  NAVFREQ 0 0
  UMB 0 0.0000
END
END_SHIPS

I tried this out. It seems that "av_fair_1.msh" and "av_fair_2.msh" are not a part of the LRO add-on, or any of BrianJ's other add-ons. Rather, all of BrianJ's fairing meshes are mission specific, with logo (BrianJ having an exceptional attention to detail). I substituted in the LRO fairing meshes, but if you have AtlasV blank fairing meshes, would you mind sharing.

Also, I think the guidance file needs to be tweaked. I re-entered before reaching orbit. However, I know that multistage guidance can be a little, er, inconsistent, so I would believe that it worked for you.

Edit:
Okay, I tweaked the AtlasV guidance file for Cygnus. I use the first stage to get a higher apogee. Then, the Centaur does not need to be pitched up so much during its LONG burn.

This should put one in a low-eccentricity orbit (~370 x 350 km) just under the ISS altitude. Catch-up for rendezvous will take a few days.

-10=PlaySound(Sound\Vessel\countdown1.wav)
-2=engine(0,100,2)
0=engine(100,100,1)
13.9=roll(3,89.5,42.8,89.2,1)
20=pitch(89.2, 89.48, 10.0)
30=pitch(89.48, 86.29, 10.0)
40=pitch(86.29, 82.98, 10.0)
50=pitch(82.98, 79.02, 10.0)
60=pitch(79.02, 73.16, 10.0)
70=pitch(73.16, 67.46, 10.0)
80=pitch(67.46, 60.99, 10.0)
90=pitch(60.99, 54.92, 10.0)
100=pitch(54.92, 48.13, 10.0)
110=pitch(48.13, 41.47, 10.0)
120=pitch(41.47, 36.14, 10.0)
130=pitch(36.14, 31.57, 10.0)
140=pitch(31.57, 28.28, 10.0)
150=pitch(28,28, 28.28, 110)
220=engine(100, 70, 15)
258=fairing()
260=pitch(28.28, 18.70, 10.0)
270=pitch(18.70, 18.3, 10.0)
280=pitch(18.3, 18.3, 680.0)
952=engine(100, 0, 1)
953=engine(0, 0, 1)
960=pitch(18.3, 18.3, 5)

 

[orbitingpluto]

To put Antares in motion again, Orbital buys RD-181s

Related Russian Space Web article: the RD-193 engine
http://www.russianspaceweb.com/rd193.html

 

[Kyle]

I'm not surprised by that, OSC had been pursuing RD-181 as an alternative even before Orb-3 spontaneously disassembled itself after launch.

 

[Cosmic Penguin]

I tried this out. It seems that "av_fair_1.msh" and "av_fair_2.msh" are not a part of the LRO add-on, or any of BrianJ's other add-ons. Rather, all of BrianJ's fairing meshes are mission specific, with logo (BrianJ having an exceptional attention to detail). I substituted in the LRO fairing meshes, but if you have AtlasV blank fairing meshes, would you mind sharing.

Also, I think the guidance file needs to be tweaked. I re-entered before reaching orbit. However, I know that multistage guidance can be a little, er, inconsistent, so I would believe that it worked for you.

Edit:
Okay, I tweaked the AtlasV guidance file for Cygnus. I use the first stage to get a higher apogee. Then, the Centaur does not need to be pitched up so much during its LONG burn.

This should put one in a low-eccentricity orbit (~370 x 350 km) just under the ISS altitude. Catch-up for rendezvous will take a few days.

-10=PlaySound(Sound\Vessel\countdown1.wav)
-2=engine(0,100,2)
0=engine(100,100,1)
13.9=roll(3,89.5,42.8,89.2,1)
20=pitch(89.2, 89.48, 10.0)
30=pitch(89.48, 86.29, 10.0)
40=pitch(86.29, 82.98, 10.0)
50=pitch(82.98, 79.02, 10.0)
60=pitch(79.02, 73.16, 10.0)
70=pitch(73.16, 67.46, 10.0)
80=pitch(67.46, 60.99, 10.0)
90=pitch(60.99, 54.92, 10.0)
100=pitch(54.92, 48.13, 10.0)
110=pitch(48.13, 41.47, 10.0)
120=pitch(41.47, 36.14, 10.0)
130=pitch(36.14, 31.57, 10.0)
140=pitch(31.57, 28.28, 10.0)
150=pitch(28,28, 28.28, 110)
220=engine(100, 70, 15)
258=fairing()
260=pitch(28.28, 18.70, 10.0)
270=pitch(18.70, 18.3, 10.0)
280=pitch(18.3, 18.3, 680.0)
952=engine(100, 0, 1)
953=engine(0, 0, 1)
960=pitch(18.3, 18.3, 5)

Oops, I think I forgotten to attach these two files that should be in the "Meshes/Beta" file. They are included in the zip-file below. :facepalm:

 

[orbitingpluto]

The deal to buy RD-181s has been signed, according to Energia PR. First delivery could be as early as June of this year.

 

[GLS]

Exclusive: Orbital explosion probe said to find debris in engine: sources

http://www.reuters.com/article/2015/02/20/us-orbital-atk-gencorp-explosion-idUSKBN0LO28P20150220

If that's true, new engines will not change anything.

 

[Astro SG Wise]

Exclusive: Orbital explosion probe said to find debris in engine: sources If that's true, new engines will not change anything.

Man, I was about to celebrate :sweet:. So you are saying the fuel tank was to blame :facepalm:?

 

[GLS]

Not the first time this happens to this engine, if I remember well the 2º N1 also had this "foreign object debris" problem. Unlucky engine.

 

[Cosmic Penguin]

Exclusive: Orbital explosion probe said to find debris in engine: sources

http://www.reuters.com/article/2015/02/20/us-orbital-atk-gencorp-explosion-idUSKBN0LO28P20150220

If that's true, new engines will not change anything.

Keep in mind that the article stated that FOD in engine is only one of "about half dozen" causes that they are studying, and actually this is one of the "less likely" causes.

Don't make any conclusions until the final report is out....

 

[C3PO]

Keep in mind that the article stated that FOD in engine is only one of "about half dozen" causes that they are studying, and actually this is one of the "less likely" causes.

Don't make any conclusions until the final report is out....

I thought this was the most interesting part.

One of the sources familiar with the probe said investigators found particles of a crystallized desiccant, or drying agent, in the turbo pump and other parts of the AJ-26 engine.

It has to come from somewhere and FOD sounds very likely to me. That is if the source is reliable. But I agree that we need to wait for the report.

 

[GLS]

Keep in mind that the article stated that FOD in engine is only one of "about half dozen" causes that they are studying, and actually this is one of the "less likely" causes.

Don't make any conclusions until the final report is out....

I'm not making any conclusions... I just said "if this is true...":hello:

 

[orbitingpluto]

Problem in the Turbopump is said to be the most likely cause of the Antares Launch Failure

Specifically 'excessive' wear of the bearings in the turbopump, allowing the spinning and non-spinning parts to collide.

Course, while this was spoken by the President for Flight Systems at Orbital, it was at a panel at the Space Symposium, and the final report isn't out yet.

 

[orbitingpluto]

More info about Orbital ATK's reengined Antares and the effects of the October accident(excerpts from a article about the company as a whole):

The company said it is on track to start launches of its Antares rocket — whose October failure accelerated Orbital’s plans to replace the rocket’s Russian-made main engine — with a new Russian engine in March.

In a conference call with investors, Orbital Chief Executive David W. Thompson said the new RD-181 engine from Russia’s Energomash has successfully conducted seven certification firings, “all of which went as expected.”

The first two flight models — two are used for each Antares main stage — are now in final tests and will be delivered to Orbital in early July. Engine-related modifications to the Antares first stage are on schedule, he said, and post-failure repairs to the Mid-Atlantic Regional Spaceport at NASA’s Wallops Flight Facility in Wallops Island, Virginia, are on track for completion in September.

Thompson did not address whether the company would need to invest its own funds to complete the repairs.

Full system tests of the re-engined Antares would be conducted late this year and into January under the current schedule, with a late-March inaugural flight. Orbital has said that it likely will proceed directly with the launch of a cargo capsule to the International Space Station under its Commercial Resupply Services (CRS) contract with NASA without conducting a demonstration flight.

Thompson said the late-March flight schedule includes one month of schedule margin, meaning unforeseen delays in the program could slow progress by up to a month without affecting the March date.

Orbital apparently has felt little or no pressure from the U.S. Congress about its choice of a Russian engine, despite congressional demand that United Launch Alliance of Denver phase out its use of a Russian engine to power the company’s Atlas 5 rocket, which launches U.S. military payloads.

Thompson said the company has not yet revised its expected CRS operating profit forecast but may revise it upward later this year. Orbital has said the October failure, which destroyed a Cygnus space station cargo freighter, will have no material effect on CRS profitability or revenue because from now on it will be launching larger Cygnus cargo modules, allowing it to fulfill its CRS contract obligation — measured in delivered kilograms — with fewer launches.

 

[Cosmic Penguin]

Finally some updates from Orbital ATK!

- The cargo compartment for the CRS-4 Cygnus (first "extended Cygnus" with a longer cargo compartment and circular solar arrays) is now at the Cape, with the service module now in final testing ahead of launch on December 3. Thanks to the capabilities of the Atlas V, this Cygnus will fly more than 3.5 tonnes of cargo, 25% more than the specifications of the usual "extended Cygnus"!

- The existing Antares rockets are now being converted into the 200 series with the first RD-181 engines (derived from Angara's RD-191) now being installed onto the 1st stages stuck at Wallops. The repairs to Wallops pad 0A is almost complete with the first Antares 200 series hot fire test coming as early as late this year, ahead of their first flight next spring.

- However due to flexibilities problems with their launch schedule (probably because their CRS competitor also knocked out of the ISS supply line till late in the year) OATK is now looking at ordering a second Atlas V flight for one of their 2016 Cygnus flights.

 

[Kyle]

Also worth noting they're renaming ORB-4 to OA-4, as in Orbital-ATK.

---------- Post added at 03:49 AM ---------- Previous post was at 03:44 AM ----------

Cool picture of the upgraded Cygnus!

 

[Donamy]

Does anyone know if these new panels will track ?

 

[Kyle]

Good question, I'll look around NSF.com and see what I can find.

 

[boogabooga]

https://www.orbitalatk.com/space-sy...ar-arrays/docs/FS007_15_OA_3862 UltraFlex.pdf

?