Not currently tracked · last seen 2h ago
- Flights observed
- 241 showing last 50
- Avg flight time
- 3h 42m
- Typical route
- BOG → CUN
- Last seen
- 2h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 04:45 UTC | Jul 14, 05:05 UTC | 20m |
| 2026-07-14 | - | Jul 14, 01:00 UTC | Jul 14, 01:20 UTC | 20m |
| 2026-07-13 | - | Jul 13, 19:50 UTC | Jul 13, 20:00 UTC | 10m |
| 2026-07-13 | - | Jul 13, 12:35 UTC | Jul 13, 12:50 UTC | 15m |
| 2026-07-12 | CUN → BOG | Jul 12, 23:35 UTC | Jul 13, 02:20 UTC | 2h 45m |
| 2026-07-12 | BOG → CUN | Jul 12, 19:01 UTC | Jul 12, 22:05 UTC | 3h 5m |
| 2026-07-12 | - | Jul 12, 17:01 UTC | Jul 12, 17:20 UTC | 20m |
| 2026-07-12 | - | Jul 12, 15:55 UTC | Jul 12, 16:05 UTC | 10m |
| 2026-07-12 | - | Jul 12, 13:15 UTC | Jul 12, 13:35 UTC | 20m |
| 2026-07-12 | - | Jul 12, 05:50 UTC | Jul 12, 11:50 UTC | 6h 0m |
| 2026-07-11 | - | Jul 11, 23:55 UTC | Jul 12, 03:55 UTC | 4h 0m |
| 2026-07-11 | - | Jul 11, 22:50 UTC | Jul 11, 23:05 UTC | 15m |
| 2026-07-11 | - | Jul 11, 18:25 UTC | Jul 11, 21:15 UTC | 2h 50m |
| 2026-07-11 | - | Jul 11, 15:10 UTC | Jul 11, 16:50 UTC | 1h 40m |
| 2026-07-11 | - | Jul 11, 05:55 UTC | Jul 11, 12:00 UTC | 6h 5m |
| 2026-07-10 | - | Jul 10, 23:50 UTC | Jul 11, 04:30 UTC | 4h 40m |
| 2026-07-10 | - | Jul 10, 21:00 UTC | Jul 10, 21:10 UTC | 10m |
| 2026-07-10 | - | Jul 10, 18:35 UTC | Jul 10, 20:00 UTC | 1h 25m |
| 2026-07-10 | BOG → CUN | Jul 10, 13:55 UTC | Jul 10, 17:10 UTC | 3h 15m |
| 2026-07-09 | - | Jul 9, 20:20 UTC | Jul 10, 02:15 UTC | 5h 55m |
| 2026-07-09 | - | Jul 9, 14:35 UTC | Jul 9, 18:40 UTC | 4h 5m |
| 2026-07-09 | - | Jul 9, 13:35 UTC | Jul 9, 13:45 UTC | 10m |
| 2026-07-09 | - | Jul 9, 04:45 UTC | Jul 9, 09:45 UTC | 5h 0m |
| 2026-07-08 | YYZ → EZE | Jul 8, 13:15 UTC | Jul 9, 03:05 UTC | 13h 50m |
| 2026-07-08 | - | Jul 8, 08:10 UTC | Jul 8, 11:05 UTC | 2h 55m |
| 2026-07-07 | - | Jul 7, 22:40 UTC | Jul 7, 23:55 UTC | 1h 15m |
| 2026-07-07 | BOG → CZE | Jul 7, 19:40 UTC | Jul 7, 20:45 UTC | 1h 5m |
| 2026-07-07 | - | Jul 7, 10:20 UTC | Jul 7, 16:25 UTC | 6h 5m |
| 2026-07-07 | - | Jul 7, 03:55 UTC | Jul 7, 08:30 UTC | 4h 35m |
| 2026-07-07 | - | Jul 7, 00:45 UTC | Jul 7, 00:55 UTC | 10m |
| 2026-07-06 | - | Jul 6, 20:25 UTC | Jul 6, 23:25 UTC | 3h 0m |
| 2026-07-06 | - | Jul 6, 15:00 UTC | Jul 6, 18:15 UTC | 3h 15m |
| 2026-07-06 | BOG → GIR | Jul 6, 04:10 UTC | Jul 6, 04:20 UTC | 10m |
| 2026-07-06 | SDQ → BOG | Jul 6, 02:20 UTC | Jul 6, 02:40 UTC | 20m |
| 2026-07-05 | - | Jul 5, 13:30 UTC | Jul 5, 16:20 UTC | 2h 50m |
| 2026-07-05 | - | Jul 5, 09:00 UTC | Jul 5, 11:25 UTC | 2h 25m |
| 2026-07-04 | - | Jul 4, 21:40 UTC | Jul 4, 21:50 UTC | 10m |
| 2026-07-04 | - | Jul 4, 10:10 UTC | Jul 4, 15:10 UTC | 5h 0m |
| 2026-07-03 | TPA → AEP | Jul 3, 21:00 UTC | Jul 4, 08:15 UTC | 11h 15m |
| 2026-07-03 | BOG → TPA | Jul 3, 17:55 UTC | Jul 3, 18:55 UTC | 1h 0m |
| 2026-07-02 | - | Jul 2, 06:35 UTC | Jul 3, 00:50 UTC | 18h 15m |
| 2026-07-02 | - | Jul 2, 05:20 UTC | Jul 3, 00:50 UTC | 19h 30m |
| 2026-07-02 | - | Jul 2, 00:35 UTC | Jul 2, 02:55 UTC | 2h 20m |
| 2026-07-01 | - | Jul 1, 00:50 UTC | Jul 1, 01:40 UTC | 50m |
| 2026-06-30 | - | Jun 30, 21:35 UTC | Jun 30, 22:35 UTC | 1h 0m |
| 2026-06-30 | - | Jun 30, 17:35 UTC | Jun 30, 19:10 UTC | 1h 35m |
| 2026-06-29 | GRU → BOG | Jun 29, 20:30 UTC | Jun 30, 01:14 UTC | 4h 45m |
| 2026-06-29 | - | Jun 29, 05:59 UTC | Jun 29, 18:39 UTC | 12h 40m |
| 2026-06-28 | - | Jun 28, 23:14 UTC | Jun 29, 00:10 UTC | 55m |
| 2026-06-28 | JFK → BOG | Jun 28, 11:55 UTC | Jun 28, 22:34 UTC | 10h 40m |
Specifications
| Registration | HK-5368 |
| Aircraft type | AIRBUS A-320neo (A20N) |
| Mode-S code | 0AC9F2 · 02544762 (octal) |
Looking for transponder-level data? View the Mode-S 0AC9F2 page for country allocation, callsign history, and ADS-B signal details.
HK-5368 frequently asked
What type of aircraft is HK-5368?
HK-5368 is a AIRBUS A-320neo (ICAO type code A20N).
What is the Mode-S transponder code for HK-5368?
HK-5368 broadcasts on Mode-S (ICAO 24-bit) address 0AC9F2 (octal 02544762). View the transponder page.
What route does HK-5368 typically fly?
HK-5368 most frequently flies between BOG and CUN based on observed flights.
Where is HK-5368 right now?
HK-5368 is not currently being tracked; last seen 2h ago.