Skip to content
SafetyScorer

Boeing · Single-aisle jet

Boeing 737-100/200

Is the Boeing 737-100/200 safe? It ranks #36 of 53 airliner families we rate, with 46 fatal accidents counted in about 43 million passenger flights.

High confidenceFew left in serviceUpdated 9 October 2026
Spot a mistake?
1 in 1.3 millionchance of dying on a flight0.75 deaths per million passenger boardings

How the score is built

Fatal passenger accidents
46 in 43 million flights

1.1 fatal passenger accidents per million flights. Counted: passenger flights, accidents and unexplained losses; not counted: sabotage, hijackings, shoot-downs and deliberate crew acts.

Full-loss equivalents
31.9

Each counted accident adds the share of people on board who died (1 = no survivors). This is what the score is based on.

Flights flown
43 million

Estimated passenger departures. Passenger departures 1968 to 7 October 2026 from a fleet model: deliveries with a median passenger service life of about 25 years and about 1,599 departures per aircraft per year (average of similar types in OpenSky). OpenSky sees too few of these aircraft. Uncertainty roughly ±50%.

Technology generation
Gen 2 jet (integrated autoflight, analogue cockpit)

Small fleets are pulled toward the record of their generation: 0.88 full-loss equivalents per million flights over 236 million flights. Weight of this family's own record: 93%.

Last fatal passenger accident
18 May 2018

Cubana de Aviación, lsf Global Air, 1 km E of Havana-José Martí International Airport (HAV/MUHA), Cuba: 112 of 113 people on board died.

Hull losses
123

Civil aircraft destroyed or written off from all causes, including non-fatal accidents, cargo flights and attacks; airframes flown by air forces on military operations are left out (context only, not in the score).

Compared with everyday risks

One flight on the Boeing 737-100/200 carries about the same risk of death as the activities near it below.

  • An hour's walk1 in 14 million
  • Driving 100 miles (160 km)1 in 5.9 million
  • One flight on the Boeing 737-100/200This aircraft1 in 1.3 million
  • A day of skiing1 in 1.3 million
  • An ordinary day: accidents and violence1 in 1 million
  • A scuba dive1 in 500,000
  • Cycling 100 miles (160 km)1 in 430,000
  • Running a marathon1 in 290,000
  • A skydive1 in 250,000
  • A general anaesthetic1 in 100,000
  • Riding a motorbike 100 miles (160 km)1 in 83,000
Chance of dying from each activity, on a log scale (longer bar = riskier). Activity figures are approximate and come from our activity pages; the ordinary day and the anaesthetic come from The Norm Chronicles (Blastland and Spiegelhalter, 2013).

Accident history

46 fatal accidents count toward the score, with 2,644 people on board killed.

