Firefly Alpha Payload User's Guide April 2018
Firefly Alpha Payload User's Guide April 2018
Overview
The goal of the Firefly Payload User’s Guide is to provide summary information for preliminary
mission planning for Payload Customers. The contents found herein are not intended to be
mission specific and are subject to change. Firefly welcomes detailed design data such as payload-
specific requirements and interfaces, and operational plans once a Launch Service Agreement is
in place.
Contact Firefly
Please contact Firefly Aerospace Launch Services with inquiries into the suitability of the launch
vehicle for your mission.
Copies of this Firefly Payload User’s Guide may be obtained from the Firefly website at the link
above. Hard copies are also available upon request.
Contents
1 Introduction ......................................................................................................................... 3
1.1 Firefly’s History ............................................................................................................................... 4
2 Vehicle Overview.................................................................................................................. 5
2.1 Alpha Architecture ......................................................................................................................... 6
2.2 Beta Architecture ......................................................................................................................... 12
2.3 Launch Services............................................................................................................................. 17
2.4 The Firefly Advantage ................................................................................................................... 19
6 Facilities ............................................................................................................................. 48
6.1 Headquarters & Mission Control Center ..................................................................................... 48
6.2 Test Site ........................................................................................................................................ 48
6.3 Launch Site.................................................................................................................................... 49
7 Safety................................................................................................................................. 52
7.1 Safety Requirements..................................................................................................................... 52
1 Introduction
Welcome to the Payload User’s Guide for the Firefly launch vehicles - we’re glad you’re here!
Firefly’s mission is to make space accessible by providing our customers with reliable, economical,
high- frequency launches for orbital services.
Our Alpha and Beta launch vehicles enable this vision. Come aboard.
Firefly’s facilities include a 20,000-square foot design campus in Cedar Park, Texas, just north of
Austin, which houses the corporate headquarters, engineering staff, prototyping facilities and
machine shop. The Firefly Briggs operations facility, a 200-acre test and production site, is a short
drive north from the design campus. It hosts extensive and growing test and manufacturing
capabilities. Briggs facilities house ground systems fabrication, a test control center, surface
finishing/processing, composites fabrication and assembly production. Briggs is also home to the
propulsion, structures and materials testing range, whose proximity to the design campus
facilitates rapid transitions from paper to proven designs. Rapid development testing is optimized
at low cost utilizing our in-house horizontal engine test, vertical stage test, and high-pressure
component stands.
Firefly’s first Alpha vehicle launch is scheduled for the third quarter of 2019. By the first quarter
of 2021, Firefly plans to launch two Alpha vehicles per month given planned production capacity.
The Firefly team is currently evaluating market demands to determine the first launch date of
Beta.
2 Vehicle Overview
Firefly launch vehicles service the small-to-medium-sized satellite market. Alpha delivers 1,000 kg
(2,204 lbm) to Low Earth Orbit (LEO) and the larger Beta launch vehicle delivers up to 4,000 kg
(8,818 lbm) to LEO and smaller payloads to Geostationary Transfer Orbit (GTO). Firefly vehicles
draw on well-established, historically-successful rocket technology, such as LOX/RP-1, pump-fed,
regeneratively cooled engines.
Figure 1 highlights the Alpha and Beta vehicle characteristics. More details of Alpha architecture
are presented in Section 2.1; the Beta architecture is detailed in Section 2.2.
Quantity of engines 4 1
Payload
Payload Fairing
Payload Segment
1,000 kg LEO 28.5o, 200km
Carbon Composite Structure
Second Stage
1.0 m (3.3 ft) Payload Interface
Figure 3 shows the definition of the axes for the Firefly Alpha vehicle. The X-axis is the roll axis for
the vehicle, and the vertical axis for any vertically mounted satellite. The axes definitions in
Figure 3 are used throughout this User’s Guide to specify payload environments, loads, and test
requirements.
The fairing separates into two equal halves as shown in Figure 4. Figure 5 details the mechanical
separation design.
Pyrotechnically Actuated
Ejection Pistons (6)
Passively Actuated
Hinges (1)
Frangible Bolts (2)
After the second stage burn, the second stage and payload are stabilized. Then the payload fairing
separates, exposing the payload. Finally, each satellite is deployed from the Payload Attach Fitting
(PAF). A typical direct inject flight profile is discussed in Figure 8 of Section 2.1.4
A representative flight profile of the Firefly Alpha launch vehicle is depicted in Figure 8. Most
missions follow a similar profile, although the times and altitudes for key events may vary slightly.
1st stage
jettison
Liftoff
t = 0 sec
h = 0 km
v = 0 km/s
As depicted above, payload deployment occurs approximately 500 seconds after liftoff. For multi-
manifested missions and those requiring higher orbits, the Alpha second stage first inserts into a
low elliptical transfer orbit, coasts to apogee, then initiates a second burn to circularize into the
final orbit.
The Beta vehicle also utilizes efficient technologies such as composite tanks and COTS components
(e.g. Avionics electronics) and builds on the Alpha architecture discussed in Section 2.1. To learn
more about the Beta vehicle, please see Table 2 and Figure 9.
Quantity of engines 12 1
Thrust (stage total vac) 2,208 kN (496,378 lbf) 163 kN (36,643 lbf)
Payload Segment
Payload Fairing
Second Stage
5.3 m (17.4 ft)
Lightning 2
Qty Engines: 1
Second Stage Avionics Propellant: LOX/RP-1
Flight Computer Thrust: 163 kN (36,643 lbf) (vac)
Multi-Band Path Array Antennae Isp: 324.0 seconds (vac)
GPS/IMU Navigation
Power Conditioning & Distribution Unit
(PCDU)
Solenoid Drive
Data Acquisition Chassis (DAC)
Telemetry Transmitter
Lithium Polymer Batteries
Autonomous Flight Termination System
Interstage
Figure 10 and Figure 11 provide the orbit delivery performance capabilities from LEO to
Geosynchronous Transfer Orbit (GTO) for inclinations typical of a launch from the East Coast of
the United States.
Figure 12 provides orbit delivery performance for inclinations typical of a launch from the West
Coast of the United States, including Sun Synchronous Orbit insertions.
• Payload access prior to fairing closure • Payload access after fairing closure
• Launch of the payload into the desired • Payload heating and/or dedicated
orbit thermal control during cruise phase (prior
to payload separation)
• Customer support from the Payload
Mission Manager, Ground support and • Additional planning meetings
Launch Operations resources and
• Additional Customer offices and payload
personnel needed to support Mission
checkout space
planning, integration and launch
• Increased cleanliness levels in payload
• ISO 8 (same as 100K) clean room
checkout areas
payload and PAF integration space
• Additional fueling services and provisions
• Payload processing, integration and
Additional launch documentation
encapsulation within the fairing
Hypergolic fueling of payload
• Testing of payload interfaces at the
• RF transmission after encapsulation and
launch site
before payload separation
• Environmental conditions per contract
• Separation system provided by Firefly
agreement and payload health and
monitoring requirements
• Provisions for safety interfaces and
protocols, pursuant to range
regulations
• Acquisition and maintenance of
mission- required licensing for launch
vehicle, including US FAA and State
Department
• Mission Simulation Test exercising
operational readiness, vehicle
resources and equipment and ground
system support
• Mission Dress Rehearsal for key launch
team members
• Post-flight launch services, including
delivery of the Post-Flight Data
Package, including payload separation
confirmation, payload environment
report and final orbit configuration
• Separation system provided by
Customer
Availability - Firefly launch vehicles are mass produced to the highest quality standards. Mass
production empowers industry change through regularly scheduled launches.
Reliability - Firefly launch vehicles are designed and built for reliability. Separation events are kept
to a minimum of three: stage, fairing, and payload separation. Each launch vehicle runs through
a regime of tests, starting at the component level, up to a full stage test prior to transportation to
the launch site. Specific design choices have been made to ensure uncompromised reliability
beginning at the architectural level, including, but not limited to those found in Table 4.
Parts, Materials and The Firefly-developed Parts, Materials and Processes Plan is used to
Processes Plan standardize and establish reliability for Firefly designed hardware;
The EEE parts baseline is Automotive Grade with extended
temperature ranges
Pump-Fed Engine Pump-fed engine enables tank design pressures for low operating
strain
Coupled Loads Analysis Coupled Loads Analysis with Vibroacoustic analysis ensures that the
Firefly launch environment will not exceed the vibration
requirements of the payload
Composite Materials Composite materials enable monolithic parts with fewer structural
joints, which leads to fewer failure points and leak paths
Commercial off the With space launch vehicle heritage, COTS hardware is employed for
Shelf (COTS) hardware many Avionics and Fluid System components, as well as prepreg
carbon fiber to ensure consistent quality and robust material for
Structures components
Autonomous Flight The Autonomous Flight Termination Unit (AFTU) is procured from a
Termination RCC-319-14/AFSPCMAN qualified manufacturer
3 Mission Management
3.1 Mission Planning & Preparation
Firefly provides a single point of contact to guide every Customer through the entire mission
planning and execution process. This Firefly point of contact, the Payload Mission Manager,
remains the primary liaison for the entirety of the Firefly-Customer relationship. Customers can
expect transparency and open communication throughout the entire process, with regular status
reports.
One fit check meeting is foreseen during the mission preparation phase, typically to take place at
Firefly’s integration facilities at our Customers’ convenience, combined with a meeting to finalize
the payload to launch vehicle Interface Control Document (ICD). Activities and objectives of the
Fit Check include the following activities:
• Assemble a comprehensive mass and volume representative model of the entire payload
segment, including all payloads (in the event of multi-manifested launch configurations)
and separation systems and adapters,
• Validate the mechanical and electrical interfaces, and
• Where possible, validate the operation of all separation systems
Figure 14 depicts a notional launch timeline as the launch date nears, and Firefly welcomes the
opportunity to discuss adjustments for Customer needs. Additional or fewer days can be
supported for payload operations depending on Customer needs. The current schedule carries
two margin days post-payload mate to the launch vehicle.
The Mission Readiness Review (MRR) evaluates the status of the facilities, the launch vehicle,
ground support, and payload in route to mission success. This review is the final review of the
launch vehicle configuration and all hardware and software modifications needed to support
spacecraft mission requirement. It is conducted before shipment of launch vehicle hardware to
the launch site.
The Flight Readiness Review (FRR) ensures that safety systems and procedures are enabled and
readied for mission success. The FRR examines previously performed tests, demonstrations,
analyses, and audits that determine the overall system readiness for a safe and successful
flight/launch and for subsequent flight operations. It also ensures that all flight and ground
hardware, software, personnel and procedures are operationally ready. The Flight Safety Review
is incorporated into the FRR. The review shall include vehicle hazards, the status of any applicable
waivers and any other issues that contribute to flight risk.
The Launch Readiness Review (LRR) is the final prelaunch assessment of the integrated launch
vehicle/payload system and launch-facility readiness for launch. It is the last critical review before
launch.
An expected overall launch campaign duration is three weeks, with seven to ten days typically
assigned to payload checkout and miscellaneous autonomous payload operations. An additional
seven to ten days is typically required for payload to launch vehicle integration activities and final
launch vehicle preparation activities (including fairing closure, transport to launch pad, and
launcher erection). The Payload Mission Manager works with Ground Support to facilitate clear
communication and coordinate launch site activities. Firefly aims to exceed Customer
expectations during all phases of launch preparation.
desired beyond the PPF, given advance discussion, Firefly can work with Customers to process the
payload elsewhere.
The payload arrives at the Firefly PPF and is lifted from the transportation carrier by fork truck or
overhead crane located within the airlock. The satellite shipping container is wiped down prior to
being relocated into the clean room area, which provides a minimum processing area of 500ft2.
The satellite is removed from the shipping container with an overhead crane and mated to the
PAF. Once the payload is fully assembled, checked out, and (if required) fueled, it is encapsulated
by the fairing.
4.2.2 Encapsulation
After the payload is mated to the PAF and checkouts are complete, all contamination-critical
hardware is inspected and, if necessary, cleaned prior to encapsulation. The payload is enclosed
by the fairing in the vertical position. Upon payload encapsulation, a continuous supply of clean
air is provided at a typical environment range as presented in Table 8. The air is supplied to the
encapsulated payload through the air-distribution access door. A deflector can be installed within
the fairing at the inlet to direct any airflow from sensitive payload components. The payload fairing
with enclosed payload is rotated to a horizontal orientation by means of a break-over fixture. The
PAF will be mated to the launch vehicle in the horizontal position. The payload will be in a
horizontal, cantilevered position until the launch vehicle is rolled to the pad and raised to the
vertical position. The air distribution access door is closed during the roll out to the launch pad
with no climate control provided until arrival at the pad.
4.2.3 Fueling
Gaseous helium and nitrogen fluid panels are available in the Payload Processing Facility and main
vehicle integration hangar. Nitrogen will be 99.99% pure per MIL-PRF-27401F, Grade B. Helium
will be 99.995% pure per MIL-PRF-27407D, Grade A. Higher purities can be provided upon request.
Hypergolic fueling can be completed as a non-standard option and Firefly welcomes the discussion
at initial mission planning meetings. Early missions that require fueling may take place at a third-
party facility and then be transported to the launch site.
4.2.7 Infrastructure
4.2.7.1 Power
The following Electrical Ground Support Equipment (EGSE) power sources are provided for
payloads at the Payload Processing Facility (PPF) and launch equipment building: 120V/240V
single phase, and 208V three phase, 60 Hz. 50 Hz accommodations May be made via frequency
converters; this requirement should be included within the ICD requirements and discussed
during initial meetings.
4.2.7.2 Internet
High-speed, broadband internet access (both Ethernet and Wi-Fi) is available to Customers both
in the offices provided and the payload processing cleanroom facilities. A single connection in
each office/ area will be provided. This is not part of the mission network and can only be used
generally – if local networks are required it is expected that the Customers bring their own
equipment to set up local networks.
personnel may view the launcher while it is in its processing and assembly facility only if the proper
government approvals are in place.
Baseline accommodations for Secondary Payloads are presented in Section 5.5. Figure 18 depicts
a representative secondary payload configuration.
• Dassault ASAP 5
• Planetary Systems Lightband
• Ruag Clamp Band Separation Systems
• ISIPOD CubeSat Deployer
On Customer request, Firefly may provide a separation system as a non-standard service. the PAF
design can be modified to accommodate satellite separation systems of diameters ranging from
8 inches up to 38.81 inches. Requests for accommodation of any non-standard payload interface
should be discussed early in the mission planning process.
All payload interfaces to the Alpha PAF must be electrically conductive with sheet resistance less
than 0.1 per unit area. This interface will be auto verified during payload integration. It is the
Customer’s responsibility to ensure this requirement is met prior to shipment of the payload to
the launch site.
Payload data is provided via a second-stage Category -5E umbilical pass-through to the Alpha
Ethernet Switch, providing the operator access to telemetry during pre-flight operations. This
configuration isolates the payload data from other vehicle systems. It should remain powered off
until payload deployment. Customers that require a powered payload during launch should
coordinate with Firefly early in the mission planning.
• 100Base-TX link – This data will be sent directly through Firefly’s communication system
and will not be processed by any vehicle computers except for bandwidth monitoring.
Customers should contact Firefly early to determine network compatibility and bandwidth
limitations to ensure that Alpha is well-equipped to handle the format and size of the
desired data. Additional integration time might be required to ensure compatibility. This
switchover will be performed prior to launch for verification.
• RS-422 – This connection can be provided to the payload for simple signaling of events
including stage separation, fairing deployment and payload separation at no greater than
115200bps.
The Customer may request one or both of two forms of digital communication. A representative
optional payload configuration from the Alpha vehicle is depicted in Figure 20.
5.3.1 Mechanical
5.3.1.1 Transportation and Handling Loads
Table 5 shows the maximum transportation and ground handling loads anticipated during payload
accommodations. The ground handling refers to transport down a standard highway, which is
currently not provided as a service to the Customer. A slow-moving dolly will be used for any
service to be provided to the Customer, which will have the same loading capacity as the Transport
Erector Rollout (TEL). The following values reflect the concept of operations that assume an
integrated launch vehicle is rolled to the pad horizontally.
EVENT AXIAL LOAD (X), G LATERAL LOAD (Y), G VERTICAL LOAD (Z), G
It is possible to represent random vibrations in the frequency domain as a power spectral density
(PSD) function. Results from PSD calculations are depicted in the form of a line graph, where the
overall GRMS value is obtained by integrating the area under the PSD curve. The GRMS value is
then equal to the square root of the area.
PSD levels as determined for Alpha by Firefly will be updated as further analysis is performed.
Figure 22 shows representative values for launch vehicles of similar size and classification.
The PSD values are dependent on mass, with the corner values and slopes of Figure 22
summarized in Table 6. The MIL-STD-1540E example values yield a root mean square acceleration
(GRMS) of 3.8.
Individual payloads may use values such as those listed in Table 6 to create a random vibration
response of PSD versus frequency, in-line with actual levels experienced during flight based on the
NASA General Environmental Verification Standard (GEVS) GSFC-7000A (See Reference 2).
Analysis will be performed to predict random vibrations of the vehicle, and the preliminary Alpha
environment is presented based on data from vehicles of similar size. The NASA GEVS levels are
designed to encompass most of the common launch vehicles used. For this reason, Firefly uses
NASA GEVS vibration testing levels when the launch vehicle environment is unknown. It is
expected that the results of Alpha analysis will be bound by the values in Figure 23.
20 0.002 0.013
Representative values corresponding to the Shock Response Spectrum (SRS) are presented in
Table 7.
10 Hz 20
1,000-10,000 Hz 100
The Firefly vehicle fairings are made up of carbon composite with a hemispherical total emissivity
of 0.8. Acoustic foam can provide a relatively cool radiation environment by effectively shielding
the payload from ascent heating in blanketed areas. Analysis on the payload and fairing will detail
the radiative environment in which Firefly will shield the payload from hazardous heating.
The Firefly vehicle RF system is particularly sensitive to payload RF emissions in the L-band GPS
frequencies. It is recommended that payloads are powered off during launch to reduce the risk of
damage caused by RF interference.
Additionally, Customers must ensure that any payload component or material constituents that
are sensitive to RF transmissions are compatible with the electromagnetic environment provided
in Table 9.
ID TITLE DESCRIPTION
1 Resonances The Primary Payload Customer shall provide evidence of the 1st lateral
and First resonant frequency being above 6 Hz at Max Q [Ref 2]. Please refer to the
Natural Firefly vehicle axis definitions as shown in Section 2.1. Firefly will complete a
Frequency Coupled Loads Analysis (CLA) as early as possible to identify any issues
associated with dynamic coupling. The threshold given in this requirement is
a representative value of a similar vehicle and will be re-evaluated upon
completion of the CLA.
The Primary Payload Customer shall provide evidence of the 1st axial
resonant frequency being above 25 Hz at Max Q. Please refer to the Firefly
vehicle axis definitions as shown in Figure 3 of Section 2.1.
2 Quasi-static The Primary Payload Customer shall provide evidence that the payload is
and/ or Sine robust and will not suffer mechanical failure under the loadings specified in
Vibration Section 5.3.1.2, with positive margin.
Loading
3 Random The Primary Payload Customer shall provide evidence that the payload is
Vibration robust and will not suffer mechanical failure under the loadings specified in
Table 6, with +3 dB margin. Test duration shall be 2 minutes, per Reference
2.
4 Acoustic Should the Primary Payload Customer choose to design and qualify/accept
Vibration their design against the acoustic load environment (as may be expected for
larger satellites), the Customer shall provide evidence that the payload is
robust and will not suffer mechanical failure under the loadings specified in
Section 5.3.1.4, with positive margin.
6 Mass The required position of the payload’s Center of Gravity (CoG), relative to
Properties the plane of separation, is defined below.
This assumes that the Primary Payload Customer is mounted centrally, i.e.
with its vertical axis aligned with the launch vehicle roll (X) axis.
Offset of CoG from Y & Z axis: < 2 in (50mm)
ID TITLE DESCRIPTION
7 Grounding, It is assumed that all payloads will be powered off during launch (in line with
EMC and RF the Firefly baseline launch offering), and therefore will not be emitting any
Transmissions signals or radio frequency noise during the launch phase. Payloads that
request to be powered on during launch will be required to provide
evidence of a payload level EMC test which shows EM compatibility with the
Firefly vehicle assuring that any payload operations during launch cannot
interfere with Firefly’s Avionics & Flight Systems. All payloads (including
those which will be powered off) are required to show compliance to the
Firefly EMC specification to ensure that post-separation operations of the
launch vehicle upper stage are not compromised by the payload(s).
All payload interfaces to the Alpha PAF must be electrically conductive to
less than 0.1 per unit area. This interface will be auto verified during
payload integration. It is the Customer’s responsibility to ensure this
requirement is met prior to shipment of the payload to the launch site.
8 Primary For Firefly to carry out its mission design, analysis, and verification for the
Payload Data Primary Payload Customer, the following numerical/computer models and
Package reports for the Primary Payload will be required, in addition to the general
requirements of the Payload Data Package found in Table 10:
• A computer aided design (CAD) model, in STEP (*.stp or *.step) or Parasolid
(*.x_t) or Inventor format: The CAD model supplied should include accurate
representations of the external characteristics and features of the payload,
including all appendages, and the separation system.
• A Finite Element (FE) model of the payload, in ANSYS Workbench Project
Archive (*.wbpz), Femap Neutral (*.neu, version 11.1 or older) or NASTRAN
input (*.nas or *.bdf) format: The FE model should accurately represent the
payload’s stiffness and mass properties, contain all relevant
material/connection property definitions, and should ideally be simplified.
• Mass properties report: The report shall include total mass, center of mass
location in body coordinates, and moment of inertia properties about the
center of mass.
• Analysis and Test report: The report shall include information regarding the
first six modes of the payload, and evidence that the payload has been
analyzed and/or tested to withstand the quasi-static and random vibration
loads stated in Section 5.3.1.2 in each of the three orthogonal body axes.
The report shall also include compliance evidence for atmospheric, thermal,
and EMI/EMC requirements.
9 Mass A mass representative model of the Primary payload will be required for the
Simulators fit check. This mass simulator should ideally be mass and volume
representative and should have a representative launch vehicle interfaces.
Customers with CubeSat payloads will have the opportunity to manually check battery voltage and
charge if needed prior to integration with the CubeSat dispenser. By default, charging or other
diagnostic checks will not be available once the dispenser is mated to the vehicle. Customers who
opt to integrate their CubeSat with the dispenser at their own facility and ship the integrated
assembly to Firefly will not have the opportunity to check battery state before the dispenser is
mated to the vehicle.
Please contact Firefly early in the mission planning process if your Secondary Payload requires
data or power accommodations similar to those mentioned in Section 5.2.2.1 or Section 5.2.2.2
ID TITLE DESCRIPTION
1 Resonances and First Secondary Payload Customers shall provide evidence of the 1st
Natural Frequency resonant frequency being above 100 Hz.
ID TITLE DESCRIPTION
3 Random Vibration Secondary Payload Customers shall provide evidence that the
payload is robust and will not suffer mechanical failure under
the loadings specified in Table 6, with +3 dB margin. Test
duration shall be 2 minutes, per Reference 2.
5 Mass Properties Secondary Payloads shall adhere to the following mass limits.
Larger CubeSat masses may be evaluated on a mission by
mission basis.
1U CubeSats shall not exceed a mass of 1.33 kg 3U CubeSats
shall not exceed a mass of 4.0 kg 6U CubeSats shall not exceed a
mass of 12.0 kg
6 Center of Gravity There are no strict requirements for CoG positioning on the
(CoG) Secondary Payloads, as they are expected to be arranged as a
whole within the payload space by Firefly to achieve optimal
mass distribution. Measured mass properties of all payloads
must be communicated to Firefly.
7 Grounding, EMC and It is assumed that all payloads will be powered off during launch
RF Transmissions (in line with the Firefly baseline launch offering), and therefore
will not be emitting any signals or radio frequency noise during
the launch phase. Secondary Payloads cannot be powered on
during launch. Secondary Payloads are required to follow the
same grounding and EMC compliance as Primary Payloads.
8 Secondary Payload The Secondary Payload Data Package is the same as the
Data Package requested Primary Payload Data Package, sans Finite Element
Analysis.
ITEM DESCRIPTION
Payload Flight Mode Data outputs from qualification model mechanical tests or payload
flight models to inform Firefly of the specific path of the payload
once deployed, which may affect the trajectory and launch window
of the vehicle.
RF Data Sheet Test results of RF transmissions are requested so that Firefly may
prepare ground support for specific frequencies and expected
durations.
EMC Data Sheet Response traces and results from an EMC test must be provided,
showing that payload emissions are within acceptable ranges.
Electromagnetic compatibility test results ensure that the provided
payload or its elements do not generate interference that can
adversely affects its own subsystems and components, or other
payloads, or the safety and operation of the launch vehicle and
launch site.
Payload Model CAD and a finite element model are required for Coupled Loads
Analysis (CLA) so Firefly can assess payload dynamics. Requirements,
tools, and formats can be provided by Firefly.
Mass Properties The following must be provided as part of a report or in the form of
raw data:
• Measurement/test data from mass properties measurements of
the flight model payload or
• Output data from a sufficiently representative simulation or CAD/
FE model of the payload
ITEM DESCRIPTION
Media Package When appropriate and desired, Firefly intends to help socialize the
launch of specific payloads through the use of Payload Customer
logos, insignias, graphics, video files, solid models and drawings. The
earlier this package, or components of this package arrive, the more
comprehensive the branding effort may be. In the case of mission-
specific insignias to be positioned on the launch vehicle, Firefly
requests the proposed design submission no later than 4 months
before the launch date.
Safety Package The following shall be provided as part of a report or in the form of
raw data:
• Relevant certificates and certifications relating to the safety
requirements
• Any exemptions or associated justifications
Representative volume Representative volume and mass dummy of payload including the
expected mechanical and electrical interfaces.
Loads Compatibility Demonstrated (test) evidence of compatibility with the loads and
environments generated by the Firefly vehicle.
6 Facilities
6.1 Headquarters & Mission Control Center
The Mission Control Center (MCC) is located at Firefly headquarters in Cedar Park, TX. The MCC
seats up to fifteen personnel and include GUI displays and voice and data communication systems,
allowing personnel to view ground systems data and monitor telemetry from the LV prior to and
after launch. It is the engineering backroom on launch day.
A separate viewing area for the Customer can also be provided. The data and communication to
this area is limited to a payload graphical user interface (GUI) and the countdown net.
In the future, Firefly may offer additional launch sites and will soon begin the process to secure a
site on the east coast with potential locations being KSC, CCAFS or the Mid-Atlantic Regional
Spaceport (MARS). Once an east coast location is determined, Firefly can establish a site within 24
months or less to include approvals and necessary construction.
three phrase 60Hz, and 240/480V three phase 60Hz electrical power for processing. The HIF will
consist of a five thousand square foot open high bay with an eave height of twenty-five feet. This
eave height allows for the removal of Alpha components from their shipping fixtures located on
flatbed transportation trailers with deck heights up to 58 inches. Two bridge cranes in the high
bay will support shipping and processing efforts. Within the HIF will be space for engineering work
stations and consumable storage. The high bay and ancillary rooms will be operated as visibly
clean, air conditioned, humidity-controlled work spaces maintained at a temperature of
75o F ± 10o F (23.89 o C ± 5.55 o C) and a relative humidity between 30% and 75%.
The HIF provides short-term storage of Firefly launch vehicle assemblies prior to shipping to a
storage site. Several vehicles may be stored at each site, with the details of the storage yet to be
defined. The ultimate intent is to maintain an inventory of Firefly vehicles to support near-term
flight rates with possible market surges and commercial missions.
The high bay will be an ISO 8 cleanroom (Class 100K). Climate will be maintained to a temperature
of 75F ± 10F (23.89C ± 5.6C) and a relative humidity of 50% ± 15%. Ancillary rooms will be visibly
clean, air conditioned, humidity-controlled work space. Additional payloads will be processed in
modular soft- walled ISO 8 cleanrooms (Class 100K) within the Alpha processing area.
• A separate viewing area for additional payload team members which will provide data and
communication (limited to a payload GUI and the countdown net),
• approximately 3,000 square feet of office space for Engineering support,
• a GSE shop area, and
• storage space.
7 Safety
7.1 Safety Requirements
Customers must meet the requirements in AFSPCMAN 91-710, Range Safety User Requirements
(see Reference 3) when designing flight and ground systems. AFSPCMAN 91-710 contains
requirements for mechanical, electrical, fluid system, ordnance and RF design along with
requirements for ground handling and lifting hardware. Firefly is happy to assist Customers in
determining whether their current designs meet such requirements.
ID ITEM DESCRIPTION
2 Pressure Vessels Payloads containing pressure vessels shall comply with the
safety standards specified in ATR-2005(5128)-1, Operational
Guidelines for Spaceflight Pressure Vessels.
4 Ground Support All ground support equipment (GSE) shall be safety tested
Equipment with test reports available for review upon request. Electrical
GSE should include safety measures which allow payload
power to be cut in case of emergency, and to prevent
overcharging of payload batteries. Lifting fixtures should be
clearly marked with proof load limits. Propulsion system GSE
should include vent valves that will automatically activate to
prevent over pressurization.
Payload Questionnaire
A completed Payload Questionnaire informs Firefly of Customer requirements which feed into
preliminary feasibility and compatibility assessments. If you are considering using Firefly for your
mission needs, please complete and return the requested information to Firefly approximately 18
months prior to your desired launch date.
With your dedicated, single point of contact, Firefly ensures a streamlined and secured process
from initial contact through end of mission. We look forward to working with you
Payload Questionnaire
PAYLOAD INFORMATION
Payload Name/Acronym
POINTS OF CONTACT
Name
Phone
Payload Description
Primary Objectives
PAYLOAD INTERFACE
If additional information is available, please continue to populate the following with your mission
specific data:
Y ±
Z ±
PAYLOAD ENVIRONMENT
CONTAMINATION CONTROL
DYNAMIC ENVIRONMENT
Supporting Documents
1. NASA Langley Research Center. NASA-SP-8077, Transportation and Handling Loads.
http: //ntrs.nasa.gov/search.jsp?R=197200052422.
https://standards.nasa.gov/standard/gsfc/gsfc-std-70003.
3. United States Air Force Space Command. AFSPCMAN 91-710, Range Safety User
Requirements.
http://static.e-publishing.af.mil/production/1/afspc/publication/afspcman91-
710v3/afspcman91-710v3.pdf4
http://everyspec.com/USAF/TORs/download.php?spec=TR2004-8583-1A.026768.pdf
Acronyms
AFSPCMAN Air Force Space Command Manual
AFTS Autonomous Flight Termination System
AFTU Autonomous Flight Termination Unit
C&DH Command and Data Handling
CAD Computer Aided Design
CFM Cubic Feet per Minute
CLA Coupled Loads Analysis
COTS Commercial-Off-The-Shelf
EEE Electrical, Electronic and Electromechanical
EGSE Electrical Ground Support Equipment
EIRP Effective Isotropic Radiated Power
EPS Electric Power System
ESPA EELV Secondary Payload Adapter
FAA Federal Aviation Administration
FED-STD Federal Standard
FF Firefly
FRR Flight Readiness Review
FPS Frames Per Second GLOW Gross Lift-Off Weight
GN&C Guidance Navigation and Control
GPS Global Positioning System
GRMS Root Mean Square Acceleration
GSE Ground Support Equipment
GUI Graphical User Interface
HIF Horizontal Integration Facility
ICD Interface Control Document
ISO International Organization for Standardization
Isp Specific Impulse
ITAR International Traffic in Arms Regulations
LEO Low-Earth Orbit
LRR Launch Readiness Review
List of Figures
Figure 1: Firefly Vehicles Overview .............................................................................................................. 5
Figure 2: Alpha Overview ............................................................................................................................. 7
Figure 3: Alpha Vehicle Coordinate Frame .................................................................................................. 8
Figure 4: Open Alpha Clamshell Fairing Concept ......................................................................................... 9
Figure 5: Baseline Alpha Fairing Separation Design ..................................................................................... 9
Figure 6: Alpha Performance East Coast Launch ....................................................................................... 10
Figure 7: Alpha Performance West Coast Launch...................................................................................... 11
Figure 8: Example Alpha Direct Insert Flight Profile .................................................................................. 12
Figure 9: Beta Overview ............................................................................................................................. 14
Figure 10: Beta Performance East Coast Launch for lower altitudes ........................................................ 15
Figure 11: Beta Performance East Coast Launch for higher altitudes ....................................................... 16
Figure 12: Beta Performance, West Coast Launch..................................................................................... 17
Figure 13: Typical Launch Event Timing ..................................................................................................... 22
Figure 14: Notional Launch Campaign Timeline ........................................................................................ 23
Figure 15: Launch Control Organization .................................................................................................... 24
Figure 16: Firefly Alpha Standard Fairing ................................................................................................... 28
Figure 17: Firefly Beta Standard Fairing ..................................................................................................... 29
Figure 18: Secondary Payload Configuration ............................................................................................. 29
Figure 19: Payload Wiring Diagram –Standard Configuration ................................................................... 31
Figure 20: Payload Wiring Diagram –Optional Payload Configuration ...................................................... 32
Figure 21: Example Steady State Axial Acceleration Alpha (left) and Beta (right).................................... 34
Figure 22: Payload Interface Random Vibration Test Levels [Ref 4] .......................................................... 35
Figure 23: Bounding Random Vibration Test Levels [Ref 2,4].................................................................... 36
Figure 24: Representative Expected Shock Levels During Payload Separation [Ref 4]............................. 37
Figure 25: Example of Fairing Internal Pressure Profile [Reference 4] ...................................................... 40
Figure 26: Lightning Heatsink in Testing at Firefly’s Test Facility............................................................... 48
Figure 27: Firefly Launch Site Concept ....................................................................................................... 49
Figure 28: Typical Horizontal Integration Facility Layout with the Alpha vehicle ...................................... 50
List of Tables
Table 1: Alpha Characteristics ...................................................................................................................... 6
Table 2: Beta Characteristics ...................................................................................................................... 13
Table 3: Launch services ............................................................................................................................ 18
Table 4: Design choices for increased reliability ........................................................................................ 19
Table 5: Typical Transportation & Handling Loads .................................................................................... 33
Table 6: Firefly Vehicle Random Vibration Maximum Predicted Values ................................................... 36
Table 7: Expected Shock Values ................................................................................................................. 38
Table 8: Payload Environmental Conditioning ........................................................................................... 38
Table 9: Firefly Vehicle RF System Characteristics ..................................................................................... 41
Table 10: Firefly Primary Payload Customer Requirements ...................................................................... 42
Table 11: Alpha RF System Characteristics ................................................................................................ 44
Table 12: Requested Payload Data Package .............................................................................................. 46
Table 13: Payload Safety Requirements .................................................................................................... 52