Not currently tracked · last seen 13h ago
- Flights observed
- 83 showing last 50
- Avg flight time
- 53m
- Typical route
- -
- Last seen
- 13h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | - | May 29, 20:40 UTC | May 29, 21:05 UTC | 25m |
| 2026-05-29 | - | May 29, 17:00 UTC | May 29, 17:45 UTC | 45m |
| 2026-05-28 | - | May 28, 17:05 UTC | May 28, 18:15 UTC | 1h 10m |
| 2026-05-28 | - | May 28, 13:30 UTC | May 28, 14:30 UTC | 1h 0m |
| 2026-05-27 | - | May 27, 14:20 UTC | May 27, 14:45 UTC | 25m |
| 2026-05-19 | - | May 19, 20:05 UTC | May 19, 21:20 UTC | 1h 15m |
| 2026-05-19 | - | May 19, 17:05 UTC | May 19, 18:00 UTC | 55m |
| 2026-05-17 | - | May 17, 02:30 UTC | May 17, 03:35 UTC | 1h 5m |
| 2026-05-16 | - | May 16, 22:00 UTC | May 16, 23:25 UTC | 1h 25m |
| 2026-05-16 | - | May 16, 15:50 UTC | May 16, 16:25 UTC | 35m |
| 2026-05-15 | - | May 15, 18:20 UTC | May 15, 18:55 UTC | 35m |
| 2026-05-15 | - | May 15, 15:25 UTC | May 15, 16:45 UTC | 1h 20m |
| 2026-05-15 | - | May 15, 12:15 UTC | May 15, 12:55 UTC | 40m |
| 2026-05-13 | - | May 13, 15:35 UTC | May 13, 16:50 UTC | 1h 15m |
| 2026-05-13 | - | May 13, 12:15 UTC | May 13, 13:10 UTC | 55m |
| 2026-05-11 | - | May 11, 18:25 UTC | May 11, 19:30 UTC | 1h 5m |
| 2026-05-11 | - | May 11, 15:30 UTC | May 11, 16:30 UTC | 1h 0m |
| 2026-05-11 | - | May 11, 12:35 UTC | May 11, 13:20 UTC | 45m |
| 2026-05-10 | - | May 10, 19:30 UTC | May 10, 19:54 UTC | 25m |
| 2026-05-10 | - | May 10, 17:05 UTC | May 10, 18:29 UTC | 1h 25m |
| 2026-05-09 | - | May 9, 21:14 UTC | May 9, 21:50 UTC | 35m |
| 2026-05-09 | - | May 9, 20:30 UTC | May 9, 20:40 UTC | 10m |
| 2026-05-09 | - | May 9, 17:30 UTC | May 9, 19:05 UTC | 1h 35m |
| 2026-05-09 | TOP → DSM | May 9, 02:05 UTC | May 9, 03:55 UTC | 1h 50m |
| 2026-05-08 | - | May 8, 20:30 UTC | May 8, 21:25 UTC | 55m |
| 2026-05-08 | - | May 8, 13:45 UTC | May 8, 14:45 UTC | 1h 0m |
| 2026-05-07 | - | May 7, 19:35 UTC | May 7, 20:30 UTC | 55m |
| 2026-05-07 | - | May 7, 17:30 UTC | May 7, 17:40 UTC | 10m |
| 2026-05-07 | - | May 7, 16:35 UTC | May 7, 16:45 UTC | 10m |
| 2026-05-07 | - | May 7, 14:15 UTC | May 7, 14:55 UTC | 40m |
| 2026-05-06 | - | May 6, 20:36 UTC | May 6, 21:00 UTC | 24m |
| 2026-05-06 | - | May 6, 16:40 UTC | May 6, 17:25 UTC | 45m |
| 2026-05-06 | - | May 6, 13:35 UTC | May 6, 14:40 UTC | 1h 5m |
| 2026-05-04 | - | May 4, 19:45 UTC | May 4, 20:55 UTC | 1h 10m |
| 2026-05-04 | - | May 4, 17:00 UTC | May 4, 18:10 UTC | 1h 10m |
| 2026-05-04 | - | May 4, 13:55 UTC | May 4, 14:25 UTC | 30m |
| 2026-05-01 | - | May 1, 19:45 UTC | May 1, 20:25 UTC | 40m |
| 2026-05-01 | - | May 1, 16:05 UTC | May 1, 16:55 UTC | 50m |
| 2026-05-01 | - | May 1, 01:55 UTC | May 1, 03:20 UTC | 1h 25m |
| 2026-04-30 | - | Apr 30, 22:05 UTC | Apr 30, 23:25 UTC | 1h 20m |
| 2026-04-30 | - | Apr 30, 19:25 UTC | Apr 30, 20:10 UTC | 45m |
| 2026-04-30 | - | Apr 30, 16:40 UTC | Apr 30, 17:30 UTC | 50m |
| 2026-04-30 | - | Apr 30, 02:00 UTC | Apr 30, 03:25 UTC | 1h 25m |
| 2026-04-29 | - | Apr 29, 22:40 UTC | Apr 29, 23:35 UTC | 54m |
| 2026-04-29 | - | Apr 29, 20:30 UTC | Apr 29, 21:00 UTC | 30m |
| 2026-04-29 | - | Apr 29, 17:10 UTC | Apr 29, 17:45 UTC | 35m |
| 2026-04-28 | - | Apr 28, 01:40 UTC | Apr 28, 03:10 UTC | 1h 30m |
| 2026-04-27 | - | Apr 27, 21:50 UTC | Apr 27, 22:00 UTC | 10m |
| 2026-04-27 | - | Apr 27, 19:00 UTC | Apr 27, 20:20 UTC | 1h 20m |
| 2026-04-27 | - | Apr 27, 16:10 UTC | Apr 27, 17:00 UTC | 50m |
Specifications
| Registration | 01-3620 |
| Aircraft type | BEECHCRAFT T-6 Texan 2 (TEX2) |
| Mode-S code | AE1108 · 53410410 (octal) |
Looking for transponder-level data? View the Mode-S AE1108 page for country allocation, callsign history, and ADS-B signal details.
01-3620 frequently asked
What type of aircraft is 01-3620?
01-3620 is a BEECHCRAFT T-6 Texan 2 (ICAO type code TEX2).
What is the Mode-S transponder code for 01-3620?
01-3620 broadcasts on Mode-S (ICAO 24-bit) address AE1108 (octal 53410410). View the transponder page.
Where is 01-3620 right now?
01-3620 is not currently being tracked; last seen 13h ago.