sensors Mode-S transponder
A3203B
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N300KH · BOMBARDIER BD-100 Challenger 300 · operated by TVPX AIRCRAFT SOLUTIONS INC TRUSTEE
- Hex
- A3203B
- Octal
- 50620073
- Decimal
- 10,690,619
- Country
- US
- Tail
- N300KH
- Type
- CL30
- Flights observed
- 71
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 33m ago
Current position
Country allocation
The ICAO 24-bit address A3203B 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 |
|---|---|---|---|
| LXJ350 | - | 71 | 2026-07-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | LXJ350 | - | Jul 18, 22:00 UTC | Jul 18, 22:45 UTC | 45m |
| 2026-07-15 | LXJ350 | - | Jul 15, 13:50 UTC | Jul 15, 17:25 UTC | 3h 35m |
| 2026-07-15 | LXJ350 | - | Jul 15, 11:00 UTC | Jul 15, 12:25 UTC | 1h 25m |
| 2026-07-12 | LXJ350 | - | Jul 12, 21:25 UTC | Jul 13, 00:01 UTC | 2h 35m |
| 2026-07-10 | LXJ350 | - | Jul 10, 13:20 UTC | Jul 10, 15:50 UTC | 2h 30m |
| 2026-07-09 | LXJ350 | - | Jul 9, 20:10 UTC | Jul 9, 21:40 UTC | 1h 30m |
| 2026-07-09 | LXJ350 | - | Jul 9, 18:40 UTC | Jul 9, 19:25 UTC | 45m |
| 2026-07-09 | LXJ350 | - | Jul 9, 15:10 UTC | Jul 9, 16:05 UTC | 55m |
| 2026-07-09 | LXJ350 | - | Jul 9, 11:50 UTC | Jul 9, 13:15 UTC | 1h 25m |
| 2026-07-06 | LXJ350 | - | Jul 6, 00:30 UTC | Jul 6, 01:25 UTC | 55m |
| 2026-07-05 | LXJ350 | - | Jul 5, 18:35 UTC | Jul 5, 19:15 UTC | 40m |
| 2026-07-05 | LXJ350 | PWK → TEB | Jul 5, 15:55 UTC | Jul 5, 17:40 UTC | 1h 45m |
| 2026-07-02 | LXJ350 | - | Jul 2, 18:40 UTC | Jul 2, 19:20 UTC | 40m |
| 2026-07-02 | LXJ350 | - | Jul 2, 16:05 UTC | Jul 2, 17:25 UTC | 1h 20m |
| 2026-07-02 | LXJ350 | - | Jul 2, 14:05 UTC | Jul 2, 14:25 UTC | 20m |
| 2026-07-01 | LXJ350 | - | Jul 1, 15:55 UTC | Jul 1, 19:10 UTC | 3h 15m |
| 2026-06-28 | LXJ350 | - | Jun 28, 13:19 UTC | Jun 28, 17:10 UTC | 3h 50m |
| 2026-06-27 | LXJ350 | TEB → HPN | Jun 27, 19:34 UTC | Jun 27, 19:45 UTC | 10m |
| 2026-06-22 | LXJ350 | - | Jun 22, 14:49 UTC | Jun 22, 19:34 UTC | 4h 45m |
| 2026-06-21 | LXJ350 | - | Jun 21, 21:05 UTC | Jun 21, 21:29 UTC | 25m |
| 2026-06-21 | LXJ350 | - | Jun 21, 18:50 UTC | Jun 21, 20:14 UTC | 1h 25m |
| 2026-06-20 | LXJ350 | SFO → PWT | Jun 20, 22:20 UTC | Jun 20, 23:55 UTC | 1h 35m |
| 2026-06-20 | LXJ350 | - | Jun 20, 18:45 UTC | Jun 20, 19:24 UTC | 40m |
| 2026-06-18 | LXJ350 | - | Jun 18, 12:55 UTC | Jun 18, 19:15 UTC | 6h 20m |
| 2026-06-16 | LXJ350 | RKV → TEB | Jun 16, 15:09 UTC | Jun 16, 20:30 UTC | 5h 21m |
| 2026-06-13 | LXJ350 | - | Jun 13, 12:15 UTC | Jun 13, 12:35 UTC | 20m |
| 2026-06-10 | LXJ350 | - | Jun 10, 01:35 UTC | Jun 10, 07:10 UTC | 5h 35m |
| 2026-06-07 | LXJ350 | - | Jun 7, 22:35 UTC | Jun 8, 00:45 UTC | 2h 10m |
| 2026-05-31 | LXJ350 | - | May 31, 20:45 UTC | May 31, 21:50 UTC | 1h 5m |
| 2026-05-28 | LXJ350 | - | May 28, 13:00 UTC | May 28, 15:15 UTC | 2h 15m |
| 2026-05-27 | LXJ350 | - | May 27, 01:54 UTC | May 27, 03:59 UTC | 2h 5m |
| 2026-05-26 | LXJ350 | - | May 26, 18:19 UTC | May 26, 20:20 UTC | 2h 0m |
| 2026-05-25 | LXJ350 | - | May 25, 22:55 UTC | May 26, 01:14 UTC | 2h 20m |
| 2026-05-25 | LXJ350 | - | May 25, 19:25 UTC | May 25, 22:15 UTC | 2h 50m |
| 2026-05-25 | LXJ350 | - | May 25, 17:55 UTC | May 25, 18:20 UTC | 25m |
| 2026-05-22 | LXJ350 | - | May 22, 14:20 UTC | May 22, 17:35 UTC | 3h 15m |
| 2026-05-21 | LXJ350 | - | May 21, 18:10 UTC | May 21, 19:15 UTC | 1h 5m |
| 2026-05-21 | LXJ350 | - | May 21, 15:25 UTC | May 21, 17:10 UTC | 1h 45m |
| 2026-05-21 | LXJ350 | - | May 21, 11:25 UTC | May 21, 13:55 UTC | 2h 30m |
| 2026-05-20 | LXJ350 | SBA → TEB | May 20, 16:35 UTC | May 20, 21:45 UTC | 5h 10m |
| 2026-05-19 | LXJ350 | BUR → SBA | May 19, 21:50 UTC | May 19, 22:10 UTC | 20m |
| 2026-05-15 | LXJ350 | TEB → BUR | May 15, 14:30 UTC | May 15, 19:45 UTC | 5h 14m |
| 2026-05-11 | LXJ350 | RDU → TEB | May 11, 13:45 UTC | May 11, 14:45 UTC | 1h 0m |
| 2026-05-10 | LXJ350 | TEB → RDU | May 10, 16:30 UTC | May 10, 17:40 UTC | 1h 10m |
| 2026-05-10 | LXJ350 | - | May 10, 13:40 UTC | May 10, 15:05 UTC | 1h 25m |
| 2026-05-08 | LXJ350 | - | May 8, 17:20 UTC | May 8, 20:15 UTC | 2h 55m |
| 2026-05-02 | LXJ350 | LAS → SCF | May 2, 21:30 UTC | May 2, 22:10 UTC | 40m |
| 2026-05-02 | LXJ350 | CCR → LAS | May 2, 00:10 UTC | May 2, 01:15 UTC | 1h 5m |
| 2026-05-01 | LXJ350 | - | May 1, 21:05 UTC | May 1, 22:05 UTC | 1h 0m |
| 2026-05-01 | LXJ350 | SMF → LGB | May 1, 19:05 UTC | May 1, 20:10 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 N300KH page for operator, model, and routing details .