On the ground · transponder active
- Flights observed
- 374 showing last 50
- Avg flight time
- 2h 15m
- Typical route
- ORY → OPO
- Last seen
- 1h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 05:40 UTC | Jul 14, 06:15 UTC | 35m |
| 2026-07-13 | ORY → OPO | Jul 13, 19:00 UTC | Jul 13, 21:00 UTC | 2h 0m |
| 2026-07-13 | - | Jul 13, 09:45 UTC | Jul 13, 17:40 UTC | 7h 55m |
| 2026-07-13 | - | Jul 13, 06:35 UTC | Jul 13, 09:40 UTC | 3h 5m |
| 2026-07-12 | ORY → ORY | Jul 12, 07:31 UTC | Jul 12, 18:05 UTC | 10h 35m |
| 2026-07-10 | BIA → ORY | Jul 10, 18:05 UTC | Jul 10, 19:25 UTC | 1h 20m |
| 2026-07-10 | - | Jul 10, 15:40 UTC | Jul 10, 17:10 UTC | 1h 30m |
| 2026-07-10 | - | Jul 10, 13:00 UTC | Jul 10, 14:20 UTC | 1h 20m |
| 2026-07-10 | ORY → AJA | Jul 10, 10:25 UTC | Jul 10, 11:50 UTC | 1h 25m |
| 2026-07-10 | - | Jul 10, 04:30 UTC | Jul 10, 07:45 UTC | 3h 15m |
| 2026-07-09 | - | Jul 9, 17:30 UTC | Jul 9, 20:25 UTC | 2h 55m |
| 2026-07-09 | - | Jul 9, 13:05 UTC | Jul 9, 15:15 UTC | 2h 10m |
| 2026-07-09 | - | Jul 9, 09:20 UTC | Jul 9, 11:15 UTC | 1h 55m |
| 2026-07-09 | LIS → ORY | Jul 9, 05:55 UTC | Jul 9, 07:50 UTC | 1h 55m |
| 2026-07-08 | ORY → LIS | Jul 8, 20:20 UTC | Jul 8, 22:35 UTC | 2h 15m |
| 2026-07-08 | - | Jul 8, 16:45 UTC | Jul 8, 19:00 UTC | 2h 15m |
| 2026-07-08 | - | Jul 8, 13:00 UTC | Jul 8, 15:05 UTC | 2h 5m |
| 2026-07-08 | OPO → ORY | Jul 8, 09:05 UTC | Jul 8, 10:50 UTC | 1h 45m |
| 2026-07-08 | ORY → OPO | Jul 8, 06:10 UTC | Jul 8, 08:00 UTC | 1h 50m |
| 2026-07-07 | - | Jul 7, 18:30 UTC | Jul 7, 20:05 UTC | 1h 35m |
| 2026-07-07 | - | Jul 7, 16:10 UTC | Jul 7, 17:35 UTC | 1h 25m |
| 2026-07-07 | - | Jul 7, 09:10 UTC | Jul 7, 10:15 UTC | 1h 5m |
| 2026-07-07 | ORY → MPL | Jul 7, 07:10 UTC | Jul 7, 08:10 UTC | 1h 0m |
| 2026-07-06 | - | Jul 6, 16:50 UTC | Jul 6, 17:55 UTC | 1h 5m |
| 2026-07-06 | - | Jul 6, 14:30 UTC | Jul 6, 15:45 UTC | 1h 15m |
| 2026-07-06 | TLN → BES | Jul 6, 12:15 UTC | Jul 6, 13:40 UTC | 1h 25m |
| 2026-07-06 | - | Jul 6, 10:00 UTC | Jul 6, 11:25 UTC | 1h 25m |
| 2026-07-06 | - | Jul 6, 07:50 UTC | Jul 6, 09:10 UTC | 1h 20m |
| 2026-07-05 | - | Jul 5, 19:40 UTC | Jul 5, 20:40 UTC | 1h 0m |
| 2026-07-05 | - | Jul 5, 17:50 UTC | Jul 5, 18:40 UTC | 50m |
| 2026-07-05 | - | Jul 5, 15:00 UTC | Jul 5, 16:40 UTC | 1h 40m |
| 2026-07-05 | - | Jul 5, 12:10 UTC | Jul 5, 13:55 UTC | 1h 45m |
| 2026-07-05 | - | Jul 5, 09:50 UTC | Jul 5, 10:50 UTC | 1h 0m |
| 2026-07-05 | - | Jul 5, 06:10 UTC | Jul 5, 07:55 UTC | 1h 45m |
| 2026-07-04 | ORY → ORY | Jul 4, 08:20 UTC | Jul 4, 19:20 UTC | 11h 0m |
| 2026-07-04 | OPO → ORY | Jul 4, 05:15 UTC | Jul 4, 07:00 UTC | 1h 45m |
| 2026-07-03 | ORY → OPO | Jul 3, 19:40 UTC | Jul 3, 21:30 UTC | 1h 50m |
| 2026-07-03 | - | Jul 3, 16:45 UTC | Jul 3, 18:15 UTC | 1h 30m |
| 2026-07-03 | - | Jul 3, 14:15 UTC | Jul 3, 15:45 UTC | 1h 30m |
| 2026-07-03 | - | Jul 3, 10:55 UTC | Jul 3, 13:05 UTC | 2h 10m |
| 2026-07-03 | - | Jul 3, 07:35 UTC | Jul 3, 09:20 UTC | 1h 45m |
| 2026-07-02 | ORY → ORY | Jul 2, 14:00 UTC | Jul 2, 19:35 UTC | 5h 35m |
| 2026-07-02 | - | Jul 2, 09:50 UTC | Jul 2, 11:30 UTC | 1h 40m |
| 2026-07-02 | - | Jul 2, 05:55 UTC | Jul 2, 07:30 UTC | 1h 35m |
| 2026-07-01 | - | Jul 1, 17:55 UTC | Jul 1, 21:00 UTC | 3h 5m |
| 2026-07-01 | - | Jul 1, 13:00 UTC | Jul 1, 16:05 UTC | 3h 5m |
| 2026-07-01 | NCE → ORY | Jul 1, 10:40 UTC | Jul 1, 11:50 UTC | 1h 10m |
| 2026-07-01 | - | Jul 1, 07:25 UTC | Jul 1, 08:40 UTC | 1h 15m |
| 2026-07-01 | - | Jul 1, 05:05 UTC | Jul 1, 06:10 UTC | 1h 5m |
| 2026-06-30 | ORY → MPL | Jun 30, 18:55 UTC | Jun 30, 20:00 UTC | 1h 5m |
Specifications
| Registration | F-HTVB |
| Aircraft type | BOEING 737-800 (B738) |
| Mode-S code | 39CEA1 · 16347241 (octal) |
Looking for transponder-level data? View the Mode-S 39CEA1 page for country allocation, callsign history, and ADS-B signal details.
F-HTVB frequently asked
What type of aircraft is F-HTVB?
F-HTVB is a BOEING 737-800 (ICAO type code B738).
What is the Mode-S transponder code for F-HTVB?
F-HTVB broadcasts on Mode-S (ICAO 24-bit) address 39CEA1 (octal 16347241). View the transponder page.
What route does F-HTVB typically fly?
F-HTVB most frequently flies between ORY and OPO based on observed flights.
Where is F-HTVB right now?
F-HTVB is currently on the ground with its transponder active.