The problem
Aircraft positions become useful only when traffic, weather, hazards, trajectories, and time are understood together. Live data also makes interface behavior difficult to review consistently from one session to the next.
Selected work / 02
Flight Tracker AI
A browser-based aviation intelligence system that brings live or replayed traffic, weather, hazards, trajectories, and explainable attention cues into one map-led interface.
- My role
- Independent product engineer
- Scope
- Product design, frontend engineering, and Rust service integration
- Stage
- Deployed read-only portfolio demo
- Core technologies
- Next.js · TypeScript · Rust + Axum · PostgreSQL + PostGIS
Case study
Making a dense air picture understandable and reviewable.
What I built
I built a map-led portfolio demo with live and replay traffic, regional weather context, selected-aircraft detail, route comparison, and explainable attention cues. A typed browser interface connects to a Rust service and spatial data layer.
Key decisions
- 01Live when available, repeatable when needed
The same workspace supports current regional traffic and deterministic scenarios that can be replayed during design and engineering review.
- 02Keep the primary question spatial
Traffic, weather, trails, and route context stay anchored to the map while supporting detail remains close enough to inspect without losing place.
- 03Explain why something needs attention
Priority cues expose the contributing conditions and rule result instead of presenting an unexplained score or model judgment.
Inside the work / 04 views
Live traffic, replay, and route context
The map-led workspace brings regional traffic and weather together, deterministic replay makes the same interface reviewable on demand, and focused comparisons explain route tradeoffs without leaving the product.
Deterministic replay workspace
A repeatable scenario combines the replay clock, telemetry, weather evidence, route context, and explainable attention scoring in one reviewable state.
Route comparison
A focused comparison translates modeled hazard clearance and added distance into a concise, readable tradeoff.
Mobile replay
A compact replay view preserves the scenario clock, tracked-aircraft state, and core telemetry on a phone-sized canvas.
Technical view
Architecture
Live providers and deterministic fixtures enter one Rust domain service; the browser receives a sanitized, read-only air picture.
surfaceservicedataaiintegrationcontrolruntime
Read system connections
- Aircraft positions → Ingestion + normalize
- Aviation weather → Ingestion + normalize
- Weather imagery → Interactive airspace
- Base map → Interactive airspace
- Ingestion + normalize → Spatial record
- Ingestion + normalize → Spatial engine
- Spatial record ↔ Spatial engine
- Replay fixtures → Spatial enginereplay
- Spatial engine → Attention policy
- Attention policy → Constrained wording
- Attention policy → Public read API
- Constrained wording → Public read API
- Public read API → Interactive airspace
Built so far
- Supports both live and deterministic replay modes so product behavior can be reviewed without depending on current air traffic.
- Connects aircraft, trajectory, weather, and hazard context in a single geospatial product surface.
- Uses a typed browser-to-service architecture with a Rust API and a spatial database.
Where it stands
- The product is a portfolio demonstration, not a certified aviation system.
- It is not intended for flight planning, dispatch, aircraft control, or operational decision-making.
Continue exploring
Next case study
Audio software / DSP
Wave Factory Essentials
Pre-release tester builds
Open case study