Not currently tracked · last seen 2d ago
- Flights observed
- 35
- Avg flight time
- 38m
- Typical route
- -
- Last seen
- 2d ago
Last known area
Recent flights last 35
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-31 | - | May 31, 17:05 UTC | May 31, 17:20 UTC | 15m |
| 2026-05-31 | - | May 31, 16:20 UTC | May 31, 16:50 UTC | 30m |
| 2026-05-30 | - | May 30, 20:35 UTC | May 30, 20:55 UTC | 20m |
| 2026-05-30 | - | May 30, 18:25 UTC | May 30, 19:55 UTC | 1h 30m |
| 2026-05-30 | - | May 30, 16:45 UTC | May 30, 18:10 UTC | 1h 25m |
| 2026-05-30 | - | May 30, 16:15 UTC | May 30, 16:35 UTC | 20m |
| 2026-05-29 | - | May 29, 05:20 UTC | May 29, 05:45 UTC | 25m |
| 2026-05-29 | - | May 29, 03:10 UTC | May 29, 04:55 UTC | 1h 45m |
| 2026-05-28 | - | May 28, 14:50 UTC | May 28, 15:55 UTC | 1h 5m |
| 2026-05-18 | - | May 18, 14:35 UTC | May 18, 15:40 UTC | 1h 5m |
| 2026-05-11 | - | May 11, 02:40 UTC | May 11, 03:45 UTC | 1h 5m |
| 2026-05-10 | - | May 10, 23:00 UTC | May 10, 23:05 UTC | 5m |
| 2026-05-10 | VDZ → VDZ | May 10, 19:09 UTC | May 10, 19:19 UTC | 10m |
| 2026-05-08 | - | May 8, 17:15 UTC | May 8, 18:40 UTC | 1h 25m |
| 2026-05-08 | - | May 8, 16:05 UTC | May 8, 16:20 UTC | 15m |
| 2026-05-07 | - | May 7, 23:59 UTC | May 8, 00:25 UTC | 25m |
| 2026-05-07 | - | May 7, 21:35 UTC | May 7, 23:05 UTC | 1h 30m |
| 2026-05-07 | - | May 7, 20:40 UTC | May 7, 21:05 UTC | 25m |
| 2026-05-06 | - | May 6, 05:10 UTC | May 6, 05:30 UTC | 20m |
| 2026-05-06 | - | May 6, 00:50 UTC | May 6, 01:10 UTC | 20m |
| 2026-05-05 | - | May 5, 23:35 UTC | May 6, 00:15 UTC | 40m |
| 2026-05-05 | - | May 5, 18:00 UTC | May 5, 20:01 UTC | 2h 0m |
| 2026-05-04 | - | May 4, 03:19 UTC | May 4, 03:40 UTC | 20m |
| 2026-05-04 | - | May 4, 00:50 UTC | May 4, 01:15 UTC | 25m |
| 2026-05-02 | - | May 2, 15:15 UTC | May 2, 15:35 UTC | 20m |
| 2026-04-29 | - | Apr 29, 22:00 UTC | Apr 29, 22:45 UTC | 45m |
| 2026-04-29 | - | Apr 29, 20:25 UTC | Apr 29, 20:35 UTC | 10m |
| 2026-04-29 | - | Apr 29, 18:45 UTC | Apr 29, 19:30 UTC | 45m |
| 2026-04-28 | - | Apr 28, 16:00 UTC | Apr 28, 16:10 UTC | 10m |
| 2026-04-27 | - | Apr 27, 22:30 UTC | Apr 27, 22:45 UTC | 15m |
| 2026-04-27 | - | Apr 27, 16:20 UTC | Apr 27, 16:35 UTC | 15m |
| 2026-04-17 | - | Apr 17, 23:30 UTC | Apr 17, 23:50 UTC | 20m |
| 2026-04-17 | - | Apr 17, 22:50 UTC | Apr 17, 23:20 UTC | 30m |
| 2026-04-17 | - | Apr 17, 21:25 UTC | Apr 17, 22:05 UTC | 40m |
| 2026-04-17 | - | Apr 17, 21:10 UTC | Apr 17, 21:20 UTC | 10m |
Specifications
| Registration | N929NX |
| Operator | N929NX LLC |
| Mode-S code | ACE0DB · 53160333 (octal) |
Looking for transponder-level data? View the Mode-S ACE0DB page for country allocation, callsign history, and ADS-B signal details.
N929NX frequently asked
Who operates N929NX?
N929NX is operated by N929NX LLC.
What is the Mode-S transponder code for N929NX?
N929NX broadcasts on Mode-S (ICAO 24-bit) address ACE0DB (octal 53160333). View the transponder page.
Where is N929NX right now?
N929NX is not currently being tracked; last seen 2d ago.