sensors Mode-S transponder
A5C053
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N47SB · CESSNA 680 Citation Latitude · operated by WABASH AVIATION LLC
- Hex
- A5C053
- Octal
- 51340123
- Decimal
- 10,862,675
- Country
- US
- Tail
- N47SB
- Type
- C68A
- Flights observed
- 54
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 26, 22:45 UTC
Last known position
Country allocation
The ICAO 24-bit address A5C053 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 |
|---|---|---|---|
| N47SB | - | 54 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N47SB | - | Jul 26, 20:40 UTC | Jul 26, 22:45 UTC | 2h 5m |
| 2026-07-24 | N47SB | FLL → BED | Jul 24, 18:45 UTC | Jul 24, 21:50 UTC | 3h 5m |
| 2026-07-15 | N47SB | - | Jul 15, 23:55 UTC | Jul 16, 02:40 UTC | 2h 45m |
| 2026-07-15 | N47SB | - | Jul 15, 20:15 UTC | Jul 15, 22:50 UTC | 2h 35m |
| 2026-07-15 | N47SB | - | Jul 15, 19:20 UTC | Jul 15, 19:30 UTC | 10m |
| 2026-07-08 | N47SB | - | Jul 8, 17:15 UTC | Jul 8, 18:55 UTC | 1h 40m |
| 2026-07-08 | N47SB | - | Jul 8, 15:45 UTC | Jul 8, 15:55 UTC | 10m |
| 2026-07-07 | N47SB | - | Jul 7, 14:55 UTC | Jul 7, 16:35 UTC | 1h 40m |
| 2026-07-05 | N47SB | - | Jul 5, 20:00 UTC | Jul 5, 21:55 UTC | 1h 55m |
| 2026-07-05 | N47SB | - | Jul 5, 19:10 UTC | Jul 5, 19:20 UTC | 10m |
| 2026-07-02 | N47SB | - | Jul 2, 15:30 UTC | Jul 2, 16:35 UTC | 1h 5m |
| 2026-07-02 | N47SB | - | Jul 2, 14:20 UTC | Jul 2, 15:00 UTC | 40m |
| 2026-06-27 | N47SB | - | Jun 27, 14:45 UTC | Jun 27, 18:39 UTC | 3h 55m |
| 2026-06-18 | N47SB | - | Jun 18, 17:50 UTC | Jun 18, 20:10 UTC | 2h 20m |
| 2026-06-16 | N47SB | - | Jun 16, 14:09 UTC | Jun 16, 17:10 UTC | 3h 0m |
| 2026-06-14 | N47SB | - | Jun 14, 11:00 UTC | Jun 14, 14:30 UTC | 3h 30m |
| 2026-06-10 | N47SB | - | Jun 10, 20:25 UTC | Jun 10, 22:50 UTC | 2h 25m |
| 2026-06-09 | N47SB | - | Jun 9, 12:45 UTC | Jun 9, 15:30 UTC | 2h 45m |
| 2026-06-06 | N47SB | - | Jun 6, 20:25 UTC | Jun 6, 21:50 UTC | 1h 25m |
| 2026-06-06 | N47SB | - | Jun 6, 18:14 UTC | Jun 6, 19:50 UTC | 1h 35m |
| 2026-06-04 | N47SB | - | Jun 4, 15:25 UTC | Jun 4, 17:00 UTC | 1h 35m |
| 2026-06-04 | N47SB | - | Jun 4, 13:00 UTC | Jun 4, 14:40 UTC | 1h 40m |
| 2026-05-31 | N47SB | TPA → FLL | May 31, 19:00 UTC | May 31, 19:40 UTC | 40m |
| 2026-05-31 | N47SB | - | May 31, 13:45 UTC | May 31, 14:20 UTC | 35m |
| 2026-05-19 | N47SB | - | May 19, 14:40 UTC | May 19, 15:25 UTC | 45m |
| 2026-05-14 | N47SB | - | May 14, 12:50 UTC | May 14, 13:30 UTC | 40m |
| 2026-05-14 | N47SB | - | May 14, 10:40 UTC | May 14, 11:15 UTC | 35m |
| 2026-05-13 | N47SB | - | May 13, 20:00 UTC | May 13, 20:40 UTC | 40m |
| 2026-05-12 | N47SB | - | May 12, 12:00 UTC | May 12, 12:35 UTC | 35m |
| 2026-05-10 | N47SB | GRB → FLL | May 10, 15:45 UTC | May 10, 18:45 UTC | 3h 0m |
| 2026-05-10 | N47SB | - | May 10, 11:15 UTC | May 10, 14:20 UTC | 3h 5m |
| 2026-05-06 | N47SB | - | May 6, 21:40 UTC | May 7, 00:00 UTC | 2h 20m |
| 2026-05-05 | N47SB | - | May 5, 20:50 UTC | May 5, 21:20 UTC | 30m |
| 2026-05-04 | N47SB | - | May 4, 21:25 UTC | May 4, 22:05 UTC | 40m |
| 2026-05-04 | N47SB | - | May 4, 11:25 UTC | May 4, 14:20 UTC | 2h 55m |
| 2026-05-03 | N47SB | - | May 3, 14:20 UTC | May 3, 14:40 UTC | 20m |
| 2026-05-03 | N47SB | - | May 3, 12:50 UTC | May 3, 13:15 UTC | 25m |
| 2026-04-28 | N47SB | - | Apr 28, 21:15 UTC | Apr 28, 21:35 UTC | 20m |
| 2026-04-28 | N47SB | - | Apr 28, 19:45 UTC | Apr 28, 20:00 UTC | 15m |
| 2026-04-26 | N47SB | - | Apr 26, 19:30 UTC | Apr 26, 21:10 UTC | 1h 40m |
| 2026-04-24 | N47SB | - | Apr 24, 16:20 UTC | Apr 24, 18:15 UTC | 1h 55m |
| 2026-04-23 | N47SB | - | Apr 23, 17:35 UTC | Apr 23, 21:15 UTC | 3h 39m |
| 2026-04-19 | N47SB | - | Apr 19, 21:45 UTC | Apr 19, 22:10 UTC | 25m |
| 2026-04-19 | N47SB | - | Apr 19, 20:25 UTC | Apr 19, 20:40 UTC | 15m |
| 2026-04-17 | N47SB | - | Apr 17, 17:05 UTC | Apr 17, 17:15 UTC | 10m |
| 2026-04-15 | N47SB | - | Apr 15, 21:55 UTC | Apr 15, 22:15 UTC | 20m |
| 2026-04-15 | N47SB | - | Apr 15, 20:40 UTC | Apr 15, 21:00 UTC | 20m |
| 2026-04-13 | N47SB | - | Apr 13, 16:15 UTC | Apr 13, 17:05 UTC | 50m |
| 2026-04-13 | N47SB | - | Apr 13, 15:50 UTC | Apr 13, 17:05 UTC | 1h 15m |
| 2026-04-13 | N47SB | - | Apr 13, 13:10 UTC | Apr 13, 16:15 UTC | 3h 5m |
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 N47SB page for operator, model, and routing details .