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