TaskFlight
Notes from building a five-airframe maintenance trainer and flight simulator — the flight dynamics, the debugging stories, and the design decisions, written by the people who made them. No marketing copy; commit messages with paragraphs.
Every aircraft in TaskFlight — 154 selectable parts, a 2.5 km runway, the lot — is procedural geometry built in code. No downloaded models, no asset licences, no CAD provenance questions, and a first load that got lighter as the fleet grew.
Read postTaskFlight’s competency exam is generated from the maintenance records themselves — symptoms, faults, tooling and procedure steps become questions at runtime. No parallel bank to write, and none to drift out of date.
Read postMaintenance CBT and flight simulators are usually separate procurements. TaskFlight closes the loop instead: the trainee performs the maintenance, then flies the aircraft they signed off — and inherits the fault they installed.
Read postCockpit view rendered nothing. Chase and orbit were fine. The cause was two constants that were individually reasonable and jointly capable of hanging an integrated GPU — and the investigation is a lesson in what counts as evidence.
Read postThe CH-47 has no tail rotor, no torque to trim, and pedals that do something else entirely. Why our flight model branches into physics families instead of parameterising one helicopter.
Read post