Not currently tracked · last seen 11h ago
- Flights observed
- 537 showing last 50
- Avg flight time
- 52m
- Typical route
- NCL → CDG
- Last seen
- 11h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | VLC → CDG | Jul 13, 19:50 UTC | Jul 13, 20:35 UTC | 45m |
| 2026-07-13 | DUS → CDG | Jul 13, 17:35 UTC | Jul 13, 18:30 UTC | 55m |
| 2026-07-13 | CDG → DUS | Jul 13, 15:55 UTC | Jul 13, 16:40 UTC | 45m |
| 2026-07-13 | BER → CDG | Jul 13, 14:00 UTC | Jul 13, 14:55 UTC | 55m |
| 2026-07-13 | CDG → BSL | Jul 13, 12:05 UTC | Jul 13, 12:50 UTC | 45m |
| 2026-07-13 | - | Jul 13, 05:05 UTC | Jul 13, 06:01 UTC | 55m |
| 2026-07-12 | - | Jul 12, 18:50 UTC | Jul 12, 19:35 UTC | 45m |
| 2026-07-12 | BIQ → CDG | Jul 12, 13:50 UTC | Jul 12, 14:50 UTC | 1h 0m |
| 2026-07-12 | - | Jul 12, 11:45 UTC | Jul 12, 12:45 UTC | 1h 0m |
| 2026-07-11 | DUS → CDG | Jul 11, 17:30 UTC | Jul 11, 18:20 UTC | 50m |
| 2026-07-11 | CDG → DUS | Jul 11, 15:50 UTC | Jul 11, 16:35 UTC | 45m |
| 2026-07-11 | NCL → CDG | Jul 11, 10:40 UTC | Jul 11, 11:55 UTC | 1h 15m |
| 2026-07-11 | - | Jul 11, 08:50 UTC | Jul 11, 09:55 UTC | 1h 5m |
| 2026-07-11 | NCL → CDG | Jul 11, 05:45 UTC | Jul 11, 07:15 UTC | 1h 30m |
| 2026-07-10 | - | Jul 10, 19:15 UTC | Jul 10, 20:25 UTC | 1h 10m |
| 2026-07-10 | NCL → CDG | Jul 10, 10:40 UTC | Jul 10, 11:55 UTC | 1h 15m |
| 2026-07-10 | - | Jul 10, 08:30 UTC | Jul 10, 09:35 UTC | 1h 5m |
| 2026-07-10 | BOD → CDG | Jul 10, 05:20 UTC | Jul 10, 06:10 UTC | 50m |
| 2026-07-09 | - | Jul 9, 18:35 UTC | Jul 9, 19:25 UTC | 50m |
| 2026-07-09 | NTE → LYS | Jul 9, 16:40 UTC | Jul 9, 17:30 UTC | 50m |
| 2026-07-09 | LYS → NTE | Jul 9, 14:55 UTC | Jul 9, 15:45 UTC | 50m |
| 2026-07-09 | TLS → LYS | Jul 9, 13:20 UTC | Jul 9, 13:55 UTC | 35m |
| 2026-07-09 | LYS → TLS | Jul 9, 11:50 UTC | Jul 9, 12:30 UTC | 40m |
| 2026-07-09 | - | Jul 9, 09:40 UTC | Jul 9, 10:20 UTC | 40m |
| 2026-07-09 | - | Jul 9, 08:10 UTC | Jul 9, 08:50 UTC | 40m |
| 2026-07-09 | - | Jul 9, 06:00 UTC | Jul 9, 06:55 UTC | 55m |
| 2026-07-08 | LYS → BIQ | Jul 8, 18:30 UTC | Jul 8, 19:30 UTC | 1h 0m |
| 2026-07-08 | BOD → LYS | Jul 8, 16:40 UTC | Jul 8, 17:35 UTC | 55m |
| 2026-07-08 | ORY → TLS | Jul 8, 14:45 UTC | Jul 8, 15:30 UTC | 45m |
| 2026-07-08 | BIQ → LYS | Jul 8, 12:40 UTC | Jul 8, 13:35 UTC | 55m |
| 2026-07-08 | - | Jul 8, 10:55 UTC | Jul 8, 11:45 UTC | 50m |
| 2026-07-08 | - | Jul 8, 08:35 UTC | Jul 8, 09:25 UTC | 50m |
| 2026-07-08 | - | Jul 8, 06:40 UTC | Jul 8, 07:30 UTC | 50m |
| 2026-07-08 | - | Jul 8, 04:50 UTC | Jul 8, 05:40 UTC | 50m |
| 2026-07-07 | - | Jul 7, 18:45 UTC | Jul 7, 19:40 UTC | 55m |
| 2026-07-07 | TLS → LYS | Jul 7, 16:55 UTC | Jul 7, 17:35 UTC | 40m |
| 2026-07-07 | LYS → TLS | Jul 7, 14:50 UTC | Jul 7, 15:35 UTC | 45m |
| 2026-07-07 | TLS → LYS | Jul 7, 13:00 UTC | Jul 7, 13:35 UTC | 35m |
| 2026-07-07 | LYS → TLS | Jul 7, 11:20 UTC | Jul 7, 12:00 UTC | 40m |
| 2026-07-07 | - | Jul 7, 08:45 UTC | Jul 7, 09:30 UTC | 45m |
| 2026-07-07 | - | Jul 7, 06:45 UTC | Jul 7, 07:35 UTC | 50m |
| 2026-07-07 | - | Jul 7, 04:45 UTC | Jul 7, 05:45 UTC | 1h 0m |
| 2026-07-06 | LYS → BIQ | Jul 6, 18:30 UTC | Jul 6, 19:25 UTC | 55m |
| 2026-07-06 | BOD → LYS | Jul 6, 16:50 UTC | Jul 6, 17:35 UTC | 45m |
| 2026-07-06 | ORY → TLS | Jul 6, 15:10 UTC | Jul 6, 16:00 UTC | 50m |
| 2026-07-06 | BIQ → LYS | Jul 6, 12:50 UTC | Jul 6, 13:45 UTC | 55m |
| 2026-07-06 | - | Jul 6, 10:55 UTC | Jul 6, 11:45 UTC | 50m |
| 2026-07-05 | BIQ → LYS | Jul 5, 12:25 UTC | Jul 5, 13:20 UTC | 55m |
| 2026-07-03 | LYS → BIQ | Jul 3, 19:30 UTC | Jul 3, 20:20 UTC | 50m |
| 2026-07-03 | BOD → LYS | Jul 3, 17:40 UTC | Jul 3, 18:25 UTC | 45m |
Specifications
| Registration | F-HBXA |
| Aircraft type | EMBRAER ERJ-170-100 (E170) |
| Mode-S code | 3986E0 · 16303340 (octal) |
Looking for transponder-level data? View the Mode-S 3986E0 page for country allocation, callsign history, and ADS-B signal details.
F-HBXA frequently asked
What type of aircraft is F-HBXA?
F-HBXA is a EMBRAER ERJ-170-100 (ICAO type code E170).
What is the Mode-S transponder code for F-HBXA?
F-HBXA broadcasts on Mode-S (ICAO 24-bit) address 3986E0 (octal 16303340). View the transponder page.
What route does F-HBXA typically fly?
F-HBXA most frequently flies between NCL and CDG based on observed flights.
Where is F-HBXA right now?
F-HBXA is not currently being tracked; last seen 11h ago.