Not currently tracked · last seen Jul 26, 23:00 UTC
- Flights observed
- 315 showing last 50
- Avg flight time
- 2h 49m
- Typical route
- BPS → VCP
- Last seen
- Jul 26, 23:00 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | MAO → CGB | Jul 26, 22:30 UTC | Jul 26, 23:00 UTC | 30m |
| 2026-07-26 | MVD → SSA | Jul 26, 19:10 UTC | Jul 26, 20:35 UTC | 1h 25m |
| 2026-07-26 | BPS → VCP | Jul 26, 16:20 UTC | Jul 26, 17:35 UTC | 1h 15m |
| 2026-07-26 | CNF → POA | Jul 26, 13:20 UTC | Jul 26, 14:45 UTC | 1h 25m |
| 2026-07-26 | CNF → GIG | Jul 26, 09:20 UTC | Jul 26, 10:35 UTC | 1h 15m |
| 2026-07-25 | BEL → VCP | Jul 25, 20:20 UTC | Jul 25, 23:05 UTC | 2h 45m |
| 2026-07-25 | VCP → BEL | Jul 25, 11:50 UTC | Jul 25, 14:55 UTC | 3h 5m |
| 2026-07-25 | FOR → VCP | Jul 25, 06:35 UTC | Jul 25, 09:50 UTC | 3h 15m |
| 2026-07-25 | VCP → FOR | Jul 25, 02:25 UTC | Jul 25, 05:25 UTC | 3h 0m |
| 2026-07-24 | MEA → VCP | Jul 24, 22:00 UTC | Jul 25, 01:05 UTC | 3h 5m |
| 2026-07-24 | VCP → MEA | Jul 24, 18:05 UTC | Jul 24, 21:00 UTC | 2h 55m |
| 2026-07-24 | VCP → SSA | Jul 24, 11:40 UTC | Jul 24, 16:45 UTC | 5h 5m |
| 2026-07-24 | VCP → MAO | Jul 24, 02:05 UTC | Jul 24, 09:55 UTC | 7h 50m |
| 2026-07-23 | BPS → VCP | Jul 23, 23:00 UTC | Jul 24, 00:40 UTC | 1h 40m |
| 2026-07-23 | PPB → BPS | Jul 23, 20:35 UTC | Jul 23, 21:40 UTC | 1h 5m |
| 2026-07-23 | BPS → PPB | Jul 23, 15:25 UTC | Jul 23, 19:45 UTC | 4h 20m |
| 2026-07-23 | VCP → UDI | Jul 23, 12:55 UTC | Jul 23, 13:30 UTC | 35m |
| 2026-07-22 | - | Jul 22, 23:40 UTC | Jul 23, 00:55 UTC | 1h 15m |
| 2026-07-22 | - | Jul 22, 21:15 UTC | Jul 22, 22:25 UTC | 1h 10m |
| 2026-07-22 | GIG → VCP | Jul 22, 14:50 UTC | Jul 22, 15:35 UTC | 45m |
| 2026-07-22 | REC → SDU | Jul 22, 12:30 UTC | Jul 22, 13:40 UTC | 1h 10m |
| 2026-07-20 | VCP → MAO | Jul 20, 16:25 UTC | Jul 21, 09:40 UTC | 17h 14m |
| 2026-07-20 | VCP → PFB | Jul 20, 12:00 UTC | Jul 20, 15:15 UTC | 3h 15m |
| 2026-07-19 | CNF → NAT | Jul 19, 20:10 UTC | Jul 20, 00:20 UTC | 4h 10m |
| 2026-07-19 | BPS → RAO | Jul 19, 17:15 UTC | Jul 19, 18:35 UTC | 1h 20m |
| 2026-07-19 | SJP → BPS | Jul 19, 14:15 UTC | Jul 19, 15:30 UTC | 1h 15m |
| 2026-07-19 | BPS → SJP | Jul 19, 11:45 UTC | Jul 19, 13:10 UTC | 1h 25m |
| 2026-07-19 | VCP → BPS | Jul 19, 09:10 UTC | Jul 19, 10:20 UTC | 1h 10m |
| 2026-07-19 | - | Jul 19, 05:45 UTC | Jul 19, 08:00 UTC | 2h 15m |
| 2026-07-19 | - | Jul 19, 02:15 UTC | Jul 19, 04:05 UTC | 1h 50m |
| 2026-07-18 | - | Jul 18, 23:00 UTC | Jul 18, 23:35 UTC | 35m |
| 2026-07-18 | VCP → NVT | Jul 18, 21:05 UTC | Jul 18, 21:40 UTC | 35m |
| 2026-07-18 | - | Jul 18, 10:35 UTC | Jul 18, 19:40 UTC | 9h 5m |
| 2026-07-17 | MEA → VCP | Jul 17, 20:50 UTC | Jul 18, 00:00 UTC | 3h 10m |
| 2026-07-17 | VCP → MEA | Jul 17, 16:55 UTC | Jul 17, 19:49 UTC | 2h 55m |
| 2026-07-17 | - | Jul 17, 12:10 UTC | Jul 17, 15:15 UTC | 3h 5m |
| 2026-07-16 | - | Jul 16, 20:55 UTC | Jul 17, 01:09 UTC | 4h 15m |
| 2026-07-16 | - | Jul 16, 12:00 UTC | Jul 16, 15:25 UTC | 3h 25m |
| 2026-07-16 | - | Jul 16, 06:45 UTC | Jul 16, 09:25 UTC | 2h 40m |
| 2026-07-16 | - | Jul 16, 03:05 UTC | Jul 16, 05:20 UTC | 2h 15m |
| 2026-07-15 | - | Jul 15, 23:45 UTC | Jul 16, 01:20 UTC | 1h 35m |
| 2026-07-15 | - | Jul 15, 17:20 UTC | Jul 15, 22:15 UTC | 4h 55m |
| 2026-07-15 | - | Jul 15, 14:30 UTC | Jul 15, 15:40 UTC | 1h 10m |
| 2026-07-15 | - | Jul 15, 12:00 UTC | Jul 15, 13:30 UTC | 1h 30m |
| 2026-07-15 | - | Jul 15, 09:15 UTC | Jul 15, 10:25 UTC | 1h 10m |
| 2026-07-14 | - | Jul 14, 20:20 UTC | Jul 15, 00:45 UTC | 4h 24m |
| 2026-07-14 | - | Jul 14, 14:45 UTC | Jul 14, 18:35 UTC | 3h 50m |
| 2026-07-14 | - | Jul 14, 11:55 UTC | Jul 14, 13:05 UTC | 1h 10m |
| 2026-07-14 | - | Jul 14, 09:15 UTC | Jul 14, 10:20 UTC | 1h 5m |
| 2026-07-14 | - | Jul 14, 02:55 UTC | Jul 14, 08:00 UTC | 5h 5m |
Specifications
| Registration | PR-YSO |
| Aircraft type | AIRBUS A-320neo (A20N) |
| Mode-S code | E49AF4 · 71115364 (octal) |
Looking for transponder-level data? View the Mode-S E49AF4 page for country allocation, callsign history, and ADS-B signal details.
PR-YSO frequently asked
What type of aircraft is PR-YSO?
PR-YSO is a AIRBUS A-320neo (ICAO type code A20N).
What is the Mode-S transponder code for PR-YSO?
PR-YSO broadcasts on Mode-S (ICAO 24-bit) address E49AF4 (octal 71115364). View the transponder page.
What route does PR-YSO typically fly?
PR-YSO most frequently flies between BPS and VCP based on observed flights.
Where is PR-YSO right now?
PR-YSO is not currently being tracked; last seen Jul 26, 23:00 UTC.