# Australia CASA Aircraft Mark Portfolio Status Monitor (`plym-actor-factory/au-casa-reg-mark-portfolio-status-monitor`) Actor

- **URL**: https://apify.com/plym-actor-factory/au-casa-reg-mark-portfolio-status-monitor.md
- **Developed by:** [Daniel Witney](https://apify.com/plym-actor-factory) (community)
- **Categories:** Automation, AI, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 casa aircraft registration status event delivereds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Australia CASA Aircraft Registration Mark Portfolio Status Event Monitor

Watch a **book of Australia CASA civil aircraft registration marks** and emit typed status events when a mark **appears, drops, suspends, returns to Full Registration, or changes holder/operator** on the official daily CASA register file.

### Source

- Official daily CSV: `https://services.casa.gov.au/CSV/acrftreg.csv` (also published as zip)
- Docs: [CASA data files for registered aircraft](https://www.casa.gov.au/aircraft/aircraft-registration/data-files-registered-aircraft)
- Durable key: 3-character `Mark` (accepts `VH-22A` / `VH22A` / `22A` → canonical `22A`, display `VH-22A`)
- Only **currently registered** aircraft are published (CASR 47.030). Deregistered marks leave the file → `DROPPED`.

### Events (PPE)

| Event | Meaning |
|-------|---------|
| `APPEARED` | Mark present after previously missing |
| `DROPPED` | Mark absent after previously present |
| `SUSPENDED` | `suspendstatus` / `regType` flips to Suspended |
| `FULL_REGISTRATION` | Returns to / becomes Full Registration |
| `REG_TYPE_CHANGED` | Other regType change |
| `HOLDER_CHANGED` | Registration holder name change (attributes group) |
| `OPERATOR_CHANGED` | Registered operator name change (attributes group) |

Non-billable: `RUN_STATUS` (including `FIXTURE_HEALTH`). First observation stores baseline with **no** charge.

### Not this Actor

- **Not** FAA N-Number twin (US registry / Store change monitors)
- **Not** ACMA radiocomms licence twin
- **Not** Australia ABN / APVMA twin
- **Not** a national CASA dump billed as rows

### Pricing

- `casa-aircraft-reg-status-event-delivered` @ **$0.02** / unique delivered event
- `apify-actor-start` @ **$0.00005**

### Input

```json
{
  "registrationMarks": ["22A", "VH-ABC", "XYZ"],
  "sourceMode": "live",
  "signalGroups": ["directory", "status", "attributes"],
  "maxRunSeconds": 180
}
```

`sourceMode=fixture` (default) is Store/CI health — no network, `RUN_STATUS` / `FIXTURE_HEALTH` only unless `emitFixtureDemoEvents=true`.

# Actor input Schema

## `registrationMarks` (type: `array`):

Australia civil aircraft registration marks to monitor against the official CASA daily register (e.g. 22A, VH-22A, or VH22A). Canonical key is the 3-character mark without VH- prefix. Invalid entries skipped with no charge. Not a national CASA dump bill.

## `marks` (type: `array`):

Optional alias for registrationMarks — same mark keys, merged into the watchlist.

## `signalGroups` (type: `array`):

Which change groups to evaluate: directory (APPEARED/DROPPED), status (FULL\_REGISTRATION/SUSPENDED/REG\_TYPE\_CHANGED), attributes (HOLDER\_CHANGED/OPERATOR\_CHANGED). Default: directory+status.

## `maxRunSeconds` (type: `integer`):

Wall-clock budget (register download + parse + watchlist diff).

## `maxEvents` (type: `integer`):

Stop after this many unique change events are delivered (does not include RUN\_STATUS).

## `resumeFromCheckpoint` (type: `boolean`):

If true, resume mark snapshots and seen event\_uids from the default Key-Value Store.

## `sourceMode` (type: `string`):

fixture = Store/CI health default (no network; RUN\_STATUS only unless emitFixtureDemoEvents=true). live = official CASA daily acrftreg.csv (no API key; daily publish lag).

## `emitFixtureDemoEvents` (type: `boolean`):

When sourceMode=fixture, if true push fabricated change events from local fixtures. Default false so Store daily auto-tests never emit fake CASA events or charge casa-aircraft-reg-status-event-delivered.

## `asOfHint` (type: `string`):

Optional as\_of label for events / RUN\_STATUS. Defaults to Last-Modified date from the CSV response when present.

## `maxTotalChargeUsd` (type: `number`):

Optional soft budget hint for delivered change events.

## `casaRegisterCsvUrl` (type: `string`):

Optional override for the official CASA civil aircraft register CSV URL.

## Actor input object example

```json
{
  "registrationMarks": [
    "22A",
    "ABC",
    "XYZ",
    "ALR"
  ],
  "signalGroups": [
    "directory",
    "status"
  ],
  "maxRunSeconds": 180,
  "maxEvents": 500,
  "resumeFromCheckpoint": true,
  "sourceMode": "fixture",
  "emitFixtureDemoEvents": false
}
```

# Actor output Schema

## `OUTPUT` (type: `string`):

JSON summary: delivered, charged, runStatus, checkpoint, stats, CASA Mark coverage limits

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("plym-actor-factory/au-casa-reg-mark-portfolio-status-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("plym-actor-factory/au-casa-reg-mark-portfolio-status-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call plym-actor-factory/au-casa-reg-mark-portfolio-status-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,plym-actor-factory/au-casa-reg-mark-portfolio-status-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/N6I3Y4JWZMB84OYbP/builds/9ncsDOfjlRy9Pj5xp/openapi.json