sensors Mode-S transponder
AE118A
ICAO 24-bit transponder address
Currently assigned to 02-01863 · Gulfstream Aerospace C-37A
- Hex
- AE118A
- Octal
- 53410612
- Decimal
- 11,407,754
- Tail
- 02-01863
- Type
- GLF5
- Flights observed
- 60
- Distinct callsigns
- 2
- Country
- -
- Last broadcast
- 1d ago
Last known position
Callsign history 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | FORGE63 | - | Jul 24, 20:00 UTC | Jul 24, 22:15 UTC | 2h 15m |
| 2026-07-24 | FORGE63 | - | Jul 24, 14:35 UTC | Jul 24, 17:25 UTC | 2h 50m |
| 2026-07-23 | FORGE63 | - | Jul 23, 20:25 UTC | Jul 23, 21:20 UTC | 55m |
| 2026-07-23 | FORGE63 | - | Jul 23, 15:45 UTC | Jul 23, 16:45 UTC | 1h 0m |
| 2026-07-22 | FORGE63 | - | Jul 22, 19:20 UTC | Jul 22, 20:20 UTC | 1h 0m |
| 2026-07-22 | FORGE63 | - | Jul 22, 16:10 UTC | Jul 22, 18:30 UTC | 2h 20m |
| 2026-07-21 | FORGE63 | - | Jul 21, 13:20 UTC | Jul 21, 17:00 UTC | 3h 40m |
| 2026-07-20 | FORGE63 | - | Jul 20, 15:55 UTC | Jul 20, 17:05 UTC | 1h 10m |
| 2026-07-19 | FORGE63 | TEB → ADW | Jul 19, 22:50 UTC | Jul 19, 23:30 UTC | 40m |
| 2026-07-19 | FORGE63 | - | Jul 19, 15:25 UTC | Jul 19, 16:30 UTC | 1h 5m |
| 2026-07-16 | FORGE63 | - | Jul 16, 20:15 UTC | Jul 16, 23:25 UTC | 3h 10m |
| 2026-07-16 | FORGE63 | - | Jul 16, 00:35 UTC | Jul 16, 23:25 UTC | 22h 50m |
| 2026-07-15 | FORGE63 | - | Jul 15, 22:35 UTC | Jul 16, 22:30 UTC | 23h 55m |
| 2026-07-15 | FORGE63 | - | Jul 15, 22:00 UTC | Jul 16, 20:19 UTC | 22h 20m |
| 2026-07-14 | FORGE63 | - | Jul 14, 15:10 UTC | Jul 14, 15:40 UTC | 30m |
| 2026-07-13 | FORGE63 | - | Jul 13, 18:15 UTC | Jul 13, 19:25 UTC | 1h 10m |
| 2026-07-13 | FORGE63 | - | Jul 13, 12:25 UTC | Jul 13, 13:35 UTC | 1h 10m |
| 2026-07-09 | FORGE63 | - | Jul 9, 18:00 UTC | Jul 9, 19:20 UTC | 1h 20m |
| 2026-07-08 | FORGE63 | - | Jul 8, 18:10 UTC | Jul 8, 19:30 UTC | 1h 20m |
| 2026-07-06 | FORGE63 | - | Jul 6, 18:00 UTC | Jul 6, 19:20 UTC | 1h 20m |
| 2026-07-06 | FORGE63 | - | Jul 6, 14:05 UTC | Jul 6, 16:45 UTC | 2h 40m |
| 2026-06-30 | PAT63 | - | Jun 30, 05:25 UTC | Jun 30, 14:10 UTC | 8h 45m |
| 2026-06-25 | PAT63 | - | Jun 25, 07:15 UTC | Jun 25, 13:35 UTC | 6h 20m |
| 2026-06-25 | PAT63 | - | Jun 25, 01:50 UTC | Jun 25, 06:14 UTC | 4h 25m |
| 2026-06-24 | FORGE63 | - | Jun 24, 22:39 UTC | Jun 25, 00:44 UTC | 2h 5m |
| 2026-06-24 | FORGE63 | - | Jun 24, 19:49 UTC | Jun 24, 21:19 UTC | 1h 30m |
| 2026-06-19 | PAT63 | HEL → ADW | Jun 19, 11:59 UTC | Jun 19, 20:59 UTC | 9h 0m |
| 2026-06-18 | PAT63 | - | Jun 18, 05:50 UTC | Jun 18, 08:10 UTC | 2h 20m |
| 2026-06-15 | PAT63 | - | Jun 15, 10:45 UTC | Jun 15, 17:40 UTC | 6h 55m |
| 2026-06-11 | FORGE63 | - | Jun 11, 17:00 UTC | Jun 11, 18:15 UTC | 1h 15m |
| 2026-06-11 | FORGE63 | - | Jun 11, 12:25 UTC | Jun 11, 14:30 UTC | 2h 5m |
| 2026-06-06 | FORGE63 | TEB → ADW | Jun 6, 17:40 UTC | Jun 6, 18:25 UTC | 45m |
| 2026-06-06 | FORGE63 | - | Jun 6, 13:49 UTC | Jun 6, 16:50 UTC | 3h 0m |
| 2026-06-05 | FORGE63 | - | Jun 5, 21:40 UTC | Jun 5, 23:25 UTC | 1h 45m |
| 2026-06-05 | FORGE63 | - | Jun 5, 19:20 UTC | Jun 5, 20:50 UTC | 1h 30m |
| 2026-06-05 | FORGE63 | - | Jun 5, 17:15 UTC | Jun 5, 18:10 UTC | 55m |
| 2026-06-05 | FORGE63 | - | Jun 5, 12:40 UTC | Jun 5, 13:00 UTC | 20m |
| 2026-06-04 | FORGE63 | - | Jun 4, 18:35 UTC | Jun 4, 19:25 UTC | 50m |
| 2026-06-04 | FORGE63 | - | Jun 4, 12:15 UTC | Jun 4, 12:40 UTC | 25m |
| 2026-06-03 | FORGE63 | - | Jun 3, 19:20 UTC | Jun 3, 21:05 UTC | 1h 45m |
| 2026-06-03 | FORGE63 | - | Jun 3, 17:30 UTC | Jun 3, 18:45 UTC | 1h 15m |
| 2026-06-02 | FORGE63 | - | Jun 2, 21:10 UTC | Jun 2, 22:10 UTC | 1h 0m |
| 2026-06-02 | FORGE63 | - | Jun 2, 17:35 UTC | Jun 2, 18:15 UTC | 40m |
| 2026-06-02 | FORGE63 | - | Jun 2, 11:55 UTC | Jun 2, 13:35 UTC | 1h 40m |
| 2026-06-01 | FORGE63 | JFK → ADW | Jun 1, 15:05 UTC | Jun 1, 15:50 UTC | 45m |
| 2026-06-01 | FORGE63 | - | Jun 1, 13:00 UTC | Jun 1, 13:35 UTC | 35m |
| 2026-05-30 | PAT63 | - | May 30, 09:15 UTC | May 30, 17:35 UTC | 8h 20m |
| 2026-05-29 | PAT63 | - | May 29, 07:25 UTC | May 29, 11:50 UTC | 4h 25m |
| 2026-05-27 | PAT63 | KEF → HEL | May 27, 23:00 UTC | May 28, 01:45 UTC | 2h 45m |
| 2026-05-27 | PAT63 | - | May 27, 21:50 UTC | May 27, 22:05 UTC | 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 02-01863 page for operator, model, and routing details .