Append only audit ledger
Every consequential action is written once and retained with the actor, the device and the time. Corrections are recorded as corrections, never as silent edits.
Features
Cooman is a single integrated aviation management system rather than four products sold together. Flight operations, continuing airworthiness, maintenance execution and the commercial side read and write the same aircraft, the same component tree, the same people and the same calendar. What follows is what each module does.
Everything between a customer asking for an aircraft and that aircraft being legally able to leave. Dispatch holds the plan and the gates, and it refuses to produce a movement that the regulation would not allow.
Capture the enquiry with route, passengers, payload and dates, price it from the aircraft's own cost model, and convert an accepted quotation into a confirmed schedule without retyping it.
A single planning board across the fleet showing commercial commitments, maintenance inputs and unavailability together, so a trip is never planned onto an aircraft that will be in the hangar.
Assign commanders, co-pilots and cabin crew against licence validity, type and route currency, medical expiry, recurrent training and flight duty time limitations. An illegal assignment is refused at the point of making it.
Route, alternates, fuel policy, reserves and endurance, with the operational flight plan and the ATS flight plan produced from the same figures.
Weight and balance against the aircraft's current basic weight, with the load sheet generated and filed as part of the flight record.
A controlled register of airports, helipads and unprepared sites with coordinates held to survey precision, approvals, site notes, and NOTAM and weather context on the same screen.
Manifests with identity details, special handling and dangerous goods declarations, carried into the load sheet and the flight file.
Fuel uplift, handling agents, permits, landing and parking arrangements recorded against the sector and priced into the trip.
A single decision point that reads the airworthiness position, the open defect list, the MEL, the crew legality and the CRS. If any of them says no, the flight cannot be released.
The day as it actually happens. Operations is where the plan meets weather, defects, delays and customers, and where the record of what the aircraft did is created.
One board showing every aircraft, its current sector, its airworthiness status and what is holding it, with a live fleet map for rotary and fixed wing movements.
Block and flight times, landings, cycles, fuel and crew, posted from the aircraft. This is the entry the rest of the system is computed from.
Pilot and engineer defect entries raised at the aircraft, with MEL and CDL deferral, rectification limits and the deferred defect list visible to dispatch.
Duty, flight time, rest and cumulative limits tracked continuously rather than reconstructed at the end of the month, with projections for the roster ahead.
Reason coded delays, diversions, cancellations and AOG events, with the operational and commercial consequences captured at the same time.
Uplift against burn per sector and per aircraft, with variance visible where it matters rather than buried in a monthly total.
Contracts, rate cards, minimum guarantees and positioning charges applied to flown sectors, producing an invoice from the flight record rather than a re-entered summary.
Occurrence, hazard and voluntary reports raised from any device, routed to the safety manager and tracked through investigation to closure.
Utilisation, dispatch reliability, on time performance, revenue per hour and fleet availability, all derived from the same records that the regulator would inspect.
Continuing airworthiness management, computed from the flights the operation actually flew. The airworthiness position is never a reconstruction, because the flights and the components are the same data.
AD applicability assessed against the aircraft and component effectivity, with recurring compliance, next due calculation and the compliance record held as evidence.
SB evaluation, embodiment decisions, modification and repair records and the resulting configuration change, all on the aircraft's history.
The approved programme held as executable tasks with hours, cycles, calendar and multiple threshold intervals, revision controlled with the approval reference.
Forward projection of every due item against planned utilisation, so the next input is known in weeks rather than discovered on the day.
The full component tree with serial numbers, installation and removal history, time since new and overhaul, shelf life and life limited part status.
Engine and APU life, trend monitoring inputs, cycle counting and on-condition parameters kept alongside the airframe record.
Repetitive defect detection, ATA chapter analysis, removal rates and the reliability report the programme review needs.
ARC and Certificate of Airworthiness renewal supported by a document pack assembled from the live record instead of collected by hand.
Controlled maintenance data, manual revisions, weight schedules and certificates, versioned and retained with the aircraft for its whole life.
Maintenance execution for a CAR-145 or Part-145 organisation, working on the same component tree the CAMO plans against. What the hangar does is immediately what the airworthiness position says.
Scheduled inputs, defect rectification and customer work raised as work orders, with the pack built from the maintenance programme and the open defect list.
Task cards worked and signed at the aircraft, with independent inspection where the task demands it and the signature bound to the person by a second factor.
CRS issued only when every task in the pack is complete and signed, producing the certificate and releasing the aircraft in one action.
Time booked against tasks by engineer and by trade, giving real estimates for the next input and a defensible basis for customer billing.
Serialised and batch controlled stock, bin locations, shelf life, quarantine and unserviceable segregation, with issue and return against the work order.
Release documentation held with every part, so the chain from supplier to installed position is complete and can be produced on request.
Tool register with calibration due dates and issue control. A tool out of calibration cannot be booked to a task.
Scope of authorisation by aircraft type, task category and rating, with expiry and continuation training tracked. An engineer cannot sign outside their scope.
Requisitions, purchase orders, repair and overhaul orders with vendor approval status, turnaround tracking and cost against the job.
Line and base maintenance for other operators, quoted, executed and invoiced without mixing their records with your own.
Internal audit programme, findings, corrective actions and the evidence trail an oversight audit asks for.
Hangar and bay capacity, shift handover notes and job status, so the next shift starts from where the last one stopped.
The platform
These are not features of one module. They are properties of the system, and they are the reason the records hold up when somebody asks to see them.
Every consequential action is written once and retained with the actor, the device and the time. Corrections are recorded as corrections, never as silent edits.
Certifying actions are confirmed with a second factor on the signer's own device, binding the signature to a person rather than to a session someone left open.
One deployment, many organisations, each seeing only its own records. Isolation is enforced in the database, not left to application code to remember.
Roles that match the exposition: Accountable Manager, Quality Manager, CAMO post holder, certifying staff, planner, commander, storekeeper and dispatcher.
The mobile app records at the aircraft with no network and reconciles when the link returns, so a remote helipad does not delay the record.
Controlled document numbering and generated PDFs carrying the operator's own mark, for flight plans, load sheets, work packs, CRS and invoices.
Weather and NOTAM feeds, accounting export, single sign on and a documented API for the systems you already run.
Airworthiness records retained for the life of the aircraft and beyond it, in the form an audit expects rather than a database dump.
Delivered as a managed service, or deployed inside the operator's own environment where a regulator or a contract requires it.
Next step
The fastest way to judge Cooman is to see it hold your own aircraft. We will load a type, a programme and a roster, and show you the gates the system produces from them.