Not currently tracked · last seen 4d ago
- Flights observed
- 51 showing last 50
- Avg flight time
- 2h 51m
- Typical route
- GYE → BOG
- Last seen
- 4d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-25 | BOG → UIO | May 25, 12:35 UTC | May 25, 12:55 UTC | 20m |
| 2026-05-25 | BOG → GYE | May 25, 03:00 UTC | May 25, 10:05 UTC | 7h 5m |
| 2026-05-23 | BOG → GYE | May 23, 18:05 UTC | May 23, 18:15 UTC | 11m |
| 2026-05-22 | GYE → BOG | May 22, 21:55 UTC | May 23, 15:45 UTC | 17h 50m |
| 2026-05-22 | UIO → BOG | May 22, 12:30 UTC | May 22, 16:35 UTC | 4h 5m |
| 2026-05-22 | CLO → BOG | May 22, 09:50 UTC | May 22, 10:05 UTC | 15m |
| 2026-05-22 | BOG → GYE | May 22, 03:40 UTC | May 22, 03:55 UTC | 15m |
| 2026-05-22 | GYE → BOG | May 22, 01:35 UTC | May 22, 01:55 UTC | 20m |
| 2026-05-21 | BOG → UIO | May 21, 12:30 UTC | May 21, 12:50 UTC | 20m |
| 2026-05-20 | UIO → BOG | May 20, 21:25 UTC | May 21, 01:35 UTC | 4h 10m |
| 2026-05-20 | UIO → BOG | May 20, 16:00 UTC | May 20, 16:25 UTC | 25m |
| 2026-05-08 | MIA → GYE | May 8, 06:20 UTC | May 8, 08:09 UTC | 1h 50m |
| 2026-05-08 | GYE → MIA | May 8, 02:29 UTC | May 8, 04:29 UTC | 2h 0m |
| 2026-05-03 | MIA → GYE | May 3, 05:55 UTC | May 3, 07:50 UTC | 1h 55m |
| 2026-05-03 | GYE → MIA | May 3, 02:00 UTC | May 3, 03:45 UTC | 1h 44m |
| 2026-04-28 | GYE → BOG | Apr 28, 01:10 UTC | Apr 28, 01:30 UTC | 20m |
| 2026-04-27 | BOG → GYE | Apr 27, 21:10 UTC | Apr 27, 21:25 UTC | 15m |
| 2026-04-27 | BOG → UIO | Apr 27, 05:00 UTC | Apr 27, 16:30 UTC | 11h 30m |
| 2026-04-26 | MIA → GYE | Apr 26, 07:20 UTC | Apr 27, 01:45 UTC | 18h 25m |
| 2026-04-26 | MIA → GYE | Apr 26, 05:55 UTC | Apr 27, 01:45 UTC | 19h 50m |
| 2026-04-26 | GYE → MIA | Apr 26, 02:00 UTC | Apr 26, 03:50 UTC | 1h 50m |
| 2026-04-25 | GYE → MIA | Apr 25, 05:35 UTC | Apr 26, 03:50 UTC | 22h 15m |
| 2026-04-25 | GYE → BOG | Apr 25, 01:55 UTC | Apr 25, 02:15 UTC | 20m |
| 2026-04-24 | BOG → UIO | Apr 24, 12:30 UTC | Apr 24, 12:35 UTC | 5m |
| 2026-04-24 | BOG → UIO | Apr 24, 05:05 UTC | Apr 24, 08:40 UTC | 3h 35m |
| 2026-04-23 | GYE → BOG | Apr 23, 21:30 UTC | Apr 24, 02:00 UTC | 4h 30m |
| 2026-04-23 | GYE → BOG | Apr 23, 12:40 UTC | Apr 23, 17:00 UTC | 4h 20m |
| 2026-04-23 | GYE → BOG | Apr 23, 09:45 UTC | Apr 23, 10:15 UTC | 30m |
| 2026-04-23 | - | Apr 23, 03:35 UTC | Apr 23, 03:50 UTC | 15m |
| 2026-04-23 | UIO → BOG | Apr 23, 01:10 UTC | Apr 23, 01:45 UTC | 35m |
| 2026-04-20 | MIA → GYE | Apr 20, 06:50 UTC | Apr 20, 08:40 UTC | 1h 50m |
| 2026-04-20 | GYE → MIA | Apr 20, 02:30 UTC | Apr 20, 04:20 UTC | 1h 50m |
| 2026-04-18 | MIA → GYE | Apr 18, 08:00 UTC | Apr 18, 08:20 UTC | 20m |
| 2026-04-18 | MIA → GYE | Apr 18, 06:35 UTC | Apr 18, 07:05 UTC | 30m |
| 2026-04-18 | GYE → MIA | Apr 18, 04:10 UTC | Apr 18, 04:40 UTC | 30m |
| 2026-04-18 | GYE → MIA | Apr 18, 02:45 UTC | Apr 18, 02:55 UTC | 10m |
| 2026-04-16 | BOG → UIO | Apr 16, 06:25 UTC | Apr 16, 06:45 UTC | 20m |
| 2026-04-16 | GYE → BOG | Apr 16, 01:25 UTC | Apr 16, 01:50 UTC | 25m |
| 2026-04-15 | - | Apr 15, 21:45 UTC | Apr 15, 22:00 UTC | 15m |
| 2026-04-15 | - | Apr 15, 18:05 UTC | Apr 15, 18:30 UTC | 25m |
| 2026-04-15 | UIO → BOG | Apr 15, 12:05 UTC | Apr 15, 12:25 UTC | 20m |
| 2026-04-15 | UIO → BOG | Apr 15, 09:25 UTC | Apr 15, 09:50 UTC | 25m |
| 2026-04-15 | GYE → BOG | Apr 15, 01:10 UTC | Apr 15, 01:30 UTC | 20m |
| 2026-04-14 | - | Apr 14, 21:00 UTC | Apr 14, 21:15 UTC | 15m |
| 2026-04-14 | - | Apr 14, 16:05 UTC | Apr 14, 16:25 UTC | 20m |
| 2026-04-14 | BOG → UIO | Apr 14, 12:30 UTC | Apr 14, 12:45 UTC | 15m |
| 2026-04-14 | - | Apr 14, 09:20 UTC | Apr 14, 09:50 UTC | 30m |
| 2026-04-13 | - | Apr 13, 07:55 UTC | Apr 13, 08:05 UTC | 10m |
| 2026-04-13 | - | Apr 13, 06:20 UTC | Apr 13, 08:05 UTC | 1h 45m |
| 2026-04-13 | GYE → MIA | Apr 13, 03:55 UTC | Apr 13, 04:15 UTC | 20m |
Specifications
| Registration | HC-CTX |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | E84084 · 72040204 (octal) |
Looking for transponder-level data? View the Mode-S E84084 page for country allocation, callsign history, and ADS-B signal details.
HC-CTX frequently asked
What type of aircraft is HC-CTX?
HC-CTX is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for HC-CTX?
HC-CTX broadcasts on Mode-S (ICAO 24-bit) address E84084 (octal 72040204). View the transponder page.
What route does HC-CTX typically fly?
HC-CTX most frequently flies between GYE and BOG based on observed flights.
Where is HC-CTX right now?
HC-CTX is not currently being tracked; last seen 4d ago.