Cooman is the flight management application for aircraft operators. It is used by an operator's own crew and staff, at the aircraft and in the operations room, alongside the web console that holds the records.

This is not consumer software. There is no public sign-up and nothing to browse without an account. You sign in with credentials your operator issued and a second factor: an authenticator code, or a one-time code sent to your address. If your operator does not run Cooman, this application will do nothing for you.

FOR A PILOT

Today: the sectors you are flying, drawn on a map, with anything needing your attention lifted above them: an unfiled log, a lapsed check.

Your currency: the licence, medical and training register the operator holds against you, and when each falls due. The certificate for a completed check is scanned into a document on the phone and handed in for a post-holder to verify. Handing evidence in does not move a due date; only a verification does, and you are told either way.

The journey log, per sector, recorded and filed on the aircraft. Filed hours move component life, so the log posts through the same rule the desk is held to.

A snag, raised against the aircraft you have just flown.

FOR AN ENGINEER

Your own regulatory record: the authorisations the operator holds against you, what each covers and what it lets you sign. Nothing is submitted there, because an authorisation is granted and withdrawn by the operator, not renewed by you.

A defect, reported at the airframe where you found it. A report records what you saw. It defers nothing and clears nothing, and the base assesses it.

FOR THE BASE AND THE DESK

The open defect register across the fleet, filtered to the aircraft you are dealing with.

What is outstanding against you across whichever registers your role reaches, and which of them your account was not allowed to read.

THE OPERATIONS ROOM

The Command Centre puts the day's flying on one map: every aircraft at its position or at its base, carrying both verdicts side by side, whether dispatch will release it and whether it is airworthy. Two desks, two decisions, and the screen refuses to average them. Pilots whose paperwork falls due inside the window are named alongside, as a name and an urgency and nothing further.

Positions are derived from the filed schedule and from reported off-blocks and on-blocks times. This is not a surveillance source. There is no radar, no ADS-B and no tracker behind the map: the symbols show where the schedule says an aircraft should be, not where it is, and the map prints that on its own face.

ONE BUILD, THREE SURFACES

The same application draws a pilot's phone, a tablet at the hangar door and an Android TV panel on an operations-room wall, from one build on one Play track. On the wall it holds the screen awake and cycles through the day's sectors on a timer, because nobody in an operations room is holding a remote.

WHAT IS NOT IN THE APP YET

Signing a release certificate, accepting a part against its Form 1, and approving a purchase or repair order each have a tab, and each tab says in as many words that it is not built yet and that the work is done on the web console today. They are named here so nobody arrives expecting them.

Nor is there a barcode to scan against a part, a voice note against a defect, or an offline mode. The application needs a connection, and nothing is queued on the device to send later.

THE REGULATORY FRAME

The records follow what an Indian operator works to: DGCA CAR requirements, and the operator's own Operations Manual and Exposition. Cooman is a record-keeping and coordination tool for the staff who hold those approvals. It holds no approval or certification of its own, and it reaches no airworthiness or dispatch decision: every verdict it shows was reached by a person, or by a rule the operator configured, on the operator's server.

Published by Akam Innovations, Chennai, Tamil Nadu, India.

Akam Innovations

Additional Information