DateFlightKilledWhat happened
Cubana de Aviación, lsf Global Air737-201 Advanced · 1 km E of Havana-José Martí International Airport (HAV/MUHA), Cuba112 / 113 on boardA wrong load sheet put the centre of gravity near its aft limit and the trim was set accordingly wrong. Right after takeoff from Havana the jet pitched up steeply, rolled from side to side, lost speed and crashed. Investigators pointed mainly to crew errors.Type: Loss of control in flightASN record
Bhoja Airlines B4213737-236A · 4,2 km SE of Islamabad-Benazir Bhutto International Airport (ISB), Pakistan127 / 127 on boardThe crew flew into a squall line on approach to Islamabad against company rules and met strong downdrafts in the wrong flap setting. They ignored windshear and terrain warnings and did not go around; the jet hit the ground short of the runway.Type: Windshear or stormASN record
First Air737-210C · 1,8 km E of Resolute Airport, NU (YRB), Canada12 / 15 on boardOn approach to Resolute in low cloud, compass errors and an unnoticed autopilot mode change pushed the jet off the localizer to the right. The captain pressed on despite the first officer's hints to go around, and it flew into a hill east of the runway.Type: Flight into terrainASN record
Itek Air, opf Iran Aseman Airlines IRC6895737-219 · 7,8 km WNW of Bishkek-Manas International Airport (FRU), Kyrgyzstan65 / 90 on boardA cabin pressure fault, probably a jammed door seal, made the crew turn back to Bishkek at night. Badly set up for a straight-in visual approach, they made an orbit to configure and let the jet sink below the minimum altitude into the ground 7.5 km out.Type: Flight into terrainASN record
TAAG Angola Airlines737-2M2 · M'Banza Congo Airport (SSY), Angola5 / 78 on boardThe jet touched down short of the runway at M'Banza Congo, collapsing its right main gear, and slid into cars and two buildings.Type: Landed short or longASN record
ADC Airlines737-2B7 · Abuja International Airport (ABV), Nigeria96 / 105 on boardThe crew took off from Abuja as a thunderstorm moved in and met a windshear just after lift-off. The pilot pulled the nose up too far, the jet stalled, rolled left and dived into a field. Investigators faulted the decision to depart and the recovery technique.Type: Windshear or stormASN record
Bellview Airlines737-2L9 · Lisa Village, Ogun State, Nigeria117 / 117 on boardMinutes after departing Lagos at night, the jet struck the ground in open woodland north of the city. Without flight recorders investigators could not find the cause, but noted poor captain training, possible fatigue and known defects that should have grounded it.Type: Unknown causeASN record
Mandala Airlines737-230 · Medan-Polonia Airport (MES), Indonesia100 / 117 on boardThe crew began the takeoff from Medan with flaps and slats retracted after poor checklist use, and the takeoff warning probably did not sound. The jet failed to lift off, ran off the end and ploughed into houses and vehicles, killing 49 people on the ground.Type: Runway excursionASN record
Transportes Aéreos Nacionales de la Selva - TANS737-244 · 5,5 km S of Pucallpa-Cap. FAP David A. Abensur Rengifo Airport (PCL), Peru40 / 98 on boardApproaching Pucallpa, the crew pressed on into a severe hailstorm they had seen on radar long before. Hail blocked the view, the descent was unstable and steep, and the jet crash-landed in swampland short of the runway; 58 people survived.Type: Windshear or stormASN record
Kam Air, lsf Phoenix Aviation737-242 Advanced · 32 km ESE of Kabul Airport (KBL), Afghanistan105 / 105 on boardOn a VOR approach to Kabul in snow, the jet descended below the 13,000 ft minimum it had been assigned and struck a mountain. The search was hampered by a snowstorm, and the reason for the early descent was not found.Type: Flight into terrainASN record
Sudan Airways737-2J8C · 5 km E of Port Sudan, Sudan116 / 117 on boardAbout 15 minutes after leaving Port Sudan one engine lost power and the crew turned back. Unable to see the runway in blowing sand, they began a missed approach but the jet descended into open ground east of the airport. A two-year-old boy was the only survivor.Type: Engine failureASN record
Air Algérie737-2T4 · Tamanrasset Airport (TMR), Algeria102 / 103 on boardJust after lift-off at Tamanrasset the left engine's turbine failed. The captain took control before identifying the problem, the gear stayed down and the jet lost speed, stalled and crashed on rocky ground. One passenger survived.Type: Engine failureASN record
Alliance Air737-2A8 Advanced · 2 km SW of Patna Airport (PAT), India55 / 58 on boardHigh on approach to Patna with engines at idle, the crew let speed fall too low, then asked for an orbit. With high pitch and rapid roll reversals the stick shaker fired; they tried a go-around instead of a stall recovery, stalled and hit houses, killing five on the ground.Type: Loss of control in flightASN record
Air Philippines737-2H4 · 8 km NE of Davao City-Francisco Bangoy International Airport (DVO), Philippines131 / 131 on boardSeeing traffic still on the runway, the crew abandoned an ILS approach to Davao and, instead of the published missed approach, flew low in cloud to try the opposite runway. Well below the profile, the jet struck a hillside coconut plantation.Type: Flight into terrainASN record
LAPA - Líneas Aéreas Privadas Argentinas737-204C · Buenos Aires-Jorge Newbery Airport, BA (AEP), Argentina63 / 100 on boardDistracted by personal conversation, the crew left the flaps retracted and ignored the takeoff warning horn. The jet stalled after rotation, ran off the runway end across a road and burned; two people in a car were also killed.Type: Loss of control in flightASN record
Occidental Petroleum, lsf Fuerza Aérea del Peru - FAP737-282 Advanced · 3 km from Andoas, Peru75 / 88 on boardThe aircraft crashed at night in rain during an NDB approach to Andoas, about 3 km from the airport. No cause is given.Type: Unknown causeASN record
Varig737-2C3 · Carajás Airport, PA (CKS), Brazil1 / 52 on boardLanding in a thunderstorm with poor visibility after a VOR approach, the right main gear collapsed and the jet veered off the runway into forest. The first officer was the only person killed.Type: Hard landing or abnormal runway contactASN record
Faucett Perú CF251737-222 · 6,3 km W of Arequipa-Rodriguez Ballon Airport (AQP), Peru123 / 123 on boardOn a night VOR/DME approach in fog, the crew went below the minimum altitude and hit hills west of the airport; a position report had given a height almost 900 ft above the real one. Investigators cited crew error and visual flight in cloud.Type: Flight into terrainASN record
Cameroon Airlines737-2K9 · 1,7 km S of Douala Airport (DLA), Cameroon71 / 76 on boardOn short final at night a compressor blade broke from fatigue in the left engine; the crew began a late go-around, lost speed in a sharp left turn and crashed into a mangrove swamp.Type: Loss of control in flightASN record
Nigeria Airways WT357737-2F9 · Kaduna Airport (KAD), Nigeria11 / 138 on boardThe captain insisted on the runway with a tailwind and flew a steep, badly unstable approach, landing with little runway left. Turning into a high-speed exit too fast, the jet skidded, a wing struck the ground and fire broke out.Type: Runway excursionASN record
Aviateca GUG901737-2H6 · 24 km NE of San Salvador, El Salvador65 / 65 on boardDeviating around thunderstorms near San Salvador, neither crew nor controller was sure of the aircraft's position; cleared to 5,000 ft, it struck the San Vicente volcano. Investigators cited descent below the minimum safe altitude and weak crew coordination.Type: Flight into terrainASN record
Indian Airlines737-2A8 · 3 km NE of Aurangabad Airport (IXU), India55 / 118 on boardHeavily loaded on a hot day, the jet lifted off near the runway end and its gear hit a lorry on the highway beyond, then it struck power lines and crashed. Investigators cited late, incorrect rotation and the failure to control road traffic.Type: Flight into terrainASN record
COPA Panama - Compañía Panameña de Aviación737-204 Advanced · 13 km SW of Tucutí, Panama47 / 47 on boardAt night in cruise near bad weather, an intermittent short circuit gave false readings on the main attitude indicator. The crew followed them, lost control, and the jet broke up in a steep dive.Type: Loss of control in flightASN record
Indian Airlines737-2A8 Advanced · 38 km SW of Imphal Municipal Airport (IMF), India69 / 69 on boardDeparting from the published let-down, the captain descended early and turned outbound without reporting over the VOR, lost his timing reference and flew into Thangjing Hill in cloud and rain. His close familiarity with the area may have played a part.Type: Flight into terrainASN record
United Airlines737-291 · 6,4 km S of Colorado Springs, CO, United States of America25 / 25 on boardOn final approach the jet suddenly rolled right and pitched down, hitting the ground almost vertically. The NTSB at first could not find the cause, but later linked it to a rudder servo-valve jam like the one in the 1994 USAir 737 crash.Type: System failureASN record
China Airlines737-209 · 5,5 km N of Hualien Airport (HUN), Taiwan54 / 54 on boardThree minutes after takeoff the jet flew into a mountain at about 7,000 ft; the crew had flown the climb-out procedure for the other runway and turned left instead of right.Type: Flight into terrainASN record
Varig737-241 · São José do Xingu, MT, Brazil12 / 54 on boardThe captain misread the computer flight plan and set a course of 270 instead of 027, and the copilot copied it. Lost over the Amazon at dusk, the crew ran out of fuel and force-landed in the jungle at night; the wreck was found 44 hours later.Type: FuelASN record
Indian Airlines737-2A8 · 2,54 km NE of Ahmedabad Airport (AMD), India133 / 135 on boardOn a localiser-DME approach in haze with about 2 km visibility, the jet struck trees and a power pylon short of the runway and crashed into a paddy field. The pilots had not followed the procedures for poor visibility.Type: Flight into terrainASN record
Ethiopian Airlines ET604737-260 · 10 km SW of Bahar Dar Airport (BJR), Ethiopia35 / 104 on boardJust after rotation both engines ingested a flock of pigeons. They surged but kept some power while the crew turned back, then failed completely on the downwind leg, and the captain belly-landed in a clearing.Type: Bird strikeASN record
Aloha Airlines737-297 · near Maui, HI, United States of America1 / 95 on boardAs the jet levelled at 24,000 ft, a large section of the upper forward fuselage tore away and a flight attendant was swept out; the crew landed safely on Maui. The NTSB found disbonding and fatigue cracks missed by the airline's maintenance.Type: System failureASN record
Condor Flugdienst737-230 Advanced · near Seferihisar, Türkiye16 / 16 on boardAfter passing the NDB the crew switched to the ILS without confirming their position, followed a false side beam and descended to outer-marker height, striking Dümentepe Hill about 10 nm from the airport.Type: Flight into terrainASN record
Thai Airways737-2P5 · 15 km E off Phuket International Airport (HKT), Thailand83 / 83 on boardCompeting with a Dragonair 737 for landing priority, the crew let airspeed bleed away while watching the other traffic. The aircraft stalled after the stick shaker sounded and hit the sea before they could recover.Type: Loss of control in flightASN record
LAN Chile737-2A1 · Calama-El Loa Airport (CJC), Chile1 / 33 on boardLanding into the sun, the pilot touched down about 520 m before a threshold displaced for construction work. The nose gear failed, the fuselage split in two and a fire broke out half an hour later.Type: Landed short or longASN record
China Airlines737-281 · 19 km N off Magong Airport (MZG), Taiwan13 / 13 on boardA nose-wheel tyre reportedly burst on the first landing attempt at Magong. During the go-around the 737 crashed into the sea; the wreck was found weeks later in 190 ft of water.Type: Unknown causeASN record
VASP - Viação Aérea São Paulo737-2A1 · São Paulo-Guarulhos International Airport, SP (GRU), Brazil1 / 72 on boardIn fog, the crew began their take-off on a taxiway without realising it. They rejected the take-off, but the 737 ran off the end, hit an embankment and split in two.Type: Runway excursionASN record
British Airtours KT328737-236 · Manchester International Airport (MAN), United Kingdom55 / 137 on boardA repaired combustor can failed during the take-off roll and pierced a wing fuel panel. The crew stopped, but fire spread into the cabin while a jammed door slowed the evacuation; most victims were overcome by toxic smoke.Type: Engine failureASN record
Thai Airways737-2P5 · 18 km from Phuket International Airport (HKT), Thailand11 / 11 on boardAt night the crew lost DME reception, then reported losing both engines and narrowly missing a mountain while approaching Phuket. The 737 then hit a mountain at about 800 ft. No cause is given.Type: Unknown causeASN record
Cameroon Airlines737-2H7C · Douala Airport (DLA), Cameroon2 / 116 on boardWhile the 737 was taxiing out at Douala, a compressor disc in the right engine broke apart. Fragments pierced the wing fuel tank and the fire that followed burned out the aircraft.Type: Engine failureASN record
TAME Ecuador737-2V2 · 1,5 km from Cuenca, Ecuador119 / 119 on boardInstead of the cleared instrument approach, the crew flew a visual approach, ignored repeated terrain warnings and descended below the minimum altitude into cloud. The 737 hit a ridge with its tail about a mile short of the runway.Type: Flight into terrainASN record
VASP - Viação Aérea São Paulo VP234737-2A1 · Brasilia International Airport, DF (BSB), Brazil2 / 118 on boardLanding in rain, the 737 touched down hard on its nose gear, which collapsed; it slid off the side and the fuselage split. Investigators cited a visual illusion that misled the crew about height, and procedures not being followed.Type: Hard landing or abnormal runway contactASN record
Air Florida737-222 · 1,4 km N of Washington-National Airport, DC (DCA) [Potomac River], United States of America74 / 79 on boardThe crew left engine anti-ice off and took off with snow and ice on the wings after a long wait. The 737 barely climbed, stalled, hit a crowded bridge and fell into the frozen Potomac; four people in cars also died.Type: IcingASN record
Far Eastern Air Transport - FEAT737-222 · near Sanyi Township, Miaoli County, Taiwan110 / 110 on boardSevere corrosion and probable cracks in the lower fuselage, after repeated pressurisation problems, gave way in the climb. The cabin depressurised explosively, cutting controls and wiring, and the 737 broke up in the air.Type: System failureASN record
Indian Airlines737-2A8 · Hyderabad-Begumpet Airport (HYD), India1 / 132 on boardRight after lift-off, the leading-edge devices failed to extend and the 737 became unstable. The crew put it back down on its belly; it slid off the runway, through a fence and into rough ground and burned. People cutting grass by the fence were killed.Type: System failureASN record
Pacific Western Airlines737-275 · Cranbrook Airport, BC (YXC), Canada42 / 49 on boardAn error in the arrival estimate left a snowplough on the runway in falling snow. Seeing it after touchdown with reversers deployed, the crew tried to take off again; a reverser deployed in flight, control was lost and the 737 crashed beside the runway.Type: Runway collisionASN record
Indian Airlines IC440737-2A8 · 6 km from Delhi-Indira Gandhi International Airport (DEL), India48 / 65 on boardOn an NDB approach in visibility below minima, the pilot went below minimum descent altitude without seeing the runway, hit high-tension power lines and crashed; the wreck caught fire.Type: Flight into terrainASN record
United Airlines737-222 · 2 km from Chicago-Midway Airport, IL (MDW), United States of America43 / 61 on boardOn a non-precision approach to Midway, ATC slowed the jet for spacing and then ordered a go-around; the stick shaker fired and, despite full power, it kept sinking nose-high into houses. The captain was found to have let speed decay into a stall.Type: Loss of control in flightASN record

