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.

Spoiler warning on why regulations are written in blood - the checklist debacle that caused one of Canada´s worst aircrashes was OTD, 56 years ago July 6 1970: Air Canada 621, a DC-8, crashes in Toronto (Canada), and all 109 aboard die. After a hard landing, the #4 engine... and part of the wing fell. The crew was attempting a go-around when the jet exploded. The investigation pointed out issues with SOP related to the deployment of ground spoilers. More details on this accident below, which is a textbook example on “why” not to invent regarding SOP, in this case regarding lift spoilers, a device which is activated on landing to reduce lift and slow the aircraft. The crew of Air Canada 621 (Captain Hamilton and First Officer Rowland) had an informal arrangement to handle spoilers differently depending on who was flying, deviating from standard procedure. The landing flare reduces descent just before touchdown, and if spoilers are armed, they deploy automatically upon landing. Instead of arming them during the pre-landing checklist as required, the captain favored deploying them only after touchdown, while the co-pilot preferred doing so during the landing flare. Both procedures were unauthorized. During this flight, the captain was landing and asked for spoilers during the flare, which was unusual. The first officer mistakenly deployed them, instead of arming them, causing a sudden loss of lift. The aircraft hit the runway hard, damaging an engine and the wing, but managed to take off again for a go-around. However, fuel leaks ignited, leading to multiple explosions that destroyed the right wing. The aircraft went into an irrecoverable dive and impacted a field, killing all aboard instantly. As expected, the enquiry focused on crew actions. Eight recommendations were made, including redesigning the spoiler activation lever so it cannot be used during flight, strengthening the DC-8’s wings and fuel tanks, and updating Air Canada’s training and operating manuals to clearly define proper spoiler arming and deployment procedures. Video is an extract from the Disaster Breakdown excellent video on the occurrence, titled “Did This Small Mistake Kill Everyone?” (don´t forget to go see it and drop them a like and subscribe)show more

Francisco Cunha

71,126 subscribers

29,127 Aufrufe • vor 1 Monat •via X (Twitter)

Nachrichten & Politik Wissenschaft & Technologie

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Air Canada Boeing 737 MAX 8 veered off the taxiway after landing at Montreal Airport on Thursday, coming to a stop on the grass. ADS-B data indicates that the aircraft landed on runway 06L and at a ground speed of 55 knots the aircraft vacated the runway via taxiway B3. It failed to turn onto taxiway B and veered off into the grass. In a statement Air Canada officials said Flight AC774 arriving from Los Angeles around 4 p.m. exited the taxiway after landing. By 7:45 p.m., Air Canada confirmed all passengers and crew had disembarked the plane and been transported to the terminal via buses.

Air Canada Boeing 737 MAX 8 veered off the taxiway after landing at Montreal Airport on Thursday, coming to a stop on the grass. ADS-B data indicates that the aircraft landed on runway 06L and at a ground speed of 55 knots the aircraft vacated the runway via taxiway B3. It failed to turn onto taxiway B and veered off into the grass. In a statement Air Canada officials said Flight AC774 arriving from Los Angeles around 4 p.m. exited the taxiway after landing. By 7:45 p.m., Air Canada confirmed all passengers and crew had disembarked the plane and been transported to the terminal via buses.

Breaking Aviation News & Videos

309,616 Aufrufe • vor 1 Monat

