sensors Mode-S transponder
A0998A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N138GL · GULFSTREAM 5 · operated by SWR SERVICES III LLC
- Hex
- A0998A
- Octal
- 50114612
- Decimal
- 10,525,066
- Country
- US
- Tail
- N138GL
- Type
- GLF5
- Flights observed
- 59
- Distinct callsigns
- 2
- Country
- US
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address A0998A 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | N138GL | - | Jul 15, 06:40 UTC | Jul 15, 07:50 UTC | 1h 10m |
| 2026-07-03 | N138GL | - | Jul 3, 11:00 UTC | Jul 3, 11:20 UTC | 20m |
| 2026-06-27 | N138GL | - | Jun 27, 10:29 UTC | Jun 27, 10:40 UTC | 10m |
| 2026-06-27 | N138GL | - | Jun 27, 08:25 UTC | Jun 27, 09:34 UTC | 1h 10m |
| 2026-06-25 | N138GL | - | Jun 25, 22:49 UTC | Jun 26, 06:00 UTC | 7h 10m |
| 2026-06-21 | N138GL | BUR → MDW | Jun 21, 21:10 UTC | Jun 22, 00:10 UTC | 3h 0m |
| 2026-06-21 | N138GL | FAI → BUR | Jun 21, 03:44 UTC | Jun 21, 07:59 UTC | 4h 15m |
| 2026-06-20 | N138GL | - | Jun 20, 17:49 UTC | Jun 20, 22:54 UTC | 5h 5m |
| 2026-06-19 | N138GL | - | Jun 19, 17:55 UTC | Jun 19, 18:39 UTC | 45m |
| 2026-06-15 | N138GL | - | Jun 15, 22:20 UTC | Jun 15, 22:54 UTC | 35m |
| 2026-06-15 | N138GL | TEB → MDW | Jun 15, 19:20 UTC | Jun 15, 20:59 UTC | 1h 40m |
| 2026-06-14 | N138GL | BUR → TEB | Jun 14, 19:45 UTC | Jun 15, 00:05 UTC | 4h 19m |
| 2026-06-12 | N138GL | OAK → BUR | Jun 12, 20:35 UTC | Jun 12, 21:25 UTC | 50m |
| 2026-06-12 | N138GL | - | Jun 12, 16:05 UTC | Jun 12, 16:55 UTC | 50m |
| 2026-06-12 | N138GL | - | Jun 12, 14:35 UTC | Jun 12, 15:25 UTC | 50m |
| 2026-06-10 | N138GL | - | Jun 10, 22:10 UTC | Jun 11, 03:10 UTC | 5h 0m |
| 2026-06-10 | N138GL | - | Jun 10, 17:50 UTC | Jun 10, 18:40 UTC | 50m |
| 2026-06-09 | N138GL | - | Jun 9, 21:30 UTC | Jun 9, 23:00 UTC | 1h 30m |
| 2026-06-08 | N138GL | OAK → MDW | Jun 8, 23:15 UTC | Jun 9, 02:30 UTC | 3h 15m |
| 2026-06-07 | N138GL | BUR → OAK | Jun 7, 21:05 UTC | Jun 7, 21:55 UTC | 50m |
| 2026-06-05 | N138GL | - | Jun 5, 12:15 UTC | Jun 5, 17:00 UTC | 4h 45m |
| 2026-06-02 | N138GL | - | Jun 2, 22:35 UTC | Jun 3, 00:15 UTC | 1h 40m |
| 2026-06-01 | N138GL | OAK → MDW | Jun 1, 13:30 UTC | Jun 1, 16:45 UTC | 3h 15m |
| 2026-05-30 | N138GL | - | May 30, 11:30 UTC | May 30, 20:45 UTC | 9h 15m |
| 2026-05-29 | TWY4 | NCE → LTN | May 29, 08:05 UTC | May 29, 09:35 UTC | 1h 30m |
| 2026-05-28 | TWY4 | - | May 28, 20:35 UTC | May 29, 07:10 UTC | 10h 35m |
| 2026-05-28 | N138GL | - | May 28, 04:40 UTC | May 28, 08:15 UTC | 3h 35m |
| 2026-05-27 | N138GL | OAK → MDW | May 27, 23:40 UTC | May 28, 03:00 UTC | 3h 20m |
| 2026-05-23 | N138GL | - | May 23, 02:10 UTC | May 23, 07:00 UTC | 4h 49m |
| 2026-05-22 | N138GL | TEB → TTN | May 22, 23:50 UTC | May 23, 00:05 UTC | 15m |
| 2026-05-21 | N138GL | BFI → TEB | May 21, 17:50 UTC | May 21, 21:55 UTC | 4h 5m |
| 2026-05-21 | N138GL | - | May 21, 13:55 UTC | May 21, 15:25 UTC | 1h 30m |
| 2026-05-18 | N138GL | - | May 18, 21:35 UTC | May 19, 02:50 UTC | 5h 15m |
| 2026-05-17 | N138GL | OAK → TEB | May 17, 22:55 UTC | May 18, 03:30 UTC | 4h 35m |
| 2026-05-17 | N138GL | BUR → OAK | May 17, 21:35 UTC | May 17, 22:25 UTC | 50m |
| 2026-05-15 | N138GL | OAK → BUR | May 15, 21:50 UTC | May 15, 22:40 UTC | 50m |
| 2026-05-14 | N138GL | PBI → OAK | May 14, 16:40 UTC | May 14, 21:50 UTC | 5h 10m |
| 2026-05-14 | N138GL | - | May 14, 10:25 UTC | May 14, 12:30 UTC | 2h 5m |
| 2026-05-13 | N138GL | - | May 13, 02:40 UTC | May 13, 04:50 UTC | 2h 10m |
| 2026-05-11 | N138GL | OAK → XNA | May 11, 11:30 UTC | May 11, 14:15 UTC | 2h 45m |
| 2026-05-10 | N138GL | SBA → OAK | May 10, 22:20 UTC | May 10, 23:09 UTC | 50m |
| 2026-05-08 | N138GL | OAK → SBA | May 8, 23:00 UTC | May 8, 23:45 UTC | 45m |
| 2026-05-07 | N138GL | SBA → OAK | May 7, 03:45 UTC | May 7, 04:30 UTC | 45m |
| 2026-05-06 | N138GL | OAK → SBA | May 6, 23:40 UTC | May 7, 00:25 UTC | 45m |
| 2026-05-03 | N138GL | BUR → OAK | May 3, 20:49 UTC | May 3, 21:39 UTC | 50m |
| 2026-05-03 | N138GL | OAK → BUR | May 3, 14:35 UTC | May 3, 15:30 UTC | 55m |
| 2026-04-30 | N138GL | BUR → OAK | Apr 30, 02:00 UTC | Apr 30, 02:50 UTC | 50m |
| 2026-04-28 | N138GL | - | Apr 28, 21:55 UTC | Apr 29, 03:04 UTC | 5h 10m |
| 2026-04-26 | N138GL | OAK → TEB | Apr 26, 23:25 UTC | Apr 27, 03:45 UTC | 4h 20m |
| 2026-04-22 | N138GL | - | Apr 22, 01:35 UTC | Apr 22, 06:35 UTC | 5h 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 N138GL page for operator, model, and routing details .