Listed but not counted

These events did not happen on regular passenger flights or were caused by a crime or a deliberate act, which says little about the aircraft design.

DateFlightKilledWhy not counted
IBM Airlines, opf South Sudan Air Force737-290C Adv. · Nyala Airport (UYL/HSNN), Sudan20 / 86 on boardMilitary operation. The 737, flying military cargo reportedly including drones for the RSF militia, was destroyed on the ground at Nyala in a strike by the Sudanese army. Reports say foreign military specialists were among the dead; accounts of the numbers vary widely.Type: SecurityASN record
Bako Air737-275 · Massamba, Bandundu Province, Congo (Democratic Republic)7 / 7 on boardFerry flight without passengers. Ferry flight taking the jet to Harare for maintenance, with two pilots and five engineers aboard, which crashed near Massamba after a refuelling stop at Brazzaville. No cause is given.Type: Unknown causeASN record
Conviasa737-291 · near Toacaso, Ecuador3 / 3 on boardFerry flight without passengers. Ferry flight taking a stored jet to Latacunga for a new owner. In the procedure turn the crew strayed outside the protected area and hit the Iliniza volcano; investigators found they did not fly the turn as published and did not know the terrain.Type: Flight into terrainASN record
United States Air Force - USAFT-43A (737-200) · 3 km N of Dubrovnik Airport (DBV), Croatia35 / 35 on boardMilitary operation. US Air Force flight carrying Commerce Secretary Ron Brown and business leaders that hit a hillside on an NDB approach to Dubrovnik, off course. The board cited planning and flying errors, a command failure to vet the approach, and the approach's poor design.Type: Flight into terrainASN record
Phoenix Aviation Ltd, lsf Air Algérie737-2D6C · 1,7 km NE of Coventry-Baginton Airport (CVT), United Kingdom5 / 5 on boardCargo flight. Livestock export cargo flight that hit an electricity pylon on a radar approach to Coventry in patchy fog. Investigators found the crew went below the minimum height without seeing the runway, tired after over ten hours of night flying.Type: Flight into terrainASN record
Sahara Airlines737-2R4C · Delhi-Indira Gandhi International Airport (DEL), India4 / 4 on boardTraining flight. Training flight doing circuits at Delhi. During an engine failure exercise the trainee applied the wrong rudder and the instructor did not stop it; the jet rolled left and crashed onto the terminal apron, setting a parked Il-86 alight and killing three on the ground.Type: Loss of control in flightASN record
Indian Airlines737-2A8 · Amritsar-Raja Sansi Airport (ATQ), India1 / 141 on boardUnlawful interference (sabotage, hijacking or shoot-down). Hijacking. A man claiming to belong to Hizbul Mujahideen, armed with pistols and a grenade, demanded to go to Kabul; denied passage by Pakistan, the jet landed at Amritsar, where commandos stormed it 11 hours later and killed him.Type: SecurityASN record
VASP - Viação Aérea São Paulo737-2A1C · 15 km W of Cruzeiro do Sul-Campo Internacional Airport, AC (CZS), Brazil3 / 3 on boardCargo flight. Night cargo flight that crashed in jungle while flying the arrival procedure to Cruzeiro do Sul. An intermittent cargo fire warning distracted the crew, who did not make callouts or use the radio altimeter and altitude alert properly.Type: Flight into terrainASN record
Xiamen Airlines MF8301737-247 · Guangzhou-Baiyun Airport (CAN), China82 / 102 on boardUnlawful interference (sabotage, hijacking or shoot-down). A passenger claiming to carry explosives burst into the cockpit and demanded to go to Taiwan. Short of fuel, the captain tried to land at Guangzhou; amid a cockpit fight the jet hit hard, veered, struck two airliners on the ground and burned. No explosives were found.Type: SecurityASN record
Iraqi Airways737-270C · near Arar, Saudi Arabia63 / 106 on boardUnlawful interference (sabotage, hijacking or shoot-down). Four hijackers tried to get into the cockpit as the flight to Amman entered Saudi airspace. Guards on board resisted, grenades went off in the cabin and then the cockpit during an emergency descent, and the 737 crash-landed near Arar, broke in two and burned.Type: SecurityASN record
Iran Air737-286 · Shiraz Airport (SYZ), Iran3 / 86 on boardUnlawful interference (sabotage, hijacking or shoot-down). Iraqi warplanes bombed Shiraz airport while passengers were leaving the 737, which was destroyed. Iran said several military transports were also wrecked.Type: SecurityASN record
EgyptAir737-266 · Malta-Luqa Airport (MLA), Malta60 / 98 on boardUnlawful interference (sabotage, hijacking or shoot-down). Three men hijacked the flight from Athens and an onboard guard killed one before being wounded. At Malta, refused fuel, they shot five hostages, two fatally. After 22 hours Egyptian commandos stormed the 737; grenades set the cabin alight and most deaths came then.Type: SecurityASN record
Saudi Arabian Airlines737-268 · Dhahran International Airport (DHA), Saudi Arabia1 / 97 on boardUnlawful interference (sabotage, hijacking or shoot-down). A man with a grenade took over the flight just before it landed at Riyadh. During a fuel stop at Dhahran he let everyone go except the two pilots; when he refused to give up, security forces stormed the jet and shot him after he threw the grenade.Type: SecurityASN record
Iraqi Airways737-270 · Baghdad-Saddam International Airport (SDA), Iraq3 / 110 on boardUnlawful interference (sabotage, hijacking or shoot-down). Three Iranian men tried to hijack the flight to Baghdad; one opened the cockpit door holding a wrapped bottle and announced it. Iraqi security agents on board shot all three dead.Type: SecurityASN record
TAAG Angola Airlines737-2M2 · 1 km from Lubango Airport (SDD), Angola130 / 130 on boardUnlawful interference (sabotage, hijacking or shoot-down). Just after take-off from Lubango the 737 sank from about 200 feet, turned left, caught a wingtip and burned. Angola blamed a technical failure; UNITA rebels claimed to have shot it down with a missile.Type: Unknown causeASN record
Gulf Air737-2P6 · Mino Jebel Ali, United Arab Emirates112 / 112 on boardUnlawful interference (sabotage, hijacking or shoot-down). During the descent to Abu Dhabi the crew sent two mayday calls before the 737 came down in the desert with signs of fire before impact. A bomb in the cargo hold appears to have gone off and started an intense fire.Type: SecurityASN record
VASP - Viação Aérea São Paulo737-2A1C · Manaus-Eduardo Gomes International Airport, AM (MAO), Brazil2 / 2 on boardTraining flight. On a training flight, the co-pilot lost control during a practice take-off with one engine at reduced thrust; power was added but the engine stalled and the 737 rolled left into the ground. Investigators cited procedures not followed and poor supervision.Type: Loss of control in flightASN record
Indian Airlines737-200 · Amritsar Airport (ATQ), India1 / 86 on boardUnlawful interference (sabotage, hijacking or shoot-down). An armed man took over the domestic flight and tried to go to Lahore, which refused it, so it landed at Amritsar. Hours into talks, with the door opened against the heat, he leaned out firing into the air and police shot him dead.Type: SecurityASN record
China Airlines737-281 · Hong Kong, Hong Kong1 / 86 on boardUnlawful interference (sabotage, hijacking or shoot-down). A crew member armed with an axe and scissors tried to take over the flight and force it to mainland China, injuring both pilots. A security guard killed him and the 737 landed in Hong Kong.Type: SecurityASN record
Malaysian Airlines System - MAS MH653737-2H6 · near Tanjong Kupang, Malaysia100 / 100 on boardUnlawful interference (sabotage, hijacking or shoot-down). A hijacker took over the domestic flight near Kuala Lumpur and demanded Singapore. He apparently shot both pilots and himself; with nobody in control, the 737 entered growing pitch swings, dived into a swamp and broke up.Type: SecurityASN record
Frontier Airlines (FL)737-200 · Kansas City, MO, United States of America1 / 34 on boardUnlawful interference (sabotage, hijacking or shoot-down). A man produced a shotgun at airport screening and took over the 737, which flew to Kansas City for fuel and on to Atlanta. He demanded a friend's release, money and weapons, then let the hostages go and shot himself.Type: SecurityASN record
Lufthansa LH181737-230C · Mogadishu International Airport (MGQ), Somalia4 / 95 on boardUnlawful interference (sabotage, hijacking or shoot-down). Palestinian militants hijacked the 'Landshut' and flew it around the Middle East, demanding jailed Red Army Faction members be freed. They shot the captain in Aden; in Mogadishu, German GSG 9 commandos stormed the jet and killed three of the four hijackers.Type: SecurityASN record
Iraqi Airways737-200 · Tehran-Mehrabad Airport (THR), Iran1 / 92 on boardUnlawful interference (sabotage, hijacking or shoot-down). Three passengers hijacked the domestic flight to Tehran, demanding the release of Kurdish prisoners. Iraqi guards on board opened fire, killing a passenger; the hijackers then gave up.Type: SecurityASN record
Lufthansa737-130 · Kuwait International Airport (KWI), Kuwait1 / 19 on boardUnlawful interference (sabotage, hijacking or shoot-down). After an attack at Rome's airport that set a Pan Am 707 on fire, the gunmen took hostages and forced their way onto the 737, flying it around the region until they surrendered in Kuwait. One person on board died.Type: SecurityASN record
Pacific Southwest Airlines - PSA737-200 · San Francisco International Airport, CA (SFO), United States of America3 / 86 on boardUnlawful interference (sabotage, hijacking or shoot-down). Two hijackers demanded $800,000 and a flight to the Soviet Union. When the 737 was stormed at San Francisco both were shot dead, and a passenger was also killed in the gunfire.Type: SecurityASN record

