Japan Air Lines Flight 123
Japan Air Lines Flight 123 (JAL123) was a scheduled domestic Japan Air Lines passenger flight from Haneda Airport in Tokyo to Itami International Airport in Osaka. On August 12, 1985, the Boeing 747SR operating this flight suffered a sudden decompression 12 minutes into the flight, and crashed in the area of Mount Takamagahara, Ueno, Gunma Prefecture, 100 kilometres (62 mi; 54 nmi) from Tokyo 32 minutes later. The crash site was on Osutaka Ridge, near Mount Osutaka.
![]() JA8119, the aircraft involved in the accident, seen at Haneda Airport, in 1984, one year before the crash. | |
Accident | |
---|---|
Date | August 12, 1985 |
Summary | In-flight structural failure due to improper maintenance, leading to rapid decompression and loss of control systems exacerbated by hypoxia |
Site | Mount Takamagahara, Ueno, Gunma Prefecture, Japan 36°0′5″N 138°41′38″E |
Aircraft | |
Aircraft type | Boeing 747-146SR |
Operator | Japan Air Lines |
IATA flight No. | JL123 |
ICAO flight No. | JAL123 |
Call sign | JAPAN AIR 123 |
Registration | JA8119 |
Flight origin | Haneda Airport, Tokyo |
Destination | Itami Airport, Osaka |
Occupants | 524 |
Passengers | 509 |
Crew | 15 |
Fatalities | 520 |
Injuries | 4 |
Survivors | 4 |
Japan's Aircraft Accident Investigation Commission (AAIC) concluded,[1]: 129 agreeing with investigators from the U.S. National Transportation Safety Board,[2] that the rapid decompression was caused by a faulty repair by Boeing technicians after a tailstrike incident during a landing at Osaka Airport in 1978 as JAL Flight 115. The rear bulkhead of the plane had been repaired with an improperly installed doubler plate, compromising the plane's airworthiness. Cabin pressurization continued to expand and contract the improperly repaired bulkhead until the day of the accident, when the faulty repair failed, causing a rapid decompression that ripped off a large portion of the tail and caused the loss of hydraulic controls to the entire plane.
The aircraft, which was configured with increased economy-class seating, was carrying 524 people. All 15 crew members and 505 of the 509 passengers died in the accident. Some of the passengers survived the initial crash but died of their injuries hours later while awaiting rescue. Surpassing the fatalities of All Nippon Airways Flight 58, which crashed 14 years earlier with 162 fatalities, it is the deadliest single-aircraft accident both in Japan and global aviation history.[3]
The event is known in Japan as The crash accident of Japan Air Lines Jumbo Jet (Japanese: 日航ジャンボ機墜落事故).[4]
Background
Aircraft
The accident aircraft, a Boeing 747-146SR, registration JA8119, serial number 20783, line number 230, first flew on January 28, 1974, and was delivered to Japan Air Lines in February 1974. It had accumulated slightly more than 25,000 flight hours and 18,835 cycles[3] (one cycle consists of a takeoff, cabin pressurization, and a landing) in service.
Tailstrike incident
On June 2, 1978, Japan Air Lines Flight 115, a scheduled domestic passenger flight from Tokyo's Haneda Airport to Itami Airport, Osaka Prefecture, was carrying out an instrument landing system (ILS) approach to runway 32L at Itami Airport in Japan but bounced heavily on landing. The pilot excessively flared the plane, causing a severe tail strike. No fatalities occurred among the 394 people on board, but 25 people were injured, 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][1][6]
The crew of Flight 115 consisted of a 41-year-old captain who had 7,912 flight hours, including 220 hours on the Boeing 747. The 36-year-old first officer had 564 flight hours, with 286 hours on the 747. The 44-year-old flight engineer had 4,070 hours and was the most experienced on the Boeing 747 out of all crew members, having flown 2,780 hours on it.[5]: 3–4 The aircraft had flown for 8,830 hours at the time of the tailstrike incident.[5]: 4
Crew
At the time of the accident, the aircraft was on the fifth of its six planned flights of the day.[1] The flight had 15 crew members, including 3 cockpit crew and 12 flight attendants.
The cockpit crew consisted of:
- Captain Masami Takahama (高浜 雅己, Takahama Masami) served as a training instructor for First Officer Yutaka Sasaki on the flight, supervising him while handling the radio communications,[7][8][9] while also acting as the first officer. Takahama was a veteran pilot, having logged around 12,423 total flight hours, roughly 4,842 hours of which were accumulated flying 747s. Takahama was aged 49 at the time of the accident.
- First Officer Yutaka Sasaki (佐々木 祐, Sasaki Yutaka) was undergoing training for promotion to the rank of captain, and flew Flight 123 as one of his final training/evaluation flights, acting as captain on the flight.[1]: 14–15 Sasaki, who was 39 years old at the time of the accident, had about 3,963 total flight hours to his credit, and had logged roughly 2,665 hours in the 747.
- Flight Engineer Hiroshi Fukuda (福田 博, Fukuda Hiroshi), a 46-year-old veteran flight engineer, had approximately 9,831 total flight hours, of which roughly 3,846 hours were accrued flying 747s.[1]
Passengers
Nationality | Passengers | Crew | Fatalities | Survivors | Total |
---|---|---|---|---|---|
Japan | 487 | 15 | 498 | 4 | 502 |
China | 1 | — | 1 | — | 1 |
West Germany | 2 | — | 2 | — | 2 |
Hong Kong | 4 | — | 4 | — | 4 |
India | 3 | — | 3 | — | 3 |
Italy | 2 | — | 2 | — | 2 |
South Korea | 3 | — | 3 | — | 3 |
United Kingdom | 1 | — | 1 | — | 1 |
United States | 6 | — | 6 | — | 6 |
Total | 509 | 15 | 520 | 4 | 524 |
![](../I/Japan_Airlines_123_-_sitting_plan-en.svg.png.webp)
The flight was around the Obon holiday period in Japan when many Japanese people make yearly trips to their hometowns or resorts.[10] Twenty-two non-Japanese were on board the flight.[11] By August 13, 1985, a spokesman for Japan Airlines stated that the list included 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 foreigners had dual nationalities, 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.[1]: 22
Kyu Sakamoto, who was famous for singing "Ue o Muite Arukō", known in Anglophone countries under the title "Sukiyaki", was among those who perished in the crash.[13]
Sequence of events
Take-off and decompression
![](../I/Japan_Airlines_123_fig01_Estimated_flight_path_of_JA8119_ja.png.webp)
External video | |
---|---|
![]() |
The aircraft landed at Haneda from Chitose Airport at 4:50 p.m. as JL514. After more than an hour on the ground, Flight 123 pushed back from gate 18 at 6:04 p.m.[1] and took off from Runway 15L[1] at Haneda Airport in Ōta, Tokyo, Japan, at 6:12 p.m., 12 minutes behind schedule.[14] At about 6:24 p.m. (or 12 minutes after takeoff), 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[1]: 83 bringing down the ceiling around the rear lavatories, damaging the unpressurized fuselage aft of the plane, unseating the vertical stabilizer, and severing all four hydraulic lines. A photograph taken from the ground confirmed that the vertical stabilizer was missing.[15]
The pilots set their transponder to broadcast a distress signal. Afterward, Captain Takahama contacted Tokyo Area Control Center to declare an emergency, and to request to 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 towards Oshima, and the aircraft entered an initial right-hand bank of 40°, several degrees greater than observed previously. Captain Takahama, alarmed, ordered First Officer Sasaki to bank the aircraft back ("Don't bank so much.").[1]: 296 When the aircraft did not respond to the control wheel being turned left, he expressed confusion, after which the flight engineer reported that the hydraulic pressure was dropping. The captain repeated the order to reduce the bank, as the autopilot had disengaged. He then ordered the first officer to bank it back, then ordered him to pull up. All of these maneuvers produced no response. At this point, the pilots realized that the aircraft had become virtually uncontrollable, and Captain Takahama ordered the copilot to descend.[1]: 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 towards the shore.[1]: 150 Due to the apparent loss of control, the aircraft did not follow Tokyo Control's directions and 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 requested as to the nature of the emergency. At this point, hypoxia appears 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 was lost, seemingly unable to comprehend it. (Flight engineer: "Hydro pressure all loss." Co-pilot: "All loss?" Captain: "No, look." Flight engineer: "All loss." Co-pilot: "All loss?" Flight Engineer: "Yes.")[1]: 298 Tokyo Control then 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.")[1]: 299
After traversing Suruga Bay and passing over Yaizu, Shizuoka,[1]: 7 at 6:31:02 p.m., Tokyo Control asked the crew if they could descend, and Captain Takahama replied that they were now descending, and stated that the aircraft's altitude was 24,000 feet (7,300 m) after Tokyo Control requested their altitude. Captain Takahama also declined Tokyo Control's suggestion to divert to Nagoya Airport 72 nautical miles (83 mi; 133 km) away, instead preferring to land at Haneda,[1]: 302 which had the facilities to handle the 747. The flight data recorder shows that the flight did not descend, but was instead rising and falling uncontrollably.[1]: 1–6 Hydraulic fluid completely drained away through the rupture. With the total loss of hydraulic control and non-functional control surfaces, the aircraft began up and down oscillations in phugoid cycles lasting about 90 seconds each, during which the aircraft's airspeed decreased as it climbed, then increased as it fell. The rise in airspeed increased the lift over the wings, which resulted in the aircraft climbing and slowing down, then descending and gaining speed again. The loss of the vertical stabilizer and the rudder removed the only means of damping yaw, and the aircraft lost virtually all meaningful yaw stability. Almost immediately after the separation of the stabilizer, the aircraft began to exhibit Dutch roll, simultaneously yawing right and banking left, before yawing back left and banking right. At some points during the flight, the banking motion became very profound, with the banks in large arcs around 50° back and forth in cycles of 12 seconds.[16]
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.[1]: 7–12, 128 The pilots also began efforts to establish control using differential engine thrust,[1]: 19–24 as the aircraft slowly wandered back towards Haneda. Their efforts were of limited success. The unpressurized aircraft rose and fell in an altitude range of 20,000–24,000 feet (6,100–7,300 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.[1]: 1–6 This is 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 heard, and the subsequent difficulty in controlling the jet.[1]: 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]."[1]: 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.[1]: 96, 126
6:34–6:48 p.m.
Shortly before 6:34 p.m., Japan Air Tokyo attempted to call the flight via the selective-calling system multiple times. At 6:35 p.m., the flight responded, with the flight engineer handling communications to the company. The company stated that they had been monitoring the emergency, and the flight engineer, having been notified by a flight attendant that the R-5 masks had stopped working, replied that they believed the R-5 door was broken and 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.[1]: 306–07
Eventually, the pilots were able to achieve limited control of the aircraft by adjusting engine thrust, and in doing so, they were able to dampen the phugoid cycle and somewhat stabilize their altitude. Suppressing the Dutch roll was another matter, as the engines cannot respond quickly enough to counter the Dutch roll. According to the accident report, "Suppressing of Dutch roll mode by use of the differential thrust between the right and left engines is estimated practically impossible for a pilot."[1]: 89 Shortly after 6:40 p.m., the landing gear was lowered in an attempt to damp the phugoid cycles and Dutch rolls further, and to attempt to decrease the aircraft's airspeed to descend. 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.[16]
Shortly after lowering the gear, the flight engineer asked if the speed brakes should be used ("Shall we use speed brakes?"), but the pilots did not acknowledge the request.[1]: 310 The aircraft then began a right-hand descending 42° turn from a heading of 040° at 6:40 p.m. to a heading of 100° at 6:45 p.m. 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.[1]: 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.[1]: 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.[1]: 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.[1]: 317 At 6:47 p.m., the pilots recognized that they were beginning to turn towards the mountains, and despite efforts by the crew to get the aircraft to continue to turn right, it instead turned left, flying directly towards the mountainous terrain on a westerly heading.
Around 6:47 p.m., a photographer on the ground captured a photograph of the aircraft, which showed that the vertical stabilizer was missing.
6:48–6:55 p.m.
![](../I/Japan_Airlines_123_124_The_accident_aircraft_flying_over_Okutama.png.webp)
As the aircraft continued west, it descended below 7,000 feet (2,100 m) and was getting dangerously close to the mountains. The lower altitude and thicker air caused the cabin altitude alert to momentarily turn itself 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.[1]: 319 This greatly excited the phugoid motion,[1]: 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° at 6:49:30 p.m.,[1]: 1–6 briefly stalling at 8,000 feet (2,400 m). The captain immediately ordered maximum power at 6:49:40 p.m. as the stick shaker sounded ("Ah, no good... Stall. Max power. Max power. Max power.").[1]: 320 The aircraft's airspeed increased as it was brought into an unsteady climb. Possibly as a measure to prevent a recurrence of stalling, due to the lowered airspeed caused by the drag of the landing gear, the crew quickly discussed lowering the flaps. Without hydraulics, the captain expressed that this would not work, but the flight engineer pointed out this could be done via an alternate electrical system.[1]: 322 At 6:51 p.m., the captain lowered the flaps 5 units as an additional attempt to exert control over the stricken jet.[1]: 291 [16] During the period from 6:49:03 – 6:52:11 p.m., Japan Air Tokyo attempted to call the aircraft via the selective-calling radio system. During the entire 3-minute period, the SELCAL alarm continued to ring according to the CVR recordings,[1]: 320–23 the pilots most likely ignored it due to the difficulty they were experiencing at the time.
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 to talk to the Tokyo Approach ("Japan Air 123, switch the frequency to 119.7 please!"), and while the pilots did not acknowledge the request over the radio, they did as instructed (Captain: "Yes, Yes, 119.7" Co-pilot: "Ah, Yes, number 2" Captain: "119.7" Co-pilot: "Yes" Flight Engineer: "Shall we try?" Co-pilot: "Yes"). Tokyo Approach then contacted the flight via the SELCAL system, briefly activating the SELCAL alarm again until the flight engineer responded to Tokyo's request. At this point, the captain asked the flight engineer to request their position (Captain: "Request position" Flight engineer: "Request position"). At 6:54 p.m., this 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, while the flaps were already being extended from 5 units at 6:54:30 p.m.. This began to cause the aircraft to begin to a bank to the right, possibly due to an imbalance in the lift between the left and right flaps. Power was increased at the same time. A differential thrust setting caused engine power on the left side to be slightly higher than on the right side. This contributed to further increasing the bank angle to the right.[1]: 291–92
One minute later, the flaps were extended to 25 units, which caused the aircraft to bank dramatically to the right beyond 60°, and the nose began to drop.[1]: 292 Captain Takahama immediately ordered the flaps to be retracted ("Hey, halt the flap"),[1]: 326 and power was added abruptly, but still with engine power higher on the left vs. the right engines.[1]: 292 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[17][1]: 326–27 (Captain: "Power! Flap stop crowding together." Co-pilot: "Flap up, flap up, flap up, flap up!" Captain: "Flap up?" Co-pilot: "Yes." Captain: "Power. Power! Flap!" Flight engineer: "It is up!" Captain: "Raise the nose. Raise the nose! Power!"). The aircraft continued to enter an unrecoverable right-hand descent into the mountains as the engines were pushed to full power, during which the ground proximity warning system sounded, and the captain knew it was too late to recover (Captain: "We can not do anything now!"). 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.[1]: 292
6:56 p.m. Time of impact
![](../I/Japan_crash.jpg.webp)
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 bank sharply back 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). This impact is speculated to have separated the remainder of the weakened tail from the airframe, the outer third of the right-wing, as well as the remaining three engines, which were "dispersed 500–700 metres (1,600–2,300 ft) ahead".[1]: 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.[1]: 108–09
After the crash
The aircraft's crash point, at an elevation of 1,565 metres (5,135 ft), is 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.[1] Ed Magnuson of Time magazine said that the area where the aircraft crashed was referred to as the "Tibet" of Gunma Prefecture.[8] The elapsed time from the bulkhead failure to the crash was 32 minutes.[1]: 123, 127 [18]
Delayed rescue operation
![](../I/Japan_location_map_with_side_map_of_the_Ryukyu_Islands.svg.png.webp)
![](../I/Green_pog.svg.png.webp)
RJOO
![](../I/Blue_pog.svg.png.webp)
RJTT
![](../I/Red_X.svg.png.webp)
Crash location
Tokyo International Airport (flight origin)
Osaka International Airport (destination)
A United States Air Force navigator stationed at Yokota Air Base published an account in 1995 that stated 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.[19] 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.[20]
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 mi) 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.[16] One doctor said, "If the discovery had come 10 hours earlier, we could have found more survivors."[21]
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.[16]
Investigation
The official cause of the crash according to the report published by Japan's Aircraft Accident Investigation Commission is:
![](../I/JA8119_Bulkhead_Repair_en.png.webp)
- 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.[22] The Boeing repair technicians, however, had used two splice plates parallel to the stress crack.[23][2] Cutting the plate in this manner negated the effectiveness of one of the rows 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.[1][2][24] During the investigation, the Accident Investigation Commission calculated that this incorrect installation would fail after about 10,000 pressurization cycles; the aircraft accomplished 12,318 successful flights from the time that the faulty repair was made to when the crash happened.[1]: 101–05
- Consequently, after repeated pressurization cycles during normal flight, the bulkhead gradually started to crack near one of the two rows 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 stabilizer. With many of the aircraft's flight controls disabled, the aircraft became uncontrollable.[1]: 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.[1]: 102
Aftermath and legacy
![](../I/Fujioka_city_Japan_Airlines_Flight_123_accident_monument.jpg.webp)
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.[16] In the months after the crash, domestic 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.[25]
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.[16] In the aftermath of the incident, Hiroo Tominaga, a JAL maintenance manager, died from suicide intended to atone for the incident,[26] as did Susumu Tajima, an engineer who had inspected and cleared the aircraft as flightworthy, due to difficulties at work.[27]
In compliance with standard procedures, Japan Air Lines 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 777, Boeing 787 Dreamliner, and Airbus A350 utilized on the routes instead.[28]
In 2009, stairs with a handrail were installed to facilitate visitors' access to the crash site. Japan Land, Infrastructure, Transport, and Tourism Minister Seiji Maehara visited the site on August 12, 2010, to remember the victims.[29] Families of the victims, together with local volunteer groups, hold an annual memorial gathering every August 12 near the crash site in Gunma Prefecture.[30]
![](../I/Cenotaph_of_the_japan_air_flight_123_at_osutaka_Ridge.JPG.webp)
The crash led to the 2006 opening of the Safety Promotion Center,[31][32] which is located in the Daini Sogo Building on the grounds of Haneda Airport.[33] 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 two months before the visit.[34]
The captain's daughter, Yoko Takahama, who was a high-school student at the time of the crash, went on to become a flight attendant for Japan Air Lines.[35]
Japanese banker Akihisa Yukawa had an undisclosed second family at the time he died in the crash. (His wife had earlier suffered severe brain injuries.) His girlfriend, Susanne Bayly, was pregnant with their second daughter at the time of the crash; she subsequently returned to London, where Yukawa and she had met, bringing with her their daughters. To avoid embarrassment to Yukawa's family, she accepted a settlement of £340,000, rather than claiming under the airline's compensation scheme. In 2002, the airline made a payment of an undisclosed amount to enable the daughters, Cassie and Diana, to complete their educations.[36]
On June 24, 2022, an oxygen mask belonging to Japan Air Lines 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.[37]
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,[38] 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 (御巣鷹の尾根)" in Japan. The flight was also included in a Mayday season-six (2007) Science of Disaster special, entitled "Fatal Flaw",[39] which was broadcast with the title "Fatal Fix" in the United Kingdom, Australia, and Asia. The crash will be covered again in season 23 of Mayday.[40]
- 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.[41][42]
- 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.
- 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.[43]
- 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,[44] but also bitterly criticized the film, saying that it "not only damages public trust in the company but [also] could lead to a loss of customers."[45] 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.[46]
- 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.[47]
See also
- List of aircraft accidents and incidents resulting in at least 50 fatalities
- China Airlines Flight 611 – a 2002 aviation accident also caused by faulty repairs to a tailstrike that occurred 22 years prior.
Similar accidents caused by major pressurization failures:
- British European Airways Flight 706 – 1971
- Far Eastern Air Transport Flight 103 – 1981
- Helios Airways Flight 522 – 2005
Similar accidents involving loss of flight controls:
- United Airlines Flight 232 – caused by a catastrophic engine failure, 1989
- Baghdad DHL attempted shootdown incident – caused by a surface-to-air missile striking the left-wing, 2003
- American Airlines Flight 96 and Turkish Airlines Flight 981 – caused by a cargo door failure; accidents happened in 1972 and 1974, respectively
- Continental Express Flight 2574 – caused by missing screws that maintenance workers had failed to replace
- Chalk's Ocean Airways Flight 101 – caused by structural failures in an aging plane that were not properly repaired
Bibliography
- 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
- "Aircraft Accident Investigation Report Japan Air Lines Co., Ltd. Boeing 747 SR-100, JA8119 Gunma Prefecture, Japan August 12, 1985" (PDF). Aircraft Accident Investigation Commission. June 19, 1987. Retrieved April 21, 2019.
- Horikoshi, Toyohiro (August 11, 2015). "U.S. leaked crucial Boeing repair flaw that led to 1985 JAL jet crash: ex-officials". The Japan Times. Retrieved September 20, 2020.
- Ranter, Harro. "ASN Aircraft accident Boeing 747SR-46 JA8119 Ueno". aviation-safety.net. Aviation Safety Network. Retrieved June 15, 2009.
- "日航ジャンボ機墜落事故とは" (in Japanese). kotobank. Retrieved September 20, 2022.
- "日本航空(株)所属 ボーイング式747SR-100型 JA8119に関する航空事故報告書" [Aviation accident report for Boeing 747SR-100 JA8119 belonging to Japan Airlines Co., Ltd.] (PDF) (in Japanese). Aircraft Accident Investigation Commission. December 14, 1978. Retrieved May 27, 2020.
- Ranter, Harro. "ASN Aircraft accident Boeing 747SR-46 JA8119 Osaka-Itami Airport (ITM)". aviation-safety.net. Aviation Safety Network. Retrieved January 31, 2019.
- Times, Clyde Haberman, Special To The New York (August 20, 1985). "Plane's Final Minutes: 'Raise the Nose'". The New York Times. Retrieved June 2, 2017.
- Magnuson, Ed. "Last Minutes of JAL 123." Time. 9171,1074738-1,00.html 1. Retrieved October 25, 2007.
- "Pictures of the three pilots". Retrieved January 22, 2013.
- Haberman, Clyde (August 13, 1985). "Jetliner Crashes with 524 Aboard in Central Japan". The New York Times. Retrieved June 2, 2017.
- "524 killed in worst single air disaster." The Guardian.
- Moosa, Eugene. "Jet Crash Kills Over 500 In Mountains of Japan." Associated Press at The Schenectady Gazette. Tuesday Morning August 13, 1985. First Edition. Volume 91 (XCI) No. 271. Front Page (p. 5?). Retrieved from Google News (1 of 2) on August 24, 2013. "JAL spokesman Geoffrey Tudor said two Americans were on the passenger list." and "JAL released a passenger list that included 21 non-Japanese names, and Tudor said there were two Americans, two Italians, one Briton, one West German, and four Chinese residents of Hong Kong"
- "Kin of JAL123 victims pray ahead of 35th anniversary of deadly 747 crash next month". The Japan Times. July 25, 2020. Retrieved February 19, 2021.
- Magnuson, Ed. "Last Minutes of JAL 123." Time. 2.
- "Special Report: Japan Air Lines Flight 123". AirDisaster.Com. August 12, 1985. Archived from the original on January 8, 2013. Retrieved January 22, 2013.
{{cite web}}
: CS1 maint: unfit URL (link) - Macarthur Job, Air Disaster Volume 2, Aerospace Publications, 1996, ISBN 1-875671-19-6: pp. 136–53
- "12 August 1985 – Japan Air Lines 123". Tailstrike.com. Retrieved December 31, 2018.
- "For Survivors and Kin, Joy and Sorrow". The New York Times. August 14, 1985. Retrieved June 2, 2017.
- Antonucci, Michael (August 27, 1995). "1985 air crash rescue botched, ex-airman says". Pacific Stars and Stripes. Tokyo. p. 1. Retrieved January 1, 2020 – via NewspapersArchive.com.
- Jimbo, Tetsuo; Drake, Hal (August 14, 1985). "Military on standby to help in JAL crash". Pacific Stars and Stripes. p. 1.
- "Last Minutes of JAL 123", Time, p.5. Retrieved October 25, 2007.
- "Case Details > Crash of Japan Air Lines B-747 at Mt. Osutaka". Sozogaku.com. Retrieved January 22, 2013.
- Witkin, Richard (September 6, 1985). "Clues Are Found in Japan Air Crash". The New York Times. Retrieved June 2, 2017.
- Witkin, Richard (September 8, 1985). "Boeing Says Repairs on Japanese 747 Were Faulty". The New York Times. ISSN 0362-4331. Retrieved September 20, 2020.
- Andrew Horvat, "United's Welcome in Japan Less Than Warm", Los Angeles Times February 28, 1986
- New York Times "J.A.L. Official Dies, Apparently a Suicide", September 22, 1985,
- The Associated Press "Engineer Who Inspected Plane Before Crash Commits Suicide", March 18, 1987
- "What Happened To Japan Airlines' Boeing 747s?". Simple Flying. August 15, 2019. Retrieved November 15, 2020.
- Mainichi News "毎日jp(毎日新聞)". Archived from the original on July 10, 2012. Retrieved August 12, 2010.
- 日航機事故28年、遺族ら灯籠流し 墜落現場の麓で [Japan Air Lines accident 28 years, bereaved family lanterns sink at the fall site]. 共同通信 (in Japanese). August 11, 2013. Retrieved August 12, 2013.
- "Why Japan Air Lines Opened a Museum to Remember a Crash", The Wall Street Journal. Retrieved March 2, 2007.
- Black Box as a Safety Device, The New York Times. Retrieved February 21, 2009.
- "Safety Promotion Center." Japan Air Lines. Retrieved August 18, 2010. Archived May 1, 2008, at the Wayback Machine
- "For Visitors of Safety Promotion Center – Safety and Flight Information Information". Japan Airlines Corporate Information. Retrieved July 27, 2012.
- 日航機墜落30年 機長の長女はいま… [Nikko Aircraft Crash 30 years The eldest daughter of the captain is now...]. livedoor News (in Japanese). 日テレNEWS24 (Nittele NEWS24). August 12, 2015. Retrieved August 12, 2015.
- Ward, David (March 8, 2002). "Air crash payout after 17 years". The Guardian. Retrieved June 18, 2022 – via www.theguardian.com.
- Pickett, Riley (August 6, 2022). "JAL Flight 123: Oxygen Mask Found Near 1985 Crash Site". Simple Flying. Retrieved August 7, 2022.
- "Out of Control". Mayday. Season 3. Episode 3. 2005. Discovery Channel Canada / National Geographic Channel.
- "Fatal Flaw". Mayday. Season 6. Episode 2. 2007. Discovery Channel Canada / National Geographic Channel.
- "Program Overview". www.cineflixrights.com. Retrieved August 13, 2022.
- Aircrash Confidential web page Archived November 20, 2010, at the Wayback Machine
- "Discovery Channel TV Listings for March 15, 2012". Discoveryuk.com. Retrieved January 22, 2013.
- "Climber's High". The Japan Times. July 11, 2008. Retrieved April 17, 2018.
- "Japanese films reach for the sky, but it's a good bet JAL wishes this one had stayed grounded". The Japan Times. October 23, 2009.
- Jiji, "JAL hits film's disparaging parallels," The Japan Times, November 4, 2009, p. 1.
- "Step inside the cockpit of six real-life air disasters". New York Post. January 26, 2014. Retrieved March 26, 2018.
- Daly, Joe (May 1, 2019). "Rammstein – The Ultimate Celebration – Bang Bangers!". Metal Hammer UK. p. 55.
External links
![](../I/Commons-logo.svg.png.webp)
- Learning from the Past Japan Air Lines
- Crash of Japan Air Lines B-747 at Mt. Osutaka
- JAL123 CVR (cockpit voice recorder) transcript
- "Christopher Hood's Research about JL123."
- JAL123 CVR (cockpit voice recorder) audio of the final moments of flight[Usurped!] (Archive[Usurped!])
- The record of JAL123 (Japanese with English place names) (Archive)
- CVR (cockpit voice recorder) audio of the final moments of flight on YouTube
- JAL123 Tokyo control communications records on YouTube
- Japan Air Lines Flight 123 – Out of Control. National Geographic Documentary on YouTube
- CVR recording (longer version) on YouTube
- Planesafe.org: JAL123 (Archive)
- The New York Times: J.A.L.'s Post-Crash Troubles
Simulation of the final 32 minutes with the CVR on YouTube