This counter records the number of frames tail-dropped at this flow point during the archived historical interval. A historical spike here tells the admin exactly which past interval experienced buffer overflow severe enough to lose whole frames at that flow point. For example, if a customer references choppy service from two days ago, the admin would check that day's cmFlowPointHistoryFTD value to confirm frame loss occurred on their flow point.