OTD in 2010: Air India Express Flight 812, a Boeing 737, crashes in Mangalore (India), 158 of 166 aboard die. On landing, the aircraft overran runway, fell down in a gorge and caught fire. Inquiry noted Captain actions in the unstabilized approach maneuver, despite multiple F/O and EGPWS warnings (More info below)⬇️ 🎥 Air Crash Animation (Youtube - go follow them there) From the accident enquiry (via ASN) "Direct Causes: The Court of Inquiry determines that the cause of this accident was Captain's failure to discontinue the 'unstabilised approach' and his persistence in continuing with the landing, despite three calls from the First Officer to 'go around' and a number of warnings from EGPWS. Contributing Factors to the Accident: 1. In spite of the availability of an adequate rest period prior to the flight, the Captain was in prolonged sleep during the flight, which could have led to sleep inertia. As a result of a relatively short period of time between his awakening and the approach, it possibly led to impaired judgment. This aspect might have got accentuated while flying in the Window of Circadian Low (WOCL). 2. In the absence of Mangalore Area Control Radar (MSSR), due to unserviceability, the aircraft was given descent at a shorter distance on DME as compared to the normal. However, the flight crew did not plan the descent profile properly, resulting in remaining high on approach. 3. Probably in view of ambiguity in various instructions empowering the 'copilot' to initiate a 'go around ', the First Officer gave repeated calls to this effect, but did not take over the controls to actually discontinue the ill-fated approach. "

Francisco Cunha

33,823 Aufrufe • vor 3 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,423 Aufrufe • vor 3 Monaten

The first accident covered by Mayday - Air Crash Investigation On this day in 1999: American Airlines Flight 1420, an MD-82, crashes in Little Rock (Arkansas, US), 11 of 145 aboard die. On landing, the jet overran the runway and hit airport structures. Factors: crew actions – continuing approach in bad weather, improper use of spoilers, etc- fatigue, poor CRM, others (as detailed below) From the NTSB report - (...) "The probable causes of this accident were the flight crew's failure to discontinue the approach when severe thunderstorms and their associated hazards to flight operations had moved into the airport area, and the crew's failure to ensure that the spoilers had extended after touchdown. Contributing to the accident were the flight crew's (1) impaired performance resulting from fatigue, and the situational stress associated with the intent to land under the circumstances; (2) continuation of the approach to a landing when the company's maximum crosswind component was exceeded; and (3) use of reverse thrust greater than 1.3 engine pressure ratio after landing." The events of Flight 1420 were featured in the first ever episode of the famous Mayday - Air Crash Investigation series, entitled "Racing the Storm", which debuted in 2003*. (Some folks might ask why the show´s crash animation isn´t here, but simply because this one, produced by the NTSB, is clearer to explain what happened)

The first accident covered by Mayday - Air Crash Investigation On this day in 1999: American Airlines Flight 1420, an MD-82, crashes in Little Rock (Arkansas, US), 11 of 145 aboard die. On landing, the jet overran the runway and hit airport structures. Factors: crew actions – continuing approach in bad weather, improper use of spoilers, etc- fatigue, poor CRM, others (as detailed below) From the NTSB report - (...) "The probable causes of this accident were the flight crew's failure to discontinue the approach when severe thunderstorms and their associated hazards to flight operations had moved into the airport area, and the crew's failure to ensure that the spoilers had extended after touchdown. Contributing to the accident were the flight crew's (1) impaired performance resulting from fatigue, and the situational stress associated with the intent to land under the circumstances; (2) continuation of the approach to a landing when the company's maximum crosswind component was exceeded; and (3) use of reverse thrust greater than 1.3 engine pressure ratio after landing." The events of Flight 1420 were featured in the first ever episode of the famous Mayday - Air Crash Investigation series, entitled "Racing the Storm", which debuted in 2003*. (Some folks might ask why the show´s crash animation isn´t here, but simply because this one, produced by the NTSB, is clearer to explain what happened)

Francisco Cunha

12,516 Aufrufe • vor 3 Monaten

A case of “get there itis” August 23 2005: TANS Perú Flight 204, a B-737, crashes in Pucallpa (Peru), 40 of 98 aboard die. On approach, the jet impacted swamplands in a CFIT, 3.8 mi from the runway. Report pointed to pilot actions, namely the decision to proceed with the landing attempt in poor weather, stating it was safer to divert. Inquiry noted that the crew failed to follow SOP in adverse weather. The captain assumed control of the aircraft, but the trainee pilot did not immediately monitor the instruments, leaving the crew unaware of the rapid descent during the critical seconds when the accident might have been avoided. Investigation of the crash site was hampered by looters, who removed various items from the wreck as scrap. A US$500 reward was offered and successfully led to the return of the flight data recorder. According to Aviation Safety Network, it was among the deadliest accidents of 2005 and the second major crash involving a TANS Perú aircraft in just over two years. Video – Mayday ACI “Blind Landing”

