Integrated Aviation Management System
Cooman runs Dispatch, Flight Operations, Continuing Airworthiness and Maintenance on a single record. A journey log posted on the ramp advances component life, consumes a maintenance interval, accrues crew duty time and raises the client invoice. No re-keying, no month-end reconciliation, no spreadsheet that disagrees with the aircraft.
Built for NSOP and scheduled operators, CAR-145 and Part-145 stations, and CAMO organisations. Multi-operator by design.
Every downstream figure is derived, never typed twice. The audit ledger records who posted it, from which device, and when.
Four modules, one record
Each module is complete on its own and none of them is an island. They read and write the same aircraft, the same component tree, the same people and the same calendar.
Turn a request into a legal, costed, crewed and fuelled flight, and do it in one screen instead of six.
One board for the day: where every aircraft is, what is holding it, and what happens next.
The airworthiness position of every aircraft, always current, because it is computed from the same flights the operation flew.
The hangar floor, the stores and the certifying staff, on the same component tree the CAMO plans against.
The design principle
An expired Airworthiness Directive, a pilot out of currency or an unsigned Certificate of Release to Service is not a reporting problem. It is a grounding event. In Cooman the regulation is an executable code path, so if a flight is not legal the release button does not work.
Every block carries its reason, the rule it came from and the person who can clear it. Nobody has to read a report to find out that an aircraft should not have flown.
The platform underneath
Nothing of consequence is edited in place. Every certifying action, correction and approval is written once and kept, with the actor, the device and the time. An audit asks for evidence and the system already holds it.
A release, a CRS and a journey log entry are signed with a second factor on the signer's own device, so the signature is bound to a human being and not merely to an open session.
One deployment serves many organisations. An operator, a CAR-145 station and a CAMO each see only their own records, enforced in the database itself rather than in application code.
Accountable Manager, Quality Manager, CAMO post holder, certifying staff, commander, planner and storekeeper. Permissions follow the exposition, not a generic admin and user split.
Flight plans, load sheets, work packs, CRS and invoices are generated from the live record with the operator's own mark, ready to file and to hand to a regulator.
A documented API, weather and NOTAM feeds, accounting export and single sign on, so Cooman sits inside your estate instead of beside it.
Cooman Field
Pilots close the journey log on the helipad. Engineers raise and clear defects at the aircraft, sign a task card with biometrics and photograph the evidence. Nothing waits for someone to reach a desk, and nothing depends on a signal being there at the time.
The field app signs in with your operator's Cooman account.
Talk to us
We will walk one of your aircraft through a full cycle: a trip request, a roster, a release, a journey log, the maintenance it triggers and the invoice that follows. Bring your maintenance programme and your exposition, and we will show you the gates it produces.