Tracking Methodology

How we track cloud seeding aircraft

ADS-B flight tracking display

ADS-B Technology

Aircraft automatically broadcast identity, position, altitude, and velocity derived from satellite navigation systems.

ADS-B Technology Overview

Update frequency: Approximately once per second

1090 MHz Extended Squitter (1090ES)

International standard used by most commercial and high-altitude aircraft. Same frequency as traditional Mode S transponders.

978 MHz Universal Access Transceiver (UAT)

Primarily used in the US by general aviation aircraft operating below 18,000 feet.

Data Broadcast

ICAO 24-bit addressCallsignLatitude/LongitudeBarometric altitudeGround speedHeading/TrackVertical rateEmergency statusSquawk codeData quality indicators

Tracking API Providers

ADS-B Exchange

REST API

Recommended

Policy: Unfiltered — no aircraft blocking

Coverage: Global (community-driven feeder network)

Pricing: Free API for non-commercial use

No filtering of military, government, or private aircraft
Critical for tracking privately registered aircraft
Community-driven data
Free for non-commercial use
Smaller feeder network than commercial giants
Potential coverage gaps in remote areas
Visit

FlightAware

REST API, Streaming

Policy: Filtered — honors FAA LADD list and block requests

Coverage: Strong North America coverage, satellite ADS-B constellation

Pricing: Commercial (paid tiers)

Deep FAA data integration
Own satellite ADS-B constellation
Excellent North American coverage
Historical data back to 2011
Well-documented commercial API
Filters aircraft from LADD list
Some cloud seeding aircraft may be hidden
Paid service
Visit

Flightradar24

REST API

Policy: Filtered — honors block requests

Coverage: Largest global ground-based receiver network (35,000+), strong in Europe

Pricing: Commercial (paid tiers)

Largest feeder network globally (35,000+ receivers)
Polished user experience
Multiple data source integration
Filters certain aircraft from public view
Some cloud seeding aircraft may be hidden
Paid service
Visit

OpenSky Network

REST API

Recommended

Policy: Open — research-focused

Coverage: Global (smaller network)

Pricing: Free for academic and governmental research

Free for research purposes
High data quality
Non-profit, research-focused
Smaller receiver network
Less comprehensive coverage
Visit

Aviationstack

REST API

Policy: Commercial

Pricing: Free and paid tiers

Visit

Aviation Edge

REST API

Policy: Commercial

Pricing: Paid tiers

Historical flight radar and tracker API
Visit

AirLabs

REST API

Policy: Commercial

Pricing: Free and paid tiers

Visit

Identification Methods

Tail Number (Registration Number)

High — permanent identifier for the airframe

Primary method. Unique alphanumeric code assigned upon registration. US aircraft use 'N' prefix (e.g., N555DS). Search FAA registry or flight tracking platforms.

FAA Registry: https://registry.faa.gov/aircraftinquiry/search/nnumberinquiry

ICAO 24-bit Address

High — unique per aircraft

Unique hexadecimal code broadcast by the aircraft's ADS-B transponder. Tied to the aircraft's registration.

Company Registration Lookup

Medium — requires knowing the operating company

Identify cloud seeding companies first, then search FAA registry for aircraft registered to those companies or parent entities.

Visual Equipment Identification

High for visual confirmation, requires direct observation

Look for wing-mounted BIP flare racks, belly-mounted ejectable flare racks, wingtip acetone burners, and other cloud seeding equipment.

Flight Pattern Analysis

Medium — indicative but not conclusive

Cloud seeding aircraft exhibit distinctive flight patterns: repeated passes over mountain ridges, orbiting patterns in target areas, operations during storm events.

Typical Flight Characteristics

Operational Altitudes

cold cloud seeding

Typically 15,000–25,000 ft MSL (at or above cloud level)

warm cloud seeding

Typically at cloud base level, lower altitudes

general aviation uat ceiling

Below 18,000 ft for UAT-equipped aircraft

Flight Patterns

Repeated passes along mountain ridges (orographic seeding)
Orbiting or racetrack patterns over target areas
Low-altitude passes at cloud base (hygroscopic seeding)
Operations concentrated during storm events and winter months

Operational Seasons

winter orographic

November through April (snowpack enhancement)

summer convective

May through September (rainfall enhancement, hail suppression)

Implementation Best Practices

Use tail number as primary tracking key for consistent identification
Prefer unfiltered data sources (ADS-B Exchange) for cloud seeding aircraft
Implement rate limiting logic to stay within API constraints
Cache static data (aircraft details, airport metadata) to reduce API calls
Store historical tracking data locally for post-mission analysis
Use REST API polling (10-30 second intervals) for near-real-time tracking
Consider WebSocket streaming for lowest latency requirements