sensors Mode-S transponder
AD5C46
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N960BG · operated by GOKCE BARAN
- Hex
- AD5C46
- Octal
- 53256106
- Decimal
- 11,361,350
- Country
- US
- Tail
- N960BG
- Type
- SR22
- Flights observed
- 64
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address AD5C46 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 |
|---|---|---|---|
| N960BG | - | 64 | 2026-07-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-06 | N960BG | - | Jul 6, 14:30 UTC | Jul 6, 14:50 UTC | 20m |
| 2026-07-05 | N960BG | - | Jul 5, 16:15 UTC | Jul 5, 17:40 UTC | 1h 25m |
| 2026-07-04 | N960BG | - | Jul 4, 15:15 UTC | Jul 4, 16:45 UTC | 1h 30m |
| 2026-07-02 | N960BG | - | Jul 2, 23:40 UTC | Jul 3, 00:05 UTC | 25m |
| 2026-07-02 | N960BG | - | Jul 2, 22:40 UTC | Jul 2, 22:55 UTC | 15m |
| 2026-07-02 | N960BG | - | Jul 2, 21:05 UTC | Jul 2, 21:25 UTC | 20m |
| 2026-06-28 | N960BG | - | Jun 28, 19:59 UTC | Jun 28, 20:25 UTC | 25m |
| 2026-06-28 | N960BG | - | Jun 28, 14:54 UTC | Jun 28, 15:20 UTC | 25m |
| 2026-06-27 | N960BG | - | Jun 27, 23:19 UTC | Jun 27, 23:45 UTC | 25m |
| 2026-06-27 | N960BG | - | Jun 27, 21:29 UTC | Jun 27, 22:20 UTC | 50m |
| 2026-06-27 | N960BG | - | Jun 27, 19:24 UTC | Jun 27, 20:44 UTC | 1h 20m |
| 2026-06-24 | N960BG | - | Jun 24, 23:14 UTC | Jun 24, 23:59 UTC | 45m |
| 2026-06-23 | N960BG | - | Jun 23, 10:35 UTC | Jun 23, 11:35 UTC | 1h 0m |
| 2026-06-20 | N960BG | - | Jun 20, 16:14 UTC | Jun 20, 17:39 UTC | 1h 25m |
| 2026-06-20 | N960BG | - | Jun 20, 14:54 UTC | Jun 20, 15:29 UTC | 35m |
| 2026-06-09 | N960BG | - | Jun 9, 23:00 UTC | Jun 9, 23:05 UTC | 5m |
| 2026-06-09 | N960BG | - | Jun 9, 22:35 UTC | Jun 9, 22:55 UTC | 20m |
| 2026-06-09 | N960BG | - | Jun 9, 21:20 UTC | Jun 9, 21:55 UTC | 35m |
| 2026-06-08 | N960BG | - | Jun 8, 23:45 UTC | Jun 9, 00:00 UTC | 15m |
| 2026-06-07 | N960BG | - | Jun 7, 23:20 UTC | Jun 8, 00:10 UTC | 50m |
| 2026-06-07 | N960BG | - | Jun 7, 23:05 UTC | Jun 7, 23:15 UTC | 10m |
| 2026-06-07 | N960BG | - | Jun 7, 21:55 UTC | Jun 7, 22:25 UTC | 30m |
| 2026-06-07 | N960BG | - | Jun 7, 16:45 UTC | Jun 7, 18:20 UTC | 1h 35m |
| 2026-06-06 | N960BG | - | Jun 6, 22:39 UTC | Jun 6, 23:09 UTC | 30m |
| 2026-06-06 | N960BG | - | Jun 6, 19:54 UTC | Jun 6, 20:14 UTC | 20m |
| 2026-06-06 | N960BG | - | Jun 6, 18:35 UTC | Jun 6, 19:10 UTC | 35m |
| 2026-06-06 | N960BG | - | Jun 6, 15:44 UTC | Jun 6, 16:55 UTC | 1h 10m |
| 2026-06-05 | N960BG | - | Jun 5, 12:30 UTC | Jun 5, 13:00 UTC | 30m |
| 2026-06-04 | N960BG | - | Jun 4, 12:05 UTC | Jun 4, 12:50 UTC | 45m |
| 2026-05-31 | N960BG | OPF → OPF | May 31, 12:00 UTC | May 31, 13:00 UTC | 1h 0m |
| 2026-05-30 | N960BG | OPF → OPF | May 30, 17:35 UTC | May 30, 19:35 UTC | 2h 0m |
| 2026-05-30 | N960BG | - | May 30, 14:05 UTC | May 30, 16:05 UTC | 2h 0m |
| 2026-05-23 | N960BG | - | May 23, 22:30 UTC | May 23, 22:50 UTC | 20m |
| 2026-05-23 | N960BG | - | May 23, 13:30 UTC | May 23, 14:05 UTC | 35m |
| 2026-05-21 | N960BG | - | May 21, 23:30 UTC | May 22, 00:25 UTC | 55m |
| 2026-05-21 | N960BG | - | May 21, 20:50 UTC | May 21, 21:15 UTC | 25m |
| 2026-05-20 | N960BG | - | May 20, 15:05 UTC | May 20, 15:30 UTC | 25m |
| 2026-05-20 | N960BG | - | May 20, 13:25 UTC | May 20, 13:55 UTC | 30m |
| 2026-05-19 | N960BG | - | May 19, 23:35 UTC | May 20, 00:10 UTC | 35m |
| 2026-05-19 | N960BG | - | May 19, 20:50 UTC | May 19, 21:15 UTC | 25m |
| 2026-05-19 | N960BG | TMB → OPF | May 19, 15:25 UTC | May 19, 15:40 UTC | 15m |
| 2026-05-16 | N960BG | - | May 16, 20:10 UTC | May 16, 20:30 UTC | 20m |
| 2026-05-16 | N960BG | - | May 16, 18:25 UTC | May 16, 18:55 UTC | 30m |
| 2026-05-16 | N960BG | - | May 16, 16:10 UTC | May 16, 17:30 UTC | 1h 20m |
| 2026-05-10 | N960BG | - | May 10, 21:30 UTC | May 10, 22:55 UTC | 1h 25m |
| 2026-05-10 | N960BG | - | May 10, 01:04 UTC | May 10, 01:24 UTC | 20m |
| 2026-05-09 | N960BG | - | May 9, 21:19 UTC | May 9, 21:55 UTC | 35m |
| 2026-05-09 | N960BG | - | May 9, 15:15 UTC | May 9, 15:35 UTC | 20m |
| 2026-05-05 | N960BG | - | May 5, 15:30 UTC | May 5, 15:55 UTC | 25m |
| 2026-05-02 | N960BG | - | May 2, 21:35 UTC | May 2, 21:55 UTC | 20m |
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 N960BG page for operator, model, and routing details .