The sign-in screen, with Open demo.
Signing in, and getting an account
From the FlyPack CAMO manual
Everything on this page happens before there is a fleet on screen.
The sign-in screen
| Control | What it does |
|---|---|
| Work email and Password | The ordinary way in |
| Continue with Google | The same account, reached with a Google identity |
| Forgot password? | Sends a reset link, from FlyPack CAMO (no-reply@flypack.net) |
| Open demo | A worked fleet with real data, no sign-up |
| Create an organisation account | Registers a new organisation |
It refuses in one sentence and never says which half was wrong:
"That email and password do not match."
That is deliberate. Telling somebody the address exists but the password is wrong tells whoever is guessing that the address exists.
Two other refusals mean something different:
- "This account has been disabled." — an administrator turned it off, or whoever runs the installation did. It is not a password problem.
- "This account signs in with Google. Use the password reset link to set a password." — the account was created through Google and has no password yet. The reset link is how it gets one; both then work.
Google, and the same person twice
Signing in with Google against an address that already has a password account attaches the two rather than making a second account. One person, one record, two ways in — which is what the Sign-in methods line on Your account lists.
Registering an organisation
Create an organisation account asks for your name, a work email and a password of at least twelve characters including a number and a symbol, then sends a link to confirm the address. "We send a link to confirm the address before the account is active." Nothing works until that link is followed.
Then Set up your organisation: its name, the kind of approval it holds — Part-CAO, Part-M Subpart G, or none yet — the approval reference, and the competent authority. The reference can be left blank: "Leave blank if the approval has not been issued yet." An organisation that has applied and is waiting is a real organisation.
The account that creates an organisation becomes its administrator. An account already in one is refused: "This account already belongs to an organisation."
Belonging to more than one organisation
One login can be a member of several — an engineer who works for two clubs. Where that is true, Choose an organisation comes before the fleet, and everything after it is scoped to whichever was chosen. There is no cross-fleet view, on purpose: the records of two organisations are two sets of records.
Forgetting, and resetting
Forgot password? always says "Check your inbox", whether or not the address is one we know. Saying "no such account" would be a way of asking us which addresses exist.
The link opens Choose a new password — twelve characters, a number, a symbol — and warns that "Signing in elsewhere will be ended." That is the point: a password is reset because somebody may have the old one.
A link that arrives incomplete says so rather than failing quietly: "This reset link is incomplete. Request a new one from the sign-in page."
Staying signed in
The session is held in the browser and renewed from a cookie that JavaScript cannot read. Closing the tab and coming back keeps you signed in; Sign out ends it everywhere that cookie reached.
What the session carries
Besides who you are: which organisation you are working in, what your roles let you do, whether the organisation is read-only — and how it writes an hour figure and a date, so the first screen drawn after signing in is already in the right convention rather than redrawing itself a moment later. See How hours are written and How dates are written on the same page.
The demo fleet
Open demo signs you into a worked organisation — a fleet of aircraft, a real due list, real defects, real paperwork. The presentation site's Open the demo goes to /demo, which does the same without the sign-in form: it signs in and opens the demo's dashboard, replacing whatever session the browser had.
It is a separate organisation from anybody's records and nothing done in it touches a real fleet. On an installation where it has been switched off — from either button: "The demo fleet is not available on this server."
The demo fleet writes hours and minutes — 892:24 h, not 892.4 h — so it shows the setting in use. A new organisation of your own starts on decimal.
Getting around
From the FlyPack CAMO manual
The left rail
| Dashboard | The fleet at a glance |
| Fleet | Every aircraft managed, and each aircraft's own record behind it |
| Aircraft types | The type-level record behind them — designator, TCDS, mass |
| Planning & work packs | What is due across the fleet, and the packs built to do it |
| Tech log | Flights |
| Defects & MEL | What is broken and what has been deferred |
| Stores | Parts — only where the organisation keeps a store |
| Reliability & trends | Oil, defect rates, unscheduled removals |
| Organisation info | The organisation, its approvals, and its people |
| Audit trail | Every change recorded — administrators, accountable manager and compliance only |
| Safety & compliance | Occurrences, findings, the audit plan |
| Training & authorisations | Who is trained and who may sign |
| Billing & invoices | Money out and money in |
| Manual | These pages. Last, because it is about the software rather than about an aircraft |
The logo, and folding the rail
The FlyPack mark at the top of the rail is a link to the dashboard. It is the shortest way home from anywhere, and it is where everybody already clicks.
The « button at the left of the top bar folds the rail to its icons and » opens it again. Folded it is fifty-four pixels wide and every destination is still there — the icon, with its name on hover — because a menu that disappears entirely is one people stop trusting they can get back to. The choice is remembered in the browser, so it survives navigation and a refresh; it is a preference on that computer, not something recorded against you.
On a phone the rail is not shown at all and the bar along the bottom takes its place, so there is nothing to fold and the button is hidden.
Where the dashboard lives
The dashboard is at /dashboard. The bare address of the installation is the presentation site — what FlyPack CAMO is, page by page, for somebody who has not used it — with Sign in and Open the demo at the top. A browser that is signed in to FlyPack CAMO is sent from there straight on to the dashboard, so somebody who uses it every day does not have to step over the brochure.
The aircraft's own tabs
Behind every aircraft, ten tabs, and the tab is in the URL so a particular view can be linked to and survives a refresh:
Overview · Programme · Weight & balance · AD & SB · Modifications · Components · Defects · Tech log · Documents · Airworthiness review
There is also an Audit trail → link in the same strip, for whoever holds the role, which opens the trail filtered to that aircraft.
The top bar
- Search — a registration, a part number, or an airworthiness directive reference. Results are grouped by kind; arrow keys move through them.
- Ask FlyPack CAMO (
Ctrl/Cmd+K) — the help panel. It opens as a dock beside the screen rather than over it, and carries the aircraft you are looking at as a chip.Esccloses it. - Sign out, and the avatar, which opens your own account.
Why an hour figure reads 3,411:54
Because the organisation is set to write hours and minutes rather than decimals. Counters, times since overhaul, block time and what is left before something falls due all follow that setting; limits quoted from a manual, and man-hours, stay decimal. Every box that takes hours accepts both forms whichever is set. See How hours are written.
Why a date reads 21/08/2026
Because the organisation has chosen a numeric date convention — dd/mm/yyyy or mm/dd/yyyy — instead of the default 21 Aug 2026. Every date on every screen follows it, and so does every box a date is typed into, which also takes the date written that way. See How dates are written.
A menu item you cannot see
Items are hidden when they do not apply to you rather than shown and refused — Stores when the organisation keeps none, the audit trail without the role, the platform console unless you run the installation. If a colleague can see something you cannot, it is a role or a setting, not a fault.
The banner that says the organisation is read-only
An organisation whose trial has ended can be read, printed and exported, but nothing further can be recorded in it. The banner is on every screen rather than at the point of refusal, because letting somebody fill in a flight and meet the refusal on the way out teaches them the application is broken.
Every page of this manual
| Page | What it covers |
|---|---|
| Signing in, and getting an account | Sign in, Google, resets, registering an organisation |
| Dashboard, fleet and adding an aircraft | The tiles, the due list, adding an aeroplane |
| Aircraft records | The counters, the Edit form, ending management |
| Aircraft types | Designator, TCDS, mass, and what makes a type complex |
| The maintenance programme | Tasks, intervals, revisions, reading a programme out of the manuals |
| Planning and what is due | Where due dates come from, tolerance, the capacity view |
| Work packs and estimates | Building a pack, signing items off, the quote |
| Release to service (CRS) | Issuing the certificate, and who may sign it |
| Components and their lives | Fitting, removing, and what a life limit does |
| Stores | Receipt, inspection, segregation, issue |
| Tech log | Flights, and how the counters advance |
| Defects and MEL | Severity, deferral, rectification |
| Airworthiness directives and service bulletins | Applicability, compliance, recurrence |
| Modifications, repairs and standard changes | STCs, repairs, CS-STAN |
| Weight and balance | Stations, weighings, the envelope |
| Airworthiness review and the ARC | The review, the certificate, extensions |
| Documents, and the records as a file | The register, backups, restore |
| Your organisation and people | Details, approvals, staff, roles, the digest |
| Safety, compliance and training | Occurrences, findings, audits, training |
| Billing, invoices and rates | Invoices, supplier invoices, currency |
| Audit trail | Every change, and who may read it |
| The helper, and this manual | What the panel can and cannot do |
| The installation, and the owner portal | The platform console, and the owner's view |
What this software does not do
It manages continuing airworthiness records. It does not decide airworthiness. No figure it shows and nothing the helper says releases an aircraft to service — that stays with the authorised person, which is where Part-ML puts it.
The owner portal
From the FlyPack CAMO manual
The owner portal
An aircraft owner who has a login gets their own screen, not the CAMO's with columns hidden. An owner is not a smaller version of a CAMO user; they want different things, and the screen answers them in this order:
- Can I fly it? — the state of each of their aircraft, and the reason where the answer is no.
- When is it next unavailable? — the planned visits.
- Is the certificate still valid? — the ARC and when it expires.
- What am I being charged? — invoices, and the management agreement.
Their session is narrowed to their own customer record as well as to the organisation, so an owner cannot reach another owner's aircraft. A CAMO account opening this view is told plainly: "This view is for owner accounts. Your account manages aircraft rather than owning them."
Owner logins are created from Owners & contracts on Organisation info.