GENESIS VENTURES

EXPORT CONTROL: ALL WORK SCREENED AGAINST ITAR/EAR. GENESIS SELLS DESIGN PACKAGES, NOT HARDWARE.

PROPULSION: LIMITED-LIFE ENGINES

Attritable turbojet design.

Genesis Ventures designs limited-life and expendable turbojet engines as fixed-scope packages: a closed cycle, release geometry and a declared check matrix, engineered against the unit-cost target the procurement category actually imposes. Design packages, not hardware. Every engagement is screened against ITAR/EAR before scope is frozen.

What limited life trades

Design life, unit cost and TSFC are one trade space. Pick two honestly and the third follows.

A conventional small turbojet is priced by its life, not its thrust. The engineering that makes an engine survive a thousand hours (bearing margins, superalloy hot sections, recirculating oil systems, inspection access) is most of what the unit costs. Attritable aircraft propulsion starts from the opposite premise: the airframe is not coming back, or is not expected to, so the engine’s design life is a requirement to be set, not a number to be assumed.

Set design life to 100 hours and the trade space moves. Set it to 50 hours and it moves again. What does not move is the thermodynamics: an expendable turbojet still lives or dies on its cycle. Pressure ratio, turbine inlet temperature and mass flow decide the fuel burn, and the fuel burn decides whether the vehicle closes its mission. The art is holding the cycle at long-life quality while stripping the life-support out of the hardware around it.

That is the distinction a serious design package has to make explicit: which margins were sized to the mission and which were kept. The wrong way to buy an expendable turbojet is to accept a lower TSFC target in exchange for the shorter life: fuel burn is set by the cycle, and the cycle costs nothing extra at the design desk. Giving up specific fuel consumption to hit a unit-cost target is a hardware decision masquerading as a thermodynamic one.

Below is where a 100-hour or 50-hour engine genuinely differs from a 1,000-hour one. Each trade is legitimate exactly because the design life was stated first.

  • Bearings & shaft system

    A 1,000-hour engine carries bearing life margins, contamination tolerance and an oil system designed for hundreds of thermal cycles. A 100-hour engine sizes bearings to the mission with a declared margin, not a fleet-life one; a 50-hour engine can accept rolling-element choices and lubrication schemes that no long-life program would sign. The shaft and bearing structure get lighter, cheaper and faster to make, and the trade is stated in the package, not hidden in it.

  • Hot-section materials

    Turbine inlet temperature sets the fuel burn, and the hot section sets what that temperature costs. Long-life engines pay for single-crystal blades, thermal barrier coatings and cooled hardware to hold creep and oxidation at bay for years. A limited-life engine holds the same temperature for hours, not decades: directionally solidified or conventionally cast alloys, simpler coatings, less cooling air bled off the compressor. The TSFC stays; the material bill does not.

  • Oil & fuel system

    Recirculating oil systems with scavenge pumps, filters, coolers and chip detectors exist to protect a long life. At limited life the system shrinks toward the minimum that survives the envelope (sometimes a total-loss scheme) and every removed component is unit cost, mass and a failure mode deleted from the bill.

  • Inspection burden

    A long-life engine is designed to be inspected: borescope ports, modular strip-down, life-limited parts tracked per serial number. An expendable turbojet is designed to be accepted, not inspected: the verification happens once, at design release and at acceptance, against declared checks. The sustainment tail that dominates the cost of a reusable engine simply does not exist.

  • Cost structure & lead time

    Long-life hardware drags long-lead processes with it: single-crystal casting, coating lines, extensive acceptance testing. Limited-life design reopens every one of those choices. The package states the resulting cost basis per component, so the buyer can see which decisions bought the unit-cost target and what each one is worth revisiting if the requirement changes.

A category, not a derate

“Attritable” is a procurement category. Treating it as a derated long-life engine is how programs overpay.

The lazy version of expendable propulsion is an existing engine with the life-limiting parts swapped for cheaper ones and the nameplate left alone. That buys a worse long-life engine, not a good expendable one. The design requirements were never re-opened, so the cost structure of the original life requirement survives inside the new article.

Done properly, the procurement category is the requirement. The buyer states the design life, the mission envelope, the acceptance standard and the unit-cost target; the engine is then closed against those constraints from the cycle outward. Bearing life, hot-section material, oil-system architecture and inspection provisions are consequences of the stated life, each one traceable to it. Where the trade cuts into reliability, the cut is declared in the package with its basis: the buyer sees exactly what the unit-cost target cost in engineering margin.

This is also why the category rewards a fixed-scope engagement. The question “what does a 100-hour, 13 kN-class engine look like at this cost target” has a closed, checkable answer: a design point, a geometry and a check matrix. It does not require an open-ended development program to find out.

