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