Skip to content

Serbia ๐Ÿ‡ท๐Ÿ‡ธ CAD Registry โ€‹

Namers-cad-registry
CountrySerbia
Registration prefixYU-
Data sourcehttps://apps.cad.gov.rs/ords/dcvws/regvaz/site/listAircraft
FormatJSON API (Oracle ORDS REST endpoint, fixed URL with query params)
Run frequencyWeekly (Tuesday, 10:10 UTC)
Depends on Mictronics for ICAO hexYes โ€” this runner does not publish ICAO hex addresses; registrations are resolved via RediSearch against Mictronics records (idx:aircraft:mictronics). Must run after the mictronics runner.

How it works โ€‹

A single GET request to the Serbia CAD ORDS REST endpoint (?...&limit=10000) returns the entire register in one response's items[] array โ€” no pagination or index-page discovery needed. The endpoint's TLS certificate has an untrusted issuer chain, so requests are made with verify=False and urllib3's InsecureRequestWarning is disabled globally. Only items whose registarska_oznaka starts with YU- are kept. Aircraft type (vrsta_vazduhoplova) is decoded from Serbian via a lookup table, passing through unmapped values. As with pg-casapng-registry, registrations are resolved to icao_hex in batches of 100 via a RediSearch TagField query against the Mictronics index; unmatched registrations are skipped for this run. 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.

Columns โ€‹

Source columnImportedNotes
registarska_oznakaโœ…YU- filter; used as the Mictronics lookup key
vrsta_vazduhoplovaโœ…โ†’ aircraft.type, decoded via lookup table (e.g. Avion โ†’ Airplane)
proizvoฤ‘aฤโœ…โ†’ aircraft.manufacturer
proizvoฤ‘aฤka_oznakaโœ…โ†’ aircraft.model
serijski_brojโœ…โ†’ aircraft.serial_number
korisnikโœ…โ†’ registrant.names[0]

See specs/data-dictionary.yaml (rs-cad-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 4C0E4D | python3 -m json.tool --sort-keys --no-ensure-ascii
json
{
    "aircraft": {
        "manufacturer": "TEXTRON AVIATION INC.",
        "manufacturer_model": "CESSNA 172 Skyhawk",
        "model": "CESSNA 172S",
        "serial_number": "172S11225",
        "type": "Airplane",
        "type_designator": "C172"
    },
    "data_sources": [
        "mictronics",
        "rs-cad-registry"
    ],
    "icao_hex": "4C0E4D",
    "military": false,
    "registrant": {
        "names": [
            "Vazduhoplovna akademija"
        ]
    },
    "registration": "YU-DSN"
}
bash
docker run --rm --network host redis:latest redis-cli EVAL "$(cat ./shared/lua/merge_aircraft.lua)" 0 4C01F1 | python3 -m json.tool --sort-keys --no-ensure-ascii
json
{
    "aircraft": {
        "manufacturer": "The Boeing Company",
        "manufacturer_model": "BOEING 737-700",
        "model": "BOEING 737-700",
        "serial_number": "37592",
        "type": "Airplane",
        "type_designator": "B737"
    },
    "data_sources": [
        "mictronics",
        "rs-cad-registry"
    ],
    "icao_hex": "4C01F1",
    "military": false,
    "registrant": {
        "names": [
            "Skybridge International Balkan D.O.O."
        ]
    },
    "registration": "YU-APR"
}

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/rs-cad-registry/statistic/{name} (all retained):

Topic suffixValueFormat
records_importede.g. 271Integer as string
last_run_ate.g. 2026-07-07T14:32:01.123456+00:00ISO 8601 UTC
last_run_statusSuccess or FailureString

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