sensors Mode-S transponder
C8809F
ICAO 24-bit transponder address · allocated to Fiji
Currently assigned to DQ-FAH · BOEING 737 MAX 8
- Hex
- C8809F
- Octal
- 62100237
- Decimal
- 13,140,127
- Country
- FJ
- Tail
- DQ-FAH
- Type
- B38M
- Flights observed
- 174
- Distinct callsigns
- 20
- Country
- FJ
- Last broadcast
- Jul 26, 10:25 UTC
Last known position
Country allocation
The ICAO 24-bit address C8809F 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FJI914 | Air Pacific | 17 | 2026-07-25 |
| FJI915 | - | 15 | 2026-07-14 |
| FJI921 | - | 13 | 2026-06-30 |
| FJI961 | - | 10 | 2026-07-15 |
| FJI960 | - | 10 | 2026-07-16 |
| FJI413 | - | 9 | 2026-07-18 |
| FJI951 | - | 8 | 2026-07-10 |
| FJI461 | - | 8 | 2026-07-10 |
| FJI981 | Air Pacific | 7 | 2026-07-22 |
| FJI950 | - | 7 | 2026-07-10 |
| FJI935 | Air Pacific | 7 | 2026-07-22 |
| FJI460 | - | 7 | 2026-06-25 |
| FJI820 | Air Pacific | 6 | 2026-07-26 |
| FJI451 | - | 6 | 2026-06-27 |
| FJI412 | - | 6 | 2026-07-18 |
| FJI930 | Air Pacific | 5 | 2026-07-24 |
| FJI920 | - | 5 | 2026-06-17 |
| FJI934 | Air Pacific | 4 | 2026-07-21 |
| FJI931 | Air Pacific | 4 | 2026-07-24 |
| FJI853 | - | 4 | 2026-06-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | FJI821 | HNL → NAN | Jul 26, 10:05 UTC | Jul 26, 10:25 UTC | 20m |
| 2026-07-26 | FJI820 | NAN → HNL | Jul 26, 07:45 UTC | Jul 26, 08:05 UTC | 20m |
| 2026-07-25 | FJI914 | SYD → NAN | Jul 25, 20:20 UTC | Jul 25, 21:10 UTC | 50m |
| 2026-07-25 | FJI450 | CHC → NAN | Jul 25, 01:25 UTC | Jul 25, 12:05 UTC | 10h 40m |
| 2026-07-24 | FJI930 | MEL → NAN | Jul 24, 14:00 UTC | Jul 25, 00:15 UTC | 10h 15m |
| 2026-07-24 | FJI931 | NAN → MEL | Jul 24, 08:25 UTC | Jul 24, 12:40 UTC | 4h 15m |
| 2026-07-23 | FJI980 | OOL → NAN | Jul 23, 02:35 UTC | Jul 23, 03:10 UTC | 35m |
| 2026-07-22 | FJI981 | NAN → OOL | Jul 22, 22:45 UTC | Jul 23, 01:00 UTC | 2h 15m |
| 2026-07-22 | FJI935 | NAN → MEL | Jul 22, 00:25 UTC | Jul 22, 02:05 UTC | 1h 40m |
| 2026-07-21 | FJI935 | NAN → MEL | Jul 21, 03:50 UTC | Jul 22, 02:05 UTC | 22h 15m |
| 2026-07-21 | FJI934 | MEL → NAN | Jul 21, 03:40 UTC | Jul 22, 01:45 UTC | 22h 5m |
| 2026-07-21 | FJI935 | NAN → MEL | Jul 21, 00:10 UTC | Jul 21, 01:50 UTC | 1h 40m |
| 2026-07-20 | FJI935 | NAN → MEL | Jul 20, 05:30 UTC | Jul 21, 01:50 UTC | 20h 20m |
| 2026-07-20 | FJI935 | NAN → MEL | Jul 20, 02:40 UTC | Jul 21, 01:45 UTC | 23h 5m |
| 2026-07-19 | FJI821 | - | Jul 19, 10:10 UTC | Jul 19, 10:25 UTC | 15m |
| 2026-07-19 | FJI820 | NAN → HNL | Jul 19, 07:40 UTC | Jul 19, 08:00 UTC | 20m |
| 2026-07-18 | FJI412 | - | Jul 18, 19:10 UTC | Jul 18, 19:40 UTC | 30m |
| 2026-07-18 | FJI413 | - | Jul 18, 03:40 UTC | Jul 18, 11:20 UTC | 7h 40m |
| 2026-07-17 | FJI930 | - | Jul 17, 13:50 UTC | Jul 18, 11:20 UTC | 21h 31m |
| 2026-07-17 | FJI930 | MEL → AKL | Jul 17, 13:40 UTC | Jul 18, 11:20 UTC | 21h 41m |
| 2026-07-17 | FJI931 | NAN → MEL | Jul 17, 08:20 UTC | Jul 17, 12:04 UTC | 3h 45m |
| 2026-07-16 | FJI960 | - | Jul 16, 03:00 UTC | Jul 16, 05:05 UTC | 2h 5m |
| 2026-07-15 | FJI961 | - | Jul 15, 23:20 UTC | Jul 16, 01:25 UTC | 2h 5m |
| 2026-07-14 | FJI914 | - | Jul 14, 20:25 UTC | Jul 14, 21:20 UTC | 55m |
| 2026-07-14 | FJI915 | - | Jul 14, 10:40 UTC | Jul 14, 11:50 UTC | 1h 10m |
| 2026-07-13 | FJI970 | - | Jul 13, 01:15 UTC | Jul 13, 04:25 UTC | 3h 10m |
| 2026-07-12 | FJI916 | - | Jul 12, 04:30 UTC | Jul 13, 01:30 UTC | 21h 0m |
| 2026-07-12 | FJI917 | - | Jul 12, 01:25 UTC | Jul 12, 02:35 UTC | 1h 10m |
| 2026-07-11 | FJI917 | WLG → SYD | Jul 11, 04:20 UTC | Jul 12, 02:35 UTC | 22h 15m |
| 2026-07-10 | FJI461 | - | Jul 10, 19:10 UTC | Jul 11, 02:55 UTC | 7h 45m |
| 2026-07-10 | FJI950 | - | Jul 10, 02:45 UTC | Jul 10, 11:25 UTC | 8h 40m |
| 2026-07-10 | FJI951 | - | Jul 10, 00:05 UTC | Jul 10, 01:25 UTC | 1h 20m |
| 2026-07-08 | FJI914 | - | Jul 8, 20:20 UTC | Jul 8, 21:10 UTC | 50m |
| 2026-07-07 | FJI915 | - | Jul 7, 19:10 UTC | Jul 8, 12:10 UTC | 17h 0m |
| 2026-07-06 | FJI413 | - | Jul 6, 19:15 UTC | Jul 7, 11:00 UTC | 15h 45m |
| 2026-07-06 | FJI980 | OOL → NAN | Jul 6, 02:40 UTC | Jul 6, 11:05 UTC | 8h 25m |
| 2026-07-05 | FJI981 | NAN → OOL | Jul 5, 10:50 UTC | Jul 6, 01:20 UTC | 14h 30m |
| 2026-07-04 | FJI820 | - | Jul 4, 19:25 UTC | Jul 5, 08:15 UTC | 12h 50m |
| 2026-07-04 | FJI980 | OOL → NAN | Jul 4, 02:25 UTC | Jul 4, 11:40 UTC | 9h 15m |
| 2026-07-03 | FJI930 | - | Jul 3, 14:25 UTC | Jul 4, 01:10 UTC | 10h 45m |
| 2026-07-02 | FJI931 | - | Jul 2, 20:35 UTC | Jul 3, 13:00 UTC | 16h 25m |
| 2026-07-01 | FJI915 | SYD → SYD | Jul 1, 20:30 UTC | Jul 2, 12:00 UTC | 15h 30m |
| 2026-07-01 | FJI915 | BNE → SYD | Jul 1, 01:50 UTC | Jul 1, 12:05 UTC | 10h 15m |
| 2026-06-30 | FJI921 | - | Jun 30, 22:00 UTC | Jul 1, 00:10 UTC | 2h 10m |
| 2026-06-29 | FJI914 | - | Jun 29, 20:44 UTC | Jun 29, 21:39 UTC | 55m |
| 2026-06-29 | FJI915 | - | Jun 29, 02:54 UTC | Jun 29, 12:29 UTC | 9h 35m |
| 2026-06-28 | FJI981 | NAN → OOL | Jun 28, 05:49 UTC | Jun 29, 01:25 UTC | 19h 35m |
| 2026-06-28 | FJI981 | NAN → OOL | Jun 28, 05:34 UTC | Jun 29, 01:25 UTC | 19h 50m |
| 2026-06-27 | FJI451 | - | Jun 27, 19:45 UTC | Jun 28, 04:05 UTC | 8h 20m |
| 2026-06-27 | FJI960 | - | Jun 27, 03:09 UTC | Jun 27, 05:25 UTC | 2h 15m |
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-FAH page for operator, model, and routing details .