sensors Mode-S transponder
AE278C
ICAO 24-bit transponder address
Currently assigned to 166340 · SIKORSKY UH-60 Black Hawk
- Hex
- AE278C
- Octal
- 53423614
- Decimal
- 11,413,388
- Tail
- 166340
- Type
- H60
- Flights observed
- 67
- Distinct callsigns
- 5
- Country
- -
- Last broadcast
- 20d ago
Last known position
Callsign history 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-24 | LSXX | NZY → NZY | Jun 24, 05:49 UTC | Jun 24, 06:15 UTC | 25m |
| 2026-06-24 | LSXX | NZY → NZY | Jun 24, 04:30 UTC | Jun 24, 05:20 UTC | 50m |
| 2026-06-24 | LSXX | - | Jun 24, 02:49 UTC | Jun 24, 03:55 UTC | 1h 5m |
| 2026-06-24 | LSXX | - | Jun 24, 01:09 UTC | Jun 24, 02:30 UTC | 1h 20m |
| 2026-06-18 | FFAB123 | NRS → NZY | Jun 18, 00:50 UTC | Jun 18, 01:40 UTC | 50m |
| 2026-06-17 | FFAB123 | - | Jun 17, 23:30 UTC | Jun 18, 00:45 UTC | 1h 15m |
| 2026-06-17 | FFAB123 | NZY → NZY | Jun 17, 20:35 UTC | Jun 17, 23:20 UTC | 2h 45m |
| 2026-06-17 | FFAB123 | NZY → NZY | Jun 17, 19:55 UTC | Jun 17, 20:25 UTC | 30m |
| 2026-06-17 | FFAB123 | NZY → NZY | Jun 17, 18:05 UTC | Jun 17, 19:30 UTC | 1h 25m |
| 2026-06-17 | FFAB123 | - | Jun 17, 16:20 UTC | Jun 17, 17:25 UTC | 1h 5m |
| 2026-06-16 | FFAB123 | - | Jun 16, 05:40 UTC | Jun 16, 06:54 UTC | 1h 15m |
| 2026-06-16 | FFAB123 | NZY → NZY | Jun 16, 03:39 UTC | Jun 16, 05:00 UTC | 1h 20m |
| 2026-06-16 | FFAB123 | - | Jun 16, 00:05 UTC | Jun 16, 02:54 UTC | 2h 50m |
| 2026-06-15 | LS10 | NRS → NZY | Jun 15, 20:30 UTC | Jun 15, 21:25 UTC | 55m |
| 2026-06-15 | LS10 | NZY → NZY | Jun 15, 18:04 UTC | Jun 15, 19:45 UTC | 1h 40m |
| 2026-06-13 | LS10 | - | Jun 13, 03:20 UTC | Jun 13, 03:35 UTC | 15m |
| 2026-06-13 | LS10 | NZY → NZY | Jun 13, 00:20 UTC | Jun 13, 01:40 UTC | 1h 20m |
| 2026-06-12 | LS10 | NZY → NZY | Jun 12, 23:45 UTC | Jun 12, 23:50 UTC | 5m |
| 2026-06-12 | LS10 | NZY → NZY | Jun 12, 21:30 UTC | Jun 12, 23:40 UTC | 2h 10m |
| 2026-06-12 | LS10 | - | Jun 12, 19:20 UTC | Jun 12, 20:50 UTC | 1h 30m |
| 2026-06-12 | LS10 | - | Jun 12, 16:50 UTC | Jun 12, 18:50 UTC | 2h 0m |
| 2026-06-11 | LS10 | NZY → NZY | Jun 11, 21:40 UTC | Jun 12, 02:30 UTC | 4h 51m |
| 2026-06-11 | LSXX | - | Jun 11, 18:55 UTC | Jun 11, 21:05 UTC | 2h 10m |
| 2026-06-11 | LS10 | - | Jun 11, 05:05 UTC | Jun 11, 06:40 UTC | 1h 35m |
| 2026-06-10 | LS10 | NZY → NZY | Jun 10, 23:25 UTC | Jun 11, 04:45 UTC | 5h 20m |
| 2026-06-10 | LS10 | - | Jun 10, 03:40 UTC | Jun 10, 04:30 UTC | 50m |
| 2026-06-10 | LS10 | - | Jun 10, 00:35 UTC | Jun 10, 01:10 UTC | 35m |
| 2026-06-10 | LS10 | NZY → NZY | Jun 10, 00:10 UTC | Jun 10, 00:20 UTC | 10m |
| 2026-06-04 | LS10 | - | Jun 4, 02:55 UTC | Jun 4, 04:30 UTC | 1h 35m |
| 2026-06-03 | LS11 | BHX → LBA | Jun 3, 23:40 UTC | Jun 4, 02:25 UTC | 2h 45m |
| 2026-06-03 | LS10 | NZY → NZY | Jun 3, 20:50 UTC | Jun 3, 22:55 UTC | 2h 5m |
| 2026-06-03 | LS10 | NZY → NZY | Jun 3, 17:50 UTC | Jun 3, 20:05 UTC | 2h 15m |
| 2026-06-03 | LS10 | - | Jun 3, 15:30 UTC | Jun 3, 17:25 UTC | 1h 55m |
| 2026-06-02 | LS11 | BHX → LBA | Jun 2, 03:05 UTC | Jun 2, 05:30 UTC | 2h 25m |
| 2026-06-02 | LS10 | NZY → NZY | Jun 2, 00:10 UTC | Jun 2, 02:35 UTC | 2h 25m |
| 2026-06-01 | LS10 | NZY → NZY | Jun 1, 21:25 UTC | Jun 1, 23:55 UTC | 2h 30m |
| 2026-06-01 | LS10 | NZY → NZY | Jun 1, 15:50 UTC | Jun 1, 17:30 UTC | 1h 40m |
| 2026-05-29 | LS10 | - | May 29, 04:25 UTC | May 29, 04:55 UTC | 30m |
| 2026-05-29 | LS10 | - | May 29, 02:50 UTC | May 29, 03:55 UTC | 1h 5m |
| 2026-05-29 | LS10 | - | May 29, 01:05 UTC | May 29, 02:15 UTC | 1h 10m |
| 2026-05-29 | LS10 | - | May 29, 00:15 UTC | May 29, 00:20 UTC | 5m |
| 2026-05-22 | LS10 | NZY → NZY | May 22, 05:35 UTC | May 22, 06:40 UTC | 1h 5m |
| 2026-05-22 | LS10 | - | May 22, 03:30 UTC | May 22, 05:10 UTC | 1h 40m |
| 2026-05-22 | LS10 | NZY → NZY | May 22, 03:15 UTC | May 22, 03:20 UTC | 5m |
| 2026-05-07 | BRACE10 | - | May 7, 18:30 UTC | May 7, 20:55 UTC | 2h 25m |
| 2026-05-07 | LS10 | NZY → NZY | May 7, 00:20 UTC | May 7, 02:25 UTC | 2h 5m |
| 2026-05-06 | LS10 | - | May 6, 21:55 UTC | May 6, 23:55 UTC | 2h 0m |
| 2026-05-06 | LS10 | - | May 6, 19:35 UTC | May 6, 19:45 UTC | 10m |
| 2026-05-06 | LS10 | - | May 6, 19:05 UTC | May 6, 19:15 UTC | 10m |
| 2026-04-23 | LS10 | - | Apr 23, 20:55 UTC | Apr 23, 21:05 UTC | 10m |
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 166340 page for operator, model, and routing details .