Second VDL2 frequency active in USA

Status
Not open for further replies.

ATCTech

Active Member
Joined
Aug 13, 2002
Messages
1,857
CONFIRMED 136.650 is active in the Cleveland, Ohio area. Aircraft logged and confirmed positions from the ECK area of Michigan (north of DTW) to the Cleveland area to slightly east of Pittsburgh. I believe this is the first posted confirmation of a second active VDL2 frequency in North America.

All traffic seen so far has been using address 11512A as the destination ground station.

Cheers!

Bob

Sample decodes from DumpVDL2:

[2018-10-11 01:47:54 GMT] [136.650] [-5.2/-46.1 dBFS] [40.9 dB] [-2.8 ppm]
AAED0D (Aircraft, Airborne) -> 11512A (Ground station): Command
AVLC type: I sseq: 3 rseq: 3 poll: 0
ACARS:
Reg: .N803AL Flight: AA0042
Mode: 2 Label: 5Z Blk id: 1 Ack: ! Msg no.: M29A
Message:
OS LIPZ /FTMTHE.TURB.REPORTS.ALL
SEEM.TO.BE.ABOVE.330
DO.YOU.THINK.WE
WOULD.BE.OK.AT.310

[2018-10-11 01:52:22 GMT] [136.650] [-27.4/-45.9 dBFS] [18.5 dB] [4.7 ppm]
A557C3 (Aircraft, Airborne) -> 11512A (Ground station): Command
AVLC type: I sseq: 0 rseq: 0 poll: 0
ACARS:
Reg: .N443WN Flight: WN1831
Mode: 2 Label: 37 Blk id: 4 Ack: ! Msg no.: M36A
Message:
09UCQHI
AQTOKAFQ(
RPC/VC/CWDOA/2P
 
D

DaveNF2G

Guest
I am receiving VDL2 on 136.650 in the Albany, NY, area (KALB).

Later I will set up side-by-side monitoring and try to figure out the traffic distribution.
 

ATCTech

Active Member
Joined
Aug 13, 2002
Messages
1,857
What G/S address are the downlink messages routing to Dave? I've had it running here all day and it's been 11512A exclusively.

Bob
 

kma371

QRT
Joined
Feb 20, 2001
Messages
6,204
Picking it up in the San Francisco Bay Area as well. Not hearing the ground station, but aircraft are communicating to 1131EA.
 

AirScan

Member
Joined
Feb 13, 2007
Messages
2,831
(from the other thread)

According to the FCC database 136.650 is active at the following airports (from East to West) -

JFK, LGA, EWR, PHL, DTW, BNA, MDW, ORD, STL, PHX, LAS, SAN, LAX, OAK.

https://fjallfoss.fcc.gov/General_Me...?accessible=NO

So far we have ...

11512A - probably DTW (received in Toronto and Ottawa)
1131EA - probably OAK (received in San Francisco and Reno)

Based on these two it seems 136.650 ARINC GS ID is 11xxxx vs 10xxxx on 136.975

AS
 

EricCottrell

Member
Premium Subscriber
Joined
Nov 8, 2002
Messages
2,413
Location
Boston, Ma
Hello,

In the emission field of FCC licenses, 6K00A3E is Voice, 13K0A2D is ACARS, and 14K0G1D is VDL2.

There are two nationwide mobile licenses that have 14K0G1D listed on frequencies from 136.500 to 136.975 (25 KHz steps). I found several licenses for voice on 136.500 in New England, but the only licensed VDL2 Frequency is 136.975. However, there is a pending license modication for VDL2 on 136.800.

It turns out 136.800 is the secondary SITA frequency for VDL2. It is currently licensed at:
Code:
KOE3	LOS ANGELES INTL AIRPORT	33-56-30.8 N, 118-24-07.7 W
KPD97	ST LOUIS INTERNATIONAL AIRPORT	38-44-54.1 N, 090-20-47.3 W	
KPE8	FORT LAUDERDALE-HOLLYWOOD AIRPORT	26-04-09.0 N, 080-09-21.3 W		
KSU73	CHICAGO OHARE INTERNATIONAL AIRPORT	41-58-30.2 N, 087-54-22.9 W	
WPTA590	Washington Dulles International Airport 38-56-55.3 N, 077-27-03.8 W	
WPVS825 5800 Blue Lagoon Dr Miami, FL 	25-46-55.3 N, 080-17-30.0 W
WQAD500	Philadelphia International Airport	39-53-27.5 N, 075-14-00.1 W	
WQDR976 Hartsfield-Jackson Atlanta 		33-39-21.1 N, 084-25-26.3 W		
WQDU856 Orlando International Airport		28-25-52.2 N, 081-18-24.7 W		
WQEG284 Dallas Ft Worth International Airport	32-53-57.3 N, 097-02-09.4 W	
WQEW396	Tampa Intl Airport	27-58-49.4 N, 082-32-03.5 W	
WQGZ716 LaGuardia Airport 		40-46-12.0 N, 073-51-40.0 W		
WQK6	LOS ANGELES INTL AIRPORT	33-56-32.0 N, 118-24-34.0 W	
WQLF455 Memphis International Airport 	35-02-59.0 N, 089-58-43.0 W
WQYE696 Chicago Midway International Airport	41-47-12.7 N, 087-45-40.3 W

136.650 is likely the secondary ARINC frequency for VDL2.

73 Eric
 
D

DaveNF2G

Guest
The license modification might be to harmonize the name of the official licensee, as SITA now handles all licensing within the FCC's jurisdiction.
 

EricCottrell

Member
Premium Subscriber
Joined
Nov 8, 2002
Messages
2,413
Location
Boston, Ma
Hello,

In reviewing my logs from my Bowie Trip, I see there is quite a bit of activity on 136.650. It seemed to be in the DE, MD, and VA area.

It appears several aircraft started to try connecting to a too distant ground station on 136.650 when at only 1000 feet. The nearest ground station on 136.650 in the Washington, DC area is 11126A and aircraft successfully communicated with it. I could also get frames from the 101126A station on 136.976. I saw aircraft trying to connect to 11340a 11341a and 11346a, but did not appear successful.

I also captured a couple of autotune to 136.650 transmissions from several ground stations to aircraft.

[2018-12-27 20:02:06 EST] [136.650] [-39.8/-52.0 dBFS] [12.2 dB] [1.1 ppm]
A23200 (Aircraft, Airborne) -> 11126A (Ground station): Command
AVLC: type: U (XID) P/F: 1
XID: Handoff Initiation
Public params:
Parameter set ID: 8885:1993
Procedure classes: 00 01
HDLC options: 20 84 80
VDL params:
Parameter set ID: V
XID sequencing: 02
Destination airport: KBNA
Aircraft location: 39.4N 78.2W 37000 ft
AVLC specific options: 24
Connection management: 01


[2018-12-27 20:02:07 EST] [136.650] [-39.4/-51.8 dBFS] [12.4 dB] [1.3 ppm]
A23200 (Aircraft, Airborne) -> 11126A (Ground station): Command
AVLC type: I sseq: 0 rseq: 0 poll: 0
ACARS:
Reg: .N240WN Flight: WN6059
Mode: 2 Label: H1 Blk id: 6 Ack: ! Msg no.: D80A
Message:
#DFB++76502,240,B737-700,181228,WN6059,KPHL,KBNA,0197,SW1804
6
N3956.2,W07608.4,280045,22237,-22.3,262,045,CL,00000,0,
N3952.6,W07633.2,280048,27390,-35.8,262,044,CL,00000,0,
N3945.8,W07658.8,280051,32926,-


[2018-12-27 20:15:08 EST] [136.650] [-41.7/-52.1 dBFS] [10.4 dB] [-0.9 ppm]
A73410 (Aircraft, Airborne) -> 11126A (Ground station): Command
AVLC: type: U (XID) P/F: 1
XID: Handoff Initiation
Public params:
Parameter set ID: 8885:1993
Procedure classes: 00 01
HDLC options: 20 84 80
VDL params:
Parameter set ID: V
XID sequencing: 04
Destination airport: KATL
Aircraft location: 38.4N 78.2W 38000 ft
AVLC specific options: 24
Connection management: 01


[2018-12-27 21:13:34 EST] [136.975] [-14.0/-51.5 dBFS] [37.6 dB] [-1.1 ppm]
104CDA (Ground station, On ground) -> AA159E (Aircraft): Command
AVLC: type: U (XID) P/F: 0
XID: Handoff Request / Broadcast Handoff
Public params:
Parameter set ID: 8885:1993
Procedure classes: 00 01
HDLC options: 20 84 80
N1-downlink: 07 d8
N1-uplink: 07 d8
VDL params:
Parameter set ID: V
Connection management: 01
XID sequencing: 00
AVLC specific options: 20
Autotune frequency: 136.650 MHz (VDL-M2, D8PSK, 31500 bps)
Replacement ground stations: 11126A
ATN router NETs: 00 00 00 00 00 00 "......"
System mask: fc 02 00 00


[2018-12-27 22:12:58 EST] [136.975] [-32.9/-51.3 dBFS] [18.4 dB] [-2.1 ppm]
1054BA (Ground station, On ground) -> A2195D (Aircraft): Command
AVLC: type: U (XID) P/F: 0
XID: Handoff Request / Broadcast Handoff
Public params:
Parameter set ID: 8885:1993
Procedure classes: 00 01
HDLC options: 20 84 80
N1-downlink: 07 d8
N1-uplink: 07 d8
VDL params:
Parameter set ID: V
Connection management: 01
XID sequencing: 00
AVLC specific options: 20
Autotune frequency: 136.650 MHz (VDL-M2, D8PSK, 31500 bps)
Replacement ground stations: 11126A
ATN router NETs: 00 00 00 00 00 00 "......"
System mask: fc 02 00 00


[2018-12-28 17:23:07 EST] [136.975] [-43.9/-51.7 dBFS] [7.8 dB] [-0.8 ppm]
10509A (Ground station, On ground) -> A388A9 (Aircraft): Command
AVLC: type: U (XID) P/F: 0
XID: Handoff Request / Broadcast Handoff
Public params:
Parameter set ID: 8885:1993
Procedure classes: 00 01
HDLC options: 20 84 80
N1-downlink: 07 d8
N1-uplink: 07 d8
VDL params:
Parameter set ID: V
Connection management: 01
XID sequencing: 00
AVLC specific options: 20
Autotune frequency: 136.650 MHz (VDL-M2, D8PSK, 31500 bps)
Replacement ground stations: 11126A
ATN router NETs: 00 00 00 00 00 00 "......"
System mask: fc 02 00 00


73 Eric
 

EricCottrell

Member
Premium Subscriber
Joined
Nov 8, 2002
Messages
2,413
Location
Boston, Ma
Hello,

It looks like SITA is doing some work in the New York City area. In the log this evening I see activity on 136.800 from aircraft sending messages to these ground stations. I did not see any activity when I went through the area just before New Years.

22DE41 KEWR
261C21 KLGA

[2019-02-02 19:11:41 EST] [136.800] [-29.7/-51.0 dBFS] [21.2 dB] [-0.6 ppm] [S:0] [L:44] [F:0] [#0]
A8DD7B (Aircraft, Airborne) -> 261C21 (Ground station): Command
AVLC type: I sseq: 0 rseq: 0 poll: 0
ACARS:
Reg: .N670UA Flight: UA0019
Mode: 2 Label: Q0 Blk id: 6 Ack: ! Msg no.: S46A
Message:

[2019-02-02 19:11:42 EST] [136.800] [-29.9/-51.2 dBFS] [21.3 dB] [-0.6 ppm] [S:0] [L:55] [F:0] [#0]
A8DD7B (Aircraft, Airborne) -> 261C21 (Ground station): Command
AVLC type: I sseq: 1 rseq: 1 poll: 0
ACARS:
Reg: .N670UA Flight: UA0019
Mode: 2 Label: SA Blk id: 7 Ack: ! Msg no.: M18A
Message:
0E20010422S
Media Advisory, version 0:
Link VDL2 established at 00:10:42 UTC
Available links: VDL2, Default SATCOM

[2019-02-02 19:13:14 EST] [136.800] [-31.5/-50.6 dBFS] [19.2 dB] [-0.6 ppm] [S:0] [L:44] [F:0] [#0]
A8DD7B (Aircraft, Airborne) -> 22DE41 (Ground station): Command
ff ff 01 32 ae ce b6 37 b0 d5 c1 15 51 b0 38 02 d3 34 37 c1 d5 c1 b0 b0 31 b9 83 64 f1 7f
AVLC type: I sseq: 0 rseq: 0 poll: 0
ACARS:
Reg: .N670UA Flight: UA0019
Mode: 2 Label: Q0 Blk id: 8 Ack: ! Msg no.: S47A
Message:

[2019-02-02 19:13:15 EST] [136.800] [-31.2/-51.2 dBFS] [20.0 dB] [-0.7 ppm] [S:0] [L:14] [F:0] [#0]
A8DD7B (Aircraft, Airborne) -> 22DE41 (Ground station): Response
AVLC: type: S (Receive Ready) P/F: 0 rseq: 1

73 Eric
 

EricCottrell

Member
Premium Subscriber
Joined
Nov 8, 2002
Messages
2,413
Location
Boston, Ma
Hello,

JFK appeared on 136.800 shortly after I posted my previous message, of course.

251961 KJFK

No activity heard on 136.650 in my listening area.

73 Eric
 

AirScan

Member
Joined
Feb 13, 2007
Messages
2,831
Eric,

Are you still getting anything on 136.800 in the Boston area ?

Recent logs from the Florida and New York area are not showing any traffic on 136.800 now. Anyone on the forum here in the central/southern Florida area monitoring VDL2 ?

AS
 
D

DaveNF2G

Guest
I think there might be sporadic testing on other channels from time to time, as well as the occasional misconfiguring of a new ground station that directs aircraft to use a frequency that is unassigned.
 

xantegh

Member
Joined
Sep 11, 2017
Messages
81
Location
Washington
Gents,

is there a document that explains the content of the VDL2 Messages?

[#6 (F:136.975 P:-08.5) 10/07/2019 07:15:30.018 --------------------------------

Command from Aircraft:A5DEE3 (airborne) to GroundD:10150A

Frame-I: Ns:3 Nr:1

ACARS

Aircraft reg: N478AS Flight id: AS0024

Mode: 2 Msg. label: H1

Block id: 0 Ack: !

Msg. no: D93A

Message :

#DFBA3M5100715KSEAKBOSN47258W1213881193M001213031G0009N47257W1213551263M001215032G0009N47257W1213221343M002204039G0009N47256W1212901417M006206042G0009N47256W1212561481M007210045G0009A0101
 
D

DaveNF2G

Guest
Alaska Airlines flight 24 transmitting its intended path between Seattle and Boston.
 

AirScan

Member
Joined
Feb 13, 2007
Messages
2,831
is there a document that explains the content of the VDL2 Messages?

You can find some basic information here to get the general idea. (You can scroll through the topics using the "Navigator" window on the right side of the page).

http://acarsonline.pbworks.com/w/page/1286714/About ACARS

A lot of message formats are specific to each airline company. If you break them down and compare them to other similar type message you can usually figure out what they mean.

#DFBA3M5100715KSEAKBOSN47258W1213881193M001213031G0009N47257W1213551263M001215032G0009N47257W1213221343M002204039G0009N47256W1212901417M006206042G0009N47256W1212561481M007210045G0009A0101

The example you posted is a type of position report. My guesses.

#DFB = message header
A3M = message type identifier
5 = message sequence
10 = date (day)
0715 = time (07:15 UTC)
KSEA KBOS = route (Seattle to Boston)
N47258 W121388 1193 M001 213031 G0009
N47257 W121355 1263 M001 215032 G0009
N47257 W121322 1343 M002 204039 G0009
N47256 W121290 1417 M006 206042 G0009
N47256 W121256 1481 M007 210045 G0009
A0101 = message type identifier ?

N47258 = longitude
W121388 = latitude
1193 = altitude (11,93x feet)
M001 = temperature -1C
213031 = wind direction and speed (213 degrees at 31 knots)
G0009 = ? (have also seen B0009)
 
Status
Not open for further replies.
Top