sensors Mode-S transponder
AE627E
ICAO 24-bit transponder address
Currently assigned to 163638
- Hex
- AE627E
- Octal
- 53461176
- Decimal
- 11,428,478
- Tail
- 163638
- Type
- HAWK
- Flights observed
- 71
- Distinct callsigns
- 4
- Country
- -
- Last broadcast
- 18h ago
Last known position
Callsign history 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | BLZR238 | NQI → NQI | May 29, 15:05 UTC | May 29, 15:55 UTC | 50m |
| 2026-05-29 | BLZR238 | NQI → NQI | May 29, 13:25 UTC | May 29, 14:25 UTC | 1h 0m |
| 2026-05-29 | BLZR238 | NQI → NQI | May 29, 01:20 UTC | May 29, 02:30 UTC | 1h 10m |
| 2026-05-28 | BLZP238 | LRD → NQI | May 28, 21:00 UTC | May 28, 22:15 UTC | 1h 15m |
| 2026-05-28 | HAWK238 | NQI → NQI | May 28, 15:00 UTC | May 28, 15:55 UTC | 55m |
| 2026-05-28 | BLZR238 | NQI → NQI | May 28, 01:30 UTC | May 28, 02:35 UTC | 1h 5m |
| 2026-05-27 | BLZR238 | NQI → NQI | May 27, 20:05 UTC | May 27, 20:55 UTC | 50m |
| 2026-05-27 | HAWK238 | - | May 27, 01:34 UTC | May 27, 02:49 UTC | 1h 15m |
| 2026-05-26 | HAWK238 | - | May 26, 20:09 UTC | May 26, 21:09 UTC | 1h 0m |
| 2026-05-26 | BLZR238 | - | May 26, 17:30 UTC | May 26, 18:30 UTC | 1h 0m |
| 2026-05-26 | BLZR238 | - | May 26, 14:50 UTC | May 26, 15:54 UTC | 1h 5m |
| 2026-05-18 | HAWK238 | NQI → NQI | May 18, 22:30 UTC | May 18, 23:20 UTC | 50m |
| 2026-05-18 | BLZR238 | NQI → NQI | May 18, 19:45 UTC | May 18, 20:35 UTC | 50m |
| 2026-05-17 | HAWK238 | NQI → NQI | May 17, 15:15 UTC | May 17, 16:05 UTC | 50m |
| 2026-05-15 | HAWK238 | - | May 15, 21:00 UTC | May 15, 21:20 UTC | 20m |
| 2026-05-15 | HAWK238 | NQI → NQI | May 15, 19:55 UTC | May 15, 20:20 UTC | 25m |
| 2026-05-15 | HAWK238 | NQI → NQI | May 15, 18:55 UTC | May 15, 19:15 UTC | 20m |
| 2026-05-15 | HAWK238 | NQI → NQI | May 15, 17:55 UTC | May 15, 18:45 UTC | 50m |
| 2026-05-15 | BLZR238 | - | May 15, 15:30 UTC | May 15, 16:20 UTC | 50m |
| 2026-05-15 | BLZR238 | - | May 15, 13:40 UTC | May 15, 14:25 UTC | 45m |
| 2026-05-15 | HAWK238 | NQI → NQI | May 15, 01:05 UTC | May 15, 02:15 UTC | 1h 10m |
| 2026-05-14 | BLZR238 | NQI → NQI | May 14, 21:35 UTC | May 14, 22:00 UTC | 25m |
| 2026-05-14 | BLZR238 | - | May 14, 19:50 UTC | May 14, 20:45 UTC | 55m |
| 2026-05-14 | BLZR238 | - | May 14, 18:05 UTC | May 14, 18:50 UTC | 45m |
| 2026-05-14 | HAWK238 | NQI → NQI | May 14, 14:30 UTC | May 14, 15:30 UTC | 1h 0m |
| 2026-05-14 | HAWK238 | NQI → NQI | May 14, 01:40 UTC | May 14, 02:40 UTC | 1h 0m |
| 2026-05-13 | HAWK238 | NQI → NQI | May 13, 20:05 UTC | May 13, 21:05 UTC | 1h 0m |
| 2026-05-13 | HAWK238 | - | May 13, 16:10 UTC | May 13, 17:20 UTC | 1h 10m |
| 2026-05-13 | BLZR238 | NQI → NQI | May 13, 02:45 UTC | May 13, 03:00 UTC | 15m |
| 2026-05-13 | BLZR238 | NQI → NQI | May 13, 00:55 UTC | May 13, 01:20 UTC | 25m |
| 2026-05-12 | HAWK238 | NQI → NQI | May 12, 15:20 UTC | May 12, 16:15 UTC | 55m |
| 2026-05-11 | BLZR238 | NQI → NQI | May 11, 16:30 UTC | May 11, 17:50 UTC | 1h 21m |
| 2026-05-11 | HAWK238 | NQI → NQI | May 11, 13:50 UTC | May 11, 14:15 UTC | 25m |
| 2026-05-08 | LTHL238 | - | May 8, 21:30 UTC | May 8, 22:40 UTC | 1h 10m |
| 2026-05-08 | LTHL238 | - | May 8, 17:50 UTC | May 8, 18:05 UTC | 15m |
| 2026-05-06 | HAWK238 | - | May 6, 15:10 UTC | May 6, 16:05 UTC | 55m |
| 2026-05-06 | BLZR238 | NQI → NQI | May 6, 01:20 UTC | May 6, 02:40 UTC | 1h 20m |
| 2026-05-05 | BLZR238 | - | May 5, 19:50 UTC | May 5, 20:30 UTC | 40m |
| 2026-05-05 | HAWK238 | NQI → NQI | May 5, 17:35 UTC | May 5, 18:20 UTC | 45m |
| 2026-05-05 | BLZR238 | NQI → NQI | May 5, 14:50 UTC | May 5, 15:50 UTC | 1h 0m |
| 2026-05-04 | BLZR238 | - | May 4, 20:10 UTC | May 4, 21:20 UTC | 1h 10m |
| 2026-05-04 | BLZR238 | NQI → NQI | May 4, 17:50 UTC | May 4, 18:35 UTC | 46m |
| 2026-05-04 | LTHL238 | - | May 4, 14:05 UTC | May 4, 15:05 UTC | 1h 0m |
| 2026-05-03 | LTHL238 | - | May 3, 17:29 UTC | May 3, 17:54 UTC | 25m |
| 2026-04-24 | BLZR238 | - | Apr 24, 17:30 UTC | Apr 24, 17:40 UTC | 10m |
| 2026-04-24 | BLZR238 | - | Apr 24, 16:35 UTC | Apr 24, 16:40 UTC | 5m |
| 2026-04-23 | BLZR238 | - | Apr 23, 17:25 UTC | Apr 23, 18:25 UTC | 1h 0m |
| 2026-04-23 | BLZR238 | - | Apr 23, 14:25 UTC | Apr 23, 15:15 UTC | 50m |
| 2026-04-23 | HAWK238 | NQI → NQI | Apr 23, 00:55 UTC | Apr 23, 02:25 UTC | 1h 30m |
| 2026-04-22 | HAWK238 | NQI → NQI | Apr 22, 21:10 UTC | Apr 22, 22:00 UTC | 50m |
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 163638 page for operator, model, and routing details .