Jakarta Tragedy: Lion Air’s Bad Luck and a Questionable Aircraft
What Went Down—Fast
- The first flight left Bali on Sunday, hit some tech snags, yet the captain kept his cool and flew on to Jakarta.
- Only hours later the same old Boeing 737 MAX took off for Bangka Island, went down 13 minutes after the take‑off, and nobody survived.
The Chief’s Calm Speech
Herson, the head of the Bali–Nusa Tenggara airport authority, told Reuters that after the pilot sounded a “Pan‑Pan” alert, he reassured the tower the plane was flying normal—no emergency return needed. “The captain was confident enough to keep going to Jakarta,” Herson said.
Other Pilots Heard the Lament
- A pilot who was approaching Bali after that first flight heard the radio tones and sat back as the Lion Air crew tried to politely ask the tower to hold them in the air.
- He told reporters they’d given the after‑take‑off Ju 43 a “return to base” call but the pilot claimed the problem was solved and pushed on.
Why “Pan‑Pan” Isn’t the Same as Mayday
Controllers use a “Pan‑Pan” call for any urgent situation—less severe than the “Mayday” that signals an emergency.
Flight Times & Numbers
- Denpasar‑Jakarta: landed at 10:55 p.m. local time on Sunday.
- Bangka‑flight: took off at 6:20 a.m. Monday, crashed after 13 minutes.
The Company’s Heavy‑Duty Response
When asked about the earlier alert, a Lion Air spokesperson stayed silent, citing an ongoing investigation. CEO Edward Sirait acknowledged a technical hiccup on the Bali‑Jakarta leg that had been “resolved according to procedure.”
Meanwhile, Indonesia’s transport minister fired Lion Air’s technical director and three other officials this past Wednesday to speed up the investigation.
What’s at Stake: Boeing’s 737 MAX
The 737 MAX hit the market just last year; it had been accident‑free until this incident. It’s a “narrowbody” upgrade of the world’s most prolific family of commercial jets, known for strong safety—but this crash has renewed concerns about Indonesia’s patchy aviation record.
Flight Tracking Drama
According to flight‑tracking data, the first Sunday flight wobble after take‑off featured a dramatic 875‑foot drop in short order—an anomaly if you’d expect a smooth climb. The jet later stayed at 28,000 feet rather than the usual 36,000 feet.
Data‑Recorder Retrieval
Divers recovered the flight‑data recorder from the wreckage on a muddy sea floor off Jakarta. The National Transport Safety Committee (NTSC) will now dig deeper into the July and Monday flights.
Passenger Stories
- Two passengers on Sunday’s flight posted on Instagram about air‑conditioning and cabin lighting issues that had delayed the departure by nearly three hours.
- One passenger from JT43 joked that while the plane was going up and down, the seatbelt sign stayed on the entire time—so no one dared loosen their straps.
- Another passenger shared on Indonesia’s TVOne: “Everyone in the plane shouted Allahu Akbar… we recited all the prayers we knew.”
Final Take‑away
Two flights, one on a clear Sunday, the other a tragic Monday—all involving the same Boeing 737 MAX and a recurring technical glitch. The big questions now are: was the aircraft’s design at fault, or was it summer storm‑height procedures? The answers will play a huge role in future aviation safety in Indonesia and beyond.
