Not currently tracked · last seen 9h ago
- Flights observed
- 63 showing last 50
- Avg flight time
- 4h 28m
- Typical route
- VVI → GRU
- Last seen
- 9h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | GRU → VVI | May 29, 17:10 UTC | May 29, 18:55 UTC | 1h 45m |
| 2026-05-29 | VVI → GRU | May 29, 14:30 UTC | May 29, 15:55 UTC | 1h 26m |
| 2026-05-25 | EZE → VVI | May 25, 18:15 UTC | May 25, 19:00 UTC | 45m |
| 2026-05-25 | VVI → EZE | May 25, 16:00 UTC | May 25, 16:20 UTC | 20m |
| 2026-05-24 | VVI → EZE | May 24, 23:00 UTC | May 25, 13:40 UTC | 14h 40m |
| 2026-05-24 | VVI → GRU | May 24, 19:10 UTC | May 24, 20:40 UTC | 1h 30m |
| 2026-05-19 | ASU → VVI | May 19, 23:55 UTC | May 20, 00:30 UTC | 35m |
| 2026-05-19 | GRU → VVI | May 19, 17:00 UTC | May 19, 22:35 UTC | 5h 35m |
| 2026-05-19 | VVI → GRU | May 19, 14:35 UTC | May 19, 15:45 UTC | 1h 10m |
| 2026-05-17 | GRU → VVI | May 17, 17:01 UTC | May 17, 18:45 UTC | 1h 45m |
| 2026-05-17 | VVI → GRU | May 17, 14:10 UTC | May 17, 15:40 UTC | 1h 30m |
| 2026-05-16 | VVI → GRU | May 16, 18:00 UTC | May 17, 15:40 UTC | 21h 40m |
| 2026-05-16 | EZE → VVI | May 16, 05:35 UTC | May 16, 16:45 UTC | 11h 11m |
| 2026-05-15 | GRU → VVI | May 15, 21:50 UTC | May 16, 04:20 UTC | 6h 30m |
| 2026-05-15 | VVI → GRU | May 15, 18:30 UTC | May 15, 20:00 UTC | 1h 30m |
| 2026-05-11 | GRU → VVI | May 11, 17:30 UTC | May 11, 19:00 UTC | 1h 30m |
| 2026-05-11 | VVI → GRU | May 11, 14:40 UTC | May 11, 16:00 UTC | 1h 20m |
| 2026-05-08 | EZE → VVI | May 8, 18:35 UTC | May 8, 19:05 UTC | 30m |
| 2026-05-08 | CBB → EZE | May 8, 16:55 UTC | May 8, 17:30 UTC | 35m |
| 2026-05-07 | EZE → VVI | May 7, 17:40 UTC | May 8, 17:00 UTC | 23h 20m |
| 2026-05-07 | CBB → EZE | May 7, 15:45 UTC | May 7, 16:15 UTC | 30m |
| 2026-05-06 | EZE → VVI | May 6, 18:00 UTC | May 6, 18:35 UTC | 35m |
| 2026-05-06 | CBB → EZE | May 6, 16:20 UTC | May 6, 16:50 UTC | 30m |
| 2026-05-05 | EZE → VVI | May 5, 17:45 UTC | May 5, 18:20 UTC | 35m |
| 2026-05-05 | CBB → EZE | May 5, 11:20 UTC | May 5, 16:10 UTC | 4h 50m |
| 2026-05-03 | EZE → VVI | May 3, 17:50 UTC | May 3, 18:20 UTC | 30m |
| 2026-05-03 | CBB → EZE | May 3, 15:35 UTC | May 3, 16:05 UTC | 30m |
| 2026-05-03 | VVI → LPB | May 3, 04:50 UTC | May 3, 05:00 UTC | 10m |
| 2026-05-02 | LPB → VVI | May 2, 20:55 UTC | May 2, 23:25 UTC | 2h 30m |
| 2026-05-01 | VVI → GRU | May 1, 17:00 UTC | May 1, 18:45 UTC | 1h 45m |
| 2026-05-01 | GIG → VVI | May 1, 07:55 UTC | May 1, 15:25 UTC | 7h 30m |
| 2026-05-01 | - | May 1, 03:30 UTC | May 1, 06:45 UTC | 3h 15m |
| 2026-04-30 | EZE → VVI | Apr 30, 06:45 UTC | Apr 30, 11:30 UTC | 4h 45m |
| 2026-04-30 | VVI → EZE | Apr 30, 00:40 UTC | Apr 30, 05:30 UTC | 4h 50m |
| 2026-04-28 | GRU → VVI | Apr 28, 17:20 UTC | Apr 28, 19:00 UTC | 1h 40m |
| 2026-04-28 | VVI → GRU | Apr 28, 10:15 UTC | Apr 28, 16:05 UTC | 5h 50m |
| 2026-04-27 | VVI → LPB | Apr 27, 23:45 UTC | Apr 27, 23:55 UTC | 10m |
| 2026-04-26 | GRU → VVI | Apr 26, 17:40 UTC | Apr 26, 19:25 UTC | 1h 45m |
| 2026-04-26 | VVI → GRU | Apr 26, 14:50 UTC | Apr 26, 16:15 UTC | 1h 25m |
| 2026-04-25 | GRU → VVI | Apr 25, 19:05 UTC | Apr 26, 16:15 UTC | 21h 10m |
| 2026-04-25 | GRU → VVI | Apr 25, 18:50 UTC | Apr 26, 16:15 UTC | 21h 25m |
| 2026-04-25 | VVI → GIG | Apr 25, 16:00 UTC | Apr 25, 17:50 UTC | 1h 50m |
| 2026-04-25 | EZE → VVI | Apr 25, 05:25 UTC | Apr 25, 06:10 UTC | 45m |
| 2026-04-24 | GRU → VVI | Apr 24, 21:45 UTC | Apr 25, 04:10 UTC | 6h 25m |
| 2026-04-24 | VVI → GRU | Apr 24, 15:10 UTC | Apr 24, 20:05 UTC | 4h 55m |
| 2026-04-21 | VVI → LPB | Apr 21, 22:05 UTC | Apr 21, 22:15 UTC | 10m |
| 2026-04-21 | - | Apr 21, 17:15 UTC | Apr 21, 18:55 UTC | 1h 40m |
| 2026-04-21 | - | Apr 21, 14:25 UTC | Apr 21, 16:05 UTC | 1h 40m |
| 2026-04-19 | - | Apr 19, 17:35 UTC | Apr 19, 18:50 UTC | 1h 15m |
| 2026-04-18 | - | Apr 18, 21:05 UTC | Apr 19, 16:15 UTC | 19h 10m |
Specifications
| Registration | CP-3196 |
| Aircraft type | BOEING 737-800 (B738) |
| Mode-S code | E94C7C · 72246174 (octal) |
Looking for transponder-level data? View the Mode-S E94C7C page for country allocation, callsign history, and ADS-B signal details.
CP-3196 frequently asked
What type of aircraft is CP-3196?
CP-3196 is a BOEING 737-800 (ICAO type code B738).
What is the Mode-S transponder code for CP-3196?
CP-3196 broadcasts on Mode-S (ICAO 24-bit) address E94C7C (octal 72246174). View the transponder page.
What route does CP-3196 typically fly?
CP-3196 most frequently flies between VVI and GRU based on observed flights.
Where is CP-3196 right now?
CP-3196 is not currently being tracked; last seen 9h ago.