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