Not currently tracked · last seen Jul 26, 21:30 UTC
- Flights observed
- 230 showing last 50
- Avg flight time
- 17h 19m
- Typical route
- VVI → MAD
- Last seen
- Jul 26, 21:30 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | MAD → VVI | Jul 26, 13:20 UTC | Jul 26, 21:30 UTC | 8h 10m |
| 2026-07-25 | VVI → MAD | Jul 25, 16:20 UTC | Jul 26, 10:40 UTC | 18h 21m |
| 2026-07-25 | VVI → MAD | Jul 25, 14:35 UTC | Jul 26, 10:40 UTC | 20h 6m |
| 2026-07-24 | MAD → VVI | Jul 24, 15:35 UTC | Jul 25, 09:55 UTC | 18h 20m |
| 2026-07-24 | MAD → VVI | Jul 24, 13:35 UTC | Jul 25, 09:55 UTC | 20h 20m |
| 2026-07-24 | VVI → MAD | Jul 24, 01:00 UTC | Jul 24, 10:45 UTC | 9h 45m |
| 2026-07-23 | VVI → MAD | Jul 23, 09:35 UTC | Jul 24, 09:30 UTC | 23h 55m |
| 2026-07-23 | VVI → MAD | Jul 23, 07:35 UTC | Jul 24, 03:10 UTC | 19h 35m |
| 2026-07-23 | VVI → MAD | Jul 23, 07:15 UTC | Jul 24, 03:10 UTC | 19h 55m |
| 2026-07-23 | MIA → VVI | Jul 23, 05:30 UTC | Jul 23, 05:55 UTC | 25m |
| 2026-07-22 | VVI → MIA | Jul 22, 11:35 UTC | Jul 23, 03:05 UTC | 15h 30m |
| 2026-07-22 | MAD → CBB | Jul 22, 03:55 UTC | Jul 23, 03:05 UTC | 23h 10m |
| 2026-07-20 | VVI → MAD | Jul 20, 16:20 UTC | Jul 21, 10:20 UTC | 17h 59m |
| 2026-07-20 | VVI → MAD | Jul 20, 14:35 UTC | Jul 21, 10:20 UTC | 19h 45m |
| 2026-07-19 | - | Jul 19, 15:35 UTC | Jul 20, 10:10 UTC | 18h 35m |
| 2026-07-19 | - | Jul 19, 13:35 UTC | Jul 20, 10:10 UTC | 20h 35m |
| 2026-07-19 | - | Jul 19, 13:15 UTC | Jul 20, 10:10 UTC | 20h 55m |
| 2026-07-18 | VVI → MAD | Jul 18, 16:05 UTC | Jul 19, 10:05 UTC | 18h 0m |
| 2026-07-18 | VVI → MAD | Jul 18, 14:20 UTC | Jul 19, 10:05 UTC | 19h 45m |
| 2026-07-17 | - | Jul 17, 15:35 UTC | Jul 18, 10:00 UTC | 18h 26m |
| 2026-07-17 | - | Jul 17, 13:35 UTC | Jul 18, 10:00 UTC | 20h 26m |
| 2026-07-17 | - | Jul 17, 13:15 UTC | Jul 18, 10:00 UTC | 20h 46m |
| 2026-07-17 | - | Jul 17, 00:20 UTC | Jul 17, 10:00 UTC | 9h 40m |
| 2026-07-16 | - | Jul 16, 05:35 UTC | Jul 17, 02:30 UTC | 20h 55m |
| 2026-07-16 | - | Jul 16, 05:00 UTC | Jul 17, 02:30 UTC | 21h 30m |
| 2026-07-16 | - | Jul 16, 01:35 UTC | Jul 17, 01:09 UTC | 23h 35m |
| 2026-07-16 | - | Jul 16, 01:25 UTC | Jul 16, 05:45 UTC | 4h 20m |
| 2026-07-15 | VVI → MIA | Jul 15, 15:35 UTC | Jul 15, 20:20 UTC | 4h 45m |
| 2026-07-14 | VVI → MIA | Jul 14, 23:35 UTC | Jul 15, 20:20 UTC | 20h 45m |
| 2026-07-14 | MAD → CBB | Jul 14, 21:35 UTC | Jul 15, 20:20 UTC | 22h 44m |
| 2026-07-14 | MAD → CBB | Jul 14, 21:15 UTC | Jul 15, 17:25 UTC | 20h 9m |
| 2026-07-14 | MAD → CBB | Jul 14, 13:20 UTC | Jul 14, 23:45 UTC | 10h 24m |
| 2026-07-13 | - | Jul 13, 17:10 UTC | Jul 14, 10:15 UTC | 17h 5m |
| 2026-07-13 | - | Jul 13, 14:30 UTC | Jul 14, 10:15 UTC | 19h 45m |
| 2026-07-12 | - | Jul 12, 15:35 UTC | Jul 13, 09:45 UTC | 18h 10m |
| 2026-07-12 | - | Jul 12, 13:35 UTC | Jul 13, 09:45 UTC | 20h 10m |
| 2026-07-12 | - | Jul 12, 13:05 UTC | Jul 13, 09:30 UTC | 20h 25m |
| 2026-07-11 | - | Jul 11, 18:20 UTC | Jul 12, 10:10 UTC | 15h 50m |
| 2026-07-11 | MIA → MAD | Jul 11, 14:50 UTC | Jul 12, 10:10 UTC | 19h 20m |
| 2026-07-10 | - | Jul 10, 15:35 UTC | Jul 11, 10:35 UTC | 19h 0m |
| 2026-07-10 | - | Jul 10, 13:35 UTC | Jul 11, 10:35 UTC | 21h 1m |
| 2026-07-10 | - | Jul 10, 00:30 UTC | Jul 10, 10:05 UTC | 9h 35m |
| 2026-07-09 | - | Jul 9, 05:35 UTC | Jul 10, 02:40 UTC | 21h 5m |
| 2026-07-09 | - | Jul 9, 05:00 UTC | Jul 10, 02:40 UTC | 21h 40m |
| 2026-07-09 | MIA → VVI | Jul 9, 01:35 UTC | Jul 10, 01:20 UTC | 23h 45m |
| 2026-07-09 | MIA → VVI | Jul 9, 01:15 UTC | Jul 9, 05:50 UTC | 4h 35m |
| 2026-07-08 | VVI → MIA | Jul 8, 19:50 UTC | Jul 8, 20:10 UTC | 20m |
| 2026-07-07 | MAD → CBB | Jul 7, 21:35 UTC | Jul 8, 16:25 UTC | 18h 50m |
| 2026-07-07 | MAD → CBB | Jul 7, 20:50 UTC | Jul 8, 16:25 UTC | 19h 35m |
| 2026-07-07 | MAD → CBB | Jul 7, 15:35 UTC | Jul 8, 15:30 UTC | 23h 55m |
Specifications
| Registration | CP-3214 |
| Aircraft type | AIRBUS A-330-200 (A332) |
| Mode-S code | E94C8E · 72246216 (octal) |
Looking for transponder-level data? View the Mode-S E94C8E page for country allocation, callsign history, and ADS-B signal details.
CP-3214 frequently asked
What type of aircraft is CP-3214?
CP-3214 is a AIRBUS A-330-200 (ICAO type code A332).
What is the Mode-S transponder code for CP-3214?
CP-3214 broadcasts on Mode-S (ICAO 24-bit) address E94C8E (octal 72246216). View the transponder page.
What route does CP-3214 typically fly?
CP-3214 most frequently flies between VVI and MAD based on observed flights.
Where is CP-3214 right now?
CP-3214 is not currently being tracked; last seen Jul 26, 21:30 UTC.