Not currently tracked · last seen 16h ago
- Flights observed
- 78 showing last 50
- Avg flight time
- 1h 19m
- Typical route
- DVT → DVT
- Last seen
- 16h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-02 | DVT → DVT | Jun 2, 16:20 UTC | Jun 2, 17:35 UTC | 1h 15m |
| 2026-06-01 | DVT → DVT | Jun 1, 16:05 UTC | Jun 1, 17:20 UTC | 1h 15m |
| 2026-05-31 | DVT → DVT | May 31, 14:45 UTC | May 31, 16:10 UTC | 1h 25m |
| 2026-05-28 | DVT → DVT | May 28, 15:20 UTC | May 28, 16:45 UTC | 1h 25m |
| 2026-05-26 | - | May 26, 15:00 UTC | May 26, 15:29 UTC | 30m |
| 2026-05-26 | - | May 26, 13:24 UTC | May 26, 13:50 UTC | 25m |
| 2026-05-22 | - | May 22, 17:40 UTC | May 22, 18:20 UTC | 40m |
| 2026-05-22 | - | May 22, 15:45 UTC | May 22, 16:25 UTC | 40m |
| 2026-05-21 | DVT → DVT | May 21, 13:55 UTC | May 21, 16:10 UTC | 2h 15m |
| 2026-05-21 | OCN → DVT | May 21, 00:40 UTC | May 21, 03:25 UTC | 2h 45m |
| 2026-05-20 | - | May 20, 16:30 UTC | May 20, 16:50 UTC | 20m |
| 2026-05-20 | - | May 20, 13:50 UTC | May 20, 15:30 UTC | 1h 40m |
| 2026-05-18 | - | May 18, 18:05 UTC | May 18, 19:10 UTC | 1h 4m |
| 2026-05-18 | - | May 18, 15:45 UTC | May 18, 16:40 UTC | 55m |
| 2026-05-17 | - | May 17, 16:50 UTC | May 17, 17:30 UTC | 40m |
| 2026-05-17 | - | May 17, 15:40 UTC | May 17, 16:05 UTC | 25m |
| 2026-05-16 | - | May 16, 20:30 UTC | May 16, 21:10 UTC | 40m |
| 2026-05-16 | - | May 16, 17:15 UTC | May 16, 17:50 UTC | 35m |
| 2026-05-14 | - | May 14, 16:25 UTC | May 14, 17:25 UTC | 1h 0m |
| 2026-05-14 | - | May 14, 15:01 UTC | May 14, 15:50 UTC | 50m |
| 2026-05-13 | OCN → DVT | May 13, 20:05 UTC | May 13, 23:15 UTC | 3h 10m |
| 2026-05-13 | - | May 13, 14:35 UTC | May 13, 17:45 UTC | 3h 10m |
| 2026-05-12 | - | May 12, 16:50 UTC | May 12, 17:25 UTC | 35m |
| 2026-05-12 | - | May 12, 14:10 UTC | May 12, 14:40 UTC | 30m |
| 2026-05-12 | - | May 12, 02:45 UTC | May 12, 05:25 UTC | 2h 40m |
| 2026-05-11 | - | May 11, 16:55 UTC | May 11, 17:35 UTC | 41m |
| 2026-05-11 | - | May 11, 14:45 UTC | May 11, 15:20 UTC | 35m |
| 2026-05-08 | DVT → DVT | May 8, 18:45 UTC | May 8, 20:30 UTC | 1h 45m |
| 2026-05-08 | DVT → DVT | May 8, 01:04 UTC | May 8, 03:49 UTC | 2h 45m |
| 2026-05-07 | - | May 7, 19:15 UTC | May 7, 19:45 UTC | 30m |
| 2026-05-01 | AZA → DVT | May 1, 17:40 UTC | May 1, 18:20 UTC | 40m |
| 2026-05-01 | DVT → AZA | May 1, 14:35 UTC | May 1, 15:10 UTC | 35m |
| 2026-04-30 | DVT → DVT | Apr 30, 14:30 UTC | Apr 30, 17:15 UTC | 2h 45m |
| 2026-04-29 | - | Apr 29, 17:55 UTC | Apr 29, 20:55 UTC | 3h 0m |
| 2026-04-29 | - | Apr 29, 13:45 UTC | Apr 29, 16:05 UTC | 2h 20m |
| 2026-04-28 | - | Apr 28, 20:05 UTC | Apr 28, 21:30 UTC | 1h 25m |
| 2026-04-28 | - | Apr 28, 16:20 UTC | Apr 28, 17:55 UTC | 1h 35m |
| 2026-04-28 | - | Apr 28, 13:55 UTC | Apr 28, 14:55 UTC | 1h 0m |
| 2026-04-27 | - | Apr 27, 18:05 UTC | Apr 27, 19:05 UTC | 1h 0m |
| 2026-04-27 | - | Apr 27, 13:40 UTC | Apr 27, 14:30 UTC | 50m |
| 2026-04-24 | DVT → DVT | Apr 24, 16:35 UTC | Apr 24, 17:30 UTC | 55m |
| 2026-04-23 | DVT → DVT | Apr 23, 13:55 UTC | Apr 23, 15:25 UTC | 1h 30m |
| 2026-04-22 | - | Apr 22, 15:30 UTC | Apr 22, 17:10 UTC | 1h 40m |
| 2026-04-22 | - | Apr 22, 14:10 UTC | Apr 22, 14:55 UTC | 45m |
| 2026-04-21 | - | Apr 21, 02:40 UTC | Apr 21, 03:40 UTC | 1h 0m |
| 2026-04-20 | - | Apr 20, 22:05 UTC | Apr 21, 00:40 UTC | 2h 35m |
| 2026-04-20 | - | Apr 20, 16:40 UTC | Apr 20, 18:55 UTC | 2h 15m |
| 2026-04-20 | - | Apr 20, 14:25 UTC | Apr 20, 15:15 UTC | 50m |
| 2026-04-20 | - | Apr 20, 01:55 UTC | Apr 20, 02:35 UTC | 40m |
| 2026-04-20 | - | Apr 20, 00:00 UTC | Apr 20, 01:05 UTC | 1h 5m |
Specifications
| Registration | N520TF |
| Operator | TANGO FLIGHT INC |
| Mode-S code | A68A9D · 51505235 (octal) |
Looking for transponder-level data? View the Mode-S A68A9D page for country allocation, callsign history, and ADS-B signal details.
N520TF frequently asked
Who operates N520TF?
N520TF is operated by TANGO FLIGHT INC.
What is the Mode-S transponder code for N520TF?
N520TF broadcasts on Mode-S (ICAO 24-bit) address A68A9D (octal 51505235). View the transponder page.
What route does N520TF typically fly?
N520TF most frequently flies between DVT and DVT based on observed flights.
Where is N520TF right now?
N520TF is not currently being tracked; last seen 16h ago.