It is worth saying what the category is not, as well. Attritable does not mean crude. A one-way article still has to start reliably, hold its fuel schedule across the envelope and meet the acceptance standard on every unit. At volume, a two percent failure rate is a fleet problem, not a footnote. The engineering discipline is the same as any other engine program; only the life requirement changes. Design life stops being an assumption inherited from the last program and becomes a declared parameter with a number attached, and every life-driven decision in the package traces back to it.

Proof: the pipeline closes real design points

The Orion engine is the published reference release from the same pipeline a limited-life package runs on: a 13.34 kN single-spool turbojet concept closed against declared constraints, with every figure checked against a threshold that existed before the run.

The screening trail is the part worth reading. The supplied baseline ran an overall pressure ratio of 4.2 : 1 and a TSFC of 125.3 kg/(kN·h). A prescribed screening point at 8.5 : 1 missed the TSFC target at 105.0, and stayed on the record. The selected point, 11.0 : 1 at a 1320 K turbine inlet temperature, closed at 99.3 kg/(kN·h): 20.8% below baseline, with positive margin to the ≤ 100 target the brief had frozen.

The cycle deck did not stay on paper. The Orion-T1 airframe carried the same engine deck into six scripted 6-DoF air-start tests and passed six, with the installed fuel burn landing at TSFC 129.0 against a cycle prediction of 128.9, inside the ±10% corridor the test card had declared. For a buyer, that is the difference between a promise and a pipeline: the numbers a limited-life package hands you are the kind that survive contact with a flight model.

Off the design point, the same release publishes the anchors a mission planner actually uses: 7.93 kN at 5 km and Mach 0.40 with a TSFC of 115.1, and 5.01 kN at 10 km and Mach 0.70 with a TSFC of 123.7: the nozzle solved at the design point and held fixed, choked at every published condition. A limited-life package delivers the same shape of deck for your envelope, so range and loiter calculations run on evaluated tables rather than a brochure figure.

Nineteen automated checks (thrust, TSFC, mass, envelope, shaft-power balance, choking) all passed against declared thresholds, 19 of 19. The full release, including the rejected design point and the altitude × Mach deck, is on the Orion project page.

The segment

Where expendable turbojets actually fly, stated factually.

The established buyers of limited-life turbine propulsion are cruise missiles, loitering munitions and recoverable target drones. The first two categories are one-way articles: the engine’s entire useful life is a single mission measured in minutes to hours, which is precisely the regime where long-life engineering is pure cost. Target drones come back, but they are flown to be shot at, so fleet life is short and attrition is a planning assumption rather than an accident.

Across all three, the propulsion requirement reads the same way: a declared design life, a thrust class set by the vehicle, a fuel burn that decides range or loiter time, and a unit cost that decides whether the procurement maths works at volume. That is an engineering specification, and it is answered with a design package, not with a derated heirloom engine.

The volume point deserves emphasis, because it changes what “good” means. A reusable-engine program can amortize engineering over decades of service; an attritable program amortizes it over a production run, and every dollar of unit cost is multiplied by the size of that run. Design decisions that look marginal on a single article (a coating step, a forged part where a casting would do, an extra pump) become line items with five-figure consequences at volume. Getting the design life right at the requirements gate is the cheapest cost control the program has.

Genesis Ventures works the design side of this segment only. Engagements are screened against ITAR/EAR before scope is frozen, and the deliverable is the design package: cycle, geometry and declared checks.

The fixed-scope package

What a buyer holds at the end, scoped at the requirements gate, priced before the run.

A limited-life engine package runs the same gates as every Genesis engagement: objectives and thresholds frozen before any solve, the cycle closed against them, geometry generated from the closed solution, every published figure checked against the declared matrix. The deliverables:

  • 01A closed design point against your constraints: thrust, TSFC, OPR and mass flow, with the screening trail and every rejected point on the record
  • 02An engine cycle deck: altitude × Mach tables evaluated from the cycle solution, ready for your flight model
  • 03Release geometry generated from the closed solution: the shape is the answer, not an illustration of it
  • 04A check matrix with thresholds declared before the run, and the measured value against each one after it
  • 05A component-level mass budget with a declared material basis per component

Design life, thrust class and the unit-cost target are set in the brief; the rejected points and the margins stay on the record in the release. Where a package lands relative to a long-life reference, the difference is itemized: material basis per component, life assumption per rotating group, acceptance standard per check. The five-gate sequence is on the method page.

Start here

Bring the design life, thrust class and unit-cost target. The intake takes under five minutes.

START A DESIGN INTAKE →