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