The original Boeing 737, the -100 and -200, was the aircraft that made the 737 the world's most common airliner, and its record reflects its age and the places it ended up. Up to 7 October 2026 it has had 71 fatal events, 46 of which count, in about 43 million passenger flights. Most crashes after 1990 involved small or weak operators flying old airframes in Africa, Asia and Latin America. Today only a few dozen remain.

What the original 737 is

The 737-100 first flew in 1967 and entered service with Lufthansa in 1968; only 30 were built. The longer 737-200, launched by United, entered service later that year and became the standard short-haul jet of the 1970s and 80s, with about 115 seats. 1,144 were built, the later ones as the 737-200 Advanced. Both have Pratt & Whitney JT8D engines tucked under the wing, cable-and-hydraulic flight controls and an analogue cockpit. The 1980s 737 Classic replaced it.

Gravel strips and the far north

Unusually for a jet, the 737-200 could be fitted with a gravel runway kit. Airlines in Alaska and the Canadian Arctic, including Alaska Airlines, First Air and Canadian North, flew -200 combis carrying cargo in front and passengers behind into unpaved strips for decades. A few still fly charters there. That environment shows up in the record: on 20 August 2011, a First Air 737-210C built in 1975 flew into a hill on approach to Resolute Bay in drizzle and low cloud, after turning onto final 600 feet above the glideslope. 12 of 15 died.

