Commentary

Thomas Claburn
 

Pilots Who Missed Airport Busy With Laptops

The pilots of Northwest Airlines Flight 188, which overflew the runway at Minneapolis-St. Paul airport last week, told investigators from the National Transportation Safey Board that they used their laptop computers -- a violation of company policy -- while discussing airline crew scheduling procedures.

The pilots of Northwest Airlines Flight 188, which overflew the runway at Minneapolis-St. Paul airport last week, told investigators from the National Transportation Safey Board that they used their laptop computers -- a violation of company policy -- while discussing airline crew scheduling procedures.Both pilots told NTSB investigators that they lost track of time.

Thankfully, the plane landed without anyone being injured. It could have been much worse. Distractions, in the form of gadgets or gabbing in the next seat, can be deadly.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

In August, a plane and a helicopter collided over New York, killing nine people. The air traffic controller at New Jersey's Teterboro Airport who was supposed to be working to prevent such incidents was reportedly involved in a telephone conversation at the time of the accident. It must have been an important call.

A year ago in Los Angeles, a train engineer had reportedly sent a text message on his mobile phone just 22 seconds before the commuter train he was driving hit a freight train, killing 25 people.

Last month, U.S. transportation officials said that almost 6,000 people were killed and over 500,000 were injured last year in crashes involving driver distraction. Much of that distraction can be attributed to mobile phones.

Just to put that number into perspective, the National Counterterrorism Center said that 19 U.S. citizens were killed in terrorist attacks in 2008.

As we become more connected with the network, we're becoming less connected to reality. Distraction is the ultimate killer app.


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