Not currently tracked · last seen 1h ago
- Flights observed
- 89 showing last 50
- Avg flight time
- 2h 34m
- Typical route
- BOG → BOG
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 04:50 UTC | Jul 14, 05:00 UTC | 10m |
| 2026-07-14 | - | Jul 14, 00:45 UTC | Jul 14, 01:15 UTC | 30m |
| 2026-07-13 | BOG → BOG | Jul 13, 12:20 UTC | Jul 13, 16:30 UTC | 4h 10m |
| 2026-07-13 | - | Jul 13, 03:50 UTC | Jul 13, 04:10 UTC | 20m |
| 2026-07-12 | BOG → BOG | Jul 12, 21:05 UTC | Jul 13, 01:30 UTC | 4h 25m |
| 2026-07-12 | BOG → BOG | Jul 12, 12:15 UTC | Jul 12, 16:35 UTC | 4h 20m |
| 2026-07-12 | - | Jul 12, 09:20 UTC | Jul 12, 09:50 UTC | 30m |
| 2026-07-11 | BOG → BOG | Jul 11, 12:10 UTC | Jul 12, 09:50 UTC | 21h 40m |
| 2026-07-11 | - | Jul 11, 09:45 UTC | Jul 11, 10:10 UTC | 25m |
| 2026-07-11 | - | Jul 11, 01:10 UTC | Jul 11, 01:30 UTC | 20m |
| 2026-07-10 | BOG → BOG | Jul 10, 12:20 UTC | Jul 10, 16:30 UTC | 4h 10m |
| 2026-07-07 | BOG → BOG | Jul 7, 21:35 UTC | Jul 8, 01:05 UTC | 3h 30m |
| 2026-07-07 | - | Jul 7, 16:15 UTC | Jul 7, 16:45 UTC | 30m |
| 2026-07-07 | - | Jul 7, 01:10 UTC | Jul 7, 01:35 UTC | 25m |
| 2026-06-19 | - | Jun 19, 04:50 UTC | Jun 19, 05:09 UTC | 20m |
| 2026-06-19 | - | Jun 19, 01:10 UTC | Jun 19, 01:29 UTC | 20m |
| 2026-06-18 | - | Jun 18, 21:15 UTC | Jun 18, 21:25 UTC | 10m |
| 2026-06-18 | BOG → BOG | Jun 18, 12:15 UTC | Jun 18, 16:50 UTC | 4h 35m |
| 2026-06-18 | BOG → BOG | Jun 18, 03:20 UTC | Jun 18, 10:10 UTC | 6h 50m |
| 2026-06-18 | - | Jun 18, 00:55 UTC | Jun 18, 01:15 UTC | 20m |
| 2026-06-15 | BOG → UIO | Jun 15, 21:20 UTC | Jun 16, 01:10 UTC | 3h 50m |
| 2026-06-15 | UIO → BOG | Jun 15, 15:55 UTC | Jun 15, 16:09 UTC | 15m |
| 2026-06-15 | UIO → BOG | Jun 15, 10:09 UTC | Jun 15, 10:35 UTC | 25m |
| 2026-06-15 | - | Jun 15, 01:00 UTC | Jun 15, 01:25 UTC | 25m |
| 2026-06-14 | BOG → GYE | Jun 14, 20:50 UTC | Jun 14, 21:05 UTC | 15m |
| 2026-06-11 | BOG → UIO | Jun 11, 04:50 UTC | Jun 11, 05:10 UTC | 20m |
| 2026-06-10 | BOG → GYE | Jun 10, 21:05 UTC | Jun 11, 01:35 UTC | 4h 30m |
| 2026-06-10 | BOG → GYE | Jun 10, 12:20 UTC | Jun 10, 16:45 UTC | 4h 25m |
| 2026-06-10 | BOG → GYE | Jun 10, 03:15 UTC | Jun 10, 10:20 UTC | 7h 5m |
| 2026-06-10 | GYE → BOG | Jun 10, 01:00 UTC | Jun 10, 01:25 UTC | 25m |
| 2026-06-09 | BOG → GYE | Jun 9, 21:00 UTC | Jun 9, 21:15 UTC | 15m |
| 2026-06-09 | UIO → BOG | Jun 9, 19:00 UTC | Jun 9, 19:20 UTC | 20m |
| 2026-06-04 | MIA → GYE | Jun 4, 05:55 UTC | Jun 4, 07:40 UTC | 1h 45m |
| 2026-06-04 | GYE → MIA | Jun 4, 02:05 UTC | Jun 4, 03:55 UTC | 1h 50m |
| 2026-06-01 | MIA → GYE | Jun 1, 05:55 UTC | Jun 1, 07:40 UTC | 1h 45m |
| 2026-06-01 | GYE → MIA | Jun 1, 02:10 UTC | Jun 1, 04:05 UTC | 1h 55m |
| 2026-05-30 | MIA → GYE | May 30, 05:45 UTC | May 30, 07:35 UTC | 1h 50m |
| 2026-05-30 | GYE → MIA | May 30, 02:00 UTC | May 30, 03:50 UTC | 1h 50m |
| 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 |
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 BOG and BOG based on observed flights.
Where is HC-CTX right now?
HC-CTX is not currently being tracked; last seen 1h ago.