Four platforms we own and keep developing.

A charter trip is one object that six people touch. In most operations it is six objects that nobody reconciles: a quote in one tool, a schedule entry in another, a crew assignment on a whiteboard, an invoice typed from memory.

This platform makes it one live record. A request arrives by email or through a marketplace, becomes a priced and feasible quote, gains a signature, gains crew and a release, gets flown, and gets billed — without anyone re-entering a tail number.

• Inbound email and marketplace RFQs parsed into structured requests
• Pricing from the aircraft's own configuration, not a generic table
• Crew assigned to legs, so recency counts only what was actually flown
• Release gated on the things that must be true, signed by a person
• Part 5 SMS, hazard reporting and a document vault on the same record
• Invoicing and payments that inherit the trip's own numbers

• Part 135
• Part 91
• 3–30 aircraft

Manufacturer intervals are built for the average operator. You are not the average operator — your sectors, your environment and your removal history are your own, and they are the best available predictor of what comes off next.

We model your history to forecast removals, parts demand and shop load, so a visit is planned into a gap in the schedule instead of appearing in the middle of one.

• Component removal forecasting from your own recorded history
• Parts demand and inventory modelling against forecast removals
• MEL exposure: what you are carrying, and what it will cost you
• AD and service bulletin workload planned across the fleet
• Reads from your tracker; it never writes airworthiness status back

• Part 145
• Fleet operators
• Read-only on the tracker

A duty manager asks the same three questions all day: what is out of position, what is at risk, and what does it cost to fix. Most dashboards answer none of them, because they were built to show data rather than to support a decision.

• Fleet position and utilisation against plan, live
• Disruption cost modelled per option, so recovery is a choice not a guess
• Scenario comparison: swap the tail, delay the leg, sub-charter it
• Alerting tuned to the thing that changed, not to every threshold
• Honest about latency — every figure states how fresh it is

• Part 121
• Part 135
• Duty desk

Ground support equipment is becoming an electrical problem. A ramp that has just electrified half its fleet now has a charging schedule that competes with the turn plan, and usually no data about either.

• GSE telematics and utilisation across conventional and electric fleets
• Smart charging scheduled against the turn plan and the site's power limit
• Predictive maintenance for tugs, loaders, GPUs and belt vehicles
• Turn-time measurement and fuel uplift reconciliation
• The handling record that settles a dispute six weeks later

• FBOs
• Handlers
• Airports