sensors Mode-S transponder
C880A9
ICAO 24-bit transponder address · allocated to Fiji
Currently assigned to DQ-FAN · AIRBUS A-350-900
- Hex
- C880A9
- Octal
- 62100251
- Decimal
- 13,140,137
- Country
- FJ
- Tail
- DQ-FAN
- Type
- A359
- Flights observed
- 55
- Distinct callsigns
- 9
- Country
- FJ
- Last broadcast
- 11d ago
Last known position
Country allocation
The ICAO 24-bit address C880A9 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 9 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FJI935 | Air Pacific | 11 | 2026-05-04 |
| FJI911 | Air Pacific | 9 | 2026-05-13 |
| FJI934 | Air Pacific | 8 | 2026-05-04 |
| FJI891 | Air Pacific | 8 | 2026-05-17 |
| FJI890 | Air Pacific | 8 | 2026-05-16 |
| FJI910 | Air Pacific | 6 | 2026-05-12 |
| FJI811 | Air Pacific | 3 | 2026-05-11 |
| FJI810 | Air Pacific | 1 | 2026-04-16 |
| FJI2007 | Air Pacific | 1 | 2026-05-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-18 | FJI2007 | NAN → HKG | May 18, 06:45 UTC | May 18, 08:01 UTC | 1h 15m |
| 2026-05-17 | FJI891 | DFW → NAN | May 17, 04:10 UTC | May 17, 07:00 UTC | 2h 50m |
| 2026-05-16 | FJI890 | NAN → DFW | May 16, 21:25 UTC | May 16, 22:40 UTC | 1h 15m |
| 2026-05-16 | FJI890 | NAN → DFW | May 16, 02:30 UTC | May 16, 22:40 UTC | 20h 10m |
| 2026-05-15 | FJI891 | DFW → NAN | May 15, 06:20 UTC | May 16, 00:40 UTC | 18h 19m |
| 2026-05-15 | FJI891 | DFW → NAN | May 15, 04:50 UTC | May 16, 00:40 UTC | 19h 49m |
| 2026-05-14 | FJI890 | NAN → DFW | May 14, 03:35 UTC | May 14, 21:30 UTC | 17h 55m |
| 2026-05-13 | FJI911 | NAN → SYD | May 13, 07:15 UTC | May 14, 01:50 UTC | 18h 35m |
| 2026-05-12 | FJI910 | SYD → NAN | May 12, 03:40 UTC | May 12, 19:35 UTC | 15h 55m |
| 2026-05-11 | FJI811 | LAX → NAN | May 11, 07:15 UTC | May 11, 07:45 UTC | 30m |
| 2026-05-10 | FJI910 | SYD → NAN | May 10, 03:35 UTC | May 10, 19:40 UTC | 16h 5m |
| 2026-05-09 | FJI911 | NAN → SYD | May 9, 07:15 UTC | May 10, 01:45 UTC | 18h 30m |
| 2026-05-08 | FJI910 | SYD → NAN | May 8, 04:25 UTC | May 8, 20:05 UTC | 15h 40m |
| 2026-05-07 | FJI911 | NAN → SYD | May 7, 07:20 UTC | May 8, 01:55 UTC | 18h 35m |
| 2026-05-06 | FJI910 | SYD → NAN | May 6, 03:35 UTC | May 6, 19:55 UTC | 16h 19m |
| 2026-05-05 | FJI911 | NAN → SYD | May 5, 07:50 UTC | May 6, 01:35 UTC | 17h 45m |
| 2026-05-04 | FJI934 | MEL → NAN | May 4, 04:00 UTC | May 4, 20:30 UTC | 16h 31m |
| 2026-05-04 | FJI935 | NAN → MEL | May 4, 00:05 UTC | May 4, 02:00 UTC | 1h 55m |
| 2026-05-03 | FJI935 | NAN → MEL | May 3, 04:20 UTC | May 4, 02:00 UTC | 21h 40m |
| 2026-05-03 | FJI935 | NAN → MEL | May 3, 04:05 UTC | May 4, 02:00 UTC | 21h 55m |
| 2026-05-02 | FJI890 | NAN → DFW | May 2, 04:20 UTC | May 2, 22:10 UTC | 17h 50m |
| 2026-05-02 | FJI911 | NAN → SYD | May 2, 00:25 UTC | May 2, 01:35 UTC | 1h 10m |
| 2026-05-01 | FJI891 | DFW → NAN | May 1, 04:20 UTC | May 2, 01:35 UTC | 21h 15m |
| 2026-04-30 | FJI890 | NAN → DFW | Apr 30, 03:30 UTC | Apr 30, 21:05 UTC | 17h 35m |
| 2026-04-29 | FJI911 | NAN → SYD | Apr 29, 07:35 UTC | Apr 30, 01:15 UTC | 17h 40m |
| 2026-04-28 | FJI910 | SYD → NAN | Apr 28, 03:30 UTC | Apr 28, 19:50 UTC | 16h 20m |
| 2026-04-27 | FJI911 | NAN → SYD | Apr 27, 06:20 UTC | Apr 28, 01:05 UTC | 18h 45m |
| 2026-04-27 | FJI911 | NAN → SYD | Apr 27, 05:20 UTC | Apr 28, 01:05 UTC | 19h 45m |
| 2026-04-26 | FJI891 | DFW → NAN | Apr 26, 08:20 UTC | Apr 27, 03:50 UTC | 19h 30m |
| 2026-04-26 | FJI891 | DFW → NAN | Apr 26, 07:55 UTC | Apr 27, 03:50 UTC | 19h 55m |
| 2026-04-25 | FJI910 | SYD → NAN | Apr 25, 03:45 UTC | Apr 25, 21:20 UTC | 17h 35m |
| 2026-04-24 | FJI911 | NAN → SYD | Apr 24, 07:20 UTC | Apr 25, 01:10 UTC | 17h 50m |
| 2026-04-23 | FJI934 | MEL → NAN | Apr 23, 04:05 UTC | Apr 23, 20:40 UTC | 16h 35m |
| 2026-04-23 | FJI935 | NAN → MEL | Apr 23, 00:10 UTC | Apr 23, 02:15 UTC | 2h 5m |
| 2026-04-22 | FJI935 | NAN → MEL | Apr 22, 04:20 UTC | Apr 23, 02:15 UTC | 21h 55m |
| 2026-04-22 | FJI935 | NAN → MEL | Apr 22, 03:55 UTC | Apr 23, 02:15 UTC | 22h 20m |
| 2026-04-21 | FJI890 | NAN → DFW | Apr 21, 19:55 UTC | Apr 21, 21:45 UTC | 1h 50m |
| 2026-04-20 | FJI934 | MEL → NAN | Apr 20, 04:05 UTC | Apr 20, 05:25 UTC | 1h 20m |
| 2026-04-19 | FJI935 | NAN → MEL | Apr 19, 07:25 UTC | Apr 20, 02:10 UTC | 18h 45m |
| 2026-04-18 | FJI934 | MEL → NAN | Apr 18, 05:25 UTC | Apr 18, 05:40 UTC | 15m |
| 2026-04-18 | FJI934 | MEL → NAN | Apr 18, 04:45 UTC | Apr 18, 05:40 UTC | 55m |
| 2026-04-18 | FJI934 | MEL → NAN | Apr 18, 04:10 UTC | Apr 18, 20:45 UTC | 16h 35m |
| 2026-04-18 | FJI935 | NAN → MEL | Apr 18, 01:25 UTC | Apr 18, 02:20 UTC | 55m |
| 2026-04-18 | FJI935 | NAN → MEL | Apr 18, 00:40 UTC | Apr 18, 01:20 UTC | 40m |
| 2026-04-17 | FJI811 | LAX → NAN | Apr 17, 07:25 UTC | Apr 17, 07:55 UTC | 30m |
| 2026-04-16 | FJI810 | NAN → LAX | Apr 16, 20:00 UTC | Apr 16, 20:35 UTC | 35m |
| 2026-04-16 | FJI934 | MEL → NAN | Apr 16, 05:09 UTC | Apr 16, 05:39 UTC | 30m |
| 2026-04-16 | FJI934 | MEL → NAN | Apr 16, 04:20 UTC | Apr 16, 05:05 UTC | 45m |
| 2026-04-16 | FJI935 | NAN → MEL | Apr 16, 01:10 UTC | Apr 16, 02:19 UTC | 1h 10m |
| 2026-04-16 | FJI935 | NAN → MEL | Apr 16, 00:20 UTC | Apr 16, 01:05 UTC | 45m |
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-FAN page for operator, model, and routing details .