sensors Mode-S transponder
08A0F3
ICAO 24-bit transponder address · allocated to Zambia
Currently assigned to 9J-PFA · BOMBARDIER Regional Jet CRJ-200
- Hex
- 08A0F3
- Octal
- 02120363
- Decimal
- 565,491
- Country
- ZM
- Tail
- 9J-PFA
- Type
- CRJ2
- Flights observed
- 49
- Distinct callsigns
- 12
- Country
- ZM
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 08A0F3 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 12 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PFZ020 | Propflight Air Services | 11 | 2026-05-30 |
| PFZ023 | Propflight Air Services | 10 | 2026-05-30 |
| PFZ024 | Propflight Air Services | 8 | 2026-05-27 |
| PFZ025 | Propflight Air Services | 5 | 2026-05-15 |
| PFZ309 | - | 4 | 2026-05-20 |
| PFZ911 | Propflight Air Services | 2 | 2026-05-10 |
| PFZ910 | - | 2 | 2026-06-01 |
| PFZ7580 | - | 2 | 2026-04-16 |
| PFZ311 | - | 2 | 2026-05-23 |
| PFZ919 | - | 1 | 2026-05-13 |
| P0025 | - | 1 | 2026-04-15 |
| P0024 | - | 1 | 2026-04-15 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | PFZ910 | - | Jun 1, 12:20 UTC | Jun 1, 12:50 UTC | 30m |
| 2026-06-01 | PFZ910 | - | Jun 1, 10:15 UTC | Jun 1, 10:45 UTC | 30m |
| 2026-05-30 | PFZ023 | JNB → LUN | May 30, 10:15 UTC | May 30, 10:45 UTC | 30m |
| 2026-05-30 | PFZ020 | LUN → JNB | May 30, 07:40 UTC | May 30, 08:15 UTC | 35m |
| 2026-05-29 | PFZ020 | LUN → JNB | May 29, 10:50 UTC | May 30, 08:15 UTC | 21h 25m |
| 2026-05-29 | PFZ023 | JNB → LUN | May 29, 10:20 UTC | May 30, 08:15 UTC | 21h 55m |
| 2026-05-29 | PFZ020 | LUN → JNB | May 29, 07:55 UTC | May 29, 08:25 UTC | 30m |
| 2026-05-27 | PFZ024 | LUN → JNB | May 27, 12:05 UTC | May 27, 12:40 UTC | 35m |
| 2026-05-27 | PFZ024 | LUN → JNB | May 27, 10:10 UTC | May 27, 10:40 UTC | 30m |
| 2026-05-23 | PFZ311 | - | May 23, 10:25 UTC | May 23, 11:00 UTC | 35m |
| 2026-05-23 | PFZ311 | - | May 23, 07:10 UTC | May 23, 07:40 UTC | 30m |
| 2026-05-22 | PFZ023 | JNB → LUN | May 22, 10:15 UTC | May 23, 07:40 UTC | 21h 24m |
| 2026-05-22 | PFZ020 | LUN → JNB | May 22, 07:30 UTC | May 22, 08:05 UTC | 35m |
| 2026-05-20 | PFZ309 | - | May 20, 12:05 UTC | May 20, 12:35 UTC | 30m |
| 2026-05-20 | PFZ309 | - | May 20, 10:20 UTC | May 20, 10:55 UTC | 35m |
| 2026-05-18 | PFZ023 | JNB → LUN | May 18, 10:25 UTC | May 18, 11:00 UTC | 35m |
| 2026-05-18 | PFZ020 | LUN → JNB | May 18, 07:35 UTC | May 18, 08:05 UTC | 30m |
| 2026-05-16 | PFZ309 | - | May 16, 10:20 UTC | May 16, 10:50 UTC | 30m |
| 2026-05-16 | PFZ309 | - | May 16, 07:35 UTC | May 16, 08:05 UTC | 30m |
| 2026-05-15 | PFZ025 | JNB → LUN | May 15, 12:15 UTC | May 16, 08:05 UTC | 19h 50m |
| 2026-05-15 | PFZ024 | LUN → JNB | May 15, 10:15 UTC | May 15, 10:45 UTC | 30m |
| 2026-05-13 | PFZ025 | JNB → LUN | May 13, 12:10 UTC | May 13, 12:40 UTC | 30m |
| 2026-05-13 | PFZ919 | - | May 13, 10:20 UTC | May 13, 10:50 UTC | 30m |
| 2026-05-11 | PFZ023 | JNB → LUN | May 11, 10:25 UTC | May 11, 10:55 UTC | 30m |
| 2026-05-11 | PFZ020 | LUN → JNB | May 11, 07:30 UTC | May 11, 08:05 UTC | 35m |
| 2026-05-10 | PFZ911 | LUN → JNB | May 10, 12:05 UTC | May 11, 08:05 UTC | 20h 0m |
| 2026-05-10 | PFZ911 | LUN → JNB | May 10, 10:10 UTC | May 10, 10:40 UTC | 30m |
| 2026-05-09 | PFZ023 | JNB → LUN | May 9, 10:15 UTC | May 9, 10:45 UTC | 30m |
| 2026-05-09 | PFZ020 | LUN → JNB | May 9, 07:35 UTC | May 9, 08:10 UTC | 35m |
| 2026-05-03 | PFZ025 | JNB → LUN | May 3, 12:10 UTC | May 3, 12:40 UTC | 30m |
| 2026-05-03 | PFZ024 | LUN → JNB | May 3, 10:20 UTC | May 3, 10:55 UTC | 35m |
| 2026-05-02 | PFZ025 | JNB → LUN | May 2, 12:10 UTC | May 3, 10:45 UTC | 22h 34m |
| 2026-05-02 | PFZ024 | LUN → JNB | May 2, 10:00 UTC | May 2, 10:40 UTC | 40m |
| 2026-04-30 | PFZ023 | JNB → LUN | Apr 30, 10:35 UTC | Apr 30, 11:05 UTC | 30m |
| 2026-04-30 | PFZ020 | LUN → JNB | Apr 30, 07:40 UTC | Apr 30, 08:50 UTC | 1h 10m |
| 2026-04-25 | PFZ024 | LUN → JNB | Apr 25, 12:10 UTC | Apr 25, 12:40 UTC | 30m |
| 2026-04-25 | PFZ024 | LUN → JNB | Apr 25, 10:15 UTC | Apr 25, 10:50 UTC | 35m |
| 2026-04-24 | PFZ023 | JNB → LUN | Apr 24, 10:10 UTC | Apr 24, 10:40 UTC | 30m |
| 2026-04-24 | PFZ020 | LUN → JNB | Apr 24, 07:40 UTC | Apr 24, 08:10 UTC | 30m |
| 2026-04-23 | PFZ023 | JNB → LUN | Apr 23, 10:10 UTC | Apr 24, 08:10 UTC | 21h 59m |
| 2026-04-23 | PFZ020 | LUN → JNB | Apr 23, 07:35 UTC | Apr 23, 08:15 UTC | 40m |
| 2026-04-20 | PFZ025 | JNB → LUN | Apr 20, 12:10 UTC | Apr 20, 12:45 UTC | 35m |
| 2026-04-20 | PFZ024 | LUN → JNB | Apr 20, 10:10 UTC | Apr 20, 10:50 UTC | 40m |
| 2026-04-17 | PFZ023 | JNB → LUN | Apr 17, 10:25 UTC | Apr 17, 10:55 UTC | 30m |
| 2026-04-17 | PFZ020 | LUN → JNB | Apr 17, 07:55 UTC | Apr 17, 08:25 UTC | 30m |
| 2026-04-16 | PFZ7580 | - | Apr 16, 12:00 UTC | Apr 16, 12:29 UTC | 30m |
| 2026-04-16 | PFZ7580 | - | Apr 16, 10:14 UTC | Apr 16, 10:54 UTC | 40m |
| 2026-04-15 | P0025 | - | Apr 15, 12:05 UTC | Apr 15, 12:35 UTC | 30m |
| 2026-04-15 | P0024 | - | Apr 15, 10:15 UTC | Apr 15, 10:55 UTC | 40m |
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-PFA page for operator, model, and routing details .