Not currently tracked · last seen 22h ago
- Flights observed
- 51 showing last 50
- Avg flight time
- 8h 49m
- Typical route
- MRS → RUN
- Last seen
- 22h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | MRS → RUN | Jul 13, 19:55 UTC | Jul 13, 22:55 UTC | 3h 0m |
| 2026-07-13 | MRS → RUN | Jul 13, 17:15 UTC | Jul 13, 17:50 UTC | 35m |
| 2026-07-13 | - | Jul 13, 07:05 UTC | Jul 13, 07:40 UTC | 35m |
| 2026-07-11 | - | Jul 11, 20:00 UTC | Jul 11, 23:55 UTC | 3h 55m |
| 2026-07-11 | - | Jul 11, 12:20 UTC | Jul 11, 16:25 UTC | 4h 5m |
| 2026-07-10 | - | Jul 10, 18:20 UTC | Jul 11, 16:25 UTC | 22h 6m |
| 2026-07-10 | - | Jul 10, 16:20 UTC | Jul 11, 16:15 UTC | 23h 55m |
| 2026-07-10 | - | Jul 10, 15:55 UTC | Jul 11, 14:15 UTC | 22h 20m |
| 2026-07-09 | ORY → ORY | Jul 9, 11:00 UTC | Jul 10, 06:10 UTC | 19h 10m |
| 2026-07-08 | - | Jul 8, 06:25 UTC | Jul 8, 08:30 UTC | 2h 5m |
| 2026-07-07 | - | Jul 7, 12:25 UTC | Jul 7, 13:30 UTC | 1h 5m |
| 2026-07-06 | ORY → ORY | Jul 6, 12:30 UTC | Jul 7, 08:15 UTC | 19h 45m |
| 2026-07-05 | - | Jul 5, 12:20 UTC | Jul 6, 06:55 UTC | 18h 35m |
| 2026-07-05 | ORY → ORY | Jul 5, 11:15 UTC | Jul 6, 06:55 UTC | 19h 40m |
| 2026-07-04 | ORY → ORY | Jul 4, 11:05 UTC | Jul 5, 06:10 UTC | 19h 5m |
| 2026-06-06 | ORY → FDF | Jun 6, 12:20 UTC | Jun 7, 07:45 UTC | 19h 25m |
| 2026-06-02 | PTP → ORY | Jun 2, 12:20 UTC | Jun 3, 06:40 UTC | 18h 20m |
| 2026-06-02 | ORY → PTP | Jun 2, 11:30 UTC | Jun 3, 06:40 UTC | 19h 10m |
| 2026-06-01 | ORY → PTP | Jun 1, 10:35 UTC | Jun 2, 05:50 UTC | 19h 15m |
| 2026-05-30 | ORY → FDF | May 30, 12:15 UTC | May 30, 15:35 UTC | 3h 20m |
| 2026-05-27 | MRS → RUN | May 27, 19:55 UTC | May 27, 22:25 UTC | 2h 30m |
| 2026-05-27 | MRS → RUN | May 27, 17:30 UTC | May 27, 18:10 UTC | 40m |
| 2026-05-27 | MRS → LYS | May 27, 07:50 UTC | May 27, 08:20 UTC | 30m |
| 2026-05-26 | MRS → RUN | May 26, 00:39 UTC | May 26, 01:20 UTC | 40m |
| 2026-05-25 | MRS → RUN | May 25, 19:44 UTC | May 25, 22:15 UTC | 2h 30m |
| 2026-05-25 | MRS → RUN | May 25, 17:20 UTC | May 25, 17:55 UTC | 35m |
| 2026-05-25 | MRS → LYS | May 25, 06:45 UTC | May 25, 07:20 UTC | 35m |
| 2026-05-23 | ORY → DZA | May 23, 19:25 UTC | May 23, 23:00 UTC | 3h 35m |
| 2026-05-10 | MRU → ORY | May 10, 00:45 UTC | May 10, 04:39 UTC | 3h 55m |
| 2026-05-08 | ORY → MRU | May 8, 19:40 UTC | May 8, 23:25 UTC | 3h 45m |
| 2026-05-07 | ABJ → ORY | May 7, 15:55 UTC | May 8, 06:59 UTC | 15h 5m |
| 2026-05-06 | PTP → ORY | May 6, 04:50 UTC | May 6, 06:20 UTC | 1h 30m |
| 2026-05-05 | PTP → ORY | May 5, 10:25 UTC | May 6, 06:20 UTC | 19h 55m |
| 2026-05-03 | MRU → ORY | May 3, 00:15 UTC | May 3, 04:40 UTC | 4h 24m |
| 2026-05-01 | ORY → MRU | May 1, 20:05 UTC | May 1, 22:55 UTC | 2h 50m |
| 2026-05-01 | RUN → ORY | May 1, 02:00 UTC | May 1, 05:40 UTC | 3h 40m |
| 2026-04-29 | ORY → RUN | Apr 29, 19:20 UTC | Apr 29, 22:15 UTC | 2h 55m |
| 2026-04-27 | PTP → ORY | Apr 27, 12:20 UTC | Apr 28, 07:50 UTC | 19h 30m |
| 2026-04-27 | ORY → PTP | Apr 27, 10:40 UTC | Apr 28, 07:50 UTC | 21h 10m |
| 2026-04-26 | RUN → ORY | Apr 26, 02:20 UTC | Apr 26, 05:40 UTC | 3h 20m |
| 2026-04-24 | ORY → TNR | Apr 24, 19:35 UTC | Apr 24, 23:40 UTC | 4h 5m |
| 2026-04-23 | ORY → ABJ | Apr 23, 15:05 UTC | Apr 24, 06:35 UTC | 15h 30m |
| 2026-04-22 | FDF → ORY | Apr 22, 12:20 UTC | Apr 23, 07:45 UTC | 19h 25m |
| 2026-04-22 | FDF → ORY | Apr 22, 12:00 UTC | Apr 23, 07:45 UTC | 19h 45m |
| 2026-04-19 | ORY → RUN | Apr 19, 19:35 UTC | Apr 19, 22:25 UTC | 2h 50m |
| 2026-04-17 | - | Apr 17, 21:25 UTC | Apr 17, 22:55 UTC | 1h 30m |
| 2026-04-17 | - | Apr 17, 20:00 UTC | Apr 17, 21:20 UTC | 1h 20m |
| 2026-04-15 | - | Apr 15, 21:05 UTC | Apr 15, 22:35 UTC | 1h 30m |
| 2026-04-15 | - | Apr 15, 19:30 UTC | Apr 15, 21:00 UTC | 1h 30m |
| 2026-04-14 | RUN → ORY | Apr 14, 05:15 UTC | Apr 14, 05:20 UTC | 5m |
Specifications
| Registration | F-HRNB |
| Aircraft type | AIRBUS A-330-900 (A339) |
| Mode-S code | 39C5A1 · 16342641 (octal) |
Looking for transponder-level data? View the Mode-S 39C5A1 page for country allocation, callsign history, and ADS-B signal details.
F-HRNB frequently asked
What type of aircraft is F-HRNB?
F-HRNB is a AIRBUS A-330-900 (ICAO type code A339).
What is the Mode-S transponder code for F-HRNB?
F-HRNB broadcasts on Mode-S (ICAO 24-bit) address 39C5A1 (octal 16342641). View the transponder page.
What route does F-HRNB typically fly?
F-HRNB most frequently flies between MRS and RUN based on observed flights.
Where is F-HRNB right now?
F-HRNB is not currently being tracked; last seen 22h ago.