The fatal record

Many of the counted crashes changed how the industry works:

  • 13 January 1982, Air Florida 90, Washington: took off with ice on the wings and false engine readings, stalled and hit a bridge over the Potomac. 74 of 79 on board died, plus 4 on the bridge.
  • 22 August 1985, British Airtours 328, Manchester: an engine failed on take-off and fire spread into the cabin. 55 of 137 died, most from smoke. The inquiry led to floor-level lighting, wider access to overwing exits and fire-blocking seats.
  • 28 April 1988, Aloha 243: fuselage fatigue on a high-cycle aircraft; 1 of 95 died.
  • 3 March 1991, United 585, Colorado Springs: a rudder power control unit jammed and the aircraft rolled into the ground. All 25 died. The same flaw was later found in a 737-300 crash, and Boeing redesigned the rudder system.

After 1995 the pattern shifts to operators. ADC Airlines in Nigeria (2006, 96 dead) and Bhoja Air in Pakistan (2012, all 127) flew into windshear near thunderstorms. Mandala Airlines in Indonesia took off without flaps in 2005, killing 100 on board and 49 on the ground. Kam Air hit a mountain near Kabul in snow in 2005 (105 dead). The last counted crash was on 18 May 2018, when a 39-year-old 737-201 leased by Cubana from Mexico's Global Air stalled after take-off from Havana with a wrong weight and balance calculation; 112 of 113 died.

