sensors Mode-S transponder
A207C3
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N23SM · DASSAULT Falcon 2000 · operated by SAM & SAM3 CONSULTING LLC
- Hex
- A207C3
- Octal
- 50403703
- Decimal
- 10,618,819
- Country
- US
- Tail
- N23SM
- Type
- F2TH
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address A207C3 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 |
|---|---|---|---|
| N23SM | - | 48 | 2026-07-10 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | N23SM | - | Jul 10, 16:45 UTC | Jul 10, 18:35 UTC | 1h 50m |
| 2026-07-10 | N23SM | - | Jul 10, 13:50 UTC | Jul 10, 15:45 UTC | 1h 55m |
| 2026-07-06 | N23SM | SCF → SCF | Jul 6, 13:10 UTC | Jul 6, 18:05 UTC | 4h 55m |
| 2026-07-05 | N23SM | - | Jul 5, 21:10 UTC | Jul 5, 22:00 UTC | 50m |
| 2026-07-05 | N23SM | SCF → SDM | Jul 5, 19:35 UTC | Jul 5, 20:20 UTC | 45m |
| 2026-06-27 | N23SM | - | Jun 27, 19:05 UTC | Jun 27, 23:45 UTC | 4h 40m |
| 2026-06-27 | N23SM | - | Jun 27, 15:24 UTC | Jun 27, 16:24 UTC | 1h 0m |
| 2026-06-26 | N23SM | - | Jun 26, 19:55 UTC | Jun 26, 22:05 UTC | 2h 10m |
| 2026-06-26 | N23SM | - | Jun 26, 17:15 UTC | Jun 26, 19:04 UTC | 1h 50m |
| 2026-06-24 | N23SM | - | Jun 24, 23:14 UTC | Jun 25, 00:24 UTC | 1h 10m |
| 2026-06-24 | N23SM | - | Jun 24, 22:04 UTC | Jun 24, 22:29 UTC | 25m |
| 2026-06-24 | N23SM | - | Jun 24, 15:09 UTC | Jun 24, 17:05 UTC | 1h 55m |
| 2026-06-21 | N23SM | - | Jun 21, 18:10 UTC | Jun 21, 20:05 UTC | 1h 55m |
| 2026-06-21 | N23SM | - | Jun 21, 14:34 UTC | Jun 21, 16:25 UTC | 1h 50m |
| 2026-06-14 | N23SM | - | Jun 14, 20:00 UTC | Jun 14, 20:50 UTC | 50m |
| 2026-06-12 | N23SM | - | Jun 12, 17:35 UTC | Jun 12, 18:30 UTC | 55m |
| 2026-06-07 | N23SM | - | Jun 7, 18:10 UTC | Jun 7, 20:20 UTC | 2h 10m |
| 2026-06-07 | N23SM | - | Jun 7, 15:45 UTC | Jun 7, 17:30 UTC | 1h 45m |
| 2026-06-03 | N23SM | - | Jun 3, 02:15 UTC | Jun 3, 03:40 UTC | 1h 25m |
| 2026-06-02 | N23SM | - | Jun 2, 23:20 UTC | Jun 2, 23:35 UTC | 15m |
| 2026-06-02 | N23SM | - | Jun 2, 22:00 UTC | Jun 2, 22:10 UTC | 10m |
| 2026-06-02 | N23SM | - | Jun 2, 18:00 UTC | Jun 2, 18:15 UTC | 15m |
| 2026-06-02 | N23SM | - | Jun 2, 17:20 UTC | Jun 2, 17:30 UTC | 10m |
| 2026-06-02 | N23SM | - | Jun 2, 15:10 UTC | Jun 2, 16:50 UTC | 1h 40m |
| 2026-05-29 | N23SM | COE → SCF | May 29, 22:50 UTC | May 30, 01:00 UTC | 2h 10m |
| 2026-05-27 | N23SM | - | May 27, 16:20 UTC | May 27, 18:20 UTC | 2h 0m |
| 2026-05-25 | N23SM | - | May 25, 16:00 UTC | May 25, 22:00 UTC | 5h 59m |
| 2026-05-21 | N23SM | - | May 21, 18:05 UTC | May 21, 20:15 UTC | 2h 10m |
| 2026-05-20 | N23SM | - | May 20, 18:20 UTC | May 20, 20:10 UTC | 1h 50m |
| 2026-05-17 | N23SM | LAS → SCF | May 17, 18:10 UTC | May 17, 18:50 UTC | 40m |
| 2026-05-16 | N23SM | - | May 16, 21:00 UTC | May 16, 21:40 UTC | 40m |
| 2026-05-15 | N23SM | - | May 15, 17:15 UTC | May 15, 19:10 UTC | 1h 55m |
| 2026-05-15 | N23SM | - | May 15, 13:45 UTC | May 15, 15:40 UTC | 1h 54m |
| 2026-05-14 | N23SM | GUA → SCF | May 14, 19:50 UTC | May 15, 00:05 UTC | 4h 15m |
| 2026-05-14 | N23SM | - | May 14, 15:20 UTC | May 14, 19:00 UTC | 3h 40m |
| 2026-05-11 | N23SM | - | May 11, 18:55 UTC | May 11, 22:35 UTC | 3h 39m |
| 2026-05-11 | N23SM | - | May 11, 17:50 UTC | May 11, 18:00 UTC | 10m |
| 2026-05-11 | N23SM | - | May 11, 14:10 UTC | May 11, 17:15 UTC | 3h 6m |
| 2026-05-08 | N23SM | - | May 8, 19:15 UTC | May 8, 21:10 UTC | 1h 55m |
| 2026-05-08 | N23SM | - | May 8, 16:25 UTC | May 8, 18:30 UTC | 2h 5m |
| 2026-05-07 | N23SM | - | May 7, 20:40 UTC | May 8, 01:24 UTC | 4h 44m |
| 2026-05-04 | N23SM | - | May 4, 16:40 UTC | May 4, 20:10 UTC | 3h 31m |
| 2026-04-30 | N23SM | YYZ → SCF | Apr 30, 21:15 UTC | May 1, 01:25 UTC | 4h 10m |
| 2026-04-27 | N23SM | - | Apr 27, 16:45 UTC | Apr 27, 20:05 UTC | 3h 20m |
| 2026-04-22 | N23SM | BFL → SCF | Apr 22, 23:50 UTC | Apr 23, 00:50 UTC | 1h 0m |
| 2026-04-22 | N23SM | - | Apr 22, 17:35 UTC | Apr 22, 18:45 UTC | 1h 10m |
| 2026-04-19 | N23SM | - | Apr 19, 20:00 UTC | Apr 19, 21:00 UTC | 1h 0m |
| 2026-04-16 | N23SM | - | Apr 16, 15:35 UTC | Apr 16, 16:40 UTC | 1h 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 N23SM page for operator, model, and routing details .