Not currently tracked · last seen 1d ago
- Flights observed
- 31
- Avg flight time
- 1h 33m
- Typical route
- -
- Last seen
- 1d ago
Last known area
Recent flights last 31
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-01 | - | Jun 1, 15:30 UTC | Jun 1, 17:55 UTC | 2h 25m |
| 2026-06-01 | - | Jun 1, 12:05 UTC | Jun 1, 12:40 UTC | 35m |
| 2026-05-29 | - | May 29, 16:00 UTC | May 29, 18:20 UTC | 2h 20m |
| 2026-05-26 | - | May 26, 11:39 UTC | May 26, 13:10 UTC | 1h 30m |
| 2026-05-18 | - | May 18, 17:00 UTC | May 18, 18:55 UTC | 1h 54m |
| 2026-05-18 | - | May 18, 15:45 UTC | May 18, 16:35 UTC | 50m |
| 2026-05-18 | FTY → CHS | May 18, 12:05 UTC | May 18, 12:50 UTC | 45m |
| 2026-05-17 | TPA → FTY | May 17, 12:15 UTC | May 17, 14:15 UTC | 2h 0m |
| 2026-05-14 | - | May 14, 00:25 UTC | May 14, 01:10 UTC | 45m |
| 2026-05-12 | - | May 12, 22:45 UTC | May 13, 00:05 UTC | 1h 20m |
| 2026-05-12 | - | May 12, 14:10 UTC | May 12, 15:30 UTC | 1h 20m |
| 2026-05-09 | - | May 9, 01:35 UTC | May 9, 04:10 UTC | 2h 35m |
| 2026-05-04 | - | May 4, 19:50 UTC | May 4, 22:55 UTC | 3h 5m |
| 2026-05-03 | PBI → DAL | May 3, 23:30 UTC | May 4, 02:39 UTC | 3h 10m |
| 2026-05-01 | - | May 1, 17:20 UTC | May 1, 20:10 UTC | 2h 50m |
| 2026-04-29 | - | Apr 29, 11:40 UTC | Apr 29, 13:05 UTC | 1h 25m |
| 2026-04-26 | - | Apr 26, 13:15 UTC | Apr 26, 15:50 UTC | 2h 35m |
| 2026-04-26 | - | Apr 26, 13:00 UTC | Apr 26, 13:10 UTC | 10m |
| 2026-04-24 | DAL → PBI | Apr 24, 12:45 UTC | Apr 24, 15:15 UTC | 2h 30m |
| 2026-04-22 | - | Apr 22, 17:25 UTC | Apr 22, 18:55 UTC | 1h 30m |
| 2026-04-22 | - | Apr 22, 01:35 UTC | Apr 22, 03:05 UTC | 1h 30m |
| 2026-04-20 | - | Apr 20, 19:05 UTC | Apr 20, 20:30 UTC | 1h 25m |
| 2026-04-18 | - | Apr 18, 23:50 UTC | Apr 19, 01:40 UTC | 1h 50m |
| 2026-04-18 | - | Apr 18, 16:05 UTC | Apr 18, 17:35 UTC | 1h 30m |
| 2026-04-15 | - | Apr 15, 11:00 UTC | Apr 15, 12:15 UTC | 1h 15m |
| 2026-04-15 | - | Apr 15, 10:35 UTC | Apr 15, 10:55 UTC | 20m |
| 2026-04-14 | - | Apr 14, 21:15 UTC | Apr 14, 21:50 UTC | 35m |
| 2026-04-14 | - | Apr 14, 14:50 UTC | Apr 14, 16:20 UTC | 1h 30m |
| 2026-04-14 | - | Apr 14, 13:50 UTC | Apr 14, 14:45 UTC | 55m |
| 2026-04-12 | - | Apr 12, 23:55 UTC | Apr 13, 00:25 UTC | 30m |
| 2026-04-12 | - | Apr 12, 17:20 UTC | Apr 12, 18:15 UTC | 55m |
Specifications
| Registration | N12ZW |
| Operator | RODFORCE 2 LLC |
| Mode-S code | A053AD · 50051655 (octal) |
Looking for transponder-level data? View the Mode-S A053AD page for country allocation, callsign history, and ADS-B signal details.
N12ZW frequently asked
Who operates N12ZW?
N12ZW is operated by RODFORCE 2 LLC.
What is the Mode-S transponder code for N12ZW?
N12ZW broadcasts on Mode-S (ICAO 24-bit) address A053AD (octal 50051655). View the transponder page.
Where is N12ZW right now?
N12ZW is not currently being tracked; last seen 1d ago.