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