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