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