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