Commentary

Are Text Messages Responsible For 25 Deaths?

Saturday's Metrolink train crash was a tragedy and may have occurred because the engineer was distracted by text messages sent to his cell phone. The possibility raises the issue of how companies are to handle personal technology in the workplace -- especially when lives are at stake.

Saturday's Metrolink train crash was a tragedy and may have occurred because the engineer was distracted by text messages sent to his cell phone. The possibility raises the issue of how companies are to handle personal technology in the workplace -- especially when lives are at stake.The Metrolink crash that took place in California on Saturday happened because the train failed to yield to a stop signal. The passenger train then rammed into the back of a freight train that was sitting on the same track, killing 25 of those aboard and injuring more than 100 others. Why didn't the engineer stop the train? Federal officials are investigating the possibility that the engineer was distracted by text messages.

Apparently two teenagers were interested in trains and had befriended the engineer. They sent him text messages to ask him about his work, and were sending him messages in the minutes leading up to the crash.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

According to CNN, "We have been in contact with them and their families. They have been fully cooperative," Kitty Higgins of the National Transportation Safety Board said. "We are going to be obtaining records from their cell phones and of the deceased ... to begin to determine what might have happened and what, if any, role [cell phones] might have played in this accident." Metrolink train engineers are not allowed to use their cell phones while on duty, and for good reason.

Nearly every adult in the U.S. has a cell phone. Odds are, most of them are bringing them to work. Many keep them tucked away in their briefcase or purse while in the office, but others are not so quick to ignore what is increasingly used as a link to outside social networks. Let's discount whether or not they are being used to breach corporate security or simply waste time while on the clock

How are companies to govern their use when safety is a priority?

Sure, businesses can put policies in place that forbid their use at the workplace -- as Metrolink did -- but that doesn't mean those policies will be followed. They certainly won't be followed if the policies aren't strictly enforced. Could Metrolink have taken any more steps to prevent the train's engineer from bringing his cell phone onto the train on Saturday? Would that have prevented the crash and saved the lives of the 25 who were lost? Should Metrolink be held liable in this case, or does the blame lay fully with the engineer?

Should different rules be set in place for those who are responsible for the lives of others, such as train engineers, airplane pilots, bus drivers, truck drivers, etc.?

I think they should. But what form those rules take, how they are enforced, and what consequences are tied to them need serious consideration.

Please share your thoughts.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links