Not currently tracked · last seen Jul 26, 17:45 UTC
- Flights observed
- 202 showing last 50
- Avg flight time
- 1h 40m
- Typical route
- CUR → BOG
- Last seen
- Jul 26, 17:45 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | - | Jul 26, 17:25 UTC | Jul 26, 17:45 UTC | 20m |
| 2026-07-26 | CUR → BOG | Jul 26, 15:10 UTC | Jul 26, 15:20 UTC | 10m |
| 2026-07-26 | CUR → BOG | Jul 26, 14:00 UTC | Jul 26, 14:15 UTC | 15m |
| 2026-07-26 | - | Jul 26, 10:45 UTC | Jul 26, 11:55 UTC | 1h 10m |
| 2026-07-26 | - | Jul 26, 07:25 UTC | Jul 26, 07:35 UTC | 10m |
| 2026-07-25 | - | Jul 25, 22:30 UTC | Jul 26, 00:05 UTC | 1h 35m |
| 2026-07-25 | BOG → LET | Jul 25, 19:45 UTC | Jul 25, 21:20 UTC | 1h 35m |
| 2026-07-25 | CUR → BOG | Jul 25, 14:15 UTC | Jul 25, 14:35 UTC | 20m |
| 2026-07-25 | CUR → BOG | Jul 25, 13:10 UTC | Jul 25, 13:25 UTC | 15m |
| 2026-07-24 | - | Jul 24, 22:00 UTC | Jul 25, 00:25 UTC | 2h 25m |
| 2026-07-24 | - | Jul 24, 17:20 UTC | Jul 24, 19:30 UTC | 2h 10m |
| 2026-07-24 | CUR → BOG | Jul 24, 13:45 UTC | Jul 24, 15:05 UTC | 1h 20m |
| 2026-07-24 | - | Jul 24, 10:50 UTC | Jul 24, 12:15 UTC | 1h 25m |
| 2026-07-24 | - | Jul 24, 00:00 UTC | Jul 24, 00:20 UTC | 20m |
| 2026-07-23 | - | Jul 23, 19:55 UTC | Jul 23, 20:05 UTC | 10m |
| 2026-07-23 | - | Jul 23, 17:50 UTC | Jul 23, 18:05 UTC | 15m |
| 2026-07-23 | CUR → BOG | Jul 23, 10:50 UTC | Jul 23, 15:10 UTC | 4h 20m |
| 2026-07-19 | - | Jul 19, 19:00 UTC | Jul 19, 21:25 UTC | 2h 25m |
| 2026-07-19 | - | Jul 19, 16:35 UTC | Jul 19, 16:45 UTC | 10m |
| 2026-07-19 | - | Jul 19, 14:35 UTC | Jul 19, 14:45 UTC | 10m |
| 2026-07-16 | - | Jul 16, 13:49 UTC | Jul 16, 14:00 UTC | 10m |
| 2026-07-15 | - | Jul 15, 17:45 UTC | Jul 15, 22:00 UTC | 4h 15m |
| 2026-07-12 | - | Jul 12, 23:50 UTC | Jul 13, 00:05 UTC | 15m |
| 2026-07-12 | - | Jul 12, 17:40 UTC | Jul 12, 19:55 UTC | 2h 15m |
| 2026-07-12 | - | Jul 12, 10:50 UTC | Jul 12, 15:15 UTC | 4h 25m |
| 2026-07-12 | - | Jul 12, 00:40 UTC | Jul 12, 02:45 UTC | 2h 5m |
| 2026-07-11 | - | Jul 11, 16:45 UTC | Jul 11, 16:55 UTC | 10m |
| 2026-07-11 | - | Jul 11, 14:35 UTC | Jul 11, 14:50 UTC | 15m |
| 2026-07-10 | - | Jul 10, 17:50 UTC | Jul 10, 20:05 UTC | 2h 15m |
| 2026-07-06 | - | Jul 6, 00:45 UTC | Jul 6, 03:05 UTC | 2h 20m |
| 2026-07-05 | - | Jul 5, 19:15 UTC | Jul 5, 19:30 UTC | 15m |
| 2026-07-04 | - | Jul 4, 23:05 UTC | Jul 5, 00:00 UTC | 55m |
| 2026-07-04 | - | Jul 4, 16:30 UTC | Jul 4, 16:40 UTC | 10m |
| 2026-07-01 | - | Jul 1, 20:35 UTC | Jul 1, 20:45 UTC | 10m |
| 2026-06-28 | - | Jun 28, 10:04 UTC | Jun 28, 13:34 UTC | 3h 30m |
| 2026-06-28 | - | Jun 28, 00:20 UTC | Jun 28, 01:10 UTC | 50m |
| 2026-06-21 | - | Jun 21, 00:19 UTC | Jun 21, 01:14 UTC | 55m |
| 2026-06-19 | - | Jun 19, 16:44 UTC | Jun 19, 17:04 UTC | 20m |
| 2026-06-18 | - | Jun 18, 15:20 UTC | Jun 18, 15:35 UTC | 15m |
| 2026-06-18 | - | Jun 18, 14:15 UTC | Jun 18, 14:30 UTC | 15m |
| 2026-06-18 | - | Jun 18, 08:05 UTC | Jun 18, 11:40 UTC | 3h 35m |
| 2026-06-18 | - | Jun 18, 00:45 UTC | Jun 18, 02:45 UTC | 2h 0m |
| 2026-06-17 | - | Jun 17, 15:50 UTC | Jun 17, 16:05 UTC | 15m |
| 2026-06-17 | SJO → BOG | Jun 17, 09:25 UTC | Jun 17, 12:50 UTC | 3h 25m |
| 2026-06-16 | - | Jun 16, 22:55 UTC | Jun 16, 23:05 UTC | 10m |
| 2026-06-16 | - | Jun 16, 20:40 UTC | Jun 16, 20:50 UTC | 10m |
| 2026-06-15 | - | Jun 15, 08:40 UTC | Jun 15, 15:55 UTC | 7h 15m |
| 2026-06-14 | - | Jun 14, 01:00 UTC | Jun 14, 17:25 UTC | 16h 25m |
| 2026-06-13 | - | Jun 13, 17:25 UTC | Jun 13, 17:35 UTC | 10m |
| 2026-06-12 | - | Jun 12, 23:40 UTC | Jun 13, 02:10 UTC | 2h 30m |
Specifications
| Registration | HK-5139 |
| Aircraft type | BOEING 737-400 (B734) |
| Mode-S code | 0AC333 · 02541463 (octal) |
Looking for transponder-level data? View the Mode-S 0AC333 page for country allocation, callsign history, and ADS-B signal details.
HK-5139 frequently asked
What type of aircraft is HK-5139?
HK-5139 is a BOEING 737-400 (ICAO type code B734).
What is the Mode-S transponder code for HK-5139?
HK-5139 broadcasts on Mode-S (ICAO 24-bit) address 0AC333 (octal 02541463). View the transponder page.
What route does HK-5139 typically fly?
HK-5139 most frequently flies between CUR and BOG based on observed flights.
Where is HK-5139 right now?
HK-5139 is not currently being tracked; last seen Jul 26, 17:45 UTC.