Canada should be able to develop and maintain the software used in its defence. We want to contribute by choosing a problem we can examine closely and working through it in detail.
Uncrewed flight planning offers that starting point. A request has a route, a schedule and aircraft limits, and it must fit around other activity. When a conflict appears, someone needs to understand why it matters and what could change.
Choose a task with a clear result
For Aerlattice, the useful result is a flight request that a person can inspect and review. That gives the product a concrete purpose and gives us specific questions to answer about the interface and calculations.
Can a reviewer connect a finding to a particular part of the route? Can they compare a detour with a later departure? Can they return to the decision and understand which information supported it?
Learn through the work
Those questions give us a basis for developing the application and testing its behaviour. They also help keep the scope manageable while we build expertise in the underlying problem.
A Canadian contribution can begin with a focused tool. Its value will come from how well it serves the people using it and how reliably we can keep improving it.