A case of “get there itis” August 23 2005: TANS Perú Flight 204, a B-737, crashes in Pucallpa (Peru), 40 of 98 aboard die. On approach, the jet impacted swamplands in a CFIT, 3.8 mi from the runway. Report pointed to pilot actions, namely the decision to proceed with the landing attempt in poor weather, stating it was safer to divert. Inquiry noted that the crew failed to follow SOP in adverse weather. The captain assumed control of the aircraft, but the trainee pilot did not immediately monitor the instruments, leaving the crew unaware of the rapid descent during the critical seconds when the accident might have been avoided. Investigation of the crash site was hampered by looters, who removed various items from the wreck as scrap. A US$500 reward was offered and successfully led to the return of the flight data recorder. According to Aviation Safety Network, it was among the deadliest accidents of 2005 and the second major crash involving a TANS Perú aircraft in just over two years. Video – Mayday ACI “Blind Landing”

Francisco Cunha

188,772 Aufrufe • vor 8 Tagen

The name on one of the crew might ring a bell... June 19 1947: Pan Am Flight 121, a Constellation, crash-lands in Mayadine (Syria). 14 of 36 aboard die. In flight, the #1 engine failed due to a mechanical issue. Attempting to divert to an alternate airport, the #2 engine also failed. The crew made a belly landing in the desert, where the aircraft caught fire. Among the survivors was a dead heading 3rd officer named Gene Roddenberry, who would go on to create the iconic science fiction television series “Star Trek”. This was Roddenbery´s 2nd major plane crash, having survived another major accident during his service in the Pacific Theatre, during WW2 Accident description from ASN (One of many period accidents where an engine failure led to a fatal crash. Nowadays, an engine fail is nearly routine and at worst it causes a diversion...) "The Constellation, named "Clipper Eclipse", was cruising at FL185 when the no. 1 prop had to be feathered due to engine problems. The remaining three engines overheated, forcing the crew to reduced power. This resulted in a gradual descent. The crew elected to continue to Istanbul instead of landing at the nearby Habbaniya RAF Station in Iraq. While descending through FL100 a fire broke out in the engine no. 2 nacelle. A rapid descent was started during which the no. 2 engine separated from the wing. With the left wing on fire a belly landing was carried out in the desert. It appeared the no. 1 engine failure was due to a broken exhaust rocker arm on the no.18 cylinder. The no. 2 engine failure was due to a failure of the thrust bearing which in turn resulted in blocking the passage of oil from the propeller feathering motor to the propeller dome. PROBABLE CAUSE: "The Board determines that the probable cause of this accident was a fire which resulted from an attempt to feather the No. 2 propeller after the failure of the No. 2 engine thrust bearing."

The name on one of the crew might ring a bell... June 19 1947: Pan Am Flight 121, a Constellation, crash-lands in Mayadine (Syria). 14 of 36 aboard die. In flight, the #1 engine failed due to a mechanical issue. Attempting to divert to an alternate airport, the #2 engine also failed. The crew made a belly landing in the desert, where the aircraft caught fire. Among the survivors was a dead heading 3rd officer named Gene Roddenberry, who would go on to create the iconic science fiction television series “Star Trek”. This was Roddenbery´s 2nd major plane crash, having survived another major accident during his service in the Pacific Theatre, during WW2 Accident description from ASN (One of many period accidents where an engine failure led to a fatal crash. Nowadays, an engine fail is nearly routine and at worst it causes a diversion...) "The Constellation, named "Clipper Eclipse", was cruising at FL185 when the no. 1 prop had to be feathered due to engine problems. The remaining three engines overheated, forcing the crew to reduced power. This resulted in a gradual descent. The crew elected to continue to Istanbul instead of landing at the nearby Habbaniya RAF Station in Iraq. While descending through FL100 a fire broke out in the engine no. 2 nacelle. A rapid descent was started during which the no. 2 engine separated from the wing. With the left wing on fire a belly landing was carried out in the desert. It appeared the no. 1 engine failure was due to a broken exhaust rocker arm on the no.18 cylinder. The no. 2 engine failure was due to a failure of the thrust bearing which in turn resulted in blocking the passage of oil from the propeller feathering motor to the propeller dome. PROBABLE CAUSE: "The Board determines that the probable cause of this accident was a fire which resulted from an attempt to feather the No. 2 propeller after the failure of the No. 2 engine thrust bearing."

