Created Thursday, Apr 22nd 2021 19:52Z, last updated Thursday, Apr 22nd 2021 19:52Z
A Jin Air Boeing 737-800, registration HL8243 performing flight LJ-262 from Kitakyushu (Japan) to Seoul (South Korea), was climbing out of Kitakyushu's runway 36 when the aircraft encountered turbulence causing injuries to a flight attendant. The aircraft continued to Seoul for a safe landing about 65 minutes after departure.

Japan's TSB reported the flight attendant received serious injuries during an upset during the climb out of Kitakyushu.

On Apr 22nd 2021 the JTSB released their final report concluding the probable causes of the accident were:

In this accident, it is highly probable that the Aircraft was strongly shaken by encountering clear air turbulence during the climb, which caused the cabin crew member who was standing in the center of the aft galley to fall down and fracture her right ankle.

The JTSB analysed:

(1) Sudden shaking in the Aircraft

No clouds were observed near the airspace of the accident site, however, it is highly probable that as described in 2.6 (2), around the airspace there was jet stream, below which VWS of about 20 kt/1,000 ft was also there. In addition, no aircraft whose wake turbulence might have affected the Aircraft was flying around her, therefore, it is highly probable that in the airspace, there might have occurred clear air turbulence caused by the jet stream. It is also highly probable that this clear air turbulence caused the Aircraft to shake.

Besides, in addition to the fact that along the flight route of the Aircraft, there were no such clouds that turbulence could be expected, according to the FDR records, any significant changes to be a sign of turbulence were not confirmed on the instruments in the cockpit. Therefore, it is probable that there was no sign of turbulence which the flight crew members could have detected.

(2) Judgment about the weather conditions along the flight route and the operation of seat belt sign

Based on the weather data obtained prior to the departure of the flight, the flight crew members were able to expect that they would encounter shear at between FL 240 and FL 270 during the climb after taking off from Kitakyushu Airport and the Aircraft would be shaken. However, the possibility of severe turbulence was indicated in the weather data checked in the previous flight before the departure from Incheon International Airport, but it was light turbulence in the actual flight. And in the weather forecast checked before the departure from Kitakyushu Airport, the turbulence in the accident flight was expected to be moderate, which was better than that that of the previous flight, therefore, it is somewhat likely that the flight crew members did not expect that the turbulence, which they would encounter after taking off from Kitakyushu Airport, could be so severe. As a result, it is somewhat likely that the flight crew member did not turn on the seat belt sign when the Aircraft was approaching the airspace where turbulence was expected.

It is desirable for flight crew members to make decisions on the operation of seat belt sign from a safer side, by the information obtained from pre-flight meteorological data.

(3) The Purser’s falling

Although the Purser was instructed by the PIC at the pre-flight briefing, to beware of turbulence that was expected during the climb, the seat belt sign was turned off when severe turbulence occurred, and then the Purser was not informed by flight crew members that the Aircraft was approaching the airspace where turbulence was expected. Therefore, it is highly probable that the Purser, who was standing, got off balance to fall down because the Aircraft repeatedly fluctuated with vertical and horizontal accelerations, irregular left and right movements, and irregular rotational movements at the same time in a short period of time.

Related Flight: LJ262, Twitter: #LJ262, Jin Air News
Flight Delay Compensation up to 600€/$: Claim for delay, cancellation, or baggage issues >
Flight-schedule data supplied by Aviation Edge Real-time Flight Schedules API.