The Jacksonville Jaguars visit the Baltimore Ravens on Thursday Night Football, giving fantasy managers a matchup with two very different offensive outlooks. Baltimore turns to Joe Fagnano after Lamar Jackson suffered a potentially season-ending thumb injury and Tyler Huntley was reportedly ruled out for the rest of the season with turf toe. Fagnano is dealing with a right ankle injury himself, although he practiced fully on Tuesday and is confirmed as Thursday’s starter.
Jacksonville has several appealing options, but Bhayshul Tuten’s availability requires attention after ankle and foot injuries kept him out of the first two practices. Here are my lineup locks, strong starts, players to sit, and toughest decision for Thursday Night Football.
Lineup Locks
- Bhayshul Tuten, RB (JAX) – If Tuten can’t play, Chris Rodriguez becomes a strong start this week.
- Trevor Lawrence, QB (JAX)
- Parker Washington, WR (JAX)
Strong Starts
Zay Flowers, WR (BAL)
Baltimore’s quarterback situation makes Zay Flowers considerably riskier than his season-long numbers suggest. Flowers has 40 receptions for 608 yards and three touchdowns, but his production has changed dramatically depending on who’s throwing the passes. In the available splits, his yards per route run fall from 7.67 with Lamar Jackson to 1.73 without him, while fantasy points per route drop from 1.42 to 0.39. His average target depth also falls from 10.5 yards to 6.4. Those are limited, uneven samples, but the decline makes it difficult to use his overall efficiency as evidence of a dependable floor with Fagnano.
The reason I’m still considering Flowers is his position as Baltimore’s primary receiving option. Jacksonville has surrendered yardage to opposing wideouts, and Flowers could accumulate shorter receptions if the Ravens simplify the offense and find themselves trailing. However, additional passing attempts won’t guarantee useful production if Baltimore struggles to complete passes and extend possessions. I’m treating Flowers as a volatile WR3 or flex option, with more appeal in PPR leagues than in formats that depend heavily on yardage and touchdowns. He remains the Ravens receiver I’d trust most, but this Strong Start designation comes with substantially less confidence than it would with Jackson available.
Sit ’Em
Jakobi Meyers, WR (JAX)
A favorable offensive environment doesn’t automatically make every Jacksonville receiver a dependable fantasy starter. Jakobi Meyers caught two passes for 24 yards against Indianapolis, finishing with 4.4 PPR points while Lawrence attempted just 14 passes. The limited team volume explains some of the disappointment, but Meyers hasn’t consistently commanded enough opportunities to protect against those quieter games. Lawrence has targeted him on 16.7% of his routes, leaving his weekly value vulnerable when Jacksonville spreads the ball around or controls the game without needing an aggressive passing approach.
Meyers also remained limited in Jacksonville’s first two practices with hamstring and ankle injuries, adding another consideration on a short turnaround. Baltimore can allow Jacksonville to score without necessarily creating enough receiving volume for multiple wideouts to deliver strong fantasy results. Washington is my preferred starting option, while Meyers needs either more concentrated targets or a touchdown to become comfortable in typical lineups. I’m sitting him in standard three-receiver leagues when a healthier player with a clearer workload is available. He remains a deeper flex consideration, but Jacksonville’s overall scoring potential shouldn’t be mistaken for a dependable individual floor.
Mark Andrews, TE (BAL)
Mark Andrews’ receiving production hasn’t provided much reason to trust him, even before accounting for Baltimore’s latest quarterback change. He caught three passes for 14 yards against Buffalo, finishing with 4.4 PPR points. Through Week 8, Andrews has 29 receptions for 218 yards and one touchdown while averaging just 1.15 yards per route run. That level of efficiency makes it difficult to generate a useful fantasy result without substantial target volume or a touchdown, and neither has been dependable enough to offset the limited yardage.
His role was already less secure than managers typically want from a starting tight end, with a 66.1% route participation rate entering Week 8. Now Baltimore is asking Fagnano to make his first start against a Jacksonville defense that has done a strong job keeping opponents off the scoreboard. Short receptions could help Andrews contribute, but simply being available underneath doesn’t guarantee enough catches to create starting value. I’m looking elsewhere at tight end because the combination of modest receiving efficiency and uncertain offensive production leaves him too dependent on scoring. His past fantasy success isn’t enough to justify starting him over an option with stronger current involvement.
Rashod Bateman, WR (BAL)
Rashod Bateman’s downfield role becomes much harder to trust when Baltimore struggles to complete passes. He caught one pass for 22 yards against Buffalo, accounting for his entire receiving production on a single play. His season-long profile also reflects a volatile secondary option: 19 catches for 288 yards, a 13.79-yard average depth of target and 1.43 yards per route run. Those deeper opportunities can produce a useful fantasy week when they connect, but the reception volume hasn’t supplied enough protection when they don’t.
Fagnano averaged just 4.3 yards per attempt in relief against Buffalo, which makes projecting consistent downfield success especially difficult. Bateman can remain involved in the offense without converting that playing time into fantasy production, and Flowers is the receiver I’m prioritizing when choosing where Baltimore’s limited passing opportunities might go. Jacksonville has surrendered receiving yardage, but taking advantage requires better execution than the Ravens showed Sunday. I’m sitting Bateman because his path to a useful result depends too heavily on an explosive reception or touchdown. He’s a speculative option in unusually deep formats rather than someone I’d trust to open the week in a typical starting lineup.
Ja’Kobi Lane, WR (BAL)
The early flashes from Ja’Kobi Lane haven’t developed into a dependable fantasy workload. He caught one pass for 13 yards against Buffalo after recording seven receptions for 65 yards across his previous two appearances. The latest game also left him behind Bateman in receiving participation, running routes on 67.7% of Baltimore’s dropbacks. That creates an additional obstacle beyond the quarterback concerns: Lane needs to earn opportunities while competing with receivers who are playing more consistently.
A trailing game script could create additional passing attempts, but that isn’t enough to make Baltimore’s third receiving option a comfortable fantasy play. Lane’s recent production hasn’t demonstrated the target volume necessary to withstand inefficient quarterback performance, and there’s little room for error if the Ravens struggle to reach scoring position. I’m keeping him on the bench because the current combination of playing time and offensive uncertainty makes his floor too low. He remains someone to monitor if his role expands or Baltimore’s passing situation improves, but Thursday’s matchup asks managers to project several positive developments at once.
Justice Hill, RB (BAL)
Eight targets against Buffalo gave Justice Hill a meaningful receiving opportunity, even though the production remained modest. He caught four passes for 20 yards and added three carries for 15 yards, finishing with 7.5 PPR points. That target total is worth acknowledging because it shows Baltimore was willing to involve him repeatedly while trailing. However, converting eight opportunities into just 20 receiving yards also demonstrates why an increase in checkdowns doesn’t automatically establish a dependable fantasy floor.
Hill improved from limited participation Monday to a full practice Tuesday after dealing with a groin issue, which is encouraging for his availability. He could again benefit from passing situations if Jacksonville establishes an early lead, but Henry remains the more established rushing option and Hill still needs efficient receptions or a scoring play to deliver a strong result. I’m sitting him in typical leagues because his receiving opportunities haven’t consistently translated into enough yardage to justify a flex start. He’s a deeper PPR fallback for managers short on alternatives, but I’d prefer a running back with a clearer combination of carries, receiving work and touchdown access.
Joe Fagnano, QB (BAL)
Baltimore is asking Joe Fagnano to make his first start under difficult circumstances. Against Buffalo, he completed 10 of 21 passes for 91 yards with an interception and a lost fumble, averaging 4.3 yards per attempt. He also suffered a right ankle injury, although his progression to full practice participation Tuesday is encouraging. Fagnano is confirmed as Thursday’s starter with Jackson out indefinitely and Huntley reportedly facing a season-ending turf toe injury. Preparing with the first-team offense should help, but the short turnaround and ankle issue add challenges to an already difficult assignment.
Jacksonville has allowed a passing touchdown on just 3.3% of opponent attempts and generated pressure on 39.2% of dropbacks. More attempts while trailing wouldn’t necessarily solve the problem if sacks and stalled possessions continue limiting production. Fagnano also supplied just three rushing yards against Buffalo, offering little additional fantasy value outside the passing game. I’m sitting him in one-quarterback leagues and treating him as an emergency option in superflex formats. Baltimore could simplify the offense and improve on Sunday’s results, but there isn’t enough demonstrated passing efficiency or rushing upside to make him a comfortable streamer against this defense.
Brian Thomas Jr., WR (JAX)
A touchdown against Indianapolis made Brian Thomas Jr.’s box score more appealing than his workload. His only reception went for a 12-yard score, producing 8.2 PPR points while he participated on just 47.4% of Lawrence’s dropbacks. That’s a difficult foundation for a starting receiver, particularly in an offense that has repeatedly won without needing substantial passing volume. Thomas’ ability to create a scoring play remains valuable, but one touchdown doesn’t establish that Jacksonville has restored a dependable receiving role.
Baltimore’s defensive struggles create an opportunity for Jacksonville’s offense, but Thomas still needs enough routes and targets to take advantage. A productive Jaguars performance could easily flow through Washington, the running backs, and other receiving options while leaving Thomas with another limited workload. I’m sitting him because the current opportunity share makes his production too dependent on finding the end zone. His talent gives him upside if the rotation changes, but managers should wait for stronger involvement before treating him as a routine starter. For Thursday, he’s a deeper touchdown-dependent option rather than a dependable WR3.
On the Fence
Derrick Henry, RB (BAL)
Derrick Henry still has the clearest rushing role in Baltimore, but the surrounding offense makes this a much tougher decision than usual. He rushed 11 times for 53 yards and a touchdown against Buffalo while catching two passes for seven yards, finishing with 14 PPR points. His established scoring responsibilities remain encouraging: through Week 7, Henry had handled 15 carries inside the five-yard line, accounting for 83% of Baltimore’s rushing attempts from that distance. However, he has received just one fourth-quarter touch over his last two games, illustrating how quickly his opportunities can disappear when Baltimore falls behind.
Jacksonville has allowed opposing running backs just 57.7 rushing yards per game, the fewest in the NFL, and 3.3 yards per carry, the second-fewest. Losing defensive tackle DaVon Hamilton for the season could weaken the interior run defense, providing some counterbalance to those difficult matchup numbers. Still, Henry needs Baltimore to remain competitive enough to sustain his workload and reach scoring position. I’m treating him as a riskier RB2 rather than an automatic start. If my alternatives have uncertain roles, I’m leaning toward Henry’s carries and touchdown access. In full PPR, a comparable back with steady receiving involvement becomes more appealing because of the risk that another early deficit limits Henry’s second-half opportunities.
