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