Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

Seconds from catastrophe. This arriving aircraft touched down while the departing aircraft was still on the runway finishing its takeoff roll. A few seconds either way, and this could have become one of aviation’s darkest accidents. ✈️ Put yourself in the cockpit: If you’re the arriving pilot and you... show more

aircraftmaintenancengineer

63,737 subscribers

104,368 Aufrufe • vor 25 Tagen •via X (Twitter)

Wissenschaft & Technologie Nachrichten & Politik

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

In case you missed yet another gem from AIR INDIA — An Air India Express aircraft departing from Oman to Kannur mistook the runway edge lights for the lights on the centre of the runway and started to take-off from the edge of the runway on May 15, damaging multiple runway edge lights. The crew aborted the take-off only after a cockpit alert and a loud bang inside the aircraft. The accident also caused a hydraulic leak and a flat tyre, leaving the aircraft disabled and grounded. Read more here:

In case you missed yet another gem from AIR INDIA — An Air India Express aircraft departing from Oman to Kannur mistook the runway edge lights for the lights on the centre of the runway and started to take-off from the edge of the runway on May 15, damaging multiple runway edge lights. The crew aborted the take-off only after a cockpit alert and a loud bang inside the aircraft. The accident also caused a hydraulic leak and a flat tyre, leaving the aircraft disabled and grounded. Read more here:

Shubhendu

29,076 Aufrufe • vor 2 Monaten

That Was WAY Too Close!The Runway Is Almost Gone for this A340✈️ Watch closely as the massive four-engine aircraft accelerates towards the end of the runway. For a moment, it looks like the runway is simply running out and then the aircraft finally lifts off. What could have been the reason for the risky late takeoff?

That Was WAY Too Close!The Runway Is Almost Gone for this A340✈️ Watch closely as the massive four-engine aircraft accelerates towards the end of the runway. For a moment, it looks like the runway is simply running out and then the aircraft finally lifts off. What could have been the reason for the risky late takeoff?

Aviation Reporter

789,131 Aufrufe • vor 2 Tagen

This is why fighter pilots are among the best in the world. The aircraft touches down on its main landing gear, and the pilot holds the nose high for several moments while still traveling at jet landing speeds. Notice how the tail comes within inches of the runway yet, thanks to the pilot's exceptional precision and control, it never strikes the ground. Incredible display of skills ✈️

This is why fighter pilots are among the best in the world. The aircraft touches down on its main landing gear, and the pilot holds the nose high for several moments while still traveling at jet landing speeds. Notice how the tail comes within inches of the runway yet, thanks to the pilot's exceptional precision and control, it never strikes the ground. Incredible display of skills ✈️

Aviation Reporter

236,773 Aufrufe • vor 4 Tagen

There are fast aircraft… and then there is this aircraft. The fastest crewed aircraft ever built… How much of an AvGeek are you? Do you know the answer to this one? #Aviation #pilot #avgeek #aviationdaily

There are fast aircraft… and then there is this aircraft. The fastest crewed aircraft ever built… How much of an AvGeek are you? Do you know the answer to this one? #Aviation #pilot #avgeek #aviationdaily

Scott Bateman MBE

28,847 Aufrufe • vor 1 Jahr

A Frontier Airlines flight bound for LAX hit a person on the runway during takeoff from Denver International Airport on Friday. The Airbus A321 was taking off from runway 17L when it appeared to strike an individual walking on the runway. The pilot quickly aborted the takeoff. Passengers were evacuated on the runway and are being bused back to the terminal. Fire crews were dispatched to the aircraft to extinguish the engine fire. Authorities have not yet released additional information about the person on the runway or the circumstances that led to the incident.

A Frontier Airlines flight bound for LAX hit a person on the runway during takeoff from Denver International Airport on Friday. The Airbus A321 was taking off from runway 17L when it appeared to strike an individual walking on the runway. The pilot quickly aborted the takeoff. Passengers were evacuated on the runway and are being bused back to the terminal. Fire crews were dispatched to the aircraft to extinguish the engine fire. Authorities have not yet released additional information about the person on the runway or the circumstances that led to the incident.

Breaking Aviation News & Videos

