Japan Air Lines Flight 123
1985 plane crash in Japan From Wikipedia, the free encyclopedia
Japan Air Lines Flight 123 was a scheduled domestic passenger flight from Tokyo to Osaka, Japan. On August 12, 1985, the Boeing 747 flying the route suffered a severe structural failure and decompression 12 minutes into the flight. After flying under minimal control for a further 32 minutes, it crashed in the area of Mount Takamagahara, 100 kilometres (62 mi; 54 nmi) from Tokyo.
 The stricken jet photographed approximately 6 minutes before the crash. The vertical stabilizer is largely missing. | |
| Accident | |
|---|---|
| Date | August 12, 1985 |
| Summary | Crashed following in-flight structural failure and loss of control |
| Site | Mount Takamagahara, Ueno, Tano District, Gunma, Japan 36°0′5″N 138°41′38″E |
| Aircraft | |
 JA8119, the Boeing 747 involved in the accident, at Haneda Airport in 1984 | |
| Aircraft type | Boeing 747SR-46 |
| Operator | Japan Air Lines |
| IATA flight No. | JL123 |
| ICAO flight No. | JAL123 |
| Call sign | JAPAN AIR 123 |
| Registration | JA8119 |
| Flight origin | Haneda Airport, Tokyo, Japan |
| Destination | Itami Airport, Osaka, Japan |
| Occupants | 524 |
| Passengers | 509 |
| Crew | 15 |
| Fatalities | 520 |
| Injuries | 4 |
| Survivors | 4 |
The aircraft, featuring a high-density seating configuration, was carrying 524 people. The crash killed all 15 crew members and 505 of the 509 passengers on board, leaving four survivors. An estimated 20 to 50 passengers survived the initial crash but died from their injuries while awaiting rescue. The crash is the deadliest single-aircraft accident in aviation history[1] and remains the deadliest aviation incident in Japan.[2]
Japan's Aircraft Accident Investigation Commission (AAIC),[3]: 129 assisted by the U.S. National Transportation Safety Board,[4] concluded that the structural failure was caused by a faulty repair by Boeing technicians following a tailstrike seven years earlier. When the faulty repair eventually failed, it resulted in a rapid decompression that ripped off a large portion of the tail and caused the loss of all hydraulic systems and the flight controls.
Background
Aircraft
The Boeing 747SR-46 with registration JA8119 (serial number 20783, line number 230), was built and delivered to Japan Air Lines in 1974 (prior to their name change to "Japan Airlines"). It had accumulated slightly more than 25,000 flight hours and 18,800 cycles (one cycle consisting of takeoff, cabin pressurization, depressurization, and landing).[1]
1978 tailstrike incident
On June 2, 1978, while operating Japan Air Lines Flight 115 along the same route, JA8119 bounced heavily on landing while carrying out an instrument approach to runway 32L at Itami Airport. The pilot then excessively flared the aircraft, causing a severe tail strike on the second touchdown. Of the 394 people on board, 25 sustained injuries, 23 minor and 2 serious. The tailstrike cracked open the aft pressure bulkhead. The damage was repaired by Boeing technicians, and the aircraft was returned to service.[5][3][6] The aircraft had flown for 8,830 hours at the time.[5]: 4
Crew
At the time of the accident, the aircraft was on the fifth of its six planned flights of the day.[3] The flight had 15 crew members, consisting of 3 cockpit crew and 12 cabin crew.
The cockpit crew consisted of:
- Captain Masami Takahama (高浜 雅己, Takahama Masami), aged 49, served as a training instructor for First Officer Yutaka Sasaki on the flight, supervising him while handling the radio communications,[7][8][9] and also acting as first officer. Takahama was a veteran pilot, having logged about 12,423 flight hours, including about 4,842 hours in 747s.
- First Officer Yutaka Sasaki (佐々木 祐, Sasaki Yutaka), age 39, was undergoing training for promotion to captain, and flew Flight 123 as one of his final training/evaluation flights, acting as captain.[3]: 14–15 He had logged about 3,963 flight hours, including about 2,665 hours in 747s.
- Flight Engineer Hiroshi Fukuda (福田 博, Fukuda Hiroshi), age 46, was a veteran flight engineer having logged about 9,831 flight hours, including about 3,846 hours in 747s.[3]
Passengers
Summarize
Perspective
| Nationality | Passengers | Crew | Survivors | Total |
|---|---|---|---|---|
 Japan | 487 | 15 | 4 | 502 |
 China | 1 | 0 | 0 | 1 |
 West Germany | 2 | 0 | 0 | 2 |
 British Hong Kong | 4 | 0 | 0 | 4 |
 India | 3 | 0 | 0 | 3 |
 Italy | 2 | 0 | 0 | 2 |
 South Korea | 3 | 0 | 0 | 3 |
 United Kingdom | 1 | 0 | 0 | 1 |
 United States | 6 | 0 | 0 | 6 |
