logo
Small planes crash in midair over Arizona airport, killing 2: What we know

Small planes crash in midair over Arizona airport, killing 2: What we know

Yahoo20-02-2025
Two people were killed Wednesday morning when two small airplanes crashed in midair at a regional airport in southern Arizona – the latest in a series of North American aviation disasters in recent weeks.
The crash, which occurred at the Marana Regional Airport, about 21 miles northwest of Tucson, is also the second fatal aviation mishap this month in Arizona.
Details about the victims and the circumstances that preceded the crash remained slim Thursday morning, nearly 24 hours later.
Here's everything to know so far:
Plane crashes 2025: How many have plane crashes have there been in 2025? How many people have died?
The crash involved two fixed-wing, single-engine aircraft, Vincent Rizzi, a Marana Police Department sergeant, told the Arizona Republic, a USA TODAY Network publication.
One of the airplanes has been identified as a Cessna 172S and the other as a Lancair 360 MK II.
The collision occurred around 8:30 a.m. over a runway at the Marana Regional Airport. While the Cessna landed safely, the Lancair crashed near another runway, sparking a fire that sent plumes of smoke into the air, the National Transportation Safety Board said in a written statement to the Republic.
Marana Airport Superintendent Galen Beem described the crash as "an unprecedented event" in a statement.
'On behalf of the Town of Marana and the Marana Regional Airport, our hearts go out to all the individuals and families impacted by this event,' Beem said in a written statement shared in a news release from the Marana police.
The airport remained closed as of Wednesday afternoon, police said in the latest post on social media.
Two people were on board each aircraft, the Marana town government posted on Facebook.
Rizzi told the Republic that the two aboard the Cessna that landed safely were not severely injured, meaning both those on the Lancair were killed in the crash.
Authorities had not publicly identified any of the victims in the crash as of Thursday morning.
The Marana Regional Airport, which is mostly used for leisure flights, is located in a rural area surrounded by farm fields and desert brush.
The airport is also home to two flight schools.
The two aircraft involved in the fatal crash were not among the 259 aircraft based at the airport, Vic Hathaway, communications manager for the town of Marana, told the Republic.
The National Transportation Safety Board confirmed on social media site X it was investigating the crash. Marana officials indicated Wednesday that further information would come from the NTSB.
The FAA released a statement to USA TODAY confirming details about the crash. USA TODAY left a message Thursday morning with the NTSB seeking further information.
The regional airport is what's known as an "uncontrolled field," meaning it does not have an air traffic control tower, according to the FAA.
At uncontrolled airports, pilots use a common traffic advisory frequency to regularly announce their position to other pilots who are in the airport vicinity, the agency said. Pilots operating in uncontrolled fields also must still comply with all FAA regulations, including maintaining visibility and safe altitudes.
While a crewed tower was supposed to be in place by the end of 2024 to accommodate an increase in traffic and improve safety, its construction was delayed, Hathaway told the Republic. That delay was mostly related to supply chain issues stemming from the COVID-19 pandemic, she added.
Although experts have said air travel remains extremely safe, the crash is at least the sixth major aviation disaster of 2025 in North America, USA TODAY reported.
That includes a high-profile deadly crash in Washington DC on Jan. 29 in which a military Black Hawk helicopter collided in midair with an American Airlines regional jet, killing 67 people near Ronald Reagan National Airport. It was the first fatal crash of a U.S. airliner in nearly 16 years.
Just days after the crash near Washington, D.C., a medical jet carrying a child patient crashed into a Philadelphia neighborhood. Seven people died, including all six on board the aircraft and another in a car on the ground.
The Arizona crash also comes days after 18 people were injured when a Delta Airlines regional jet crash landed upside down Monday in Toronto.
Another 10 people were killed earlier this month when a small plane crashed in Alaska after experiencing a rapid loss of altitude and speed. The aircraft, heading from the village of Unalakleet to the town of Nome, was initially reported missing before it was later recovered.
The crash is also the second fatal aviation incident this month in Arizona after one person was killed Feb. 10 when two private jets collided on a runway at Scottsdale Airport.
Another four people were injured when a Learjet owned by Mötley Crüe singer Vince Neil veered off the runway and hit a parked Gulfstream jet at the small municipal airport, officials said. While the investigation revealed that it appeared the plane's landing gear had failed, no official cause of the crash had been announced.
Neil was not among the two passengers and two pilots on board the Learjet during the crash. One person was aboard the other Gulfstream jet.
Contributing: Christopher Cann, USA TODAY
This article originally appeared on USA TODAY: 2 killed in Arizona after planes collide in midair: What we know
Orange background

