Not currently tracked · last seen 12h ago
- Flights observed
- 199 showing last 50
- Avg flight time
- 1h 10m
- Typical route
- BJC → BJC
- Last seen
- 12h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | BJC → BJC | Jul 14, 01:20 UTC | Jul 14, 02:15 UTC | 55m |
| 2026-07-13 | BJC → BJC | Jul 13, 18:45 UTC | Jul 13, 20:30 UTC | 1h 45m |
| 2026-07-13 | BJC → BJC | Jul 13, 13:05 UTC | Jul 13, 14:20 UTC | 1h 15m |
| 2026-07-12 | BJC → BJC | Jul 12, 18:40 UTC | Jul 12, 20:20 UTC | 1h 40m |
| 2026-07-12 | BJC → BJC | Jul 12, 15:40 UTC | Jul 12, 16:30 UTC | 50m |
| 2026-07-12 | BJC → BJC | Jul 12, 13:25 UTC | Jul 12, 14:30 UTC | 1h 5m |
| 2026-07-12 | - | Jul 12, 01:30 UTC | Jul 12, 02:30 UTC | 1h 0m |
| 2026-07-11 | - | Jul 11, 20:35 UTC | Jul 11, 21:30 UTC | 55m |
| 2026-07-11 | BJC → BJC | Jul 11, 18:20 UTC | Jul 11, 19:40 UTC | 1h 20m |
| 2026-07-11 | BJC → BJC | Jul 11, 15:55 UTC | Jul 11, 17:15 UTC | 1h 20m |
| 2026-07-11 | BJC → BJC | Jul 11, 12:40 UTC | Jul 11, 14:00 UTC | 1h 20m |
| 2026-07-10 | BJC → BJC | Jul 10, 18:25 UTC | Jul 10, 20:05 UTC | 1h 40m |
| 2026-07-10 | BJC → BJC | Jul 10, 15:50 UTC | Jul 10, 17:20 UTC | 1h 30m |
| 2026-07-10 | - | Jul 10, 14:30 UTC | Jul 10, 14:40 UTC | 10m |
| 2026-07-10 | - | Jul 10, 13:40 UTC | Jul 10, 14:25 UTC | 45m |
| 2026-07-09 | BJC → BJC | Jul 9, 16:55 UTC | Jul 9, 18:35 UTC | 1h 40m |
| 2026-07-09 | BJC → BJC | Jul 9, 15:15 UTC | Jul 9, 15:55 UTC | 40m |
| 2026-07-08 | BJC → BJC | Jul 8, 13:30 UTC | Jul 8, 15:05 UTC | 1h 35m |
| 2026-07-07 | BJC → BJC | Jul 7, 18:45 UTC | Jul 7, 19:15 UTC | 30m |
| 2026-07-07 | BJC → BJC | Jul 7, 14:50 UTC | Jul 7, 16:10 UTC | 1h 20m |
| 2026-07-06 | - | Jul 6, 00:10 UTC | Jul 6, 00:35 UTC | 25m |
| 2026-07-05 | - | Jul 5, 23:20 UTC | Jul 6, 00:05 UTC | 45m |
| 2026-07-05 | BJC → BJC | Jul 5, 21:05 UTC | Jul 5, 21:40 UTC | 35m |
| 2026-07-05 | BJC → BJC | Jul 5, 18:05 UTC | Jul 5, 19:20 UTC | 1h 15m |
| 2026-07-05 | BJC → BJC | Jul 5, 12:50 UTC | Jul 5, 15:05 UTC | 2h 15m |
| 2026-07-04 | BJC → BJC | Jul 4, 17:20 UTC | Jul 4, 18:45 UTC | 1h 25m |
| 2026-07-03 | BJC → BJC | Jul 3, 23:45 UTC | Jul 4, 00:55 UTC | 1h 10m |
| 2026-07-03 | - | Jul 3, 20:10 UTC | Jul 3, 20:20 UTC | 10m |
| 2026-07-03 | - | Jul 3, 18:50 UTC | Jul 3, 20:05 UTC | 1h 15m |
| 2026-07-03 | BJC → BJC | Jul 3, 15:50 UTC | Jul 3, 17:30 UTC | 1h 40m |
| 2026-07-03 | BJC → BJC | Jul 3, 12:40 UTC | Jul 3, 14:25 UTC | 1h 45m |
| 2026-07-02 | BJC → BJC | Jul 2, 20:50 UTC | Jul 2, 22:10 UTC | 1h 20m |
| 2026-07-02 | - | Jul 2, 18:25 UTC | Jul 2, 19:50 UTC | 1h 25m |
| 2026-07-02 | BJC → BJC | Jul 2, 16:15 UTC | Jul 2, 17:20 UTC | 1h 5m |
| 2026-07-02 | BJC → BJC | Jul 2, 13:20 UTC | Jul 2, 14:50 UTC | 1h 30m |
| 2026-07-02 | BJC → BJC | Jul 2, 01:15 UTC | Jul 2, 02:15 UTC | 1h 0m |
| 2026-07-01 | BJC → BJC | Jul 1, 21:55 UTC | Jul 1, 23:10 UTC | 1h 15m |
| 2026-07-01 | BJC → BJC | Jul 1, 19:25 UTC | Jul 1, 20:40 UTC | 1h 15m |
| 2026-07-01 | BJC → BJC | Jul 1, 17:30 UTC | Jul 1, 18:35 UTC | 1h 5m |
| 2026-07-01 | - | Jul 1, 15:25 UTC | Jul 1, 15:40 UTC | 15m |
| 2026-07-01 | - | Jul 1, 14:30 UTC | Jul 1, 15:20 UTC | 50m |
| 2026-07-01 | BJC → BJC | Jul 1, 12:25 UTC | Jul 1, 13:35 UTC | 1h 10m |
| 2026-06-30 | BJC → BJC | Jun 30, 17:40 UTC | Jun 30, 19:05 UTC | 1h 25m |
| 2026-06-30 | BJC → BJC | Jun 30, 15:20 UTC | Jun 30, 16:25 UTC | 1h 5m |
| 2026-06-30 | BJC → BJC | Jun 30, 12:25 UTC | Jun 30, 13:45 UTC | 1h 20m |
| 2026-06-29 | BJC → BJC | Jun 29, 23:25 UTC | Jun 30, 00:35 UTC | 1h 10m |
| 2026-06-29 | BJC → BJC | Jun 29, 13:19 UTC | Jun 29, 14:34 UTC | 1h 15m |
| 2026-06-28 | BJC → BJC | Jun 28, 19:44 UTC | Jun 28, 21:10 UTC | 1h 25m |
| 2026-06-28 | BJC → BJC | Jun 28, 16:39 UTC | Jun 28, 18:14 UTC | 1h 35m |
| 2026-06-28 | BJC → BJC | Jun 28, 13:40 UTC | Jun 28, 14:54 UTC | 1h 15m |
Specifications
| Registration | N75FF |
| Operator | FF22 LLC |
| Mode-S code | AA1833 · 52414063 (octal) |
Looking for transponder-level data? View the Mode-S AA1833 page for country allocation, callsign history, and ADS-B signal details.
N75FF frequently asked
Who operates N75FF?
N75FF is operated by FF22 LLC.
What is the Mode-S transponder code for N75FF?
N75FF broadcasts on Mode-S (ICAO 24-bit) address AA1833 (octal 52414063). View the transponder page.
What route does N75FF typically fly?
N75FF most frequently flies between BJC and BJC based on observed flights.
Where is N75FF right now?
N75FF is not currently being tracked; last seen 12h ago.