| Total (9 Nationalities) | 509 | 15 | 4 | 524 |
The flight was during the Obon holiday period when many Japanese people make trips to their hometowns or to resorts.[10] Twenty-two non-Japanese were on board the flight,[11] including four residents of Hong Kong, two each from Italy and the United States, and one each from West Germany and the United Kingdom.[12] Some ostensible foreigners had dual nationality, and some of them were residents of Japan.[10]
The four survivors, all female, were seated on the left side and toward the middle of seat rows 54–60, in the rear of the aircraft.[3]: 22 They were Yumi Ochiai, an off-duty flight attendant; Hiroko and Mikiko Yoshizaki, a mother and her 8-year-old daughter; and Keiko Kawakami, a 12-year-old girl who lost her parents and sister in the crash.[13] Among the victims were Japanese singer and actor Kyu Sakamoto, and banker Akihisa Yukawa, the father of violinist and composer Diana Yukawa.[14][15]
The flight connected two of the largest cities of Japan, and a number of other celebrities initially booked the flight but ultimately had either switched to another flight or used the Tokaido Shinkansen instead. These include Sanma Akashiya, Masataka Itsumi and his family, Johnny Kitagawa, and the then cast of Shōten.[16][17][18] Some members of the Shonentai were also scheduled to travel with Kitagawa but had stayed in Tokyo.[18]
Sequence of events
Summarize
Perspective
Take-off and decompression
| Flight 123 audio transcript | |
|---|---|
 Flight 123 CVR and ATC transcript in English with map of flight on YouTube |
