Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

0D8469

ICAO 24-bit transponder address · allocated to Venezuela

Currently assigned to YV3535 · AIRBUS A-340-600

Hex
0D8469
Octal
03302151
Decimal
885,865
Country
VE
Tail
YV3535
Type
A346
No current signal · last broadcast 2h ago
Flights observed
49
Distinct callsigns
6
Country
VE
Last broadcast
2h ago

Last known position

Most recent position reported by Mode-S 0D8469.

Country allocation

The ICAO 24-bit address 0D8469 falls within the block assigned to Venezuela (VE) by ICAO Annex 10, Volume III. Every aircraft registered in Venezuela 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 6 distinct

Callsign Airline Flights Last seen
VCV3727 Conviasa 13 2026-05-26
VCV3492 Conviasa 13 2026-05-29
VCV3726 Conviasa 10 2026-06-02
VCV3493 - 7 2026-05-13
VCV3496 Conviasa 5 2026-04-30
VCV3497 - 1 2026-04-16

Recent flights last 49

DateFlightRouteTakeoffLandingDuration
2026-06-02 VCV3726 CCS → NLU Jun 2, 14:50 UTCJun 2, 18:15 UTC3h 25m
2026-05-29 VCV3492 CCS → HAV May 29, 18:15 UTCMay 30, 00:45 UTC6h 30m
2026-05-27 VCV3492 CCS → HAV May 27, 18:20 UTCMay 28, 00:40 UTC6h 20m
2026-05-27 VCV3492 CCS → HAV May 27, 01:44 UTCMay 27, 18:50 UTC17h 5m
2026-05-26 VCV3727 NLU → CCS May 26, 22:25 UTCMay 27, 18:50 UTC20h 25m
2026-05-26 VCV3726 CCS → NLU May 26, 14:35 UTCMay 26, 18:55 UTC4h 20m
2026-05-22 VCV3492 CCS → HAV May 22, 18:45 UTCMay 23, 02:25 UTC7h 40m
2026-05-20 VCV3492 CCS → HAV May 20, 18:20 UTCMay 21, 00:50 UTC6h 30m
2026-05-20 VCV3492 CCS → HAV May 20, 01:55 UTCMay 20, 18:45 UTC16h 51m
2026-05-19 VCV3727 NLU → CCS May 19, 22:30 UTCMay 20, 18:45 UTC20h 16m
2026-05-19 VCV3726 CCS → NLU May 19, 15:05 UTCMay 19, 19:10 UTC4h 5m
2026-05-15 VCV3492 CCS → HAV May 15, 18:35 UTCMay 16, 01:00 UTC6h 25m
2026-05-13 VCV3493 - May 13, 07:05 UTCMay 14, 01:00 UTC17h 55m
2026-05-13 VCV3727 NLU → CCS May 13, 04:20 UTCMay 14, 01:00 UTC20h 40m
2026-05-13 VCV3727 NLU → CCS May 13, 03:40 UTCMay 14, 01:00 UTC21h 20m
2026-05-12 VCV3726 CCS → NLU May 12, 19:20 UTCMay 12, 23:10 UTC3h 50m
2026-05-08 VCV3493 - May 8, 18:05 UTCMay 9, 00:35 UTC6h 30m
2026-05-06 VCV3492 CCS → HAV May 6, 18:10 UTCMay 7, 00:30 UTC6h 20m
2026-05-06 VCV3727 NLU → CCS May 6, 01:45 UTCMay 7, 00:15 UTC22h 29m
2026-05-05 VCV3727 NLU → CCS May 5, 22:25 UTCMay 6, 18:35 UTC20h 9m
2026-05-05 VCV3726 CCS → NLU May 5, 14:55 UTCMay 5, 19:00 UTC4h 5m
2026-05-01 VCV3492 CCS → HAV May 1, 18:35 UTCMay 2, 00:55 UTC6h 20m
2026-04-30 VCV3496 CCS → HAV Apr 30, 00:20 UTCApr 30, 18:50 UTC18h 30m
2026-04-30 VCV3493 - Apr 30, 00:05 UTCApr 30, 18:50 UTC18h 45m
2026-04-29 VCV3493 - Apr 29, 18:30 UTCApr 30, 12:55 UTC18h 24m
2026-04-29 VCV3493 - Apr 29, 02:20 UTCApr 30, 00:35 UTC22h 15m
2026-04-29 VCV3727 NLU → CCS Apr 29, 00:20 UTCApr 30, 00:15 UTC23h 55m
2026-04-28 VCV3727 NLU → CCS Apr 28, 22:40 UTCApr 29, 18:55 UTC20h 16m
2026-04-28 VCV3726 CCS → NLU Apr 28, 15:10 UTCApr 28, 19:15 UTC4h 5m
2026-04-24 VCV3492 CCS → HAV Apr 24, 20:45 UTCApr 25, 03:05 UTC6h 20m
2026-04-23 VCV3496 CCS → HAV Apr 23, 00:20 UTCApr 23, 18:20 UTC18h 0m
2026-04-23 VCV3496 CCS → HAV Apr 23, 00:10 UTCApr 23, 18:20 UTC18h 10m
2026-04-22 VCV3496 CCS → HAV Apr 22, 18:20 UTCApr 23, 18:15 UTC23h 55m
2026-04-22 VCV3492 CCS → HAV Apr 22, 02:20 UTCApr 23, 00:30 UTC22h 10m
2026-04-22 VCV3727 NLU → CCS Apr 22, 02:05 UTCApr 23, 00:15 UTC22h 10m
2026-04-21 VCV3727 NLU → CCS Apr 21, 22:45 UTCApr 22, 18:40 UTC19h 55m
2026-04-21 VCV3726 CCS → NLU Apr 21, 14:45 UTCApr 21, 18:55 UTC4h 10m
2026-04-18 VCV3493 - Apr 18, 01:00 UTCApr 18, 01:15 UTC15m
2026-04-17 VCV3492 - Apr 17, 19:05 UTCApr 17, 19:20 UTC15m
2026-04-16 VCV3497 - Apr 16, 17:40 UTCApr 16, 18:05 UTC25m
2026-04-16 VCV3496 - Apr 16, 12:00 UTCApr 16, 12:09 UTC10m
2026-04-16 VCV3493 - Apr 16, 00:15 UTCApr 16, 00:40 UTC25m
2026-04-15 VCV3492 - Apr 15, 18:30 UTCApr 15, 18:50 UTC20m
2026-04-15 VCV3727 - Apr 15, 01:30 UTCApr 15, 01:50 UTC20m
2026-04-14 VCV3727 - Apr 14, 22:55 UTCApr 15, 00:15 UTC1h 20m
2026-04-14 VCV3727 - Apr 14, 22:15 UTCApr 14, 22:50 UTC35m
2026-04-14 VCV3726 CCS → NLU Apr 14, 18:55 UTCApr 14, 19:15 UTC20m
2026-04-14 VCV3726 CCS → NLU Apr 14, 17:20 UTCApr 14, 18:45 UTC1h 25m
2026-04-14 VCV3726 CCS → NLU Apr 14, 14:55 UTCApr 14, 15:20 UTC25m

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 YV3535 page for operator, model, and routing details .

Mode-S 0D8469 frequently asked

What is Mode-S code 0D8469?
0D8469 is an ICAO 24-bit transponder address. Allocated to Venezuela. Assigned to YV3535.
Where is Mode-S 0D8469 registered?
Mode-S code 0D8469 is allocated to Venezuela (VE). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0D8469 broadcasting right now?
No active broadcast right now. Last signal was 2h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0D8469, octal 03302151, decimal 885,865.
What flights does 0D8469 operate?
Mode-S 0D8469 has broadcast 6 distinct callsigns, including VCV3727, VCV3492, VCV3726, VCV3493, VCV3496.