Australia 🇦🇺 CASA Registry


Name	`au-casa-registry`
Country	Australia
Registration prefix	`VH-`
Data source	https://services.casa.gov.au/CSV/acrftreg.csv
Format	CSV (fixed URL)
Run frequency	Weekly (Tuesday, 07:10 UTC)
Depends on Mictronics for ICAO hex	Yes — this runner does not publish ICAO hex addresses; `VH-{Mark}` registrations are resolved via RediSearch against Mictronics records (`idx:aircraft:mictronics`). Must run after the `mictronics` runner.

How it works

The CASA register CSV is downloaded from a fixed URL and parsed with csv.DictReader (BOM-tolerant utf-8-sig decoding). Rows whose suspendstatus is suspended are filtered out before lookup. Registrations (VH- + Mark) are resolved to icao_hex in batches of 100 via RediSearch against the Mictronics index, then a type sanity check compares tokens extracted from the CASA Model column against the existing Mictronics type_designator/manufacturer_model fields, rejecting the match only when both sides have tokens and none overlap. Airframe and Engtype are decoded from CASA's plain-English categories (e.g. Power Driven Aeroplane → Airplane, Turbofan → Turbo-fan) and regholdCountry full country names are mapped to ISO 3166-1 alpha-2 codes, with unmapped values passed through as-is. Every written record explicitly sets military: false — this register is exclusively civil, and the explicit value ensures a stale military: true flag (from Mictronics or a prior record on a reused hex) is corrected on re-registration.

Whenever a record has an aircraft.type_designator, aircraft:type:{type_designator} is looked up in Redis (populated by the mictronics runner) and, if found, its manufacturer_model and description_code (ICAO Doc 8643 description code, e.g. L2J) are set directly on this record — unconditionally, regardless of whether Mictronics also has values for the same hex. This runner's own type_designator is sourced directly from CASA and is authoritative; merge_aircraft.lua's "registry wins over mictronics" precedence rule guarantees these values take priority at read time either way. The lookup is not a hard dependency — a missing reference table entry, or the table not existing yet, leaves the record exactly as it would have been without this step.

Columns

Source column	Imported	Notes
`Mark`	✅	Combined with `VH-` prefix; used as the Mictronics lookup key
`Manu`	✅	→ `aircraft.manufacturer`
`Type`	❌	Present in source; not read by this runner
`Model`	✅	→ `aircraft.model`; also used for the type sanity check against Mictronics
`Serial`	✅	→ `aircraft.serial_number`
`MTOW`	❌	Present in source; not read by this runner
`engnum`	✅	→ `aircraft.powerplant.count`
`Engmanu`	✅	→ `aircraft.powerplant.manufacturer`
`Engtype`	✅	→ `aircraft.powerplant.type`, decoded (e.g. `Turboprop` → `Turbo-prop`); `Not Applicable` omits the field
`Engmodel`	✅	→ `aircraft.powerplant.model`
`Fueltype`	❌	Present in source; not read by this runner
`regType`	❌	Present in source; not read by this runner
`regholdname`	✅	→ `registrant.names[0]`
`regholdadd1` / `regholdadd2`	✅	→ `registrant.street[]`
`regholdSuburb`	✅	→ `registrant.city`
`regholdState`	✅	→ `registrant.administrative_area`
`regholdPostcode`	✅	→ `registrant.postal_code`
`regholdCountry`	✅	→ `registrant.country`, mapped to ISO 3166-1 alpha-2
`regholdCommdate`	❌	Present in source; not read by this runner
`regopName`	❌	Present in source; not read by this runner
`regopadd1` / `regopadd2`	❌	Present in source; not read by this runner
`regopSuburb`	❌	Present in source; not read by this runner
`regopState`	❌	Present in source; not read by this runner
`regopPostcode`	❌	Present in source; not read by this runner
`regopCountry`	❌	Present in source; not read by this runner
`regopCommdate`	❌	Present in source; not read by this runner
`Datefirstreg`	❌	Present in source; not read by this runner
`gear`	❌	Present in source; not read by this runner
`Airframe`	✅	→ `aircraft.type`, decoded from CASA's category names
`CoAcata` / `CoAcatb` / `CoAcatc`	❌	Present in source; not read by this runner
`Propmanu`	❌	Present in source; not read by this runner
`Propmodel`	❌	Present in source; not read by this runner
`Typecert`	❌	Present in source; not read by this runner
`Countrymanu`	❌	Present in source; not read by this runner
`Yearmanu`	✅	→ `aircraft.manufactured_date` (4-digit year → `YYYY-01-01T00:00:00Z`)
`Regexpirydate`	❌	Present in source; not read by this runner
`suspendstatus`	✅	Used only as a filter (`suspended` rows are dropped); not stored
`suspenddate`	❌	Present in source; not read by this runner
`ICAOtypedesig`	✅	→ `aircraft.type_designator`; also used to look up `aircraft:type:{type_designator}` in Redis, setting `aircraft.manufacturer_model` and `aircraft.description_code` when found
`IDERA_Authorised_Party`	❌	Present in source; not read by this runner

