sensors Mode-S transponder
C8809D
ICAO 24-bit transponder address · allocated to Fiji
Currently assigned to DQ-FAJ · AIRBUS A-350-900
- Hex
- C8809D
- Octal
- 62100235
- Decimal
- 13,140,125
- Country
- FJ
- Tail
- DQ-FAJ
- Type
- A359
- Flights observed
- 146
- Distinct callsigns
- 14
- Country
- FJ
- Last broadcast
- Jul 26, 20:35 UTC
Last known position
Country allocation
The ICAO 24-bit address C8809D falls within the block assigned to Fiji (FJ) by ICAO Annex 10, Volume III. Every aircraft registered in Fiji 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FJI911 | Air Pacific | 37 | 2026-07-18 |
| FJI935 | Air Pacific | 28 | 2026-07-25 |
| FJI934 | Air Pacific | 19 | 2026-07-26 |
| FJI910 | Air Pacific | 17 | 2026-07-24 |
| FJI890 | - | 16 | 2026-07-18 |
| FJI891 | Air Pacific | 9 | 2026-07-19 |
| FJI811 | - | 7 | 2026-06-22 |
| FJI810 | Air Pacific | 3 | 2026-05-05 |
| FJI920 | Air Pacific | 2 | 2026-05-09 |
| FJI880 | Air Pacific | 2 | 2026-05-26 |
| FJI393 | - | 2 | 2026-07-22 |
| FJI392 | Air Pacific | 2 | 2026-07-23 |
| FJI881 | Air Pacific | 1 | 2026-05-27 |
| FJI411 | Air Pacific | 1 | 2026-04-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FJI934 | MEL → NAN | Jul 26, 04:00 UTC | Jul 26, 20:25 UTC | 16h 26m |
| 2026-07-25 | FJI935 | NAN → MEL | Jul 25, 07:25 UTC | Jul 26, 02:10 UTC | 18h 45m |
| 2026-07-24 | FJI910 | SYD → NAN | Jul 24, 04:30 UTC | Jul 24, 20:25 UTC | 15h 55m |
| 2026-07-23 | FJI392 | HKG → NAN | Jul 23, 09:40 UTC | Jul 24, 02:35 UTC | 16h 55m |
| 2026-07-22 | FJI393 | - | Jul 22, 19:35 UTC | Jul 22, 20:55 UTC | 1h 20m |
| 2026-07-20 | FJI934 | MEL → NAN | Jul 20, 04:00 UTC | Jul 20, 05:25 UTC | 1h 25m |
| 2026-07-19 | FJI935 | NAN → MEL | Jul 19, 07:20 UTC | Jul 20, 02:15 UTC | 18h 55m |
| 2026-07-19 | FJI891 | DFW → NAN | Jul 19, 05:20 UTC | Jul 20, 02:15 UTC | 20h 55m |
| 2026-07-18 | FJI890 | SYD → DFW | Jul 18, 03:35 UTC | Jul 18, 21:55 UTC | 18h 20m |
| 2026-07-18 | FJI911 | NAN → SYD | Jul 18, 00:39 UTC | Jul 18, 01:39 UTC | 1h 0m |
| 2026-07-17 | FJI911 | NAN → SYD | Jul 17, 05:20 UTC | Jul 18, 01:39 UTC | 20h 20m |
| 2026-07-17 | FJI891 | DFW → SYD | Jul 17, 04:49 UTC | Jul 18, 01:39 UTC | 20h 50m |
| 2026-07-16 | FJI890 | - | Jul 16, 03:30 UTC | Jul 16, 22:15 UTC | 18h 45m |
| 2026-07-16 | FJI910 | SYD → SYD | Jul 16, 03:20 UTC | Jul 16, 03:25 UTC | 5m |
| 2026-07-15 | FJI911 | - | Jul 15, 07:20 UTC | Jul 16, 01:30 UTC | 18h 10m |
| 2026-07-14 | FJI910 | - | Jul 14, 03:25 UTC | Jul 14, 20:10 UTC | 16h 45m |
| 2026-07-14 | FJI911 | - | Jul 14, 00:45 UTC | Jul 14, 01:35 UTC | 50m |
| 2026-07-13 | FJI934 | - | Jul 13, 05:20 UTC | Jul 14, 01:35 UTC | 20h 15m |
| 2026-07-13 | FJI934 | MEL → SYD | Jul 13, 04:40 UTC | Jul 14, 01:35 UTC | 20h 55m |
| 2026-07-12 | FJI935 | - | Jul 12, 07:25 UTC | Jul 13, 02:30 UTC | 19h 5m |
| 2026-07-11 | FJI934 | - | Jul 11, 03:50 UTC | Jul 11, 20:55 UTC | 17h 5m |
| 2026-07-11 | FJI935 | - | Jul 11, 00:10 UTC | Jul 11, 01:45 UTC | 1h 35m |
| 2026-07-10 | FJI891 | - | Jul 10, 04:20 UTC | Jul 11, 01:15 UTC | 20h 55m |
| 2026-07-09 | FJI890 | SYD → DFW | Jul 9, 03:50 UTC | Jul 9, 22:25 UTC | 18h 35m |
| 2026-07-09 | FJI911 | - | Jul 9, 00:45 UTC | Jul 9, 02:10 UTC | 1h 25m |
| 2026-07-08 | FJI911 | - | Jul 8, 05:20 UTC | Jul 9, 02:10 UTC | 20h 50m |
| 2026-07-08 | FJI911 | DFW → SYD | Jul 8, 04:55 UTC | Jul 9, 02:10 UTC | 21h 15m |
| 2026-07-07 | FJI890 | - | Jul 7, 20:40 UTC | Jul 7, 21:55 UTC | 1h 15m |
| 2026-07-06 | FJI934 | - | Jul 6, 04:25 UTC | Jul 6, 05:55 UTC | 1h 30m |
| 2026-07-06 | FJI935 | - | Jul 6, 00:40 UTC | Jul 6, 02:05 UTC | 1h 25m |
| 2026-07-05 | FJI935 | - | Jul 5, 05:20 UTC | Jul 6, 02:05 UTC | 20h 45m |
| 2026-07-05 | FJI935 | DFW → MEL | Jul 5, 05:00 UTC | Jul 6, 02:05 UTC | 21h 5m |
| 2026-07-04 | FJI890 | SYD → DFW | Jul 4, 03:45 UTC | Jul 4, 22:20 UTC | 18h 35m |
| 2026-07-04 | FJI911 | - | Jul 4, 00:35 UTC | Jul 4, 01:55 UTC | 1h 20m |
| 2026-07-03 | FJI911 | - | Jul 3, 05:20 UTC | Jul 4, 01:55 UTC | 20h 35m |
| 2026-07-03 | FJI911 | DFW → SYD | Jul 3, 04:55 UTC | Jul 4, 01:55 UTC | 21h 0m |
| 2026-07-02 | FJI890 | SYD → DFW | Jul 2, 03:35 UTC | Jul 2, 21:55 UTC | 18h 20m |
| 2026-07-01 | FJI911 | - | Jul 1, 07:20 UTC | Jul 2, 01:45 UTC | 18h 25m |
| 2026-07-01 | FJI911 | - | Jul 1, 07:00 UTC | Jul 2, 01:45 UTC | 18h 45m |
| 2026-06-30 | FJI910 | - | Jun 30, 03:40 UTC | Jun 30, 19:50 UTC | 16h 10m |
| 2026-06-30 | FJI911 | - | Jun 30, 00:14 UTC | Jun 30, 01:30 UTC | 1h 16m |
| 2026-06-29 | FJI911 | - | Jun 29, 05:20 UTC | Jun 30, 01:30 UTC | 20h 11m |
| 2026-06-29 | FJI934 | - | Jun 29, 04:00 UTC | Jun 30, 01:14 UTC | 21h 15m |
| 2026-06-28 | FJI935 | - | Jun 28, 07:29 UTC | Jun 29, 02:20 UTC | 18h 50m |
| 2026-06-27 | FJI934 | - | Jun 27, 04:09 UTC | Jun 27, 21:04 UTC | 16h 55m |
| 2026-06-27 | FJI935 | - | Jun 27, 00:20 UTC | Jun 27, 02:20 UTC | 2h 0m |
| 2026-06-26 | FJI935 | - | Jun 26, 05:19 UTC | Jun 27, 02:20 UTC | 21h 0m |
| 2026-06-26 | FJI935 | DFW → MEL | Jun 26, 04:45 UTC | Jun 27, 02:20 UTC | 21h 35m |
| 2026-06-25 | FJI890 | SYD → DFW | Jun 25, 03:50 UTC | Jun 25, 21:40 UTC | 17h 50m |
| 2026-06-25 | FJI911 | - | Jun 25, 01:04 UTC | Jun 25, 01:54 UTC | 50m |
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 DQ-FAJ page for operator, model, and routing details .