Not currently tracked · last seen 2d ago
- Flights observed
- 31
- Avg flight time
- 55m
- Typical route
- PAO → PAO
- Last seen
- 2d ago
Last known area
Recent flights last 31
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-31 | HWD → PAO | May 31, 20:15 UTC | May 31, 20:25 UTC | 10m |
| 2026-05-31 | - | May 31, 17:50 UTC | May 31, 18:15 UTC | 25m |
| 2026-05-29 | - | May 29, 19:20 UTC | May 29, 20:00 UTC | 40m |
| 2026-05-25 | - | May 25, 19:20 UTC | May 25, 21:30 UTC | 2h 10m |
| 2026-05-22 | PAO → CLD | May 22, 21:20 UTC | May 22, 23:40 UTC | 2h 20m |
| 2026-05-22 | PAO → PAO | May 22, 16:50 UTC | May 22, 18:45 UTC | 1h 55m |
| 2026-05-22 | PAO → PAO | May 22, 00:00 UTC | May 22, 00:40 UTC | 40m |
| 2026-05-21 | - | May 21, 20:40 UTC | May 21, 21:05 UTC | 25m |
| 2026-05-21 | - | May 21, 19:50 UTC | May 21, 20:05 UTC | 15m |
| 2026-05-21 | - | May 21, 18:45 UTC | May 21, 19:15 UTC | 30m |
| 2026-05-21 | - | May 21, 17:15 UTC | May 21, 17:20 UTC | 5m |
| 2026-05-21 | HWD → HWD | May 21, 16:50 UTC | May 21, 17:05 UTC | 15m |
| 2026-05-21 | PAO → HWD | May 21, 15:30 UTC | May 21, 16:35 UTC | 1h 5m |
| 2026-05-20 | PAO → PAO | May 20, 21:55 UTC | May 21, 00:00 UTC | 2h 5m |
| 2026-05-20 | - | May 20, 18:35 UTC | May 20, 19:25 UTC | 50m |
| 2026-05-20 | - | May 20, 17:35 UTC | May 20, 18:00 UTC | 25m |
| 2026-05-19 | SQL → PAO | May 19, 21:45 UTC | May 19, 21:50 UTC | 5m |
| 2026-05-19 | - | May 19, 19:10 UTC | May 19, 19:15 UTC | 5m |
| 2026-05-19 | - | May 19, 17:55 UTC | May 19, 18:25 UTC | 30m |
| 2026-05-19 | PAO → SQL | May 19, 14:50 UTC | May 19, 16:30 UTC | 1h 40m |
| 2026-05-19 | SJC → PAO | May 19, 01:10 UTC | May 19, 01:30 UTC | 20m |
| 2026-05-18 | HWD → SJC | May 18, 23:15 UTC | May 18, 23:30 UTC | 15m |
| 2026-05-18 | PAO → HWD | May 18, 21:05 UTC | May 18, 22:30 UTC | 1h 25m |
| 2026-04-28 | - | Apr 28, 23:05 UTC | Apr 29, 00:59 UTC | 1h 55m |
| 2026-04-28 | PAO → VNY | Apr 28, 15:55 UTC | Apr 28, 17:50 UTC | 1h 55m |
| 2026-04-23 | PAO → PAO | Apr 23, 22:50 UTC | Apr 24, 00:10 UTC | 1h 20m |
| 2026-04-18 | VNY → PAO | Apr 18, 22:15 UTC | Apr 19, 00:00 UTC | 1h 45m |
| 2026-04-18 | PAO → VNY | Apr 18, 16:50 UTC | Apr 18, 18:45 UTC | 1h 55m |
| 2026-04-15 | HWD → PAO | Apr 15, 22:20 UTC | Apr 15, 22:30 UTC | 10m |
| 2026-04-15 | - | Apr 15, 21:55 UTC | Apr 15, 22:15 UTC | 20m |
| 2026-04-15 | PAO → HWD | Apr 15, 21:20 UTC | Apr 15, 21:40 UTC | 20m |
Specifications
| Registration | N526ZK |
| Operator | PYNG LLC |
| Mode-S code | A6A181 · 51520601 (octal) |
Looking for transponder-level data? View the Mode-S A6A181 page for country allocation, callsign history, and ADS-B signal details.
N526ZK frequently asked
Who operates N526ZK?
N526ZK is operated by PYNG LLC.
What is the Mode-S transponder code for N526ZK?
N526ZK broadcasts on Mode-S (ICAO 24-bit) address A6A181 (octal 51520601). View the transponder page.
What route does N526ZK typically fly?
N526ZK most frequently flies between PAO and PAO based on observed flights.
Where is N526ZK right now?
N526ZK is not currently being tracked; last seen 2d ago.