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