Try Our AI Features

Explore what Daily8 AI can do for you:

Comments

No comments yet...

Related Articles

Less than a second before hitting a passenger jet, helicopter instructor told pilot to change course, NTSB hearing reveals
Less than a second before hitting a passenger jet, helicopter instructor told pilot to change course, NTSB hearing reveals

CNN

time25 minutes ago

  • CNN

Less than a second before hitting a passenger jet, helicopter instructor told pilot to change course, NTSB hearing reveals

The first of the National Transportation Safety Board's three days of investigative hearings is underway to help determine what caused the deadly midair collision on January 29 between an Army helicopter on a training mission and American Airlines flight 5342 landing at Ronald Reagan Washington National Airport. Transcripts of the cockpit voice recorders and air traffic control audio released in the docket for Wednesday's hearing reveal what was said inside the aircraft in the moments before the crash. As the passenger jet approached the airport, inside the helicopter the instructor was asking the pilot to descend. 'You're at three hundred feet, come down for me,' the transcript from the cockpit voice recorder, also known as a black box, says. Pilots on the regional jet performed their checks to land as the tower told the helicopter, call sign PAT 25, to look out for their CRJ-700 regional jet approaching at 1,200 feet. 'PAT 25 has the traffic in sight. Request visual separation,' the helicopter responds, asking for permission to avoid it visually. In the helicopter the instructor says, 'He's got'em stacked up tonight,' according to the black box transcript. The pilot responds, 'Yeah kinda, busy.' At 8:47 p.m., the controller asks the helicopter, 'PAT 25, you have the CRJ in sight?' as the beeping of an alert the planes are getting too close together is heard in the background. 'PAT two five has uh – aircraft in sight. Request visual separation,' the helicopter responds. Another instruction – to stay behind the passenger plane – wasn't heard in the helicopter as a momentary press of the radio microphone in the Black Hawk cut it off. Inside the helicopter, the instructor tells the pilot to change course. 'Alright kinda come left for me ma'am, I think that's why he's asking… We're kinda… out towards the middle.' 'Oh-kay,' the helicopter pilot responds. 'Fine.' Not even a second later the recordings capture the sound of the collision and impact as the aircraft falls into the icy river below. The NTSB also presented for the first time major 'discrepancies' in the altitude readouts on board the US Army Black Hawk helicopter that led to the crew believing they were flying lower over the Potomac River than they actually were. Investigators said Wednesday that, following the crash, they tested three of the same models of Black Hawk helicopters from the same Army unit involved in the collision flying over the river. 'Notably, the barometric altimeters continued to be 80 to 130 feet lower than the helicopter's determined altitude above sea level when flying at speed over the tidal portion of the Potomac River,' NTSB investigator Marie Moler presented to the hearing. Barometric altimeters use pressure to gauge altitude and can be impacted by a variety of atmospheric and other factors. In its preliminary report, the NTSB said the Black Hawk was consistently higher than maximum published altitudes along the Potomac River, including when it collided with the passenger jet. The heavily technical findings are the most significant in the early moments of Wednesday's 10-hour-long hearing schedule. The Army, PSA Airlines, a regional subsidiary of American Airlines which operated the plane, the Federal Aviation Administration and other parties are represented. 'This is not an adversarial hearing,' NTSB Chair Jennifer Homendy said in her opening remarks. 'This does not mean difficult questions won't be asked. They will be, and they should be. This is an investigation. We are here to improve safety.' At the start of the hearing, an 11-minute animation was shown detailing the minutes leading up to the collision and a video of the accident itself. The board paused briefly to allow any of the family members of the victims of the crash to leave the room or look away before it was played. The air traffic controller working in the control tower that night was responsible for two different positions on two different radio channels, the timeline animation reveled. The captain of the regional jet had completed 106 flights into the airport and the first officer had completed 51, records reviewed by NTSB showed. However, investigators said interviews with PSA Airline's pilots showed they generally didn't know much about the helicopter routes in the area. Three Reagan National Airport-based captains and one first officer were asked about their knowledge of published helicopter routes and only one PSA captain – who was a former military helicopter pilot in the region – had knowledge of the routes prior to the accident. Sixty-seven people died in the accident over the Potomac River, including 60 passengers and four crew on the plane and three soldiers on the helicopter. The NTSB will meet Wednesday, Thursday and Friday to discuss the facts learned in the investigation. It is expected to conclude with a determination of what caused the crash in January.

