Joelton fire shut every eastbound I-24 lane; second crash added delays

Two obstructions disrupted the same morning drive into Nashville: a vehicle fire that shut every eastbound lane of Interstate 24 in Joelton, followed by a multi-vehicle crash just west of it. Traffic backed up for miles to Pleasant View, and drivers who left the interstate encountered congestion on the nearby route around the blockage, too. ²

The Tennessee Department of Transportation closed the eastbound lanes around 5:30 a.m. CDT on Friday, October 30, according to WSMV. The closure cut off inbound traffic at the fire location during the morning commute. It was a shutdown of all eastbound lanes there—not a reported closure of both directions of I-24. ¹

For drivers, the immediate questions are when they can get through and whether leaving the interstate offers any relief. The available reporting provides no clearance timetable, and no subsequent reopening has been verified. Whether anyone was hurt in either incident also remains unknown. Those limits matter: the early closure report is not proof that the lanes remain closed now. ²

WSMV’s fuller account adds an important detail to the initial report of a vehicle fire: the disruption involved a second incident on the same side of the interstate. The station described the crash as occurring afterward and just west of the fire, compounding the problems for traffic heading toward Nashville. ²

That sequence does not establish a cause. There is no verified account connecting the crash to the fire, and nothing in the report establishes that the crash caused the vehicle to burn. The number and types of vehicles involved have not been established beyond the description of a multi-vehicle crash. ²

The location is also less precise than drivers might need for a routing decision. The report identifies Joelton but supplies no exact mile marker. It describes the queue as stretching for miles to Pleasant View, without a measured length or a reliable estimate of how much time the disruption added to the journey. ²

Many motorists exited I-24 in Pleasant View and took Highway 49 to Highway 112, which runs alongside the interstate. WSMV reported that the volume of diverted traffic produced backups on that route as well. The warning extended to drivers coming from the Clarksville area toward Nashville. ²

That makes the alternate route part of the traffic problem, not a confirmed escape from it. The account establishes congestion on both the interstate and the nearby roads; it does not establish which choice was faster. There is no supported travel-time saving or additional-mileage figure to offer drivers. ²

The distinction is practical. A road can remain available while still being heavily delayed. Describing Highway 49 and Highway 112 simply as an alternative, without the reported backups, would leave out the very condition that made the choice difficult that morning.

The incident details come from WSMV’s account, published at 6:32 a.m. CDT, which identifies TDOT as the agency that closed the lanes. An independent, incident-specific transportation or emergency status record has not been verified. The fuller story supplies the crash and diversion details, but not a dated reopening announcement. ^{1 2}

The unresolved questions extend beyond traffic. There is no verified explanation for the fire, account of rescues, or confirmation of when it was extinguished. Most importantly, “unknown” injuries cannot be read as “no injuries.” The morning report left the human outcome unsettled as well as the clearance time. ²

The clearest account is therefore a bounded one: all eastbound lanes were closed at the Joelton fire location, a later crash added to the disruption, and diverted traffic backed up too. A confirmed reopening, an injury report and evidence that the alternate-route congestion has cleared are still needed to describe how the morning’s disruption ended. ²