sensors Mode-S transponder
A44660
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N375AB · BOMBARDIER BD-100 Challenger 350 · operated by BOMBARDIER AEROSPACE CORP
- Hex
- A44660
- Octal
- 51043140
- Decimal
- 10,765,920
- Country
- US
- Tail
- N375AB
- Type
- CL35
- Flights observed
- 58
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address A44660 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-19 | FTD375 | - | Jun 19, 11:59 UTC | Jun 19, 14:15 UTC | 2h 15m |
| 2026-06-17 | FTD375 | - | Jun 17, 15:40 UTC | Jun 17, 19:10 UTC | 3h 30m |
| 2026-06-15 | FTD375 | - | Jun 15, 11:30 UTC | Jun 15, 17:15 UTC | 5h 45m |
| 2026-06-14 | FTD375 | - | Jun 14, 22:50 UTC | Jun 14, 23:20 UTC | 30m |
| 2026-06-14 | FTD375 | - | Jun 14, 19:20 UTC | Jun 14, 22:05 UTC | 2h 45m |
| 2026-06-14 | FTD375 | - | Jun 14, 14:50 UTC | Jun 14, 16:10 UTC | 1h 20m |
| 2026-06-12 | FTD375 | - | Jun 12, 01:35 UTC | Jun 12, 04:20 UTC | 2h 45m |
| 2026-06-11 | FTD375 | - | Jun 11, 19:05 UTC | Jun 11, 21:15 UTC | 2h 10m |
| 2026-06-10 | FTD375 | - | Jun 10, 15:35 UTC | Jun 10, 18:15 UTC | 2h 40m |
| 2026-06-10 | FTD375 | - | Jun 10, 12:50 UTC | Jun 10, 13:40 UTC | 50m |
| 2026-06-08 | FTD375 | AUS → NUQ | Jun 8, 14:25 UTC | Jun 8, 17:45 UTC | 3h 20m |
| 2026-06-07 | FTD375 | BNA → AUS | Jun 7, 23:15 UTC | Jun 8, 01:05 UTC | 1h 50m |
| 2026-06-07 | FTD375 | - | Jun 7, 18:10 UTC | Jun 7, 19:50 UTC | 1h 40m |
| 2026-06-07 | FTD375 | ALB → PHL | Jun 7, 15:45 UTC | Jun 7, 16:35 UTC | 50m |
| 2026-06-05 | FTD375 | - | Jun 5, 16:25 UTC | Jun 5, 21:15 UTC | 4h 50m |
| 2026-06-04 | FTD375 | - | Jun 4, 19:55 UTC | Jun 4, 21:20 UTC | 1h 25m |
| 2026-06-02 | FTD375 | - | Jun 2, 21:40 UTC | Jun 2, 23:55 UTC | 2h 15m |
| 2026-06-02 | FTD375 | - | Jun 2, 20:25 UTC | Jun 2, 21:35 UTC | 1h 10m |
| 2026-06-02 | FTD375 | - | Jun 2, 17:05 UTC | Jun 2, 19:30 UTC | 2h 25m |
| 2026-05-29 | FTD375 | - | May 29, 16:20 UTC | May 29, 18:50 UTC | 2h 30m |
| 2026-05-28 | FTD375 | - | May 28, 18:55 UTC | May 28, 21:35 UTC | 2h 40m |
| 2026-05-27 | FTD375 | - | May 27, 21:30 UTC | May 27, 22:15 UTC | 45m |
| 2026-05-26 | FTD375 | TMB → DKK | May 26, 00:19 UTC | May 26, 02:55 UTC | 2h 35m |
| 2026-05-25 | FTD375 | FTW → TMB | May 25, 20:24 UTC | May 25, 23:04 UTC | 2h 40m |
| 2026-05-25 | FTD375 | - | May 25, 16:20 UTC | May 25, 18:50 UTC | 2h 30m |
| 2026-05-24 | N375AB | - | May 24, 12:45 UTC | May 24, 19:10 UTC | 6h 25m |
| 2026-05-17 | FTD375 | - | May 17, 08:25 UTC | May 17, 18:01 UTC | 9h 35m |
| 2026-05-16 | FTD375 | - | May 16, 02:15 UTC | May 16, 03:20 UTC | 1h 5m |
| 2026-05-15 | FTD375 | - | May 15, 21:35 UTC | May 15, 22:45 UTC | 1h 10m |
| 2026-05-15 | FTD375 | - | May 15, 02:20 UTC | May 15, 05:00 UTC | 2h 40m |
| 2026-05-14 | FTD375 | - | May 14, 11:50 UTC | May 14, 14:15 UTC | 2h 25m |
| 2026-05-14 | FTD375 | - | May 14, 08:40 UTC | May 14, 09:45 UTC | 1h 5m |
| 2026-05-12 | FTD375 | - | May 12, 23:10 UTC | May 13, 01:50 UTC | 2h 40m |
| 2026-05-12 | FTD375 | - | May 12, 21:15 UTC | May 12, 21:35 UTC | 20m |
| 2026-05-10 | FTD375 | - | May 10, 20:35 UTC | May 10, 21:49 UTC | 1h 15m |
| 2026-05-07 | FTD375 | - | May 7, 19:50 UTC | May 7, 21:20 UTC | 1h 30m |
| 2026-05-06 | FTD375 | ORF → BED | May 6, 19:55 UTC | May 6, 21:05 UTC | 1h 10m |
| 2026-05-06 | FTD375 | BUR → ORF | May 6, 14:15 UTC | May 6, 18:40 UTC | 4h 24m |
| 2026-05-03 | FTD375 | ORF → VNY | May 3, 16:09 UTC | May 3, 22:00 UTC | 5h 50m |
| 2026-05-02 | N375AB | IAD → ORF | May 2, 19:55 UTC | May 2, 20:30 UTC | 35m |
| 2026-05-01 | N375AB | - | May 1, 21:10 UTC | May 1, 22:35 UTC | 1h 25m |
| 2026-05-01 | N375AB | - | May 1, 15:50 UTC | May 1, 16:40 UTC | 50m |
| 2026-05-01 | N375AB | - | May 1, 12:50 UTC | May 1, 14:50 UTC | 2h 0m |
| 2026-04-30 | N375AB | - | Apr 30, 20:25 UTC | Apr 30, 23:15 UTC | 2h 50m |
| 2026-04-30 | N375AB | - | Apr 30, 14:20 UTC | Apr 30, 17:25 UTC | 3h 5m |
| 2026-04-29 | N375AB | - | Apr 29, 01:10 UTC | Apr 29, 01:45 UTC | 35m |
| 2026-04-28 | N375AB | - | Apr 28, 14:55 UTC | Apr 28, 15:40 UTC | 45m |
| 2026-04-28 | N375AB | - | Apr 28, 11:25 UTC | Apr 28, 12:00 UTC | 35m |
| 2026-04-28 | N375AB | - | Apr 28, 04:25 UTC | Apr 28, 05:05 UTC | 40m |
| 2026-04-28 | N375AB | - | Apr 28, 02:15 UTC | Apr 28, 03:25 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 N375AB page for operator, model, and routing details .