1,134,350 Aufrufe • vor 3 Monaten

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 that the first landing attempt was aborted. •Aligning with the runway in the fog proved difficult. •A second landing attempt was made. •During this, the pilot issued a MAYDAY call. •According to DGCA sources, it is a table-top runway. •During landing, the aircraft crashed near the edge of the runway. •Balance was lost at approximately 100 feet altitude. •The plane hit the ground before reaching the runway. •On impact, a major explosion occurred, followed by several smaller blasts. •A severe fire broke out on the aircraft. •Due to the fire, immediate rescue was not possible. •Investigation into the crash is ongoing; the final cause will be confirmed in the DGCA report.

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 that the first landing attempt was aborted. •Aligning with the runway in the fog proved difficult. •A second landing attempt was made. •During this, the pilot issued a MAYDAY call. •According to DGCA sources, it is a table-top runway. •During landing, the aircraft crashed near the edge of the runway. •Balance was lost at approximately 100 feet altitude. •The plane hit the ground before reaching the runway. •On impact, a major explosion occurred, followed by several smaller blasts. •A severe fire broke out on the aircraft. •Due to the fire, immediate rescue was not possible. •Investigation into the crash is ongoing; the final cause will be confirmed in the DGCA report.

Rahul Shivshankar

369,998 Aufrufe • vor 6 Monaten

#WATCH | Today, at around 8:50 AM, a training aircraft belonging to Red Bird Aviation made a crash landing near Gojubavi village adjacent to the Baramati airport. During the crash landing, a part of the aircraft hit a light pole before the aircraft crashed onto the ground. Only one trainee pilot was on board the aircraft and did not sustain any serious injuries. (Visuals from the spot)

#WATCH | Today, at around 8:50 AM, a training aircraft belonging to Red Bird Aviation made a crash landing near Gojubavi village adjacent to the Baramati airport. During the crash landing, a part of the aircraft hit a light pole before the aircraft crashed onto the ground. Only one trainee pilot was on board the aircraft and did not sustain any serious injuries. (Visuals from the spot)

ANI

30,931 Aufrufe • vor 2 Monaten

In 2025, a Flexjet 560 forced a Southwest 737 to go-around at Midway after crossing the runway while the aircraft was on final. Incredible awareness by the Southwest pilots to spot the danger and react in time 📹: streamtimelive

In 2025, a Flexjet 560 forced a Southwest 737 to go-around at Midway after crossing the runway while the aircraft was on final. Incredible awareness by the Southwest pilots to spot the danger and react in time 📹: streamtimelive

Aviation

80,357 Aufrufe • vor 3 Monaten

✈️| History was made on our runway last week. We welcomed the first all-electric aircraft to the airport as part of its European demo tour - the BETA ALIA CTOL. Did you spot it? 🔍

✈️| History was made on our runway last week. We welcomed the first all-electric aircraft to the airport as part of its European demo tour - the BETA ALIA CTOL. Did you spot it? 🔍

Edinburgh Airport

10,809 Aufrufe • vor 4 Monaten

The MD-11 has always had a critical design flaw. It was manageable until someone screwed up. To improve fuel efficiency and range, its horizontal stabilizer was made smaller than those of earlier DC-10 variants. While the design delivered performance benefits, it also reduced the aircraft's natural pitch stability, particularly at slower speeds during approach and landing. To help compensate, the MD-11 relied heavily on computerized stability augmentation systems. Many crews also preferred flying slightly faster approaches, which improved pitch stability but could make the aircraft more challenging to manage during touchdown due to its weight and sensitivity in roll and yaw. These characteristics became evident in several high-profile accidents. In 1997, a FedEx MD-11 arriving at Newark was reportedly operating under the belief that runway length was limited, prompting the crew to aim for an immediate touchdown. The aircraft landed hard, bounced, and became unstable. Instead of executing a go-around, attempts to salvage the landing resulted in another severe impact, collapsing the landing gear and destroying the aircraft in a post-crash fire. All five crew members survived. The accident highlighted a key lesson: when an MD-11 bounced significantly after touchdown, a go-around was often the safest option. That lesson resurfaced in tragic fashion in 2009 at Narita, Japan. During strong and gusty crosswinds, a FedEx MD-11 touched down hard and bounced. Believing the aircraft could still be recovered onto the runway, the crew attempted to continue the landing. The resulting control inputs led to an even harder impact, loss of control, and a crash that destroyed the aircraft and claimed the lives of both pilots. 📹: buybygb