Francisco Cunha

56,655 Aufrufe • vor 2 Monaten

Toronto Miracle was 21 years ago August 2 2005 - Air France Flight 358, an A340, crashes in Toronto (Canada). All 309 aboard survived. Due to the crew's actions landing in bad weather, the plane skidded off the runway and caught fire. A highly effective cabin evacuation was vital to the outcome. Due to severe weather, over 500 flights at Toronto Pearson were cancelled due to poor weather, but the crew persisted in attempting the landing. Canada´s Transport Minister called the event a “miracle”. Inquiry noted crew action: use of the shortest runway; the plane touched down nearly halfway through the runway, and the thrust reversers were not on full power until 17 seconds after touchdown. Video – Mayday ACI episode "Miracle Escape” (available on Youtube)

Toronto Miracle was 21 years ago August 2 2005 - Air France Flight 358, an A340, crashes in Toronto (Canada). All 309 aboard survived. Due to the crew's actions landing in bad weather, the plane skidded off the runway and caught fire. A highly effective cabin evacuation was vital to the outcome. Due to severe weather, over 500 flights at Toronto Pearson were cancelled due to poor weather, but the crew persisted in attempting the landing. Canada´s Transport Minister called the event a “miracle”. Inquiry noted crew action: use of the shortest runway; the plane touched down nearly halfway through the runway, and the thrust reversers were not on full power until 17 seconds after touchdown. Video – Mayday ACI episode "Miracle Escape” (available on Youtube)

Francisco Cunha

82,038 Aufrufe • vor 29 Tagen

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 2 Jahren

“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".

“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 Aufrufe • vor 1 Monat

Breaking - Air Canada 737 Max had runway excursion today in Montreal. None of 162 aboard hurt. After landing, jet veered into the grass as seen on this video. Aircraft was operating Flight AC774 and arriving from LAX. Plane is to be towed to a hangar for inspection.

Breaking - Air Canada 737 Max had runway excursion today in Montreal. None of 162 aboard hurt. After landing, jet veered into the grass as seen on this video. Aircraft was operating Flight AC774 and arriving from LAX. Plane is to be towed to a hangar for inspection.

Francisco Cunha

154,011 Aufrufe • vor 1 Monat

June 6 1989: the colorful 11 tragedy On This Day in 1989: Surinam Airways Flight 764, a DC-8, crashes in Paramaribo (Surinam). 176 of 187 aboard die in the worst air disaster in the country. The victims included several Dutch Surinamese football players, known as the “Colorful 11”- who were taking part in an exhibition match. The accident occurred as, attempting to land under foggy weather, the crew led the aircraft below the MSA – Minimum Sector Altitude – causing the jet to hit a tree near the airport. The investigation was very critical of the crew's actions, who opted to use an unreliable ILS system on the maneuver and did not react to GPWS alarms. Subsequently, the enquiry unearthed severe issues with the crew´s qualifications. The Captain was over the legal age to operate the aircraft, and also his license did not allow flying the DC-8, while the copilot also had some legal issues. The "probable cause" paragraph from the report reads as follows: CAUSE: "The Commission determines: a) That, as a result of the captain's glaring carelessness and recklessness, the aircraft was flown below the published minimum altitudes during the approach and consequently collided with a tree. b) As an underlying factor in the accident was the failure of SLM's operational management to observe the pertinent regulations as well as the procedures prescribed in the SLM Operations Manual concerning qualification and certification during recruitment and employment of the crew members furnished by ACI." The video seen here is an extract from a 1992 Dutch TV special on the accident, which includes a reenactment of the accident. You can see it on YouTube as “TV: Reporter (19920304) - SLM Vliegramp Suriname PY 764 | PY764”

