Not currently tracked · last seen 22h ago
- Flights observed
- 200 showing last 50
- Avg flight time
- 40m
- Typical route
- BOG → MTR
- Last seen
- 22h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-02 | MTR → BOG | Jun 2, 03:05 UTC | Jun 2, 03:25 UTC | 20m |
| 2026-06-02 | MTR → BOG | Jun 2, 01:45 UTC | Jun 2, 01:55 UTC | 10m |
| 2026-06-02 | BOG → MTR | Jun 2, 00:25 UTC | Jun 2, 00:30 UTC | 5m |
| 2026-06-01 | BOG → CCS | Jun 1, 16:05 UTC | Jun 1, 16:20 UTC | 15m |
| 2026-06-01 | RCH → BOG | Jun 1, 14:05 UTC | Jun 1, 14:25 UTC | 20m |
| 2026-06-01 | MTR → BOG | Jun 1, 02:45 UTC | Jun 1, 03:00 UTC | 15m |
| 2026-06-01 | BOG → MTR | Jun 1, 00:00 UTC | Jun 1, 00:20 UTC | 20m |
| 2026-05-31 | MDE → BOG | May 31, 22:40 UTC | May 31, 22:55 UTC | 15m |
| 2026-05-31 | BOG → MDE | May 31, 17:50 UTC | May 31, 18:05 UTC | 15m |
| 2026-05-31 | SMR → BOG | May 31, 15:20 UTC | May 31, 15:35 UTC | 15m |
| 2026-05-31 | BOG → BGA | May 31, 12:35 UTC | May 31, 12:45 UTC | 10m |
| 2026-05-31 | BOG → MTR | May 31, 00:35 UTC | May 31, 00:40 UTC | 5m |
| 2026-05-30 | BOG → CLO | May 30, 19:30 UTC | May 30, 21:10 UTC | 1h 40m |
| 2026-05-30 | CLO → BOG | May 30, 17:35 UTC | May 30, 18:10 UTC | 35m |
| 2026-05-30 | CLO → BOG | May 30, 16:35 UTC | May 30, 16:50 UTC | 15m |
| 2026-05-30 | MDE → BOG | May 30, 14:30 UTC | May 30, 14:45 UTC | 15m |
| 2026-05-30 | BOG → SMR | May 30, 04:30 UTC | May 30, 04:40 UTC | 10m |
| 2026-05-30 | MTR → BOG | May 30, 03:10 UTC | May 30, 03:35 UTC | 25m |
| 2026-05-30 | MTR → BOG | May 30, 01:50 UTC | May 30, 01:55 UTC | 5m |
| 2026-05-30 | BOG → MTR | May 30, 00:30 UTC | May 30, 00:40 UTC | 10m |
| 2026-05-29 | BOG → MTR | May 29, 23:00 UTC | May 29, 23:20 UTC | 20m |
| 2026-05-29 | CTG → BOG | May 29, 17:50 UTC | May 29, 21:35 UTC | 3h 45m |
| 2026-05-29 | MDE → BOG | May 29, 16:20 UTC | May 29, 16:35 UTC | 15m |
| 2026-05-29 | ADZ → MDE | May 29, 13:45 UTC | May 29, 13:55 UTC | 10m |
| 2026-05-29 | MDE → ADZ | May 29, 12:45 UTC | May 29, 12:50 UTC | 5m |
| 2026-05-29 | BOG → MDE | May 29, 02:50 UTC | May 29, 03:00 UTC | 10m |
| 2026-05-28 | MCO → BOG | May 28, 21:45 UTC | May 29, 01:20 UTC | 3h 35m |
| 2026-05-28 | BOG → MCO | May 28, 18:50 UTC | May 28, 19:55 UTC | 1h 5m |
| 2026-05-28 | BOG → MCO | May 28, 16:10 UTC | May 28, 16:25 UTC | 15m |
| 2026-05-28 | PEI → BOG | May 28, 13:20 UTC | May 28, 13:35 UTC | 15m |
| 2026-05-28 | SMR → BOG | May 28, 02:50 UTC | May 28, 03:05 UTC | 15m |
| 2026-05-27 | BOG → BAQ | May 27, 23:55 UTC | May 28, 00:05 UTC | 10m |
| 2026-05-27 | MIA → BOG | May 27, 22:10 UTC | May 27, 22:25 UTC | 15m |
| 2026-05-27 | MIA → BOG | May 27, 19:15 UTC | May 27, 19:40 UTC | 25m |
| 2026-05-27 | BOG → MIA | May 27, 13:55 UTC | May 27, 17:10 UTC | 3h 15m |
| 2026-05-27 | MDE → BOG | May 27, 11:55 UTC | May 27, 12:10 UTC | 15m |
| 2026-05-26 | MIA → BOG | May 26, 19:20 UTC | May 26, 19:45 UTC | 25m |
| 2026-05-26 | BOG → MIA | May 26, 16:50 UTC | May 26, 17:20 UTC | 30m |
| 2026-05-26 | BOG → MIA | May 26, 14:00 UTC | May 26, 14:14 UTC | 15m |
| 2026-05-26 | MDE → BOG | May 26, 11:15 UTC | May 26, 11:34 UTC | 20m |
| 2026-05-26 | BOG → MDE | May 26, 00:14 UTC | May 26, 00:29 UTC | 15m |
| 2026-05-25 | BOG → BAQ | May 25, 14:20 UTC | May 25, 23:10 UTC | 8h 50m |
| 2026-05-25 | CLO → BOG | May 25, 12:45 UTC | May 25, 13:00 UTC | 15m |
| 2026-05-25 | BOG → CLO | May 25, 10:10 UTC | May 25, 10:25 UTC | 15m |
| 2026-05-25 | - | May 25, 05:25 UTC | May 25, 05:50 UTC | 25m |
| 2026-05-24 | CTG → ADZ | May 24, 15:35 UTC | May 24, 15:45 UTC | 10m |
| 2026-05-24 | CTG → ADZ | May 24, 14:10 UTC | May 24, 14:20 UTC | 10m |
| 2026-05-24 | BOG → CTG | May 24, 10:55 UTC | May 24, 11:10 UTC | 15m |
| 2026-05-24 | EYP → BOG | May 24, 03:05 UTC | May 24, 03:25 UTC | 20m |
| 2026-05-24 | BOG → MTR | May 24, 01:10 UTC | May 24, 01:20 UTC | 10m |
Specifications
| Registration | CC-BFD |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | E80204 · 72001004 (octal) |
Looking for transponder-level data? View the Mode-S E80204 page for country allocation, callsign history, and ADS-B signal details.
CC-BFD frequently asked
What type of aircraft is CC-BFD?
CC-BFD is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for CC-BFD?
CC-BFD broadcasts on Mode-S (ICAO 24-bit) address E80204 (octal 72001004). View the transponder page.
What route does CC-BFD typically fly?
CC-BFD most frequently flies between BOG and MTR based on observed flights.
Where is CC-BFD right now?
CC-BFD is not currently being tracked; last seen 22h ago.