Turbine Traveller

206,274 Aufrufe • vor 2 Monaten

A tense ATC recording is making rounds after a pilot forcefully rejected an assigned runway, warning air traffic control he would declare an emergency if unable to land on his preferred option. In the audio, the pilot states: “We can’t land on two two… if you don’t get us to runway three one right, we’re gonna declare emergency.” When the request wasn’t immediately approved, the crew followed through: “We’re declaring emergency. We’re going to land three one right.” repeating multiple times that the aircraft was now operating under emergency authority and instructing ATC to “remove everybody from our way.” ATC sought clarification before ultimately clearing the aircraft to land on Runway 31R, responding: “I just want to verify… I know you told me if you didn’t get 31 right, you would have to declare emergency.” What wasn’t obvious at first: • The aircraft had already gone around from Runway 22 • Crosswind components were about to exceed aircraft limits • Fuel state ruled out a diversion • The emergency was declared to secure a longer runway with less crosswind. 📹: Flight. Simulator.Fantasy Audio via LiveATC What’s your take? 👇

A tense ATC recording is making rounds after a pilot forcefully rejected an assigned runway, warning air traffic control he would declare an emergency if unable to land on his preferred option. In the audio, the pilot states: “We can’t land on two two… if you don’t get us to runway three one right, we’re gonna declare emergency.” When the request wasn’t immediately approved, the crew followed through: “We’re declaring emergency. We’re going to land three one right.” repeating multiple times that the aircraft was now operating under emergency authority and instructing ATC to “remove everybody from our way.” ATC sought clarification before ultimately clearing the aircraft to land on Runway 31R, responding: “I just want to verify… I know you told me if you didn’t get 31 right, you would have to declare emergency.” What wasn’t obvious at first: • The aircraft had already gone around from Runway 22 • Crosswind components were about to exceed aircraft limits • Fuel state ruled out a diversion • The emergency was declared to secure a longer runway with less crosswind. 📹: Flight. Simulator.Fantasy Audio via LiveATC What’s your take? 👇

Turbine Traveller

782,480 Aufrufe • vor 7 Monaten

V1 is the decision speed—the last speed at which a rejected takeoff is guaranteed to stop within the available runway. Above V1, the takeoff must be continued unless the aircraft is clearly unable to fly. But I read somewhere that when calculating takeoff performance (for any eventuality on the takeoff roll, like engine failure), instead of continuing the takeoff, the pilot flying would wait 2 seconds after reaching V1, then decide to reject the takeoff and safely come to a stop on the available runway distance. Could the LATAM B777-300ER pilots have used this same principle at Guarulhos? 📹: Aviação Guarulhos JPD (YouTube)

V1 is the decision speed—the last speed at which a rejected takeoff is guaranteed to stop within the available runway. Above V1, the takeoff must be continued unless the aircraft is clearly unable to fly. But I read somewhere that when calculating takeoff performance (for any eventuality on the takeoff roll, like engine failure), instead of continuing the takeoff, the pilot flying would wait 2 seconds after reaching V1, then decide to reject the takeoff and safely come to a stop on the available runway distance. Could the LATAM B777-300ER pilots have used this same principle at Guarulhos? 📹: Aviação Guarulhos JPD (YouTube)

Turbine Traveller

50,622 Aufrufe • vor 5 Monaten

The pilot of a twin-engine Cessna made an emergency belly landing at Arlington Municipal Airport on Thursday. With gears retracted, the pilot touched down on a foam-covered runway at about 12:42 p.m. and slid to a stop. A few moments later, two people exited the aircraft with their luggage and walked away, uninjured.

The pilot of a twin-engine Cessna made an emergency belly landing at Arlington Municipal Airport on Thursday. With gears retracted, the pilot touched down on a foam-covered runway at about 12:42 p.m. and slid to a stop. A few moments later, two people exited the aircraft with their luggage and walked away, uninjured.

