sensors Mode-S transponder
A33229
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N305CT · GULFSTREAM G500 · operated by GULFSTEAM AEROSPACE CORP
- Hex
- A33229
- Octal
- 50631051
- Decimal
- 10,695,209
- Country
- US
- Tail
- N305CT
- Type
- GA5C
- Flights observed
- 47
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address A33229 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 |
|---|---|---|---|
| N305CT | - | 47 | 2026-06-30 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-30 | N305CT | BOS → AFW | Jun 30, 20:25 UTC | Jun 30, 23:35 UTC | 3h 10m |
| 2026-06-29 | N305CT | - | Jun 29, 18:10 UTC | Jun 29, 19:05 UTC | 55m |
| 2026-06-29 | N305CT | FTW → BWI | Jun 29, 11:04 UTC | Jun 29, 13:44 UTC | 2h 40m |
| 2026-06-25 | N305CT | - | Jun 25, 07:30 UTC | Jun 25, 08:24 UTC | 55m |
| 2026-06-24 | N305CT | - | Jun 24, 21:34 UTC | Jun 25, 06:40 UTC | 9h 5m |
| 2026-06-21 | N305CT | - | Jun 21, 23:40 UTC | Jun 22, 08:35 UTC | 8h 55m |
| 2026-06-17 | N305CT | IAD → AFW | Jun 17, 17:35 UTC | Jun 17, 20:05 UTC | 2h 30m |
| 2026-06-16 | N305CT | - | Jun 16, 16:15 UTC | Jun 16, 18:25 UTC | 2h 10m |
| 2026-06-04 | N305CT | RDU → AFW | Jun 4, 23:35 UTC | Jun 5, 01:55 UTC | 2h 20m |
| 2026-06-03 | N305CT | - | Jun 3, 16:55 UTC | Jun 3, 17:40 UTC | 45m |
| 2026-06-02 | N305CT | - | Jun 2, 17:55 UTC | Jun 2, 19:25 UTC | 1h 30m |
| 2026-06-02 | N305CT | - | Jun 2, 12:15 UTC | Jun 2, 13:40 UTC | 1h 25m |
| 2026-06-01 | N305CT | - | Jun 1, 16:10 UTC | Jun 1, 18:15 UTC | 2h 5m |
| 2026-05-29 | N305CT | - | May 29, 16:30 UTC | May 29, 18:30 UTC | 2h 0m |
| 2026-05-19 | N305CT | - | May 19, 00:55 UTC | May 19, 06:20 UTC | 5h 25m |
| 2026-05-18 | N305CT | KIX → ANC | May 18, 06:01 UTC | May 18, 13:05 UTC | 7h 5m |
| 2026-05-13 | N305CT | - | May 13, 22:40 UTC | May 13, 23:45 UTC | 1h 5m |
| 2026-05-12 | N305CT | ANC → NRT | May 12, 16:35 UTC | May 12, 23:10 UTC | 6h 35m |
| 2026-05-12 | N305CT | - | May 12, 09:30 UTC | May 12, 15:25 UTC | 5h 55m |
| 2026-05-05 | N305CT | - | May 5, 02:30 UTC | May 5, 03:15 UTC | 45m |
| 2026-05-04 | N305CT | - | May 4, 21:20 UTC | May 5, 01:55 UTC | 4h 35m |
| 2026-05-04 | N305CT | - | May 4, 12:55 UTC | May 4, 14:40 UTC | 1h 45m |
| 2026-05-03 | N305CT | - | May 3, 22:34 UTC | May 3, 23:55 UTC | 1h 20m |
| 2026-05-03 | N305CT | - | May 3, 20:10 UTC | May 3, 21:50 UTC | 1h 40m |
| 2026-05-03 | N305CT | - | May 3, 18:55 UTC | May 3, 19:30 UTC | 35m |
| 2026-05-01 | N305CT | - | May 1, 19:35 UTC | May 1, 22:35 UTC | 3h 0m |
| 2026-05-01 | N305CT | - | May 1, 12:40 UTC | May 1, 14:45 UTC | 2h 5m |
| 2026-04-28 | N305CT | - | Apr 28, 17:10 UTC | Apr 28, 19:30 UTC | 2h 20m |
| 2026-04-27 | N305CT | - | Apr 27, 19:10 UTC | Apr 27, 20:55 UTC | 1h 45m |
| 2026-04-25 | N305CT | - | Apr 25, 04:05 UTC | Apr 25, 04:45 UTC | 40m |
| 2026-04-24 | N305CT | - | Apr 24, 21:45 UTC | Apr 24, 22:35 UTC | 50m |
| 2026-04-23 | N305CT | - | Apr 23, 21:50 UTC | Apr 24, 01:05 UTC | 3h 15m |
| 2026-04-23 | N305CT | - | Apr 23, 17:15 UTC | Apr 23, 20:25 UTC | 3h 10m |
| 2026-04-22 | N305CT | - | Apr 22, 22:00 UTC | Apr 22, 23:25 UTC | 1h 25m |
| 2026-04-22 | N305CT | - | Apr 22, 20:50 UTC | Apr 22, 21:25 UTC | 35m |
| 2026-04-21 | N305CT | FTW → AGS | Apr 21, 18:30 UTC | Apr 21, 20:55 UTC | 2h 25m |
| 2026-04-17 | N305CT | - | Apr 17, 01:20 UTC | Apr 17, 01:35 UTC | 15m |
| 2026-04-17 | N305CT | - | Apr 17, 00:05 UTC | Apr 17, 01:15 UTC | 1h 10m |
| 2026-04-16 | N305CT | - | Apr 16, 21:24 UTC | Apr 16, 22:45 UTC | 1h 20m |
| 2026-04-16 | N305CT | - | Apr 16, 19:15 UTC | Apr 16, 20:35 UTC | 1h 20m |
| 2026-04-16 | N305CT | - | Apr 16, 18:45 UTC | Apr 16, 19:10 UTC | 25m |
| 2026-04-16 | N305CT | - | Apr 16, 17:44 UTC | Apr 16, 18:10 UTC | 25m |
| 2026-04-16 | N305CT | - | Apr 16, 02:04 UTC | Apr 16, 03:04 UTC | 1h 0m |
| 2026-04-15 | N305CT | - | Apr 15, 23:10 UTC | Apr 15, 23:35 UTC | 25m |
| 2026-04-15 | N305CT | - | Apr 15, 22:15 UTC | Apr 15, 23:00 UTC | 45m |
| 2026-04-13 | N305CT | - | Apr 13, 23:25 UTC | Apr 13, 23:40 UTC | 15m |
| 2026-04-13 | N305CT | - | Apr 13, 20:45 UTC | Apr 13, 23:00 UTC | 2h 15m |
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 N305CT page for operator, model, and routing details .