Not currently tracked · last seen 24m ago
- Flights observed
- 365 showing last 50
- Avg flight time
- 1h 44m
- Typical route
- TLS → ORY
- Last seen
- 24m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | ORY → SFA | Jul 14, 06:05 UTC | Jul 14, 08:20 UTC | 2h 15m |
| 2026-07-13 | - | Jul 13, 18:20 UTC | Jul 13, 20:30 UTC | 2h 10m |
| 2026-07-13 | - | Jul 13, 15:05 UTC | Jul 13, 17:00 UTC | 1h 55m |
| 2026-07-13 | - | Jul 13, 11:55 UTC | Jul 13, 13:50 UTC | 1h 55m |
| 2026-07-13 | - | Jul 13, 07:45 UTC | Jul 13, 10:15 UTC | 2h 30m |
| 2026-07-13 | TLS → ORY | Jul 13, 04:30 UTC | Jul 13, 05:25 UTC | 55m |
| 2026-07-12 | ORY → TLS | Jul 12, 20:10 UTC | Jul 12, 21:05 UTC | 55m |
| 2026-07-12 | NCE → ORY | Jul 12, 17:35 UTC | Jul 12, 18:45 UTC | 1h 10m |
| 2026-07-12 | ORY → NCE | Jul 12, 15:20 UTC | Jul 12, 16:30 UTC | 1h 10m |
| 2026-07-12 | TLS → ORY | Jul 12, 12:05 UTC | Jul 12, 13:05 UTC | 1h 0m |
| 2026-07-12 | ORY → TLS | Jul 12, 10:05 UTC | Jul 12, 11:05 UTC | 1h 0m |
| 2026-07-12 | - | Jul 12, 07:35 UTC | Jul 12, 08:45 UTC | 1h 10m |
| 2026-07-12 | ORY → PGF | Jul 12, 05:40 UTC | Jul 12, 06:45 UTC | 1h 5m |
| 2026-07-11 | - | Jul 11, 16:35 UTC | Jul 11, 18:50 UTC | 2h 15m |
| 2026-07-11 | - | Jul 11, 13:20 UTC | Jul 11, 15:25 UTC | 2h 5m |
| 2026-07-11 | - | Jul 11, 09:00 UTC | Jul 11, 11:10 UTC | 2h 10m |
| 2026-07-11 | - | Jul 11, 05:35 UTC | Jul 11, 07:40 UTC | 2h 5m |
| 2026-07-10 | - | Jul 10, 18:35 UTC | Jul 10, 20:50 UTC | 2h 15m |
| 2026-07-10 | - | Jul 10, 15:10 UTC | Jul 10, 17:05 UTC | 1h 55m |
| 2026-07-10 | VLC → ORY | Jul 10, 12:00 UTC | Jul 10, 13:55 UTC | 1h 55m |
| 2026-07-10 | ORY → VLC | Jul 10, 09:20 UTC | Jul 10, 10:55 UTC | 1h 35m |
| 2026-07-10 | - | Jul 10, 05:15 UTC | Jul 10, 07:05 UTC | 1h 50m |
| 2026-07-09 | ORY → OPO | Jul 9, 19:45 UTC | Jul 9, 21:30 UTC | 1h 45m |
| 2026-07-09 | - | Jul 9, 17:05 UTC | Jul 9, 18:30 UTC | 1h 25m |
| 2026-07-09 | - | Jul 9, 14:30 UTC | Jul 9, 15:55 UTC | 1h 25m |
| 2026-07-09 | - | Jul 9, 10:05 UTC | Jul 9, 12:20 UTC | 2h 15m |
| 2026-07-09 | - | Jul 9, 06:20 UTC | Jul 9, 08:35 UTC | 2h 15m |
| 2026-07-08 | IBZ → ORY | Jul 8, 17:40 UTC | Jul 8, 19:15 UTC | 1h 35m |
| 2026-07-08 | ORY → IBZ | Jul 8, 15:05 UTC | Jul 8, 16:40 UTC | 1h 35m |
| 2026-07-08 | - | Jul 8, 11:30 UTC | Jul 8, 13:35 UTC | 2h 5m |
| 2026-07-08 | - | Jul 8, 07:50 UTC | Jul 8, 09:45 UTC | 1h 55m |
| 2026-07-08 | - | Jul 8, 04:20 UTC | Jul 8, 06:25 UTC | 2h 5m |
| 2026-07-07 | - | Jul 7, 18:45 UTC | Jul 7, 20:35 UTC | 1h 50m |
| 2026-07-07 | ORY → SAW | Jul 7, 16:25 UTC | Jul 7, 17:10 UTC | 45m |
| 2026-07-04 | - | Jul 4, 20:40 UTC | Jul 4, 22:00 UTC | 1h 20m |
| 2026-07-04 | - | Jul 4, 17:10 UTC | Jul 4, 18:55 UTC | 1h 45m |
| 2026-07-04 | - | Jul 4, 14:00 UTC | Jul 4, 15:35 UTC | 1h 35m |
| 2026-07-04 | - | Jul 4, 11:35 UTC | Jul 4, 13:05 UTC | 1h 30m |
| 2026-07-04 | ATH → LYS | Jul 4, 07:50 UTC | Jul 4, 10:25 UTC | 2h 35m |
| 2026-07-04 | LYS → ATH | Jul 4, 04:15 UTC | Jul 4, 06:35 UTC | 2h 20m |
| 2026-07-03 | - | Jul 3, 18:35 UTC | Jul 3, 20:20 UTC | 1h 45m |
| 2026-07-03 | BOD → SVQ | Jul 3, 15:50 UTC | Jul 3, 17:10 UTC | 1h 20m |
| 2026-07-03 | - | Jul 3, 13:20 UTC | Jul 3, 14:45 UTC | 1h 25m |
| 2026-07-03 | LYS → SVQ | Jul 3, 10:25 UTC | Jul 3, 12:15 UTC | 1h 50m |
| 2026-07-03 | - | Jul 3, 07:20 UTC | Jul 3, 09:10 UTC | 1h 50m |
| 2026-07-03 | - | Jul 3, 04:40 UTC | Jul 3, 06:15 UTC | 1h 35m |
| 2026-07-02 | - | Jul 2, 17:20 UTC | Jul 2, 20:00 UTC | 2h 40m |
| 2026-07-02 | - | Jul 2, 13:35 UTC | Jul 2, 16:15 UTC | 2h 40m |
| 2026-07-02 | - | Jul 2, 07:55 UTC | Jul 2, 09:20 UTC | 1h 25m |
| 2026-07-02 | - | Jul 2, 04:50 UTC | Jul 2, 06:00 UTC | 1h 10m |
Specifications
| Registration | F-HTVK |
| Aircraft type | BOEING 737-800 (B738) |
| Mode-S code | 39CEAA · 16347252 (octal) |
Looking for transponder-level data? View the Mode-S 39CEAA page for country allocation, callsign history, and ADS-B signal details.
F-HTVK frequently asked
What type of aircraft is F-HTVK?
F-HTVK is a BOEING 737-800 (ICAO type code B738).
What is the Mode-S transponder code for F-HTVK?
F-HTVK broadcasts on Mode-S (ICAO 24-bit) address 39CEAA (octal 16347252). View the transponder page.
What route does F-HTVK typically fly?
F-HTVK most frequently flies between TLS and ORY based on observed flights.
Where is F-HTVK right now?
F-HTVK is not currently being tracked; last seen 24m ago.