CamoBook was born at an airfield, not in a software house

Who writes it

CamoBook is written by Paweł Mamcarz (mamcarz.com) and published by his business, Doradztwo Paweł Mamcarz. The same business runs Akrobacja.com: aerobatic flights and training on an Extra 300L from Radom-Piastów airfield. This is not a software company that picked aviation as a market — it is an operator who wrote a tool for himself.

The Extra 300L leaves no margin for error in maintenance: high loads, demanding hardware, life limits running simultaneously in hours, cycles and calendar days. A single aircraft can still be kept in a notebook — as long as nobody makes a mistake and nobody falls ill.

The second point of reference is Heli Solution — a separate company and an operational partner, a helicopter pilot training organisation in Jedlińsk, at Piastów airfield. Its training fleet, a Guimbal Cabri G2 and a Robinson R44, flies a lot, in short flights, with crews changing constantly. Heli Solution neither publishes nor co-owns the system; it is the place where CamoBook had to survive a pace one aircraft never imposes.

Both worlds share the same thing: responsibility for keeping an aircraft airworthy — and first-hand knowledge of how much paperwork stands behind it.

The problem we could no longer work around

Keeping an aircraft airworthy is not one document. It is the technical log filled in after every flight, counters that must match to the minute, life limits running simultaneously in hours, cycles and calendar days, defects and their deferrals, airworthiness directives and service bulletins, inspection and ARC deadlines, crew qualifications — and, at the end, the duty to present all of it to the authority as one coherent record.

In practice: a paper log in the cockpit, a spreadsheet at the maintenance desk, deadlines in someone’s head, bulletins searched manually on manufacturers’ websites, and the same flights typed in twice — once into the log, once into the training system. Every one of those places had a life of its own, and every one could drift.

The worst part was not the retyping. It was the uncertainty: is the counter I am planning the next inspection from actually up to date?

A look at what already existed

Before the first line of code, we looked at what was available. Some systems keep a good technical log but know nothing about life limits. Others track life limits very well, but flight data has to be imported and manually verified — so the problem comes back through the side door.

None of them closed the full loop: from the pilot’s entry after landing to the answer whether the aircraft may fly tomorrow. And that is exactly the stretch where the currency of the data gets lost.

So the system got built

CamoBook is built around one principle: one chain of data, no retyping.

The pilot closes the technical log entry and signs it electronically. At that moment the counters move, life limits are recalculated, and the maintenance and airworthiness staff see the current state of the fleet. The aircraft status comes back to the pilot before the next flight — not after it.

Who it is for

For operators like the ones this was built on: flying clubs and training organisations, helicopter operators, single-aircraft owners and continuing airworthiness management organisations. For everyone still holding this together with a notebook and a spreadsheet — and knowing it will eventually catch up with them.

This is not the product of a software company that picked aviation as a market. It is a tool an operator wrote for himself — and took to the point where it can be handed to others.