Breaking Aviation News & Videos

278,677 Aufrufe • vor 1 Jahr

It’s 1989 and you’re making out on the hood of a car that’s parked close to a runway while a large aircraft takes off above you ✈️👩‍❤️‍💋‍👨 We all know this movie scene… #80s #nostalgia #synth

It’s 1989 and you’re making out on the hood of a car that’s parked close to a runway while a large aircraft takes off above you ✈️👩‍❤️‍💋‍👨 We all know this movie scene… #80s #nostalgia #synth

D r e a m k i d

13,112 Aufrufe • vor 1 Jahr

The crash occurred under conditions of dense fog in the Pune–Baramati area, with visibility severely reduced. The Baramati airstrip is a small facility without an Instrument Landing System (ILS), requiring the pilot to perform a manual visual landing. The aircraft did not make a direct approach to the runway; instead, it executed a wide turn, indicating that the first landing attempt was aborted. Aligning with the runway proved challenging in the poor visibility. On the second landing attempt, the pilot transmitted a MAYDAY call. The airstrip is a table-top runway, according to DGCA sources. During the final approach, the aircraft lost stability at around 100 feet and crashed just short of the runway, near its edge. On impact, a massive explosion occurred, followed by multiple smaller blasts, and an intense fire engulfed the aircraft. The impact of the crash & severity of the fire proved fatal for all the passengers & crew.

The crash occurred under conditions of dense fog in the Pune–Baramati area, with visibility severely reduced. The Baramati airstrip is a small facility without an Instrument Landing System (ILS), requiring the pilot to perform a manual visual landing. The aircraft did not make a direct approach to the runway; instead, it executed a wide turn, indicating that the first landing attempt was aborted. Aligning with the runway proved challenging in the poor visibility. On the second landing attempt, the pilot transmitted a MAYDAY call. The airstrip is a table-top runway, according to DGCA sources. During the final approach, the aircraft lost stability at around 100 feet and crashed just short of the runway, near its edge. On impact, a massive explosion occurred, followed by multiple smaller blasts, and an intense fire engulfed the aircraft. The impact of the crash & severity of the fire proved fatal for all the passengers & crew.

Rishi Bagree

100,764 Aufrufe • vor 6 Monaten

Another ill-fated take-off over V1 (in this case, V2!) June 13 1996: Garuda Indonesia Flight 865, a DC-10, crashes in Fukuoka (Japan) 3 of 275 aboard die. On take-off, the jet had just left the ground when one of the engines failed. Crew opted to reject the maneuver; the aircraft was unable to stop safely and left the runway: landing gear collapsed, and the airplane caught fire. Inquiry noted pilot actions by aborting takeoff above V1, where SOP dictated pilots should have continued takeoff and deal with the engine later. More info below from Aviation Safety Network – Aftermath video is from Aircrashdaily (go give them a follow on YouTube) “The DC-10 accelerated for takeoff. The nose was raised, and at a speed of 158 kts, the first officer called "Rotate". It was 12:07:40. Three seconds later, at a radio altitude of 9 feet, a fan blade of the 1st stage HP turbine from the no. 3 engine separated. The N1 dropped to 23,7% within a few seconds. At 12:07:45, the flight engineer called "Engine failure number one." Takeoff was aborted at about the V2 speed, and the airplane contacted the runway one second later at a vertical acceleration force of 2.1 Gs. The thrust reversers were deployed and ground spoilers were extended. The DC-10 skidded off the runway through a ditch, fence and a road, before coming to a halt 620 m past the runway threshold. Investigation revealed that the turbine blade that failed, had operated for 30913 hours and 6182 cycles. General Electric had advised customers to discard blades after about 6000 cycles. Accident cause Although the Aircraft was well in excess of V1 and the aircraft had already lifted off from the runway, the takeoff was aborted. Consequently, the aircraft departed the end of the runway, came to rest and caught fire. It is estimated that contributing to the rejection of the takeoff under this circumstance was the fact that the CAP's judgement in the event of the engine failure was inadequate."

