Loading video...

Video Failed to Load

Go Home

Crash Sequence: •Dense fog over the Pune–Baramati area, visibility extremely low. •Baramati airstrip is small and does not have ILS (Instrument Landing System) facilities. •The pilot had to attempt a manual and visual landing. •The aircraft did not approach the runway directly but made a large turn. •This indicated...

369,998 views • 6 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

#WATCH | Charter plane crash landing in Baramati (Maharashtra) | Delhi: Vijay Kumar Singh, director and key owner of VSR Ventures Private Limited (operating as VSR Aviation), which operated the ill-fated plane, says, "...It was the pilot's decision. He made an approach from runway 29, and then he carried out a missed approach, after which he again tried to make an attempt from runway 11. I also have no contact with the pilots; they are not there. It is a very unfortunate decision. We are very sad about it. We are trying to first be with the families who have lost their next of kin. It is a very unfortunate incident. Primarily, it appears that the pilot could not see the runway...He was a very experienced pilot, more than 16,000 hours of experience. The co-pilot also had 1500 hours of experience. The Captain was very experienced. He was with Sahara, JetLite, Jet Airways and he was very experienced on this type of aeroplane also...The aircraft was very well-maintained. There was absolutely no problem in the aircraf, there was no technical failure in the aircraft as far as we know...My deepest condolences. Captain Sumit Kapoor was a very good friend of mine. He was a brother to me. His son is also a pilot with us. Captain Shambhavi Pathak was a daughter to me. Both of them were extremely good human beings and extremely good pilots..." On the 2023 plane crash incident, he says, "What happened in 2023 occurred at Mumbai airport. It was raining then too and the visibility was low. The pilot skidded off the runway after touchdown. So, that was the incident..."

ANI

265,571 views • 6 months ago

“Probable Cause: The pilot's operation of the airplane while intoxicated, which resulted in a loss of airplane control on landing” (and at the wrong airport) July 18 2019: a private Citation II crashes in Nevada (US), no casualties. Jet left the runway on landing at Mesquite, lost its undercarriage, and was destroyed in a fire. The aircraft was on a ferry flight, and it was not intended to land at Mesquite: the pilot was later arrested on suspicion of flying while drunk (later confirmed) (Below is an exact quote of the accident report: I can imagine that when this came out, the pilot was busy printing CVs) “After authorities arrived on site, the pilot was arrested for operating an aircraft under the influence of alcohol. The pilot was found to have a blood alcohol level of .288, which exceeded the FAA's allowable limit of .040. This likely contributed to the pilot landing at the incorrect airport and his subsequent loss of airplane control during landing” More info here, from the NTSB report "The flight departed Pasco-Tri-Cities Airport, Washington, at about 16:25 on a ferry flight to Las Vegas-Henderson Sky Harbor Airport, Nevada. While approaching Class B airspace, air traffic control noted the pilot’s slurred speech and repeatedly asked if the oxygen system was working. About 85 miles from the destination, the pilot reported having a nearby airport in sight and requested a visual approach several times, despite being instructed to continue southwest. The airplane soon dropped off radar, landed at the unintended airport instead, and touched down hard about halfway down the runway before sliding to a stop on the left side, with the fuselage and wings largely destroyed by post-impact fire".

Francisco Cunha

25,158 views • 1 month ago

Remember the C-130 crash in Colombia a month ago and killed 24 and left 43 injured? News reports indicated the pilots were arrested after the preliminary report came out. Given the outcome, the preliminary report pointed to pilot actions, along with runway conditions and weather, underlining there were no mechanical issues with the aircraft. Key findings from the investigation include: No mechanical failures contributed to the accident. The aircraft departed Viru Viru bound for El Alto. Weather conditions at the destination deteriorated en route, with storms and hail reported, but the crew received no weather updates. On arrival at El Alto, the crew was cleared to land on runway 10. Due to convective activity on that runway, they opted to approach runway 28 instead. Runway 28 is located at 13,300 ft elevation, measures 4,000 m in length, and has a negative gradient of 1.55%. METAR data indicated winds between 050°/10 kt and 360°/08 kt. According to the Investigators, the approach was conducted above the glide slope and at excessive speed. The aircraft touched down on the nose gear only, approximately 1,200 m beyond the threshold. Without compression of the main landing gear struts, the brakes and thrust reversers remained unavailable. Once the main gear touched down, the aircraft entered a section of runway contaminated by hail and slush, resulting in hydroplaning in the final third of the runway, an overrun, and the accident. Info - Aviation today

Francisco Cunha

693,526 views • 3 months ago