sensors Mode-S transponder
A976A5
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N709GT · BOEING 777-200LR · operated by WILMINGTON TRUST CO TRUSTEE
- Hex
- A976A5
- Octal
- 52273245
- Decimal
- 11,105,957
- Country
- US
- Tail
- N709GT
- Type
- B77L
- Flights observed
- 177
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 12d ago
Last known position
Country allocation
The ICAO 24-bit address A976A5 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| GTI3596 | - | 21 | 2026-06-30 |
| GTI3595 | - | 14 | 2026-06-29 |
| GTI3113 | Atlas Air | 14 | 2026-05-27 |
| GTI3111 | Atlas Air | 10 | 2026-05-29 |
| GTI303 | - | 10 | 2026-06-28 |
| GTI3019 | Atlas Air | 10 | 2026-06-20 |
| GTI339 | Atlas Air | 9 | 2026-05-03 |
| GTI3112 | - | 8 | 2026-05-28 |
| GTI354 | Atlas Air | 7 | 2026-06-22 |
| GTI353 | Atlas Air | 6 | 2026-06-21 |
| GTI3090 | - | 6 | 2026-06-16 |
| GTI302 | - | 6 | 2026-06-27 |
| GTI3093 | Atlas Air | 5 | 2026-06-17 |
| GTI3013 | Atlas Air | 5 | 2026-06-25 |
| GTI9345 | Atlas Air | 4 | 2026-06-03 |
| GTI346 | Atlas Air | 4 | 2026-06-11 |
| GTI3091 | Atlas Air | 4 | 2026-05-19 |
| GTI7590 | - | 3 | 2026-04-20 |
| GTI3510 | Atlas Air | 3 | 2026-04-27 |
| GTI347 | Atlas Air | 3 | 2026-06-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-01 | GTI9019 | - | Jul 1, 12:15 UTC | Jul 2, 01:00 UTC | 12h 45m |
| 2026-07-01 | GTI9019 | - | Jul 1, 04:05 UTC | Jul 1, 09:35 UTC | 5h 30m |
| 2026-06-30 | GTI3596 | ANC → ORD | Jun 30, 05:20 UTC | Jun 30, 11:00 UTC | 5h 40m |
| 2026-06-29 | GTI3596 | - | Jun 29, 11:39 UTC | Jun 30, 03:40 UTC | 16h 1m |
| 2026-06-29 | GTI3595 | - | Jun 29, 05:20 UTC | Jun 30, 03:40 UTC | 22h 21m |
| 2026-06-29 | GTI3595 | - | Jun 29, 01:20 UTC | Jun 29, 21:39 UTC | 20h 20m |
| 2026-06-29 | GTI3595 | - | Jun 29, 01:14 UTC | Jun 29, 21:39 UTC | 20h 25m |
| 2026-06-28 | GTI303 | - | Jun 28, 07:34 UTC | Jun 28, 10:39 UTC | 3h 5m |
| 2026-06-27 | GTI303 | - | Jun 27, 21:55 UTC | Jun 28, 04:05 UTC | 6h 10m |
| 2026-06-27 | GTI303 | - | Jun 27, 05:15 UTC | Jun 27, 14:39 UTC | 9h 25m |
| 2026-06-27 | GTI302 | - | Jun 27, 02:20 UTC | Jun 27, 02:35 UTC | 15m |
| 2026-06-26 | GTI302 | - | Jun 26, 11:55 UTC | Jun 27, 00:10 UTC | 12h 15m |
| 2026-06-25 | GTI3013 | NGO → LAX | Jun 25, 23:55 UTC | Jun 26, 09:00 UTC | 9h 5m |
| 2026-06-25 | GTI3013 | NGO → LAX | Jun 25, 03:54 UTC | Jun 25, 07:54 UTC | 4h 0m |
| 2026-06-24 | GTI3080 | - | Jun 24, 09:39 UTC | Jun 25, 01:35 UTC | 15h 55m |
| 2026-06-22 | GTI354 | ICN → NLU | Jun 22, 15:10 UTC | Jun 22, 18:09 UTC | 3h 0m |
| 2026-06-22 | GTI354 | ICN → NLU | Jun 22, 04:49 UTC | Jun 22, 10:34 UTC | 5h 45m |
| 2026-06-21 | GTI354 | ICN → NLU | Jun 21, 18:29 UTC | Jun 22, 02:04 UTC | 7h 35m |
| 2026-06-21 | GTI353 | MST → MST | Jun 21, 13:50 UTC | Jun 21, 14:15 UTC | 25m |
| 2026-06-21 | GTI353 | MST → MST | Jun 21, 00:25 UTC | Jun 21, 12:40 UTC | 12h 15m |
| 2026-06-20 | GTI3019 | NGO → LAX | Jun 20, 00:59 UTC | Jun 20, 10:15 UTC | 9h 15m |
| 2026-06-19 | GTI3019 | NGO → LAX | Jun 19, 21:49 UTC | Jun 19, 22:45 UTC | 55m |
| 2026-06-19 | GTI3019 | NGO → LAX | Jun 19, 18:54 UTC | Jun 19, 19:04 UTC | 10m |
| 2026-06-19 | GTI3081 | LAX → HAN | Jun 19, 01:15 UTC | Jun 19, 16:14 UTC | 15h 0m |
| 2026-06-18 | GTI3013 | NGO → LAX | Jun 18, 10:20 UTC | Jun 18, 20:10 UTC | 9h 50m |
| 2026-06-18 | GTI3013 | NGO → LAX | Jun 18, 04:30 UTC | Jun 18, 08:20 UTC | 3h 50m |
| 2026-06-18 | GTI3094 | - | Jun 18, 01:55 UTC | Jun 18, 02:05 UTC | 10m |
| 2026-06-17 | GTI3094 | - | Jun 17, 17:15 UTC | Jun 18, 01:20 UTC | 8h 5m |
| 2026-06-17 | GTI3093 | HKG → OTP | Jun 17, 13:00 UTC | Jun 17, 13:20 UTC | 20m |
| 2026-06-17 | GTI3093 | HKG → OTP | Jun 17, 10:50 UTC | Jun 17, 12:05 UTC | 1h 15m |
| 2026-06-17 | GTI3093 | HKG → OTP | Jun 17, 02:35 UTC | Jun 17, 02:50 UTC | 15m |
| 2026-06-16 | GTI3090 | - | Jun 16, 16:39 UTC | Jun 16, 16:55 UTC | 15m |
| 2026-06-16 | GTI3090 | - | Jun 16, 02:34 UTC | Jun 16, 16:05 UTC | 13h 30m |
| 2026-06-15 | GTI354 | ICN → NLU | Jun 15, 20:45 UTC | Jun 15, 23:39 UTC | 2h 55m |
| 2026-06-15 | GTI354 | ICN → NLU | Jun 15, 11:19 UTC | Jun 15, 16:35 UTC | 5h 15m |
| 2026-06-14 | GTI354 | ICN → NLU | Jun 14, 13:20 UTC | Jun 15, 09:05 UTC | 19h 45m |
| 2026-06-14 | GTI354 | ICN → NLU | Jun 14, 11:45 UTC | Jun 15, 09:05 UTC | 21h 19m |
| 2026-06-14 | GTI353 | MST → MST | Jun 14, 07:20 UTC | Jun 15, 07:15 UTC | 23h 55m |
| 2026-06-14 | GTI353 | MST → MST | Jun 14, 06:05 UTC | Jun 15, 03:00 UTC | 20h 54m |
| 2026-06-14 | GTI353 | MST → MST | Jun 14, 03:20 UTC | Jun 15, 03:00 UTC | 23h 40m |
| 2026-06-14 | GTI353 | MST → MST | Jun 14, 02:15 UTC | Jun 14, 13:50 UTC | 11h 35m |
| 2026-06-13 | GTI303 | SZX → ANC | Jun 13, 22:15 UTC | Jun 13, 23:35 UTC | 1h 20m |
| 2026-06-13 | GTI303 | SZX → ANC | Jun 13, 11:10 UTC | Jun 13, 17:30 UTC | 6h 20m |
| 2026-06-12 | GTI303 | SZX → ANC | Jun 12, 23:30 UTC | Jun 13, 09:15 UTC | 9h 44m |
| 2026-06-12 | GTI302 | MIA → ANC | Jun 12, 20:00 UTC | Jun 12, 20:15 UTC | 15m |
| 2026-06-12 | GTI302 | MIA → ANC | Jun 12, 05:00 UTC | Jun 12, 17:45 UTC | 12h 45m |
| 2026-06-12 | GTI347 | ANC → ORD | Jun 12, 00:45 UTC | Jun 12, 02:05 UTC | 1h 20m |
| 2026-06-11 | GTI347 | ANC → ORD | Jun 11, 23:05 UTC | Jun 11, 23:15 UTC | 10m |
| 2026-06-11 | GTI346 | MIA → LGG | Jun 11, 13:45 UTC | Jun 11, 19:50 UTC | 6h 5m |
| 2026-06-10 | GTI346 | MIA → LGG | Jun 10, 19:20 UTC | Jun 11, 10:45 UTC | 15h 25m |
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 N709GT page for operator, model, and routing details .