Skip to content

FousCAMP MTX

Pull your CAMP MTX due lists into your own systems

Read each tail's due list, aircraft times and open work order items from CAMP MTX with one API call each. Or have a workflow check the due list for every aircraft each morning and email you the items coming due before the next trip.

Works with your own CAMP MTX account. Fous is an independent product.

What you can build on CAMP

  • Get the due list for an aircraft

    Build this

    Reads the due list for one aircraft in CAMP MTX over the time window you choose, with what is coming due by date, hours and landings.

    Takes
    Aircraft registration, months ahead
    Returns
    Task number, description, next due date, next due hours, next due landings, remaining
  • Get aircraft times and status

    Build this

    Reads one aircraft's current times in CAMP MTX: airframe hours and landings, the date they were last updated, and its airworthiness status.

    Takes
    Aircraft registration
    Returns
    Registration, serial number, airframe hours, landings, times as of, airworthiness status
  • List open work order items

    Build this

    Reads an open work order in CAMP MTX for one aircraft: each item, the technician it is assigned to and whether it has been signed off.

    Takes
    Aircraft registration, work order number (optional)
    Returns
    Work order number, item, description, assigned technician, signed off, sign-off date

Automate CAMP with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • Items coming due across the fleet, each morning

    Build this
    Starts
    Every weekday at 7:00
    Step 1
    For each aircraft you name, get the due list for the next 2 months.
    Step 2
    Keep the items due within the next 30 days or the next 25 hours.
    Step 3
    Email you the list, one section per aircraft, soonest first.
  • New due list items, posted to your scheduling system

    Build this
    Starts
    Every day at 18:00
    Step 1
    For each aircraft, get the due list for the next 3 months.
    Step 2
    Keep the items that were not on the due list on the last run.
    Step 3
    Post each one, with its aircraft and due limits, to your scheduling or ERP webhook.
  • Weekly check that aircraft times are current

    Build this
    Starts
    Every Monday at 8:00
    Step 1
    For each aircraft, get its current times and status.
    Step 2
    Keep the aircraft whose times were last updated more than 7 days ago.
    Step 3
    Email you those aircraft with their airframe hours, landings and update date.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get the due list for an aircraft” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "mtx30.campsystems.com/get_due_list",
    "input": {
      "registration": "N512AC",
      "months_ahead": 2
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "registration": "N512AC",
    "items": [
      {
        "task_number": "05-20-01",
        "description": "Main landing gear wheel bearings, inspect",
        "next_due_date": "2026-12-04",
        "next_due_hours": null,
        "next_due_landings": 2300,
        "remaining": "22 days, 115 landings"
      }
    ]
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

CAMP’s own options

CAMP's MTX pages list no API you can sign up for yourself. CAMP connects MTX to partner systems such as flight scheduling software: you ask CAMP Support to set up the integration, CAMP issues the login for it and enables each aircraft. Hours and cycles flow in and due lists flow out. The iCAMP mobile app shows aircraft times, status and next due items.

OptionWhat it coversWhat it takes
Partner integration (for example FL3XX)Sends total hours and cycles to CAMP after each flight and pulls due lists back into the partner's software.A request to CAMP Support and the partner. CAMP issues an integration login and sets a flag for each aircraft.
iCAMP mobile appAircraft times, airworthiness status and next due items, checklists, discrepancies and electronic sign-off of completed maintenance.Your CAMP account, in the app from the Apple App Store or in a mobile browser.
CAMP MTX by handDue lists with adjustable time windows, task filters and utilization, work orders with ezSign, OEM revisions and ADs and SBs.A CAMP account with your username or email address and password.

Read on November 12, 2026: CAMP Maintenance Management (MTX), iCAMP mobile application, FL3XX guide to the CAMP integration.

Signing in to CAMP

CAMP signs you in through its Login button with your username or email address and your password, and may then ask for a code from an authenticator app or a text message. An SSO Login page is also offered. With Fous you sign in once through CAMP's own sign-in with your own account, and the login is sealed with AES-256, never returned by the API or written to logs.

Worth knowing

Times and cycles only go up
FL3XX's guide says its CAMP integration can only increase an aircraft's hours and cycles. A flight sent with lower values than those already in CAMP returns an error.
Each aircraft is enabled by CAMP Support
For an integration, CAMP Support sets a flag on each aircraft, and the registration and serial numbers in the other system must match CAMP exactly.
The due list depends on its window
The MTX due list changes with the time window, the task types you filter and the utilization you assume. A method takes the window as an input, so every run reads the list with the same settings.
CAMP analysts apply revisions
CAMP applies OEM revisions automatically, or holds them for your approval, and its analysts review ADs and SBs. A due list can change without anyone on your team editing it.

More in Maritime and aviation

Other industries: HomeWiseDocs, NLIS database, Syndigo CXH, Coles Supplier Portal, T-Mobile for Business Account Hub, GreenSky merchant portal.

Frequently asked questions

Not one you can sign up for yourself: CAMP's MTX pages list none. CAMP connects MTX to partner systems such as flight scheduling software: you ask CAMP Support, CAMP issues an integration login and enables each aircraft. Hours and cycles go in and due lists come out through the partner's software.

Yes, through a partner integration that pulls due lists into its own software, or with a method you build that reads the due list for each aircraft and returns it as JSON. A workflow can then send it to you by email or to your system by webhook.

Because the FL3XX integration can only increase hours and cycles. FL3XX's guide says an update with lower values than those already in CAMP causes an error.

Yes, CAMP uses multi-factor authentication. You enter your password at every sign-in and may then be asked for a time-sensitive code from an authenticator app such as Google Authenticator or Microsoft Authenticator, or from a text message.

No. Fous is an independent product. You use it with your own CAMP account, and a method reads and does only what that account can.

Put CAMP MTX behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextMyBoeingFleetSatair MarketIATA SISHomeWiseDocsHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of CAMP MTX (CAMP Systems International). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.