A corporate jet pilot reported the vny runway 16R ILS/localizer frequency 111.3 erroneously reported...

Attributes
ACN	1370657
Time
Date	201607
Local Time Of Day	1201-1800
Place
Locale Reference	VNY.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Light Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Component
Aircraft Component	DME
Person 1
Function	Captain Pilot Not Flying
Qualification	Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 124 Flight Crew Total 3089 Flight Crew Type 1486
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy

Narrative:

While established on a visual approach to runway 16R at van nuys; we observed intermittent; incorrect DME readings on both NAV1 and NAV2 while tuned to i-vny; runway 16R localizer 111.30 mhz. These indications showed a DME reading of 86.3 NM while on a 6.4 NM final at 3450 feet (established on the localizer and glideslope).I-vny does not have DME associated with the localizer according to current aeronautical charts. Upon selecting DME1 and DME2 on the audio panel; we heard a single dash tone every 30 - 40 seconds but not a full morse code identification. On subsequent flights; we have observed continuous erroneous DME information from i-vny when tuned to the facility both on departure and also on arrival. Both DME1 and DME2 in our aircraft provide correct distance readings when tuned to other navaids.these incorrect DME indications could be misleading to flight crews who are not familiar with van nuys airport or the ILS 16R approach. Perhaps there is some type of signal interference from another NAVAID causing these incorrect DME indications; which could be investigated by techops and frequency management.

Original NASA ASRS Text

Title: A corporate jet pilot reported the VNY Runway 16R ILS/LOC frequency 111.3 erroneously reported an 86.3 DME on a 6.4 NM final at 3;450 feet. The I-VNY ILS/LOC does not transmit a DME signal and so the false DME can be confusing for some flight crews.

Narrative: While established on a visual approach to Runway 16R at Van Nuys; we observed intermittent; incorrect DME readings on both NAV1 and NAV2 while tuned to I-VNY; Runway 16R Localizer 111.30 Mhz. These indications showed a DME reading of 86.3 NM while on a 6.4 NM final at 3450 feet (established on the localizer and glideslope).I-VNY does not have DME associated with the localizer according to current aeronautical charts. Upon selecting DME1 and DME2 on the audio panel; we heard a single dash tone every 30 - 40 seconds but not a full Morse code identification. On subsequent flights; we have observed continuous erroneous DME information from I-VNY when tuned to the facility both on departure and also on arrival. Both DME1 and DME2 in our aircraft provide correct distance readings when tuned to other Navaids.These incorrect DME indications could be misleading to flight crews who are not familiar with Van Nuys airport or the ILS 16R approach. Perhaps there is some type of signal interference from another NAVAID causing these incorrect DME indications; which could be investigated by TechOps and Frequency Management.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

A corporate jet pilot reported the vny runway 16R ILS/localizer frequency 111.3 erroneously reported an 86.3 DME on a 6.4 NM final at 3;450 feet. The i-vny ILS/localizer does not transmit a DME signal and so the false DME can be confusing for some flight crews.