Another ill-fated take-off over V1 (in this case, V2!) June 13 1996: Garuda Indonesia Flight 865, a DC-10, crashes in Fukuoka (Japan) 3 of 275 aboard die. On take-off, the jet had just left the ground when one of the engines failed. Crew opted to reject the maneuver; the aircraft was unable to stop safely and left the runway: landing gear collapsed, and the airplane caught fire. Inquiry noted pilot actions by aborting takeoff above V1, where SOP dictated pilots should have continued takeoff and deal with the engine later. More info below from Aviation Safety Network – Aftermath video is from Aircrashdaily (go give them a follow on YouTube) “The DC-10 accelerated for takeoff. The nose was raised, and at a speed of 158 kts, the first officer called "Rotate". It was 12:07:40. Three seconds later, at a radio altitude of 9 feet, a fan blade of the 1st stage HP turbine from the no. 3 engine separated. The N1 dropped to 23,7% within a few seconds. At 12:07:45, the flight engineer called "Engine failure number one." Takeoff was aborted at about the V2 speed, and the airplane contacted the runway one second later at a vertical acceleration force of 2.1 Gs. The thrust reversers were deployed and ground spoilers were extended. The DC-10 skidded off the runway through a ditch, fence and a road, before coming to a halt 620 m past the runway threshold. Investigation revealed that the turbine blade that failed, had operated for 30913 hours and 6182 cycles. General Electric had advised customers to discard blades after about 6000 cycles. Accident cause Although the Aircraft was well in excess of V1 and the aircraft had already lifted off from the runway, the takeoff was aborted. Consequently, the aircraft departed the end of the runway, came to rest and caught fire. It is estimated that contributing to the rejection of the takeoff under this circumstance was the fact that the CAP's judgement in the event of the engine failure was inadequate."

Francisco Cunha

157,331 Aufrufe • vor 1 Monat

That was a spectacular emergency landing while dragging the wing on the Runway surface before coming to a rest. On Wednesday, a Beechcraft B200 Super King Air aircraft (N3PX) made an emergency landing at the Conroe North Houston Regional Airport after experiencing a landing gear failure. The pilot is being hailed for the skill and successful emergency landing, while the prompt response from the first responders was praised. All three people on board, two passengers and the pilot, remained safe. 🎥Conroe Police Department, Texas #aircraft #safety

That was a spectacular emergency landing while dragging the wing on the Runway surface before coming to a rest. On Wednesday, a Beechcraft B200 Super King Air aircraft (N3PX) made an emergency landing at the Conroe North Houston Regional Airport after experiencing a landing gear failure. The pilot is being hailed for the skill and successful emergency landing, while the prompt response from the first responders was praised. All three people on board, two passengers and the pilot, remained safe. 🎥Conroe Police Department, Texas #aircraft #safety

FL360aero

52,846 Aufrufe • vor 1 Jahr

February 11, 2026 — Serious runway incursion at San Francisco International Airport. An Aeroméxico Boeing 737 operating Flight AM623 to Guadalajara began its takeoff roll on Runway 10R after being told to “hold position” — but was never cleared for takeoff. At the same time, an American Airlines aircraft was on short final to Runway 19L. As the jet accelerated, ATC urgently transmitted: “You are not cleared for takeoff. Cancel takeoff clearance.” The crew rejected take-off at approximately 49 knots, exited the runway, and were later advised to copy a phone number for a possible pilot deviation. 📹: flight.simulator.fantasy(Tiktok)

February 11, 2026 — Serious runway incursion at San Francisco International Airport. An Aeroméxico Boeing 737 operating Flight AM623 to Guadalajara began its takeoff roll on Runway 10R after being told to “hold position” — but was never cleared for takeoff. At the same time, an American Airlines aircraft was on short final to Runway 19L. As the jet accelerated, ATC urgently transmitted: “You are not cleared for takeoff. Cancel takeoff clearance.” The crew rejected take-off at approximately 49 knots, exited the runway, and were later advised to copy a phone number for a possible pilot deviation. 📹: flight.simulator.fantasy(Tiktok)

Turbine Traveller

47,967 Aufrufe • vor 5 Monaten