sensors Mode-S transponder
A3FB4E
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N356CE · BEECHCRAFT Super King Air 350 · operated by TEXTRON AVIATION INC
- Hex
- A3FB4E
- Octal
- 50775516
- Decimal
- 10,746,702
- Country
- US
- Tail
- N356CE
- Type
- B350
- Flights observed
- 79
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 32m ago
Current position
Country allocation
The ICAO 24-bit address A3FB4E 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 |
|---|---|---|---|
| N356CE | - | 79 | 2026-07-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | N356CE | - | Jul 18, 13:05 UTC | Jul 18, 13:30 UTC | 25m |
| 2026-07-08 | N356CE | ORL → ICT | Jul 8, 20:15 UTC | Jul 8, 23:55 UTC | 3h 40m |
| 2026-07-08 | N356CE | - | Jul 8, 16:55 UTC | Jul 8, 17:35 UTC | 40m |
| 2026-07-08 | N356CE | - | Jul 8, 16:00 UTC | Jul 8, 16:10 UTC | 10m |
| 2026-07-07 | N356CE | - | Jul 7, 19:05 UTC | Jul 7, 20:25 UTC | 1h 20m |
| 2026-07-07 | N356CE | - | Jul 7, 14:05 UTC | Jul 7, 17:55 UTC | 3h 50m |
| 2026-07-01 | N356CE | - | Jul 1, 17:50 UTC | Jul 1, 19:45 UTC | 1h 55m |
| 2026-07-01 | N356CE | - | Jul 1, 15:00 UTC | Jul 1, 17:15 UTC | 2h 15m |
| 2026-07-01 | N356CE | - | Jul 1, 11:30 UTC | Jul 1, 13:50 UTC | 2h 20m |
| 2026-06-30 | N356CE | - | Jun 30, 03:20 UTC | Jun 30, 03:55 UTC | 35m |
| 2026-06-26 | N356CE | - | Jun 26, 20:34 UTC | Jun 26, 20:55 UTC | 20m |
| 2026-06-26 | N356CE | - | Jun 26, 15:10 UTC | Jun 26, 18:39 UTC | 3h 30m |
| 2026-06-26 | N356CE | - | Jun 26, 00:15 UTC | Jun 26, 00:59 UTC | 45m |
| 2026-06-25 | N356CE | - | Jun 25, 20:30 UTC | Jun 25, 21:40 UTC | 1h 10m |
| 2026-06-25 | N356CE | ICT → DVT | Jun 25, 16:09 UTC | Jun 25, 19:39 UTC | 3h 30m |
| 2026-06-24 | N356CE | - | Jun 24, 21:04 UTC | Jun 25, 00:05 UTC | 3h 0m |
| 2026-06-24 | N356CE | - | Jun 24, 17:59 UTC | Jun 24, 20:30 UTC | 2h 30m |
| 2026-06-23 | N356CE | BEC → FOK | Jun 23, 17:50 UTC | Jun 23, 21:54 UTC | 4h 5m |
| 2026-06-19 | N356CE | - | Jun 19, 13:54 UTC | Jun 19, 17:44 UTC | 3h 50m |
| 2026-06-19 | N356CE | - | Jun 19, 00:20 UTC | Jun 19, 00:45 UTC | 25m |
| 2026-06-18 | N356CE | - | Jun 18, 16:20 UTC | Jun 18, 16:40 UTC | 20m |
| 2026-06-17 | N356CE | - | Jun 17, 21:05 UTC | Jun 17, 21:25 UTC | 20m |
| 2026-06-17 | N356CE | - | Jun 17, 20:10 UTC | Jun 17, 20:25 UTC | 15m |
| 2026-06-17 | N356CE | - | Jun 17, 18:40 UTC | Jun 17, 19:25 UTC | 45m |
| 2026-06-17 | N356CE | - | Jun 17, 14:45 UTC | Jun 17, 17:50 UTC | 3h 5m |
| 2026-06-06 | N356CE | - | Jun 6, 20:39 UTC | Jun 6, 22:44 UTC | 2h 5m |
| 2026-06-06 | N356CE | - | Jun 6, 15:30 UTC | Jun 6, 19:40 UTC | 4h 10m |
| 2026-06-05 | N356CE | - | Jun 5, 17:35 UTC | Jun 6, 17:29 UTC | 23h 55m |
| 2026-06-05 | N356CE | - | Jun 5, 17:05 UTC | Jun 6, 15:30 UTC | 22h 25m |
| 2026-06-05 | N356CE | - | Jun 5, 14:15 UTC | Jun 5, 14:25 UTC | 10m |
| 2026-06-03 | N356CE | - | Jun 3, 13:05 UTC | Jun 3, 13:20 UTC | 15m |
| 2026-06-02 | N356CE | - | Jun 2, 21:15 UTC | Jun 2, 21:30 UTC | 15m |
| 2026-06-02 | N356CE | - | Jun 2, 17:30 UTC | Jun 2, 17:40 UTC | 10m |
| 2026-06-01 | N356CE | - | Jun 1, 20:00 UTC | Jun 2, 17:40 UTC | 21h 40m |
| 2026-06-01 | N356CE | - | Jun 1, 16:30 UTC | Jun 1, 20:15 UTC | 3h 45m |
| 2026-05-29 | N356CE | - | May 29, 18:45 UTC | May 29, 19:20 UTC | 35m |
| 2026-05-28 | N356CE | - | May 28, 20:05 UTC | May 28, 20:40 UTC | 35m |
| 2026-05-28 | N356CE | - | May 28, 15:45 UTC | May 28, 16:20 UTC | 35m |
| 2026-05-26 | N356CE | - | May 26, 19:10 UTC | May 26, 21:14 UTC | 2h 5m |
| 2026-05-24 | N356CE | - | May 24, 20:05 UTC | May 24, 20:25 UTC | 20m |
| 2026-05-22 | N356CE | - | May 22, 11:40 UTC | May 22, 12:25 UTC | 45m |
| 2026-05-21 | N356CE | - | May 21, 17:00 UTC | May 21, 17:35 UTC | 35m |
| 2026-05-21 | N356CE | - | May 21, 15:10 UTC | May 21, 15:40 UTC | 30m |
| 2026-05-21 | N356CE | - | May 21, 11:25 UTC | May 21, 12:00 UTC | 35m |
| 2026-05-20 | N356CE | - | May 20, 20:40 UTC | May 20, 20:55 UTC | 15m |
| 2026-05-20 | N356CE | - | May 20, 14:30 UTC | May 20, 14:50 UTC | 20m |
| 2026-05-19 | N356CE | - | May 19, 12:00 UTC | May 19, 14:20 UTC | 2h 20m |
| 2026-05-17 | N356CE | - | May 17, 13:31 UTC | May 17, 17:20 UTC | 3h 50m |
| 2026-05-14 | N356CE | - | May 14, 19:00 UTC | May 14, 19:45 UTC | 45m |
| 2026-05-14 | N356CE | - | May 14, 12:15 UTC | May 14, 14:50 UTC | 2h 35m |
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 N356CE page for operator, model, and routing details .