Not currently tracked · last seen 1h ago
- Flights observed
- 94 showing last 50
- Avg flight time
- 2h 21m
- Typical route
- ATH → OTP
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-06 | OTP → MAD | Jun 6, 05:35 UTC | Jun 6, 09:09 UTC | 3h 35m |
| 2026-06-05 | MAD → OTP | Jun 5, 10:50 UTC | Jun 5, 13:55 UTC | 3h 5m |
| 2026-06-05 | OTP → MAD | Jun 5, 05:40 UTC | Jun 5, 09:25 UTC | 3h 45m |
| 2026-06-04 | AMS → OTP | Jun 4, 10:15 UTC | Jun 4, 12:30 UTC | 2h 15m |
| 2026-06-04 | OTP → AMS | Jun 4, 06:10 UTC | Jun 4, 08:45 UTC | 2h 35m |
| 2026-06-03 | CLJ → OTP | Jun 3, 17:20 UTC | Jun 3, 17:50 UTC | 30m |
| 2026-06-03 | OTP → CLJ | Jun 3, 15:35 UTC | Jun 3, 16:00 UTC | 25m |
| 2026-06-03 | MAD → OTP | Jun 3, 11:00 UTC | Jun 3, 14:10 UTC | 3h 10m |
| 2026-06-03 | OTP → MAD | Jun 3, 05:30 UTC | Jun 3, 09:05 UTC | 3h 35m |
| 2026-06-02 | CLJ → OTP | Jun 2, 17:35 UTC | Jun 2, 18:05 UTC | 30m |
| 2026-06-02 | OTP → CLJ | Jun 2, 15:50 UTC | Jun 2, 16:20 UTC | 30m |
| 2026-06-02 | MAD → OTP | Jun 2, 10:55 UTC | Jun 2, 14:25 UTC | 3h 30m |
| 2026-06-02 | OTP → MAD | Jun 2, 05:35 UTC | Jun 2, 09:10 UTC | 3h 35m |
| 2026-06-01 | FRA → OTP | Jun 1, 09:50 UTC | Jun 1, 11:40 UTC | 1h 50m |
| 2026-06-01 | OTP → FRA | Jun 1, 06:00 UTC | Jun 1, 08:20 UTC | 2h 20m |
| 2026-05-31 | ATH → OTP | May 31, 18:05 UTC | May 31, 19:20 UTC | 1h 15m |
| 2026-05-31 | OTP → ATH | May 31, 15:45 UTC | May 31, 16:55 UTC | 1h 10m |
| 2026-05-30 | - | May 30, 23:15 UTC | May 31, 01:11 UTC | 1h 56m |
| 2026-05-30 | - | May 30, 20:10 UTC | May 30, 20:40 UTC | 30m |
| 2026-05-30 | - | May 30, 09:05 UTC | May 30, 09:30 UTC | 25m |
| 2026-05-30 | - | May 30, 05:30 UTC | May 30, 07:35 UTC | 2h 5m |
| 2026-05-30 | - | May 30, 01:00 UTC | May 30, 04:05 UTC | 3h 5m |
| 2026-05-29 | MAD → OTP | May 29, 11:15 UTC | May 29, 14:30 UTC | 3h 15m |
| 2026-05-29 | OTP → MAD | May 29, 06:10 UTC | May 29, 09:25 UTC | 3h 15m |
| 2026-05-28 | ATH → OTP | May 28, 16:35 UTC | May 28, 17:55 UTC | 1h 20m |
| 2026-05-28 | OTP → ATH | May 28, 14:05 UTC | May 28, 15:15 UTC | 1h 10m |
| 2026-05-27 | ATH → OTP | May 27, 17:55 UTC | May 27, 19:10 UTC | 1h 15m |
| 2026-05-27 | OTP → ATH | May 27, 15:10 UTC | May 27, 16:25 UTC | 1h 15m |
| 2026-05-27 | PRG → OTP | May 27, 11:55 UTC | May 27, 13:25 UTC | 1h 30m |
| 2026-05-27 | - | May 27, 08:20 UTC | May 27, 10:35 UTC | 2h 15m |
| 2026-05-27 | - | May 27, 04:30 UTC | May 27, 06:40 UTC | 2h 10m |
| 2026-05-25 | PRG → PRG | May 25, 07:05 UTC | May 25, 16:55 UTC | 9h 50m |
| 2026-05-25 | - | May 25, 04:20 UTC | May 25, 05:50 UTC | 1h 30m |
| 2026-05-24 | ATH → OTP | May 24, 18:15 UTC | May 24, 19:30 UTC | 1h 15m |
| 2026-05-24 | OTP → ATH | May 24, 15:35 UTC | May 24, 16:55 UTC | 1h 20m |
| 2026-05-24 | - | May 24, 12:15 UTC | May 24, 13:50 UTC | 1h 35m |
| 2026-05-24 | - | May 24, 08:00 UTC | May 24, 10:00 UTC | 2h 0m |
| 2026-05-24 | - | May 24, 04:10 UTC | May 24, 06:05 UTC | 1h 55m |
| 2026-05-23 | PRG → PRG | May 23, 05:15 UTC | May 23, 15:05 UTC | 9h 50m |
| 2026-05-22 | PRG → PRG | May 22, 05:45 UTC | May 22, 15:20 UTC | 9h 35m |
| 2026-05-22 | - | May 22, 02:50 UTC | May 22, 04:25 UTC | 1h 35m |
| 2026-05-21 | ATH → OTP | May 21, 16:10 UTC | May 21, 17:25 UTC | 1h 15m |
| 2026-05-21 | OTP → ATH | May 21, 13:40 UTC | May 21, 14:55 UTC | 1h 15m |
| 2026-05-20 | ATH → OTP | May 20, 18:15 UTC | May 20, 19:30 UTC | 1h 15m |
| 2026-05-20 | OTP → ATH | May 20, 15:30 UTC | May 20, 16:50 UTC | 1h 20m |
| 2026-05-20 | - | May 20, 12:10 UTC | May 20, 13:40 UTC | 1h 30m |
| 2026-05-20 | - | May 20, 08:05 UTC | May 20, 10:25 UTC | 2h 20m |
| 2026-05-20 | - | May 20, 04:20 UTC | May 20, 06:35 UTC | 2h 16m |
| 2026-05-19 | - | May 19, 10:25 UTC | May 19, 11:55 UTC | 1h 30m |
| 2026-05-17 | ATH → OTP | May 17, 18:10 UTC | May 17, 19:30 UTC | 1h 20m |
Specifications
| Registration | YR-HAA |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 4A2021 · 22420041 (octal) |
Looking for transponder-level data? View the Mode-S 4A2021 page for country allocation, callsign history, and ADS-B signal details.
YR-HAA frequently asked
What type of aircraft is YR-HAA?
YR-HAA is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for YR-HAA?
YR-HAA broadcasts on Mode-S (ICAO 24-bit) address 4A2021 (octal 22420041). View the transponder page.
What route does YR-HAA typically fly?
YR-HAA most frequently flies between ATH and OTP based on observed flights.
Where is YR-HAA right now?
YR-HAA is not currently being tracked; last seen 1h ago.