Firefly Aerospace Inc. (FLY) Earnings Call Transcript
November 10, 2026
Earnings Call Speaker Segments
Thanks, Carmen. Hi, everyone. Michael Sheetz here, and welcome to Firefly's call covering the third quarter financial results. I'm happy to have with me on this call CEO Jason Kim and CFO Darren Ma as we report on the period that ended September 30th, 2026. This call today will contain forward-looking statements, which include, without limitation, statements the company makes regarding its future financial and operating performance, its growth strategy, and its market outlook. Actual results could differ materially from what those forward-looking statements contemplate. The factors that could cause actual results and trends to differ materially are described in our annual and quarterly reports filed with the SEC. Firefly undertakes no obligation to update any forward-looking statements, which speak only as of their respective dates. In addition, on this call we will discuss both GAAP and non-GAAP financial measures. A reconciliation of GAAP to non-GAAP measures appears in the third quarter 2026 earnings release. Unless otherwise stated, financial information referenced on this call is non-GAAP. Our earnings press release, SEC filings, and a replay of today's call are available on our investor relations website at investors.fireflyspace.com. Now I'll hand the call over to Jason.
Thanks, Michael, and welcome everyone to our earnings call for the third quarter of 2026. Since tomorrow marks Veterans Day, I want to express my gratitude to the men and women who serve our country for their commitment and the sacrifices they make in support of our nation. At Firefly, we're proud to have over 200 veterans on our team, myself included, and we're honored to take on a wide range of critical national security missions that back our war fighters and our allies. Before I move into business updates, I'll talk about the transformative deal we recently signed with AST SpaceMobile. Our agreement covering intellectual property, supply, and services, worth over $1.3 billion, marks the start of a three-year partnership that unites two bold, complementary companies from Texas. For anyone who doesn't know them, AST is constructing a space-based satellite constellation to deliver global cellular broadband directly to everyday smartphones. The company is collaborating with over 60 mobile network operators worldwide and has launched more than a dozen satellites so far. Launch capacity is highly constrained, with demand for deployment of proliferated constellations such as AST's direct-to-device satellites; this agreement is one more tremendous validation of our technology. Having a seasoned player such as AST SpaceMobile review what's available and then choose Firefly amounts to a strong outside validation of the engine technology we've built. Our patented tap-off cycle has proven itself, and we've invested years of work into developing and perfecting the next-generation Miranda engines. It's worth noting that by design this arrangement complements the launch business we already run. The vehicle for AST will be built specifically to carry their own satellite constellation, and Firefly will keep serving the wider commercial and government launch market. At its core, this deal leaves Firefly's identity intact. We're a vertically integrated space and defense company with a diversified set of business lines. We build and operate launch vehicles, lunar landers, spacecraft platforms, and national security software. This collaboration draws on a strength that's central to who we are, and it flows quite naturally out of the business we've always run. When it comes to our main launch offerings, Alpha and Eclipse, our dedication isn't going to waver. Because this arrangement doesn't dilute equity and comes to over $1.3 billion, it gives Firefly fresh resources to grow with, so we can move quickly on several fronts. We're going to grow both our infrastructure and our team, and we'll also strengthen our supply chain further. At our Rocket Ranch we're putting up several new test bays so we can boost how much launch vehicle production and testing we can handle; we're bringing on additional people focused on our launch programs. We'll be buying long-lead materials in bulk, which makes our supply chain more resilient and more cost-efficient. This added capacity is going to let us scale our engineering core's bandwidth even more. As part of the partnership agreement, Firefly is on the hook to build, test, and deliver 27 Miranda first-stage engines plus nine Vira upper-stage engines in total — that adds up to three complete flight sets. Those engines are going to power AST's new reusable three-stage heavy lift launch vehicle, which is built to carry 20 metric tons to low Earth orbit. The key point: Firefly keeps full ownership of the intellectual property tied to our engines. We're licensing that technology to AST, and they will configure the engines on their own to fit their vehicle's mission profile and integration needs. For any company that chooses to develop its own rocket, the engine is the toughest decision they will face, and it carries the greatest risk. AST chose Firefly, and that fact speaks volumes about the state of our technology. This deal truly benefits both sides. AST gets control of its own launch timeline. Firefly gets dependable, non-dilutive capital that supports production for our launch services, fortifies our supply chain and infrastructure, expands our team, and stretches the boundaries of what is achievable in space. At this point I would like to turn the call over to Darren, who will walk through selected financial terms of this agreement.
Thanks, Jason. From an operational and financial standpoint, this partnership is transformative. The deal comprises three main components totaling $1.3 billion. First, roughly $800 million in cash in AST stock tied to the Miranda and Vira engine IP licenses to AST. That IP license splits into $400 million in cash plus 10 million — 14 million shares of AST Class A common stock, determined through a forward VWAP calculation. Various lockup periods also apply to those shares. Second, $250 million goes toward support services that draw on our team's expertise. Third, the remaining $250 million covers engine deliveries supporting their first three flights. Revenue on this contract gets recognized in two parts. The fair value of the IP portion and the support services will be recognized over time on a percentage of completion basis. The fair value of engine deliveries gets recognized at a point in time when delivered to the customer. Please note that revenue recognized under this agreement will sit within our launch business. Now let me walk through how operational milestones will help shape the revenue ramp for this program. The program starts immediately, but revenue begins in earnest next year, ramping gradually as we hire and execute toward contract milestones. Engine deliveries start ramping in year two of the agreement, and we expect that to drive revenue higher in the second year, continuing to ramp through the third year. From a gross margin perspective, the corresponding revenue tied to the intellectual property agreement and support services will steadily expand our gross margin profile. On the cost side, we expect significant investments through research and development, as well as CapEx and infrastructure related to this agreement. We expect those investments to generate returns over the long term as they benefit our existing launch services business. For Firefly, the agreement represents a tremendous source of non-dilutive funding that bolsters our future, partners us with an industry leader, and enhances our financial profile. Now I'll turn the call back over to Jason for our third quarter business updates.
Thanks, Darren. We're finishing the year with genuine momentum—securing new contracts and reaching milestones throughout our programs. With those additional wins, our backlog reached a record $1.7 billion as the third quarter ended, which gives us even more confidence in our long-term growth path. We completed the clean room expansion at our spacecraft campus and moved in, and that increased our square footage fourfold for assembly, integration, and testing of both Blue Ghost landers and Elytra orbiters. The timing of this expansion is perfect, because, as we heard this weekend, NASA is moving full speed ahead on the Moon. We've discussed with all of you previously our work on building larger landers. That point is now here with Eclipse 2, and we're excited to begin. Larger cargo landers—able to help carry bigger payloads such as lunar terrain vehicles—will expand what we can do to support Moon Base operations. Having been brought onto this $10 billion program, we're positioned to compete for task orders and deliver them. Firefly is constructing the railroad to the Moon. The vehicles we build will deliver and sustain many of the capabilities needed to make a permanent lunar presence possible. The Moon is not just about exploration and discovery. The U.S. is caught in a space race with China, and we recognize just as clearly that the Moon represents the ultimate high ground. A recent report from the US Defense Intelligence Agency put it this way: "China portrays its interest in cislunar space as peaceful, but PRC officials have also discussed pursuing military capabilities in cislunar space." The Pentagon is putting funding behind its response to that adversarial threat. U.S. Space Force Major General Stephen Purdy, who heads acquisition for the branch, is calling on commercial providers to back national security efforts on and around the Moon. Our fleet of spacecraft stands ready to support. If you're new to Firefly, or just need a refresher, we're a space and defense company that delivers innovative hardware and software for the hardest missions in space—serving national security, exploration, and commercial technology. When it comes to hardware, we have our spacecraft — the Blue Ghost lunar landers and Elytra satellite orbiters — along with our launch vehicles, Alpha for small lift and Eclipse for medium lift. The spacecraft solutions platform also encompasses our software portfolio of AI-enabled products, which have been demonstrated in national security missions, plus autonomous guidance and navigation systems. Safety, quality, and reliability remain our tenacious focus and top priority as we expand deliveries of hardware and software products. Moving now to business updates: we are making headway toward launching Alpha Flight 8 during the first quarter of 2027. A national security customer gave us direction that called for an adjustment to our launch manifest. The demand for Alpha from national security is something I'm proud of, since Alpha is uniquely built for dedicated orbits on missions like hypersonics, tactically responsive space, and Golden Dome. This wasn't an easy call for us — ideally we'd have launched before the year was out. Still, we're proud that the customer has confidence in us to carry out this essential mission. This isn't new territory for us; we handled a similar manifest change when we conducted the historic Victus Nox responsive launch on Alpha Flight 3. As always, the schedule depends on outside factors that move, such as customer readiness, range availability, weather conditions, and others. We're going to take a close look at everything from Flight 8 so that whatever we learn gets applied to upcoming launches. This important launch is the first time our Block II vehicle configuration flies — a group of upgrades we've been working on to increase how fast we build and to improve reliability. Our attention is on the Block II first appearance since it's not just about Flight 8. Over at the Rocket Ranch, we already have structures and engine chambers ready for Flight 9, Flight 10, Flight 11 and Flight 12 as we head toward a higher launch pace in 2027. All structures and tanks for Flight 9 are complete, and all four Reaver engines plus the Lightning engine are in assembly. Testing on the Flight 10 structures has wrapped up. Every tank and structure needed for Flight 11 has finished manufacturing, and composite work for Flight 12 is underway. Our automated fiber placement machine produced each of these structures, and over the last few years we've continued honing our processes on that equipment. The AFP can produce several structures simultaneously. To back these launches and additional ones, we're increasing production of engine chambers. Right now, 24 Reaver engine chambers are in production, with more coming. Block II is essentially about unlocking rate for Alpha, and those gains are becoming visible on the factory floor. I realize many of you are keen to learn what we have planned for Alpha's launches in the coming year, but right now our attention is on the Block II debut. Our target for launches in 2027 will be shared during our fourth quarter earnings call. Demand for Alpha has never been as supply-constrained as it is now in the history of our company. In the near-term manifest, customers outnumber the rockets we can offer. That is a very good problem to have, and it reinforces our investment in production capacity. With Block II, we are stepping into rate. In the quarter, we announced our first contract with SSC Space, covering two Alpha launches from Esrange Space Center in Sweden. This deal is a milestone for us — it marks the first European launch contracts we've signed, and we're eager to support European customers locally as we continue building a worldwide business. In addition, Firefly received a third hypersonic task order for Alpha, this one from a customer whose identity is confidential, and we expanded our multi-launch agreement with Lockheed Martin. We also welcomed another strong commercial partner: Synspective, a Japanese company that operates synthetic aperture radar satellites, has signed with us for as many as 10 launches through 2030. With two satellites delivered to orbit on every mission, Alpha will double the pace at which Synspective can deploy per launch. Those satellites will launch from our sites in California and Virginia, giving Synspective adaptable access to a variety of orbital inclinations. Not long ago, I visited the site where we plan to launch in the future, at NASA's Wallops Flight Facility. I got to see up close the headway we're making as we prepare for the Alpha and Eclipse launches. This purpose-built pad will allow us to launch two separate vehicles from a single spot. The Fireflies crew is at work on the launch adapters, the strongback, the launch control center, and the commodity systems. I met with local officials, partners, and NASA leadership, as well as our own staff; seeing the progress toward launching out of Virginia no sooner than next year was terrific. Finally, during the third quarter, Firefly joined NASA's Spacecraft Processing Operations Contract. Being among the limited number of commercial sites for payload processing located at Vandenberg Space Force Base, this agreement enables us to expand our backing of NASA missions; we deliver adaptable infrastructure and services that ease congestion for our partners while opening a fresh revenue stream that will leverage our current facilities. Moving to Eclipse, our reusable medium launch vehicle being developed together with Northrop Grumman, we achieved meaningful advances during the quarter. I'm glad to report that the qualification campaign for our Miranda engine has begun.
To date, more than 175 hot fire tests have been conducted, totaling 4,230 seconds of cumulative runtime across 20 engines. Taking Miranda from a clean sheet all the way through the qual campaign is a feat without equal, and it reflects how dedicated our team has been. What we learned from Alpha is what made this achievable, because the common tap-off cycle engine technology allows us to bring this critically needed vehicle to market faster. Fireflies have been working hard to test the critical technologies required for reusability, including multiple relights and power throttling; at the same time, we've reduced risk and compressed the schedule while developing this powerful next-generation engine. What we've learned from building Miranda makes us quite confident about the engine's performance and its dependability. With qualification now underway, we're able to push forward on producing and putting together Miranda engines destined for the first Eclipse launch. Alongside Northrop Grumman, our co-developer, we're glad to watch Eclipse move closer to the launchpad. I'm adding more technical specialists to the program team, and I'm putting money into infrastructure as well, so that we can be prepared to scale up Eclipse production. Interest in this segment's launch remains at record levels, and capacity is tighter than it has ever been, so I'm working hard to ensure our team has what it needs—the tools, staffing, and funding—to get Eclipse into the market. Eclipse is needed by the world now more than at any prior point. Moving on to Blue Ghost, our lunar program maintained strong momentum during Q3. We have five Moon missions underway simultaneously—an achievement demonstrating how mature and repeatable our lunar architecture has become. Every one of those missions is at a distinct phase of development, and the team is overseeing this portfolio with exceptional discipline. A key achievement this quarter was finishing the new clean room at our Austin, Texas campus. At the ribbon cutting, we were glad to welcome several partners, among them leaders from the Texas Space Commission, NASA's Moon Base team, and state and local officials. Almost as soon as the ribbon came down, we started moving in several spacecraft for NASA and the Department of War, so the clean room went into service right away. That represents a substantial upgrade. The facility, built in multiple phases, is designed so we can integrate as many as twelve lunar landers and orbital vehicles at the same time, which gives us room to take on additional spacecraft contracts. Our Moon Base ambitions rest on this new clean room. We're increasing output to handle the expanding NASA pipeline and to serve commercial demand too. With Blue Ghost Mission 2, which we call Riders to the Dark, we're nearing launch readiness. During the third quarter the lander finished proof testing — the last check confirming the fully integrated fluid system is complete, including pressurization and leak checks. We stacked the lander together with the Elytra transfer vehicle, put electronics on the lander, and powered it up. Riders to the Dark is one of the most complex multi-stage lunar missions ever tried, and the spacecraft stack measures 22 feet in height. We take pride in flying commercial and government payloads for the U.S., Australia, Canada, the United Arab Emirates, and the United Kingdom; the second Blue Ghost mission is expected to launch next year, though the precise timing depends on our spacecraft reaching Florida and the launch window being confirmed. Following Riders to the Dark, Blue Ghost's Gruithuisen Domes mission is progressing through flight hardware production. The team has moved from design into build, and hardware is taking shape, with launch targeted in 2028. A new customer, Starcloud, is joining the Gruithuisen Domes mission; it signed an agreement with Firefly in the third quarter to fly an advanced AI compute payload aboard the Elytra vehicle. Starcloud and Elytra will jointly work to prove out the key functions of a future data center positioned in lunar orbit, one that would serve infrastructure both on the Moon's surface and in orbit around it. Data from Firefly's Solux autonomous vision system — an important technology we brought in through our acquisition of Space-ng earlier this year — will be processed by Starcloud's processor. Our agreement with Starcloud strongly confirms our belief that the Moon represents a platform for commercial infrastructure, rather than just a destination for government science. We're uniting space-based computing with the cislunar economy. And we aren't stopping there either, because Solux will also back other commercial surface initiatives connected to the Moon Base program. I'll share additional details on those down the road. The team has finished the critical design review for our Blue Ghost mission to the lunar south pole, and that moves the mission's development forward. We see this as another hugely exciting mission, since we're chasing resource discoveries that could be groundbreaking — for instance, searching for water ice that unlocks key Moon Base resources on the surface, including breathable oxygen, rocket propellant, and science. In addition, Firefly has brought Zeno Power Systems on board as a commercial payload customer for the accelerated Blue Ghost mission we're flying to the Moon's near side. Zeno's radioisotope heater payload represents a remarkable cutting-edge technology that is critical to a sustained lunar presence. With Blue Ghost onboard, Zeno aims to show off its survive-the-night package — designed so spacecraft and infrastructure can keep working through the long lunar night's extreme cold, where temperatures drop below minus 275 degrees Fahrenheit. NASA's Moon Base program is seeding the lunar economy. Every mission we fly offers bolt-on opportunities and hosted payload options for commercial customers, and those improve gross margins on each mission while opening up additional revenue sources. Turning to Elytra: the MoonFall mission has cleared preliminary design review, which confirmed our spacecraft's design can support this flagship NASA mission. Under our $75 million subcontract, we're working hand in hand with NASA's Jet Propulsion Laboratory to get their drones delivered to low lunar orbit. This mission is a new frontier for exploring and moving around on the Moon, and we're excited to be part of it alongside one of the top research institutions in the world. A short while back, I visited NASA's JPL and met with Director Dave Gallagher. During a fireside chat in front of the JPL staff — you can watch it online — I really appreciated the way Dave described the drones Elytra is providing. In his words, "They are going to be tremendous scouts for the resources you need, potential Moon Base locations, and there's a bit of national security flavor to this as well." In the third quarter, Elytra brought in one more contract with the Department of War's Defense Innovation Unit. We're designing a mission in which Elytra would supply deorbit services. As soon as the preliminary design review is finished, Firefly will be able to compete for the following phase, which might involve launch and spacecraft operations for a low Earth orbit mission. We're also energized about securing a spacecraft subcontract in support of NASA's SkyFall mission to Mars. This marks our first time supporting a mission to the red planet, and it's another statement mission for JPL. Our spacecraft for the DIU's Project Sinequone is moving into integration and testing as we get ready to launch next year. Not long ago, we finished testing how the folding solar panels deploy for this Elytra maneuverability mission.
The orbiter has arrived in our spacecraft cleanroom, where it will undergo the remaining integration and testing work. Meanwhile, our subcontract with Benchmark Space Systems under the Department of War's DARPA LASSO program is advancing to the next stage after a competitive down select. Benchmark moved its feasibility and design efforts forward for DARPA, and we're pleased to support this lunar mission with our Solux autonomous vision navigation system. Let me now shift to SciTec. Recently, I had the opportunity to visit the FORGE Operations Floor at Buckley Space Force Base in Colorado. During that visit, I observed an impressive group of U.S. Space Force guardians and contractors who are dedicated to serving our nation and our allies. I observed FORGE operations firsthand, with Firefly's SciTec team providing support. Witnessing the way we directly enable advanced processing of missile warning and tracking data—leveraging our own AI capability to amplify the U.S. Space Force's efforts—filled me with real pride. In conversations with senior guardians, they shared that FORGE has been producing outcomes valued not only by the U.S. Space Force and our country, but that allied nations also call them to express gratitude for these life-saving capabilities; those same guardians added that they see capabilities from Firefly that no other contractor offers. FORGE remains among our most consequential programs. Ongoing conflict in the Middle East, together with evolving missile threats worldwide, has underscored just how strategically vital FORGE's capabilities are to the government customers we serve. FORGE is up and running, delivering results, and the signals we get from customers about demand stay strong. In the third quarter we reached yet another operational milestone for FORGE by feeding data into the U.S. Space Force's GEO Wide Field of View space vehicle; speaking personally, that milestone means a lot to me, since in an earlier role I was responsible for building and operating that geostationary orbit satellite. The spacecraft contributes wide-area situational awareness and boosts time-critical detection capability, which makes the FORGE system even stronger. We're making steady operational progress on FORGE, and within recent weeks we've added fresh technical intelligence features. Since our engineers work side by side with U.S. Space Force operations, we can address customer requirements directly and move the technology forward at a pace that's hard to match. We're now also broadening both our capabilities and our revenue into neighboring opportunities and programs of record. In the third quarter, we secured a $94 million U.S. Space Force contract through the Ground Based Radar Digitization, or GBRD, program, supporting efforts to overhaul legacy defense systems. GBRD takes the FORGE approach and applies it to radar modernization. We have onboarded to the $981 million U.S. We secured a Space Force IDIQ contract for NITE-STAR, which lets us bid on task orders supporting advanced space-based test and training operations through 2032. That's one more illustration of how our hardware and software capabilities work together. We also broadened Firefly's Air Force contract for the Advanced Battle Management System Data Fusion program, and that effort leverages decades of expertise in sensor integration and multi-source data correlation. Under this ABMS contract, we're feeding a new class of counter-unmanned aerial system sensor data into the cloud-based command and control system. Since CBC2 is a central component of the Air Force Battle Network, we're glad to help integrate yet another data stream into that system. After that point, the CBC2 system earned Air Force System Interoperability Test Certification—a key program milestone showing we're ready before operational acceptance. In Q3, we also joined a $66 million IDIQ covering work within our instrumentation and testing group, and we ran a test campaign for a missile defense customer. Overall, our advanced data and AI business is performing strongly and steadily expanding into additional programs of record. We're working toward a future in which customers get an on-demand app store offering missile warning, space domain awareness, position navigation timing, targeting, and exploration services. That covers the business update, so I'll hand things over to Darren, who will walk us through the third quarter financials.
Thanks, Jason. For a second quarter in a row, our revenue came in above $100 million. Year to date, that brought revenue to $309.2 million, which is up 203% compared with the first nine months of last year. The third quarter results reflect the strength of Firefly's diversified portfolio, and they support our plan to build a fully integrated space and defense technology company. Third quarter revenue was $110.7 million, a strong 259% increase year-over-year, versus $30.8 million in the same quarter a year ago. Notably, we delivered that third quarter performance without the revenue benefit recognized in the second quarter from an accelerated national security hardware order. Looking at total revenue, spacecraft brought in $106 million, while launch added $4.7 million. The results for our third quarter demonstrate how strong and resilient our business model is. To give a quick explanation of revenue recognition, the Spacecraft Solutions business typically recognizes revenue over time on each contract using a percentage completion method. On the launch side, Alpha revenue gets recognized at a point in time, specifically when the launch happens, whereas Eclipse revenue is recognized over time according to program milestones within our Northrop Grumman partnership. Once the vehicle is up and running, Eclipse is going to move to point-in-time revenue. We closed Q3 with a total backlog of roughly $1.7 billion. That's higher than the $1.5 billion we had last quarter, and also above the $1.3 billion posted in the same quarter a year earlier. The main drivers were the ground-based radar digitization award, extra hardware server orders, and one more Alpha Hypersonics task order. Most of our third quarter revenue came from converting backlog, yet new customer contracts worth more than $300 million did more than replace the revenue we recognized during the quarter. For our business, backlog continues to be among the strongest signals of future revenue growth. GAAP gross margin for the third quarter came in at 22.9%, versus 20.3% in the previous quarter. The improvement from one quarter to the next came from a favorable product mix, since purchases of lower-margin hardware servers held Q2 back. As a reminder, the main GAAP to non-GAAP adjustments to operating expenses are stock-based compensation expense, one-time transaction-related expenses, and the amortization of intangibles. Operating expenses came to $104 million in the third quarter, versus $94.3 million in the second quarter. That increase reflects R&D investments in our next-generation launch vehicles, bringing Alpha Block II online and ramping up the Eclipse development. Operating loss was $78.7 million, compared with a loss of $70.4 million in the second quarter. Our net loss for the third quarter was $75.4 million, or a net loss of $0.45 per share. That compares to a net loss of $67.7 million last quarter, or a net loss per share of $0.42 in the prior quarter. For the third quarter, the net loss per share was computed based on a weighted average share count of 168.4 million. Because of a series of option exercises during the period, our ending share count for the third quarter stood at 171.6 million shares, and we expect that figure to grow by roughly 1 million shares each quarter. Stock-based compensation totaled $15.3 million in the third quarter, compared with $17 million in the quarter before. Adjusted EBITDA showed a loss of $69.5 million in the third quarter, while the second quarter had a loss of $61.2 million. Our balance sheet is still strong, and we closed the quarter with total liquidity of $839.7 million. That figure is made up of $534.7 million in cash equivalents and short-term investments, plus $305 million of available capacity under our revolving credit facility, which is still undrawn. Capital investments totaled $15.6 million in the third quarter, down from $24.7 million on a sequential basis. That quarter-over-quarter decrease mostly reflected the wrapping up of investments tied to test upgrades supporting Alpha Block II, the spacecraft cleanroom expansion, and other infrastructure work aimed at our growth objectives. Free cash flow was an outflow of $85.3 million, versus an outflow of $106.3 million during the second quarter. Keep in mind that the Q2 figure included the final SciTec acquisition-related payment of roughly $24 million. Turning to our revenue outlook for 2026, we are revising the 2026 revenue range to $440 million-$450 million, up from the prior range of $420 million-$450 million. That lifts the midpoint of our guidance to $445 million, from $435 million. To close, our financial strength is built on a diversified revenue base, a growing backlog, and substantial liquidity that supports disciplined investment. We keep finding ways to optimize our programs by leveraging our core technologies, while maintaining the capital-efficient discipline that has accelerated our development in only nine years as a company. Here are a few illustrations from the playbook we use. For upcoming missions, we're putting the proven Blue Ghost lander to work, and we've rolled out a lift-and-shift approach built on years of investment in the FORGE missile defense system, which opens up nearby opportunities like GBRD and ABMS. We've tapped non-dilutive funding as well, among them the Texas Space Commission's grant program, which supports our cleanroom expansion. The AST agreement stands as the most recent example of this playbook. Our Miranda and Vira engines are proprietary technology held by only a handful of companies around the globe. At this point we're putting that technology to work and generating revenue from it. With that, I'll turn the call back over to Jason.
Thank you, Darren. When I consider where Firefly sits right now, three items come to mind. To start, Alpha production is ramping up. Block II manufacturing and assembly are keeping the factory busy, and that gives me confidence. Once Alpha Flight 8 launches, Alpha Flights 9, 10, 11, and 12 follow right after. We upgraded our test stands and our Vandenberg facilities, and we are making progress at both our Virginia and Sweden launch sites. New international customers came on board through the deals with SSC Space and Synspective. Second, our platform keeps expanding. We added several commercial partnerships tied to our upcoming lunar missions. The DIU deorbit contract confirms another growth vector for our Elytra orbital services. FORGE confirms how nationally important what SciTec brings to the Firefly platform is. Our agreement with AST SpaceMobile confirms the extreme scarcity value of our propulsion technology. Third, our team is world-class. They have delivered these results each quarter and are why Firefly wins. Fireflies are bold, resilient, and passionate, and supporting them makes me proud. Our team has led Firefly to land on the Moon, to launch in 24-hour call-ups, and to provide operational no-fail AI defense software. We have a robust, diversified space and defense business. Each quarter, the addressable market for what we are building gets larger. Thank you for joining today's call. Michael, back to you.
Thanks, Jason. We’ll be at several investor events in November and December, and we’re looking forward to seeing a lot of you over the next few weeks. Operator, we’re ready for questions.
Thank you, and good afternoon to all of you. A great deal has been going on during this quarter, so I have a couple of questions if that works. With Firefly now brought onto the $10 billion CLPS 2 IDIQ, could you discuss how that opportunity's scope differs from what the current program offers, and maybe more specifically, what extra mission types or bigger payload classes Firefly is able to serve now? Thank you.
Hi, Sheila. We're genuinely thrilled and excited to have been onboarded onto CLPS 2. Looking back at last year, we became the first company to successfully touch down on the Moon, accomplishing that through Blue Ghost Mission 1, which fell under the $4 billion CLPS 1.0 program. A handful of bids in that program are still pending, and we're awaiting word on those. With CLPS 2, there's a lot of excitement on our side, since we got a head start on design work for it, and many of the core technologies that made our lunar landing a success are built into our bigger landers too; that gives NASA, Firefly, and some of our commercial customers plenty of confidence about bolt-on opportunities. We're really excited. A few items we could send up aboard the bigger cargo lander include things such as lunar terrain vehicles. You may recall Carlos with the Moon Base program noting that a pair of those vehicles has already been awarded; we're eager for the chance to bring mobility to the Moon. Additional cargo can also support a long-term human presence there. As you may recall, the Moon's entire surface is roughly comparable in size to Africa, while the usable portion of the South Pole — which we think holds the resources needed for life, including water, ice, and others — is roughly the size of Washington D.C. Those missions have us excited, and so does carrying any freight that contributes to a sustained human presence on the Moon. We can also collect plenty of other science, though what especially excites me is manufacturing on the Moon. As I noted, there are abundant resources such as water ice that could be turned into propellants. Certain rare earth minerals might be usable for manufacturing. Regolith itself could be processed and transformed into various fabricated materials. An entire commercial economy could be constructed on top of what NASA and other global agencies are doing. Beyond that, national security demand is strong as well. As you saw, the Space Force established an entire organization to coordinate cislunar activity, with Major General Stephen Purdy at the helm. Our expectation is that this will keep growing—perhaps beginning at a 10% scope. The Moon Base represents more than the $30 billion opportunity NASA discusses in connection with it. It's possible that 10% of what goes to the Moon could be U.S. Space Force based, and that share may climb to 25%. Thus far, we have received information requests involving up to five satellites tasked with surveying cislunar space, and those kinds of efforts are what we have funded via buying Space-ng, whose vision autonomous navigation camera systems now sit inside the company. That capability can be fielded, together with offerings under the Ocula service, to provide space domain awareness extending beyond space exploration by itself.
That's genuinely useful on the long-term color. If I could squeeze in one more, perhaps a bit more near term. When we look at the Q4 2026 guidance, you took the low end of the revenue guide, but Alpha Flight 8 has now shifted into Q1. Could you perhaps help us bridge what's behind the revenue uptick, and are any Alpha launches baked into Q4 revenue? Thank you.
Yeah. Hi, Sheila. Darren here; for the rest of this year, there are certainly some moving parts. There's strength in the spacecraft business. We're working on five Moon programs, all in parallel, and demand is strong on the AI software solution side, really offset by some of the revenue impact on launches that Jason discussed. One of the strengths of our business model is having a diversified portfolio that generates revenues, and basically, the AST deal also adds to this multiple of revenue streams we already have in place.
Great. Thanks a lot.
Hello. Congratulations on the AST deal, and thank you for fielding our questions. I'd like to ask about the AST, the rev rec. You folks surely understand this better than anybody, correct? Historically, Rocket programs probably run about three to five years late on average. Should there be any kind of delay on their side, nothing to do with you, would that affect the rev rec at all if we're thinking over the next couple of years?
Hey, Edison. Darren here. No. I mean, when you look at how revenue recognition works for this program, it's split into two parts. The intellectual property piece connects to the services piece, and we'll recognize that as we perform across the three-year period. Engine deliveries will likewise be recognized as we hand over the engines. So if any delay occurs on their end—I don't think that affects us where revenue recognition is concerned.
Alright. And a quick follow-up question about the deal as well. I believe you said during the prepared remarks that the gross profit margin contribution helps expansion. Do you have any sense of how we should think about just the incremental margin? Is it essentially almost pure margin? Are there some minor expenses involved? Just how should we think about it as we layer in all of this revenue?
Yes, I think the way to think about it is that when you look at our gross margin, we're currently in the mid-20s, and since the IP portion of it is tied closely to the services and recognized at the same time, that will deliver incremental gross margin expansion as we execute on this deal. But there will be some gross margin expansion associated with the contract.
Okay, thanks.
Hello, this is Kyle Benvenuto, standing in for Kristine Liwag. I appreciate you taking my question, and congrats on everything achieved during the quarter. I'd like to ask about SciTec and how the outlook appears for that business. First, given that $94 million GBRD award and the onboarding onto the $981 million NITE-STAR IDIQ, carrying the FORGE playbook over into neighboring programs of record — how should we view SciTec's organic growth as we move toward 2027, and how much might NITE-STAR task orders and other new programs add compared with the existing FORGE base? Second, as the business grows, you mentioned before shifting a larger share of SciTec's work toward fixed-price contracts. At this point, how much of that transition has actually happened, and what kind of margin improvement do you expect once offerings such as FORGE shift away from cost-plus development and into trusted software-driven deployments? Thank you.
All right, I'll do my best to address each of those several questions, though I share your enthusiasm for SciTec — I'm really excited about it. Let me return to FORGE. FORGE rests on a base of more than 45 years of algorithm work aimed squarely at national security, and even more specifically at missile warning and missile tracking. If you consider the FORGE effort, its total value stands at $800 million and rising, and as we speak that effort is carrying out no-fail operational missions. I stood on the mission operations floor, and what SciTec is accomplishing in support of that mission was truly eye-opening — assisting in the effort to save the lives of our war fighters and our allies. Much of what’s been built there—the data center hardware effort as well as the framework applied to it, plus the mission applications for missile warning and missile tracking—is largely transferable. You can lift and shift that capability into areas such as winning the ground-based radar digitization program. In this instance, what we did was lift and shift the framework, and it helped us accelerate our capabilities relative to the landscape, and we were able to win phase one, which is roughly the $94 million first phase. There are plenty of upside opportunities there; it could be somewhere around $400 million-$500 million of upside. We're concentrating on collaborating with the group we put together, which delivers an asymmetric capability for modernizing legacy ground-based radar programs—enabling us to supply additional missile warning, missile tracking, and space domain awareness to the war fighters; that's one illustration. Growth upside potential exists in that area. I'm also enthusiastic about taking what we've learned from FORGE and GBRD and applying it to other domains, such as position navigation, timing, air moving target indicator, ground moving target indicator, and space domain awareness. Many of those algorithms transfer quite readily, and they're combat-proven today. We're applying AI and enhancing it further, and those opportunities have us truly excited. Then when it comes to firm fixed-price contracts, that shift has been underway for a few years now, and it explains why a lot of the Space Force moved over to these Other Transaction Authority agreements, the OTAs, which are mostly firm fixed-price type contracts rather than the cost-plus type contracts. Those carry opportunities for gross margin expansion, provided you execute. So we're genuinely excited about what the future holds for what we do with SciTec, and don't count us out when it comes to upside opportunities from taking SciTec algorithms and deploying them to space as well, because in national security the name of the game is being faster than the adversary's OODA loop. And by bringing things to orbit and operating with lower latencies, we can get inside the adversary's OODA loop.
That's really helpful. Thanks, Jason. I'll hand it over now.
Hi there, good afternoon. My question is this: given how tight the launch supply-demand market is right now and looking ahead, especially with Falcon 9 being phased out over the next several years, and also considering what medium-lift vehicles are charging in today's market for the back half of this decade, has any of that shifted how you approach pricing for upcoming Eclipse or Alpha launch agreements?
Yes, definitely; the launch supply environment is the most constrained we have ever seen, and we are getting a great deal of inbound interest. As you can see, we signed two Alpha contracts with Sweden, plus up to 10 with Synspective out of Japan, and one more confidential hypersonic test launch on Alpha; so that demand is converting into signed contracts. And we do have pricing power. Take our VICTUS SOL mission that we signed with the Space Force — that was previously a $22 million contract. And lately we are seeing deals with upside opportunities that go beyond those higher price levels. So we are indeed seeing that across our Alpha missions, which are extraordinarily well suited to national security work, such as hypersonic test launches, along with tactically responsive space launches and more. On Eclipse, we are keeping our heads down, and the deal we completed with AST is genuinely a win-win, since it brings in capital that supports our Eclipse program while also helping AST. So we will be ramping up Miranda production as well as Eclipse production more broadly, with added engineering and manufacturing supply chain work, an injection of hardware-rich, long-lead material purchases, optimal equipment, and additional integration and test capacity. All of that will help us get Eclipse up and running as quickly as we can, because demand is so strong. And we do see that this demand supports higher pricing for medium lift too.
Great. Now, on the AST agreement — the release called it non-competitive by design and purpose-built for AST's payloads. I'm curious whether you could give any color on the formal restrictions that govern how the engines and IP can be used, and what's in place there. Is Blacklift only allowed to launch its own internal AST payloads, or is there potentially some reality where, over the long term, they could become another launch provider for the commercial market? Any clarity on that would be great. Thank you.
Yeah, one thing worth stressing is that Firefly keeps ownership of our core intellectual property — that's Miranda — and AST is focused purely on getting its own constellation into orbit; they've built a strong direct-to-mobile constellation business, and they'll keep ramping it up. And since they're scaling that proliferated constellation, they really need to have control over their launch schedule and their capacity. So my read is they'll stay laser-focused on launching their own constellations, while we remain unwavering about launch capability for our Eclipse rocket serving commercial and government customers. So it really is a strategic, transformational deal. It's a win-win.
Thanks.
Yeah. Hi, everyone. Alex here, filling in for Seth. Good afternoon.
Hi, Alex.
Hello. There's a question I've been wanting to raise, and I suppose no one has actually asked it head-on so far. I understand you're not especially eager to offer detailed guidance on how to model Alpha Rockets' launch cadence for next year. Still, you've indicated roughly that the next five Alpha Rockets, give or take, sit at different points in production. What I'd like to know is whether, assuming all goes to plan, that could serve as a sensible baseline for estimating how many launches you might manage next year. So following on from that, with this AST deal, how much might the capital coming from them speed up your ability to carry out launches next year?
Hi, Alex. Let me offer one data point from just today. In a three-hour window today at our Rocket Ranch — everything there is co-located and vertically integrated with our test stands — we knocked out a number of engine tests. Two Reavers got hot-fired today. One Lightning got hot-fired. A Miranda qualification also got hot-fired. Every bit of that took place inside three hours of one another today. So as you can tell, our testing capacity has really been scaled up. Now, regarding Alpha Block II, the upgrade's entire purpose was to boost manufacturability and reliability, and that's becoming visible and taking shape on the factory floor. So, looking at Building 3, Flight 8 and Flight 9 are there for integration, wrapping up that integration. Flight eight is being readied and prepped for shipment to Vandenberg. Flight nine is having all its Reaver engines and Lightning engines put together for integration. Then for Flight 10, every composite structure has been approved and has passed proof testing. Flight 11 composites are being completed. Flight 12 composites are getting underway. We currently have 24 Reaver engine chambers in flow. We've got roughly six ship sets in that mix, and every one of them falls inside Q4. So there's a lot of enthusiasm on our side about what comes next as we keep building on what we've already achieved. Our Cortex feeder line is now open for the full set of avionics and harnessing work too, and that line is ramping up. So the production floor is running smoothly across the board, and as I said earlier, our test capabilities have been scaled up as well. On top of that, Vandenberg has been upgraded for Block II; we're — yeah, I was out at Wallops, Virginia earlier this year, and we're seeing progress there across all the various pieces of that launchpad. I was in Sweden earlier this year too, and it's the same story — we're making substantial progress there. We're really just getting started across every part of the business.
Great, that's good to hear. So maybe just as a quick follow-up on Eclipse: is it still the expectation that you'll get that first launch off in 2027? I know you're talking about kicking off the Miranda engine qualification process. If there's anything more specific you could share about what remains to be done there, and maybe beyond that, what are the final long pulls in the tent before you can actually do an Eclipse launch?
Yeah, like I said earlier, we're heads down on Eclipse. Our laser focus is on delivering the first stage to Northrop Grumman, our co-developer. We're past 175 hot fires on Miranda. Counting the one from today, we're reviewing all the data and verifying the capability. That engine is very mature, and we're very confident in what it can do. We're also building the flight engines ahead of time. Everything is just laser-focused on all the milestones around qualifying Miranda and qualifying our composite tanks and fluid systems too. So we're really, really excited about Eclipse's future, especially with this injection of capital that will help speed up our production line.
Great. Thanks a lot.
Yeah, Mike Crawford here from B. Riley Securities. Just to follow up on Eclipse, your partner at ASTS is designing a simpler rocket that only reaches LEO, whereas Eclipse can go all the way to translunar injection. Is there any reason they'd use a three-stage rocket if it's meant to be simpler, compared with the two-stage Eclipse?
Yeah. Hey, Mike; that's AST's design. They're in charge of the overall design of their Blacklift rocket. As we said earlier, we're supplying the IP for the Miranda engines, and we're also providing the first three ship sets of 36 engines for those first three launches. There are some engineering services too that we'll provide them; that's AST's design. They're focused on the mass of their BlueBirds constellations on each launch, and that's why they're focused on what they have with their three-stage design. Whereas, for our Eclipse rocket, we're building the railroad to the Moon, so we're looking at a number of different missions for commercial and government customers, including Moon missions as well. So that's why we have a different stage design.
Oh, okay. Thanks, Jason. On Elytra specifically, could you perhaps walk us through how its RPO and maneuverability stack up against rivals such as True Anomaly Jackal, Quantum Space Scout, Turion, and others like them?
Yeah, many of the core technologies behind the successful Blue Ghost Mission 1, from the seven major burns we performed through translunar injection, through to low lunar orbit, and then at last braking, maneuvering, and setting down gently on the lunar surface, many of those same elements are incorporated into our Elytra spacecraft and give us heritage. As you know, we spent many days, 45 days, traveling through LEO, MEO, GEO, cislunar, and finally to the Moon. So we hold heritage across all of those orbits. What I would say is that the capabilities Elytra delivers include a great deal of fuel. We have chemical propulsion systems, so we can carry substantial fuel onboard. We rely on carbon composites for our primary and secondary structures, which means more mass can go toward the mission payload. We have a system that is not only maneuverable with precise thrust at millimeter per second kind of precision, but we also possess a lot of lightweight structural technology that lets us carry more mission payload capability, such as optics, camera systems, and other systems that support space domain awareness; we also bought Space-ng earlier this year, and their autonomous navigation camera system lets us carry out many autonomous maneuvers, RPO included. It is a truly excellent capability with flight heritage that can operate across all the different orbits. As I said earlier, the Moon represents the ultimate high ground, and everything is shifting more toward cislunar space. The Space Force will require more space domain awareness in that region, and we already hold capability that has been demonstrated there. Beyond that, we signed some excellent commercial hosted options like Starcloud, and now we are delivering AI from our Elytra spacecraft too. Really excited about what lies ahead for Elytra.
Okay, thanks. Thanks, Jason.
Hi, Ben Tomick here, filling in for David. Could you walk us through how we should view cash burn across the full year and going into 2027, and what amount of additional CapEx ought we to anticipate tied to the AST agreement?
Yes. Like I said before, under the AST agreement we will be putting substantial money into R&D, CapEx, and infrastructure as our production facilities get expanded and so on; that helps AST and also dovetails with the production Jason referenced for other customers on Eclipse. So those investments are coming, and because of that, you should anticipate cash burn rising through next year under this contract.
Understood. Going back to Eclipse, I believe you said there were still some additional CLPS 1.0 opportunities remaining out there. How should we think about the timing on that, and when should those first CLPS 2.0 awards be coming in?
I believe there are at least three opportunities still outstanding. One of them could be awarded in the fourth quarter, possibly as early as the fourth quarter, and it concerns a far side South Pole mission. We're quite excited about that mission, since we're heading to the far side with our next Riders 2 the Dark mission next year, so much of the underlying CONOPS and technology incorporated into that system is really transferable to this new opportunity as well. We're very excited to hear back on the results of that competition. A second mission is seeking lunar surface imaging, and it's quite similar to our existing commercial Ocula service, which will also fly on our second mission to the far side of the Moon, called Rise to the Dark, specifically our Ocula service. That's where we place a camera on our Elytra transfer vehicle, and we'll be able to image the Moon and sell that data commercially. The bid that's outstanding from NASA and in front of us is for a service of that kind, providing lunar high-resolution imaging as a commercial service. Then there's a third landing mission as well that will most likely come out early in the first quarter of next year, to be awarded in 2027; so those are the three outstanding ones I mentioned.
Great. Thank you.
Hi, guys. Appreciate the question. When AST first approached you folks to begin these discussions, did they initially just want to purchase launches from you the way any other customer would? Because from what I can tell—I've looked at the slides—there's a bullet stating that it gives them control over the launch schedule, but you all understand how difficult launch is and that delays occur fairly regularly. So wouldn't that actually get them to market faster, or are there additional factors involved in how that decision was reached?
AST strikes me as a highly innovative company, and that's what produced this blockbuster deal involving non-dilutive funding to essentially speed up our core launch services business, particularly regarding Eclipse, since we share the Miranda engine with the Blacklift launch vehicle. Now, for any launch vehicle program, the toughest piece is developing the rocket engine. Because Miranda is so mature—we're working through qualification, we've run so many hot fire tests, and we have over 4,200 cumulative seconds of hot fire testing on it—that really speeds things up for a new rocket when you begin with a mature engine like Miranda; so it's genuinely a win-win in the sense that we get to productionize our Eclipse program, and Blacklift receives these highly mature rocket engines. We'll begin by delivering the first three ship sets, so this is a win-win.
Okay, that helps and it makes sense. So as I look at this, it seems like a good deal, and I'm wondering whether there was anything you guys had to give up, right? Looking at the engine IP license, should I think about it this way: if AST eventually does 50 launches, they can build the engines themselves, and there's no revenue tied to that, because they're paying you $400 million in cash upfront for the license, so that's what you'd be giving up in exchange for that upfront cash, or is there something else?
Yeah, I just want to emphasize that this doesn't change who we are or our business model; we're still going to produce Eclipse, and we'll be able to serve all the government and commercial customers we've been working with. AST will eventually build the Miranda engines on their own, and they'll be able to use them for their Blacklift launch vehicle and support their laser focus on launching as many BlueBirds as possible for their direct-to-mobile constellations.
Okay, thanks.
Hello, thanks for asking. Regarding the AST deal and the way working capital moves, I wonder if you could explain how you expect AST funding to come through — specifically where it shows up on the cash flow statement, and whether we'll see it under working capital or under financing cash flow. And if you could also mention the other main places you expect working capital improvement this year, like the upsized CLPS 1, faster ways out of CLPS 2, or any other launch areas you find especially favorable. Thank you.
Hello, Colin. In fact, it's both. Regarding where the cash will end up, this transaction involves both cash and equity components. Essentially, we received $400 million in cash along with 10 to 14 million shares of AST Class A common stock. As for the rest, services account for $250 million, and delivery engines also come to $250 million. Consequently, everything apart from the equity will move through our operating cash. On your second question—yes, we always anticipate doing so. We believe our position is quite strong for securing additional Eclipse contracts. Historically, those have contributed meaningfully to our cash flow, and we feel very well set up for that.
Okay, understood. When you consider something like the cash flow inflection, this clearly is a big help for 2027, and with the equity rerating as well, how are you thinking about future M&A targets, between launch and particularly some of those legacy assets within launch, or growing your spacecraft business and perhaps intelligence or comms, propulsion, things like that? Thanks.
Colin, our strategy spans multiple years and we are simply carrying it out, and you witnessed that through the investments made in the lunar lander business even before it grew popular, and then the SciTec acquisition that brought us into data center work, along with all the AI defense software. We are also ramping up production of both our Alpha and Eclipse; that is a moat. Launch is a moat. It lets us launch these excellent services that our lunar landers and our Elytra orbital spacecraft provide. As we grow more autonomous with our constellations on orbit, we will be able to offer that app store on demand from space. We are simply pursuing that strategy, and M&A is one part of it. We have a robust pipeline of M&A targets; so, it is simply about executing this multi-year strategy.
Understood. Thanks very much.
Hello, Jason. Hello, Darren. Congrats on everything achieved here; regarding the FORGE products, it sounds as though you're going after several areas. Clearly, air moving missiles at present, with what you demonstrated in New York, but later ground moving and then the space domain. Jason, I'm curious whether the products needed to support those other opportunities already exist or are still being developed, so we can grasp the timeframe in which you could start monetizing them.
Yes, I mean, consider the 45 years of algorithm development behind all of national security and multiple domains. You heard about missile warning, missile tracking. You heard about space domain awareness. Ultimately, everything comes down to tracking needles in the haystack, subtracting the contrast from the backgrounds, and finding and tracking and taking custody of those hard, dim targets. Many of the algorithms can be transferred from one mission to another. The phenomenologies are an area where SciTec is really strong, since their scientists sit co-located with the software developers. When you understand the phenomenology better, you know how to build the algorithms and process the sensor data better. The short answer is yes, many of these algorithms are transferable. SciTec has plenty of R&D under development that is continually transitioning to operations. That's one of the advantages of the FORGE program, and you also heard about the Feast program. It lets us battle test our algorithms and get them really hardened, and then, once they are, we could deploy them to other mission areas.
Great, thanks for asking. On gross margins, I can see that the AST Miranda deal will provide a solid tailwind there, it sounds like, for several years. Could you remind us how we ought to think about gross margins at launch versus scaling Alpha and Eclipse? I realize those are different rev rec models, but if you could remind us, Darren, how we should think about gross margin for those two programs, that would be great. Thank you.
Yeah. Hey, Ryan. On gross margin, at present, until Alpha achieves technical feasibility, its cost is expensed in R&D. Once it reaches technical feasibility, those costs will be inventoried on our balance sheet.
Right.
From that standpoint, it moves into production. The same applies to Eclipse, which tracks a comparable path too.
Thanks, guys. I didn't catch that. Could you say again what the 2027 launch forecast was? Only joking, really. Actually, just to follow up on something you mentioned on the last call, I think you're depending on Northrop Grumman for your NSSL certification, but since their MLV differs from your Eclipse, would that be a separate certification you'd have to complete, or is that lane set aside only for Northrop?
Thanks, Chris. Yeah, we are completely focused, heads down on qualifying our Miranda engines along with our tanks and primary structure; that first stage can be used on both of those vehicles. We've stayed pretty firm on when we'll be ready to launch before we onboard onto the National Security Space Launch program. We want to be able to look the customer in the eye and say, "Hey, we are launching in this year when we onboard." So that's where our focus is. With Northrop Grumman co-developing this alongside us, we're very confident in this American-made rocket that will meet standards of National Security Space Launch as well as NASA, for the Space Force, for NASA. We want to be able to deploy a broad range of payloads for those kinds of critical missions, because I used to build a lot of those critical missions, and I know how important it is to deploy those into the right mission-unique orbits.
We appreciate everyone joining us on today's call. We're eager to talk with you once more when we share the results for our fourth quarter earnings, and we're also looking forward to connecting with you at the many investor conferences we'll be attending on the road in the weeks ahead. Speak with you shortly.
Thank you all for participating. You may now disconnect.
Read the full transcript via the API
You're viewing the first half of this call. Get the complete Firefly Aerospace Inc. transcript - plus 132,000+ transcripts from 7,000+ companies, speaker segments and full-text search - through the EarningsAPI REST API or hosted MCP server.
Get an API key View API docs →For developers and AI pipelines
Programmatic access to Firefly Aerospace Inc. earnings transcripts and 132,000+ others is available through the
EarningsAPI REST API and the hosted MCP server.
Quarterly plans from $162 - full transcripts, speaker segments, full-text search,
and the /api/v1/transcripts/recent polling endpoint for ETL pipelines.