Media watch: Karachi plane crash

One of only 419 beechcraft aeroplanes crashed in Karachi on Friday, leaving 21 dead.


November 06, 2010

Media watch is a daily round-up of key articles featured on news websites, hand-picked by The Express Tribune web staff.

21 die as small plane crashes

A chartered plane owned by JS Air crashed here Friday seconds after departure from Jinnah International Airport, killing all 21 people on board, CAA officials said. The plane was carrying ENI staff, an Italian company, to the Bhit gas field in Jamshoro district, where they were carrying out exploration. Aamir Majeed (brecorder.com)

Karachi mourns another plane crash

The charred, apparently unrecognisable bodies were moved to the Aga Khan Hospital for medico-legal formalities, where heirs of 17 victims identified their beloved. (dailytimes.com.pk)

Beechcraft planes out of production since 2002

The ill-fated Beechcraft 1900 aircraft that crashed in Karachi on Friday morning has been out of production since October 2002 and was one of the only 419 small aeroplanes of its kind left in the world today. Sabir Shah (thenews.com.pk)

Air safety standards

Pakistan has generally had a good air safety record. Yet as the International Civil Aviation Organisation has pointed out in the past, there are areas where there is room for improvement. These include a shortage of qualified inspectors and a need to increase safety oversight activities, especially of commercial air transport operators. (dawn.com)

COMMENTS (1)

Meekal Ahmed | 13 years ago | Reply The fact that there are only 419 Beech 1900 flying is completely irrelevant to the accident. However, age does mean higher maintenance costs and tighter inspections for signs of metal fatigue. There is plenty of room to improve air safety standards in Pakistan. To start with they should publish all air accident reports and share that information with the world aviation community. .
Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