Not currently tracked · last seen Jul 24, 15:25 UTC
- Flights observed
- 213 showing last 50
- Avg flight time
- 5h 52m
- Typical route
- GYD → AYT
- Last seen
- Jul 24, 15:25 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-24 | - | Jul 24, 15:05 UTC | Jul 24, 15:25 UTC | 20m |
| 2026-07-24 | GYD → AYT | Jul 24, 06:35 UTC | Jul 24, 13:20 UTC | 6h 45m |
| 2026-07-24 | GYD → AYT | Jul 24, 02:30 UTC | Jul 24, 04:55 UTC | 2h 25m |
| 2026-07-22 | BOM → GYD | Jul 22, 23:10 UTC | Jul 23, 00:00 UTC | 50m |
| 2026-07-22 | GYD → BOM | Jul 22, 04:25 UTC | Jul 22, 21:25 UTC | 17h 0m |
| 2026-07-21 | GYD → SSH | Jul 21, 14:05 UTC | Jul 22, 11:40 UTC | 21h 35m |
| 2026-07-21 | KVD → LED | Jul 21, 12:05 UTC | Jul 22, 11:40 UTC | 23h 35m |
| 2026-07-21 | - | Jul 21, 07:45 UTC | Jul 21, 10:20 UTC | 2h 35m |
| 2026-07-20 | SSH → GYD | Jul 20, 09:20 UTC | Jul 20, 11:50 UTC | 2h 30m |
| 2026-07-20 | GYD → SSH | Jul 20, 04:50 UTC | Jul 20, 07:30 UTC | 2h 40m |
| 2026-07-19 | SAW → GYD | Jul 19, 07:55 UTC | Jul 19, 09:45 UTC | 1h 50m |
| 2026-07-19 | GYD → SAW | Jul 19, 03:45 UTC | Jul 19, 06:05 UTC | 2h 20m |
| 2026-07-18 | TIV → GYD | Jul 18, 11:15 UTC | Jul 18, 14:05 UTC | 2h 50m |
| 2026-07-18 | GYD → TIV | Jul 18, 06:00 UTC | Jul 18, 09:05 UTC | 3h 5m |
| 2026-07-17 | TIV → GYD | Jul 17, 10:50 UTC | Jul 17, 13:35 UTC | 2h 45m |
| 2026-07-16 | GYD → TIV | Jul 16, 21:15 UTC | Jul 17, 09:15 UTC | 12h 0m |
| 2026-07-16 | - | Jul 16, 18:25 UTC | Jul 16, 19:30 UTC | 1h 5m |
| 2026-07-15 | - | Jul 15, 20:20 UTC | Jul 15, 20:40 UTC | 20m |
| 2026-07-15 | - | Jul 15, 18:20 UTC | Jul 15, 18:45 UTC | 25m |
| 2026-07-14 | - | Jul 14, 05:30 UTC | Jul 14, 05:45 UTC | 15m |
| 2026-07-12 | - | Jul 12, 13:25 UTC | Jul 12, 15:25 UTC | 2h 0m |
| 2026-07-12 | - | Jul 12, 09:25 UTC | Jul 12, 11:40 UTC | 2h 15m |
| 2026-07-12 | - | Jul 12, 06:25 UTC | Jul 12, 06:55 UTC | 30m |
| 2026-07-12 | - | Jul 12, 04:30 UTC | Jul 12, 05:01 UTC | 30m |
| 2026-07-11 | - | Jul 11, 10:50 UTC | Jul 11, 13:35 UTC | 2h 45m |
| 2026-07-10 | - | Jul 10, 14:40 UTC | Jul 11, 09:15 UTC | 18h 35m |
| 2026-07-10 | - | Jul 10, 10:50 UTC | Jul 10, 13:25 UTC | 2h 35m |
| 2026-07-10 | - | Jul 10, 06:50 UTC | Jul 10, 08:30 UTC | 1h 40m |
| 2026-07-10 | - | Jul 10, 02:25 UTC | Jul 10, 04:55 UTC | 2h 30m |
| 2026-07-09 | - | Jul 9, 11:10 UTC | Jul 9, 13:45 UTC | 2h 35m |
| 2026-07-09 | - | Jul 9, 00:00 UTC | Jul 9, 09:35 UTC | 9h 35m |
| 2026-07-08 | - | Jul 8, 10:50 UTC | Jul 8, 22:20 UTC | 11h 30m |
| 2026-07-08 | - | Jul 8, 05:55 UTC | Jul 8, 09:00 UTC | 3h 5m |
| 2026-07-07 | - | Jul 7, 09:55 UTC | Jul 7, 13:30 UTC | 3h 35m |
| 2026-07-07 | - | Jul 7, 04:10 UTC | Jul 7, 08:35 UTC | 4h 25m |
| 2026-07-06 | - | Jul 6, 04:35 UTC | Jul 6, 11:50 UTC | 7h 15m |
| 2026-07-05 | - | Jul 5, 10:05 UTC | Jul 6, 10:00 UTC | 23h 55m |
| 2026-07-05 | - | Jul 5, 09:55 UTC | Jul 6, 07:25 UTC | 21h 30m |
| 2026-07-04 | - | Jul 4, 23:40 UTC | Jul 5, 07:30 UTC | 7h 50m |
| 2026-07-02 | - | Jul 2, 10:20 UTC | Jul 2, 12:35 UTC | 2h 15m |
| 2026-07-02 | - | Jul 2, 00:05 UTC | Jul 2, 08:55 UTC | 8h 50m |
| 2026-07-01 | - | Jul 1, 11:45 UTC | Jul 1, 22:20 UTC | 10h 35m |
| 2026-07-01 | - | Jul 1, 00:00 UTC | Jul 1, 09:00 UTC | 9h 0m |
| 2026-06-30 | GYD → DEL | Jun 30, 21:40 UTC | Jun 30, 22:35 UTC | 55m |
| 2026-06-30 | - | Jun 30, 14:40 UTC | Jun 30, 16:25 UTC | 1h 45m |
| 2026-06-30 | - | Jun 30, 06:10 UTC | Jun 30, 13:20 UTC | 7h 10m |
| 2026-06-30 | - | Jun 30, 02:15 UTC | Jun 30, 04:40 UTC | 2h 25m |
| 2026-06-28 | - | Jun 28, 23:14 UTC | Jun 29, 10:59 UTC | 11h 45m |
| 2026-06-28 | - | Jun 28, 20:09 UTC | Jun 28, 21:20 UTC | 1h 10m |
| 2026-06-28 | - | Jun 28, 08:09 UTC | Jun 28, 09:55 UTC | 1h 45m |
Specifications
| Registration | 4K-AZ80 |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 600850 · 30004120 (octal) |
Looking for transponder-level data? View the Mode-S 600850 page for country allocation, callsign history, and ADS-B signal details.
4K-AZ80 frequently asked
What type of aircraft is 4K-AZ80?
4K-AZ80 is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for 4K-AZ80?
4K-AZ80 broadcasts on Mode-S (ICAO 24-bit) address 600850 (octal 30004120). View the transponder page.
What route does 4K-AZ80 typically fly?
4K-AZ80 most frequently flies between GYD and AYT based on observed flights.
Where is 4K-AZ80 right now?
4K-AZ80 is not currently being tracked; last seen Jul 24, 15:25 UTC.