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