sensors Mode-S transponder
A0574C
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N1209G · BOMBARDIER BD-700 Global 7000/7500
- Hex
- A0574C
- Octal
- 50053514
- Decimal
- 10,508,108
- Country
- US
- Tail
- N1209G
- Type
- GL7T
- Flights observed
- 46
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 19h ago
Last known position
Country allocation
The ICAO 24-bit address A0574C 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 |
|---|---|---|---|
| N1209G | - | 46 | 2026-07-24 |
Recent flights last 46
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | N1209G | - | Jul 24, 06:25 UTC | Jul 24, 10:55 UTC | 4h 30m |
| 2026-07-20 | N1209G | - | Jul 20, 19:45 UTC | Jul 21, 05:35 UTC | 9h 49m |
| 2026-07-20 | N1209G | BOS → JFK | Jul 20, 15:10 UTC | Jul 20, 15:55 UTC | 45m |
| 2026-07-20 | N1209G | JFK → BOS | Jul 20, 13:30 UTC | Jul 20, 14:15 UTC | 45m |
| 2026-07-17 | N1209G | - | Jul 17, 22:10 UTC | Jul 17, 22:55 UTC | 45m |
| 2026-07-17 | N1209G | JFK → BOS | Jul 17, 19:55 UTC | Jul 17, 20:35 UTC | 40m |
| 2026-07-16 | N1209G | - | Jul 16, 10:45 UTC | Jul 16, 19:14 UTC | 8h 30m |
| 2026-07-16 | N1209G | - | Jul 16, 08:00 UTC | Jul 16, 08:35 UTC | 35m |
| 2026-07-09 | N1209G | - | Jul 9, 11:10 UTC | Jul 9, 12:05 UTC | 55m |
| 2026-07-09 | N1209G | - | Jul 9, 06:25 UTC | Jul 9, 09:20 UTC | 2h 55m |
| 2026-07-05 | N1209G | LGA → OMR | Jul 5, 15:15 UTC | Jul 5, 23:45 UTC | 8h 30m |
| 2026-07-04 | N1209G | BED → LGA | Jul 4, 22:55 UTC | Jul 4, 23:30 UTC | 35m |
| 2026-06-29 | N1209G | BOS → BED | Jun 29, 04:09 UTC | Jun 29, 04:25 UTC | 15m |
| 2026-06-28 | N1209G | - | Jun 28, 19:25 UTC | Jun 29, 02:59 UTC | 7h 35m |
| 2026-06-26 | N1209G | - | Jun 26, 08:30 UTC | Jun 26, 12:39 UTC | 4h 10m |
| 2026-06-19 | N1209G | - | Jun 19, 10:14 UTC | Jun 19, 14:39 UTC | 4h 25m |
| 2026-06-17 | N1209G | - | Jun 17, 09:20 UTC | Jun 17, 14:30 UTC | 5h 10m |
| 2026-06-09 | N1209G | - | Jun 9, 14:30 UTC | Jun 9, 18:50 UTC | 4h 20m |
| 2026-06-08 | N1209G | - | Jun 8, 16:00 UTC | Jun 8, 17:50 UTC | 1h 50m |
| 2026-06-08 | N1209G | - | Jun 8, 13:45 UTC | Jun 8, 14:15 UTC | 30m |
| 2026-06-06 | N1209G | - | Jun 6, 18:19 UTC | Jun 6, 18:59 UTC | 40m |
| 2026-06-06 | N1209G | - | Jun 6, 15:10 UTC | Jun 6, 16:45 UTC | 1h 35m |
| 2026-06-03 | N1209G | ZRH → BQH | Jun 3, 12:20 UTC | Jun 3, 13:50 UTC | 1h 30m |
| 2026-06-01 | N1209G | - | Jun 1, 17:20 UTC | Jun 1, 17:50 UTC | 30m |
| 2026-05-30 | N1209G | BFI → GVA | May 30, 03:10 UTC | May 30, 12:45 UTC | 9h 35m |
| 2026-05-30 | N1209G | HIO → BFI | May 30, 01:05 UTC | May 30, 01:35 UTC | 30m |
| 2026-05-24 | N1209G | - | May 24, 15:30 UTC | May 24, 16:05 UTC | 35m |
| 2026-05-24 | N1209G | - | May 24, 05:30 UTC | May 24, 14:30 UTC | 9h 0m |
| 2026-05-21 | N1209G | - | May 21, 09:15 UTC | May 21, 09:25 UTC | 10m |
| 2026-05-13 | N1209G | - | May 13, 11:45 UTC | May 13, 16:00 UTC | 4h 15m |
| 2026-05-10 | N1209G | - | May 10, 05:20 UTC | May 10, 14:09 UTC | 8h 50m |
| 2026-05-10 | N1209G | - | May 10, 01:04 UTC | May 10, 01:34 UTC | 30m |
| 2026-05-03 | N1209G | - | May 3, 06:30 UTC | May 3, 07:00 UTC | 30m |
| 2026-05-03 | N1209G | - | May 3, 01:55 UTC | May 3, 05:45 UTC | 3h 49m |
| 2026-05-02 | N1209G | BNA → SDF | May 2, 20:40 UTC | May 2, 21:15 UTC | 35m |
| 2026-05-01 | N1209G | BFI → BNA | May 1, 19:15 UTC | May 1, 22:50 UTC | 3h 35m |
| 2026-05-01 | N1209G | HIO → BFI | May 1, 16:10 UTC | May 1, 16:35 UTC | 25m |
| 2026-04-30 | N1209G | - | Apr 30, 19:15 UTC | Apr 30, 19:55 UTC | 40m |
| 2026-04-30 | N1209G | ZRH → BLI | Apr 30, 08:30 UTC | Apr 30, 18:10 UTC | 9h 40m |
| 2026-04-28 | N1209G | - | Apr 28, 20:35 UTC | Apr 29, 05:55 UTC | 9h 20m |
| 2026-04-28 | N1209G | HIO → BFI | Apr 28, 18:45 UTC | Apr 28, 19:20 UTC | 35m |
| 2026-04-25 | N1209G | - | Apr 25, 21:05 UTC | Apr 25, 21:35 UTC | 30m |
| 2026-04-25 | N1209G | - | Apr 25, 13:00 UTC | Apr 25, 19:50 UTC | 6h 50m |
| 2026-04-24 | N1209G | - | Apr 24, 06:15 UTC | Apr 24, 12:55 UTC | 6h 40m |
| 2026-04-15 | N1209G | - | Apr 15, 07:35 UTC | Apr 15, 08:55 UTC | 1h 20m |
| 2026-04-15 | N1209G | - | Apr 15, 05:05 UTC | Apr 15, 05:50 UTC | 45m |
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 N1209G page for operator, model, and routing details .