NTSB finds Army chopper in fatal midair crash with plane was above altitude limit
NTSB finds Army chopper in fatal midair crash with plane was above altitude limit

Los Angeles Times

time2 hours ago

  • Los Angeles Times

NTSB finds Army chopper in fatal midair crash with plane was above altitude limit

Investigators probing the January midair collision of a passenger plane and an Army helicopter over Washington that killed 67 people found the chopper was flying higher than the it should have been and the altitude readings were inaccurate. The details came out of the first day of National Transportation Safety Board hearings in Washington, where investigators aim to uncover insights into what caused the crash between the American Airlines plane from Wichita, Kan., and the Black Hawk helicopter over Ronald Reagan National Airport. The board opened the three days of hearings by showing an animation and playing audio and video from the night of the collision, as well as questioning witnesses and investigators about how the Federal Aviation Administration and the Army may have contributed to nation's deadliest plane crash since November 2001. It's likely too early for the board to identify what caused the crash. The January incident was the first in a string of crashes and near misses this year that have alarmed officials and the traveling public, despite statistics that still show flying remains the safest form of transportation. The hearing opened Wednesday with a video animation showing where the helicopter and airliner were leading up to the collision. It showed how the helicopter flew above the 200 feet altitude limit on the helicopter route along the Potomac River before colliding with the plane. Investigators said Wednesday the flight data recorder showed the helicopter was actually 80 feet to 100 feet higher than the barometric altimeter the pilots relied upon showed they were flying. So the NTSB conducted tests on three other helicopters from the same unit in a flight over the same area and found similar discrepancies in their altimeters. Dan Cooper with Sikorsky helicopters said that when the Black Hawk helicopter involved in the crash was designed in the 1970s, it used a style of altimeter that was common at the time. Newer helicopters have air data computers that didn't exist back then that help provide more accurate altitude readings. Chief Warrant Officer Kylene Lewis told the board that she wouldn't find an 80 to 100 foot discrepancy between the different altimeters on a helicopter alarming because at lower altitudes she would be relying more on the radar altimeter than the barometric altimeter. Below 500 feet, Lewis said she would be checking both instruments and cross referencing them. She said as long as an altimeter registers an altitude within 70 feet of the published altitude before takeoff the altimeter is considered accurate under the checklists. But previously, NTSB Chairwoman Jennifer Homendy highlighted that the published helicopter routes around Washington D.C. would allow planes and helicopters to routinely come within 75 feet of each other during landing. Army officials said Wednesday that the flight manual for these older Black Hawks doesn't highlight the discrepancies in altimeters that has been documented previously, but typical flight separations are at least 500 feet around airports. Previously disclosed air traffic control audio had the helicopter pilot telling the controller twice that they saw the airplane and would avoid it. The animation ended with surveillance video showing the helicopter colliding with the plane in a fiery crash. Investigations have already shown the FAA failed to recognize a troubling history of 85 near misses around Reagan airport in the years before the collision, and that the Army's helicopters routinely flew around the nation's capitol with a key piece of locating equipment, known as ADS-B Out, turned off. Aviation attorney Bob Clifford, who is working to file one of the first lawsuits against the government next month, said he hopes NTSB will look beyond the immediate factors that caused this crash to highlight the bigger ongoing concerns in the crowded Washington airspace. Even though the final NTSB report won't be released until sometime next year, U.S. Sen. Ted Cruz isn't waiting to propose changes. He introduced legislation Tuesday that would require all aircraft operators to use both forms of ADS-B, or Automatic Dependent Surveillance Broadcast, the technology to broadcast aircraft location data to other planes and air traffic controllers. Most aircraft today are equipped with ADS-B Out equipment but the airlines would have to add the more comprehensive ADS-B In technology to their planes. 'There cannot be a double standard in aviation safety,' Cruz said. 'We should not tolerate special exceptions for military training flights, operating in congested air space.' The legislation would revoke an exemption on ADS-B transmission requests for Department of Defense aircrafts. It also would require the FAA to evaluate helicopter routes near airports and require the Army Inspector General to review the Army's aviation safety practices. Homendy said her agency has been recommending that move for decades after several other crashes. Transportation Secretary Sean Duffy said that while he'd like to discuss 'a few tweaks,' the legislation is 'the right approach.' He also suggested that the previous administration 'was asleep at the wheel' amid dozens of near-misses in the airspace around Washington's airspace. Homendy said the hearings over the next few days will be a 'fact-finding proceeding.' The NTSB will also post thousands of pages of evidence from the crash investigation online. FAA Administrator Bryan Bedford said that he expects 'we're going to have some very uncomfortable conversations over the next two and a half days' but that 'they need to be had in the clear light of day – and simply put the best interest of the traveling public ahead of any of our personal interests, perhaps.' The hearings in Washington involve NTSB board members, investigators and witnesses for organizations involved in the crash. Panels will focus on military helicopter routes in the Washington area, collision avoidance technology and training for air traffic controllers at Ronald Reagan National Airport, among other subjects. Federal officials have also raised concerns over the nation's outdated and understaffed air traffic control system. During January's mid-air crash above Washington, one controller was handing both commercial airline and helicopter traffic at the busy airport. Duffy has announced a multi-billion-dollar plan to overhaul the system controllers use that relies on old technology like floppy disks. Funk writes for the Associated Press. AP writers Leah Askarinam, Ben Finley and Rio Yamat contributed to this story.

