sensors Mode-S transponder
A5E47F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N479WB · BEECH 300 Super King Air · operated by FLYGUYS AVIATION II LLC
- Hex
- A5E47F
- Octal
- 51362177
- Decimal
- 10,871,935
- Country
- US
- Tail
- N479WB
- Type
- BE30
- Flights observed
- 63
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 13d ago
Last known position
Country allocation
The ICAO 24-bit address A5E47F 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 |
|---|---|---|---|
| N479WB | - | 63 | 2026-07-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | N479WB | - | Jul 23, 20:55 UTC | Jul 23, 21:35 UTC | 40m |
| 2026-07-23 | N479WB | - | Jul 23, 18:15 UTC | Jul 23, 19:00 UTC | 45m |
| 2026-07-18 | N479WB | - | Jul 18, 21:10 UTC | Jul 18, 22:10 UTC | 1h 0m |
| 2026-07-18 | N479WB | - | Jul 18, 17:10 UTC | Jul 18, 18:40 UTC | 1h 30m |
| 2026-07-18 | N479WB | - | Jul 18, 14:30 UTC | Jul 18, 15:15 UTC | 45m |
| 2026-07-15 | N479WB | - | Jul 15, 22:10 UTC | Jul 15, 22:50 UTC | 40m |
| 2026-07-15 | N479WB | - | Jul 15, 19:30 UTC | Jul 15, 20:15 UTC | 45m |
| 2026-07-12 | N479WB | - | Jul 12, 23:00 UTC | Jul 13, 02:25 UTC | 3h 25m |
| 2026-07-12 | N479WB | - | Jul 12, 18:15 UTC | Jul 12, 19:45 UTC | 1h 30m |
| 2026-07-12 | N479WB | - | Jul 12, 15:15 UTC | Jul 12, 16:01 UTC | 45m |
| 2026-07-09 | N479WB | - | Jul 9, 20:35 UTC | Jul 9, 21:15 UTC | 40m |
| 2026-07-09 | N479WB | - | Jul 9, 17:30 UTC | Jul 9, 19:25 UTC | 1h 55m |
| 2026-07-08 | N479WB | - | Jul 8, 20:50 UTC | Jul 8, 22:40 UTC | 1h 50m |
| 2026-07-07 | N479WB | - | Jul 7, 15:35 UTC | Jul 7, 16:55 UTC | 1h 20m |
| 2026-07-07 | N479WB | - | Jul 7, 13:50 UTC | Jul 7, 14:55 UTC | 1h 5m |
| 2026-07-02 | N479WB | - | Jul 2, 20:00 UTC | Jul 3, 06:00 UTC | 10h 0m |
| 2026-07-02 | N479WB | - | Jul 2, 18:15 UTC | Jul 2, 18:25 UTC | 10m |
| 2026-06-23 | N479WB | - | Jun 23, 23:34 UTC | Jun 24, 02:15 UTC | 2h 40m |
| 2026-06-19 | N479WB | - | Jun 19, 18:20 UTC | Jun 19, 20:59 UTC | 2h 40m |
| 2026-06-19 | N479WB | - | Jun 19, 15:34 UTC | Jun 19, 17:39 UTC | 2h 5m |
| 2026-06-16 | N479WB | - | Jun 16, 13:30 UTC | Jun 16, 17:24 UTC | 3h 55m |
| 2026-06-15 | N479WB | - | Jun 15, 15:15 UTC | Jun 15, 15:59 UTC | 45m |
| 2026-06-15 | N479WB | - | Jun 15, 13:25 UTC | Jun 15, 14:10 UTC | 45m |
| 2026-06-10 | N479WB | - | Jun 10, 21:10 UTC | Jun 10, 21:45 UTC | 35m |
| 2026-06-10 | N479WB | - | Jun 10, 14:25 UTC | Jun 10, 15:10 UTC | 45m |
| 2026-06-07 | N479WB | - | Jun 7, 20:25 UTC | Jun 7, 21:30 UTC | 1h 5m |
| 2026-06-07 | N479WB | - | Jun 7, 18:05 UTC | Jun 7, 19:10 UTC | 1h 5m |
| 2026-06-05 | N479WB | - | Jun 5, 17:45 UTC | Jun 5, 18:45 UTC | 1h 0m |
| 2026-06-05 | N479WB | - | Jun 5, 16:30 UTC | Jun 5, 17:10 UTC | 40m |
| 2026-06-03 | N479WB | - | Jun 3, 20:50 UTC | Jun 3, 22:00 UTC | 1h 10m |
| 2026-06-02 | N479WB | - | Jun 2, 21:30 UTC | Jun 3, 00:05 UTC | 2h 35m |
| 2026-06-01 | N479WB | - | Jun 1, 12:00 UTC | Jun 1, 14:55 UTC | 2h 55m |
| 2026-05-31 | N479WB | - | May 31, 19:15 UTC | May 31, 21:15 UTC | 2h 0m |
| 2026-05-31 | N479WB | - | May 31, 16:25 UTC | May 31, 18:05 UTC | 1h 40m |
| 2026-05-25 | N479WB | - | May 25, 16:05 UTC | May 25, 19:54 UTC | 3h 49m |
| 2026-05-24 | N479WB | - | May 24, 03:05 UTC | May 24, 04:45 UTC | 1h 40m |
| 2026-05-23 | N479WB | - | May 23, 20:55 UTC | May 23, 22:50 UTC | 1h 55m |
| 2026-05-17 | N479WB | - | May 17, 19:20 UTC | May 17, 20:15 UTC | 55m |
| 2026-05-14 | N479WB | - | May 14, 22:30 UTC | May 14, 23:45 UTC | 1h 15m |
| 2026-05-14 | N479WB | - | May 14, 20:45 UTC | May 14, 21:40 UTC | 55m |
| 2026-05-14 | N479WB | - | May 14, 16:40 UTC | May 14, 16:55 UTC | 15m |
| 2026-05-13 | N479WB | - | May 13, 12:35 UTC | May 13, 14:45 UTC | 2h 10m |
| 2026-05-12 | N479WB | - | May 12, 16:00 UTC | May 12, 17:00 UTC | 1h 0m |
| 2026-05-11 | N479WB | - | May 11, 21:20 UTC | May 11, 22:35 UTC | 1h 14m |
| 2026-05-06 | N479WB | - | May 6, 18:05 UTC | May 6, 18:45 UTC | 40m |
| 2026-05-06 | N479WB | - | May 6, 15:50 UTC | May 6, 16:40 UTC | 50m |
| 2026-05-03 | N479WB | - | May 3, 23:20 UTC | May 4, 00:00 UTC | 40m |
| 2026-05-03 | N479WB | - | May 3, 21:00 UTC | May 3, 21:50 UTC | 50m |
| 2026-04-29 | N479WB | - | Apr 29, 20:00 UTC | Apr 29, 21:10 UTC | 1h 10m |
| 2026-04-28 | N479WB | - | Apr 28, 20:35 UTC | Apr 28, 21:45 UTC | 1h 10m |
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 N479WB page for operator, model, and routing details .