sensors Mode-S transponder
AE2911
ICAO 24-bit transponder address
Currently assigned to 6034 · Sikorsky MH-60T Jayhawk
- Hex
- AE2911
- Octal
- 53424421
- Decimal
- 11,413,777
- Tail
- 6034
- Type
- H60
- Flights observed
- 67
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 13d ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| C6034 | - | 67 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | C6034 | - | Jul 10, 20:45 UTC | Jul 10, 21:00 UTC | 15m |
| 2026-07-10 | C6034 | - | Jul 10, 05:30 UTC | Jul 10, 05:45 UTC | 15m |
| 2026-06-18 | C6034 | - | Jun 18, 18:00 UTC | Jun 18, 18:05 UTC | 5m |
| 2026-06-17 | C6034 | - | Jun 17, 20:55 UTC | Jun 17, 21:30 UTC | 35m |
| 2026-06-17 | C6034 | - | Jun 17, 20:20 UTC | Jun 17, 20:30 UTC | 10m |
| 2026-06-17 | C6034 | - | Jun 17, 19:00 UTC | Jun 17, 19:05 UTC | 5m |
| 2026-06-17 | C6034 | - | Jun 17, 17:50 UTC | Jun 17, 17:55 UTC | 5m |
| 2026-06-17 | C6034 | ADQ → ADQ | Jun 17, 01:25 UTC | Jun 17, 03:30 UTC | 2h 5m |
| 2026-06-14 | C6034 | ADQ → ADQ | Jun 14, 21:15 UTC | Jun 14, 22:05 UTC | 50m |
| 2026-06-14 | C6034 | ADQ → ADQ | Jun 14, 20:10 UTC | Jun 14, 21:10 UTC | 1h 0m |
| 2026-06-10 | C6034 | - | Jun 10, 18:20 UTC | Jun 10, 21:00 UTC | 2h 40m |
| 2026-06-10 | C6034 | - | Jun 10, 03:05 UTC | Jun 10, 03:25 UTC | 20m |
| 2026-06-10 | C6034 | ADQ → ADQ | Jun 10, 01:25 UTC | Jun 10, 02:45 UTC | 1h 20m |
| 2026-06-08 | C6034 | - | Jun 8, 20:05 UTC | Jun 8, 20:35 UTC | 30m |
| 2026-06-08 | C6034 | - | Jun 8, 17:50 UTC | Jun 8, 18:35 UTC | 45m |
| 2026-06-05 | C6034 | - | Jun 5, 19:55 UTC | Jun 5, 20:50 UTC | 55m |
| 2026-06-05 | C6034 | ADQ → ADQ | Jun 5, 19:40 UTC | Jun 5, 19:45 UTC | 5m |
| 2026-05-10 | C6034 | - | May 10, 22:40 UTC | May 10, 22:49 UTC | 10m |
| 2026-05-09 | C6034 | ADQ → ADQ | May 9, 18:00 UTC | May 9, 20:00 UTC | 2h 0m |
| 2026-05-09 | C6034 | - | May 9, 08:30 UTC | May 9, 08:45 UTC | 15m |
| 2026-05-09 | C6034 | - | May 9, 06:50 UTC | May 9, 07:10 UTC | 20m |
| 2026-05-09 | C6034 | - | May 9, 05:50 UTC | May 9, 06:20 UTC | 30m |
| 2026-05-09 | C6034 | - | May 9, 03:35 UTC | May 9, 04:00 UTC | 25m |
| 2026-05-08 | C6034 | - | May 8, 23:25 UTC | May 8, 23:45 UTC | 20m |
| 2026-05-08 | C6034 | - | May 8, 22:30 UTC | May 8, 22:50 UTC | 20m |
| 2026-05-08 | C6034 | - | May 8, 19:20 UTC | May 8, 20:00 UTC | 40m |
| 2026-05-08 | C6034 | - | May 8, 18:55 UTC | May 8, 19:10 UTC | 15m |
| 2026-05-08 | C6034 | - | May 8, 17:55 UTC | May 8, 18:20 UTC | 25m |
| 2026-05-03 | C6034 | - | May 3, 19:10 UTC | May 3, 19:25 UTC | 15m |
| 2026-05-03 | C6034 | - | May 3, 17:45 UTC | May 3, 18:09 UTC | 25m |
| 2026-05-02 | C6034 | - | May 2, 19:00 UTC | May 2, 19:25 UTC | 25m |
| 2026-05-02 | C6034 | - | May 2, 17:30 UTC | May 2, 18:25 UTC | 55m |
| 2026-05-02 | C6034 | ADQ → ADQ | May 2, 03:00 UTC | May 2, 03:20 UTC | 20m |
| 2026-05-02 | C6034 | ADQ → ADQ | May 2, 02:35 UTC | May 2, 02:40 UTC | 5m |
| 2026-05-02 | C6034 | ADQ → ADQ | May 2, 02:05 UTC | May 2, 02:20 UTC | 15m |
| 2026-05-01 | C6034 | ADQ → ADQ | May 1, 23:35 UTC | May 2, 00:20 UTC | 45m |
| 2026-05-01 | C6034 | ADQ → ADQ | May 1, 00:00 UTC | May 1, 00:05 UTC | 5m |
| 2026-04-30 | C6034 | ADQ → ADQ | Apr 30, 20:00 UTC | Apr 30, 20:05 UTC | 5m |
| 2026-04-30 | C6034 | ADQ → ADQ | Apr 30, 19:30 UTC | Apr 30, 19:45 UTC | 15m |
| 2026-04-30 | C6034 | ADQ → ADQ | Apr 30, 19:00 UTC | Apr 30, 19:25 UTC | 25m |
| 2026-04-30 | C6034 | ADQ → ADQ | Apr 30, 18:35 UTC | Apr 30, 18:50 UTC | 15m |
| 2026-04-30 | C6034 | - | Apr 30, 01:30 UTC | Apr 30, 03:20 UTC | 1h 50m |
| 2026-04-29 | C6034 | ADQ → ADQ | Apr 29, 21:40 UTC | Apr 29, 23:10 UTC | 1h 29m |
| 2026-04-29 | C6034 | ADQ → ADQ | Apr 29, 17:50 UTC | Apr 29, 19:55 UTC | 2h 5m |
| 2026-04-29 | C6034 | ADQ → ADQ | Apr 29, 01:54 UTC | Apr 29, 03:34 UTC | 1h 40m |
| 2026-04-29 | C6034 | - | Apr 29, 00:20 UTC | Apr 29, 01:20 UTC | 1h 0m |
| 2026-04-28 | C6034 | - | Apr 28, 22:25 UTC | Apr 28, 23:29 UTC | 1h 5m |
| 2026-04-28 | C6034 | - | Apr 28, 20:45 UTC | Apr 28, 21:15 UTC | 30m |
| 2026-04-28 | C6034 | - | Apr 28, 03:35 UTC | Apr 28, 03:50 UTC | 15m |
| 2026-04-26 | C6034 | - | Apr 26, 18:50 UTC | Apr 26, 19:00 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 6034 page for operator, model, and routing details .