Flight Tracking Technical Documentation Hub
The aerial deportation infrastructure operates through a complex network of private contractors, charter operators, and staging facilities. This hub provides technical resources for monitoring ICE Air Operations using open-source intelligence techniques.
Why Flight Tracking Matters
| Purpose | Application |
|---|---|
| Transparency | Document scale and scope of deportation operations |
| Legal defense | Provide evidence for emergency stays and habeas petitions |
| Community alert | Enable rapid response when flights approach |
| Accountability | Expose contractor networks and government logistics |
| Advocacy | Support policy campaigns with empirical data |
ICE Air Operations at a Glance
2025-2026 Operational Scale
| Metric | Volume | Change |
|---|---|---|
| International removal flights | 2,253 | +46% |
| Destination countries | 79 | +76% |
| Domestic transfer flights | 9,066 | +132% |
| Daily domestic average | 42 flights | — |
Primary Staging Hubs
| Hub | Location | Function |
|---|---|---|
| Mesa Gateway | Arizona | Western operations |
| Brownsville | Texas | Southern border |
| San Antonio | Texas | Central staging |
| Alexandria | Louisiana | Gulf region |
| Miami | Florida | Caribbean/South America |
Core Components
Infrastructure Understanding
| Guide | Content |
|---|---|
| ICE Air Operations Overview | Organizational structure, scale, hub architecture |
| Aircraft Identification Guide | Hex codes, N-numbers, obfuscation tactics |
Tracking Technologies
| Guide | Content |
|---|---|
| Real-Time Tracking Guide | ADS-B, MLAT, unfiltered APIs |
| Historical Analysis Guide | Pattern detection, FOIA strategies, geospatial mapping |
Alert Infrastructure
| Guide | Content |
|---|---|
| Alert System Architecture | Event streaming, geofencing, notification delivery |
| Implementation Roadmap | Edge node deployment, scaling, rapid response integration |
Compliance & Resources
| Guide | Content |
|---|---|
| Legal & Ethical Framework | Regulatory landscape, OPSEC, ethical guidelines |
| Resource Directory | Active projects, tools, code repositories |
Contractor Ecosystem
Primary Contractors
| Contractor | Role | Fleet/Notes |
|---|---|---|
| CSI Aviation | Prime broker | >$1.2B lifetime contracts |
| GlobalX Airlines | International charter | A320/A321; ~74% of removal flights |
| Air Wisconsin | Domestic transfer | CRJ-200 (acquired by CSI Dec 2025) |
| Bighorn Airways | Small-capacity domestic | Dornier 228, CASA C-212 |
| GEO Group (GTI) | Air operations support | Security/transport personnel |
| Signature Aviation | Fixed Base Operator | Ground logistics, tarmac access |
Tracking Technology Stack
Data Flow Architecture
[ADS-B Transponder] → [1090 MHz Broadcast]
↓
[Ground Receiver] → [dump1090/readsb]
↓
[tar1090/aircraft.json] → [API Polling]
↓
[Watchlist Matching] → [Geofence Detection]
↓
[Alert Distribution] → [Signal/Telegram]
Key Technologies
| Technology | Function |
|---|---|
| ADS-B | Aircraft broadcast position, altitude, speed |
| MLAT | Triangulate position from multiple receivers |
| SDR | Software-defined radio for 1090 MHz reception |
| Geofencing | Detect aircraft approaching target airports |
Obfuscation Tactics
Contractors employ multiple layers of evasion:
| Tactic | Method | Countermeasure |
|---|---|---|
| Visual | White paint, no livery | Registration research |
| Call signs | "RPN" (Repatriate) prefix | Call sign filtering |
| LADD | FAA data filtering | Unfiltered networks (ADS-B Exchange) |
| PIA | Temporary spoofed hex codes | Pattern analysis, historical correlation |
Quick Start Guide
For Researchers
- Identify aircraft: Query FAA N-Number Registry, cross-reference with FOIA manifests
- Build watchlist: Compile hex codes of known contractor aircraft
- Monitor flights: Use ADS-B Exchange API to track watchlist aircraft
- Analyze patterns: Correlate flight data with known enforcement events
For Community Alerting
- Deploy receiver: Set up Raspberry Pi with RTL-SDR at strategic location
- Configure geofences: Define alert zones around staging airports
- Build notification: Integrate with Signal/Telegram for encrypted alerts
- Coordinate response: Connect alerts to rapid response networks
Ethical Principles
| Principle | Application |
|---|---|
| Verification | Confirm aircraft association before alerting |
| Restricted distribution | Alerts to vetted legal observers, not public broadcast |
| No dual-use | Prevent misuse by hostile actors |
| Privacy protection | Secure researcher and volunteer identities |
| Community consent | Work within established rapid response frameworks |
Related Resources
Last updated: March 25, 2026