sensors Mode-S transponder

4D20D1

ICAO 24-bit transponder address · allocated to Malta

Currently assigned to 9H-VCA · BOMBARDIER BD-100 Challenger 350

Hex
4D20D1
Octal
23220321
Decimal
5,054,673
Country
MT
Tail
9H-VCA
Type
CL35
No current signal · last broadcast 6h ago
Flights observed
175
Distinct callsigns
4
Country
MT
Last broadcast
6h ago

Last known position

Most recent position reported by Mode-S 4D20D1.

Country allocation

The ICAO 24-bit address 4D20D1 falls within the block assigned to Malta (MT) by ICAO Annex 10, Volume III. Every aircraft registered in Malta 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

Callsign Airline Flights Last seen
VJT401 - 172 2026-07-19
VJT711Q - 1 2026-05-13
VJT696W - 1 2026-06-07
VJT438H - 1 2026-06-08

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-19 VJT401 - Jul 19, 18:30 UTCJul 19, 19:40 UTC1h 10m
2026-07-19 VJT401 - Jul 19, 15:40 UTCJul 19, 16:10 UTC30m
2026-07-19 VJT401 ZRH → AMS Jul 19, 13:40 UTCJul 19, 14:45 UTC1h 5m
2026-07-18 VJT401 - Jul 18, 16:40 UTCJul 18, 17:25 UTC45m
2026-07-18 VJT401 FLR → LBG Jul 18, 14:20 UTCJul 18, 15:50 UTC1h 30m
2026-07-18 VJT401 GVA → FLR Jul 18, 12:05 UTCJul 18, 12:45 UTC40m
2026-07-16 VJT401 JMK → GVA Jul 16, 17:35 UTCJul 16, 20:19 UTC2h 45m
2026-07-16 VJT401 - Jul 16, 15:25 UTCJul 16, 16:44 UTC1h 20m
2026-07-15 VJT401 - Jul 15, 16:55 UTCJul 15, 18:00 UTC1h 5m
2026-07-15 VJT401 - Jul 15, 12:45 UTCJul 15, 16:00 UTC3h 15m
2026-07-14 VJT401 - Jul 14, 16:40 UTCJul 14, 18:15 UTC1h 35m
2026-07-14 VJT401 - Jul 14, 15:00 UTCJul 14, 15:30 UTC30m
2026-07-14 VJT401 - Jul 14, 04:55 UTCJul 14, 05:45 UTC50m
2026-07-13 VJT401 - Jul 13, 11:45 UTCJul 13, 13:45 UTC2h 0m
2026-07-13 VJT401 - Jul 13, 08:20 UTCJul 13, 10:20 UTC2h 0m
2026-07-12 VJT401 - Jul 12, 19:01 UTCJul 12, 19:45 UTC45m
2026-07-12 VJT401 TLL → AMS Jul 12, 16:01 UTCJul 12, 18:01 UTC2h 0m
2026-07-12 VJT401 - Jul 12, 12:01 UTCJul 12, 14:20 UTC2h 20m
2026-07-11 VJT401 - Jul 11, 13:40 UTCJul 11, 14:00 UTC20m
2026-07-11 VJT401 - Jul 11, 09:15 UTCJul 11, 11:20 UTC2h 5m
2026-07-11 VJT401 - Jul 11, 07:15 UTCJul 11, 07:35 UTC20m
2026-06-26 VJT401 ATH → FAB Jun 26, 17:09 UTCJun 26, 20:24 UTC3h 15m
2026-06-26 VJT401 - Jun 26, 12:19 UTCJun 26, 15:39 UTC3h 20m
2026-06-25 VJT401 - Jun 25, 17:44 UTCJun 25, 19:34 UTC1h 50m
2026-06-25 VJT401 - Jun 25, 14:24 UTCJun 25, 15:24 UTC1h 0m
2026-06-25 VJT401 - Jun 25, 08:30 UTCJun 25, 09:10 UTC40m
2026-06-25 VJT401 - Jun 25, 06:44 UTCJun 25, 07:39 UTC55m
2026-06-24 VJT401 LIN → BLQ Jun 24, 08:24 UTCJun 24, 08:49 UTC25m
2026-06-24 VJT401 BTS → LIN Jun 24, 06:10 UTCJun 24, 07:10 UTC1h 0m
2026-06-24 VJT401 PRG → BTS Jun 24, 04:39 UTCJun 24, 05:20 UTC40m
2026-06-23 VJT401 - Jun 23, 12:45 UTCJun 23, 14:15 UTC1h 30m
2026-06-23 VJT401 VNO → CIA Jun 23, 09:14 UTCJun 23, 11:29 UTC2h 15m
2026-06-22 VJT401 - Jun 22, 15:24 UTCJun 22, 17:40 UTC2h 15m
2026-06-22 VJT401 LIN → LTN Jun 22, 12:44 UTCJun 22, 14:34 UTC1h 50m
2026-06-21 VJT401 - Jun 21, 19:14 UTCJun 21, 20:24 UTC1h 10m
2026-06-21 VJT401 - Jun 21, 15:09 UTCJun 21, 16:04 UTC55m
2026-06-21 VJT401 - Jun 21, 11:40 UTCJun 21, 14:15 UTC2h 35m
2026-06-21 VJT401 - Jun 21, 09:29 UTCJun 21, 10:19 UTC50m
2026-06-20 VJT401 - Jun 20, 16:14 UTCJun 20, 17:04 UTC50m
2026-06-20 VJT401 - Jun 20, 13:34 UTCJun 20, 14:54 UTC1h 20m
2026-06-20 VJT401 - Jun 20, 07:24 UTCJun 20, 10:34 UTC3h 10m
2026-06-19 VJT401 - Jun 19, 10:19 UTCJun 19, 14:59 UTC4h 40m
2026-06-18 VJT401 - Jun 18, 18:40 UTCJun 18, 19:25 UTC45m
2026-06-18 VJT401 - Jun 18, 16:40 UTCJun 18, 17:35 UTC55m
2026-06-17 VJT401 - Jun 17, 14:25 UTCJun 17, 15:30 UTC1h 5m
2026-06-17 VJT401 - Jun 17, 12:50 UTCJun 17, 13:30 UTC40m
2026-06-17 VJT401 BRN → STR Jun 17, 08:40 UTCJun 17, 09:10 UTC30m
2026-06-17 VJT401 NCL → BRN Jun 17, 05:40 UTCJun 17, 07:20 UTC1h 40m
2026-06-16 VJT401 - Jun 16, 11:49 UTCJun 16, 12:39 UTC50m
2026-06-16 VJT401 MXP → FAB Jun 16, 09:25 UTCJun 16, 11:00 UTC1h 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 9H-VCA page for operator, model, and routing details .

Mode-S 4D20D1 frequently asked

What is Mode-S code 4D20D1?
4D20D1 is an ICAO 24-bit transponder address. Allocated to Malta. Assigned to 9H-VCA.
Where is Mode-S 4D20D1 registered?
Mode-S code 4D20D1 is allocated to Malta (MT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 4D20D1 broadcasting right now?
No active broadcast right now. Last signal was 6h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 4D20D1, octal 23220321, decimal 5,054,673.
What flights does 4D20D1 operate?
Mode-S 4D20D1 has broadcast 4 distinct callsigns, including VJT401, VJT711Q, VJT696W, VJT438H.