June 6 1989: the colorful 11 tragedy On This Day in 1989: Surinam Airways Flight 764, a DC-8, crashes in Paramaribo (Surinam). 176 of 187 aboard die in the worst air disaster in the country. The victims included several Dutch Surinamese football players, known as the “Colorful 11”- who were taking part in an exhibition match. The accident occurred as, attempting to land under foggy weather, the crew led the aircraft below the MSA – Minimum Sector Altitude – causing the jet to hit a tree near the airport. The investigation was very critical of the crew's actions, who opted to use an unreliable ILS system on the maneuver and did not react to GPWS alarms. Subsequently, the enquiry unearthed severe issues with the crew´s qualifications. The Captain was over the legal age to operate the aircraft, and also his license did not allow flying the DC-8, while the copilot also had some legal issues. The "probable cause" paragraph from the report reads as follows: CAUSE: "The Commission determines: a) That, as a result of the captain's glaring carelessness and recklessness, the aircraft was flown below the published minimum altitudes during the approach and consequently collided with a tree. b) As an underlying factor in the accident was the failure of SLM's operational management to observe the pertinent regulations as well as the procedures prescribed in the SLM Operations Manual concerning qualification and certification during recruitment and employment of the crew members furnished by ACI." The video seen here is an extract from a 1992 Dutch TV special on the accident, which includes a reenactment of the accident. You can see it on YouTube as “TV: Reporter (19920304) - SLM Vliegramp Suriname PY 764 | PY764”

Francisco Cunha

14,627 Aufrufe • vor 2 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 7 Monaten

NEW: Air Canada pilot dragged out of the cock pit by a flight attendant while suffering from a seizure, causing an emergency landing. Air Canada said Flight AC7664 was en route from Newark, New Jersey, to Halifax, Nova Scotia, when the pilot suffered an apparent seizure. The captain allegedly yanked the wheel, causing the aircraft to jolt sideways, alarming passengers. The flight attendant dragged the pilot out of the cockpit, and passengers held down the pilot, who was seizing, for about 40 minutes. The first officer took over as captain and safely diverted the plane to an emergency landing in Boston. Rodney McDonald, who was traveling with his wife and 2 sons, said, "It really felt like someone had jilted the controls, and then it happened over and over again. And, you know, every thought goes through your mind, you start praying. My boys instantly started praying."

NEW: Air Canada pilot dragged out of the cock pit by a flight attendant while suffering from a seizure, causing an emergency landing. Air Canada said Flight AC7664 was en route from Newark, New Jersey, to Halifax, Nova Scotia, when the pilot suffered an apparent seizure. The captain allegedly yanked the wheel, causing the aircraft to jolt sideways, alarming passengers. The flight attendant dragged the pilot out of the cockpit, and passengers held down the pilot, who was seizing, for about 40 minutes. The first officer took over as captain and safely diverted the plane to an emergency landing in Boston. Rodney McDonald, who was traveling with his wife and 2 sons, said, "It really felt like someone had jilted the controls, and then it happened over and over again. And, you know, every thought goes through your mind, you start praying. My boys instantly started praying."

E X X ➠A L E R T S

110,934 Aufrufe • vor 2 Monaten

In case you were wondering, this is how it works. A towbarless aircraft tug is used to push an aircraft back from the gate. Instead of using a towbar, it drives up to the nose wheels, clamps them in place and lifts the nose landing gear slightly off the ground. The main landing gear stays on the ground at all times. Once secured, the tug controls the steering and carefully pushes the aircraft into position for taxi. Only a small part of the aircraft's weight rests on the nose gear which is why even large aircraft like the Boeing 777 can be moved safely and smoothly. After pushback, the tug lowers the nose wheels and disconnects, and the pilots continue taxiing.

