sensors Mode-S transponder
8002CC
ICAO 24-bit transponder address · allocated to India
Currently assigned to K3602 · EMBRAER EMB-135 Legacy
- Hex
- 8002CC
- Octal
- 40001314
- Decimal
- 8,389,324
- Country
- IN
- Tail
- K3602
- Type
- E35L
- Flights observed
- 85
- Distinct callsigns
- 4
- Country
- IN
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 8002CC falls within the block assigned to India (IN) by ICAO Annex 10, Volume III. Every aircraft registered in India 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 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | VUAVT | DEL → DEL | Jul 17, 13:00 UTC | Jul 17, 16:04 UTC | 3h 5m |
| 2026-07-17 | VUAVT | - | Jul 17, 02:59 UTC | Jul 17, 05:15 UTC | 2h 15m |
| 2026-07-16 | VUAVT | - | Jul 16, 10:35 UTC | Jul 16, 11:25 UTC | 50m |
| 2026-07-16 | VUAVT | - | Jul 16, 06:25 UTC | Jul 16, 06:40 UTC | 15m |
| 2026-07-16 | VUAVT | - | Jul 16, 04:55 UTC | Jul 16, 05:30 UTC | 35m |
| 2026-07-13 | VUAVT | DEL → DEL | Jul 13, 01:35 UTC | Jul 13, 05:40 UTC | 4h 5m |
| 2026-07-11 | VUAVT | - | Jul 11, 12:00 UTC | Jul 11, 13:55 UTC | 1h 55m |
| 2026-07-11 | VUAVT | - | Jul 11, 06:40 UTC | Jul 11, 08:35 UTC | 1h 55m |
| 2026-07-06 | VUAVT | CCU → DEL | Jul 6, 17:30 UTC | Jul 6, 19:20 UTC | 1h 50m |
| 2026-07-06 | VUAVT | - | Jul 6, 08:15 UTC | Jul 6, 10:10 UTC | 1h 55m |
| 2026-07-03 | IFC32 | - | Jul 3, 04:10 UTC | Jul 3, 20:40 UTC | 16h 30m |
| 2026-07-01 | VUAVT | DEL → DEL | Jul 1, 05:00 UTC | Jul 1, 08:25 UTC | 3h 25m |
| 2026-06-28 | VUAVT | - | Jun 28, 09:45 UTC | Jun 28, 16:00 UTC | 6h 15m |
| 2026-06-26 | VUAVT | - | Jun 26, 14:55 UTC | Jun 26, 18:15 UTC | 3h 20m |
| 2026-06-24 | VUAVT | - | Jun 24, 06:25 UTC | Jun 24, 07:05 UTC | 40m |
| 2026-06-22 | IFC1 | - | Jun 22, 02:30 UTC | Jun 22, 10:19 UTC | 7h 50m |
| 2026-06-21 | VUAVT | - | Jun 21, 09:00 UTC | Jun 21, 10:34 UTC | 1h 35m |
| 2026-06-20 | IFC1 | - | Jun 20, 05:14 UTC | Jun 20, 07:14 UTC | 2h 0m |
| 2026-06-19 | VUAVT | DEL → DEL | Jun 19, 18:44 UTC | Jun 19, 23:34 UTC | 4h 50m |
| 2026-06-17 | VUAVT | - | Jun 17, 15:20 UTC | Jun 17, 16:10 UTC | 50m |
| 2026-06-17 | VUAVT | - | Jun 17, 14:20 UTC | Jun 17, 14:30 UTC | 10m |
| 2026-06-16 | VUAVT | - | Jun 16, 13:44 UTC | Jun 16, 14:00 UTC | 15m |
| 2026-06-16 | VUAVT | - | Jun 16, 12:14 UTC | Jun 16, 12:55 UTC | 40m |
| 2026-06-13 | IFC1 | DEL → DEL | Jun 13, 03:05 UTC | Jun 13, 09:20 UTC | 6h 14m |
| 2026-06-12 | VUAVT | - | Jun 12, 06:55 UTC | Jun 12, 07:55 UTC | 1h 0m |
| 2026-06-12 | VUAVT | - | Jun 12, 04:10 UTC | Jun 12, 04:40 UTC | 30m |
| 2026-06-11 | VUAVT | - | Jun 11, 06:10 UTC | Jun 11, 06:50 UTC | 40m |
| 2026-06-11 | VUAVT | - | Jun 11, 03:05 UTC | Jun 11, 03:40 UTC | 35m |
| 2026-06-08 | VUAVT | - | Jun 8, 12:45 UTC | Jun 8, 15:00 UTC | 2h 15m |
| 2026-06-05 | IFC32 | - | Jun 5, 11:40 UTC | Jun 5, 14:15 UTC | 2h 35m |
| 2026-06-03 | IFC32 | - | Jun 3, 14:25 UTC | Jun 3, 16:15 UTC | 1h 50m |
| 2026-06-02 | VUAVT | DEL → DEL | Jun 2, 05:45 UTC | Jun 2, 10:00 UTC | 4h 15m |
| 2026-05-30 | VUAVT | - | May 30, 08:25 UTC | May 30, 09:25 UTC | 1h 0m |
| 2026-05-30 | VUAVT | - | May 30, 04:55 UTC | May 30, 05:20 UTC | 25m |
| 2026-05-29 | VUAVT | BHJ → DEL | May 29, 14:55 UTC | May 29, 16:30 UTC | 1h 35m |
| 2026-05-28 | VUAVT | - | May 28, 17:00 UTC | May 28, 17:30 UTC | 30m |
| 2026-05-27 | VUAVT | - | May 27, 14:05 UTC | May 27, 15:00 UTC | 55m |
| 2026-05-23 | VUAVT | - | May 23, 07:20 UTC | May 23, 14:30 UTC | 7h 10m |
| 2026-05-21 | IFC34 | GMP → DEL | May 21, 02:45 UTC | May 21, 13:10 UTC | 10h 25m |
| 2026-05-19 | IFC34 | - | May 19, 09:55 UTC | May 19, 10:45 UTC | 50m |
| 2026-05-18 | IFC34 | - | May 18, 04:55 UTC | May 18, 08:01 UTC | 3h 5m |
| 2026-05-15 | VUAVT | - | May 15, 11:00 UTC | May 15, 11:40 UTC | 40m |
| 2026-05-15 | VUAVT | - | May 15, 04:35 UTC | May 15, 04:50 UTC | 15m |
| 2026-05-14 | VUAVT | - | May 14, 15:25 UTC | May 14, 15:40 UTC | 15m |
| 2026-05-14 | VUAVT | - | May 14, 14:25 UTC | May 14, 14:35 UTC | 10m |
| 2026-05-14 | VUAVT | - | May 14, 12:25 UTC | May 14, 12:35 UTC | 10m |
| 2026-05-14 | VUAVT | - | May 14, 04:45 UTC | May 14, 05:35 UTC | 50m |
| 2026-05-12 | VUAVT | - | May 12, 08:25 UTC | May 12, 10:45 UTC | 2h 20m |
| 2026-05-11 | VUAVT | - | May 11, 11:30 UTC | May 11, 13:20 UTC | 1h 50m |
| 2026-05-08 | VUAVT | - | May 8, 14:10 UTC | May 8, 14:45 UTC | 35m |
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 K3602 page for operator, model, and routing details .