sensors Mode-S transponder
08A105
ICAO 24-bit transponder address · allocated to Zambia
Currently assigned to 9J-PFE · BOMBARDIER Regional Jet CRJ-200
- Hex
- 08A105
- Octal
- 02120405
- Decimal
- 565,509
- Country
- ZM
- Tail
- 9J-PFE
- Type
- CRJ2
- Flights observed
- 46
- Distinct callsigns
- 8
- Country
- ZM
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 08A105 falls within the block assigned to Zambia (ZM) by ICAO Annex 10, Volume III. Every aircraft registered in Zambia receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 8 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PFZ020 | Propflight Air Services | 25 | 2026-05-26 |
| PFZ023 | Propflight Air Services | 10 | 2026-05-26 |
| PFZ025 | Propflight Air Services | 4 | 2026-05-28 |
| PFZ024 | Propflight Air Services | 3 | 2026-05-28 |
| PFZ051 | Propflight Air Services | 1 | 2026-05-16 |
| PFZ050 | Propflight Air Services | 1 | 2026-05-09 |
| P0050 | - | 1 | 2026-05-16 |
| P0024 | - | 1 | 2026-05-17 |
Recent flights last 46
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | PFZ025 | JNB → LUN | May 28, 12:00 UTC | May 28, 12:30 UTC | 30m |
| 2026-05-28 | PFZ024 | LUN → JNB | May 28, 10:15 UTC | May 28, 10:50 UTC | 35m |
| 2026-05-26 | PFZ023 | JNB → LUN | May 26, 10:14 UTC | May 26, 10:50 UTC | 35m |
| 2026-05-26 | PFZ020 | LUN → JNB | May 26, 08:04 UTC | May 26, 08:34 UTC | 30m |
| 2026-05-25 | PFZ023 | JNB → LUN | May 25, 10:25 UTC | May 26, 08:34 UTC | 22h 9m |
| 2026-05-25 | PFZ020 | LUN → JNB | May 25, 07:25 UTC | May 25, 07:55 UTC | 30m |
| 2026-05-24 | PFZ025 | JNB → LUN | May 24, 12:05 UTC | May 25, 07:55 UTC | 19h 50m |
| 2026-05-24 | PFZ024 | LUN → JNB | May 24, 10:15 UTC | May 24, 10:45 UTC | 30m |
| 2026-05-17 | PFZ025 | JNB → LUN | May 17, 12:05 UTC | May 17, 12:35 UTC | 30m |
| 2026-05-17 | P0024 | - | May 17, 10:15 UTC | May 17, 10:55 UTC | 40m |
| 2026-05-16 | PFZ051 | CPT → LVI | May 16, 10:20 UTC | May 16, 10:46 UTC | 25m |
| 2026-05-16 | P0050 | - | May 16, 08:55 UTC | May 16, 09:16 UTC | 20m |
| 2026-05-12 | PFZ023 | JNB → LUN | May 12, 10:20 UTC | May 12, 10:55 UTC | 35m |
| 2026-05-12 | PFZ020 | LUN → JNB | May 12, 07:30 UTC | May 12, 08:00 UTC | 30m |
| 2026-05-10 | PFZ023 | JNB → LUN | May 10, 10:10 UTC | May 10, 10:45 UTC | 35m |
| 2026-05-10 | PFZ020 | LUN → JNB | May 10, 07:45 UTC | May 10, 08:20 UTC | 35m |
| 2026-05-09 | PFZ020 | LUN → JNB | May 9, 10:40 UTC | May 10, 08:20 UTC | 21h 40m |
| 2026-05-09 | PFZ050 | LVI → CPT | May 9, 09:00 UTC | May 9, 09:35 UTC | 35m |
| 2026-05-05 | PFZ023 | JNB → LUN | May 5, 10:10 UTC | May 5, 10:45 UTC | 35m |
| 2026-05-05 | PFZ020 | LUN → JNB | May 5, 07:35 UTC | May 5, 08:15 UTC | 40m |
| 2026-05-04 | PFZ020 | LUN → JNB | May 4, 10:30 UTC | May 5, 08:15 UTC | 21h 46m |
| 2026-05-04 | PFZ020 | LUN → JNB | May 4, 07:40 UTC | May 4, 08:20 UTC | 40m |
| 2026-05-03 | PFZ020 | LUN → JNB | May 3, 10:05 UTC | May 4, 08:20 UTC | 22h 15m |
| 2026-05-03 | PFZ020 | LUN → JNB | May 3, 07:30 UTC | May 3, 08:10 UTC | 40m |
| 2026-05-02 | PFZ020 | LUN → JNB | May 2, 10:15 UTC | May 3, 08:10 UTC | 21h 54m |
| 2026-05-02 | PFZ020 | LUN → JNB | May 2, 07:30 UTC | May 2, 08:00 UTC | 30m |
| 2026-04-30 | PFZ025 | JNB → LUN | Apr 30, 12:00 UTC | Apr 30, 12:35 UTC | 35m |
| 2026-04-30 | PFZ024 | LUN → JNB | Apr 30, 10:15 UTC | Apr 30, 10:50 UTC | 35m |
| 2026-04-27 | PFZ023 | JNB → LUN | Apr 27, 10:40 UTC | Apr 27, 11:10 UTC | 30m |
| 2026-04-27 | PFZ020 | LUN → JNB | Apr 27, 07:35 UTC | Apr 27, 08:20 UTC | 45m |
| 2026-04-26 | PFZ020 | LUN → JNB | Apr 26, 10:15 UTC | Apr 27, 08:20 UTC | 22h 5m |
| 2026-04-26 | PFZ020 | LUN → JNB | Apr 26, 07:45 UTC | Apr 26, 08:30 UTC | 45m |
| 2026-04-21 | PFZ023 | JNB → LUN | Apr 21, 10:05 UTC | Apr 21, 10:35 UTC | 30m |
| 2026-04-21 | PFZ020 | LUN → JNB | Apr 21, 07:30 UTC | Apr 21, 08:10 UTC | 40m |
| 2026-04-20 | PFZ020 | LUN → JNB | Apr 20, 10:10 UTC | Apr 21, 08:10 UTC | 22h 0m |
| 2026-04-20 | PFZ020 | LUN → JNB | Apr 20, 07:25 UTC | Apr 20, 08:00 UTC | 35m |
| 2026-04-19 | PFZ020 | LUN → JNB | Apr 19, 10:15 UTC | Apr 20, 08:00 UTC | 21h 45m |
| 2026-04-19 | PFZ020 | LUN → JNB | Apr 19, 07:30 UTC | Apr 19, 08:05 UTC | 35m |
| 2026-04-18 | PFZ020 | LUN → JNB | Apr 18, 10:15 UTC | Apr 19, 08:05 UTC | 21h 50m |
| 2026-04-18 | PFZ020 | LUN → JNB | Apr 18, 07:25 UTC | Apr 18, 08:00 UTC | 35m |
| 2026-04-16 | PFZ023 | JNB → LUN | Apr 16, 09:59 UTC | Apr 16, 10:29 UTC | 30m |
| 2026-04-16 | PFZ020 | LUN → JNB | Apr 16, 07:29 UTC | Apr 16, 08:09 UTC | 40m |
| 2026-04-14 | PFZ023 | - | Apr 14, 10:25 UTC | Apr 14, 10:55 UTC | 30m |
| 2026-04-14 | PFZ020 | LUN → JNB | Apr 14, 07:35 UTC | Apr 14, 08:15 UTC | 40m |
| 2026-04-13 | PFZ023 | - | Apr 13, 10:30 UTC | Apr 13, 11:00 UTC | 30m |
| 2026-04-13 | PFZ020 | LUN → JNB | Apr 13, 07:25 UTC | Apr 13, 08:00 UTC | 35m |
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 9J-PFE page for operator, model, and routing details .