Not currently tracked · last seen 2d ago
- Flights observed
- 519 showing last 50
- Avg flight time
- 1h 31m
- Typical route
- MTY → CUN
- Last seen
- 2d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-11 | - | Jul 11, 22:40 UTC | Jul 12, 01:25 UTC | 2h 45m |
| 2026-07-11 | - | Jul 11, 19:15 UTC | Jul 11, 21:25 UTC | 2h 10m |
| 2026-07-11 | - | Jul 11, 16:50 UTC | Jul 11, 17:25 UTC | 35m |
| 2026-07-11 | - | Jul 11, 15:45 UTC | Jul 11, 15:55 UTC | 10m |
| 2026-07-11 | - | Jul 11, 14:20 UTC | Jul 11, 14:30 UTC | 10m |
| 2026-07-11 | - | Jul 11, 13:00 UTC | Jul 11, 13:30 UTC | 30m |
| 2026-07-11 | VER → MTY | Jul 11, 04:55 UTC | Jul 11, 06:10 UTC | 1h 15m |
| 2026-07-11 | MTY → VER | Jul 11, 02:50 UTC | Jul 11, 04:05 UTC | 1h 15m |
| 2026-07-10 | - | Jul 10, 23:50 UTC | Jul 11, 01:50 UTC | 2h 0m |
| 2026-07-10 | MTY → CUN | Jul 10, 20:55 UTC | Jul 10, 22:45 UTC | 1h 50m |
| 2026-07-10 | CUN → MTY | Jul 10, 15:15 UTC | Jul 10, 17:15 UTC | 2h 0m |
| 2026-07-10 | MTY → CUN | Jul 10, 12:05 UTC | Jul 10, 14:00 UTC | 1h 55m |
| 2026-07-10 | - | Jul 10, 02:00 UTC | Jul 10, 02:15 UTC | 15m |
| 2026-07-10 | - | Jul 10, 00:40 UTC | Jul 10, 01:10 UTC | 30m |
| 2026-07-09 | CUN → MTY | Jul 9, 21:35 UTC | Jul 9, 23:40 UTC | 2h 5m |
| 2026-07-09 | MTY → CUN | Jul 9, 18:20 UTC | Jul 9, 20:20 UTC | 2h 0m |
| 2026-07-09 | - | Jul 9, 16:55 UTC | Jul 9, 17:25 UTC | 30m |
| 2026-07-09 | - | Jul 9, 15:45 UTC | Jul 9, 15:55 UTC | 10m |
| 2026-07-09 | - | Jul 9, 14:10 UTC | Jul 9, 14:25 UTC | 15m |
| 2026-07-09 | - | Jul 9, 12:55 UTC | Jul 9, 13:25 UTC | 30m |
| 2026-07-09 | MTY → MTY | Jul 9, 00:15 UTC | Jul 9, 04:40 UTC | 4h 25m |
| 2026-07-08 | MTY → MTY | Jul 8, 18:50 UTC | Jul 8, 21:55 UTC | 3h 5m |
| 2026-07-08 | - | Jul 8, 15:20 UTC | Jul 8, 16:30 UTC | 1h 10m |
| 2026-07-08 | - | Jul 8, 13:15 UTC | Jul 8, 13:40 UTC | 25m |
| 2026-07-08 | PBC → MTY | Jul 8, 05:00 UTC | Jul 8, 06:10 UTC | 1h 10m |
| 2026-07-08 | MTY → PBC | Jul 8, 02:45 UTC | Jul 8, 04:00 UTC | 1h 15m |
| 2026-07-07 | MTY → MTY | Jul 7, 22:20 UTC | Jul 8, 01:40 UTC | 3h 20m |
| 2026-07-07 | - | Jul 7, 02:35 UTC | Jul 7, 04:55 UTC | 2h 20m |
| 2026-07-06 | - | Jul 6, 23:15 UTC | Jul 7, 01:40 UTC | 2h 25m |
| 2026-07-06 | - | Jul 6, 20:45 UTC | Jul 6, 21:50 UTC | 1h 5m |
| 2026-07-06 | - | Jul 6, 18:45 UTC | Jul 6, 19:40 UTC | 55m |
| 2026-07-06 | - | Jul 6, 16:40 UTC | Jul 6, 17:25 UTC | 45m |
| 2026-07-06 | - | Jul 6, 12:20 UTC | Jul 6, 13:00 UTC | 40m |
| 2026-07-06 | - | Jul 6, 03:40 UTC | Jul 6, 06:00 UTC | 2h 20m |
| 2026-07-05 | - | Jul 5, 23:50 UTC | Jul 6, 02:15 UTC | 2h 25m |
| 2026-07-05 | MTY → MTY | Jul 5, 19:40 UTC | Jul 5, 22:55 UTC | 3h 15m |
| 2026-07-05 | - | Jul 5, 16:30 UTC | Jul 5, 18:45 UTC | 2h 15m |
| 2026-07-05 | MTY → TIJ | Jul 5, 12:40 UTC | Jul 5, 15:00 UTC | 2h 20m |
| 2026-07-05 | MTY → MTY | Jul 5, 00:35 UTC | Jul 5, 04:05 UTC | 3h 30m |
| 2026-07-04 | - | Jul 4, 21:20 UTC | Jul 4, 23:30 UTC | 2h 10m |
| 2026-07-04 | MTY → CUN | Jul 4, 17:55 UTC | Jul 4, 19:50 UTC | 1h 55m |
| 2026-07-04 | - | Jul 4, 14:45 UTC | Jul 4, 16:55 UTC | 2h 10m |
| 2026-07-04 | MTY → CUN | Jul 4, 11:35 UTC | Jul 4, 13:25 UTC | 1h 50m |
| 2026-07-04 | - | Jul 4, 05:05 UTC | Jul 4, 05:30 UTC | 25m |
| 2026-07-04 | - | Jul 4, 03:50 UTC | Jul 4, 04:05 UTC | 15m |
| 2026-07-04 | - | Jul 4, 02:50 UTC | Jul 4, 02:55 UTC | 5m |
| 2026-07-04 | - | Jul 4, 01:20 UTC | Jul 4, 01:45 UTC | 25m |
| 2026-07-03 | CUN → MTY | Jul 3, 22:00 UTC | Jul 4, 00:15 UTC | 2h 15m |
| 2026-07-03 | MTY → CUN | Jul 3, 18:25 UTC | Jul 3, 20:25 UTC | 2h 0m |
| 2026-07-03 | - | Jul 3, 16:45 UTC | Jul 3, 17:25 UTC | 40m |
Specifications
| Registration | CC-DBO |
| Aircraft type | AIRBUS A-320neo (A20N) |
| Mode-S code | E80048 · 72000110 (octal) |
Looking for transponder-level data? View the Mode-S E80048 page for country allocation, callsign history, and ADS-B signal details.
CC-DBO frequently asked
What type of aircraft is CC-DBO?
CC-DBO is a AIRBUS A-320neo (ICAO type code A20N).
What is the Mode-S transponder code for CC-DBO?
CC-DBO broadcasts on Mode-S (ICAO 24-bit) address E80048 (octal 72000110). View the transponder page.
What route does CC-DBO typically fly?
CC-DBO most frequently flies between MTY and CUN based on observed flights.
Where is CC-DBO right now?
CC-DBO is not currently being tracked; last seen 2d ago.