sensors Mode-S transponder
A3A1DA
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N333KE · DASSAULT Falcon 100 · operated by FALCONMITCH INC
- Hex
- A3A1DA
- Octal
- 50720732
- Decimal
- 10,723,802
- Country
- US
- Tail
- N333KE
- Type
- FA10
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- Jul 26, 20:40 UTC
Last known position
Country allocation
The ICAO 24-bit address A3A1DA 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 |
|---|---|---|---|
| N333KE | - | 48 | 2026-07-26 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | N333KE | - | Jul 26, 19:10 UTC | Jul 26, 20:40 UTC | 1h 30m |
| 2026-07-24 | N333KE | - | Jul 24, 18:30 UTC | Jul 24, 20:25 UTC | 1h 55m |
| 2026-07-21 | N333KE | - | Jul 21, 21:25 UTC | Jul 21, 22:05 UTC | 40m |
| 2026-07-20 | N333KE | - | Jul 20, 13:35 UTC | Jul 20, 14:15 UTC | 40m |
| 2026-07-08 | N333KE | - | Jul 8, 20:35 UTC | Jul 8, 21:40 UTC | 1h 5m |
| 2026-07-08 | N333KE | - | Jul 8, 18:25 UTC | Jul 8, 19:30 UTC | 1h 5m |
| 2026-07-05 | N333KE | - | Jul 5, 22:25 UTC | Jul 5, 22:40 UTC | 15m |
| 2026-07-05 | N333KE | - | Jul 5, 19:00 UTC | Jul 5, 21:40 UTC | 2h 40m |
| 2026-07-02 | N333KE | - | Jul 2, 17:20 UTC | Jul 2, 20:10 UTC | 2h 50m |
| 2026-07-02 | N333KE | - | Jul 2, 15:50 UTC | Jul 2, 16:10 UTC | 20m |
| 2026-06-22 | N333KE | - | Jun 22, 21:05 UTC | Jun 22, 23:05 UTC | 2h 0m |
| 2026-06-22 | N333KE | - | Jun 22, 12:10 UTC | Jun 22, 14:29 UTC | 2h 20m |
| 2026-06-19 | N333KE | - | Jun 19, 17:39 UTC | Jun 19, 18:25 UTC | 45m |
| 2026-06-19 | N333KE | - | Jun 19, 15:54 UTC | Jun 19, 16:44 UTC | 50m |
| 2026-06-13 | N333KE | - | Jun 13, 23:30 UTC | Jun 14, 00:10 UTC | 40m |
| 2026-06-13 | N333KE | - | Jun 13, 20:15 UTC | Jun 13, 20:55 UTC | 40m |
| 2026-06-12 | N333KE | - | Jun 12, 21:35 UTC | Jun 12, 23:25 UTC | 1h 50m |
| 2026-06-12 | N333KE | - | Jun 12, 18:55 UTC | Jun 12, 21:00 UTC | 2h 5m |
| 2026-06-10 | N333KE | - | Jun 10, 19:10 UTC | Jun 10, 21:45 UTC | 2h 35m |
| 2026-06-10 | N333KE | - | Jun 10, 17:05 UTC | Jun 10, 18:20 UTC | 1h 15m |
| 2026-06-10 | N333KE | - | Jun 10, 15:55 UTC | Jun 10, 16:10 UTC | 15m |
| 2026-06-07 | N333KE | - | Jun 7, 17:05 UTC | Jun 7, 17:55 UTC | 50m |
| 2026-06-05 | N333KE | - | Jun 5, 19:15 UTC | Jun 5, 20:00 UTC | 45m |
| 2026-06-04 | N333KE | - | Jun 4, 17:00 UTC | Jun 4, 20:10 UTC | 3h 10m |
| 2026-06-03 | N333KE | - | Jun 3, 21:55 UTC | Jun 3, 22:10 UTC | 15m |
| 2026-06-03 | N333KE | - | Jun 3, 18:10 UTC | Jun 3, 18:55 UTC | 45m |
| 2026-06-02 | N333KE | - | Jun 2, 00:15 UTC | Jun 2, 00:55 UTC | 40m |
| 2026-06-01 | N333KE | - | Jun 1, 18:15 UTC | Jun 1, 20:25 UTC | 2h 10m |
| 2026-06-01 | N333KE | - | Jun 1, 17:05 UTC | Jun 1, 17:25 UTC | 20m |
| 2026-05-28 | N333KE | - | May 28, 20:00 UTC | May 28, 22:35 UTC | 2h 35m |
| 2026-05-27 | N333KE | - | May 27, 19:35 UTC | May 27, 19:55 UTC | 20m |
| 2026-05-27 | N333KE | - | May 27, 15:05 UTC | May 27, 17:35 UTC | 2h 30m |
| 2026-05-27 | N333KE | - | May 27, 14:05 UTC | May 27, 14:25 UTC | 20m |
| 2026-05-22 | N333KE | - | May 22, 14:10 UTC | May 22, 14:45 UTC | 35m |
| 2026-05-21 | N333KE | - | May 21, 16:25 UTC | May 21, 17:20 UTC | 55m |
| 2026-05-18 | N333KE | - | May 18, 15:10 UTC | May 18, 16:55 UTC | 1h 45m |
| 2026-05-16 | N333KE | - | May 16, 03:40 UTC | May 16, 05:40 UTC | 2h 0m |
| 2026-05-08 | N333KE | - | May 8, 19:10 UTC | May 8, 19:45 UTC | 35m |
| 2026-05-08 | N333KE | ADS → AUS | May 8, 17:55 UTC | May 8, 18:40 UTC | 45m |
| 2026-05-08 | N333KE | - | May 8, 17:00 UTC | May 8, 17:20 UTC | 20m |
| 2026-05-01 | N333KE | - | May 1, 18:45 UTC | May 1, 20:00 UTC | 1h 15m |
| 2026-05-01 | N333KE | - | May 1, 14:40 UTC | May 1, 15:05 UTC | 25m |
| 2026-05-01 | N333KE | - | May 1, 13:55 UTC | May 1, 14:35 UTC | 40m |
| 2026-04-27 | N333KE | - | Apr 27, 21:25 UTC | Apr 28, 00:10 UTC | 2h 45m |
| 2026-04-24 | N333KE | - | Apr 24, 15:00 UTC | Apr 24, 19:20 UTC | 4h 20m |
| 2026-04-17 | N333KE | - | Apr 17, 03:20 UTC | Apr 17, 03:40 UTC | 20m |
| 2026-04-17 | N333KE | - | Apr 17, 03:05 UTC | Apr 17, 03:15 UTC | 10m |
| 2026-04-16 | N333KE | - | Apr 16, 21:14 UTC | Apr 16, 21:55 UTC | 40m |
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 N333KE page for operator, model, and routing details .