Aeromexico Crash
Aeromexico flight reported to have crashed on takeoff from Durango. No details. |
Embraer 190 , there are already some images on social media !
|
|
Apparently flight AM2431, aircraft XA-GAL.
|
XA-GAL Aeroméxico Connect Embraer ERJ-190AR (ERJ-190-100 IGW). First flight date unknown, but built 2008. Delivered to AeroMexico on 27 June 2014. Left gate at 15:08 local.
|
|
Social media reports of ambulatory survivors and a video of 'the pilot' being taken to the hospital in a private vehicle:
|
First impression is an overrun. I hope everyone got out..
|
The governor of the state of Durango says there are no fatalities:
https://twitter.com/AispuroDurango/status/1024417175380127744 |
BBC report
Nobody killed according to the beeb: https://www.bbc.co.uk/news/world-latin-america-45027112
"The crash happened 10km (six miles) from the airport just after take-off." so doesn't sound like an overrun... |
Originally Posted by FIRESYSOK
(Post 10211409)
First impression is an overrun. I hope everyone got out..
|
Aeromexico say 97 passengers, 4 crew. |
BBC reporting problem occurred on runway and was too fast to abort. |
Originally Posted by FIRESYSOK
(Post 10211409)
First impression is an overrun. I hope everyone got out..
|
Originally Posted by RiSq
(Post 10211479)
BBC reporting problem occurred on runway and was too fast to abort. |
Well, either an over-run or a crash six miles from the airport: It can't be both.
Hope the reports of all surviving are true. |
|
interesting...the passenger states it was a high speed abort....the aircraft was at high speed when it went beyond the fence and kept going beyond the airport boundary.
very fortunate |
400 yards
The current Wall Street Journal story is posted here (but may be firewalled)
https://www.wsj.com/articles/airline...=hp_listc_pos1 It asserts the the aircraft came to rest within airport grounds about 400 meters from the end of the runway. That sounds like a high-speed abort to me if accurate. Regarding passenger and crew condition, the current New York Times article (also may be firewalled): https://www.nytimes.com/2018/07/31/w...av=bottom-well Asserts that 80 people are under hospital treatment, with 12 of the 18 at just one hospital listed in critical condition. |
That sounds like a high-speed abort to me if accurate. |
Originally Posted by malr
(Post 10211529)
Shouldn't a high-speed abort (before V1) leave enough runway to stop without the overrun?
|
oops
Originally Posted by malr
(Post 10211529)
Shouldn't a high-speed abort (before V1) leave enough runway to stop without the overrun?
|
Originally Posted by archae86
(Post 10211535)
My mistake, I guess. I'm not a pilot, and was speaking English, not realizing I had inadvertently employed a reserved term with a formal meaning. I just meant "terminated the takeoff while going pretty darn fast". As distinct from crashing minutes after takeoff, as some early reports had it.
|
Based on the photos from the BBC article, it looks to have come to a rest around 375m beyond the threshold, past the RESA but well within the airport fence.
Fingers crossed that the injured passengers and crew make a recovery |
Originally Posted by Sailvi767
(Post 10211550)
Based on no fatalities most likely a overrun. Agree .. but to get that far from an expected V1 decision point it would seem that he had to be going pretty damn fast as an overrun. Of course like any accident it doesn't add up until the facts start coming in. |
https://cimg7.ibsrv.net/gimg/www.gmf...a0382e6919.jpg
Photo by Kevin Alcantar Drones Durango There seem to be multiple reports that the plane took off into a heavy rainstorm. |
Avherald has posted a video showing that the poor bird "jettisoned" its engines to the left of the runway and before DER. So far I'd speculate it wasn't ordinary too-high-speed abort messup and that keeping the bird upright throughout the crash sequence required the heavy dose of good luck.
|
Aviation Herald report: Accident: Aeromexico Connect E190 at Durango on Jul 31st 2018, veered off and overran runway after rejected takeoff and burst into flames
MMDO 312150Z 12007KT 10SM BKN020CB BKN025 OVC200 22/14 A3023 RMK 8/903 BINOVC= MMDO 312103Z RTD 28007KT 7SM OVC015CB 17/14 A3024 RMK SLP118 57014 956 8/9// PISTA CERRADA POR ACFT ACCIDENTADA BINOVC= MMDO 312018Z 07003KT 7SM TSRA BKN020CB 20/13 A3023 RMK 8/900 TSRAB13= MMDO 311941Z 01005KT 10SM BKN025CB 28/10 A3023 RMK 8/300= MMDO 311844Z 12003KT 12SM BKN025TCU BKN200 26/11 A3026 RMK 8/201 ISOL CB= Airport elev. 6102 ft/1860m. Calculated DA (mine, from METAR above) 7934ft/2418m AH map shows both engines found off left side of runway, between RWY and TWY A, and between TWY A hold point and twy B. My observation (from misc airport photos) is that there appears to be a full-length drainage ditch between runway left side and the parallel taxiway A, in about the lateral location where the engines were found. Rest of aircraft travelled about 250 m/yds past the point the engines were found. Time between the aircraft comes to a stop, and fire ignition, about 3-4 minutes, thus the moderatel casualties. It appears to me the drainage area is a swale or valley (shallow but not flat - close order of 1.5 m/yds deep?), with the taxiways crossing it on berms to access the runways - just an impression from the look of the ground around the taxiways (google earth) and how far the ditch "tunnels" past the tawiways. https://www.google.com/maps/place/Ae...4d-104.5338168 My speculation - aircraft departs left side of runway under asymmetric thrust after engine failure, descends into swale, travels along concrete-lined ditch, loses one engine in rough ground, hits berm for TWY A hold position, lose second engine (and perhaps gear) to ground obstruction (berm), slides across TWY A hold point and along concrete ditch lining on belly, until stopping. Weight (97 seats out of 100 filled), density altitude and minimal wind may explain high true/ground speed required and achieved. Someone with EMB-190 references may be able to figure that out. Shades of Continental 1404 runway excursion and loss of gear and one engine in rought ground DEN Dec. 2008, and SWA fall into ditch off taxiway at Nashville Dec. 2015. EDIT - Airbubba added his excellent photo while I was posting. Obviously better info about final aircraft position. Confirms hold point for 21 could have been an obstruction if they got into the weeds - emphasize "could", not "did." That's a nasty ditch. I think I see an S-curved trace through the grass from the top of the image to the taxiway, but that could be "confirmation bias." |
The weather around the time of departure did not look good:
MMDO 312018Z 07003KT 7SM TSRA BKN020CB 20/13 A3023 RMK 8/900 TSRAB13 |
Originally Posted by RobertS975
(Post 10211534)
You are making a huge assumption about what transpired. With intact recorders, possible airport vicinity video and hopefully healthy pilots, there will be lots of data to dissect on this accident.
|
From the BBC News article:
The airport operator, Grupo Aeroportuario Centro Norte, said early data suggests bad weather was the cause, with the plane taking off during a heavy hailstorm before being forced to make an emergency landing. |
Originally Posted by pattern_is_full
(Post 10211590)
Time between the aircraft comes to a stop, and fire ignition, about 3-4 minutes, thus the moderate casualties.
Anyone know? |
A more comprehensive report in The Guardian: https://www.theguardian.com/world/20...-crash-durango
Eighty-five people were injured – some seriously – but José Rosas Aispuro, the governor of Durango state, said there were no fatalities among the 97 adults, two children and four crew members on board ... A spokesman for the Durango state health ministry said two of the victims were in critical condition. Aispuro later said at a press conference that information he had received suggested that “after the plane had taken off, suddenly it was hit by a gust of wind that made it go down briskly and touch the ground with its left wing, detaching its two engines.“The aircraft was projected off of the runway … and fell approximately 300 metres [away]. |
Originally Posted by PastTense
(Post 10211621)
My thought is it would take substantially longer than this to evacuate all the passengers with some injured.
But yes, real-world factors will change the actual performance. Injuries can occur in the evacuation itself, or even post-evacuation (flying blobs of burning fuel, etc.) That'll all come out eventually. |
From the photo, the marks on the ground go from the aircraft to the end of the runway, it doesn't appear to have become airborne, which is probably why the aircraft remained intact.
|
Originally Posted by Lookleft
(Post 10211643)
From the photo, the marks on the ground go from the aircraft to the end of the runway, it doesn't appear to have become airborne, which is probably why the aircraft remained intact.
|
Have only speed-read all the above, but sometimes it can be a nasty shock at VR to realise something got missed out on the check list....like flaps or reduced thrust settings. A bit early to run out of fuel...We'll just have to wait and see
|
Originally Posted by Lookleft
(Post 10211643)
From the photo, the marks on the ground go from the aircraft to the end of the runway, it doesn't appear to have become airborne
|
Big thunderstorm, marble sized hail with gusty winds. Sounds a lot like a setup for a classic wind shear or microburst. |
Originally Posted by Volume
(Post 10211683)
locked bins may...
We now have electric emergency exit locks on some models (no good Idea IMHO) to prevent passengers from opening them if not desired, it would be a piece of cake to have electric locks on the bins. They may actually even prevent them from opening during hard landings if designed accordingly. Thus I think that locked overhead bins would make the situation worse as passengers would stand around aimlessly fiddling with the catches and waiting for the bins to be unlocked. |
All times are GMT. The time now is 05:58. |
Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.