http://avherald.com/h?article=5132b9fe The Aviation Herald Last Update: Tuesday, Jan 2nd 2024 20:55Z 29940 Articles available Events from Mar 23rd 1994 to Jan 2nd 2024 www.avherald.com Incidents and News in Aviation Next Sort list List Earlier List by: by currently Filter: Crashes Accidents Incidents News Reports [ ] search Article Occurrence sorted by On On On On On date Update --------------------------------------------------------------------- Fly Safe,: ...and don't f**k up! News The Aviation Herald needs your help The Aviation Herald Apps Android and iOS Accident: JAL A359 at Tokyo on Jan 2nd 2024, collided with Coast AVHAPP on Android and iOS Guard DH8C on runway and burst into flames Support The Aviation Herald By Simon Hradecky, created Tuesday, Jan 2nd 2024 10:07Z, last updated Euro Tuesday, Jan 2nd 2024 20:55Z Support The Aviation Herald A JAL Japan Airlines Airbus A350-900, registration JA13XJ performing US$ flight JL-516 from Sapporo to Tokyo Haneda (Japan) with 367 Support The Aviation Herald passengers and 12 crew, landed on Haneda's runway 34R at 17:47L (08:47Z) in night time conditions but collided with a Japanese Coast Interview: Guard Dash 8-300 registration JA722A (Coast Guard code MA722) on the The human factor named runway shortly after touchdown and burst into flames. The A350 came "Simon Hradecky" and the to a stop off the right hand edge of the runway about 1680 meters/ team of man and machine 5510 feet down the runway and was evacuated. All occupants were able to evacuate. The other aircraft carrying 6 people also burst into flames, 5 of the six occupants are confirmed dead. Both aircraft burned down. 14 occupants of the A359 received injuries, the captain of the Dash 8 received serious injuries. The airline reported their A350 was carrying 367 passengers (including 8 children) and 12 crew, all of them evacuated from the aircraft. In a second press release the airline reported there had been no anomaly with the aircraft prior to departure. The crew had received and read back landing clearance. After the collision and coming to a stand still three emergency slides were used to evacuate the occupants of the aircraft. The details of the accident are under investigation by the JTSB. Japan's Coast Guard reported their Dash 8-300 registration JA722A (Code MA722) was carrying 6 people, the captain was able to evacuate, the other 5 are currently missing. The aircraft was carrying supplies to their Niigata based where the New Year's Earthquake struck. Tokyo's Metropolitan Police reported 5 of the occupants of the Dash 8 are confirmed dead. Tokyo's fire department reported, the captain of the DH8C received serious injuries, 17 occupants of the A359 received injuries. Later the Fire Department corrected the number to 14 injuries amongst the occupants of the A359. Passengers of the A359 reported the landing appeared normal at first, after touchdown there was a thud and the outside lit up in orange. A first announcement was made "please calm down" followed by "do not take your luggage and do not stand up". There was no clear announcement to evacuate, however, when other passengers stood up they also stood up and thus escaped. Japan's Ministry of Transport stated Haneda Airport was closed, the flights cancelled, there is no prediction when the airport will open again. In a press conference the Ministry of Transport stated that it is under investigation whether JL-516 had been cleared to land. There was a Coast Guard aircraft on the runway causing a collision, the details of the collision are under investigation. In a graphics the Ministry showed the approximate positions of both aircraft (see below). In the afternoon of Jan 2nd 2023 (European Time) the French BEA reported they have dispatched 4 investigators and 5 technical advisors to Tokyo to join Japan's JTSB, who are investigating the accident. The team is expected to be on site by Jan 3rd 2024. A number of arriving flights are being diverted to Narita Airport where the flights are being accepted one by one. According to ATC recordings the A359 as well as a number of other aircraft departing runway 34R were handed off to Tower Frequency 118.725MHz, however, the Coast Guard DH8C was handed off to tower at 124.350MHz. JL-516, upon being handed off to tower by approach, was told by tower to "continue approach", about 90 seconds later tower cleared the aircraft to land. Haneda Airport resumed operations on their runways 16R/34L, 04/22 and 05/23 at about 21:30L (12:30Z) about 3:45 hours after the accident while runway 16L/34R remains closed. Related NOTAMs: J0019/24 NOTAMN Q) RJJJ/QMRLC/IV/NBO/A/000/999/3533N13947E005 A) RJTT B) 2401021538 C) 2401031500 EST E) RWY 16L/34R-CLSD DUE TO DISABLED ACFT E5877/23 NOTAMN Q) RJJJ/QMXLC/IV/M/A/000/999/3533N13947E005 A) RJTT B) 2401021530 C) 2401302130 D) 02 05 09 12 16 19 23 26 30 1530/2130 E) TWY C1 THRU C14-CLSD DUE TO MAINT E0023/24 NOTAMN Q) RJJJ/QMXLC/IV/M/A/000/999/3533N13947E005 A) RJTT B) 2401020930 C) 2401021500 EST E) TWY C1 THRU C14-CLSD DUE TO TRBL J0011/24 NOTAMR J0010/24 Q) RJJJ/QMRLC/IV/NBO/A/000/999/3533N13947E005 A) RJTT B) 2401021136 C) 2401021300 EST E) ALL RWY-CLSD DUE TO DISABLED ACFT E0025/24 NOTAMN Q) RJJJ/QMXLC/IV/M/A/000/999/3533N13947E005 A) RJTT B) 2401021144 C) 2401021300 EST E) TWY C(FM C1 TO C14)-CLSD DUE TO TRBL E0026/24 NOTAMR E0024/24 Q) RJJJ/QMXLC/IV/M/A/000/999/3533N13947E005 A) RJTT B) 2401021154 C) 2401031200 E) TWY G(BTN C AND H2),G(INT OF H2)-CLSD DUE TO RESCUE OPR E0024/24 NOTAMN Q) RJJJ/QMXLC/IV/M/A/000/999/3533N13947E005 A) RJTT B) 2401020953 C) 2401021200 E) TWY G(BTN C AND H2),G(INT OF H2)-CLSD DUE TO RESCUE OPR Metars: RJTT 021000Z 32003KT 9999 R34L/P2000N R22/P2000N R34R/P2000N R05/ P2000N FU BKN015 08/04 Q1016 NOSIG RMK 7SC015 A3002 1000E FU ON RWYC-MID= RJTT 020930Z 31007KT 9999 R34L/P2000N R22/P2000N R34R/0900VP2000U R05 /P2000N FU BKN015 08/04 Q1016 NOSIG= RJTT 020900Z 33008KT 9999 FEW020 07/04 Q1016 NOSIG= RJTT 020830Z VRB03KT 9999 FEW020 SCT090 08/04 Q1016 BECMG TL0900 30006KT= RJTT 020800Z 13003KT 090V150 9999 FEW020 BKN090 09/05 Q1016 BECMG TL0930 30006KT RMK 1CU020 6AC090 A3000= RJTT 020730Z 16007KT 130V190 9999 FEW020 BKN100 08/05 Q1016 NOSIG= RJTT 020700Z 12007KT 9999 FEW030 BKN100 09/04 Q1016 NOSIG= RJTT 020630Z 13010KT 9999 -RA FEW030 BKN070 09/04 Q1016 NOSIG= RJTT 020600Z 14005KT 120V180 9999 -RA FEW030 SCT060 BKN080 08/03 Q1017 NOSIG= RJTT 020530Z 12005KT 9999 -RA FEW025 SCT060 BKN080 08/02 Q1017 NOSIG= RJTT 020500Z 09003KT 050V120 9999 -RA FEW040 BKN060 08/02 Q1017 NOSIG = RJTT 020430Z VRB01KT 9999 -RA FEW030 BKN050 09/01 Q1018 NOSIG= RJTT 020400Z 01003KT 310V060 9999 -RA FEW030 BKN045 09/00 Q1018 NOSIG = CCTV Video of line up of Coast Guard (at 2:40 mins), landing of A359 (coming into sight at 3:20 mins) and collision at 3:47 mins (Video: Single Preference): https://www.youtube.com/watch?v=6NbVdIoJsHY The A350 skidding to a halt on the runway: The A350 skidding to a halt on the runway The aircraft after coming to a halt: The aircraft after coming to a halt The aircraft after coming to a halt Still out CCTV recording showing the A359 shortly after touchdown, just before and at the moment of collision: Still out CCTV recording showing the A359 shortly after touchdown Still out CCTV recording showing the A359 just before collision Still out CCTV recording showing the A359 just at collision Excerpt of Haneda Aerodrome Chart with positions of aircraft (Graphics: AVH/AIP Japan): Excerpt of Haneda Aerodrome Chart with positions of aircraft (Graphics: AVH/AIP Japan) --------------------------------------------------------------------- Reader Comments: (the comments posted below do not reflect the view of The Aviation Herald but represent the view of the various posters) --------------------------------------------------------------------- @peaceful By Observer on Tuesday, Jan 2nd 2024 22:40Z Unappropriate discussion here on religious matters, but it's worth reminding you that also "western" religion as Christian catholic one believes in re-incarnation. To the point that the Latin abbreviation RIP is meant for the individual to "rest in peace" waiting for "the day" it will happen. Not a keen practitioner here, but simply knowledgeable on the basic. Take care and let us know about your aviation knowledge since your religion one is poor as just you are poor of empathy. --------------------------------------------------------------------- Answer By Tomas on Tuesday, Jan 2nd 2024 22:22Z Rest in Peace Peacefully;) --------------------------------------------------------------------- Holding pos By Max Lombardi on Tuesday, Jan 2nd 2024 22:15Z Apparently, the dash8 was told to hold at C1" point, While it s evident it alligned with the rwy ready for takeoff, when the a350 was already too low to go around and avoid it. That will be intresting to hear the atc readbacks. --------------------------------------------------------------------- Electronics Bay (EB) By Engineering on Tuesday, Jan 2nd 2024 21:52Z The front most section under the flight deck and around the NLG of a A350 is mostly fairings (non-pressurised area). Look-up online A350 nose fairings/structure and you'll see what I mean. The main avionic racks are quite a bit further back (approximately under the floor in the DR1 area), so chances are that while they may have sustained some damage, certain components may have remained operational so long as they continued to receive power. --------------------------------------------------------------------- Munich 2005 - angle of taxiway By Brian Johnson on Tuesday, Jan 2nd 2024 21:45Z A similar accident was narrowly avoided at Munich in May 2004 when a landing KLM 737 swerved (at high speed) to avoid an ATR that had partially entered the runway via a taxiway (fast exit). The investigation found that the ATR crew entered the runway at an angle such that the landing aircraft was to their rear and right i.e. behind the right shoulder of the co-pilot. From what I could discern from the airfield plan above, this could also have been the case here, and may have been a factor in why the Dash crew did not see the approaching A350. --------------------------------------------------------------------- Crash Statistics / @ Hans R. By Kai Petzke on Tuesday, Jan 2nd 2024 21:41Z Flying is very, very safe today, but this is by far not the first serious accident / hull loss since AF447, even, if one considers only "legacy carriers". Here is a (likely incomplete) list of serious accidents and crashes of flights operated by large country owned carriers in the last ten years: Korean Air Flight 631 (Oct. 23, 2022) Emirates Flight 521 (Aug. 3, 2016) EgyptAir Flight 804 (May 19, 2016) Air Canada Flight 624 (Mar. 29, 2015) Germanwings (subsidiary of the German legacy carrier Lufthansa) Flight 9525 (Mar. 24, 2015) On the EgyptAir and Germanwings crashes, everybody died. The other accidents were survived by everyone. Of course, people's mileage may vary, as to which airlines they consider "legacy carriers". Emirates is rather young (founded 1985) and Germanwings is only a subsidiary. But Air Canada for sure counts as a legacy carrier. --------------------------------------------------------------------- @ Peaceful By JF on Tuesday, Jan 2nd 2024 21:27Z What a senseless post yours... we use or faith and our beliefs...that doesnt make automatically us being fools. Recently i lost a japanese friend of mine...musician and pilot as me...i expressed my occidental RIP and no one at their family got annoyed as you are showing to us all. Peace --------------------------------------------------------------------- @Peaceful By LeftSeat on Tuesday, Jan 2nd 2024 21:25Z With all due respect - you are over reacting. Yes, they are saying words from their culture and they are meaningful. You rather people just turn their back and walk away? --------------------------------------------------------------------- TWO blasts?! By Capt. Yossarian on Tuesday, Jan 2nd 2024 21:14Z Earlier today, there has been some video footage showing the crash, in combination with a running >>time stamp<< on the right hand side. That certain video also shows that the crash actually had TWO blasts: one of yellowish fire, which then grew larger and travelled with the plane all along, plus another one about 0.4 seconds earlier, which was more like a short red flash, about one tenth of a second long. Given a speed of let s say 200 km/h at least, 0.4 seconds would mean a distance of 22 meters ... --------------------------------------------------------------------- @Part Timer By BlueMax on Tuesday, Jan 2nd 2024 21:13Z ...The level of understanding of aircraft, flying and aviation is so poor in mainstream media... Not only of aircraft, flying and aviation. --------------------------------------------------------------------- Peaceful By Peaceful on Tuesday, Jan 2nd 2024 21:09Z Stop saying 'Rest in Peace', all you western folks. The East believe in reincarnation, so there is no 'resting in peace'. Get educated, come back and post educated comments, please. There is no 'RIP' philosophy. --------------------------------------------------------------------- Someone qualified make comments By Armchair Aviation Expert on Tuesday, Jan 2nd 2024 21:06Z Can we please please please have someone who is qualified in aviation to make educated comments about the incident and not a bunch of armchair aviation experts? I don't think it'll happen but it's worth a shot. If you don't have a degree in aviation or don't work in aviation, please refrain from posting on the internet where there is freedom of speech --------------------------------------------------------------------- movement By Jmli on Tuesday, Jan 2nd 2024 21:06Z I cannot see any movement or moving lights nor any flashing lights in the seconds before the collision took place so I wonder whether the DHC-8 was holding on the runway, badly visible to the A359 crew. In addition it looks to me like the collision took place at about the spot where the A359 was about to touch down, so maybe the pilots were not able to see the DHC8 due to nose-up landing configuration and the barely lit up DHC8 without any noticable flashing and position lights? --------------------------------------------------------------------- Composite Materials and Fire By Kai Petzke on Tuesday, Jan 2nd 2024 20:58Z Carbon fiber composite materials do burn and they can feed a fire. But like wood or coal, they need rather elevated temperatures to ignite and they burn rather slowly, much much slower than for example Jet A1 fuel. Aluminum usually doesn't burn or feed a fire. It ignites only, if dispersed as a fine powder and heated to very high temperatures. But Aluminum has a low melting point of just 660 degC and many Aluminum alloys are even lower, with 7075 Al alloy melting already at 477 degC. So both materials have the problem, that an outside fuel fire will eventually burn or melt through. As this cannot be prevented, the focus is on making the cabin durable enough to withstand a fuel fire long enough for everybody to safely evacuate. Kudos to the engineers at Airbus, that did do their tests and math correctly and thus enabled the crew to save 379 lives today! Kudos also to the crew, that ensured, that everybody was out! And condolences to the crew on the Dash. Such a tragedy already in the new year. --------------------------------------------------------------------- Harry Hyams By (anonymous) on Tuesday, Jan 2nd 2024 20:50Z "I was under the impression that all aircraft had to be evacuated in 90 seconds." The better way to think of it is that every aircraft has to be ABLE to be evacuated in 90 seconds with half of the available exits in use under test conditions. Real world conditions can be quite different. Including apparently people going to exits that couldn't be used because of the fire. --------------------------------------------------------------------- a350 By kjamesk, fl on Tuesday, Jan 2nd 2024 20:48Z fly boeing fly safekkk --------------------------------------------------------------------- Lights By Mupepe on Tuesday, Jan 2nd 2024 20:47Z Most Dash aircrafts are poorly lighted using their red beacons and difficult to spot. --------------------------------------------------------------------- Horrific. By Francine Fishpaw on Tuesday, Jan 2nd 2024 20:45Z Horrific. --------------------------------------------------------------------- Mainstream media coverage - laughable By Part Timer on Tuesday, Jan 2nd 2024 20:35Z Most importantly, I m very sorry for those who perished in this incident and their families. I looked in on the live Uk mainstream media coverage of this. The presenter who was interviewing an expert from Cranfield University was an absolutely joke. The highlight was this: And we can see the chutes deployed in these pictures, presumably that means the chutes were used for the evacuation rather than the doors? The level of understanding of aircraft, flying and aviation is so poor in mainstream media that it s negligent that this kind of incompetence is allowed on air at all. A child is not this ignorant. --------------------------------------------------------------------- @ Hans R By The Legacy on Tuesday, Jan 2nd 2024 20:22Z Perhaps, though if you want to look at it another way, it could have been very easy for the occupants of the A350 to be killed from the accident sequence. I remember one covered in the TV series Mayday where a large airliner landed on top of a cessna, and careened off the runway and into a storage tank. I forget which accident that was. But considering how close the apron is to the runway (relatively speaking), it was EXTREMELY lucky (and potentially pilot intervention to keep it straight) that everyone survived on the airliner. And - assuming the pilot of the Dash 8 sirvives their injuries - the pilot is beyond lucky to survive. Although tragic, I still think it was incredibly lucky that so many survived this. --------------------------------------------------------------------- EB By soliton on Tuesday, Jan 2nd 2024 20:09Z Does anyone know if the electronics bay handles the PA system? The damage to the front was pretty bad so maybe most of the computers got taken out by the crash and the pilots couldn't really do anything afterwards. Overall the plane held up quite well. It also burned pretty well afterwards so I'm curious if the composite actually ignited or if it just burned through. RIP Dash 8 crew --------------------------------------------------------------------- Burned entirely By Skydriver on Tuesday, Jan 2nd 2024 20:06Z @Gigi Remember the Emirates 777 at Dubai, ended up the same way When internal fuel is ablazzed the fire brigade will mostly try to protect the evacuation. --------------------------------------------------------------------- Shocking start of the New Year By Hans R. on Tuesday, Jan 2nd 2024 20:01Z It's really a shocking start of the New Year. My condolences to the Families and Friends of the Deceased. That everybody was able to evacuate from the A 359 is a kind of a Wonder when looking at the Picture's. It's the first Hull Loss of an A 350 and beside the Aeroflot-Superjet-Crash in 2019 the first Crash of an Aircraft from a Legacy Carrier since AF Flight 447. It's of course too early to say anything more precise but at least one of the two involved Aircrafts was clearly not where it should have been. There were a couple of Near Misses back in 2023, all avoided by Good Luck or great situational awareness of one participant. Now the Good Luck ran out. --------------------------------------------------------------------- Lucky A350 Pax + Crew By The Legacy on Tuesday, Jan 2nd 2024 19:28Z These kinds of collisions are incredibly dangerous for those on board either aircraft. Although the Dash 8 is much smaller, I'm shocked that no one passed away, whether from the collision or the fire. I look forward to the final report... my condolences to those who died. --------------------------------------------------------------------- @ Michael K By The Legacy on Tuesday, Jan 2nd 2024 19:26Z I can't speak for the firefighters, but between the sheer distance, and the fact that they have two separate scenes involved, the priority was probably put toward the much larger and less damaged aircraft that was on fire. Personally, I'm surprised anyone survived within the Dash 8 at all. --------------------------------------------------------------------- Collision By Tim on Tuesday, Jan 2nd 2024 19:07Z I m wondering if ATCO s at Tokyo Haneda received some sort of alarm from the ARIWS prior to impact or if this system is installed in the vicinity of the airport. Props to the aircrew and firefighters & condoleance to the people who died --------------------------------------------------------------------- By (anonymous) on Tuesday, Jan 2nd 2024 19:03Z Regarding the respons time for the dash8, it could be that it wasn't known instantly the 2 planes was involved? --------------------------------------------------------------------- Fire Response took so long! By Michael K on Tuesday, Jan 2nd 2024 18:53Z Sorry for the losses, may the deceased Rest in Peace. I am shocked that the fire department took around 6 minutes to respond on site the Dash-8. That is 5 minutes too long imho. I don t know when they were onsite at the A359 though. Also shocked that the A359 crew did not give a command to evacuate. --------------------------------------------------------------------- Composite Material of A350 By Hunter Buddy on Tuesday, Jan 2nd 2024 18:48Z The question of A350 wings and box are made of composite material which makes the lighter and also gives it more range. But it is fire resistant as per the internet article : Moreover, composites, as mentioned, are by their nature inherently fire resistant. The inert fibre-reinforcement displaces polymer resin during fire and thus removes fuel for the fire. When the outermost layers of a composite laminate lose their resin, they act as an insulating layer, slowing heat penetration. Since the tail section is on fire it seems that as per JAL policy the APU is started before landing especially at night landings. Perhaps the fire warning was not activated in the cockpit so the crew did not pull the fire switches. Fuel kept on being supplied to the APU which resulted in the smoke in the Aircon ducts. JTSB will let us know. --------------------------------------------------------------------- Handovers GND to TWR By Andreas on Tuesday, Jan 2nd 2024 18:46Z 00:14:42 into LiveATCs GND-recording (that would be 08:44:42Z if the recording started exactly 08:30Z), I hear three handovers from GND to TWR. ANA627 and SNJ97 (both on TWY C) are handed over to TWR 118.725, but JA722A is handed over to TWR 124.35. Why would there be two different controllers assigned for one active runway? I do not want to suggest that this played any role in the chain of events, but maybe someone can shed light on this? Condolences to the families of the Coastguard staff, they lost their lifes in service to help earthquake victims. --------------------------------------------------------------------- Only the most recent 30 comments are shown to reduce server load. Click here to show the remaining comments --------------------------------------------------------------------- Add your comment: (max 1024 characters) Your IP address 68.32.53.220 is being tracked. We reserve the right to remove any comment for any reason. Profanities, personal attacks (against any physical or legal person), discussions about site policies, false statements or similiar as well as copyrighted materials from third parties will not be tolerated, those messages will summarily be deleted. Links and mail addresses are not permitted and will not appear in the display, posts trying to circumvent the restriction of links/mail addresses will be removed. We ask for your valid e-mail address in the email field. This address is only used by us to establish contact with you in case of further questions, it will not be displayed anywhere or be used otherwise. Your [ ] Name: Your [ ] Email: Subject: [ ] Your comment: [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [Post Comment][Return to Home] --------------------------------------------------------------------- Get the news right onto your desktop when they Subscribe Login FAQ Contact Impressum happen --------------------------------------------------------------------- (c) 2008-2024 by The Aviation Herald, all rights reserved, reprint and republishing prohibited. We use cookies to ensure you get the best experience on our site, learn more. dataimagedataimage