The aircraft landed as JL366 at Haneda Airport in Ōta, Tokyo, Japan, from Fukuoka Airport at 5:12 p.m. After almost an hour on the ground, Flight 123 pushed back from gate 18 at 6:04 p.m. and took off from Runway 15L at 6:12 p.m., 12 minutes behind schedule.[3]: 17 [8] Twelve minutes after takeoff, at 6:24 p.m., at near cruising altitude over Sagami Bay 3.5 miles (3.0 nmi; 5.6 km) east of Higashiizu, Shizuoka, the aircraft underwent rapid decompression,[3]: 83 bringing down the ceiling around the rear lavatories, damaging the unpressurised fuselage aft of the plane, unseating the vertical stabilizer, and severing all four hydraulic lines. A photograph taken from the ground shows the vertical stabilizer missing.[19]
The pilots set their transponder to broadcast a distress signal. Captain Takahama contacted Tokyo Area Control Center to declare an emergency, and request a return to Haneda Airport, descending and following emergency landing vectors to Oshima. Tokyo Control approved a right-hand turn to a heading of 090° east back toward Oshima, and the aircraft entered an initial right-hand bank of 40°, several degrees greater than observed previously. Captain Takahama ordered First Officer Sasaki to reduce the bank angle,[3]: 296 and expressed confusion when the aircraft did not respond to the control wheel being turned left. The flight engineer reported that hydraulic pressure was dropping. The captain repeated the order to reduce the bank angle, as the autopilot had disengaged. He ordered the first officer to bank it back, then ordered him to pull up. None of these attempted maneuvers produced a response. The pilots realised the aircraft had become virtually uncontrollable, and Captain Takahama ordered the copilot to descend.[3]: 297
6:27–6:34 p.m.
Heading over the Izu Peninsula at 6:26 p.m., the aircraft turned away from the Pacific Ocean and back toward the shore,[3]: 150 but only turned right far enough to fly a north-westerly course. Seeing that the aircraft was still flying west away from Haneda, Tokyo Control contacted the aircraft again. After confirming that the pilots were declaring an emergency, the controller asked the nature of the emergency. At this point, hypoxia appeared to have begun setting in, as the pilots did not respond. Also, the captain and co-pilot asked the flight engineer repeatedly if hydraulic pressure had been lost, seemingly unable to comprehend it.[3]: 298 Tokyo Control contacted the aircraft again and repeated the direction to descend and turn to a 90° heading to Oshima. Only then did the captain report that the aircraft had become uncontrollable. (Tokyo: "Japan Air 124 [sic] fly heading 090 radar vector to Oshima." JAL123: "But now uncontrol." Tokyo: "Uncontrol, roger understood.")[3]: 299
The aircraft traversed Suruga Bay and passed over Yaizu, Shizuoka, at 6:31:02 p.m.[3]: 7 Tokyo Control asked if they could descend, and Captain Takahama replied that they were now descending, stating that their altitude was 24,000 feet (7,300 m). Captain Takahama declined Tokyo Control's suggestion to divert to Nagoya Airport 72 nautical miles (83 mi; 133 km) away, instead preferring to land at Haneda, which had the facilities to handle the 747.[3]: 302 The flight data recorder shows that the flight did not descend, but was rising and falling uncontrollably.[3]: 1–6 With the total loss of hydraulic control and non-functional control surfaces, the aircraft entered phugoid oscillations lasting about 90 seconds, in which airspeed decreased as it climbed and increased as it fell. The rise in airspeed increased the lift over the wings, resulting in the aircraft climbing and slowing down, then descending and gaining speed again. Almost immediately after the separation of the stabiliser and rudder removed the only means of damping yaw, the aircraft began to exhibit Dutch roll, simultaneously yawing right and banking left, before yawing back left and banking right. At some points the banking motion became very profound, with large arcs of around 50° in cycles of 12 seconds.[20]
Despite the complete loss of control, the pilots continued to turn the control wheel, pull on the control column, and move the rudder pedals up until the moment of the crash.[3]: 7–12, 128 The pilots also began efforts to establish control using differential engine thrust,[3]: 19–24 as the aircraft slowly wandered back toward Haneda. Their efforts had limited success. The unpressurised aircraft rose and fell in an altitude range of 20,000–25,000 feet (6,100–7,600 m) for 18 minutes, from the moment of decompression until around 6:40 p.m., with the pilots seemingly unable to figure out how to descend without flight controls.[3]: 1–6 This was possibly due to the effects of hypoxia at such altitudes, as the pilots seemed to have difficulty comprehending their situation as the aircraft pitched and rolled uncontrollably. The pilots possibly were focused, instead, on the cause of the explosion they had heard, and the subsequent difficulty in controlling the jet.[3]: 126, 137–38 The flight engineer did say they should put on their oxygen masks when word reached the cockpit that the rear-most passenger masks had stopped working. None of the pilots put on their oxygen masks, however, though the captain simply replied "yes" to both suggestions by the flight engineer to do so. The accident report indicates that the captain's disregard of the suggestion is one of several features "regarded as hypoxia-related in [the] CVR record[ing]."[3]: 97 Their voices can be heard relatively clearly on the cockpit area microphone for the entire duration, until the crash, indicating that they did not put on their oxygen masks at any point in the flight.[3]: 96, 126
6:34–6:48 p.m.: Limited control
At 6:35 p.m. the flight engineer responded to multiple (hitherto unanswered) calls from Japan Air Tokyo via the SELCAL (selective-calling) system. Having just been informed about the inoperative oxygen masks, the flight engineer voiced the (erroneous) assumption that the R-5 door was broken and informed the company that they were making an emergency descent. Japan Air Tokyo asked if they intended to return to Haneda, to which the flight engineer responded that they were making an emergency descent, and to continue to monitor them.[3]: 306–07
Eventually, the pilots regained limited control of the aircraft by adjusting engine thrust. In doing so, they dampened the phugoid cycle and somewhat stabilised their altitude. However, given jet engines' inertia and the resulting response time (to changes in throttle), "[s]uppressing of Dutch roll mode by use of the differential thrust between the right and left engines is estimated practically impossible for a pilot."[3]: 89 Shortly after 6:40 p.m., they lowered the landing gear using the emergency extension system in an attempt to dampen the phugoid cycles and Dutch rolls further. This was somewhat successful, as the phugoid cycles were dampened almost completely, and the Dutch roll was damped significantly, but lowering the gear also decreased the directional control the pilots were getting by applying power to one side of the aircraft, and the aircrew's ability to control the aircraft deteriorated.[20]
Shortly after lowering the gear, the flight engineer asked if the speed brakes should be used, but the pilots did not acknowledge the request.[3]: 310 The aircraft then began a right-hand descending 420° turn from a heading of 040° at 6:40 p.m. to a heading of 100° at 6:45 p.m., flying in a loop over Otsuki, due to a thrust imbalance created from having the power setting on Engine 1 (the left-most engine) higher than the other three engines.[3]: 290 The aircraft also began descending from 22,400 feet (6,800 m) to 17,000 feet (5,200 m), as the pilots had reduced engine thrust to near idle from 6:43 to 6:48 p.m. Upon descending to 13,500 feet (4,100 m) at 6:45:46 p.m., the pilots again reported an uncontrollable aircraft.[3]: 324 At this time, the aircraft began to turn slowly to the left, while continuing to descend. The thicker air allowed the pilots more oxygen, and their hypoxia appeared to have subsided somewhat, as they were communicating more frequently.[3]: 97 The pilots also appeared to be understanding how grave their situation had become, with Captain Takahama exclaiming, "This may be hopeless" at 6:46:33 p.m.[3]: 317 At 6:47 p.m., the pilots recognised that they were beginning to turn toward the mountains. Despite efforts by the crew to get the aircraft to continue to turn right, it instead turned left, flying directly toward the mountainous terrain on a westerly heading.
Around 6:50 p.m., a photographer on the ground captured a photograph of the aircraft, which showed that the vertical stabiliser was missing.[3]: 108
6:48–6:55 p.m.: Final loss of control
As the aircraft continued west, it descended below 7,000 feet (2,100 m) and was getting dangerously close to the mountains. Because of the thicker air at lower altitude, the cabin altitude alert momentarily turned off at this time, before resuming for the rest of the flight. The captain briefly ordered maximum engine power to attempt to get the aircraft to climb to avoid the mountains, and engine power was added abruptly at 6:48 p.m., before being reduced back to near idle; then at 6:49 p.m., it was ordered raised again.[3]: 319 This greatly excited the phugoid motion,[3]: 291 and the aircraft pitched up, before pitching back down after power was reduced. When power was added again, the aircraft rapidly pitched up to 40°, and the airspeed dropped down to 108 knots (200 km/h; 124 mph) at 6:49:30 p.m.,[3]: 1–6, 291 briefly stalling at 9,000 feet (2,700 m). The captain immediately ordered maximum power at 6:49:40 p.m. as the stick shaker sounded.[3]: 320 The aircraft's airspeed increased as it was brought into an unsteady climb. Possibly in order to prevent another stall, at 6:51 p.m., the captain lowered the flaps to 5 units—due to the lack of hydraulics, using an alternate electrical system—in an additional attempt to exert control over the stricken jet. It took 3 minutes and 10 seconds for the trailing edge flaps to reach 5 units. The leading edge flaps except for the left and right outer groups were also extended and the extension was completed at 6:52:39 p.m.[3]: 291 [20] From 6:49:03 to 6:52:11 p.m., Japan Air Tokyo attempted to call the aircraft again via the SELCAL radio system. During the entire period, the SELCAL alarm continued to ring,[3]: 320–23 to which the pilots did not react.
The aircraft reached 13,000 feet (4,000 m) at 6:53 p.m., when the captain reported an uncontrollable aircraft for the third time. Shortly afterward, the controller asked the crew to switch the radio frequency to 119.7 for Tokyo Approach. Although the pilots did not acknowledge the request over the radio, they switched frequencies as instructed. Tokyo Approach then contacted the flight via the SELCAL system, briefly activating the corresponding alarm again until the flight engineer responded. At this point, the flight crew requested to be given their position, which, at 6:54 p.m., was reported to the flight as 45 nmi (83 km) northwest of Haneda, and 25 nmi (46 km) west of Kumagaya. At 6:55 p.m., the captain requested flap extension, and the co-pilot called out a flap extension to 10 units, but the flaps had already extended past 5 units at 6:54:30 p.m. and had reached 20 units 1 minute and 2 seconds later.[3]: 291 Meanwhile, the aircraft had started banking abnormally toward the right; this might have been most likely due to an imbalance in the lift generated by the left and right flaps.[3]: 90 Power was increased at the same time. While the flaps continued to extend, a differential thrust setting caused engine power on the left side to be slightly higher than on the right side, adding to the roll to the right.[3]: 291–92
One minute later, the flaps were extended to about 25 units, the bank angle exceeded 60°, and the nose began to drop.[3]: 292 Captain Takahama immediately ordered the flaps to be retracted[3]: 326 and power was added abruptly, but still with higher power settings on the left engines than on the right.[3]: 292 The asymmetric thrust settings continued to increase as the bank angle continued and exceeded 80°.[3]: 90 The captain was heard on the CVR desperately requesting for the flaps to be retracted and for more power to be applied in a last-ditch effort to raise the nose.[21][3]: 326–27 The aircraft continued an unrecoverable right-hand descent toward the mountains as the bank angle recovered to about 70° and engines were pushed to full power, during which the ground proximity warning system sounded.[3]: 292
In the final moments, as the airspeed exceeded 340 knots (630 km/h; 390 mph), the pitch attitude leveled out and the aircraft ceased descending, with the aircraft and passengers/crew being subjected to 3 g of upward vertical acceleration.[3]: 292
6:56 p.m.: Impact
The aircraft was still in a 40° right-hand bank when the right-most (#4) engine struck the trees on top of a ridge located 1.4 kilometres (0.87 mi) north-northwest of Mount Mikuni at an elevation of 1,530 metres (5,020 ft), which can be heard on the CVR recording. The backward shock of the impact, measuring 0.14 g, in addition to causing the loss of the thrust of the 4th engine, caused the aircraft to roll sharply to the right and the nose to drop again. The aircraft continued on this trajectory for 3 seconds until the right wing clipped another ridge containing a "U-shaped ditch" 520 metres (1,710 ft) west-northwest of the previous ridge at an elevation of 1,610 metres (5,280 ft). It is speculated that this impact separated the remainder of the weakened tail from the airframe, along with the outer third of the right wing, and the remaining three engines, which were "dispersed 500–700 metres (1,600–2,300 ft) ahead".[3]: 19, 91 After this impact, the aircraft flipped on its back, struck another ridge 570 metres (1,870 ft) northwest from the second ridge, near Mount Takamagahara, and exploded.
The impact registered on a seismometer located in the Shin-Etsu Earthquake Observatory at Tokyo University from 6:56:27 p.m. as a small shock, to 6:56:32 p.m. as a larger shock, believed to have been caused by the final crash. The shockwaves took an estimated 2.0–2.3 seconds to reach the seismometer, making the estimated time of the final crash 6:56:30 p.m.[3]: 108–09 Thus, 32 minutes had elapsed from the bulkhead failure to the crash.[3]: 123, 127 [13]
Crash site
The aircraft crashed at an elevation of 1,565 metres (5,135 ft) in Sector 76, State Forest, 3577 Aza Hontani, Ouaza Narahara, Ueno Village, Tano District, Gunma Prefecture. The east-west ridge is about 2.5 kilometres (8,200 ft) north-northwest of Mount Mikuni.[3] Ed Magnuson of Time magazine said that the area where the aircraft crashed was referred to as the "Tibet" of Gunma Prefecture.[8]
Delayed rescue operation
Summarize
Perspective
A United States Air Force navigator stationed at Yokota Air Base published an account in 1995, stating that the U.S. military had monitored the distress calls and prepared a search-and-rescue operation that was aborted at the call of Japanese authorities. A U.S. Air Force C-130 crew was the first to spot the crash site 20 minutes after impact, while it was still daylight, and radioed the location to the Japanese and Yokota Air Base, where an Iroquois helicopter was dispatched.[22] An article in the Pacific Stars and Stripes from 1985 stated that personnel at Yokota were on standby to help with rescue operations, but were never called by the Japanese government.[23]
A JSDF helicopter later spotted the wreck after nightfall. Poor visibility and the difficult mountainous terrain prevented it from landing at the site. The pilot reported from the air no signs of survivors. Based on this report, JSDF personnel on the ground did not set out to the site on the night of the crash. Instead, they were dispatched to spend the night at a makeshift village erecting tents, constructing helicopter landing ramps, and engaging in other preparations, 63 kilometres (39 miles) from the crash site. Rescue teams set out for the site the following morning. Medical staff later found bodies with injuries suggesting that people had survived the crash only to die from shock, exposure overnight in the mountains, or injuries that, if tended to earlier, would not have been fatal.[20] One doctor said, "If the discovery had come 10 hours earlier, we could have found more survivors."[8]
One of the four survivors, off-duty Japan Air Lines flight purser Yumi Ochiai (落合 由美, Ochiai Yumi) recounted from her hospital bed that she recalled bright lights and the sound of helicopter rotors shortly after she awoke amid the wreckage, and while she could hear screaming and moaning from other survivors, these sounds gradually died away during the night.[20]
Investigation
Summarize
Perspective
The official cause of the crash according to the report published by Japan's Aircraft Accident Investigation Commission is:
- The aircraft was involved in a tailstrike incident at Osaka International Airport seven years earlier as JAL Flight 115, which damaged the aircraft's aft pressure bulkhead.
- The subsequent repair of the bulkhead did not conform to Boeing's approved repair methods. For reinforcing a damaged bulkhead, Boeing's repair procedure calls for one continuous splice plate with three rows of rivets.[24] The Boeing repair technicians, however, had used two splice plates parallel to the stress crack.[25][4] Cutting the plate in this manner negated the effectiveness of the row of rivets, reducing the part's resistance to fatigue cracking to about 70% of that for a correct repair. The post-repair inspection by JAL did not discover the defect, as it was covered by overlapping plates.[3][4][26] During the investigation, the Accident Investigation Commission calculated that this incorrect installation would fail after about 11,000 pressurization cycles; the aircraft accomplished 12,318 successful flights from the time that the faulty repair was made to when the crash happened.[3]: 101–05
- Consequently, after repeated pressurization cycles during normal flight, the bulkhead gradually started to crack near the row of rivets holding it together. When it finally failed, the resulting rapid decompression ruptured the lines of all four hydraulic systems and ejected the vertical stabiliser. With many of the aircraft's flight controls disabled, the aircraft became uncontrollable.[3]: 128
In an unrelated incident on 19 August 1982, while under the control of the first officer, JA8119 suffered a runway strike of the No. 4 engine on landing at Chitose Air Base in poor visibility. This was repaired successfully and the aircraft again returned to service. This incident did not contribute to the Flight 123 accident.[3]: 102
Aftermath and legacy
Summarize
Perspective
The Japanese public's confidence in Japan Air Lines took a dramatic downturn in the wake of the disaster, with passenger numbers on domestic routes dropping by one-third. Rumors persisted that Boeing had admitted fault to cover up shortcomings in the airline's inspection procedures, thereby protecting the reputation of a major customer.[20] In the months after the crash, domestic air traffic decreased by as much as 25%. In 1986, for the first time in a decade, fewer passengers boarded JAL's overseas flights during the New Year period than the previous year. Some of them considered switching to All Nippon Airways, JAL's main competitor, as a safer alternative.[27]
JAL paid ¥780 million (US$7.6 million) to the victims' relatives in the form of "condolence money" without admitting liability. JAL president Yasumoto Takagi resigned.[20] In the aftermath of the incident, Hiroo Tominaga, a JAL maintenance manager, died from suicide intended to atone for the incident,[28] as did Susumu Tajima, an engineer who had inspected and cleared the aircraft as flightworthy, whose suicide note cited "work problems".[29] In the end, JAL, Boeing, and the Japanese government paid substantial compensation to the victims' families.[30]
In compliance with standard procedures, JAL retired flight number 123 for their Haneda-Itami routes, changing it to Flight 121 and Flight 127 on September 1, 1985. While Boeing 747s were still used on the same route operating with the new flight numbers in the years following the crash, they were replaced by the Boeing 767 or Boeing 777 in the mid-1990s. Boeing 747-100SRs continued to serve JAL on domestic routes until their retirement in 2006, having been replaced by newer widebody aircraft, such as the Boeing 747-400D and Boeing 777, introduced during the 1990s and early 2000s. Boeing 747 operations at JAL ended in 2011 when the last 747-400 was returned to the lessor as part of the airline's efforts to cut costs, with twin-engined widebodies such as the Boeing 767, Boeing 787 Dreamliner, and Airbus A350 operating these routes today.[citation needed]
This would not be the only time that a 747 crashed due to faulty repair work following a tailstrike. In May 2002, 17 years after Flight 123's crash and 22 years after the accident aircraft's repair, China Airlines Flight 611 from Taipei to Hong Kong with 225 people on board crashed with no survivors when it broke up while cruising at around 35,000 feet. Like Flight 123, a doubler plate was not installed based upon Boeing standards.
In 2009, stairs with a handrail were installed to facilitate visitors' access to the crash site. On August 12, 2010, for the 25th anniversary of the accident, Japan Land, Infrastructure, Transport, and Tourism Minister Seiji Maehara visited the site to remember the victims.[31] Families of the victims, together with local volunteer groups, hold an annual memorial gathering every August 12 near the crash site in Gunma Prefecture.[32]
The crash led to the 2006 opening of the Safety Promotion Center,[33][34] which is located on the grounds of Haneda Airport.[35] This center was created for training purposes to alert employees to the importance of airline safety and their responsibility to ensure safety. The center has displays regarding aviation safety, the history of the crash, and selected pieces of the aircraft and passenger effects (including handwritten farewell notes). It is open to the public by appointment made between one day and two months before the visit.[36]
The captain's daughter, Yoko Takahama, who was a high-school student at the time of the crash, went on to become a JAL flight attendant.[37]
On June 24, 2022, an oxygen mask belonging to Flight 123 was found near the crash site during road repair work. The discovery came nearly a year after engine parts were also found in the same area.[38]
In popular culture
- The events of Flight 123 were featured in "Out of Control", a season-three (2005) episode of the Canadian TV series Mayday,[39] which is entitled Air Emergency and Air Disasters in the U.S., and Air Crash Investigation in the UK and elsewhere around the world. The dramatization was broadcast with the title "Osutaka-no-One (御巣鷹の尾根)"(translation: Osutaka Ridge) in Japan. The flight was also included in a Mayday season-six (2007) Science of Disaster special, entitled "Fatal Flaw",[40] which was broadcast with the title "Fatal Fix" in the United Kingdom, Australia, and Asia. The crash was covered again in season 23 of Mayday, in the episode titled "Pressure Point".[41]
- It is featured in season 1, episode 2, of the TV show Why Planes Crash, in an episode called "Breaking Point".
- The documentary series Aircrash Confidential featured the crash in a second-season episode titled "Poor Maintenance", which first aired on March 15, 2012, on the Discovery Channel in the United Kingdom.[42][43]
- The National Geographic Channel's documentary series Seconds from Disaster featured the accident in season six, episode six, titled "Terrified over Tokyo", released December 3, 2012.[citation needed]
- Seventeen (titled in Japanese as Climber's High) the best-selling novel by Hideo Yokoyama, revolves around the reporting of the crash at the fictional newspaper Kita-Kanto Shimbun. Yokoyama was a journalist at the Jōmō Shimbun at the time of the crash. A film released in 2008, and also titled Climber's High, is based on the novel.[44]
- In 2009, the film Shizumanu Taiyō, starring Ken Watanabe, was released for national distribution in Japan. The film gives a semifictional account of the internal airline corporate disputes and politics surrounding the crash. The film does not mention Japanese Air Lines by name, using the name "National Airlines", instead. JAL not only refused to co-operate with the making of the film,[45] but also bitterly criticised the film, saying that it "not only damages public trust in the company but [also] could lead to a loss of customers."[46] The movie features music by Diana Yukawa, whose father was one of the victims of this disaster.
- The cockpit voice recording of the incident was incorporated into the script of a 1999 play called Charlie Victor Romeo.[47]
- The 2004 album Reise, Reise by German Neue Deutsche Härte band Rammstein is loosely inspired by the crash. The final moments of the cockpit voice recording are hidden in the pregap of the first track on some CD pressings of the album.[48]
See also
Sources
- Aircraft Accident Investigation Commission (June 19, 1987). Nihonkōkū (kabu) shozoku Boeing 747 SR-100-gata JA8119 Gunma ken Tano-gun Ueno-mura 日本航空(株)所属 ボーイング 747SR-100型 JA8119 群馬県多野郡上野村 [Japan Airlines Co., Ltd. Boeing 747SR-100 JA8119 Ueno Village, Tano District, Gunma Prefecture] (Report) (in Japanese).
- Aircraft Accident Investigation Commission (July 19, 1987). Aircraft Accident Investigation Report on Japan Air Lines JA8119, Boeing 747 SR-100 (Tentative Translation from Original in Japanese) (PDF) (Report). Archived (PDF) from the original on August 28, 2021.
- Aircraft Accident Investigation Commission (December 14, 1978). Nihonkōkū kabushikigaisha shozoku bōingu-shiki 747 SR-100-gata JA8119 ni kansuru kōkū jiko hōkoku-sho 日本航空株式会社所属 ボーイング式747SR-100型JA8119に関する航空事故報告書 [Japan Airlines Co., Ltd. Boeing 747SR-100 type JA8119 Aviation Accident Report] (PDF) (Report) (in Japanese). Archived from the original (PDF) on August 28, 2021. (Tailstrike incident report)
- Hood, Christopher (2013). Dealing with Disaster with Japan: Responses to the Flight JL123 Crash. Taylor & Francis. ISBN 9781136641091.
References
External links
Wikiwand in your browser!
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.
