Malaysian Airline System Flight 653
Boeing 737-2H6 · Hijacking
From Penang International Airport (PEN) to Paya Lebar Air Base (QPG)
Event
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- Event fatalities
- 100 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 100
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
Boeing 737-2H6
- Flight
- MH653
- Aircraft type
- Boeing 737
- Category
- Airplane · from aircraft type
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- 9M-MBD
- Operator
- Malaysian Airline System
- Onboard fatalities
- 100
- Route
- From Penang International Airport (PEN)To Paya Lebar Air Base (QPG)
Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.
From the Wikipedia article
Malaysian Airline System Flight 653 was a scheduled domestic flight from Penang to Kuala Lumpur in Malaysia, operated by Malaysian Airline System (MAS). On the evening of 4 December 1977, the Boeing 737-200 aircraft flying the service crashed at Tanjung Kupang, Johor, Malaysia, while purportedly being diverted by hijackers to Singapore. It was the first fatal air crash for Malaysia Airlines (as the airline is now known), with all 93 passengers and 7 crew killed. It is also the deadliest aviation disaster to occur on Malaysian soil. The flight was apparently hijacked as soon as it reached cruise altitude. The circumstances in which the hijacking and subsequent crash occurred remain unsolved.
Sequence of events
Flight 653 departed from Runway 22 at Penang International Airport at 19:21 for Kuala Lumpur's Subang Airport (now known as Sultan Abdul Aziz Shah Airport).
Captain GK Ganjoor and First Officer Karamuzaman Jali were making landing preparations at 19:54, while at an altitude of 4000 feet over Batu Arang and descending toward Runway 33 at Subang Airport, when the crew reported to Subang Tower that an "unidentified hijacker" was on board, after someone knocked on the cockpit doors. Subsequently, the pilots were forced to cut off all communications by one or more hijackers who suddenly barged into the cockpit. The tower immediately notified the authorities, who made emergency preparations at the airport.
A few minutes later, the crew radioed: "We're now proceeding to Singapore. Good night." In the last few minutes of the tapes from the cockpit voice recorder, investigators heard conversation between the pilots and the hijackers about how the aircraft would run out of fuel before it could make it to Singapore, followed by a series of gunshots. They concluded that both the pilot and co-pilot were fatally shot by the hijacker, which left the plane "professionally uncontrolled". At 20:15, all communication with the aircraft was lost. At 20:36, the residents of Kampong Ladang, Tanjung Kupang in Johor reported hearing explosions and seeing burning wreckage in a swamp. The wreckage was later identified as the aircraft; it had hit the ground at a near-vertical angle at a very high speed. There were no survivors.
Investigation and cause
Investigation and aftermath
The full circumstances of the hijacking and crash were never solved. An analysis by Malaysia's Department of Civil Aviation of evidence from the investigation concludes that:
The aircraft was "hijacked by person or persons unknown", who were determined not to land at Kuala Lumpur
The crew "carried out their hijack procedures properly and correctly... throughout the flight."
The hijackers incapacitated the crew as the aircraft descended in its approach to Singapore
There was no explosion, fire, or structural failure prior to impact
Unusual pitching – up and down – movements occurred in the aircraft's final moments in the air. These manoeuvres were the result of the actions of person or persons unknown and developed until the aircraft's trajectory became unrecoverable, resulting in its impact with the ground
All recovered remains were x-rayed in an attempt to discover evidence of a projectile or weapon, but no such evidence was ever found. The remains of the victims were interred in a mass burial.
After the incident, the Aviation Security Unit of the Airport Standard Division of the Department of Civil Aviation Malaysia was established.
Text from the Wikipedia article “Malaysian Airline System Flight 653” (revision 1356073788, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
Sources
Wikipedia article: Malaysian Airline System Flight 653
- Revision
- 1356073788 · 2026-05-25 · retrieved 2026-09-18
- Wikidata
- Q1467946
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
Where each value comes from
- Record
- Wikipedia article "Malaysian Airline System Flight 653" (page 2166718, revision 1356073788)
- Date
- Wikipedia infobox: date
- Place and country
- Wikipedia infobox: site
- Map position
- Wikipedia article coordinates
- Aircraft, operator and route
- Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- airline flight number in the infobox
- Fatalities
- Wikipedia infobox: aircraft fatalities
- Ground fatalities
- not stated in the Wikipedia infobox
- Summary
- Wikipedia infobox: summary
Source notes (1)
- Wikipedia · Facts from the Wikipedia article's infobox and coordinates, not checked against an investigation report. Independent review pending.