Not currently tracked · last seen 6h ago
- Flights observed
- 353 showing last 50
- Avg flight time
- 2h 54m
- Typical route
- RFD → ONT
- Last seen
- 6h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-14 | - | Jul 14, 12:30 UTC | Jul 14, 13:20 UTC | 50m |
| 2026-07-14 | SAT → GDL | Jul 14, 12:29 UTC | Jul 14, 14:08 UTC | 1h 39m |
| 2026-07-14 | SDF → SAT | Jul 14, 09:00 UTC | Jul 14, 11:05 UTC | 2h 5m |
| 2026-07-14 | SAN → SDF | Jul 14, 02:31 UTC | Jul 14, 06:08 UTC | 3h 37m |
| 2026-07-14 | - | Jul 14, 02:35 UTC | Jul 14, 06:15 UTC | 3h 40m |
| 2026-07-12 | - | Jul 12, 21:10 UTC | Jul 13, 00:45 UTC | 3h 35m |
| 2026-07-12 | DEN → SDF | Jul 12, 13:30 UTC | Jul 12, 15:40 UTC | 2h 10m |
| 2026-07-12 | - | Jul 12, 00:15 UTC | Jul 12, 01:30 UTC | 1h 15m |
| 2026-07-11 | - | Jul 11, 21:30 UTC | Jul 11, 23:10 UTC | 1h 40m |
| 2026-07-11 | - | Jul 11, 12:35 UTC | Jul 11, 16:05 UTC | 3h 30m |
| 2026-07-10 | FEP → ONT | Jul 10, 07:50 UTC | Jul 10, 11:20 UTC | 3h 30m |
| 2026-07-10 | RFD → ONT | Jul 10, 07:43 UTC | Jul 10, 11:31 UTC | 3h 48m |
| 2026-07-10 | - | Jul 10, 03:40 UTC | Jul 10, 06:25 UTC | 2h 45m |
| 2026-07-10 | PHX → RFD | Jul 10, 03:22 UTC | Jul 10, 06:25 UTC | 3h 3m |
| 2026-07-09 | - | Jul 9, 21:10 UTC | Jul 9, 23:05 UTC | 1h 55m |
| 2026-07-09 | - | Jul 9, 13:35 UTC | Jul 9, 16:25 UTC | 2h 50m |
| 2026-07-09 | LAX → DFW | Jul 9, 13:31 UTC | Jul 9, 16:17 UTC | 2h 46m |
| 2026-07-09 | - | Jul 9, 08:15 UTC | Jul 9, 11:55 UTC | 3h 40m |
| 2026-07-09 | SDF → LAX | Jul 9, 08:13 UTC | Jul 9, 12:00 UTC | 3h 47m |
| 2026-07-09 | - | Jul 9, 02:30 UTC | Jul 9, 06:05 UTC | 3h 35m |
| 2026-07-09 | LGB → SDF | Jul 9, 02:33 UTC | Jul 9, 05:57 UTC | 3h 24m |
| 2026-07-08 | - | Jul 8, 19:50 UTC | Jul 8, 23:35 UTC | 3h 45m |
| 2026-07-08 | SDF → LGB | Jul 8, 19:49 UTC | Jul 8, 23:27 UTC | 3h 38m |
| 2026-07-08 | BOS → SDF | Jul 8, 13:50 UTC | Jul 8, 15:45 UTC | 1h 55m |
| 2026-07-08 | BOS → SDF | Jul 8, 13:45 UTC | Jul 8, 15:42 UTC | 1h 57m |
| 2026-07-08 | - | Jul 8, 08:35 UTC | Jul 8, 10:25 UTC | 1h 50m |
| 2026-07-08 | SDF → BOS | Jul 8, 08:32 UTC | Jul 8, 10:27 UTC | 1h 55m |
| 2026-07-08 | SJC → SDF | Jul 8, 02:25 UTC | Jul 8, 06:15 UTC | 3h 50m |
| 2026-07-08 | SJC → SDF | Jul 8, 02:22 UTC | Jul 8, 06:14 UTC | 3h 52m |
| 2026-07-07 | OAK → SJC | Jul 7, 23:50 UTC | Jul 8, 00:05 UTC | 15m |
| 2026-07-03 | - | Jul 3, 20:05 UTC | Jul 4, 00:15 UTC | 4h 10m |
| 2026-07-03 | SDF → OAK | Jul 3, 20:01 UTC | Jul 4, 00:18 UTC | 4h 17m |
| 2026-07-03 | - | Jul 3, 13:15 UTC | Jul 3, 14:10 UTC | 55m |
| 2026-07-03 | MKE → SDF | Jul 3, 13:05 UTC | Jul 3, 14:09 UTC | 1h 4m |
| 2026-07-03 | - | Jul 3, 09:20 UTC | Jul 3, 10:15 UTC | 55m |
| 2026-07-03 | SDF → MKE | Jul 3, 09:15 UTC | Jul 3, 10:13 UTC | 58m |
| 2026-07-03 | GDL → SDF | Jul 3, 01:48 UTC | Jul 3, 05:02 UTC | 3h 14m |
| 2026-07-02 | - | Jul 2, 12:05 UTC | Jul 3, 05:00 UTC | 16h 55m |
| 2026-07-02 | SAT → GDL | Jul 2, 08:55 UTC | Jul 2, 10:55 UTC | 2h 0m |
| 2026-07-02 | - | Jul 2, 01:55 UTC | Jul 2, 02:45 UTC | 50m |
| 2026-07-02 | ONT → SDF | Jul 2, 01:58 UTC | Jul 2, 05:16 UTC | 3h 18m |
| 2026-07-01 | - | Jul 1, 19:50 UTC | Jul 1, 23:30 UTC | 3h 40m |
| 2026-07-01 | RFD → ONT | Jul 1, 19:53 UTC | Jul 1, 23:27 UTC | 3h 34m |
| 2026-07-01 | - | Jul 1, 13:50 UTC | Jul 1, 16:55 UTC | 3h 5m |
| 2026-07-01 | ONT → RFD | Jul 1, 13:52 UTC | Jul 1, 16:58 UTC | 3h 6m |
| 2026-07-01 | - | Jul 1, 07:55 UTC | Jul 1, 11:30 UTC | 3h 35m |
| 2026-07-01 | RFD → ONT | Jul 1, 07:52 UTC | Jul 1, 11:23 UTC | 3h 31m |
| 2026-07-01 | - | Jul 1, 05:20 UTC | Jul 1, 06:10 UTC | 50m |
| 2026-07-01 | SDF → RFD | Jul 1, 05:22 UTC | Jul 1, 06:15 UTC | 53m |
| 2026-07-01 | MTY → SDF | Jul 1, 01:20 UTC | Jul 1, 03:50 UTC | 2h 30m |
Specifications
| Registration | N387UP |
| Operator | C C & E I LLC |
| Mode-S code | A4771B · 51073433 (octal) |
Looking for transponder-level data? View the Mode-S A4771B page for country allocation, callsign history, and ADS-B signal details.
N387UP frequently asked
Who operates N387UP?
N387UP is operated by C C & E I LLC.
What is the Mode-S transponder code for N387UP?
N387UP broadcasts on Mode-S (ICAO 24-bit) address A4771B (octal 51073433). View the transponder page.
What route does N387UP typically fly?
N387UP most frequently flies between RFD and ONT based on observed flights.
Where is N387UP right now?
N387UP is not currently being tracked; last seen 6h ago.