Narrative:

Low ceilings; pilot training; poor radar updates due to new fusion system. While working position; I had numerous IFR practice approaches along with a few itinerant jet arrivals. While vectoring aircraft X for sequence for the ILS 7L; I had to break aircraft X off the approach due to an over take on the aircraft ahead of him. I had aircraft Y on a downwind to follow aircraft X. I had issued aircraft Y a base leg turn but radar still showed that aircraft Y was on the downwind and it appeared due to the radar lag in fusion that aircraft Y had not begun the turn or was turning at a very slow rate. I issued aircraft X a 050 heading which would have given me course divergence on both the aircraft on final and aircraft Y. However again due to the lag in updates under fusion; I noticed that aircraft Y went from a downwind track to a base leg track with no updates in between which made it impossible to know exactly where aircraft Y [was] due to this lag in updates. This is a very serious problem with fusion. You cannot anticipate an aircraft's rate of turn which allows you to determine weather or not the aircraft is turning or how fast or slow the aircraft is turning. This is a very critical element at dab due to the numerous training aircraft that we work. We quite often have to deal with student pilots that read back our instructions but do not follow them or are very slow in doing so. Discontinue the use of fusion until all aspects of the system have been corrected including the adsb equipment required in the aircraft that make the system work. Currently no aircraft in our area are equipped with the correct version of adsb.

Google
 

Original NASA ASRS Text

Title: DAB Controller voiced concern regarding the time lag in the Fusion RADAR system; making the identification of aircraft positions less than desired.

Narrative: Low ceilings; pilot training; poor RADAR updates due to new Fusion system. While working position; I had numerous IFR practice approaches along with a few itinerant jet arrivals. While vectoring Aircraft X for sequence for the ILS 7L; I had to break Aircraft X off the approach due to an over take on the aircraft ahead of him. I had Aircraft Y on a downwind to follow Aircraft X. I had issued Aircraft Y a base leg turn but RADAR still showed that Aircraft Y was on the downwind and it appeared due to the RADAR lag in Fusion that Aircraft Y had not begun the turn or was turning at a very slow rate. I issued Aircraft X a 050 heading which would have given me course divergence on both the aircraft on final and Aircraft Y. however again due to the lag in updates under Fusion; I noticed that Aircraft Y went from a downwind track to a base leg track with no updates in between which made it impossible to know exactly where Aircraft Y [was] due to this lag in updates. This is a very serious problem with Fusion. You cannot anticipate an aircraft's rate of turn which allows you to determine weather or not the aircraft is turning or how fast or slow the aircraft is turning. This is a very critical element at DAB due to the numerous training aircraft that we work. We quite often have to deal with student pilots that read back our instructions but do not follow them or are very slow in doing so. Discontinue the use of Fusion until all aspects of the system have been corrected including the ADSB equipment required in the aircraft that make the system work. Currently no aircraft in our area are equipped with the correct version of ADSB.

Data retrieved from NASA's ASRS site as of July 2013 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.