sensors Mode-S transponder
ADFD71
ICAO 24-bit transponder address
Currently assigned to 89-0515 · Fairchild C-26B Metro III
- Hex
- ADFD71
- Octal
- 53376561
- Decimal
- 11,402,609
- Tail
- 89-0515
- Type
- SW4
- Flights observed
- 32
- Distinct callsigns
- 10
- Country
- -
- Last broadcast
- 15d ago
Last known position
Callsign history 10 distinct
Recent flights last 32
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-18 | PAT820 | - | May 18, 15:50 UTC | May 18, 18:45 UTC | 2h 54m |
| 2026-05-15 | PAT371 | - | May 15, 17:55 UTC | May 15, 18:20 UTC | 25m |
| 2026-05-15 | PAT371 | PUB → PUB | May 15, 17:30 UTC | May 15, 17:35 UTC | 5m |
| 2026-05-15 | PAT371 | - | May 15, 16:55 UTC | May 15, 17:00 UTC | 5m |
| 2026-05-15 | PAT371 | PUB → PUB | May 15, 16:30 UTC | May 15, 16:35 UTC | 5m |
| 2026-05-15 | PAT371 | - | May 15, 15:40 UTC | May 15, 16:25 UTC | 45m |
| 2026-05-15 | PAT371 | BFK → PUB | May 15, 14:50 UTC | May 15, 15:35 UTC | 45m |
| 2026-05-14 | PAT370 | - | May 14, 21:10 UTC | May 14, 23:30 UTC | 2h 20m |
| 2026-05-14 | PAT370 | - | May 14, 19:50 UTC | May 14, 20:55 UTC | 1h 5m |
| 2026-05-14 | PAT370 | BFK → LAX | May 14, 15:01 UTC | May 14, 18:20 UTC | 3h 20m |
| 2026-05-14 | PAT370 | - | May 14, 13:35 UTC | May 14, 13:40 UTC | 5m |
| 2026-05-14 | PAT370 | - | May 14, 13:15 UTC | May 14, 13:20 UTC | 5m |
| 2026-05-14 | PAT370 | - | May 14, 12:50 UTC | May 14, 13:10 UTC | 20m |
| 2026-05-14 | PAT370 | BFK → BFK | May 14, 11:55 UTC | May 14, 12:15 UTC | 20m |
| 2026-05-14 | PAT370 | BFK → BFK | May 14, 11:35 UTC | May 14, 11:50 UTC | 15m |
| 2026-05-13 | PAT368 | - | May 13, 17:05 UTC | May 13, 17:25 UTC | 20m |
| 2026-05-13 | PAT368 | BFK → COS | May 13, 15:20 UTC | May 13, 16:50 UTC | 1h 30m |
| 2026-05-12 | PAT366 | BFK → BFK | May 12, 19:30 UTC | May 12, 23:55 UTC | 4h 25m |
| 2026-05-12 | PAT366 | - | May 12, 17:10 UTC | May 12, 17:50 UTC | 40m |
| 2026-05-12 | PAT366 | - | May 12, 16:25 UTC | May 12, 16:55 UTC | 30m |
| 2026-05-12 | PAT366 | - | May 12, 16:10 UTC | May 12, 16:15 UTC | 5m |
| 2026-05-12 | PAT366 | BFK → BFK | May 12, 15:55 UTC | May 12, 16:05 UTC | 10m |
| 2026-05-12 | PAT366 | BFK → BFK | May 12, 15:30 UTC | May 12, 15:50 UTC | 20m |
| 2026-05-11 | PAT364 | BFK → BFK | May 11, 17:15 UTC | May 11, 19:30 UTC | 2h 15m |
| 2026-05-07 | PAT104 | - | May 7, 17:40 UTC | May 7, 17:45 UTC | 5m |
| 2026-05-07 | PAT104 | - | May 7, 17:20 UTC | May 7, 17:35 UTC | 15m |
| 2026-05-07 | PAT104 | BFK → BFK | May 7, 16:50 UTC | May 7, 17:00 UTC | 10m |
| 2026-05-07 | PAT104 | BFK → BFK | May 7, 16:40 UTC | May 7, 16:45 UTC | 5m |
| 2026-04-28 | PAT134 | - | Apr 28, 17:30 UTC | Apr 28, 17:35 UTC | 5m |
| 2026-04-28 | PAT134 | BFK → BFK | Apr 28, 15:35 UTC | Apr 28, 17:25 UTC | 1h 50m |
| 2026-04-17 | PAT499 | - | Apr 17, 14:55 UTC | Apr 17, 15:05 UTC | 10m |
| 2026-04-17 | PAT290 | - | Apr 17, 14:40 UTC | Apr 17, 14:50 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 89-0515 page for operator, model, and routing details .