Skip to content

Wednesday the 20th of May, 2026

After sorting out some webpage issues, here are your stories for today...

Be safe out there!

Tom

--

Aircraft from Vance Air Force Base makes emergency belly landing in Kansas

An aircraft from Vance Air Force Base performed an emergency belly landing in Kansas on Tuesday afternoon.

By Addison Kliewer - Special Projects Producer/Digital Editor

WICHITA, Kan. —

An aircraft from Vance Air Force Base performed an emergency belly landing in Kansas on Tuesday afternoon.

An Air Force T-6A Texan II, a single-engine, two-seat aircraft used to train Joint Primary Pilot Training students, landed at McConnell Air Force Base, according to a news release from the Kansas Air Force base.

Both pilots exited the aircraft without injuries following the emergency landing, according to the news release. Emergency response crews were on the scene immediately, and the pilots were checked by medical personnel.

Students typically fly the aircraft to learn basic flying skills used by U.S. Air Force and Navy pilots.

The initial investigation is underway. A board of officers will be appointed to formally investigate the incident.

Vance Air Force Base is located in Enid, Oklahoma. The landing took place at McConnell Air Force Base, which is in Wichita, Kansas.

The two bases are about 120 miles apart.

https://www.koco.com/article/vance-air-force-base-emergency-belly-landing-kansas-t-6a-texan-ii/71356065

Another plane makes emergency landing on road near Lake Havasu

By Haley Williams

LAKE HAVASU, AZ (AZFamily) — Another plane made an emergency landing on an Arizona road, this time near Lake Havasu City.

The emergency landing happened around 3 p.m. Thursday on Highway 95 after the plane experienced engine failure after taking off from a nearby airport, according to officials with the Arizona Department of Public Safety.

No one was injured, but the two occupants of the plane were taken to a nearby hospital for further evaluation, officials said.

This comes after several planes have made emergency landings on Arizona roads in the past month. Thankfully, no one has been seriously hurt, but aviation experts are wondering what’s to blame for the trend.

One theory is that the public may just be seeing and hearing about incidents involving aircraft more often.

“Because everybody has a camera and because everybody’s on social media, a lot of these events are being brought to the public in real time,” Tim Kiefer, assistant professor of air traffic management at Embry-Riddle Aeronautical University, previously told Arizona’s Family.

Another possibility is that Arizona skies are filled with pilots in training.

“Arizona is the flight training capital of quite literally the world. People from everywhere come here to learn. So when you have new pilots in aircraft learning to fly, they’re going to have incidents and accidents,” said Steven Devine, owner of Fly Aero Angel Flight Training.

Aging aircraft could also be a factor.

“The aviation fleet is getting older. They’re not producing airplanes anymore like they used to,” Devine said. “As these planes get older, they’re going to have problems.”

The experts agreed that full investigations into each of the landings will reveal whether this is a concerning trend or a series of unfortunate coincidences.

The FAA and NTSB will investigate the landings.

https://www.azfamily.com/2026/05/19/another-plane-makes-emergency-landing-road-near-lake-havasu/

Faulty Part in UPS Plane Crash Was Often Overlooked, Witnesses Say

Investigators suggested that infrequent maintenance requirements, among other issues, appeared to contribute to the faulty part that caused the crash, which killed 15 people last year.

By Billy Witz and Karoun Demirjian

Weeks after a UPS cargo plane crashed in Louisville, Ky., last November, a preliminary report by investigators identified the cause as a fractured bracket that led an engine to break off.

On Tuesday, the investigators revealed factors that appeared to have contributed to the part’s failure: infrequent maintenance requirements, siloed inspection information and ignorance among line mechanics and other key people about longstanding warnings that a bearing assembly within the bracket could fail.

Those details emerged in a National Transportation Safety Board hearing about the crash, which killed 15 people on the outskirts of the Louisville airport.

The bearing problem was known for years and was identified by Boeing, the manufacturer, in a series of service bulletins over a decade ago. The bulletins recommended periodic visual inspections and replacing the faulty apparatus with an updated mechanism avoiding the same fundamental weaknesses.

But those warnings may have been insufficient, investigators suggested, as they questioned representatives of UPS; the Federal Aviation Administration; Boeing; the Teamsters; and ST Engineering San Antonio Aerospace, which had conducted maintenance on the plane. Boeing never insisted that operators must replace the bearing assembly, and didn’t flag the problem as posing a potential flight-safety issue, some testified.

“Pre-accident, it was never scheduled to be replaced,” David Springer, the senior director of engineering at UPS, said of the problematic bearing, which, when it failed, ended up damaging lugs in the bracket assembly and set off a chain of catastrophic events. “It would have flown to failure.”

