sensors Mode-S transponder
ADFE8F
ICAO 24-bit transponder address
Currently assigned to 95-00090 · Beech C-12V Huron
- Hex
- ADFE8F
- Octal
- 53377217
- Decimal
- 11,402,895
- Tail
- 95-00090
- Type
- BE20
- Flights observed
- 59
- Distinct callsigns
- 15
- Country
- -
- Last broadcast
- 13d ago
Last known position
Callsign history 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PAT706 | - | 9 | 2026-04-15 |
| PAT314 | - | 8 | 2026-05-09 |
| PAT090 | - | 8 | 2026-06-05 |
| PAT840 | - | 7 | 2026-04-17 |
| PAT988 | - | 6 | 2026-05-21 |
| PAT153 | - | 4 | 2026-06-24 |
| PAT930 | - | 2 | 2026-05-19 |
| PAT924 | - | 2 | 2026-05-18 |
| PAT820 | - | 2 | 2026-06-17 |
| PAT690 | - | 2 | 2026-04-20 |
| PAT333 | - | 2 | 2026-04-24 |
| PAT325 | - | 2 | 2026-06-30 |
| PAT283 | - | 2 | 2026-06-26 |
| PAT110 | - | 2 | 2026-04-22 |
| PAT740 | - | 1 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-30 | PAT325 | - | Jun 30, 19:00 UTC | Jun 30, 19:50 UTC | 50m |
| 2026-06-30 | PAT325 | - | Jun 30, 14:55 UTC | Jun 30, 15:50 UTC | 55m |
| 2026-06-26 | PAT283 | - | Jun 26, 16:54 UTC | Jun 26, 17:40 UTC | 45m |
| 2026-06-26 | PAT283 | - | Jun 26, 14:35 UTC | Jun 26, 15:34 UTC | 1h 0m |
| 2026-06-24 | PAT153 | - | Jun 24, 20:54 UTC | Jun 24, 22:14 UTC | 1h 20m |
| 2026-06-24 | PAT153 | - | Jun 24, 17:50 UTC | Jun 24, 20:14 UTC | 2h 25m |
| 2026-06-23 | PAT153 | - | Jun 23, 16:39 UTC | Jun 23, 19:10 UTC | 2h 30m |
| 2026-06-23 | PAT153 | - | Jun 23, 14:39 UTC | Jun 23, 15:59 UTC | 1h 20m |
| 2026-06-17 | PAT820 | - | Jun 17, 19:50 UTC | Jun 17, 20:20 UTC | 30m |
| 2026-06-17 | PAT820 | - | Jun 17, 15:10 UTC | Jun 17, 15:50 UTC | 40m |
| 2026-06-05 | PAT090 | - | Jun 5, 23:40 UTC | Jun 5, 23:55 UTC | 15m |
| 2026-06-04 | PAT740 | - | Jun 4, 21:55 UTC | Jun 4, 22:20 UTC | 25m |
| 2026-05-27 | PAT090 | - | May 27, 19:25 UTC | May 27, 19:45 UTC | 20m |
| 2026-05-27 | PAT090 | - | May 27, 16:30 UTC | May 27, 17:25 UTC | 55m |
| 2026-05-27 | PAT090 | - | May 27, 15:40 UTC | May 27, 15:55 UTC | 15m |
| 2026-05-21 | PAT988 | - | May 21, 22:10 UTC | May 21, 22:25 UTC | 15m |
| 2026-05-21 | PAT988 | - | May 21, 21:05 UTC | May 21, 21:15 UTC | 10m |
| 2026-05-21 | PAT988 | - | May 21, 19:20 UTC | May 21, 19:40 UTC | 20m |
| 2026-05-21 | PAT988 | - | May 21, 18:05 UTC | May 21, 18:40 UTC | 35m |
| 2026-05-21 | PAT988 | - | May 21, 17:05 UTC | May 21, 17:25 UTC | 20m |
| 2026-05-21 | PAT988 | - | May 21, 16:05 UTC | May 21, 16:20 UTC | 15m |
| 2026-05-19 | PAT930 | - | May 19, 20:30 UTC | May 19, 21:15 UTC | 45m |
| 2026-05-19 | PAT930 | - | May 19, 18:25 UTC | May 19, 19:15 UTC | 50m |
| 2026-05-18 | PAT924 | - | May 18, 16:55 UTC | May 18, 17:45 UTC | 50m |
| 2026-05-18 | PAT924 | - | May 18, 14:50 UTC | May 18, 15:35 UTC | 45m |
| 2026-05-09 | PAT314 | - | May 9, 00:25 UTC | May 9, 00:35 UTC | 10m |
| 2026-05-08 | PAT314 | - | May 8, 20:45 UTC | May 8, 21:50 UTC | 1h 5m |
| 2026-05-08 | PAT314 | - | May 8, 16:55 UTC | May 8, 19:55 UTC | 3h 0m |
| 2026-05-08 | PAT314 | - | May 8, 15:55 UTC | May 8, 16:15 UTC | 20m |
| 2026-05-07 | PAT314 | - | May 7, 17:20 UTC | May 7, 17:45 UTC | 25m |
| 2026-05-07 | PAT314 | - | May 7, 14:25 UTC | May 7, 16:20 UTC | 1h 55m |
| 2026-05-06 | PAT314 | - | May 6, 21:00 UTC | May 6, 22:20 UTC | 1h 20m |
| 2026-05-06 | PAT314 | - | May 6, 19:00 UTC | May 6, 20:15 UTC | 1h 15m |
| 2026-04-30 | PAT090 | - | Apr 30, 18:55 UTC | Apr 30, 19:20 UTC | 25m |
| 2026-04-30 | PAT090 | - | Apr 30, 17:30 UTC | Apr 30, 17:55 UTC | 25m |
| 2026-04-27 | PAT090 | - | Apr 27, 20:40 UTC | Apr 27, 22:05 UTC | 1h 25m |
| 2026-04-27 | PAT090 | - | Apr 27, 15:10 UTC | Apr 27, 16:35 UTC | 1h 25m |
| 2026-04-24 | PAT333 | - | Apr 24, 19:35 UTC | Apr 24, 20:55 UTC | 1h 20m |
| 2026-04-24 | PAT333 | - | Apr 24, 17:30 UTC | Apr 24, 18:50 UTC | 1h 20m |
| 2026-04-22 | PAT110 | - | Apr 22, 18:05 UTC | Apr 22, 19:40 UTC | 1h 35m |
| 2026-04-22 | PAT110 | - | Apr 22, 16:00 UTC | Apr 22, 17:30 UTC | 1h 30m |
| 2026-04-20 | PAT690 | - | Apr 20, 17:30 UTC | Apr 20, 19:35 UTC | 2h 5m |
| 2026-04-20 | PAT690 | - | Apr 20, 13:45 UTC | Apr 20, 16:15 UTC | 2h 30m |
| 2026-04-17 | PAT840 | - | Apr 17, 22:30 UTC | Apr 17, 22:45 UTC | 15m |
| 2026-04-17 | PAT840 | - | Apr 17, 19:45 UTC | Apr 17, 20:45 UTC | 1h 0m |
| 2026-04-17 | PAT840 | - | Apr 17, 17:25 UTC | Apr 17, 19:00 UTC | 1h 35m |
| 2026-04-17 | PAT840 | - | Apr 17, 16:55 UTC | Apr 17, 17:15 UTC | 20m |
| 2026-04-16 | PAT840 | - | Apr 16, 19:15 UTC | Apr 16, 20:35 UTC | 1h 20m |
| 2026-04-16 | PAT840 | - | Apr 16, 17:30 UTC | Apr 16, 19:10 UTC | 1h 40m |
| 2026-04-16 | PAT840 | - | Apr 16, 16:30 UTC | Apr 16, 16:40 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 95-00090 page for operator, model, and routing details .