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