sensors Mode-S transponder
A29AF3
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N267WA · GULFSTREAM 5 · operated by GLOBAL AIRCRAFT LLC
- Hex
- A29AF3
- Octal
- 50515363
- Decimal
- 10,656,499
- Country
- US
- Tail
- N267WA
- Type
- GLF5
- Flights observed
- 52
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 7d ago
Last known position
Country allocation
The ICAO 24-bit address A29AF3 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 |
|---|---|---|---|
| N267WA | - | 52 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | N267WA | - | Jul 24, 06:50 UTC | Jul 24, 09:25 UTC | 2h 35m |
| 2026-07-21 | N267WA | - | Jul 21, 13:10 UTC | Jul 21, 20:00 UTC | 6h 50m |
| 2026-07-21 | N267WA | - | Jul 21, 11:15 UTC | Jul 21, 12:15 UTC | 1h 0m |
| 2026-07-19 | N267WA | - | Jul 19, 21:10 UTC | Jul 19, 23:25 UTC | 2h 15m |
| 2026-07-19 | N267WA | STP → USA | Jul 19, 19:00 UTC | Jul 19, 20:40 UTC | 1h 40m |
| 2026-07-19 | N267WA | STP → STP | Jul 19, 13:55 UTC | Jul 19, 17:45 UTC | 3h 50m |
| 2026-07-17 | N267WA | - | Jul 17, 17:30 UTC | Jul 17, 18:50 UTC | 1h 20m |
| 2026-07-17 | N267WA | - | Jul 17, 15:40 UTC | Jul 17, 16:10 UTC | 30m |
| 2026-07-17 | N267WA | - | Jul 17, 13:40 UTC | Jul 17, 14:55 UTC | 1h 15m |
| 2026-07-16 | N267WA | - | Jul 16, 14:20 UTC | Jul 16, 16:19 UTC | 2h 0m |
| 2026-07-16 | N267WA | STP → USA | Jul 16, 10:50 UTC | Jul 16, 12:44 UTC | 1h 55m |
| 2026-07-12 | N267WA | LAS → STP | Jul 12, 22:55 UTC | Jul 13, 01:30 UTC | 2h 35m |
| 2026-07-12 | N267WA | - | Jul 12, 21:15 UTC | Jul 12, 21:50 UTC | 35m |
| 2026-07-10 | N267WA | - | Jul 10, 23:30 UTC | Jul 10, 23:55 UTC | 25m |
| 2026-07-10 | N267WA | STP → LAS | Jul 10, 19:45 UTC | Jul 10, 22:30 UTC | 2h 45m |
| 2026-06-27 | N267WA | - | Jun 27, 02:04 UTC | Jun 27, 04:39 UTC | 2h 35m |
| 2026-06-26 | N267WA | - | Jun 26, 22:10 UTC | Jun 27, 01:19 UTC | 3h 10m |
| 2026-06-26 | N267WA | - | Jun 26, 20:29 UTC | Jun 26, 21:30 UTC | 1h 0m |
| 2026-06-23 | N267WA | - | Jun 23, 03:29 UTC | Jun 23, 05:20 UTC | 1h 50m |
| 2026-06-23 | N267WA | - | Jun 23, 01:04 UTC | Jun 23, 02:49 UTC | 1h 45m |
| 2026-06-21 | N267WA | - | Jun 21, 01:45 UTC | Jun 21, 04:30 UTC | 2h 45m |
| 2026-06-20 | N267WA | - | Jun 20, 23:45 UTC | Jun 21, 00:10 UTC | 25m |
| 2026-06-20 | N267WA | - | Jun 20, 00:39 UTC | Jun 20, 00:59 UTC | 20m |
| 2026-06-19 | N267WA | - | Jun 19, 20:29 UTC | Jun 19, 23:44 UTC | 3h 15m |
| 2026-06-13 | N267WA | - | Jun 13, 05:50 UTC | Jun 13, 07:50 UTC | 2h 0m |
| 2026-06-08 | N267WA | - | Jun 8, 01:05 UTC | Jun 8, 02:55 UTC | 1h 50m |
| 2026-06-01 | N267WA | - | Jun 1, 02:30 UTC | Jun 1, 05:05 UTC | 2h 35m |
| 2026-06-01 | N267WA | - | Jun 1, 00:50 UTC | Jun 1, 01:20 UTC | 30m |
| 2026-05-31 | N267WA | - | May 31, 21:00 UTC | May 31, 21:05 UTC | 5m |
| 2026-05-22 | N267WA | - | May 22, 01:10 UTC | May 22, 01:15 UTC | 5m |
| 2026-05-21 | N267WA | - | May 21, 20:15 UTC | May 21, 21:00 UTC | 45m |
| 2026-05-21 | N267WA | - | May 21, 16:10 UTC | May 21, 19:10 UTC | 3h 0m |
| 2026-05-15 | N267WA | ORL → STP | May 15, 15:50 UTC | May 15, 18:35 UTC | 2h 45m |
| 2026-05-14 | N267WA | STP → ORL | May 14, 17:10 UTC | May 14, 19:40 UTC | 2h 30m |
| 2026-05-13 | N267WA | - | May 13, 02:30 UTC | May 13, 05:15 UTC | 2h 45m |
| 2026-05-12 | N267WA | - | May 12, 21:01 UTC | May 12, 23:45 UTC | 2h 45m |
| 2026-05-03 | N267WA | - | May 3, 21:39 UTC | May 4, 00:50 UTC | 3h 10m |
| 2026-05-01 | N267WA | STP → MIA | May 1, 17:35 UTC | May 1, 20:35 UTC | 3h 0m |
| 2026-04-30 | N267WA | - | Apr 30, 04:15 UTC | Apr 30, 06:45 UTC | 2h 30m |
| 2026-04-30 | N267WA | - | Apr 30, 00:35 UTC | Apr 30, 03:30 UTC | 2h 55m |
| 2026-04-28 | N267WA | - | Apr 28, 17:20 UTC | Apr 28, 19:20 UTC | 2h 0m |
| 2026-04-27 | N267WA | - | Apr 27, 21:05 UTC | Apr 27, 23:05 UTC | 2h 0m |
| 2026-04-24 | N267WA | STP → STP | Apr 24, 18:10 UTC | Apr 24, 22:15 UTC | 4h 5m |
| 2026-04-22 | N267WA | IAD → STP | Apr 22, 02:55 UTC | Apr 22, 05:10 UTC | 2h 15m |
| 2026-04-21 | N267WA | STP → IAD | Apr 21, 16:45 UTC | Apr 21, 18:35 UTC | 1h 50m |
| 2026-04-15 | N267WA | - | Apr 15, 23:10 UTC | Apr 15, 23:30 UTC | 20m |
| 2026-04-15 | N267WA | - | Apr 15, 21:10 UTC | Apr 15, 23:00 UTC | 1h 50m |
| 2026-04-15 | N267WA | - | Apr 15, 15:05 UTC | Apr 15, 16:50 UTC | 1h 45m |
| 2026-04-15 | N267WA | - | Apr 15, 13:55 UTC | Apr 15, 14:55 UTC | 59m |
| 2026-04-13 | N267WA | - | Apr 13, 22:45 UTC | Apr 13, 23:45 UTC | 1h 0m |
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 N267WA page for operator, model, and routing details .