On the ground · transponder active
- Flights observed
- 121 showing last 50
- Avg flight time
- 1h 5m
- Typical route
- BJC → BJC
- Last seen
- 15h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | - | May 29, 22:55 UTC | May 29, 23:10 UTC | 15m |
| 2026-05-29 | - | May 29, 20:45 UTC | May 29, 21:25 UTC | 40m |
| 2026-05-29 | BJC → BJC | May 29, 18:40 UTC | May 29, 19:55 UTC | 1h 15m |
| 2026-05-29 | BJC → BJC | May 29, 13:45 UTC | May 29, 14:45 UTC | 1h 0m |
| 2026-05-28 | BJC → BJC | May 28, 21:15 UTC | May 28, 21:55 UTC | 40m |
| 2026-05-28 | BJC → BJC | May 28, 19:05 UTC | May 28, 19:40 UTC | 35m |
| 2026-05-27 | BJC → BJC | May 27, 23:30 UTC | May 28, 00:30 UTC | 1h 0m |
| 2026-05-27 | BJC → BJC | May 27, 19:25 UTC | May 27, 20:10 UTC | 45m |
| 2026-05-27 | BJC → BJC | May 27, 15:55 UTC | May 27, 17:35 UTC | 1h 40m |
| 2026-05-26 | BJC → BJC | May 26, 19:40 UTC | May 26, 20:45 UTC | 1h 5m |
| 2026-05-26 | BJC → BJC | May 26, 13:19 UTC | May 26, 13:54 UTC | 35m |
| 2026-05-25 | BJC → BJC | May 25, 20:30 UTC | May 25, 22:15 UTC | 1h 45m |
| 2026-05-25 | BJC → BJC | May 25, 16:40 UTC | May 25, 17:30 UTC | 50m |
| 2026-05-25 | BJC → BJC | May 25, 14:00 UTC | May 25, 15:40 UTC | 1h 40m |
| 2026-05-24 | BJC → BJC | May 24, 17:40 UTC | May 24, 19:00 UTC | 1h 20m |
| 2026-05-24 | BJC → BJC | May 24, 15:20 UTC | May 24, 16:25 UTC | 1h 5m |
| 2026-05-23 | BJC → BJC | May 23, 16:05 UTC | May 23, 16:45 UTC | 40m |
| 2026-05-23 | BJC → BJC | May 23, 13:35 UTC | May 23, 15:20 UTC | 1h 45m |
| 2026-05-22 | BJC → BJC | May 22, 22:20 UTC | May 22, 23:05 UTC | 45m |
| 2026-05-22 | BJC → BJC | May 22, 15:30 UTC | May 22, 16:50 UTC | 1h 20m |
| 2026-05-22 | BJC → BJC | May 22, 12:40 UTC | May 22, 14:00 UTC | 1h 20m |
| 2026-05-21 | BJC → BJC | May 21, 21:20 UTC | May 21, 22:15 UTC | 55m |
| 2026-05-21 | - | May 21, 18:55 UTC | May 21, 20:00 UTC | 1h 5m |
| 2026-05-21 | BJC → BJC | May 21, 17:20 UTC | May 21, 17:55 UTC | 35m |
| 2026-05-21 | BJC → BJC | May 21, 14:15 UTC | May 21, 15:40 UTC | 1h 25m |
| 2026-05-21 | - | May 21, 04:30 UTC | May 21, 05:25 UTC | 55m |
| 2026-05-21 | - | May 21, 03:10 UTC | May 21, 04:00 UTC | 50m |
| 2026-05-21 | BJC → BJC | May 21, 00:00 UTC | May 21, 00:55 UTC | 55m |
| 2026-05-20 | BJC → BJC | May 20, 01:50 UTC | May 20, 02:40 UTC | 50m |
| 2026-05-19 | BJC → BJC | May 19, 23:10 UTC | May 20, 00:40 UTC | 1h 30m |
| 2026-05-17 | BJC → BJC | May 17, 16:01 UTC | May 17, 16:30 UTC | 30m |
| 2026-05-16 | BJC → BJC | May 16, 15:55 UTC | May 16, 16:50 UTC | 55m |
| 2026-05-15 | BJC → BJC | May 15, 21:10 UTC | May 15, 22:05 UTC | 55m |
| 2026-05-15 | BJC → BJC | May 15, 18:10 UTC | May 15, 19:20 UTC | 1h 10m |
| 2026-05-13 | BJC → BJC | May 13, 18:30 UTC | May 13, 19:45 UTC | 1h 15m |
| 2026-05-13 | BJC → BJC | May 13, 16:15 UTC | May 13, 17:05 UTC | 50m |
| 2026-05-13 | BJC → BJC | May 13, 02:45 UTC | May 13, 05:10 UTC | 2h 25m |
| 2026-05-12 | BJC → BJC | May 12, 23:05 UTC | May 13, 00:05 UTC | 1h 0m |
| 2026-05-12 | BJC → BJC | May 12, 20:15 UTC | May 12, 21:45 UTC | 1h 30m |
| 2026-05-12 | BJC → BJC | May 12, 18:10 UTC | May 12, 19:15 UTC | 1h 5m |
| 2026-05-12 | BJC → BJC | May 12, 16:10 UTC | May 12, 17:10 UTC | 1h 0m |
| 2026-05-12 | - | May 12, 02:45 UTC | May 12, 04:20 UTC | 1h 35m |
| 2026-05-11 | - | May 11, 22:10 UTC | May 11, 22:35 UTC | 24m |
| 2026-05-11 | BJC → BJC | May 11, 15:55 UTC | May 11, 17:00 UTC | 1h 6m |
| 2026-05-11 | BJC → BJC | May 11, 13:25 UTC | May 11, 14:35 UTC | 1h 10m |
| 2026-05-10 | BJC → BJC | May 10, 17:25 UTC | May 10, 18:45 UTC | 1h 20m |
| 2026-05-10 | BJC → BJC | May 10, 14:54 UTC | May 10, 16:14 UTC | 1h 20m |
| 2026-05-09 | BJC → BJC | May 9, 15:50 UTC | May 9, 17:30 UTC | 1h 40m |
| 2026-05-09 | BJC → BJC | May 9, 13:20 UTC | May 9, 14:00 UTC | 40m |
| 2026-05-09 | BJC → BJC | May 9, 00:45 UTC | May 9, 02:05 UTC | 1h 20m |
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 currently on the ground with its transponder active.