See specs/data-dictionary.yaml (au-casa-registry entry) for full column semantics and cross-source schema notes.

Example Output

Read back the merged record for a given ICAO hex (combines this runner's data with Mictronics and any other sources that have written to the same key):

bash

docker run --rm --network host redis:latest redis-cli EVAL "$(cat ./shared/lua/merge_aircraft.lua)" 0 7C4F42 | python3 -m json.tool --sort-keys --no-ensure-ascii

json

{
    "aircraft": {
        "description_code": "L1P",
        "manufactured_date": "2008-01-01T00:00:00Z",
        "manufacturer": "CESSNA AIRCRAFT COMPANY",
        "manufacturer_model": "CESSNA 172 Skyhawk",
        "model": "172S",
        "powerplant": {
            "count": 1,
            "manufacturer": "TEXTRON LYCOMING",
            "model": "IO-360-L2A",
            "type": "Piston"
        },
        "serial_number": "172S10673",
        "type": "Airplane",
        "type_designator": "C172"
    },
    "data_sources": [
        "mictronics",
        "au-casa-registry"
    ],
    "icao_hex": "7C4F42",
    "military": false,
    "registrant": {
        "administrative_area": "NSW",
        "city": "PARRAMATTA",
        "country": "AU",
        "names": [
            "WESTPAC BANKING CORPORATION"
        ],
        "postal_code": "2150",
        "street": [
            "Level 34 Tower 8 Parramatta Square",
            "10 Darcy St"
        ]
    },
    "registration": "VH-PXW"
}

bash

docker run --rm --network host redis:latest redis-cli EVAL "$(cat ./shared/lua/merge_aircraft.lua)" 0 7C4920 | python3 -m json.tool --sort-keys --no-ensure-ascii

json

{
    "aircraft": {
        "description_code": "L4J",
        "manufactured_date": "2008-01-01T00:00:00Z",
        "manufacturer": "AIRBUS INDUSTRIE",
        "manufacturer_model": "AIRBUS A-380-800",
        "model": "A380-842",
        "powerplant": {
            "count": 4,
            "manufacturer": "ROLLS ROYCE LTD",
            "model": "RB211 Trent 972-84",
            "type": "Turbo-fan"
        },
        "serial_number": "0014",
        "type": "Airplane",
        "type_designator": "A388"
    },
    "data_sources": [
        "mictronics",
        "au-casa-registry"
    ],
    "icao_hex": "7C4920",
    "military": false,
    "registrant": {
        "administrative_area": "NSW",
        "city": "MASCOT",
        "country": "AU",
        "names": [
            "QANTAS AIRWAYS LIMITED"
        ],
        "postal_code": "2020",
        "street": [
            "10 Bourke Rd"
        ]
    },
    "registration": "VH-OQA"
}

Configuration

See Data Runners for the full list of environment variables every runner reads. This runner writes aircraft:registry:{icao_hex} with a fixed 14-day TTL (ENRICHMENT_TTL_SECONDS in shared/timing.py).

MQTT

Published once, at the end of a run, to SkyFollower/runner/au-casa-registry/statistic/{name} (all retained):

Topic suffix	Value	Format
`records_imported`	e.g. `271`	Integer as string
`last_run_at`	e.g. `2026-07-07T14:32:01.123456+00:00`	ISO 8601 UTC
`last_run_status`	`Success` or `Failure`	String

Home Assistant autodiscovery configs are also published (retained) to homeassistant/sensor/SkyFollower_runner_au_casa_registry_{name}/config for each of the three stats above.

Australia 🇦🇺 CASA Registry ​

How it works ​

Columns ​

Example Output ​

Configuration ​

MQTT ​