In case you were wondering, this is how it works. A towbarless aircraft tug is used to push an aircraft back from the gate. Instead of using a towbar, it drives up to the nose wheels, clamps them in place and lifts the nose landing gear slightly off the ground. The main landing gear stays on the ground at all times. Once secured, the tug controls the steering and carefully pushes the aircraft into position for taxi. Only a small part of the aircraft's weight rests on the nose gear which is why even large aircraft like the Boeing 777 can be moved safely and smoothly. After pushback, the tug lowers the nose wheels and disconnects, and the pilots continue taxiing.

Mechanical Knowledge

467,411 Aufrufe • vor 5 Monaten

On November 21, 2021, a Cessna 172N was involved in an accident during a solo pattern flight at Old Bridge Airport in New Jersey. The student pilot had completed several takeoffs and landings with a flight instructor earlier that day and was cleared for solo operations. During a solo landing, the airplane bounced, and the pilot initiated a go-around. During the initial climb, the aircraft pitched up sharply, entered an aerodynamic stall, turned to the left, and descended to the ground. The airplane impacted the left side of the runway, sustained substantial damage, and a post-impact fire ensued. The student pilot sustained minor injuries. The NTSB determined the probable cause was the student pilot’s loss of control during the go-around, which resulted in an aerodynamic stall. 📸 runthisshitt

On November 21, 2021, a Cessna 172N was involved in an accident during a solo pattern flight at Old Bridge Airport in New Jersey. The student pilot had completed several takeoffs and landings with a flight instructor earlier that day and was cleared for solo operations. During a solo landing, the airplane bounced, and the pilot initiated a go-around. During the initial climb, the aircraft pitched up sharply, entered an aerodynamic stall, turned to the left, and descended to the ground. The airplane impacted the left side of the runway, sustained substantial damage, and a post-impact fire ensued. The student pilot sustained minor injuries. The NTSB determined the probable cause was the student pilot’s loss of control during the go-around, which resulted in an aerodynamic stall. 📸 runthisshitt

aircraftmaintenancengineer

19,305 Aufrufe • vor 6 Monaten

#WATCH | Aligarh, Uttar Pradesh: Trainee aircraft of Pioneer Flying Club makes emergency landing in a field in the village of Chandauda due to a reported technical glitch. Collectorate Aligarh, Atul Kumar Gupta says, “...there was a trainee pilot and an instructor on the aircraft…they took off at 9 am from the airport and made the emergency landing due to a technical glitch…both of them are safe along with the aircraft. A permission is required from DGCA, for which a team from Delhi is coming to investigate…”

#WATCH | Aligarh, Uttar Pradesh: Trainee aircraft of Pioneer Flying Club makes emergency landing in a field in the village of Chandauda due to a reported technical glitch. Collectorate Aligarh, Atul Kumar Gupta says, “...there was a trainee pilot and an instructor on the aircraft…they took off at 9 am from the airport and made the emergency landing due to a technical glitch…both of them are safe along with the aircraft. A permission is required from DGCA, for which a team from Delhi is coming to investigate…”

ANI

19,230 Aufrufe • vor 3 Monaten