The other 25 fatal events do not count: 17 acts of unlawful interference, including the 1983 Gulf Air bombing and the 1985 EgyptAir hijacking at Malta, plus military, cargo, ferry and training flights. Our methodology explains why.

The aircraft or the operators?

Mostly the operators, and age. United 585 and Aloha 243 were real airframe problems, both fixed fleet-wide. Most later crashes came from crews flying into weather, setting up the aircraft wrongly, or companies with weak oversight. A 1960s cockpit without modern terrain and windshear alerting gives less protection against those errors than a 737 NG.

How to tell if you are on one

Flight trackers show B731 or B732. The engines are long and slim, hung close under the wing, with no bulky round nacelles. If you are booked on one with a small charter operator, look at the airline's record first.

Questions people ask

Is the Boeing 737-200 still flying?

A few are. Of 1,144 737-100s and -200s built, about 40 remain in service, many of them freighters. The rest fly charters, often in northern Canada, where the type's gravel runway kit keeps it useful, and with small operators in Africa and Latin America.

Why could the 737-200 land on gravel?

Boeing offered a gravel runway kit: a deflector behind the nose wheel, devices that blow air in front of the engine intakes so they do not suck up stones, and extra protection under the fuselage and flaps. Low-slung engines under the wing made this harder than on a high-wing turboprop, but it worked, and airlines in Alaska and the Canadian Arctic used it for decades.

