Pilot-in-command responsibility

Syndik8 will tell you, helpfully and at the right moments, that your medical is approaching expiry. It will tell you when your ARC is approaching expiry. It will tell an admin that one of their members has a lapsed medical chip. What it will never do is tell you whether you are legal to fly today. That decision is yours, and this page explains why we drew the line where we drew it.

The legal frame: the pilot is responsible

The rules that apply depend on the aircraft and operation. For UK Part-NCO operations, CAA NCO.GEN.105 sets out the pilot-in-command’s responsibilities, including the checks before commencing flight. Syndik8 does not perform those checks or discharge that responsibility. Owners, operators and maintenance organisations also retain their own duties; the pilot’s responsibility does not remove them.

A missing reminder or a clear app indicator cannot establish that a flight was lawful or safe. The pilot must make the required checks against the actual aircraft, documents and operating conditions.

A management app that quietly assumes that responsibility on the pilot’s behalf would be doing the pilot a disservice. It would create a false sense that “the app has my back”, and the moment it fails (a sync glitch, a missed reminder, an out-of-date expiry, an unforeseen edge case), the pilot finds themselves in the position of having relied on something that wasn’t reliable in the way they thought it was.

What Syndik8 does

Syndik8 is designed to support a current pilot, not to replace their judgement:

It lets you record what’s true today. Your medical certificate, your licence, your aircraft’s insurance, the ARC, the radio licence. All on file, all visible to you, all visible to the right people.
It lets you carry them with you. The ship’s-papers cache puts the aircraft documents on your phone for the next ramp inspection.
It nudges you when something is approaching expiry. Reminders at sensible windows (60/30/7 days for medicals, 30/7/1 for asset documents) so you have time to renew.
It surfaces aggregate state to admins. The attention icons on the Members tab show admins the recorded licence/medical summary and expiry information. They do not verify qualifications, recency or fitness.

What Syndik8 deliberately doesn’t do:

It doesn’t block bookings on an expired medical. A pilot whose medical lapsed last week can still book the aircraft. Whether that booking results in a flight is a decision the pilot makes: possibly the booking is for a non-flying purpose, possibly the renewal is in hand, possibly the pilot wants to claim a slot before someone else does. The app doesn’t second-guess.
It doesn’t block flights on an expired ARC. Same logic. The pilot is in charge of pre-flight checks; the app is a record-keeper.
It doesn’t issue legal advice. “You are legal to fly” / “You are not legal to fly” is not a string Syndik8 will ever show you, because Syndik8 cannot know whether you are. There are too many factors: recency requirements, ratings, type-rating currency, alcohol, medication, mental health, recent flying hours, the conditions at the destination, the conditions en-route, the aircraft’s actual state.

“Reminders, not gates”: the design principle

For pilot paperwork, the pattern is reminders, not gates. Recorded grounding squawks and overdue maintenance items separately restrict booking availability:

A reminder is helpful, low-friction, and pilot-respectful. It says “here is something you might want to know”.
A paperwork gate would need information the app cannot establish, including the pilot’s actual privileges, recency and fitness.

The notification ladder for medicals is a reminder. The attention icons for admins are a reminder. The expiry chip in the document library is a reminder. None of these is a gate. The pilot can ignore them, override them, schedule around them, or do the thing they were going to do anyway. The reminder did its job by being visible; what the pilot does next is theirs.

What this means for admins

A common temptation, especially for admins of newer syndicates, is to wish the app would refuse to let a pilot with a lapsed medical book the aircraft. We’ve thought hard about that and consciously chosen not to build it. Two reasons:

The admin isn’t the one flying. If the admin imposes the gate via the app, and the pilot finds a way around it (a booking for a non-flying purpose; a booking made before the medical lapsed; an off-platform arrangement), the admin’s apparent control was illusory. The pilot is still responsible.
House rules belong off-platform. A syndicate that wants a “no flying without a current medical” rule has every right to it, but it’s a house rule, not a software feature. The right place for it is the syndicate agreement and the house rules. Syndik8 helps you write those rules; it doesn’t enforce them.

The one thing we do ask you to confirm

There is a single point where Syndik8 asks the pilot-in-command to put a declaration on the record. When you log an aircraft flight, the form asks Any defects? and won’t save until you have signed the line under it. The line reads “Nil defects” until you write one up, and names the count once you have.

This isn’t a gate on flying (the flight has already happened by the time you log it), and it isn’t the app forming a view on the aircraft’s airworthiness. It’s the opposite. It records your per-flight declaration, in your words, at the moment you’d make it anyway, much as a pilot signs off the tech log after a flight. The app holds the record; the judgement, and the responsibility for it, stay with you.

The tick is a signature and nothing else. It is not a second way to report a defect: a defect is described in a squawk, which you write up on the same form, and which then names the flight it came from. That is why the tick clears whenever you add or remove one — what you would be signing has changed. It is also why the app never infers the declaration from whether any defects were added: the absence of a squawk cannot tell “the pilot checked and found nothing” from “nobody recorded anything”, and the first of those is exactly what a declaration is for.

Once saved, you can’t change the declaration, and you can’t delete a log that reported a defect, unless you are also an admin of the syndicate. That way the record reflects what you attested at the time rather than anything edited in later — and, now that a declared defect is always described by a squawk naming the flight, deleting the flight would cut that defect loose from what produced it. If the answer was a mistake, an admin can correct it on the booking. The flight stays logged, with its hours and its charge, and the change is recorded with the admin’s name and any reason they give. The declaration is shown on each flight in the booking’s Usage Logs section, with the defects raised on that flight under it, so anyone who can see the flight can see both what was declared and what was found.

See Log a flight for the step, and Usage log fields for where it sits on the form.

What this means for pilots

The pleasant consequence of all this: you remain the pilot. The app is your assistant, not your minder. It helps you keep track of the things that matter; it does not interpose itself between you and the aircraft.

That implies a small responsibility on your part: don’t outsource your judgement to the reminder. The reminder is a courtesy. Whether to fly on a given day is a decision you make, on the merits, against the rules, the same way you would if Syndik8 didn’t exist.