32 years ago today - The (in)famous Fairchild B-52 crash June 24 1994: a USAF B-52 crashes in Fairchild AFB (Washington, US). All 4 crew members die. Practicing aerobatics, the bomber stalled at low height. Inquiry noted the pilot´s behavior/personality and his superior’s lack of reaction to earlier incidents, becoming a case study for CRM. The accident occurred as the B-52's pilot, Lieutenant Colonel Arthur "Bud" Holland, maneuvered the bomber beyond its operational limits and lost control. The aircraft stalled, fell to the ground, and exploded, killing Holland and the other three crew aboard. The crash was captured on video and was shown repeatedly on news broadcasts throughout the world. This fatal accident was preceded by several other incidents, including one where the Holland missed a ridge by some 30 ft during a fly-by. A later enquiry focused on military leadership, due to several incidents that preceded the crash, along with CRM – Crew Resource Management. The subsequent investigation concluded that the crash was attributable primarily to three factors: Holland's personality and behavior; USAF leaders' delayed or inadequate reactions to earlier incidents involving Holland, and the sequence of events during the aircraft's final flight. The crash is now used in military and civilian aviation environments as a case study in teaching crew resource management. It is also often used by the U.S. Armed Forces during aviation safety training as an example of the importance of compliance with safety regulations and correcting the behavior of anyone who violates safety procedures. The occurrence is also known as the “Czar 52 crash”, which was the bomber´s callsign. Its registration was 61-0026 and was part of the USAF´s 92nd Bomb Wing ”Czar 52” was the B-52´s callsign. Its registration was 61-0026 and was part of the USAF´s 92nd Bomb Wing

32 years ago today - The (in)famous Fairchild B-52 crash June 24 1994: a USAF B-52 crashes in Fairchild AFB (Washington, US). All 4 crew members die. Practicing aerobatics, the bomber stalled at low height. Inquiry noted the pilot´s behavior/personality and his superior’s lack of reaction to earlier incidents, becoming a case study for CRM. The accident occurred as the B-52's pilot, Lieutenant Colonel Arthur "Bud" Holland, maneuvered the bomber beyond its operational limits and lost control. The aircraft stalled, fell to the ground, and exploded, killing Holland and the other three crew aboard. The crash was captured on video and was shown repeatedly on news broadcasts throughout the world. This fatal accident was preceded by several other incidents, including one where the Holland missed a ridge by some 30 ft during a fly-by. A later enquiry focused on military leadership, due to several incidents that preceded the crash, along with CRM – Crew Resource Management. The subsequent investigation concluded that the crash was attributable primarily to three factors: Holland's personality and behavior; USAF leaders' delayed or inadequate reactions to earlier incidents involving Holland, and the sequence of events during the aircraft's final flight. The crash is now used in military and civilian aviation environments as a case study in teaching crew resource management. It is also often used by the U.S. Armed Forces during aviation safety training as an example of the importance of compliance with safety regulations and correcting the behavior of anyone who violates safety procedures. The occurrence is also known as the “Czar 52 crash”, which was the bomber´s callsign. Its registration was 61-0026 and was part of the USAF´s 92nd Bomb Wing ”Czar 52” was the B-52´s callsign. Its registration was 61-0026 and was part of the USAF´s 92nd Bomb Wing

Francisco Cunha

271,552 Aufrufe • vor 2 Monaten

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 7 Monaten

Lufthansa flight LH1753 evacuated in Athens after returning to the airport when the crew received an APU fire warning and reported smoke in the rear of the cabin. Lufthansa confirmed that three passengers suffered minor injuries during the evacuation on Monday and were transferred to a hospital in Athens for first aid treatment. A spokesperson for the airline said, "The crew of the Airbus A321, following the standard procedures, declared a state of air emergency in flight, in order to obtain priority landing clearance. During the evacuation process, three passengers were slightly injured and taken to a hospital for first aid. The safety of passengers and crew is our absolute priority."

Lufthansa flight LH1753 evacuated in Athens after returning to the airport when the crew received an APU fire warning and reported smoke in the rear of the cabin. Lufthansa confirmed that three passengers suffered minor injuries during the evacuation on Monday and were transferred to a hospital in Athens for first aid treatment. A spokesperson for the airline said, "The crew of the Airbus A321, following the standard procedures, declared a state of air emergency in flight, in order to obtain priority landing clearance. During the evacuation process, three passengers were slightly injured and taken to a hospital for first aid. The safety of passengers and crew is our absolute priority."

Breaking Aviation News & Videos

177,852 Aufrufe • vor 3 Monaten