Federal Investigators Set to Begin Hearings on D.C. Plane Crash
Federal Investigators Set to Begin Hearings on D.C. Plane Crash

New York Times

time9 hours ago

  • New York Times

Federal Investigators Set to Begin Hearings on D.C. Plane Crash

Federal investigators on Wednesday are expected to begin providing the clearest picture yet of what went wrong earlier this year when an Army Black Hawk helicopter crashed into an American Airlines regional jet outside Washington, D.C., killing 67 people and touching off a crisis of confidence in air travel safety. The National Transportation Safety Board, which has spent the last six months investigating the accident, is set to convene the first of three days of public hearings at 9 a.m. Eastern. Federal aviation safety officials, military brass and other parties involved in the crash are scheduled to testify about the events leading up to the midair collision near Ronald Reagan National Airport on the evening of Jan. 29. The board is also expected to release approximately 10,000 pages of new documents related to the crash at the same time the hearing begins, including transcripts of the cockpit recordings from both American Airlines Flight 5342 and the Army Black Hawk and of the air traffic control transmissions to all aircraft in the area. The documents are also expected to include a combined transcript illustrating how all of those communications overlapped in real time, as well as factual reports about the air control tower, aircraft and the people involved in operating them that night. Though the board already issued a preliminary report and urgent recommendations, and the Federal Aviation Administration has already implemented safety measures to reduce the risk of a similar episode in the nation's capital, there are still a number of unanswered questions. They include why an Army helicopter on a pilot evaluation mission flew higher than was allowed in the vicinity of one of the nation's most congested airports, what led to the air traffic control tower being understaffed that evening, and various communication failures that might have contributed to the fatal collision. N.T.S.B. investigators are not expected to reach any conclusions about the cause of the accident, though the board's chairwoman, Jennifer Homendy, has promised that those, and final safety recommendations, will be issued by next January. Want all of The Times? Subscribe.

DOWNLOAD THE APP

Get Started Now: Download the App

Ready to dive into a world of global content with local flavor? Download Daily8 app today from your preferred app store and start exploring.
app-storeplay-store