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