Titans release defensive lineman Jordan Elliott after facility incident
Summarised from 2 outlets · Updated 20 Oct, 17:57 · Archive
Tennessee released seventh-year defensive lineman Jordan Elliott on Tuesday following an unspecified incident at the team facility.
The Tennessee Titans released seventh-year defensive lineman Jordan Elliott on Tuesday following an incident at the team facility the previous Thursday. The franchise did not disclose specifics of the incident, stating it would have no further comment on the matter.
Elliott, 28, had been signed to a two-year, $8 million deal in the offseason, reuniting him with Titans coach Robert Saleh, with whom he had spent the previous season with the San Francisco 49ers. He appeared in all five of the Titans' games before Week 6, recording 11 combined tackles. He was ruled out for the Week 6 game against the Colts for non-injury-related personal reasons and did not practise after the incident.
The release raises questions about Elliott's NFL future, though other teams' interest may depend on details of the incident that prompted Tennessee's decision. Elliott's career totals include 102 games played, 65 starts and five sacks across stints with Cleveland, San Francisco and Tennessee.
How it is being reported
- Titans cut lineman Jordan Elliott after mysterious ‘incident’ at team facilityThe Titans announced Tuesday they released the seventh-year defensive lineman following an "incident" at the team team facility last Thursday.New York Post · 20 Oct, 17:45
- Tennessee Titans release defensive lineman Jordan Elliott after mysterious 'incident' at team's facilityThe AFC South franchise confirmed the roster move on Tuesday morning, issuing a brief statement addressing the sudden departure of the veteran defender.Daily Mail Sport · 20 Oct, 15:28
In this story: Jordan Elliott · Tennessee Titans · Robert Saleh · San Francisco 49ers
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem
Comments (0)