Airborne now · flying as TJT777C at 4,950 ft
- Flights observed
- 122 showing last 50
- Avg flight time
- 1h 3m
- Typical route
- ORY → LPY
- Last seen
- 1h ago
Live position
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 01:20 UTC | Jul 14, 02:50 UTC | 1h 30m |
| 2026-07-12 | - | Jul 12, 01:25 UTC | Jul 12, 04:15 UTC | 2h 50m |
| 2026-07-11 | - | Jul 11, 08:10 UTC | Jul 11, 08:30 UTC | 20m |
| 2026-07-02 | - | Jul 2, 11:20 UTC | Jul 2, 12:20 UTC | 1h 0m |
| 2026-06-29 | MRS → MXP | Jun 29, 17:40 UTC | Jun 29, 18:49 UTC | 1h 10m |
| 2026-06-29 | - | Jun 29, 16:00 UTC | Jun 29, 16:10 UTC | 10m |
| 2026-06-12 | MXP → MRS | Jun 12, 18:20 UTC | Jun 12, 19:30 UTC | 1h 10m |
| 2026-06-12 | LYS → MXP | Jun 12, 16:30 UTC | Jun 12, 17:30 UTC | 1h 0m |
| 2026-06-12 | BLQ → LYS | Jun 12, 14:25 UTC | Jun 12, 15:40 UTC | 1h 15m |
| 2026-06-12 | LYS → BLQ | Jun 12, 12:00 UTC | Jun 12, 13:10 UTC | 1h 10m |
| 2026-06-11 | PUF → LYS | Jun 11, 16:40 UTC | Jun 11, 17:55 UTC | 1h 15m |
| 2026-06-11 | LYS → PUF | Jun 11, 14:55 UTC | Jun 11, 16:05 UTC | 1h 10m |
| 2026-06-11 | ORY → LPY | Jun 11, 07:00 UTC | Jun 11, 08:30 UTC | 1h 30m |
| 2026-06-11 | LPY → ORY | Jun 11, 05:00 UTC | Jun 11, 06:10 UTC | 1h 10m |
| 2026-06-10 | ORY → LPY | Jun 10, 16:55 UTC | Jun 10, 17:45 UTC | 50m |
| 2026-06-10 | LPY → ORY | Jun 10, 05:05 UTC | Jun 10, 06:05 UTC | 1h 0m |
| 2026-06-09 | ORY → LPY | Jun 9, 17:00 UTC | Jun 9, 17:50 UTC | 50m |
| 2026-06-09 | LPY → ORY | Jun 9, 04:55 UTC | Jun 9, 06:00 UTC | 1h 5m |
| 2026-06-08 | ORY → LPY | Jun 8, 06:50 UTC | Jun 8, 07:40 UTC | 50m |
| 2026-06-08 | LPY → ORY | Jun 8, 05:00 UTC | Jun 8, 06:00 UTC | 1h 0m |
| 2026-06-05 | ORY → LPY | Jun 5, 17:00 UTC | Jun 5, 17:55 UTC | 55m |
| 2026-06-05 | LPY → ORY | Jun 5, 15:00 UTC | Jun 5, 16:00 UTC | 1h 0m |
| 2026-06-04 | ORY → LPY | Jun 4, 17:05 UTC | Jun 4, 18:00 UTC | 55m |
| 2026-06-04 | LPY → ORY | Jun 4, 15:10 UTC | Jun 4, 16:10 UTC | 1h 0m |
| 2026-06-04 | ORY → LPY | Jun 4, 06:45 UTC | Jun 4, 07:45 UTC | 1h 0m |
| 2026-06-04 | LPY → ORY | Jun 4, 04:55 UTC | Jun 4, 05:55 UTC | 1h 0m |
| 2026-06-03 | ORY → LPY | Jun 3, 17:10 UTC | Jun 3, 18:00 UTC | 50m |
| 2026-06-03 | LPY → ORY | Jun 3, 15:00 UTC | Jun 3, 16:05 UTC | 1h 5m |
| 2026-06-03 | ORY → LPY | Jun 3, 06:45 UTC | Jun 3, 07:35 UTC | 50m |
| 2026-06-03 | LPY → ORY | Jun 3, 04:55 UTC | Jun 3, 06:10 UTC | 1h 15m |
| 2026-06-02 | ORY → LPY | Jun 2, 17:15 UTC | Jun 2, 18:10 UTC | 55m |
| 2026-06-02 | LPY → ORY | Jun 2, 15:05 UTC | Jun 2, 16:10 UTC | 1h 5m |
| 2026-06-02 | ORY → LPY | Jun 2, 06:45 UTC | Jun 2, 07:40 UTC | 55m |
| 2026-06-02 | LPY → ORY | Jun 2, 05:00 UTC | Jun 2, 06:05 UTC | 1h 5m |
| 2026-06-01 | ORY → LPY | Jun 1, 06:45 UTC | Jun 1, 07:35 UTC | 50m |
| 2026-06-01 | LPY → ORY | Jun 1, 05:00 UTC | Jun 1, 06:10 UTC | 1h 10m |
| 2026-05-29 | ORY → LPY | May 29, 17:00 UTC | May 29, 17:50 UTC | 50m |
| 2026-05-29 | LPY → ORY | May 29, 15:05 UTC | May 29, 16:10 UTC | 1h 5m |
| 2026-05-28 | ORY → LPY | May 28, 17:55 UTC | May 28, 18:50 UTC | 55m |
| 2026-05-28 | LPY → ORY | May 28, 04:55 UTC | May 28, 06:10 UTC | 1h 15m |
| 2026-05-27 | ORY → LPY | May 27, 17:00 UTC | May 27, 17:55 UTC | 55m |
| 2026-05-27 | LPY → ORY | May 27, 05:04 UTC | May 27, 06:15 UTC | 1h 10m |
| 2026-05-26 | ORY → LPY | May 26, 16:45 UTC | May 26, 17:39 UTC | 55m |
| 2026-05-26 | LPY → ORY | May 26, 15:05 UTC | May 26, 16:05 UTC | 1h 0m |
| 2026-05-26 | ORY → LPY | May 26, 06:49 UTC | May 26, 07:45 UTC | 55m |
| 2026-05-26 | LPY → ORY | May 26, 04:54 UTC | May 26, 05:59 UTC | 1h 5m |
| 2026-05-22 | ORY → LPY | May 22, 17:00 UTC | May 22, 17:55 UTC | 55m |
| 2026-05-22 | LPY → ORY | May 22, 15:05 UTC | May 22, 16:15 UTC | 1h 10m |
| 2026-05-21 | ORY → LPY | May 21, 18:00 UTC | May 21, 18:55 UTC | 55m |
| 2026-05-21 | LPY → ORY | May 21, 15:00 UTC | May 21, 16:10 UTC | 1h 10m |
Specifications
| Registration | F-GUPE |
| Aircraft type | BEECH 1900 (B190) |
| Mode-S code | 3951E4 · 16250744 (octal) |
Looking for transponder-level data? View the Mode-S 3951E4 page for country allocation, callsign history, and ADS-B signal details.
F-GUPE frequently asked
What type of aircraft is F-GUPE?
F-GUPE is a BEECH 1900 (ICAO type code B190).
What is the Mode-S transponder code for F-GUPE?
F-GUPE broadcasts on Mode-S (ICAO 24-bit) address 3951E4 (octal 16250744). View the transponder page.
What route does F-GUPE typically fly?
F-GUPE most frequently flies between ORY and LPY based on observed flights.
Where is F-GUPE right now?
F-GUPE is currently airborne flying as TJT777C. Live position is shown on the map above.