Not currently tracked · last seen 2d ago
- Flights observed
- 24
- Avg flight time
- 3h 17m
- Typical route
- COE → TUS
- Last seen
- 2d ago
Last known area
Recent flights last 24
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-06-12 | PVU → COE | Jun 12, 22:20 UTC | Jun 12, 23:45 UTC | 1h 25m |
| 2026-06-04 | COE → PVU | Jun 4, 02:30 UTC | Jun 4, 03:45 UTC | 1h 15m |
| 2026-06-03 | TUS → COE | Jun 3, 23:25 UTC | Jun 4, 01:55 UTC | 2h 30m |
| 2026-06-03 | - | Jun 3, 19:30 UTC | Jun 3, 22:40 UTC | 3h 10m |
| 2026-06-02 | - | Jun 2, 15:30 UTC | Jun 2, 18:20 UTC | 2h 50m |
| 2026-06-02 | COE → TUS | Jun 2, 12:30 UTC | Jun 2, 14:50 UTC | 2h 20m |
| 2026-05-28 | - | May 28, 18:40 UTC | May 28, 19:20 UTC | 40m |
| 2026-05-27 | - | May 27, 19:05 UTC | May 28, 19:00 UTC | 23h 55m |
| 2026-05-27 | COE → TUS | May 27, 15:00 UTC | May 27, 17:30 UTC | 2h 30m |
| 2026-05-18 | - | May 18, 23:05 UTC | May 19, 01:25 UTC | 2h 20m |
| 2026-05-18 | STP → TUS | May 18, 19:15 UTC | May 18, 22:20 UTC | 3h 5m |
| 2026-05-17 | - | May 17, 22:35 UTC | May 17, 23:15 UTC | 40m |
| 2026-05-17 | - | May 17, 15:40 UTC | May 17, 17:50 UTC | 2h 10m |
| 2026-05-17 | COE → TUS | May 17, 12:40 UTC | May 17, 14:55 UTC | 2h 15m |
| 2026-05-10 | - | May 10, 17:45 UTC | May 10, 20:14 UTC | 2h 30m |
| 2026-05-10 | - | May 10, 14:45 UTC | May 10, 16:59 UTC | 2h 15m |
| 2026-05-10 | - | May 10, 11:00 UTC | May 10, 14:00 UTC | 3h 0m |
| 2026-05-09 | - | May 9, 13:35 UTC | May 9, 18:25 UTC | 4h 50m |
| 2026-05-09 | - | May 9, 09:25 UTC | May 9, 12:40 UTC | 3h 15m |
| 2026-05-01 | - | May 1, 10:20 UTC | May 1, 11:00 UTC | 40m |
| 2026-04-27 | - | Apr 27, 16:20 UTC | Apr 27, 17:30 UTC | 1h 10m |
| 2026-04-27 | - | Apr 27, 10:10 UTC | Apr 27, 15:30 UTC | 5h 20m |
| 2026-04-26 | - | Apr 26, 18:15 UTC | Apr 26, 20:55 UTC | 2h 40m |
| 2026-04-26 | - | Apr 26, 15:15 UTC | Apr 26, 17:25 UTC | 2h 10m |
Specifications
| Registration | N1RC |
| Aircraft type | BOMBARDIER BD-100 Challenger 350 (CL35) |
| Mode-S code | A0017C · 50000574 (octal) |
Looking for transponder-level data? View the Mode-S A0017C page for country allocation, callsign history, and ADS-B signal details.
N1RC frequently asked
What type of aircraft is N1RC?
N1RC is a BOMBARDIER BD-100 Challenger 350 (ICAO type code CL35).
What is the Mode-S transponder code for N1RC?
N1RC broadcasts on Mode-S (ICAO 24-bit) address A0017C (octal 50000574). View the transponder page.
What route does N1RC typically fly?
N1RC most frequently flies between COE and TUS based on observed flights.
Where is N1RC right now?
N1RC is not currently being tracked; last seen 2d ago.