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 Air Navigation Order is the UK’s primary aviation regulation, and it puts the responsibility for currency on a specific person: the commander of the aircraft. The pilot-in-command must, before flight, satisfy themselves that the aircraft is airworthy, that the pilot is qualified and current, that the necessary documents are aboard, that fuel and weight and balance are within limits. The list goes on. It is, by design, a pilot’s responsibility: not the syndicate’s, not the maintenance organisation’s, not a piece of management software’s.

When something goes wrong and the CAA asks who was responsible, the answer is the pilot. The pilot’s defence is not “the app didn’t warn me”. The pilot’s defence is the work they did before they pushed the throttle forward: the documents they checked, the briefing they took, the limits they respected.

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/14/7/1 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 tell admins which pilots are current and which need a friendly reminder.

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

The pattern across the product is reminders, not gates:

A reminder is helpful, low-friction, and pilot-respectful. It says “here is something you might want to know”.
A gate is patronising and brittle. It says “I will not let you do this until you do that”. A gate that gets it wrong is worse than no gate at all.

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 answer “No known defects” or “Report a defect”.

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 declaration is fixed once saved, so the record reflects what you attested at the time rather than anything edited in later.

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.