What happened on Aloha Airlines flight 243?

On 28 April 1988, part of the upper fuselage of a 737-200 tore off at 24,000 feet between Hilo and Honolulu. A flight attendant was swept out and died; the other 94 people survived after the crew landed on Maui. The aircraft had flown a very large number of short island hops in salty air, and fatigue cracks had joined up. It changed how ageing aircraft are inspected worldwide.

Is the 737-200 the same as the 737 MAX?

No. All 737s share the basic fuselage and the name, but the -200 is a 1960s design with slim JT8D engines, analogue instruments and no modern alerting systems. The later Classic, NG and MAX families have new engines, wings and cockpits, and each is a separate family in our data.

Sources

  1. 1.ASN record: Cubana de Aviación (Global Air) 737-201, Havana, 18 May 2018 (opens in a new tab) · Aviation Safety Network
  2. 2.ASN record: First Air 737-210C, Resolute Bay, 20 August 2011 (opens in a new tab) · Aviation Safety Network
  3. 3.ASN record: Aloha Airlines flight 243, near Maui, 28 April 1988 (opens in a new tab) · Aviation Safety Network
  4. 4.ASN record: British Airtours flight 328, Manchester, 22 August 1985 (opens in a new tab) · Aviation Safety Network
  5. 5.ASN record: United Airlines flight 585, Colorado Springs, 3 March 1991 (opens in a new tab) · Aviation Safety Network
  6. 6.ASN record: Air Florida flight 90, Washington, 13 January 1982 (opens in a new tab) · Aviation Safety Network
  7. 7.SafetyScorer fleet model (World Bank departures, OpenSky averages) (opens in a new tab)Passenger departures 1968 to 7 October 2026 from a fleet model: deliveries with a median passenger service life of about 25 years and about 1,599 departures per aircraft per year (average of similar types in OpenSky). OpenSky sees too few of these aircraft. Uncertainty roughly ±50%.
Spot a mistake?