Not currently tracked · last seen 9h ago
- Flights observed
- 86 showing last 50
- Avg flight time
- 1h 1m
- Typical route
- ORY → LPY
- Last seen
- 9h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 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 |
| 2026-05-21 | ORY → LPY | May 21, 06:35 UTC | May 21, 07:30 UTC | 55m |
| 2026-05-21 | LPY → ORY | May 21, 04:55 UTC | May 21, 06:00 UTC | 1h 5m |
| 2026-05-20 | ORY → LPY | May 20, 16:55 UTC | May 20, 17:50 UTC | 55m |
| 2026-05-20 | LPY → ORY | May 20, 05:05 UTC | May 20, 06:15 UTC | 1h 10m |
| 2026-05-19 | ORY → LPY | May 19, 17:00 UTC | May 19, 17:55 UTC | 55m |
| 2026-05-19 | LPY → ORY | May 19, 14:55 UTC | May 19, 16:00 UTC | 1h 5m |
| 2026-05-19 | ORY → LPY | May 19, 06:50 UTC | May 19, 07:45 UTC | 55m |
| 2026-05-19 | LPY → ORY | May 19, 04:55 UTC | May 19, 06:00 UTC | 1h 5m |
| 2026-05-18 | ORY → LPY | May 18, 06:45 UTC | May 18, 07:40 UTC | 55m |
| 2026-05-18 | LPY → ORY | May 18, 05:00 UTC | May 18, 06:05 UTC | 1h 5m |
| 2026-05-13 | ORY → LPY | May 13, 16:50 UTC | May 13, 17:45 UTC | 55m |
| 2026-05-13 | LPY → ORY | May 13, 05:00 UTC | May 13, 06:00 UTC | 1h 0m |
| 2026-05-12 | ORY → LPY | May 12, 16:55 UTC | May 12, 17:45 UTC | 50m |
| 2026-05-12 | LPY → ORY | May 12, 15:01 UTC | May 12, 16:05 UTC | 1h 5m |
| 2026-05-12 | ORY → LPY | May 12, 06:50 UTC | May 12, 07:40 UTC | 50m |
| 2026-05-12 | LPY → ORY | May 12, 05:00 UTC | May 12, 06:15 UTC | 1h 15m |
| 2026-05-11 | ORY → LPY | May 11, 06:50 UTC | May 11, 07:45 UTC | 55m |
| 2026-05-11 | LPY → ORY | May 11, 05:00 UTC | May 11, 06:05 UTC | 1h 5m |
| 2026-05-07 | ORY → LPY | May 7, 17:00 UTC | May 7, 18:00 UTC | 1h 0m |
| 2026-05-07 | LPY → ORY | May 7, 15:05 UTC | May 7, 16:10 UTC | 1h 5m |
| 2026-05-07 | ORY → LPY | May 7, 06:40 UTC | May 7, 07:35 UTC | 55m |
| 2026-05-07 | LPY → ORY | May 7, 04:50 UTC | May 7, 05:55 UTC | 1h 5m |
| 2026-05-06 | ORY → LPY | May 6, 17:00 UTC | May 6, 17:55 UTC | 54m |
| 2026-05-06 | LPY → ORY | May 6, 04:55 UTC | May 6, 06:05 UTC | 1h 10m |
| 2026-05-05 | ORY → LPY | May 5, 17:00 UTC | May 5, 18:05 UTC | 1h 5m |
| 2026-05-05 | LPY → ORY | May 5, 15:05 UTC | May 5, 16:15 UTC | 1h 10m |
| 2026-05-05 | ORY → LPY | May 5, 06:40 UTC | May 5, 07:40 UTC | 1h 0m |
| 2026-05-05 | LPY → ORY | May 5, 04:55 UTC | May 5, 06:05 UTC | 1h 10m |
| 2026-05-04 | ORY → LPY | May 4, 07:05 UTC | May 4, 08:05 UTC | 1h 0m |
| 2026-05-04 | LPY → ORY | May 4, 05:05 UTC | May 4, 06:10 UTC | 1h 5m |
| 2026-04-30 | ORY → LPY | Apr 30, 16:55 UTC | Apr 30, 17:50 UTC | 55m |
| 2026-04-30 | LPY → ORY | Apr 30, 15:00 UTC | Apr 30, 16:00 UTC | 1h 0m |
| 2026-04-30 | ORY → LPY | Apr 30, 06:45 UTC | Apr 30, 07:50 UTC | 1h 5m |
| 2026-04-30 | LPY → ORY | Apr 30, 04:55 UTC | Apr 30, 06:05 UTC | 1h 10m |
| 2026-04-29 | ORY → LPY | Apr 29, 16:50 UTC | Apr 29, 17:45 UTC | 55m |
| 2026-04-29 | LPY → ORY | Apr 29, 05:00 UTC | Apr 29, 06: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 not currently being tracked; last seen 9h ago.