The Engine Behind Boom’s Second Business: Blake Scholl on Supersonic Flight, Power and Product Control

1. Guest Background

Blake Scholl, the Boom entrepreneur interviewed in this roughly forty-seven-minute episode, is working on a problem that combines aircraft development with the economics of sustaining it. The supplied guest background identifies Boom as an American company developing a supersonic airliner and its engine. This conversation examines how that work changed when an external engine strategy broke down, and why a power-generation product subsequently became central to the company's financing plans.

Scholl's relevant experience here is his direct involvement in partnerships, technical reviews and fundraising. He says he has spent roughly a dozen years struggling with the question of how to finance a supersonic aircraft developer before it has a revenue product. The evidence supports describing that entrepreneurial experience; it does not supply a complete professional biography or establish additional engineering credentials.

His account begins with a reversal of Boom's original intention. The company initially expected to develop an engine itself. According to Scholl, its first employee, an engine designer, suggested that adapting a Rolls-Royce engine could avoid an entire development program. Industry expectations about using a major engine supplier reinforced that choice.

United and American Airlines preorders form part of the context, but they did not settle the engine question. That tension makes Scholl a useful, interested witness: he can explain the decisions from inside Boom, while his account also advances his interpretation of why the company's subsequent strategy makes sense.

2. What the Episode Covers

The interview's central business problem is the loss of an engine partner. Scholl says the Rolls-Royce relationship reached an early-2022 board discussion about approval to negotiate a contract, only to encounter leadership disruption. He describes a project losing momentum amid uncertainty over the next chief executive. Following American Airlines' preorder announcement, he says Rolls publicly ended the relationship without warning him, severely damaging Boom's fundraising and conversations with prospective partners. Approval to negotiate, however, should not be confused with a completed engine supply agreement.

Scholl offers explanations for the withdrawal that require a different level of confidence. He believes the proposed engine depended on a next-generation platform that Rolls had stopped developing, and that executive politics made Boom's potential success awkward. Those are his interpretations of the other organization's circumstances and motives. He also says Boom told American that it was working with Rolls, without presenting the arrangement as more settled than it was. The episode contains his account rather than a documentary resolution of the dispute.

The alternative involved assembling access to existing expertise. Scholl describes finding a Florida contract engineering team with former Pratt & Whitney supersonic engineers. A Brian Chesky talk about responding to crisis by returning to a company's underlying purpose helped strengthen his commitment to developing an engine under Boom's control. He dates the first sketches to around June 2022 and the public unveiling to that year's end. XB-1's first supersonic flight, in his account, came in early 2025, illustrating the distance between adopting a strategy and producing a demonstrable milestone.

The power business emerged from a technical connection recognized earlier. Scholl says engineers had explained in 2022 that supersonic engines and power turbines share demanding high-temperature, continuous full-power operation. Reports of AI electricity constraints led him to reconsider that observation in March 2025. He recounts asking early investor Sam Altman about demand for a forty-megawatt gas turbine while separately asking his engineering leader about feasibility. Strong interest and an existing technical plan prompted approximately two more months of investigation before the team committed.

Scholl describes removing the thrust-producing fan and adding turbine capacity connected to a generator to turn an approximately forty-thousand-pound-thrust engine into a proposed forty-two-megawatt power unit. Around twenty-four units could make a gigawatt-scale installation. His argument for medium-sized modules is that they balance efficiency and equipment-management complexity against the expense of providing redundancy for much larger machines; he proposes N+1 arrays.

The strategy, he says, enabled fundraising at the end of 2025 and accelerated manufacturing investment. Its commercial status remains important: when the hosts describe a large revenue stream, Scholl corrects them to revenue expected the following year. Funding aircraft development from profitable turbines is therefore the intended financial architecture, rather than an operating result established by this interview.

3. Core Views: Reasoning, Examples, and Limits

The strongest engineering argument in the episode concerns control over the space of possible designs. Scholl says the proposed Rolls engine could not support the transonic performance required for Boom's intended boomless cruise. He explains the concept as flying sufficiently high and relatively close to the speed of sound so that the boom's propagation path turns before reaching the ground. On his account, understanding that possibility was insufficient: the aircraft-engine combination also had to reach the appropriate conditions. A supplier could offer an engine while still constraining a central product ambition.

Internal development changed the available variables. Scholl recalls a roughly ninety-minute rerun of production-aircraft simulations showing that earlier optimization had already enabled the modeled boomless conditions. The team had improved the combination without immediately recognizing that an old conclusion needed revisiting. This makes a useful argument for periodically checking previously rejected capabilities after substantial design changes. It does not establish a verified operating envelope for a production airliner. The simulation account and XB-1's flight testing are separate evidence, and the interview does not supply the parameters needed to evaluate the production claim independently.

The cabin example makes the same principle tangible. A preferred, undisclosed layout required fuselage changes that, Scholl says, removed approximately one thousand miles from a four-thousand-mile design range in simulation. Rather than immediately discard the layout, the team searched elsewhere for compensating performance. It compared roughly twelve theoretically buildable engines through MakeBoom, its internally developed software, generating aircraft configurations and simulating takeoff, climb, acceleration and cruise. Scholl reports recovering most of the lost range.

