Not currently tracked · last seen Jul 26, 22:00 UTC
- Flights observed
- 451 showing last 50
- Avg flight time
- 3h 1m
- Typical route
- GRU → OPS
- Last seen
- Jul 26, 22:00 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | OPS → BSB | Jul 26, 21:30 UTC | Jul 26, 22:00 UTC | 30m |
| 2026-07-26 | GRU → OPS | Jul 26, 18:35 UTC | Jul 26, 20:35 UTC | 2h 0m |
| 2026-07-26 | CLV → GRU | Jul 26, 14:00 UTC | Jul 26, 17:15 UTC | 3h 15m |
| 2026-07-26 | FOR → GRU | Jul 26, 07:45 UTC | Jul 26, 10:50 UTC | 3h 5m |
| 2026-07-25 | GRU → FOR | Jul 25, 22:10 UTC | Jul 26, 01:10 UTC | 3h 0m |
| 2026-07-25 | SJP → GRU | Jul 25, 19:25 UTC | Jul 25, 20:15 UTC | 50m |
| 2026-07-25 | GRU → SJP | Jul 25, 17:40 UTC | Jul 25, 18:15 UTC | 35m |
| 2026-07-25 | FLN → GRU | Jul 25, 14:55 UTC | Jul 25, 16:05 UTC | 1h 10m |
| 2026-07-25 | GRU → FLN | Jul 25, 13:05 UTC | Jul 25, 14:00 UTC | 55m |
| 2026-07-25 | MGF → GRU | Jul 25, 10:55 UTC | Jul 25, 11:40 UTC | 45m |
| 2026-07-25 | BPS → GIG | Jul 25, 08:20 UTC | Jul 25, 09:20 UTC | 1h 0m |
| 2026-07-25 | GIG → BPS | Jul 25, 02:35 UTC | Jul 25, 03:30 UTC | 55m |
| 2026-07-24 | BSB → GIG | Jul 24, 21:10 UTC | Jul 25, 01:10 UTC | 4h 0m |
| 2026-07-24 | GRU → OPS | Jul 24, 18:05 UTC | Jul 24, 20:15 UTC | 2h 10m |
| 2026-07-24 | MOC → GRU | Jul 24, 12:25 UTC | Jul 24, 15:50 UTC | 3h 25m |
| 2026-07-23 | CNF → GRU | Jul 23, 23:50 UTC | Jul 24, 09:40 UTC | 9h 50m |
| 2026-07-23 | CNF → CGH | Jul 23, 21:45 UTC | Jul 23, 22:30 UTC | 45m |
| 2026-07-23 | CGH → CNF | Jul 23, 19:30 UTC | Jul 23, 20:05 UTC | 35m |
| 2026-07-23 | AJU → SDU | Jul 23, 17:50 UTC | Jul 23, 18:25 UTC | 35m |
| 2026-07-23 | CGH → CWB | Jul 23, 15:40 UTC | Jul 23, 16:20 UTC | 40m |
| 2026-07-23 | GIG → SSA | Jul 23, 01:45 UTC | Jul 23, 14:15 UTC | 12h 30m |
| 2026-07-23 | GRU → GIG | Jul 23, 00:05 UTC | Jul 23, 00:25 UTC | 20m |
| 2026-07-22 | CNF → GRU | Jul 22, 17:15 UTC | Jul 22, 20:05 UTC | 2h 50m |
| 2026-07-22 | PNZ → GRU | Jul 22, 14:15 UTC | Jul 22, 15:55 UTC | 1h 40m |
| 2026-07-22 | GRU → PNZ | Jul 22, 02:45 UTC | Jul 22, 12:30 UTC | 9h 45m |
| 2026-07-21 | CAC → GRU | Jul 21, 20:55 UTC | Jul 22, 00:10 UTC | 3h 15m |
| 2026-07-21 | CGR → GRU | Jul 21, 18:35 UTC | Jul 21, 19:15 UTC | 40m |
| 2026-07-21 | GRU → CGR | Jul 21, 15:30 UTC | Jul 21, 16:45 UTC | 1h 15m |
| 2026-07-21 | CWB → GRU | Jul 21, 10:15 UTC | Jul 21, 13:55 UTC | 3h 40m |
| 2026-07-21 | GRU → NAT | Jul 21, 01:35 UTC | Jul 21, 08:50 UTC | 7h 15m |
| 2026-07-20 | PFB → GRU | Jul 20, 19:45 UTC | Jul 20, 23:25 UTC | 3h 40m |
| 2026-07-20 | - | Jul 20, 15:10 UTC | Jul 20, 18:25 UTC | 3h 15m |
| 2026-07-20 | GRU → FOR | Jul 20, 11:15 UTC | Jul 20, 14:05 UTC | 2h 50m |
| 2026-07-20 | IMP → GRU | Jul 20, 06:50 UTC | Jul 20, 09:40 UTC | 2h 50m |
| 2026-07-20 | GRU → IMP | Jul 20, 03:10 UTC | Jul 20, 05:35 UTC | 2h 25m |
| 2026-07-19 | VDC → GRU | Jul 19, 20:05 UTC | Jul 20, 00:05 UTC | 4h 0m |
| 2026-07-19 | - | Jul 19, 15:05 UTC | Jul 19, 16:15 UTC | 1h 10m |
| 2026-07-19 | GRU → VIX | Jul 19, 13:10 UTC | Jul 19, 14:10 UTC | 1h 0m |
| 2026-07-18 | - | Jul 18, 20:40 UTC | Jul 19, 09:10 UTC | 12h 30m |
| 2026-07-18 | - | Jul 18, 10:00 UTC | Jul 18, 18:30 UTC | 8h 30m |
| 2026-07-18 | - | Jul 18, 06:35 UTC | Jul 18, 08:25 UTC | 1h 50m |
| 2026-07-17 | GRU → CGB | Jul 17, 23:50 UTC | Jul 18, 00:35 UTC | 45m |
| 2026-07-17 | - | Jul 17, 20:29 UTC | Jul 17, 21:15 UTC | 45m |
| 2026-07-17 | GRU → UBA | Jul 17, 18:40 UTC | Jul 17, 19:20 UTC | 40m |
| 2026-07-17 | - | Jul 17, 13:15 UTC | Jul 17, 16:40 UTC | 3h 25m |
| 2026-07-17 | - | Jul 17, 03:39 UTC | Jul 17, 10:50 UTC | 7h 10m |
| 2026-07-16 | - | Jul 16, 18:34 UTC | Jul 17, 00:55 UTC | 6h 20m |
| 2026-07-16 | CGH → CGH | Jul 16, 13:34 UTC | Jul 16, 17:05 UTC | 3h 30m |
| 2026-07-16 | - | Jul 16, 11:34 UTC | Jul 16, 12:05 UTC | 30m |
| 2026-07-16 | - | Jul 16, 09:45 UTC | Jul 16, 10:20 UTC | 35m |
Specifications
| Registration | PR-MYO |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | E48AD4 · 71105324 (octal) |
Looking for transponder-level data? View the Mode-S E48AD4 page for country allocation, callsign history, and ADS-B signal details.
PR-MYO frequently asked
What type of aircraft is PR-MYO?
PR-MYO is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for PR-MYO?
PR-MYO broadcasts on Mode-S (ICAO 24-bit) address E48AD4 (octal 71105324). View the transponder page.
What route does PR-MYO typically fly?
PR-MYO most frequently flies between GRU and OPS based on observed flights.
Where is PR-MYO right now?
PR-MYO is not currently being tracked; last seen Jul 26, 22:00 UTC.