Aerospace engineering / FEA / Control systems

I build engineering tools that show their working.

I am studying BEng Aerospace Engineering and expect to graduate in 2027. My main interests are finite element analysis, control systems, numerical methods and the software used to examine engineering results properly.

Featured engineering project01
MeshGuard Aerospace overview showing project status, evidence summary and engineering warnings
FEAmesh-refinement evidence
Controlsingle-axis simulation
2027expected graduation
70%+current degree average

Project 01 / 2026

MeshGuard Aerospace

A local first application for assessing mesh refinement evidence, convergence behaviour and reaction equilibrium without overstating what numerical convergence can prove.

01 / Engineering problem

A result can converge and the physical model can still be wrong.

Mesh studies often produce a clean percentage change, but that does not validate loads, materials, boundary conditions or modelling assumptions. I designed MeshGuard to keep the numerical evidence and its limits visible together.

  • Editable study data and validated CSV import
  • Adjacent mesh convergence checks
  • Force and moment reaction equilibrium
  • Conditional Richardson extrapolation and GCI
  • Evidence states and inspectable calculation traces
  • Printable engineering report export
Inspect the repository

02 / Engineering method

Why I keep the calculation trace visible.

I wanted a reviewer to see the inputs, criteria and substituted values behind each result. Met, not met and not assessed remain separate, so missing evidence cannot be mistaken for a weak pass.

03 / Engineering limitation

What MeshGuard does not prove.

MeshGuard assesses mesh refinement evidence and numerical behaviour. It does not show that an FEA model is physically correct, safe, certified or universally accurate.

MeshGuard evidence states showing met, not met and not assessed results

04 / Deliverable

An engineering report that keeps the reasoning visible.

Inputs, criteria, warnings, results and calculation traces remain connected so a reviewer can follow how each conclusion was reached.

Exported MeshGuard Aerospace engineering report with inputs, results and limitations

Project 02 / 2026

AeroControl Studio

A local first controls environment for deterministic single axis simulation, scoped stability analysis, numerical time step evidence and finite PID search.

05 / Engineering problem

A smooth response curve is not enough evidence.

Time step choice, actuator saturation and model scope can change how a controller result should be interpreted. I built AeroControl to keep the scenario, numerical method and evidence state connected to every run.

  • Single axis spacecraft and pitch surrogate modes
  • Editable plant, PID, actuator and disturbance settings
  • Event aligned classical RK4 simulation
  • Scoped Hurwitz stability conditions
  • Nominal step and half step comparison
  • Finite constraint first PID search

06 / Numerical evidence

I wanted each run to be reproducible.

The application records raw and applied torque separately, preserves immutable run identities and exposes calculation traces. A passing time step comparison is numerical consistency evidence only.

AeroControl Studio time step verification comparing nominal and half step histories

07 / Engineering limitation

What AeroControl does not prove.

The spacecraft model covers one rigid principal axis. The aircraft mode is a pitch axis surrogate. The results do not establish physical model validity, global PID optimality, flight readiness, safety or certification.

AeroControl Studio control laboratory with response history, metrics and calculation evidence

08 / Deliverable

One record for the scenario, result and limitation.

The standalone engineering report carries the scenario identity, plant and controller values, metrics, constraints, warnings and calculation trace.

AeroControl Studio engineering report with scenario identity, metrics, constraints and limitations

Engineering profile

My engineering focus.

I study aerospace engineering at the University of the West of England, expect to graduate in 2027 and currently hold an average above 70%. My work combines finite element analysis, control systems, numerical methods, software implementation and clear technical communication.

01

Engineering

  • Aerospace engineering
  • Finite element analysis
  • Control systems
  • Numerical methods
  • SolidWorks
02

Software

  • React and TypeScript
  • Engineering simulation
  • Data visualisation
  • Local first workflows
  • Technical documentation
03

Commercial

  • Small business operations
  • Audience analytics
  • Technical communication
  • Content systems
  • Product thinking

Builder experience

Small business ownership

Building and operating education and e-commerce projects developed my judgement around customers, operations, delivery and the gap between an idea and a usable result.

Communication at scale

350K+ creator audience

Growing gaming and simulation channels strengthened my scripting, editing, audience analytics and ability to make technical ideas understandable without losing the point.

Professional contact

Open to aerospace and engineering software opportunities.

I am open to aerospace engineering internships and project opportunities involving FEA, control systems, simulation, numerical analysis or engineering software.