sensors Mode-S transponder
AD5C68
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N960CR · BOMBARDIER BD-100 Challenger 350 · operated by VILLAGE TRANSPORT CORP
- Hex
- AD5C68
- Octal
- 53256150
- Decimal
- 11,361,384
- Country
- US
- Tail
- N960CR
- Type
- CL35
- Flights observed
- 41
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address AD5C68 falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| N960CR | - | 41 | 2026-07-08 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-08 | N960CR | TEB → CGF | Jul 8, 00:50 UTC | Jul 8, 01:50 UTC | 1h 0m |
| 2026-07-07 | N960CR | - | Jul 7, 14:30 UTC | Jul 7, 15:25 UTC | 55m |
| 2026-07-04 | N960CR | - | Jul 4, 19:55 UTC | Jul 4, 21:15 UTC | 1h 20m |
| 2026-07-04 | N960CR | - | Jul 4, 16:40 UTC | Jul 4, 19:05 UTC | 2h 25m |
| 2026-06-25 | N960CR | - | Jun 25, 17:49 UTC | Jun 25, 19:09 UTC | 1h 20m |
| 2026-06-23 | N960CR | - | Jun 23, 11:54 UTC | Jun 23, 13:19 UTC | 1h 25m |
| 2026-06-21 | N960CR | - | Jun 21, 15:34 UTC | Jun 21, 18:25 UTC | 2h 50m |
| 2026-06-19 | N960CR | - | Jun 19, 13:24 UTC | Jun 19, 17:24 UTC | 4h 0m |
| 2026-06-17 | N960CR | - | Jun 17, 17:50 UTC | Jun 17, 18:35 UTC | 45m |
| 2026-06-16 | N960CR | CGF → IAD | Jun 16, 17:00 UTC | Jun 16, 17:49 UTC | 50m |
| 2026-06-15 | N960CR | - | Jun 15, 19:30 UTC | Jun 15, 20:40 UTC | 1h 10m |
| 2026-06-15 | N960CR | - | Jun 15, 12:05 UTC | Jun 15, 13:25 UTC | 1h 20m |
| 2026-06-14 | N960CR | - | Jun 14, 14:05 UTC | Jun 14, 15:40 UTC | 1h 35m |
| 2026-06-11 | N960CR | - | Jun 11, 17:10 UTC | Jun 11, 18:40 UTC | 1h 30m |
| 2026-06-03 | N960CR | - | Jun 3, 20:15 UTC | Jun 3, 21:00 UTC | 45m |
| 2026-06-02 | N960CR | - | Jun 2, 20:00 UTC | Jun 2, 20:55 UTC | 55m |
| 2026-05-25 | N960CR | BJC → CGF | May 25, 16:15 UTC | May 25, 18:40 UTC | 2h 25m |
| 2026-05-22 | N960CR | - | May 22, 13:55 UTC | May 22, 16:50 UTC | 2h 55m |
| 2026-05-21 | N960CR | OAK → CGF | May 21, 22:10 UTC | May 22, 02:15 UTC | 4h 5m |
| 2026-05-18 | N960CR | - | May 18, 11:40 UTC | May 18, 16:40 UTC | 5h 0m |
| 2026-05-17 | N960CR | - | May 17, 16:10 UTC | May 17, 19:50 UTC | 3h 40m |
| 2026-05-15 | N960CR | - | May 15, 16:05 UTC | May 15, 19:00 UTC | 2h 55m |
| 2026-05-15 | N960CR | - | May 15, 14:30 UTC | May 15, 15:30 UTC | 59m |
| 2026-05-08 | N960CR | - | May 8, 16:05 UTC | May 8, 19:20 UTC | 3h 15m |
| 2026-05-07 | N960CR | - | May 7, 15:25 UTC | May 7, 16:35 UTC | 1h 10m |
| 2026-05-07 | N960CR | - | May 7, 12:25 UTC | May 7, 13:20 UTC | 55m |
| 2026-05-06 | N960CR | - | May 6, 18:30 UTC | May 6, 19:45 UTC | 1h 15m |
| 2026-05-06 | N960CR | - | May 6, 14:20 UTC | May 6, 15:35 UTC | 1h 15m |
| 2026-04-30 | N960CR | - | Apr 30, 00:25 UTC | Apr 30, 02:35 UTC | 2h 10m |
| 2026-04-29 | N960CR | - | Apr 29, 20:35 UTC | Apr 29, 23:45 UTC | 3h 9m |
| 2026-04-29 | N960CR | - | Apr 29, 17:35 UTC | Apr 29, 19:55 UTC | 2h 20m |
| 2026-04-27 | N960CR | - | Apr 27, 14:10 UTC | Apr 27, 16:45 UTC | 2h 35m |
| 2026-04-26 | N960CR | - | Apr 26, 21:15 UTC | Apr 26, 23:30 UTC | 2h 15m |
| 2026-04-26 | N960CR | - | Apr 26, 18:00 UTC | Apr 26, 20:30 UTC | 2h 30m |
| 2026-04-26 | N960CR | - | Apr 26, 15:15 UTC | Apr 26, 16:45 UTC | 1h 30m |
| 2026-04-24 | N960CR | - | Apr 24, 13:05 UTC | Apr 24, 14:25 UTC | 1h 20m |
| 2026-04-21 | N960CR | - | Apr 21, 14:55 UTC | Apr 21, 15:55 UTC | 1h 0m |
| 2026-04-21 | N960CR | - | Apr 21, 11:20 UTC | Apr 21, 12:20 UTC | 1h 0m |
| 2026-04-17 | N960CR | - | Apr 17, 18:30 UTC | Apr 17, 19:20 UTC | 50m |
| 2026-04-17 | N960CR | - | Apr 17, 14:25 UTC | Apr 17, 15:15 UTC | 49m |
| 2026-04-12 | N960CR | - | Apr 12, 19:10 UTC | Apr 12, 19:55 UTC | 45m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the N960CR page for operator, model, and routing details .