Motorcyclist, 62, killed in Salisbury Township crash; Route 30 reopens

A 62-year-old motorcyclist died and another driver was hospitalized after a collision on Route 30 in Salisbury Township, Lancaster County, early Thursday, October 29. The highway has reopened, but investigators have not established in the available reporting why the two vehicles collided. ¹¹

The man was riding eastbound on the highway when his motorcycle collided with a westbound Chrysler 200 at the Simmontown Road intersection, LancasterOnline reported, citing Pennsylvania State Police. The impact threw him into the roadway. His name was not included in the reporting examined. ¹¹

The Chrysler’s driver was taken to Lancaster General Hospital with injuries that were not considered life-threatening. That is the latest condition established by the available reports; it does not establish whether the driver remained hospitalized or had since been discharged. ¹¹

Dispatchers placed the collision at 3:53 a.m. on Lincoln Highway, the road also designated Route 30, near Simmontown Road. LancasterOnline’s account, based on state police information, located it at the intersection. Those accounts describe the same early-morning collision in Salisbury Township. ^{2 11}

Emergency crews responded, and the Lancaster County Coroner’s Office was called to the scene. WGAL’s updated report described the crash as deadly and said police conducted a crash-reconstruction investigation. LancasterOnline’s police-based follow-up supplied the rider’s age and the other driver’s injury information. ^{1 2 11}

Route 30 was shut in both directions between Mount Vernon Road and White Horse Road for several hours while police investigated. Both WGAL’s updated account and LancasterOnline’s follow-up reported that the highway had reopened. An exact reopening time was not established in those accounts. ^{2 11}

That changes the practical message for motorists. The early Thursday report described an active closure and said the extent of injuries was unknown. The later reports establish a fatal collision, an injured sedan driver and a reopened road—not an ongoing shutdown. ^{1 2 11}

The sequence matters because the first account captured an emergency still unfolding. Its uncertainty about injuries has been overtaken by the subsequent reporting, just as its closure information has been overtaken by the reopening. Neither part of that initial account should be read as the latest status.

For people following the incident, two separate developments now define the story: the traffic disruption has ended, while the fatal-crash investigation remains unresolved. Reopening the highway allowed travel to resume; it did not supply an explanation for the collision or settle responsibility for it. ^{2 11}

The directions of travel are known, but they are not a finding of fault. An eastbound motorcycle and a westbound sedan collided at an intersection; the available police account does not explain the movements that brought them together. It would be premature to assign blame from those details alone. ¹¹

A state police spokesperson told LancasterOnline that the crash remained under investigation. No final explanation or charging announcement was established in the follow-up reporting examined. That is a limit on what can be reported here, not proof that authorities have issued no additional information. ^{11 41}

The coroner’s response likewise should not be mistaken for a published medical finding. The reporting establishes that the rider died in the crash, but it does not supply a medical cause or manner-of-death determination. Nor does it establish the rider’s identity beyond his age and sex. ^{2 11}

The next substantive developments would be a verified identification, police findings explaining the collision, any charging decision and an updated condition for the Chrysler’s driver. Until those are established, the account is a fatal collision with a known location and time—but an unresolved cause.