1 injured in crash between car, light-rail train in Castle Shannon
Two people were briefly trapped inside a car in Castle Shannon when the vehicle and a T train car collided on Tuesday at a track crossing, officials said.
The crash occurred at 11:25 a.m. on Cook's Lane near the Arlington stop and Mt. Lebanon Boulevard. The car was traveling toward Mt. Lebanon Boulevard, police said.
An inbound red line train pinned the car against the guardrail. Emergency responders helped the two people inside the car get out, Port Authority officials and police said.
Flashing lights warn motorists not to cross the tracks when a T train is approaching, but the crossing is not equipped with a control arm that automatically lowers to prevent cars from crossing the tracks.
“Witnesses did say the lights were flashing so we don't know why the car crossed,” Castle Shannon police Chief Ken Truver said.
One of the car's passengers was taken to St. Clair Hospital in Mt. Lebanon with non-life-threatening injuries, Port Authority spokesman Jim Ritchie said.
The red line was closed in both directions for less than an hour between Mt. Lebanon and Castle Shannon.
Bobby Kerlik is a staff writer for Trib Total Media. He can be reached at 412-320-7886 or firstname.lastname@example.org.
Show commenting policy
TribLive commenting policy
You are solely responsible for your comments and by using TribLive.com you agree to our Terms of Service.
We moderate comments. Our goal is to provide substantive commentary for a general readership. By screening submissions, we provide a space where readers can share intelligent and informed commentary that enhances the quality of our news and information.
While most comments will be posted if they are on-topic and not abusive, moderating decisions are subjective. We will make them as carefully and consistently as we can. Because of the volume of reader comments, we cannot review individual moderation decisions with readers.
We value thoughtful comments representing a range of views that make their point quickly and politely. We make an effort to protect discussions from repeated comments either by the same reader or different readers.
We follow the same standards for taste as the daily newspaper. A few things we won't tolerate: personal attacks, obscenity, vulgarity, profanity (including expletives and letters followed by dashes), commercial promotion, impersonations, incoherence, proselytizing and SHOUTING. Don't include URLs to Web sites.
We do not edit comments. They are either approved or deleted. We reserve the right to edit a comment that is quoted or excerpted in an article. In this case, we may fix spelling and punctuation.
We welcome strong opinions and criticism of our work, but we don't want comments to become bogged down with discussions of our policies and we will moderate accordingly.
We appreciate it when readers and people quoted in articles or blog posts point out errors of fact or emphasis and will investigate all assertions. But these suggestions should be sent via e-mail. To avoid distracting other readers, we won't publish comments that suggest a correction. Instead, corrections will be made in a blog post or in an article.
- Steelers’ Martavis Bryant facing four-game suspension
- Pennsylvania warming to bring ‘profound’ changes, Penn State report says
- Animal Rescue League, miffed at Vick signing, moves gala from Heinz Field
- Steelers notebook: Tomlin leaving `light on’ for injured players
- Penguins notebook: Crosby most excited by Kessel’s footspeed
- Gorman: Don’t judge WPIAL by the cover
- Class AAAA breakdown: Wealth of talent places target on Central Catholic
- Pirates notebook: Hurdle mulling rotation options
- Former Consol employee wins nearly $587K in ‘Mark of the Beast’ lawsuit
- Kane: Emails released not everything she wants to make public
- Class A breakdown: Teams going Bear hunting again this season chasing Clairton