The mechanism matters more than the optimism. A larger fan, he explains, can reduce noise while worsening full-speed performance; a larger core can improve transonic capability. Holding the engine specification fixed would exclude combinations that might make a different cabin practical. The lesson is to widen a constrained design search, while retaining engineering limits. Recovering most of a modeled loss is not complete recovery, and theoretically buildable configurations are not manufactured, tested products. Scholl says MakeBoom predates AI and subsequently discusses additional possibilities with AI; the evidence does not isolate an AI contribution to the reported improvement.

His financing argument similarly separates quantities that can otherwise be conflated. Total capital consumed over a company's life is different from the amount required before first revenue or a convincing proof point. A commercial aircraft developer cannot cheaply launch its complete product and then use customer growth to demonstrate demand in the same way as a software startup. Scholl also argues that repeated short runways harmed Boom's capital efficiency by making long-term engineering and organizational decisions difficult. This is an explanation of his experience, rather than proof that hard technology generally requires less total capital. Its useful contribution is to make the timing and evidentiary purpose of spending explicit.

The power business could alter both that timing and the company's access to people. Scholl believes the airliner mission attracts engineers who would be harder to recruit into a conventional turbine business. That creates a plausible connection between long-term ambition and near-term work. But mission appeal does not itself demonstrate a recruiting advantage of a particular size, nor prove that the organization can execute two product programs successfully. The interview provides his assessment rather than comparative hiring or productivity evidence.

Scholl's broader industrial critique also deserves to be read as an argument. He links Boeing's difficulties to return-on-net-assets incentives, manufacturing divestitures, quarterly earnings pressure and reduced investment in new products. He connects restrictions on supersonic flight and diminished defense urgency after the Cold War to stagnation and talent moving into software. These are hypotheses about incentives and opportunity, not an independently tested causal history. They do not justify treating his sweeping judgments about an industry's remaining employees as established descriptions.

His comparison with Concorde and Apollo brings the discussion back to durability. In his interpretation, national-prestige projects could achieve extraordinary capabilities without creating the economics to sustain them. He wants supersonic flight to return on a commercial basis. His uncertain recollection of Apollo's budget share should remain uncertain rather than become a precise statistic. The analytical question is whether an achievement has a continuing economic foundation, not whether this interview settles the history of either program.

Finally, Scholl's attention to seams, window seals and marks beneath overhead bins connects these system-level ambitions to ordinary passenger experience. He attributes the marks to people hitting their heads, treating them as clues to a design problem. Such observations can generate worthwhile questions, but they are not systematic user research. Across the episode, the productive idea is that experience, performance and business viability must constrain one another—and that each claimed improvement must retain its own standard of proof.

4. Learning and Application

A practical way to use this episode is to maintain a claim-and-evidence register. Record supplier withdrawal as an event in Scholl's account, production-aircraft boomless performance as a reported simulation result, and turbine revenue as an expectation. Then identify what would advance each claim: purchasing conditions for demand signals, manufacturing progress for capital raised, and corresponding validation for modeled performance. This prevents progress at one stage from quietly standing in for completion at another.

For a team dependent on a critical supplier, the review should examine design freedom alongside delivery risk. Which parameters are fixed externally? Which product objectives become inaccessible as a result? What expertise would an alternative require? Boom's Florida engineering team illustrates that greater control can involve contracting with existing specialists. The case supports considering internal direction when a subsystem constrains the central product; it does not establish that every component should be made internally.

For adjacent markets, follow the sequence rather than imitate the destination. Identify shared operating conditions, check customer need separately from technical feasibility, and investigate the gap before committing. In Scholl's account, continuous high-temperature operation supplied the technical connection, Altman's response supplied an encouraging demand signal, and further investigation preceded investment. An analogous project would still need to establish the changes required for a saleable product and whether the new program competes with the original mission for resources. Enthusiasm and reusable technology alone do not demonstrate profitable delivery.

Passenger objectives can likewise become testable requirements. Scholl proposes no middle seats and five minutes each for boarding and deplaning. To evaluate those goals, a team would need specified passenger and baggage conditions and clear timing boundaries. These are suggested evaluation conditions, not implementation details disclosed in the interview. Planned Starlink integration and an internal antenna offer another example of considering a service during aircraft design. The claimed avoidance of additional drag remains unsupported by measurements in this discussion; integration should be assessed through its overall effects rather than inferred from the disappearance of an external protrusion.

The MakeBoom example suggests comparing alternatives over a complete mission. Use consistent evaluation conditions, preserve the passenger constraints, and document what each configuration gives up in noise, transonic capability or cruise performance. A preferred cabin can justify exploring a larger solution space, but the search still needs performance and validation gates. Commitment to experience should not become an unlimited demand that engineering find compensation somewhere else.

Manufacturing comparisons need equally careful endpoints. Scholl contrasts eighteen months to procure a blade with his claimed ability to print one in three days. That comparison can prompt investigation of waiting time, but the episode does not establish matching materials, post-processing, inspection, certification or acceptance requirements. His twenty-four-hour design-to-component ambition, supported by reduced dependence on difficult-to-reconfigure tooling, is described as a goal he expects to reach. Track time to a physical part, time to an accepted part and sustained production capacity separately before drawing conclusions about rapid commercial or wartime conversion.

The talent lesson is narrower but usable. Scholl's account of classrooms watching XB-1 and a young girl celebrating the supersonic milestone supports making technical demonstrations visible to future participants. Organizations can use such events as educational invitations, then observe engagement and subsequent choices. An inspiring viewing experience is a plausible beginning to an engineering career; it is not evidence of a measured long-term recruitment return.

Source

• Original episode: Bringing Supersonic Flight To The People