The Louisville crash harked back to the deadliest one in United States aviation history: the 1979 crash of American Airlines Flight 191 that killed all 271 people on board. That plane, a McDonnell-Douglas DC-10, was the forerunner to the MD-11 jet that crashed in Louisville, and it also went down when the left engine separated and fell to the runway.

The Louisville accident also raised questions about why, in later years, a string of problems with the MD-11’s bearing assembly hadn’t prompted more decisive action from the manufacturer or regulators — and why, in some cases, episodes appeared to have gone unreported to the Federal Aviation Administration.

Investigators zeroed in on four reports of failed bearings that were made to the F.A.A., in 2007, 2008, 2017 and 2020.

As investigators scrutinized those episodes, some — including the board chair, Jennifer Homendy — questioned why Boeing had never identified the problematic bearing as a “principal structural element,” a designation it had given the lugs holding the assembly together.

“There was a misunderstanding initially, 20 years ago, about the severity of the event that might result from the failure of this bearing,” said Melanie Violette, an F.A.A. engineer. “It was not believed to be critical to the integrity, the safety of the aircraft.”

Were it known that a bearing failure could severely damage the lug, “that would have changed the safety determination,” she added.

Henry Gallegos, the director of engineering at ST Engineering San Antonio Aerospace, said there were certain reasons to examine the bearings, which were encased in a sealant. But if the bearing “was just beginning to migrate, you would not be able to see it with that sealant installed,” he said.

As it was, the Louisville plane was up-to-date with its required maintenance schedule. But during the hearing, expert testimony revealed that the bearings could degrade even if no one was yet scheduled to look at them.

A maintenance technician told investigators that in 2020, while removing the engine on an MD-11 to reach an area of the wing he had to repair, he happened to see a bearing so corroded it had to be replaced.

But in transcribed interviews released by the N.T.S.B. on Tuesday, mechanics, quality control specialists and UPS’s own aircraft maintenance representative said they had been completely unaware of Boeing’s service letter regarding bearing maintenance. Their testimony strongly suggested they might not have known to look for degradation or damage outside of the specific visual check the F.A.A. requires every six years.

“I have never heard of that until now,” one mechanic who had been with ST Engineering for five years told N.T.S.B. investigators who asked about the published bulletin, according to transcripts. “That’s probably out of my job description,” said another, when asked if mechanics ever tried to look for potential bulletins or other airworthiness problems with the planes they serviced, outside of those flagged by UPS.

Two quality control officials for ST Engineering San Antonio Aerospace who were interviewed also professed ignorance about the existence of the service letter regarding the bearings. So did an aircraft maintenance representative for UPS. “I learned of that in Louisville a week and a half ago,” the representative said in December after the accident, according to an interview transcript. “I think somebody showed me that.”

In the aftermath of the Louisville crash, MD-11 planes were grounded and subjected to inspections. In the course of those checks, three were found to have cracks in the same bearing apparatus. But like the plane that crashed, they were not due for visual inspections.

https://www.nytimes.com/2026/05/20/us/ntsb-ups-plane-crash-louisville.html

Today in History

61 Years ago today: On 20 May 1965 PIA flight 705, a Boeing 720, crashed while on approach to Cairo Airport, Egypt, killing 121 occupants; 6 survived the accident.

Date: Thursday 20 May 1965
Time: 01:48
Type: Boeing 720-040B
Owner/operator: Pakistan International Airlines - PIA
Registration: AP-AMH
MSN: 18379/321
Year of manufacture: 1962
Engine model: P&W JT3D-3B
Fatalities: Fatalities: 121 / Occupants: 127
Other fatalities: 0
Aircraft damage: Destroyed, written off
Category: Accident
Location: ca 20 km S of Cairo International Airport (CAI) -    Egypt
Phase: Approach
Nature: Passenger - Scheduled
Departure airport: Dhahran International Airport (DHA/OEDR)
Destination airport: Cairo International Airport (CAI/HECA)
Confidence Rating:  Accident investigation report completed and information captured

Narrative:
PIA flight 705, a Boeing 720, crashed while on approach to Cairo Airport, Egypt, killing 121 occupants; 6 survived the accident.

Flight PK705 was the inaugural service from Karachi, Pakistan to London, U.K. Intermediate stops were planned at Dhahran, Saudi Arabia, Cairo, Egypt and Geneva, Switzerland.
The flight departed Dhahran at 21:22 UTC for Cairo. The flight was uneventful and at 23:40 UTC, 01:40 local time, it was cleared for a left-hand circuit for runway 34. At 23:45 the crew reported turning on finals. The Boeing 720 kept descending and struck the ground short of the runway in a slight left-bank attitude with its undercarriage up and flaps at 20 degrees.

PROBABLE CAUSE: "The aircraft did not maintain the adequate height for the circuit and continued to descend until it contacted the ground. The reason for that abnormal continuation of descent is unknown."

Scroll To Top