Not currently tracked · last seen 3d ago
- Flights observed
- 453 showing last 50
- Avg flight time
- 1h 21m
- Typical route
- BUD → AMS
- Last seen
- 3d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-11 | AMS → MUC | Jul 11, 05:40 UTC | Jul 11, 06:45 UTC | 1h 5m |
| 2026-07-10 | BUD → AMS | Jul 10, 18:35 UTC | Jul 10, 19:40 UTC | 1h 5m |
| 2026-07-10 | BUD → AMS | Jul 10, 17:45 UTC | Jul 10, 18:30 UTC | 45m |
| 2026-07-10 | AMS → BUD | Jul 10, 15:15 UTC | Jul 10, 16:50 UTC | 1h 35m |
| 2026-07-10 | - | Jul 10, 12:45 UTC | Jul 10, 13:55 UTC | 1h 10m |
| 2026-07-10 | - | Jul 10, 10:05 UTC | Jul 10, 11:20 UTC | 1h 15m |
| 2026-07-10 | - | Jul 10, 07:35 UTC | Jul 10, 08:50 UTC | 1h 15m |
| 2026-07-10 | - | Jul 10, 05:40 UTC | Jul 10, 06:40 UTC | 1h 0m |
| 2026-07-09 | BUD → AMS | Jul 9, 17:55 UTC | Jul 9, 19:50 UTC | 1h 55m |
| 2026-07-09 | AMS → BUD | Jul 9, 15:20 UTC | Jul 9, 16:55 UTC | 1h 35m |
| 2026-07-09 | - | Jul 9, 12:30 UTC | Jul 9, 13:40 UTC | 1h 10m |
| 2026-07-09 | - | Jul 9, 10:05 UTC | Jul 9, 11:20 UTC | 1h 15m |
| 2026-07-09 | MUC → AMS | Jul 9, 07:50 UTC | Jul 9, 08:55 UTC | 1h 5m |
| 2026-07-09 | - | Jul 9, 05:35 UTC | Jul 9, 06:35 UTC | 1h 0m |
| 2026-07-08 | BUD → AMS | Jul 8, 17:55 UTC | Jul 8, 19:45 UTC | 1h 50m |
| 2026-07-08 | AMS → BUD | Jul 8, 15:30 UTC | Jul 8, 17:05 UTC | 1h 35m |
| 2026-07-08 | - | Jul 8, 12:40 UTC | Jul 8, 13:55 UTC | 1h 15m |
| 2026-07-07 | - | Jul 7, 10:20 UTC | Jul 7, 11:30 UTC | 1h 10m |
| 2026-07-07 | - | Jul 7, 07:45 UTC | Jul 7, 09:00 UTC | 1h 15m |
| 2026-07-07 | AMS → MUC | Jul 7, 05:30 UTC | Jul 7, 06:35 UTC | 1h 5m |
| 2026-07-06 | BUD → AMS | Jul 6, 17:50 UTC | Jul 6, 19:45 UTC | 1h 55m |
| 2026-07-06 | AMS → BUD | Jul 6, 15:20 UTC | Jul 6, 16:55 UTC | 1h 35m |
| 2026-07-06 | LYS → AMS | Jul 6, 12:25 UTC | Jul 6, 13:40 UTC | 1h 15m |
| 2026-07-06 | - | Jul 6, 10:05 UTC | Jul 6, 11:15 UTC | 1h 10m |
| 2026-07-06 | MUC → AMS | Jul 6, 07:45 UTC | Jul 6, 09:00 UTC | 1h 15m |
| 2026-07-06 | AMS → MUC | Jul 6, 05:35 UTC | Jul 6, 06:35 UTC | 1h 0m |
| 2026-07-05 | BUD → AMS | Jul 5, 18:15 UTC | Jul 5, 20:10 UTC | 1h 55m |
| 2026-07-05 | AMS → BUD | Jul 5, 15:50 UTC | Jul 5, 17:25 UTC | 1h 35m |
| 2026-07-05 | LYS → AMS | Jul 5, 13:10 UTC | Jul 5, 14:20 UTC | 1h 10m |
| 2026-07-05 | - | Jul 5, 10:05 UTC | Jul 5, 11:15 UTC | 1h 10m |
| 2026-07-05 | MUC → AMS | Jul 5, 07:45 UTC | Jul 5, 08:55 UTC | 1h 10m |
| 2026-07-05 | - | Jul 5, 05:45 UTC | Jul 5, 06:40 UTC | 55m |
| 2026-07-04 | BUD → AMS | Jul 4, 17:50 UTC | Jul 4, 19:40 UTC | 1h 50m |
| 2026-07-04 | AMS → BUD | Jul 4, 15:15 UTC | Jul 4, 16:45 UTC | 1h 30m |
| 2026-07-04 | LYS → AMS | Jul 4, 12:30 UTC | Jul 4, 13:45 UTC | 1h 15m |
| 2026-07-04 | AMS → LYS | Jul 4, 10:15 UTC | Jul 4, 11:25 UTC | 1h 10m |
| 2026-07-03 | BUD → AMS | Jul 3, 18:05 UTC | Jul 3, 20:00 UTC | 1h 55m |
| 2026-07-03 | AMS → BUD | Jul 3, 15:35 UTC | Jul 3, 17:05 UTC | 1h 30m |
| 2026-07-03 | LYS → AMS | Jul 3, 12:55 UTC | Jul 3, 14:15 UTC | 1h 20m |
| 2026-07-03 | - | Jul 3, 10:15 UTC | Jul 3, 11:30 UTC | 1h 15m |
| 2026-07-03 | AMS → MUC | Jul 3, 05:30 UTC | Jul 3, 06:30 UTC | 1h 0m |
| 2026-07-02 | BUD → AMS | Jul 2, 18:10 UTC | Jul 2, 20:05 UTC | 1h 55m |
| 2026-07-02 | AMS → BUD | Jul 2, 15:40 UTC | Jul 2, 17:20 UTC | 1h 40m |
| 2026-07-02 | LYS → AMS | Jul 2, 13:15 UTC | Jul 2, 14:35 UTC | 1h 20m |
| 2026-07-02 | AMS → LYS | Jul 2, 10:25 UTC | Jul 2, 11:40 UTC | 1h 15m |
| 2026-07-02 | MUC → AMS | Jul 2, 07:40 UTC | Jul 2, 08:55 UTC | 1h 15m |
| 2026-07-02 | AMS → MUC | Jul 2, 05:30 UTC | Jul 2, 06:35 UTC | 1h 5m |
| 2026-07-01 | BUD → AMS | Jul 1, 18:25 UTC | Jul 1, 20:10 UTC | 1h 45m |
| 2026-07-01 | AMS → BUD | Jul 1, 15:45 UTC | Jul 1, 17:25 UTC | 1h 40m |
| 2026-07-01 | LYS → AMS | Jul 1, 12:40 UTC | Jul 1, 14:00 UTC | 1h 20m |
Specifications
| Registration | F-HBLP |
| Aircraft type | EMBRAER ERJ-190-100 (E190) |
| Mode-S code | 39856F · 16302557 (octal) |
Looking for transponder-level data? View the Mode-S 39856F page for country allocation, callsign history, and ADS-B signal details.
F-HBLP frequently asked
What type of aircraft is F-HBLP?
F-HBLP is a EMBRAER ERJ-190-100 (ICAO type code E190).
What is the Mode-S transponder code for F-HBLP?
F-HBLP broadcasts on Mode-S (ICAO 24-bit) address 39856F (octal 16302557). View the transponder page.
What route does F-HBLP typically fly?
F-HBLP most frequently flies between BUD and AMS based on observed flights.
Where is F-HBLP right now?
F-HBLP is not currently being tracked; last seen 3d ago.