Not currently tracked · last seen 5d ago
- Flights observed
- 103 showing last 50
- Avg flight time
- 1h 6m
- Typical route
- DVT → DVT
- Last seen
- 5d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 13:35 UTC | Jul 13, 13:55 UTC | 20m |
| 2026-07-07 | - | Jul 7, 15:15 UTC | Jul 7, 16:00 UTC | 45m |
| 2026-07-02 | - | Jul 2, 20:35 UTC | Jul 2, 21:15 UTC | 40m |
| 2026-07-02 | - | Jul 2, 13:45 UTC | Jul 2, 14:15 UTC | 30m |
| 2026-06-29 | - | Jun 29, 13:19 UTC | Jun 29, 13:59 UTC | 40m |
| 2026-06-28 | - | Jun 28, 12:09 UTC | Jun 28, 12:39 UTC | 30m |
| 2026-06-26 | DVT → DVT | Jun 26, 14:39 UTC | Jun 26, 16:00 UTC | 1h 20m |
| 2026-06-24 | DVT → DVT | Jun 24, 16:09 UTC | Jun 24, 16:45 UTC | 35m |
| 2026-06-23 | DVT → DVT | Jun 23, 14:39 UTC | Jun 23, 15:44 UTC | 1h 5m |
| 2026-06-22 | DVT → DVT | Jun 22, 14:34 UTC | Jun 22, 15:54 UTC | 1h 20m |
| 2026-06-21 | DVT → DVT | Jun 21, 15:09 UTC | Jun 21, 16:30 UTC | 1h 20m |
| 2026-06-19 | DVT → DVT | Jun 19, 15:04 UTC | Jun 19, 16:14 UTC | 1h 10m |
| 2026-06-19 | DVT → DVT | Jun 19, 03:49 UTC | Jun 19, 04:39 UTC | 50m |
| 2026-06-18 | DVT → DVT | Jun 18, 16:00 UTC | Jun 18, 16:55 UTC | 55m |
| 2026-06-17 | DVT → DVT | Jun 17, 16:00 UTC | Jun 17, 16:35 UTC | 35m |
| 2026-06-17 | DVT → DVT | Jun 17, 14:15 UTC | Jun 17, 15:35 UTC | 1h 20m |
| 2026-06-16 | DVT → DVT | Jun 16, 15:35 UTC | Jun 16, 16:05 UTC | 30m |
| 2026-06-15 | - | Jun 15, 17:34 UTC | Jun 15, 18:15 UTC | 40m |
| 2026-06-15 | - | Jun 15, 16:30 UTC | Jun 15, 17:04 UTC | 35m |
| 2026-06-15 | DVT → DVT | Jun 15, 14:30 UTC | Jun 15, 15:30 UTC | 1h 0m |
| 2026-06-10 | DVT → DVT | Jun 10, 15:25 UTC | Jun 10, 17:20 UTC | 1h 55m |
| 2026-06-09 | DVT → DVT | Jun 9, 22:20 UTC | Jun 9, 22:55 UTC | 35m |
| 2026-06-05 | DVT → DVT | Jun 5, 14:00 UTC | Jun 5, 16:45 UTC | 2h 45m |
| 2026-06-04 | DVT → DVT | Jun 4, 15:35 UTC | Jun 4, 17:00 UTC | 1h 25m |
| 2026-06-03 | DVT → DVT | Jun 3, 15:15 UTC | Jun 3, 16:20 UTC | 1h 5m |
| 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 |
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 5d ago.