sensors Mode-S transponder
C00A99
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-FEAI · DE HAVILLAND DHC-8-300 Dash 8 · operated by Air Inuit Ltd. Air Inuit Ltee
- Hex
- C00A99
- Octal
- 60005231
- Decimal
- 12,585,625
- Country
- CA
- Tail
- C-FEAI
- Type
- DH8C
- Flights observed
- 87
- Distinct callsigns
- 20
- Country
- CA
- Last broadcast
- 19h ago
Last known position
Country allocation
The ICAO 24-bit address C00A99 falls within the block assigned to Canada (CA) by ICAO Annex 10, Volume III. Every aircraft registered in Canada 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 |
|---|---|---|---|
| AIE833 | - | 10 | 2026-07-04 |
| AIE832 | Air Inuit | 10 | 2026-07-03 |
| AIE802 | - | 10 | 2026-07-10 |
| AIE803 | - | 8 | 2026-07-01 |
| AIE855 | - | 4 | 2026-07-06 |
| AIE896 | - | 3 | 2026-06-26 |
| AIE0832 | - | 3 | 2026-04-16 |
| AIE8Q3 | - | 2 | 2026-06-16 |
| AIE895 | Air Inuit | 2 | 2026-06-26 |
| AIE867 | Air Inuit | 2 | 2026-06-04 |
| AIE866 | Air Inuit | 2 | 2026-04-27 |
| AIE864 | - | 2 | 2026-04-23 |
| AIE860 | Air Inuit | 2 | 2026-05-28 |
| AIE859 | Air Inuit | 2 | 2026-05-27 |
| AIE853 | Air Inuit | 2 | 2026-06-27 |
| AIE850 | - | 2 | 2026-07-08 |
| AIE835 | - | 2 | 2026-05-28 |
| AIE834 | - | 2 | 2026-05-28 |
| AIE805 | - | 2 | 2026-07-13 |
| AIE804 | - | 2 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AIE805 | - | Jul 13, 21:20 UTC | Jul 13, 22:10 UTC | 50m |
| 2026-07-10 | AIE802 | - | Jul 10, 12:50 UTC | Jul 10, 13:45 UTC | 55m |
| 2026-07-08 | AIE850 | - | Jul 8, 18:05 UTC | Jul 8, 19:00 UTC | 55m |
| 2026-07-06 | AIE855 | - | Jul 6, 15:15 UTC | Jul 6, 16:05 UTC | 50m |
| 2026-07-06 | AIE855 | YUL → YQB | Jul 6, 13:45 UTC | Jul 6, 14:20 UTC | 35m |
| 2026-07-04 | AIE833 | - | Jul 4, 21:25 UTC | Jul 4, 22:00 UTC | 35m |
| 2026-07-04 | AIE833 | - | Jul 4, 20:35 UTC | Jul 4, 20:50 UTC | 15m |
| 2026-07-03 | AIE832 | YUL → YQB | Jul 3, 13:30 UTC | Jul 3, 15:05 UTC | 1h 35m |
| 2026-07-01 | AIE803 | - | Jul 1, 01:25 UTC | Jul 1, 02:15 UTC | 50m |
| 2026-06-28 | AIE802 | - | Jun 28, 13:00 UTC | Jun 28, 13:55 UTC | 55m |
| 2026-06-27 | AIE804 | - | Jun 27, 23:45 UTC | Jun 28, 00:39 UTC | 55m |
| 2026-06-27 | AIE853 | YYZ → YTS | Jun 27, 15:14 UTC | Jun 27, 16:10 UTC | 55m |
| 2026-06-26 | AIE896 | - | Jun 26, 23:44 UTC | Jun 27, 00:20 UTC | 35m |
| 2026-06-26 | AIE896 | - | Jun 26, 21:45 UTC | Jun 26, 23:04 UTC | 1h 20m |
| 2026-06-26 | AIE896 | - | Jun 26, 19:24 UTC | Jun 26, 19:55 UTC | 30m |
| 2026-06-26 | AIE895 | YUL → YGK | Jun 26, 15:54 UTC | Jun 26, 18:04 UTC | 2h 10m |
| 2026-06-26 | AIE895 | YUL → YGK | Jun 26, 14:25 UTC | Jun 26, 15:10 UTC | 45m |
| 2026-06-26 | AIE803 | - | Jun 26, 00:39 UTC | Jun 26, 01:29 UTC | 50m |
| 2026-06-23 | AIE802 | - | Jun 23, 12:49 UTC | Jun 23, 13:34 UTC | 45m |
| 2026-06-21 | AIE851 | YUY → YUL | Jun 21, 23:05 UTC | Jun 21, 23:55 UTC | 50m |
| 2026-06-20 | AIE850 | YMX → YUL | Jun 20, 23:25 UTC | Jun 21, 00:29 UTC | 1h 5m |
| 2026-06-16 | AIE8Q3 | - | Jun 16, 03:45 UTC | Jun 16, 04:30 UTC | 45m |
| 2026-06-13 | AIE8Q2 | YUL → YGW | Jun 13, 13:50 UTC | Jun 13, 14:40 UTC | 50m |
| 2026-06-11 | AIE8Q3 | - | Jun 11, 00:40 UTC | Jun 11, 01:35 UTC | 55m |
| 2026-06-06 | AIE802 | YGW → YUD | Jun 6, 13:05 UTC | Jun 6, 13:49 UTC | 45m |
| 2026-06-04 | AIE867 | YUL → YGW | Jun 4, 02:35 UTC | Jun 4, 03:30 UTC | 55m |
| 2026-06-03 | AIE803 | YGW → YUL | Jun 3, 13:00 UTC | Jun 3, 14:00 UTC | 1h 0m |
| 2026-06-02 | AIE803 | YGW → YUL | Jun 2, 23:05 UTC | Jun 2, 23:50 UTC | 45m |
| 2026-05-31 | AIE802 | YGW → YUD | May 31, 12:50 UTC | May 31, 13:50 UTC | 1h 0m |
| 2026-05-30 | AIE855 | YUL → YGW | May 30, 00:10 UTC | May 30, 00:55 UTC | 45m |
| 2026-05-29 | AIE853 | YYZ → YTS | May 29, 13:55 UTC | May 29, 14:45 UTC | 50m |
| 2026-05-28 | AIE835 | - | May 28, 22:30 UTC | May 28, 23:10 UTC | 40m |
| 2026-05-28 | AIE835 | - | May 28, 21:20 UTC | May 28, 21:40 UTC | 20m |
| 2026-05-28 | AIE834 | - | May 28, 16:55 UTC | May 28, 17:10 UTC | 15m |
| 2026-05-28 | AIE834 | YUL → YQB | May 28, 15:25 UTC | May 28, 16:00 UTC | 35m |
| 2026-05-28 | AIE860 | YQB → YUL | May 28, 00:00 UTC | May 28, 00:45 UTC | 45m |
| 2026-05-27 | AIE860 | YQB → YUL | May 27, 23:05 UTC | May 27, 23:25 UTC | 20m |
| 2026-05-27 | AIE859 | YGL → YUL | May 27, 15:50 UTC | May 27, 16:20 UTC | 30m |
| 2026-05-27 | AIE859 | YGL → YUL | May 27, 14:20 UTC | May 27, 15:00 UTC | 40m |
| 2026-05-25 | AIE803 | YGW → YUL | May 25, 22:19 UTC | May 25, 23:04 UTC | 45m |
| 2026-05-22 | AIE802 | YGW → YUD | May 22, 12:55 UTC | May 22, 13:50 UTC | 55m |
| 2026-05-21 | AIE803 | YGW → YUL | May 21, 22:50 UTC | May 21, 23:35 UTC | 45m |
| 2026-05-19 | AIE802 | YGW → YUD | May 19, 13:50 UTC | May 19, 14:40 UTC | 50m |
| 2026-05-18 | AIE803 | YGW → YUL | May 18, 23:10 UTC | May 18, 23:50 UTC | 40m |
| 2026-05-17 | AIE802 | YGW → YUD | May 17, 12:50 UTC | May 17, 13:45 UTC | 55m |
| 2026-05-14 | AIE854 | YQB → YUL | May 14, 21:50 UTC | May 14, 22:40 UTC | 50m |
| 2026-05-11 | AIE802 | YGW → YUD | May 11, 13:00 UTC | May 11, 13:35 UTC | 35m |
| 2026-05-05 | AIE833 | YQB → YUL | May 5, 23:10 UTC | May 5, 23:55 UTC | 45m |
| 2026-05-05 | AIE833 | YQB → YUL | May 5, 22:10 UTC | May 5, 22:30 UTC | 20m |
| 2026-05-05 | AIE832 | YUL → YQB | May 5, 13:40 UTC | May 5, 14:55 UTC | 1h 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 C-FEAI page for operator, model, and routing details .