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