Not currently tracked · last seen Jul 26, 22:30 UTC
- Flights observed
- 373 showing last 50
- Avg flight time
- 4h 33m
- Typical route
- BSB → MCP
- Last seen
- Jul 26, 22:30 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | JJD → GRU | Jul 26, 21:30 UTC | Jul 26, 22:30 UTC | 1h 0m |
| 2026-07-26 | GRU → JJD | Jul 26, 17:35 UTC | Jul 26, 20:25 UTC | 2h 50m |
| 2026-07-26 | UDI → GRU | Jul 26, 13:35 UTC | Jul 26, 14:25 UTC | 50m |
| 2026-07-26 | GRU → UDI | Jul 26, 11:20 UTC | Jul 26, 12:00 UTC | 40m |
| 2026-07-25 | GYN → GRU | Jul 25, 18:15 UTC | Jul 26, 09:20 UTC | 15h 6m |
| 2026-07-25 | BSB → MCP | Jul 25, 04:05 UTC | Jul 25, 16:45 UTC | 12h 40m |
| 2026-07-24 | BSB → MCP | Jul 24, 20:35 UTC | Jul 25, 16:45 UTC | 20h 10m |
| 2026-07-24 | BSB → MCP | Jul 24, 20:10 UTC | Jul 25, 16:45 UTC | 20h 35m |
| 2026-07-24 | BSB → VCP | Jul 24, 02:45 UTC | Jul 24, 18:50 UTC | 16h 5m |
| 2026-07-24 | GIG → SLZ | Jul 24, 01:45 UTC | Jul 24, 01:55 UTC | 10m |
| 2026-07-23 | CGH → CXJ | Jul 23, 20:10 UTC | Jul 24, 00:40 UTC | 4h 30m |
| 2026-07-23 | GIG → POA | Jul 23, 14:05 UTC | Jul 23, 18:55 UTC | 4h 50m |
| 2026-07-22 | CGH → VIX | Jul 22, 20:20 UTC | Jul 23, 12:55 UTC | 16h 35m |
| 2026-07-22 | NVT → CGH | Jul 22, 16:10 UTC | Jul 22, 18:55 UTC | 2h 45m |
| 2026-07-22 | CGH → CGH | Jul 22, 11:25 UTC | Jul 22, 15:00 UTC | 3h 35m |
| 2026-07-21 | BSB → FOR | Jul 21, 23:40 UTC | Jul 22, 04:50 UTC | 5h 10m |
| 2026-07-21 | BSB → FLN | Jul 21, 18:35 UTC | Jul 21, 22:45 UTC | 4h 10m |
| 2026-07-21 | SSA → CGH | Jul 21, 11:15 UTC | Jul 21, 16:30 UTC | 5h 15m |
| 2026-07-20 | NVT → CGH | Jul 20, 23:00 UTC | Jul 20, 23:45 UTC | 45m |
| 2026-07-20 | GRU → JOI | Jul 20, 21:00 UTC | Jul 20, 21:25 UTC | 25m |
| 2026-07-20 | - | Jul 20, 15:55 UTC | Jul 20, 19:10 UTC | 3h 15m |
| 2026-07-20 | GIG → NAT | Jul 20, 13:10 UTC | Jul 20, 14:25 UTC | 1h 15m |
| 2026-07-20 | - | Jul 20, 10:40 UTC | Jul 20, 12:05 UTC | 1h 25m |
| 2026-07-20 | MCZ → GRU | Jul 20, 03:15 UTC | Jul 20, 09:30 UTC | 6h 15m |
| 2026-07-19 | - | Jul 19, 16:15 UTC | Jul 19, 23:55 UTC | 7h 40m |
| 2026-07-19 | - | Jul 19, 10:30 UTC | Jul 19, 15:05 UTC | 4h 35m |
| 2026-07-19 | NAT → BSB | Jul 19, 08:00 UTC | Jul 19, 08:50 UTC | 50m |
| 2026-07-19 | GRU → NAT | Jul 19, 01:40 UTC | Jul 19, 02:15 UTC | 35m |
| 2026-07-18 | - | Jul 18, 22:50 UTC | Jul 18, 23:40 UTC | 50m |
| 2026-07-18 | GRU → UDI | Jul 18, 20:40 UTC | Jul 18, 21:20 UTC | 40m |
| 2026-07-18 | GIG → GRU | Jul 18, 18:30 UTC | Jul 18, 19:15 UTC | 45m |
| 2026-07-18 | - | Jul 18, 16:45 UTC | Jul 18, 17:25 UTC | 40m |
| 2026-07-18 | - | Jul 18, 14:50 UTC | Jul 18, 15:35 UTC | 45m |
| 2026-07-18 | - | Jul 18, 12:00 UTC | Jul 18, 13:15 UTC | 1h 15m |
| 2026-07-17 | - | Jul 17, 20:55 UTC | Jul 18, 09:30 UTC | 12h 36m |
| 2026-07-17 | - | Jul 17, 17:40 UTC | Jul 17, 19:49 UTC | 2h 10m |
| 2026-07-17 | - | Jul 17, 14:04 UTC | Jul 17, 16:19 UTC | 2h 15m |
| 2026-07-17 | - | Jul 17, 07:44 UTC | Jul 17, 13:05 UTC | 5h 20m |
| 2026-07-16 | - | Jul 16, 19:20 UTC | Jul 17, 02:34 UTC | 7h 15m |
| 2026-07-16 | - | Jul 16, 11:10 UTC | Jul 16, 17:35 UTC | 6h 25m |
| 2026-07-16 | - | Jul 16, 08:25 UTC | Jul 16, 09:05 UTC | 40m |
| 2026-07-15 | - | Jul 15, 22:55 UTC | Jul 16, 00:05 UTC | 1h 10m |
| 2026-07-15 | - | Jul 15, 20:40 UTC | Jul 15, 21:45 UTC | 1h 5m |
| 2026-07-15 | - | Jul 15, 18:40 UTC | Jul 15, 19:10 UTC | 30m |
| 2026-07-15 | - | Jul 15, 11:00 UTC | Jul 15, 14:25 UTC | 3h 25m |
| 2026-07-15 | - | Jul 15, 02:20 UTC | Jul 15, 09:25 UTC | 7h 5m |
| 2026-07-14 | - | Jul 14, 20:45 UTC | Jul 15, 00:25 UTC | 3h 39m |
| 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 |
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 BSB and MCP based on observed flights.
Where is PR-MYI right now?
PR-MYI is not currently being tracked; last seen Jul 26, 22:30 UTC.