As far as I read from local media, the plane crashed right next to a house, 12 people were evacuated from the house. The house was barely touched by the debris. My condolences to all involved. I wish quick recovery for the injured ones.
@@most-average-athelete I hear 2700' pretty clear but still that's no factor for the crash. There are no obstacles that affect to establish the glideslope at 2500' or even 2300' as others have mentioned. You descend below the glidepath, yes, but that's ot likely the cause of the crash. 2300' is altitude check on 5 miles. They crashed 1 mile short.
Incredible that anybody survived at all given the size of the fireball. My thoughts go out to the deceased person's family, and I hope for a speedy recovery of the three injured participants. Exellent work, Victor! Thank you!
According to local news, crew cabin during the crash, got separated from the burning fuselage. Person who was not in the cockpit has relatively minor injuries, however cockpit crew was not as lucky, with 1 dead, 1 unconscious whole time and 1 who was initially conscious but ... Not at the moment.
probably 2 factors that helped, 1 they're a cargo flight. So whole crew in the front(4 ppl if the info is correct), nobody in the back. So the after part can take most of the impact, 2nd, they configured for landing( with gear out/flaps) and had a low approach speed, so the impact will be less. But yeah, fly blue sky.
I was checking in at Vilnius airport when this crashed and didn't hear anything, I was very surprised to only hear about it once I'd landed in Luton. Our flight was delayed but the pilot just said due to an incident with the fire brigade.😳 crazy times. R.I.P to the pilot.
Wow. This was a quick grab and upload. Thanks for this information, Victor. My sincerest condolences to the family of the deceased, and well wishes for swift recovery to those injured in this incident.
It was so lucky that there wasn't more deaths from people inside their homes, my thoughts are with the family of the deceased. Lets hope this isn't anything narfarious.
I'm sorry to hear that, and thanksfor the quick upload. My condolences to the victim's family. I hope the others make a full recovery, and the cause of the accident is found quickly.
@@jonasbaine3538last 10 seconds the hat to pitch down, soomething happened, dont think it was pilots fault. Another video was released where u can see that in the last moment the pitch full up trying to survive. terrifing. RIP for the spanish pilot and wishing a speed and good recover to the crew.
Should be noted that approach gave the wrong ATC frequency (Vilnius tower is 118.205, the given frequency was 118.5 and the read back was 118.05). That's possibly a distraction factor and that's most likely why after the transfer we didn't hear from postman again. That's also why both frequencies gave a landing clearance, in hopes that postman was on one of them
Nice point. After watching again I realize that Approach indeed says ONE ONE EIGHT TWO ZERO FIVE. Quite fast, difficult to hear. Then for Postman I clearly hear ONE ONE EIGHT ZERO FIVE. Definitely read back the wrong frequency. Shouldn't be much of a factor since frequencies are listed in charts. You call a couple times without reply, either you come back to previous frequency for confirmation or you switch to the correct frequency yourself.
@@VASAviation the issue with that is it might not be a factor at 10 miles or more, but you don't have much time at 4 miles, could be quite a distracting factor taking into account they were overspeeding (judging by the localiser overshoot which only happens when people don't follow speed restrictions) and also considering they were in full IFR weather up until 800-900 FT. You won't be looking at charts for the frequencies at this stage of flight
The aircraft seems stable in the video up until it suddenly plummets from the sky. Based on the lights remaining pretty much in the same position the whole time this looks like a loss of airspeed close to the ground and likely not caused by weather or anything like that. Very sad for all involved.
The landing lights seem too high in my opinion, like they either didn’t have flaps out and were too slow, or did have flaps out - but were also too slow. Sounds like an unstable approach and they were behind the plane (asking for ILS clearance repeatedly so close to the ground.)
Flown into Vilnius countless times. The approach is a straightforward one. The behavior of the plane looks like it dropped suddenly the last few hundred feet- be that wind sheer, control input error or mechanical, its a sad day for those involed.
Pure speculation but more likely autopilot/autothrottle related failure or misuse/misunderstanding by the pilots, could be similar to the AMS crash - ILS capture without autothrottle (for various reasons), attempting to capture the glide from above with incorrect modes etc. Source - pilot with over 10,000hrs on Boeings
@@g1344304 Like you said pure speculation but from the CCTV footage the aircraft appears to be on a fairly stable glide, looks right for a 3 degrees glide and the V/S increases rapidly a few feet from the ground. Could be something with the A/T like you said with the AMS crash but I don't think it was related to capturing the glide from above as it looks stable for a few seconds there.
Condolences to the crewmember's family and all on the ground who lost their homes. Awful. I wonder if the incorrect QNH readback is the root cause... Damn. Not a good start to the week. Thanks for all your hard work Vas.
Anyone else getting stall vibes from that rate of descent? I'm seeing the comments about missing the glideslope, but surely they would realise that degree of drop.
These events are luckily so rare within the EU that they somehow hit different (no pun intended). Hope those who are injured are making a speedy recovery.
Not to discourage speculation, as I do enjoy it but we don't have nearly enough information without the black box. Loose cargo, wind shear, mechanical fault, software fault, icing, radar fault, etc etc etc. First observation shows a large deviation followed by immediate attempted correction in the critical stage before landing. My speculation is we can't rule out most causes at this stage. Even the door falling off, it is a boeing. Even something like a bird strike through the cockpit could kill or incapacitate the cockpit crew, medical incident, and so much more. My point is, if you guys can rule out possible explanations or reason them less likely it'd be more impressive.
There were bombs detonating at DHL in Germany in the last time, this may have been a sabotage, given the proximity to the current war, it may have been an issue too. A German spokeperson for the secret services should give a press conference soon today...
Pure speculation but most likely autopilot/autothrottle related failure or misuse/misunderstanding by the pilots, could be similar to the AMS crash - ILS capture without proper autothrottle (for various reasons), attempting to capture the glide from above with incorrect modes etc. My personal opinion with over 10,000hrs on Boeings
Did they really read back 2700 feat? It's not clearly understandable. I hear twothousandtwelvehundred what makes no sense. Perhaps they understood 2200 and were way below the glidepath while flying manually.
At 1:32 the pilot was given 2700 but sounds like the read back was 2300 and the pilot asks tower to confirm. However, the tower’s reply was stepped on. Not sure if that 400 foot difference would cause a crash, but it seems there was definitely some confusion about the ILS.
EYVI tower frequency is 118.205. The approach gave them 118.05 and they readbacked it. That might explain why we didn't hear anything from them on the tower frequency and it might have been another distraction (the handoff was kind of late as well - only 4nm from touchdown).
The acft was a bit high on the approach, what happened on short final, the rate of descent did not seem harsh (on the video) how they crashed in front the rwy. Interesting what happened in the cockpit on the last 2 miles before the crash
Airplane was very slow, very low, quite safe and airport and emergency services were nearby. And probably everybody was sitting at the front so didnt get into the "mincer".
I can only say Praise God that noone on the earth was even injured (12 people were in the house and other residential buildings nearby) and that 3 other members of the the crew survived 😯🙏 My deep condolences for the family and friends of the deceased pilot 😢
Looks like he was aiming for the wrong aimpoint short of RWY. The descend rate looked nice or maybe a bit steep but not crazy from the video. Do we know if its any windsheer in the place?
@@davidmichael5573I think they stalled it based on behind behind the plane in audio and the angle of the landing lights. CFIT is hard to do when you can see the obstacles and you’re obviously going to be looking since you’re in landing phase.
They were on an ILS .. even if their QNH was wrong .. and ILS doesn’t suffer from “QNH blunder error “ so if followed correctly it would guide them all the way to the runway safely. Had they been on an Rnav ( non precision ) in that case yes .. QNH could have played a factor .. however .. it seems apparent they were visual With the runway .. so even if their QNH was incorrect .. they could have clearly corrected visually .. so overall I do t think QNH was a factor.
The approach attitude of the aircraft seemed to on a stable 3 or maybe 3.5 degree angle as it descended …Also,……. .It looks as if the aircraft is being completely controlled all the way to impact. It also appears that the weather / landing visibility would allow the pilots to see the runway / airport environment ……. I’m only guessing here, but unless there was some sort of freak two-engine failure on short final (or) an auto flight mode /. Panel malfunction, (or) sudden flight control failure… the pilots should have been in a position to perform a go around….. If the ILS was being flown,.. obviously they would have below glideslope indications at or below the DA that far from the runway…..AND if no runway lHIRLS insight… shouldn’t be going below 100’ …….a Go-around would be performed… 🤔🤔🤔🤔
At 2:16 She said "...contact Tower 118.205." Readback was "118.05, Postman 18Delta" No comms after that. It's at least second incorrect readback. At 1:38 He said "Postman 18Zero, eh, 18Delta". Could this somehow contribute to the accident? Was the pilot too tired?
I hear him say 'two thousand three hundred feet'. That startled me on the first listen, and that is all I hear when I repeat, with good headphones (and old ears!) 1:30 is the timestamp.
So sad to hear of this tragic event with the loss of life and I’m sure life changing injuries. Thoughts go out to all involved. Maybe I’m hearing things but I’m sure he read back 2500 ft. 1:30. Not knowing the area. Does anyone know if it’s a high wind shear area?
That’s sad, but a miracle that anyone survived. As far as speculation, I don’t know… sounds like they were behind the plane for the entire approach and likely confused, hence asking for ILS multiple times. I don’t think the plane “was fine, then dropped out of the sky all of a sudden like wind shear” as some are saying - if you look at the angle of the landing lights, it seems like a VERY high AoA to me - like they either weren’t configured correctly but continued to slow, or perhaps were configured but just didn’t monitor their speed.
the video shows a dive near the end so loose cargo or stall maybe? Even its a stall for it to nosedive seems more like runaway trim or some flight control related issue. You guys think stall?
Hm so no longer fire in the cargo bay as expected by many (maybe you heard about a package burning in a parcel hub some weeks ago, suspected to be a sabotage activity also aiming at air transport between Germany and the Baltics)
Hmmm, all seemed fairly well until the part the CCTV shows...sudden power loss due to bird strike or fuel starvation 🤔 RIP to the deceased and best wishes to the survivors, I'm amazed looking at that sink rate.
Clearly something wrong happened with intercepting that localizer. V/S at -1200 ft when in the glide, no readback from the pilots, they should have done a missed approach if it was even possible
He was cleared down to 2700 feet, but it sounded to me like he read back 2300. Not saying that’s why he crashed, but it’s another hole in the Swiss cheese. That and the wrong tower frequency.
In the rough area of the crash just ahead on the flight path are some long buildings basically on the runway alignment. Wonder if the pilot spotted those and thought runway. Too soon would account for the sudden attitude change and increased descent rate.
Condolences to all those involved. Although I may be mistaken but it sounds like on the readback for the altitude to establish on the localizer the pilot said either 2300 or 2500 feet, and not the 2700 feet the subtitle says.
Don't want to get ahead of the investigation but cargo pilots are sometimes the ones rejected by the airlines. Like in the Prime air crash on approach in Houston TX some time ago....
Holy.. I don't know if it caused the accident or not but.. - wrong QNH readback - wrong ILS altitude readback - wrong tower frequency readback none of them were corrected by the controller?..
@@VASAviationMaybe it's the language barrier, but I hear a read back of 2,300 ft. Regardless, a 500ft below intercept alone wouldn't have been a causal factor.
@@VASAviation 0:39 0:40 QNH 1020 and readback was 1019 I am aware, 1 hP of difference does not make a huge change, and I am also aware that it can change by air conditions, still unless there is part cut at 0:39 the readback was not correct.
5:30 am the controllers were probably at the end of their night shift and the pilots had to start flying in the middle of the night so everyone's tired
He was supposedly on the glide anyway so it doesn't matter. A crash on final almost happened in CDG because of a confusion between 1001 and 1011 but 1 hPa isn't going to cause this anyway. Besides they were already through the clouds
What wounders me ATC said 2700 Pilot Radback 2500 And for some reason the plane still desend lower the 27 or 25 maybe the blackbox can say something about that
I hope we will learn what happened soon. It must have been something really bad. I really hope it was not human error. The airplane seems to be kind of plummeting abnormally. I dont think it is CFIT
The approach controller gave the correct frequency, it was just clipped out. (she obviously knows the correct frequency)118.205. He read it back wrong. But thats no excuse, its clearly written in the chart. The pilot sounded a little confused from the beginning querying 'expecting ILS19 not confirming ILS19?' 'Expecting ILS...is standard phraseolgy.
@@VASAviation 2500 (i missed it at first too). also there is a NOTAM for the glide slope now: A5305/24 NOTAMN Q) EYVL/QICCT/I /NBO/A /000/999/5438N02517E005 A) EYVI B) 2411251100 C) 2411251600 E) ILS (LOC, GP) AND ILS/DME IBK RWY19 OPR ON TEST. DO NOT USE, FALSE INDICATIONS POSS
Yes unfortunate. Just a few comments id like to here in the comment section. Early morning, fatigue? Cargo crews have generally, yes generally speaking demanding schedules. Pilot doing the radio sounds in my opinion somewhat unsure of himself. (once again only a comment). Flew through the localizer, not a major problem but worthy of mention as the visibilty wasnt great and speaking from expierience any deviations during the approach can get out of hand very fast. Were they late to arm approach? or was it a messy intercept?
This is purely my thoughts and I'm no expert but I'm wondering what the following aircraft had with Information Victor when the DHL had Information Uniform....what changed? Overshooting the ILS then turning back to HDG 190 whilst trying to maintain the glideslope would have increased their workload in the final few minutes. Doing anything that is mentally taxing at this time in the morning goes against our human instinct as the body is in sleep mode ( regardless if your used to it or not ). Surely if cargo had shifted mid flight then their trim balance would have been upset and they would have noticed the aircraft difficult to maintain trim. Tragic set of circumstances and loss of life to everyone involved. It just looked like they were 200ft too low, the data on flight radar doesn't appear to show any great fluctuations in speed, so whatever it was they didn't seem to know about it until the last few minutes. I'm wondering if icing could have been to blame on the descent through the clouds.
I guess UTN7022 suppose to see accident because it was a huge fire blast. Interesting that UTN7022 cabin thought that moment. Casualties 1 dead and the rest 2 injured. One person with heavy injuries. The reason why they was able to survive, because cockpit separated from fuselage and didn't burn.
Guys 1:30 pilot says 2300 ft...???? Airport operator said 2700 ft. I listened repeating on high volume 10 times....2300 ft... Si it means pilot lowed plane wrongly...
Records show light snow Friday afternoon for Vilnius, followed by temperatures around or below zero. I’m not familiar with the area, so I don’t know how far the airport is from the city.
@@tadass.2675 visible snow in footage, and NOTAM on the ILS now. 1C and going down (not 2C) METAR as follows: EYVI 250420Z 18016KT 9999 OVC008 01/M00 Q1020 NOSIG= EYVI 250350Z 18015KT 9999 OVC008 01/M00 Q1020 TEMPO OVC005= EYVI 250320Z 18017KT 9999 OVC007 01/M01 Q1020 TEMPO OVC005=
He said 2500 feet on decend via FAF. The approach plate says 2700 and the VNAV on flightaware/radar is 200 feet below glideslope. There are numerous hills on the chart marked as do not decent below 1000 feet. Last ADS-B is 750 feet. He did probably react in reverse while seeing the magenta above the glidepath from ILS, instead of pull he did a push.
M8 he clearly reads back correctly .. 2700 ft is clearly audible .. terrain is not a factor .. idk what plates you are using .. but the obstacles are way left of the runway ..
@@stefanocozzi8188 I am using the ILS 19 Z EYVI AD 2.24-22. See AIP LITHUANIA. The obstacles indicate that there is terrain on the approach path. If you check out available videos on the internet the pilots realize that they are too low and pull up but it is too late.... It might have also been false glide slope signal now that I am thinking.....
@@MoogieSRO No, it's not because the aircraft didn't crash into a mountain or a traffic for being 200 feet below the assigned altitude. Even if a mountain was there, 200 feet wouldn't be a factor since obstacle clearance altitudes exist and we must maintain a separation way greater than just 200'. The point of impact is nothing related to being 200' lower (which they were not according to ADSB data)
So many arm chair flight simmers thinking they know exactly what happened. A person has died, stop speculating with very limited knowledge and wait for the accident report.
Exactly! Like this is some contest to see who can guess the correct cause first. Happens with any crash, everyone speculating. Let the facts come out at least.
This comment will be continuously updated as more information releases.
Please leave your condolences here.
As far as I read from local media, the plane crashed right next to a house, 12 people were evacuated from the house. The house was barely touched by the debris.
My condolences to all involved. I wish quick recovery for the injured ones.
13:30 did the pilot replied saying 2500 ft instead of 2700 that was commanded by approach? ?
@@Mr.Laidukas I hear him say 2700'.
@@VASAviation I've listened it 200 times at least only after your comment :) I think he says 2500
@@most-average-athelete I hear 2700' pretty clear but still that's no factor for the crash. There are no obstacles that affect to establish the glideslope at 2500' or even 2300' as others have mentioned. You descend below the glidepath, yes, but that's ot likely the cause of the crash. 2300' is altitude check on 5 miles. They crashed 1 mile short.
Incredible that anybody survived at all given the size of the fireball. My thoughts go out to the deceased person's family, and I hope for a speedy recovery of the three injured participants.
Exellent work, Victor! Thank you!
According to local news, crew cabin during the crash, got separated from the burning fuselage. Person who was not in the cockpit has relatively minor injuries, however cockpit crew was not as lucky, with 1 dead, 1 unconscious whole time and 1 who was initially conscious but ... Not at the moment.
What a tragedy...😭
That's a really fast upload. Thanks for all your effort!
that is insane that anyone survived a crash like that
Cute sergal
the cockpit was separated from the burning part of the aircraft
probably 2 factors that helped, 1 they're a cargo flight. So whole crew in the front(4 ppl if the info is correct), nobody in the back. So the after part can take most of the impact,
2nd, they configured for landing( with gear out/flaps) and had a low approach speed, so the impact will be less.
But yeah, fly blue sky.
I was checking in at Vilnius airport when this crashed and didn't hear anything, I was very surprised to only hear about it once I'd landed in Luton. Our flight was delayed but the pilot just said due to an incident with the fire brigade.😳 crazy times. R.I.P to the pilot.
Why should he put into unnecessary stress all the passengers in his airplane? You never know how people can react including unmanaged panic attacks.
@@Ig86 I'm not suggesting he told us🙄doh ., I'm just surprised that at the airport it was all very quiet and business as normal.
Rest in peace, I hope for a speedy recovery for all those injured
Wow. This was a quick grab and upload. Thanks for this information, Victor. My sincerest condolences to the family of the deceased, and well wishes for swift recovery to those injured in this incident.
It's a horrible day for aviation... my condolences to everyone's families affected by this.
R.I.P
What else happened?
Sheeshhh how anyone inside that plane survived is beyond crazy
the cockpit was separated from the burning part of the aircraft
@@LuKas_146 another 2 crew members were behind pilots ? Front part of the plane.. ?
It was so lucky that there wasn't more deaths from people inside their homes, my thoughts are with the family of the deceased.
Lets hope this isn't anything narfarious.
I think anything nefarious is very unlikely. We will all be aware of the DHL fire, but there is nothing here to suggest an explosion or fire.
Rest in peace pilot 💔
I'm sorry to hear that, and thanksfor the quick upload. My condolences to the victim's family. I hope the others make a full recovery, and the cause of the accident is found quickly.
Got goosebumps hearing the twr controller after the crash :(
Thank you Victor, for the speedy upload. Much appreciated.
Condolences to all involved
The FACT i almost was a victim of this crash is crazy. I saw it on a BUS
wings level entire descent?
@@jonasbaine3538last 10 seconds the hat to pitch down, soomething happened, dont think it was pilots fault. Another video was released where u can see that in the last moment the pitch full up trying to survive. terrifing. RIP for the spanish pilot and wishing a speed and good recover to the crew.
@@mariohurtado260 how you know it was a spanish pilot? here in Germany they only say "it was a crew member" on the news...
@@btudrus Confirmed as Spanish a few hours ago.
Should be noted that approach gave the wrong ATC frequency (Vilnius tower is 118.205, the given frequency was 118.5 and the read back was 118.05). That's possibly a distraction factor and that's most likely why after the transfer we didn't hear from postman again. That's also why both frequencies gave a landing clearance, in hopes that postman was on one of them
Nice point. After watching again I realize that Approach indeed says ONE ONE EIGHT TWO ZERO FIVE. Quite fast, difficult to hear. Then for Postman I clearly hear ONE ONE EIGHT ZERO FIVE. Definitely read back the wrong frequency. Shouldn't be much of a factor since frequencies are listed in charts. You call a couple times without reply, either you come back to previous frequency for confirmation or you switch to the correct frequency yourself.
Should also be noted that at 1:31 18D doesn't read back the correct altitude.
@@VASAviation the issue with that is it might not be a factor at 10 miles or more, but you don't have much time at 4 miles, could be quite a distracting factor taking into account they were overspeeding (judging by the localiser overshoot which only happens when people don't follow speed restrictions) and also considering they were in full IFR weather up until 800-900 FT. You won't be looking at charts for the frequencies at this stage of flight
@@samiraperi467 he, he did read it back correctly.
@@VASAviationour lithuanian atc rules demand that you say "decimal" when mentioning comma. She didnt and that added to the mistake list.
I heard of this crash jusd 5 minutes ago, yet Victor's upload is 2 hours old. Nice work.
RIP to rhe FO.
The aircraft seems stable in the video up until it suddenly plummets from the sky. Based on the lights remaining pretty much in the same position the whole time this looks like a loss of airspeed close to the ground and likely not caused by weather or anything like that. Very sad for all involved.
Same thoughts...
At 3:07 the angle of the landing lights suddenly tilt down. With this the sinkrate increased as well as well.
The landing lights seem too high in my opinion, like they either didn’t have flaps out and were too slow, or did have flaps out - but were also too slow. Sounds like an unstable approach and they were behind the plane (asking for ILS clearance repeatedly so close to the ground.)
Flown into Vilnius countless times. The approach is a straightforward one. The behavior of the plane looks like it dropped suddenly the last few hundred feet- be that wind sheer, control input error or mechanical, its a sad day for those involed.
Pure speculation but more likely autopilot/autothrottle related failure or misuse/misunderstanding by the pilots, could be similar to the AMS crash - ILS capture without autothrottle (for various reasons), attempting to capture the glide from above with incorrect modes etc.
Source - pilot with over 10,000hrs on Boeings
@@g1344304 something like that seems plausible yes, it looks like the plane goes in a lineair way all the way down to the crash site.
Seems like sudden loss of power maybe?
@@g1344304 Like you said pure speculation but from the CCTV footage the aircraft appears to be on a fairly stable glide, looks right for a 3 degrees glide and the V/S increases rapidly a few feet from the ground. Could be something with the A/T like you said with the AMS crash but I don't think it was related to capturing the glide from above as it looks stable for a few seconds there.
looks like a CG shift to me. Maybe a sudden cargo move
As always, you're the best source of information on an incident or accident.
Thanks for your invaluable work!
Wow, RIP to the member who perished, and well-wishes for a full and speedy recovery to the ones who survived.
atmintis amžina. May that poor pilot's soul rests in peace.
Condolences to the crewmember's family and all on the ground who lost their homes. Awful. I wonder if the incorrect QNH readback is the root cause... Damn. Not a good start to the week. Thanks for all your hard work Vas.
An episode of Mayday- Air Crash Investigation is mandatory
Anyone else getting stall vibes from that rate of descent? I'm seeing the comments about missing the glideslope, but surely they would realise that degree of drop.
ADS-B suggests 149 knots so not getting stall vibes here, but if the glide slope antenna was bent maybe (i think there was a storm?)
Three people survived the disaster, let's hope they will still be alive.
Condolences to the victim’s family.
💜💜💜
Fastest upload 😮 RIP for those who lost their lives 😢
These events are luckily so rare within the EU that they somehow hit different (no pun intended). Hope those who are injured are making a speedy recovery.
Terrible tragedy. Rest in peace.
So sad to hear about it.
I can't imagine WZZ69BU's shock when he heard that it was a Boeing 737 that crashed
Not to discourage speculation, as I do enjoy it but we don't have nearly enough information without the black box. Loose cargo, wind shear, mechanical fault, software fault, icing, radar fault, etc etc etc. First observation shows a large deviation followed by immediate attempted correction in the critical stage before landing. My speculation is we can't rule out most causes at this stage. Even the door falling off, it is a boeing.
Even something like a bird strike through the cockpit could kill or incapacitate the cockpit crew, medical incident, and so much more.
My point is, if you guys can rule out possible explanations or reason them less likely it'd be more impressive.
There were bombs detonating at DHL in Germany in the last time, this may have been a sabotage, given the proximity to the current war, it may have been an issue too.
A German spokeperson for the secret services should give a press conference soon today...
Pure speculation but most likely autopilot/autothrottle related failure or misuse/misunderstanding by the pilots, could be similar to the AMS crash - ILS capture without proper autothrottle (for various reasons), attempting to capture the glide from above with incorrect modes etc.
My personal opinion with over 10,000hrs on Boeings
ua-cam.com/video/3A4ZuT-aFLs/v-deo.html
ua-cam.com/video/5MHfeqvaBP0/v-deo.html
apparently few cctv footage from nearby
Am I seeing it wrong in the first video, or one of the planes' wings (right) goes down and touches the ground? So the plane flipped on the side?
first clip looks like bank angle and wingstrike, while second looks like massive pitch up.
Stall as they tried to recover too late?
Did they really read back 2700 feat? It's not clearly understandable. I hear twothousandtwelvehundred what makes no sense. Perhaps they understood 2200 and were way below the glidepath while flying manually.
two thousand svn hundred feet. Too fast. But definitely 2700'.
1.31, he readback 2500 feet.
@@petereef4001 I hear 2700' pretty clear.
He's flying an ILS so doesn't really matter if he got the altitude wrong by a couple hundred feet. He can see the Glideslope/altitude he should be at.
They are below the cloud cover. PAPI should be plainly in sight. Also, they 100% have a radioaltimeter.
They also seemed to have flown through the ILS localizer and had to turn back to capture it from the other side.
Looks like they made a large heading change, of course this would be inevitable for an intercept of much more than 30 degrees or so.
At 1:32 the pilot was given 2700 but sounds like the read back was 2300 and the pilot asks tower to confirm. However, the tower’s reply was stepped on. Not sure if that 400 foot difference would cause a crash, but it seems there was definitely some confusion about the ILS.
EYVI tower frequency is 118.205. The approach gave them 118.05 and they readbacked it. That might explain why we didn't hear anything from them on the tower frequency and it might have been another distraction (the handoff was kind of late as well - only 4nm from touchdown).
The acft was a bit high on the approach, what happened on short final, the rate of descent did not seem harsh (on the video) how they crashed in front the rwy. Interesting what happened in the cockpit on the last 2 miles before the crash
How did 3 out of 4 people on that plane survive that?!
Airplane was very slow, very low, quite safe and airport and emergency services were nearby. And probably everybody was sitting at the front so didnt get into the "mincer".
@@tadass.2675Do we know if the three evacuated, or did they have to be extracted?
@@tadass.2675 Well 150kts is not slow :D
@@DanielsPolitics1 At least some of them had to be extracted according to local news.
@ Oh, that’s not good. Do we know how quickly the airport fire service got to the scene?
I can only say Praise God that noone on the earth was even injured (12 people were in the house and other residential buildings nearby) and that 3 other members of the the crew survived 😯🙏
My deep condolences for the family and friends of the deceased pilot 😢
Looks like he was aiming for the wrong aimpoint short of RWY. The descend rate looked nice or maybe a bit steep but not crazy from the video. Do we know if its any windsheer in the place?
That looks more like controlled flight into terrain to me.
That’s what I’m thinking based on radar return and video. It looked stabilized all the way in.
@@davidmichael5573I think they stalled it based on behind behind the plane in audio and the angle of the landing lights. CFIT is hard to do when you can see the obstacles and you’re obviously going to be looking since you’re in landing phase.
I will be checking Juan Browne's UA-cam Channel on his take on this crash.
TWr frequency was 118.205*
They read back 118.050
That’s why we don’t have any communication from the cockpit
They read back the wrong QNH value (1019 instead of 1020). That's not good. Well, I guess they would be too high, but still not good.
That's no factor. They read it back correctly just before the approach when Approach repeats the QNH 1020.
You know QNH changes due to weather conditions.... So early QNH was 1019 and later was updated...
1 millibar error makes just 26 feet difference, not much
They were on an ILS .. even if their QNH was wrong .. and ILS doesn’t suffer from “QNH blunder error “ so if followed correctly it would guide them all the way to the runway safely. Had they been on an Rnav ( non precision ) in that case yes .. QNH could have played a factor .. however .. it seems apparent they were visual
With the runway .. so even if their QNH was incorrect .. they could have clearly corrected visually .. so overall I do t think QNH was a factor.
My guess is that a sudden move of cargo caused a CG shift. Do we have AOA data?
The approach attitude of the aircraft seemed to on a stable 3 or maybe 3.5 degree angle as it descended …Also,…….
.It looks as if the aircraft is being completely controlled all the way to impact.
It also appears that the weather / landing visibility would allow the pilots to see the runway / airport environment ……. I’m only guessing here, but unless there was some sort of freak two-engine failure on short final (or) an auto flight mode /. Panel malfunction, (or) sudden flight control failure… the pilots should have been in a position to perform a go around…..
If the ILS was being flown,.. obviously they would have below glideslope indications at or below the DA that far from the runway…..AND if no runway lHIRLS insight… shouldn’t be going below 100’ …….a Go-around would be performed… 🤔🤔🤔🤔
At 2:16 She said "...contact Tower 118.205."
Readback was "118.05, Postman 18Delta"
No comms after that.
It's at least second incorrect readback. At 1:38 He said "Postman 18Zero, eh, 18Delta".
Could this somehow contribute to the accident? Was the pilot too tired?
Did i mishear it or did the Pilot read back 2300ft? It sounds like it
He said 2700'.
I heard the same 2300. They did not say 2700 vas.
I hear him say 'two thousand three hundred feet'. That startled me on the first listen, and that is all I hear when I repeat, with good headphones (and old ears!) 1:30 is the timestamp.
@@jinitom I hear 2700'.
Sorry, You are wrong. He said 2500 ft. If you reduce the speed to 0,5 times you can hear it loud and clear.
So sad to hear of this tragic event with the loss of life and I’m sure life changing injuries. Thoughts go out to all involved.
Maybe I’m hearing things but I’m sure he read back 2500 ft. 1:30.
Not knowing the area. Does anyone know if it’s a high wind shear area?
That’s sad, but a miracle that anyone survived. As far as speculation, I don’t know… sounds like they were behind the plane for the entire approach and likely confused, hence asking for ILS multiple times. I don’t think the plane “was fine, then dropped out of the sky all of a sudden like wind shear” as some are saying - if you look at the angle of the landing lights, it seems like a VERY high AoA to me - like they either weren’t configured correctly but continued to slow, or perhaps were configured but just didn’t monitor their speed.
the video shows a dive near the end so loose cargo or stall maybe? Even its a stall for it to nosedive seems more like runaway trim or some flight control related issue. You guys think stall?
Hm so no longer fire in the cargo bay as expected by many (maybe you heard about a package burning in a parcel hub some weeks ago, suspected to be a sabotage activity also aiming at air transport between Germany and the Baltics)
Hmmm, all seemed fairly well until the part the CCTV shows...sudden power loss due to bird strike or fuel starvation 🤔 RIP to the deceased and best wishes to the survivors, I'm amazed looking at that sink rate.
Clearly something wrong happened with intercepting that localizer. V/S at -1200 ft when in the glide, no readback from the pilots, they should have done a missed approach if it was even possible
Tired cargo pilots trying to finish the night?
I didn't even see this in the news feed
He was cleared down to 2700 feet, but it sounded to me like he read back 2300. Not saying that’s why he crashed, but it’s another hole in the Swiss cheese. That and the wrong tower frequency.
I hear him say 2700'.
In the rough area of the crash just ahead on the flight path are some long buildings basically on the runway alignment. Wonder if the pilot spotted those and thought runway. Too soon would account for the sudden attitude change and increased descent rate.
And what's about SSJ100 AZO5051 at LTAI any recordings???
Vau, you can fill tower controller(s) voice, when they(him ?) realized that bad shit happened :|
Were they too low when they intercepted the glide slope?
100% pilot said 2300, on 0.25 playback clear as day it's not 2700
Quick recovery to persons on board. Glad that there were no ground casualties.
it seems that the horizon level is shifted?
Condolences to all those involved. Although I may be mistaken but it sounds like on the readback for the altitude to establish on the localizer the pilot said either 2300 or 2500 feet, and not the 2700 feet the subtitle says.
He said 2700 feet pretty clear. Spanish accent and I'm Spanish.
Yes, sounds like 2500 to me.
@@saintchuck9857 I heard also 2500
I also hear two thousand FIVE hundred feet
If you survived this, would you fly again. Condolences to the family of the pilot.
There was a question asked to confirm ILS-Z after MIZOP -- but ATC just gave it to them? Overshot the localiser too :-/
Last few days have been nothing but problems with Boeing planes not able to slow down and it wouldn't surprise me if this is what happened here
Don't want to get ahead of the investigation but cargo pilots are sometimes the ones rejected by the airlines. Like in the Prime air crash on approach in Houston TX some time ago....
Anyone know the details of the crash? Why it happened?
1:30 it sounds the pilot said 2500 feet instead of 2700 feet
I don't think so.
@@VASAviation I don't hear the 2700 at all
@@novelhawk i agree it doesnt even come close to seven
❤
Holy.. I don't know if it caused the accident or not but..
- wrong QNH readback
- wrong ILS altitude readback
- wrong tower frequency readback
none of them were corrected by the controller?..
He read back the CORRECT QNH, he read back the CORRECT altitude.
@@VASAviation I'd bet my right foot that he's reading back 2500 feet, no doubt whatsoever. He does not say 2700.
@@VASAviationMaybe it's the language barrier, but I hear a read back of 2,300 ft. Regardless, a 500ft below intercept alone wouldn't have been a causal factor.
@@VASAviation 0:39 0:40 QNH 1020 and readback was 1019
I am aware, 1 hP of difference does not make a huge change, and I am also aware that it can change by air conditions, still unless there is part cut at 0:39 the readback was not correct.
@@jm-holm I hear him say 2700'.
All involved sound quite tired...fatigue???
Can already hear certain Swedish guy explain concept of Circadian Low once again.
Of course they're tired at 5:30am
5:30 am the controllers were probably at the end of their night shift and the pilots had to start flying in the middle of the night so everyone's tired
Wrong readback at first Tower :QNH 1020,Pilot QNH 1019..They cleared that up later but who knows..
He was supposedly on the glide anyway so it doesn't matter. A crash on final almost happened in CDG because of a confusion between 1001 and 1011 but 1 hPa isn't going to cause this anyway. Besides they were already through the clouds
@sanantonio855 I see, hopefully investigation finds real cause of this incident.
When did this happen? Just recently??
Today
What wounders me
ATC said 2700
Pilot Radback 2500
And for some reason the plane still desend lower the 27 or 25 maybe the blackbox can say something about that
Same day upload, or was that a typo?
It happened this morning
It was today, yes.
I hope we will learn what happened soon. It must have been something really bad. I really hope it was not human error. The airplane seems to be kind of plummeting abnormally. I dont think it is CFIT
Definetely looks like a stall, maybe due to icing or pilot error.
13:30 did the pilot replied saying 2500 ft instead of 2700 that was commanded by approach?
I hear 2700' pretty clear.
Yes. 2500ft pretty clear
@@petereef4001 and is that a factor?
Turkish 1951 vibes. Now let's see how B will manage the allegedly radioaltimeter glicht that they never bother to acknowledge and fix.
The approach controller gave the correct frequency, it was just clipped out. (she obviously knows the correct frequency)118.205. He read it back wrong. But thats no excuse, its clearly written in the chart. The pilot sounded a little confused from the beginning querying 'expecting ILS19 not confirming ILS19?' 'Expecting ILS...is standard phraseolgy.
"Expect" is "expect" = wait for it. Plan for it. He just wanted confirmation of clearance.
This makes no sense at all. I have no idea why this happened, it appeared that the airplane was in control in VFR conditions.
1:31 The readback is *2300 feet*, not 2700 as captioned.
Readback is 2700 feet. He said it too fast but it's definitely 2700 feet.
It is super hard to understand what he said there. Does not sound like a 7, but unclear.
1:37 the subtitle says 2700 feet but the audio has pilot reading back 2500
No, I hear pilot saying 2700'.
I hear 2500 feet too.
@@VASAviation 2500 (i missed it at first too). also there is a NOTAM for the glide slope now:
A5305/24 NOTAMN
Q) EYVL/QICCT/I /NBO/A /000/999/5438N02517E005
A) EYVI B) 2411251100 C) 2411251600
E) ILS (LOC, GP) AND ILS/DME IBK RWY19 OPR ON TEST. DO NOT USE,
FALSE INDICATIONS POSS
Yes unfortunate. Just a few comments id like to here in the comment section. Early morning, fatigue? Cargo crews have generally, yes generally speaking demanding schedules. Pilot doing the radio sounds in my opinion somewhat unsure of himself. (once again only a comment). Flew through the localizer, not a major problem but worthy of mention as the visibilty wasnt great and speaking from expierience any deviations during the approach can get out of hand very fast. Were they late to arm approach? or was it a messy intercept?
Looks like UTN7022 wanted to look what happen on the crash site... 🤪
This is purely my thoughts and I'm no expert but I'm wondering what the following aircraft had with Information Victor when the DHL had Information Uniform....what changed? Overshooting the ILS then turning back to HDG 190 whilst trying to maintain the glideslope would have increased their workload in the final few minutes. Doing anything that is mentally taxing at this time in the morning goes against our human instinct as the body is in sleep mode ( regardless if your used to it or not ). Surely if cargo had shifted mid flight then their trim balance would have been upset and they would have noticed the aircraft difficult to maintain trim. Tragic set of circumstances and loss of life to everyone involved. It just looked like they were 200ft too low, the data on flight radar doesn't appear to show any great fluctuations in speed, so whatever it was they didn't seem to know about it until the last few minutes. I'm wondering if icing could have been to blame on the descent through the clouds.
Yeah, Also am not a fan of this capture
How can there be survivors with this fireball?
It's a cargo plane, so everyone is in front, the fireball is obviously from fuel in the back.
I guess UTN7022 suppose to see accident because it was a huge fire blast. Interesting that UTN7022 cabin thought that moment. Casualties 1 dead and the rest 2 injured. One person with heavy injuries. The reason why they was able to survive, because cockpit separated from fuselage and didn't burn.
Yes, cockpit separated.
There is another video where you can see aircraft probably stalling and entering sharp left bank right berofe impacting ground.
Guys 1:30 pilot says 2300 ft...???? Airport operator said 2700 ft. I listened repeating on high volume 10 times....2300 ft... Si it means pilot lowed plane wrongly...
No, I hear 2700' clearly.
I hear 2300 @@VASAviation
I hear 2500ft.
I'm just speculating, but i wonder if there was snow. We've seen snow interfere with ILS before causing accidents
No snow, it was +2 outside
@@tadass.2675 coming from a cold country, +2 doesn't mean no snow, it means no new snow. Cars even warn that ice is possible below 4°
Records show light snow Friday afternoon for Vilnius, followed by temperatures around or below zero. I’m not familiar with the area, so I don’t know how far the airport is from the city.
There is a NOTAM on the ILS now
@@tadass.2675 visible snow in footage, and NOTAM on the ILS now. 1C and going down (not 2C) METAR as follows:
EYVI 250420Z 18016KT 9999 OVC008 01/M00 Q1020 NOSIG=
EYVI 250350Z 18015KT 9999 OVC008 01/M00 Q1020 TEMPO OVC005=
EYVI 250320Z 18017KT 9999 OVC007 01/M01 Q1020 TEMPO OVC005=
He said 2500 feet on decend via FAF. The approach plate says 2700 and the VNAV on flightaware/radar is 200 feet below glideslope. There are numerous hills on the chart marked as do not decent below 1000 feet. Last ADS-B is 750 feet. He did probably react in reverse while seeing the magenta above the glidepath from ILS, instead of pull he did a push.
I hear him say 2700' on the readback
M8 he clearly reads back correctly .. 2700 ft is clearly audible .. terrain is not a factor .. idk what plates you are using .. but the obstacles are way left of the runway ..
@@stefanocozzi8188 I am using the ILS 19 Z EYVI AD 2.24-22. See AIP LITHUANIA. The obstacles indicate that there is terrain on the approach path. If you check out available videos on the internet the pilots realize that they are too low and pull up but it is too late.... It might have also been false glide slope signal now that I am thinking.....
Requiescat in pace
1:30 they read back 2500 (maybe 2300?) feet
I hear 2700'. Anyway it's not a factor to the crash.
@@VASAviation Being 200ft lower than expected isn't a factor?
@@MoogieSRO No, it's not because the aircraft didn't crash into a mountain or a traffic for being 200 feet below the assigned altitude. Even if a mountain was there, 200 feet wouldn't be a factor since obstacle clearance altitudes exist and we must maintain a separation way greater than just 200'. The point of impact is nothing related to being 200' lower (which they were not according to ADSB data)
So many arm chair flight simmers thinking they know exactly what happened. A person has died, stop speculating with very limited knowledge and wait for the accident report.
Exactly! Like this is some contest to see who can guess the correct cause first. Happens with any crash, everyone speculating. Let the facts come out at least.