Model · Simulate · Validate · Fly
Mobile engineering workflow ready · Desktop interface in development
Aerospace Engineering & Flight Simulation Platform
Open engineering software for rocket vehicle definition, stability analysis, trajectory simulation, recovery modelling and technical validation.
Academic reference case: UTN FR Haedo · Mecánica de los Fluidos · Grupo 07 · CDR 2026
Live Demo · Mobile app: ready · Desktop interface: in development · User Guide · Validation · Engineering Review
TRAJECTUM is an aerospace engineering and flight-simulation platform developed to bring vehicle geometry, mass properties, propulsion, stability, trajectory, recovery, validation and technical reporting into a common analysis workflow.
The repository is organized as a modular monorepo so that geometry, physics, CAD, APIs, validation, reporting and user interfaces can evolve independently while sharing a common engineering model.
The current academic reference case is based on the Grupo 07 configuration used in the Mecánica de los Fluidos integrative project at Universidad Tecnológica Nacional — Facultad Regional Haedo (UTN FRH), including PDR and CDR design-review stages.
TRAJECTUM is an independently developed software project. It is not an official UTN institutional product, endorsement, certification or publication.
- Mass properties — mass, center of gravity and configuration state.
- Flight physics — atmosphere, propulsion, stability, recovery and trajectory foundations.
- Aerodynamics — interfaces for low- and higher-fidelity aerodynamic analysis.
- CAD & geometry — vehicle geometry and engineering model integration.
- Validation — traceable engineering checks, reference cases and verification workflows.
- Reporting — reproducible technical outputs for design reviews.
- Platform interfaces — API and web layers for future interactive engineering workflows.
flowchart LR
WEB[Web / Visualization] --> API[API Layer]
API --> CORE[Engineering Core]
CORE --> PHYS[Physics]
CORE --> CAD[CAD & Geometry]
CORE --> VAL[Validation]
CORE --> REP[Reporting]
PHYS --> MASS[Mass & CG]
PHYS --> AERO[Aerodynamics]
PHYS --> PROP[Propulsion]
PHYS --> TRAJ[Trajectory]
PHYS --> STAB[Stability / Recovery]
CAD --> VEH[Vehicle Geometry]
VAL --> TRACE[Traceability]
REP --> DOCS[Engineering Reports]
| Layer | Technology |
|---|---|
| Engineering core | Python 3.11+ |
| API | FastAPI + Pydantic |
| Web interface | TypeScript + React + Vite |
| Containers | Docker / Docker Compose |
| Quality | Pytest, Ruff, MyPy |
| CI | GitHub Actions |
| Documentation | Markdown + Mermaid |
TRAJECTUM/
├── backend/
│ ├── api/ # API contracts and services
│ ├── cad/ # CAD and geometry domain
│ ├── core/ # shared engineering core
│ ├── physics/ # flight physics engine
│ ├── reporting/ # technical reporting
│ └── validation/ # verification and validation
├── frontend/web/ # TypeScript / React interface
├── data/ # engineering datasets and vehicle definitions
├── docs/ # architecture, roadmap and validation docs
├── examples/ # reproducible engineering examples
└── infra/ # development / deployment infrastructure
- User Guide — operating workflow, engineering inputs, analysis, result interpretation and current model limitations.
- Fin Input Contract — fin geometry and airfoil input conventions.
- Validation — independent cross-checks, validation scope and reproducibility notes.
- Engineering Evidence — capability-by-capability evidence, status and limitations.
- Changelog — milestone history and release evolution.
- v0.1.0-cdr Release Notes — scope, validation status and known limits.
- Licensing — public and commercial licensing scope.
- Contributing — engineering contribution and validation standards.
- Launch Kit — concise technical copy for sharing the project responsibly.
- Consolidated modular monorepo
- Initial API, CAD, core, physics, reporting and validation domains
- Web application foundation
- CI and container infrastructure
- Source-available licensing model
- Expand flight-physics models and reference cases
- Strengthen CAD / vehicle geometry workflows
- Add aerodynamic analysis integrations
- Expand trajectory and stability visualization
- Publish reproducible validation cases
- Release an interactive technical demonstration
The current CDR reference run uses RK4 2D with a 0.002 s integration step, ISA atmosphere, variable mass, the A-100 RN/KNDX thrust curve and a provisional vehicle drag coefficient of 0.345.
| Parameter | Value |
|---|---|
| Apogee | 720.45 m |
| Time to apogee | 11.66 s |
| Maximum velocity | 138.08 m/s |
| Maximum Mach | 0.406 |
| Maximum dynamic pressure | 11.64 kPa |
| CG from nose | 523.49 mm |
| CG from support point | 301.56 mm |
| CP from nose | 602.68 mm |
| CP from support point | 222.37 mm |
| Static margin | 1.26 calibers |
The independent RocketPy cross-check gives 728.60 m apogee under matched first-order assumptions; the simplified analytical estimate gives 816.0 m. CG and CP remain reference values for the current CDR configuration until closure through CAD mass properties and/or physical measurement.
TRAJECTUM uses explicit reference cases and independent cross-checks to verify numerical behavior. The current CDR trajectory has been compared against RocketPy 1.13.0 under matched first-order assumptions, with close agreement in apogee, burnout state, maximum velocity, Mach number and dynamic pressure.
This comparison is treated as an independent cross-check, not as experimental validation. See Validation for assumptions, numerical results and scope.
TRAJECTUM separates software maturity from physical-model maturity. Each major capability is tied to an explicit method, evidence source, status and limitation so that a passing build is never mistaken for experimental validation.
See Engineering Evidence for the current verification matrix.
Technical review is welcome from engineers, researchers and developers working in aerodynamics, CFD, flight dynamics, GNC, rocketry, scientific computing and aerospace software.
Current review topics include trajectory integration, aerodynamic modelling, CG/CP and static stability, propulsion-curve treatment, variable mass, atmosphere and drag modelling, validation strategy and software reproducibility.
Use Engineering Review #52 for focused technical feedback. GitHub Discussions are also enabled for broader technical conversation. If you genuinely find the project useful or promising, a GitHub star is appreciated, but concrete engineering criticism is the priority.
TRAJECTUM aims for traceability, reproducibility and physical transparency. Numerical outputs should be tied to explicit assumptions, models, units and validation evidence. Higher-fidelity capabilities should be added without hiding the engineering reasoning behind black-box interfaces.
- Current engineering focus:
v0.1.0-cdr - Development state: active engineering development
- CI: GitHub Actions
- Release history: CHANGELOG.md
- Release notes: v0.1.0-cdr
CI status is intentionally presented here rather than in the project header so that build health remains visible without dominating the technical overview.
GitHub's language bar reflects source-code volume, not developer proficiency. This repository uses GitHub Linguist attributes to keep generated files, vendored dependencies and documentation from distorting the code-language statistics.
The active application stack is centered on Python for engineering computation and TypeScript for the web platform.
TRAJECTUM is source-available under the PolyForm Noncommercial License 1.0.0.
Use, modification and distribution for permitted noncommercial purposes are governed by the public license. Commercial use requires a separate written commercial license from the copyright holder. Third-party components remain subject to their own licenses and notices.
See LICENSE, LICENSING.md and NOTICE.
TRAJECTUM
Aerospace Engineering · Flight Physics · Simulation · Validation