Firefly Space Systems

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Firefly Space Systems
Industry Aerospace
Founded January 2014 (2014-01)
Hawthorne, California[1]
Founders Tom Markusic
P.J. King[2]
Headquarters Cedar Park, Texas, USA
Key people
Tom Markusic (CEO)
P.J. King (COO)
Michael Blum (CFO)
Shey Sabripour (CTO)
Maureen Gannon (VP BD)
Number of employees
43 (Nov 2014)[3]
Website www.fireflyspace.com

FireFly Space Systems[4][5] is a private aerospace firm based in Austin, Texas, that is developing small and medium-sized launch vehicles for launches to orbit. They are proponents of NewSpace: a movement in the aerospace industry whose objective is to increase access to space through innovative technical advances resulting in a reduction of launch cost, and the lessening of regulations and logistical restrictions associated with dependence on national space institutions.[3]

History

Firefly was formed in January 2014[4] by Dr. Tom Markusic, P.J. King,[2] and a small group of entrepreneurs who self-funded the company. In September 2014, Firefly announced it would move its headquarters from Hawthorne, California to Austin-suburb Cedar Park, Texas.[1] By November it relocated to Texas.[3] It grew to 30 employees by August 2014 and 43 employees by November 2014.[3] Firefly has office and engineering facilities in Austin, Texas and Hawthorne, California and purchased 215 acres (87 ha) of land for an engine test and manufacturing[6] facility in Briggs, Texas, 50 miles (80 km) north of Austin.[7]

Tom Markusic has a background in propulsion engineering, and has worked at other NewSpace companies including SpaceX — where he was manager of the SpaceX Texas Rocket Test Facility — and also held senior posts at Virgin Galactic and Blue Origin.[7] The company name came to Markusic while sitting on his back porch watching fireflies and realizing that in the future the sky above Earth might look like that as spacecraft ferried people to Mars.[3]

FireFly FRE-R1 engine test, September 2015

In 2014, Firefly purchased fiber-winding equipment for manufacturing composite cryotanks that will be built using an out-of-autoclave process. Prototype tanks were tested at Marshall Space Flight Center in mid-2014.[7]

The Firefly Alpha design was revealed in July 2014.[4] As of November 2014 Firefly's objective was to be cash-flow positive by 2018, based on anticipated small-satellite business.[3]

In June 2015, Firefly projected initial engine tests on their Texas test stand by September 2015 and the first full-pressure test of the full-size first-stage test article before year-end 2015. As of June 2015, a suborbital launch of Firefly Alpha was projected to occur no earlier than 2017.[6]

In the event, the first hot fire engine test of the "Firefly Rocket Engine Research 1" (FRE-R1) occurred on 10 September 2015.[8][9]

Firefly has signed an agreement with Space Florida to launch from the Florida "Space Coast". The initial demonstration launch of the Firefly Alpha could be as early as 2016.[10]

Aerospike engine

Firefly proposes to utilize a lightweight annular aerospike rocket engine and self-pressurizing propellant in order to improve the payload fraction delivered to orbit.

The engine is a 'plug cluster aerospike', a type of annular aerospike engine with an array of ten small conventional methane-fueled rockets arranged in a ring, thrusting against a plug-shaped structure. The thrusters’ force against the carefully shaped plug provides an optimal propulsive effect on the launch vehicle, while the open exhaust lets the aerospike engine’s exhaust 'self-tune' against the different ambient pressures that the rocket will experience at increasingly higher altitudes during a terrestrial launch.[3]

File:FireFly Aerospike Engine.png
FireFly Aerospike Engine

Conventionally, rockets use pressurized reserves of an inert gas to 'backfill' propellant tanks, in order to maintain tank pressure as the tank voids. However, the proposed aerospike throttled thrust architecture uses autogenous pressure-fed methane/liquid oxygen propellant. Pressure is maintained by the propellant alone, thus removing the weight requirement, complexity and additional failure modes of inert gas reserves.[3][7]

Firefly cools the truncated spike structure — which impinges the rocket exhaust of the ten surrounding conventional rocket engines — by pumping the liquid methane fuel through the spike, turning the heated fuel into a hot gas, some of which is then used to generate the gas necessary to pressurize the fuel tank. This avoids the traditional means of using helium inert gas for tank pressurization and leaves slightly more burnable fuel in the fuel tank. The plug cluster spike itself is static.[3]

Additionally, methane/liquid oxygen is clean burning with no significant coking,[clarification needed] thereby reducing the need for engine refurbishment between firings. This allows each stage to be reused, if recovered in a serviceable condition, resulting in further cost savings on subsequent flights. Methane produces slightly higher Isp and is also relatively inexpensive compared to more conventional RP-1 (kerosene) .[11]

Launch vehicles

Firefly is working on a number of design concepts within their overall vehicle architecture. As of June 2015, FireFly continues to do a large number of design trades.[6] The approximate characteristics of the conceptual launch vehicles are:

Firefly Alpha

The FireFly Alpha (Firefly α[3]) is an expendable[6] launch vehicle designed to carry light — approximately 400 kilograms (880 lb) — satellites to orbit. Projected launch cost is $9 million for orbital payloads.[7]

It utilizes the FRE-1/FRE-2 aerospike engines and a lightweight carbon composite structure to reduce launch weight, resulting in improved payload fraction.[3]

Technical description and specifications

FireFly Alpha
Performance
  • Payload / 400 kilograms (880 lb) (LEO, un-margined)[7][12]
Propulsion
Stage 1
Stage 2
  • Engine / FRE-1
  • Propellant / LOX / methane[7]
  • Type / Pressure-fed (autogenous), with pintle injector[7]
  • Configuration / Conventional bell[citation needed]
  • Thrust (vac) / 44 kilonewtons (10,000 lbf)[13]
  • Isp (vac) / 335 sec[13]
  • Thrust chambers on FRE-1 and FRE-2 are identical.[6]
Structures

Firefly Beta

Firefly β (Beta) is planned to be a multicore design, grouping α (Alpha) rockets together as a group.[3] As with Alpha, it is expected to be an expendable launch vehicle.[6]

Technical description and specifications

Performance
  • Payload / 1,100 kilograms (2,400 lb)[3]

Production

Firefly is building and testing its engines at a single location in Texas, approximately 20-minutes from company headquarters, in Cedar Park, Texas. Company design and procurement strategy intends to avoid the "large outsourced supplier structure" common in traditional aerospace companies, although a subcontractor will build the carbon-fiber rocket bodies and tanks.[3]

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 https://www.youtube.com/watch?v=FbntJeYQvqg
  3. 3.00 3.01 3.02 3.03 3.04 3.05 3.06 3.07 3.08 3.09 3.10 3.11 3.12 3.13 3.14 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 6.3 6.4 6.5 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.00 7.01 7.02 7.03 7.04 7.05 7.06 7.07 7.08 7.09 7.10 Lua error in package.lua at line 80: module 'strict' not found.
  8. First Rocket Engine Test a Success for Firefly Space Systems, press release, 10 September 2015, accessed 17 December 2015.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. New Alpha rocket will launch test flights from KSC, Florida Today, 15 October 2015, accessed 17 December 2015.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 13.2 13.3 13.4 13.5 13.6 Lua error in package.lua at line 80: module 'strict' not found.

External links