Lightcone Ledger
Flight release depends on aircraft, crew, route, authority, procedures, and current conditions. Separate tools make the reason behind a decision hard to preserve.
Commercial pilot / founder / systems builder
I am a commercial pilot, founder of Lightcone Systems, and product builder working across AI automation, API integration, and operational UX.
Four working areas
Real software, interfaces, and tools built for operational work.
Selected work
Each case study starts with the problem, then shows the system and the result.
View all workFlight release depends on aircraft, crew, route, authority, procedures, and current conditions. Separate tools make the reason behind a decision hard to preserve.
Important decisions, research, and working context scatter across files, messages, tools, and individual AI sessions.
Radiosonde recovery data arrives as separate reports. A hunter needs a clear way to find likely landing areas and inspect the supporting details.
A list of hex values does not show whether a palette will work across real interface roles, contrast needs, and brand combinations.
Latest public record
The record mixes current work with the repositories, essays, and appearances that show how the work developed.
View the full recordRepository / GitHub
Published the TypeScript code for a combined NOAA weather, radar, forecast, and aviation display.
External article / LinkedIn
A public scenario analysis for BVLOS operators preparing for a changing regulatory path.
Repository / GitHub
Published a physics-based Python simulator for detect-and-avoid and fixed-wing autonomy experiments.
Essay / This site
An argument for practical software and evidence tools alongside new BVLOS rules.
The longer pattern
I have spent years moving between aviation, software, hardware, publishing, and AI. The common thread is practical: make a difficult system legible enough to use.
Have a real operating problem that needs a clear software system?
Start a conversation