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