entity Updated 2026-07-23 Tags: Company, Aerospace, Hard-Tech, Aviation

Boom Supersonic

Boom Supersonic is Blake Scholl’s commercial supersonic-aircraft company in Blake Scholl, Founder & CEO of Boom Supersonic. The episode presents Boom as an attempt to revive passenger supersonic flight through a startup de-risking sequence rather than a government prestige program or a conventional aerospace incumbent project.

Boom’s first durable idea in the source is the All-Business-Class Supersonic Model: target travelers already paying business or first-class fares, make the flight short enough that passengers need less sleeping space, and use the cabin-density gain to support better economics than Concorde. This made the first market transoceanic premium travel, not overland boomless flight.

The company-building arc then moves through Hard-Tech Customer Intent Proof and Hard Problem MVP Scoping. [[VirginGroup|Virgin]] gave Boom a public customer-intent signal before the company had a passenger aircraft, while [[XB1SupersonicDemonstrator|XB-1]] gave the team a prototype platform for learning supersonic aircraft design and proving execution before [[OvertureSupersonicAirliner|Overture]].

The source’s most important strategic turn is the [[RollsRoyce|Rolls-Royce]] engine crisis. Scholl says Boom initially pursued a traditional engine supplier for credibility, but the break forced Crisis-Forced Vertical Integration. In his account, owning the engine path later enabled Boomless Cruise, better economics, and future product options that the supplier route would not have supported.

Source Position

  • The source argues that Concorde’s failure should not be generalized to all passenger supersonic travel.
  • Boom’s first model did not require solving sonic boom because the initial route set could be mostly over water.
  • Scholl says the company’s own engine path later made boomless cruise practical without changing the aircraft.
  • The passenger timeline, regulatory-reversal claim, airline-order status, and undisclosed engine-enabled benefits should remain source-scoped unless independently checked in a later source.

Connections