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