WingsPath CAMO

What CAMO does today.

Every feature of this module, by the team that uses it. Nothing is shown as working until it is built and in use. What is still being built is marked as such.

30 live · 2 building · 2 planned

Maintenance & CAMO

Continuing airworthiness for every aircraft you manage, worked out the way a CAMO has to.

  • Fleet and aircraft status

    Every limit tracked by date, hours, landings and cycles; the most restrictive one wins.

  • Engine-by-engine hours

    Engine items are measured against that engine's own hours, never the airframe's.

  • Calendar and work packs

    A due list becomes a scoped work order in three steps, with an AI-drafted scope to check.

  • ADs, bulletins and MEL

    Directives, service bulletins and MEL deferrals tracked per aircraft, with category deadlines.

  • Releases to service

    Certificates of release signed electronically into a permanent, append-only record.

  • Components and life-limited parts

    Each part's history from new, including moves between aircraft.

  • Interval extensions

    Extensions applied within KCAA's cap, with the authority notification recorded.

Flight operations

Plan the flight and assign the crew with their licences, medicals and currency already in view.

  • Hours posted to maintenance

    With its closing hours entered, a signed flight posts hours and landings to the aircraft — one book for operations and engineering.

    Also in: AOC

  • Utilisation and forecast

    Average daily utilisation turns hours-based limits into forecast dates.

Safety & quality

Occurrences, findings and corrective actions in one register, with the evidence attached.

  • Occurrence reports

    In the reporter's own words; a CAST/ICAO category is suggested and a person confirms it.

  • Findings register

    Audit findings with root cause, corrective and preventive actions, owners and target dates.

    Also in: AOC · ATO

  • KCAA corrective action plans

    The plan KCAA asks for after an audit, submitted by the Accountable Executive.

    Also in: AOC · ATO

  • Records reconciliation

    Tracking-system entries checked against the aircraft's own records, every mismatch listed.

  • Hazard register and risk matrixPlanned

    Hazards assessed on a 5×5 likelihood and severity matrix, with owners and review dates.

    Also in: AOC · ATO

  • Notices, read and signedPlanned

    Company notices crew must read, with a record of who has signed and who has not.

    Also in: AOC · ATO

Records & Neema

Decades of paper become searchable records, and an assistant answers from them.

  • Scans read and classified

    Logbooks, work orders, certificates and invoices read by OCR, classified and indexed.

    Also in: AOC · ATO

  • Document recovery

    Locked PDFs opened, foreign-language pages translated, poor scans read again.

    Also in: AOC · ATO

  • Whole folders uploaded

    A records folder uploaded from the browser, with files up to 500 MB.

    Also in: AOC · ATO

  • Ask Neema

    Questions in your own words, answered from what is on file, with each source named.

    Also in: Every module

  • The KCARs, quotable

    Neema can quote the Kenyan regulations from a shared reference library.

    Also in: Every module

  • Records audit

    A count of your paper archive, box by box, before any scanning is quoted.

    Also in: AOC · ATO

Owners & commercial

What an owner, a lessor or a buyer needs to know about an aircraft.

  • Ownership and parties

    Owner, operator and billing organisation kept apart, with every transfer on record.

  • Status report and C of A pack

    The reports KCAA and owners ask for, built from the records on file.

  • KCAA correspondence

    Extension requests and submissions assembled from the records, ready to sign.

  • Leasing

    Leases recorded with their KCAA approval; a lease cannot start without it.

  • Warranties

    Warranty terms and expiry dates kept with the parts they cover.

  • Buyer and engineer advisory

    A cited review of an aircraft's records for a buyer or an engineer, as a PDF.

Access & security

One login, your organisation's own walls, and a record of every change.

  • Isolated in the database

    Each organisation's records are separated by the database itself, not just the screen.

    Also in: Every module

  • Audit trail

    Who changed what and when, with the value before, for every write.

    Also in: Every module

  • Two-factor sign-in

    Authenticator-app codes, and a lock-out after repeated failed attempts.

    Also in: Every module

  • Access by position

    Each person sees the records their job needs, set by their position.

    Also in: Every module

  • One login across modules

    CAMO, AOC, ATO and Flight Deck share one sign-in and one set of records.

    Also in: Every module

  • Android field appBuilding

    Capture a logbook page or a component plate, and sync when back in range.

    Also in: Every module

  • Desktop appBuilding

    WingsPath as a desktop application for the records office.

    Also in: Every module

What is not built for this kind of operation.

  • Parts stock, purchasing and tool control are not built.
  • The AMO module holds the certifying-staff register only. Work orders, stores and release certificates for the AMO's own work are not built.
  • WingsPath reads CESCOM status reports; it does not yet connect to CAMP or other tracking systems.

See CAMO on your operation.

A 30-minute walk-through on our demonstration aircraft, and on the parts that matter to you.