sensors Mode-S transponder
A70016
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N550GW · GULFSTREAM 5 · operated by 711 CODY INC
- Hex
- A70016
- Octal
- 51600026
- Decimal
- 10,944,534
- Country
- US
- Tail
- N550GW
- Type
- GLF5
- Flights observed
- 61
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 19h ago
Last known position
Country allocation
The ICAO 24-bit address A70016 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 |
|---|---|---|---|
| N550GW | - | 61 | 2026-07-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | N550GW | BJC → TEB | Jul 20, 13:15 UTC | Jul 20, 17:25 UTC | 4h 10m |
| 2026-07-19 | N550GW | - | Jul 19, 12:40 UTC | Jul 19, 16:15 UTC | 3h 35m |
| 2026-07-16 | N550GW | - | Jul 16, 14:55 UTC | Jul 16, 18:05 UTC | 3h 10m |
| 2026-07-15 | N550GW | - | Jul 15, 20:35 UTC | Jul 15, 21:15 UTC | 40m |
| 2026-07-14 | N550GW | - | Jul 14, 17:25 UTC | Jul 14, 17:35 UTC | 10m |
| 2026-07-13 | N550GW | - | Jul 13, 15:45 UTC | Jul 13, 16:00 UTC | 15m |
| 2026-07-13 | N550GW | - | Jul 13, 11:20 UTC | Jul 13, 14:40 UTC | 3h 20m |
| 2026-07-12 | N550GW | - | Jul 12, 14:50 UTC | Jul 12, 18:30 UTC | 3h 40m |
| 2026-07-12 | N550GW | - | Jul 12, 09:10 UTC | Jul 12, 13:10 UTC | 4h 0m |
| 2026-07-11 | N550GW | - | Jul 11, 19:15 UTC | Jul 11, 23:50 UTC | 4h 35m |
| 2026-07-09 | N550GW | - | Jul 9, 21:05 UTC | Jul 10, 00:50 UTC | 3h 45m |
| 2026-07-09 | N550GW | - | Jul 9, 17:15 UTC | Jul 9, 20:15 UTC | 3h 0m |
| 2026-07-07 | N550GW | - | Jul 7, 19:00 UTC | Jul 7, 20:55 UTC | 1h 55m |
| 2026-07-07 | N550GW | - | Jul 7, 13:15 UTC | Jul 7, 15:40 UTC | 2h 25m |
| 2026-07-06 | N550GW | - | Jul 6, 17:35 UTC | Jul 6, 21:15 UTC | 3h 40m |
| 2026-07-06 | N550GW | - | Jul 6, 12:25 UTC | Jul 6, 16:20 UTC | 3h 55m |
| 2026-07-05 | N550GW | - | Jul 5, 16:50 UTC | Jul 5, 20:05 UTC | 3h 15m |
| 2026-07-05 | N550GW | - | Jul 5, 15:40 UTC | Jul 5, 15:50 UTC | 10m |
| 2026-07-05 | N550GW | - | Jul 5, 14:10 UTC | Jul 5, 14:20 UTC | 10m |
| 2026-07-01 | N550GW | - | Jul 1, 14:15 UTC | Jul 1, 17:45 UTC | 3h 30m |
| 2026-06-28 | N550GW | - | Jun 28, 22:39 UTC | Jun 29, 03:10 UTC | 4h 30m |
| 2026-06-27 | N550GW | - | Jun 27, 18:20 UTC | Jun 27, 19:29 UTC | 1h 10m |
| 2026-06-27 | N550GW | - | Jun 27, 17:04 UTC | Jun 27, 17:14 UTC | 10m |
| 2026-06-27 | N550GW | - | Jun 27, 12:15 UTC | Jun 27, 15:55 UTC | 3h 40m |
| 2026-06-25 | N550GW | - | Jun 25, 20:34 UTC | Jun 26, 00:55 UTC | 4h 20m |
| 2026-06-25 | N550GW | - | Jun 25, 14:14 UTC | Jun 25, 19:39 UTC | 5h 25m |
| 2026-06-18 | N550GW | - | Jun 18, 00:25 UTC | Jun 18, 02:00 UTC | 1h 35m |
| 2026-06-17 | N550GW | - | Jun 17, 20:20 UTC | Jun 17, 22:05 UTC | 1h 45m |
| 2026-06-12 | N550GW | - | Jun 12, 15:20 UTC | Jun 12, 19:45 UTC | 4h 25m |
| 2026-06-10 | N550GW | - | Jun 10, 12:55 UTC | Jun 10, 16:50 UTC | 3h 55m |
| 2026-06-08 | N550GW | - | Jun 8, 22:05 UTC | Jun 8, 23:45 UTC | 1h 40m |
| 2026-06-08 | N550GW | - | Jun 8, 12:25 UTC | Jun 8, 13:35 UTC | 1h 10m |
| 2026-06-03 | N550GW | - | Jun 3, 18:05 UTC | Jun 3, 19:25 UTC | 1h 20m |
| 2026-06-02 | N550GW | - | Jun 2, 19:50 UTC | Jun 2, 20:55 UTC | 1h 5m |
| 2026-05-29 | N550GW | - | May 29, 15:00 UTC | May 29, 18:10 UTC | 3h 10m |
| 2026-05-26 | N550GW | - | May 26, 13:34 UTC | May 26, 17:15 UTC | 3h 40m |
| 2026-05-17 | N550GW | - | May 17, 12:20 UTC | May 17, 14:01 UTC | 1h 40m |
| 2026-05-16 | N550GW | - | May 16, 14:31 UTC | May 16, 16:05 UTC | 1h 35m |
| 2026-05-15 | N550GW | - | May 15, 00:00 UTC | May 15, 00:30 UTC | 30m |
| 2026-05-14 | N550GW | - | May 14, 19:40 UTC | May 14, 22:50 UTC | 3h 10m |
| 2026-05-10 | N550GW | - | May 10, 13:40 UTC | May 10, 17:05 UTC | 3h 25m |
| 2026-05-10 | N550GW | - | May 10, 11:50 UTC | May 10, 12:19 UTC | 30m |
| 2026-05-05 | N550GW | PDK → TEB | May 5, 21:05 UTC | May 6, 01:25 UTC | 4h 20m |
| 2026-05-05 | N550GW | - | May 5, 15:55 UTC | May 5, 17:35 UTC | 1h 40m |
| 2026-04-30 | N550GW | - | Apr 30, 17:25 UTC | Apr 30, 19:00 UTC | 1h 35m |
| 2026-04-28 | N550GW | - | Apr 28, 19:10 UTC | Apr 28, 21:00 UTC | 1h 50m |
| 2026-04-25 | N550GW | - | Apr 25, 12:45 UTC | Apr 25, 15:10 UTC | 2h 25m |
| 2026-04-22 | N550GW | - | Apr 22, 21:45 UTC | Apr 22, 23:20 UTC | 1h 35m |
| 2026-04-21 | N550GW | - | Apr 21, 12:45 UTC | Apr 21, 14:15 UTC | 1h 30m |
| 2026-04-17 | N550GW | - | Apr 17, 18:20 UTC | Apr 17, 18:55 UTC | 35m |
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 N550GW page for operator, model, and routing details .