Benjamin Weimer · engineering portfolio
Turbojet engine build
28-lbf Single-Spool Turbojet Engine (sea-level thrust)
I’m Benjamin Weimer, December 2026-graduating mechanical engineer building and documenting a small turbojet engine from subsystem design through fabrication, assembly, testing, and iteration. This portfolio is focused on showing the real engineering behind the build.
Fuel Type:
LPG Vapor
FAREC
Full authority remote engine control
LabVIEW DAQ
Data logging
Primary project
The build. A step-by-step execution of the propulsion system design process.
If not for solidifying an elite understanding of the professional engineering process, what's the point of even doing this?
To build this engine I pulled from every elements of my propulsion courses at ERAU and from the bottomless well of information and skills that can be found and adopted through self-education via textbooks and online resources.
TOP-DOWN SYSTEM OVERVIEW · CALLOUT MAP
Subsystem overview map
This top-down render starts the technical walkthrough.
Overview · callouts · exploded subassemblies
GRound-up design: Integrating
01 · Start from the top-down layout so the full engine, enclosure, support systems, and service access are easy to orient.
02 · Use callouts to identify high-value areas: compressor path, combustion hardware, fuel delivery, ignition, controls, and instrumentation.
03 · Open selected callouts into exploded subassembly diagrams with individual components, interfaces, and manufacturing details.
04 · Oil supply, storage, and cooling subsystem to support HX40 journal bearing oil demand.
05· Custom ignition magneto designed and tested to power 40kV electrode igniter.
06 · Design, iterate on, and build custom Full Authority Remote Engine Control (FAREC) station out of pelican case. Integrate with mil-spec style multi-pin connectors and build primary control wiring harness.
Subsystem overview
Subsystems of particular interest.
Compressor
Impeller, diffuser, inlet geometry, flow path decisions, clearances, and packaging details.
Combustor
Flame tube, injector layout, air holes, liner strategy, thermal behavior, and assembly access.
Turbine / Nozzle
Nozzle guide, turbine wheel fit, hot-section interfaces, alignment, and exhaust geometry.
Fuel + Ignition
Fuel delivery, ignition setup, sensor points, test safety, and control considerations.
Detailed images
Turbojet subsystem overview for a quick technical read.
Image-ready subsystem cards
Compressor photos / CAD
Compressor + diffuser
Show impeller choice, inlet geometry, diffuser details, clearances, and how the air path is packaged into the casing.
Combustor liner / injector
Combustion chamber
Document the flame tube, air-hole pattern, injector location, liner strategy, heat management, and service access.
Turbine / nozzle images
Turbine + nozzle
Show the hot-section interface, nozzle geometry, wheel fit, exhaust path, alignment details, and inspection points.
Fuel system photos
Fuel delivery
Cover pump choice, injector routing, metering approach, safety considerations, test setup, and revision notes.
Ignition / controls
Ignition + controls
Show the spark setup, wiring, sensor points, control logic, startup procedure, and safety interlocks.
Test stand / run data
Testing + iteration
Document test stand setup, instrumentation, run observations, failure modes, and what changed after each iteration.
About me
I’m Ben — a hands-on engineer who likes making complicated machines understandable.
This turbojet build is how I like to work: learn the physics (from my Propulsion-track ME coursework, ME417 Advanced Propulsion), model the system (Excel, MATLAB, LabVIEW), prototype then make the parts, test honestly, and document the decisions. My whole life I've been insatiably drawn to machines; the natural conclusion was building a turbojet engine for my research and frankly curiosity purposes.
Engineering approach
Curious, practical, and build-driven
As a person
I'm addicted to proving the world wrong. When I'm told that a project should cost a million dollars and require massive bureaucratic bloat, I say "I think I can do that myself with $5k."
As an engineer
There's an intersection between functionality, performance, aesthetics, and ease-of-use that I'm very drawn to the pursuit of. You'll notice in my designs these themes intersecting with frequency.
Build first
I could take courses trying to predict what I need to learn for ages, but I prefer to try building something, then learn what I discover a need for.
Exceptional documentation
Why do something if you can't walk away with beautiful and functional documentation?
Iterate like a madman
Stuff really shouldn't take as long as it seems to in the engineering world.