logo
ICT Together fund will help crash victims' families

ICT Together fund will help crash victims' families

Yahoo30-01-2025
WICHITA, Kan. (KSNW) — The Wichita Foundation has started a fund to provide aid to help families of the American Airlines crash victims. The ICT Together fund will also support local efforts, such as grief counseling and mental health services.
'Our hearts go out to those on board Flight 5342 from Wichita, Kansas to Washington, D.C. last night, as well as the crew of the helicopter involved in the tragic collision,' the Wichita Foundation said in a news release. 'Wichita is strongest when we come together – ICT Together is one way we can support our neighbors in need.'
The fund will be used for:
Crisis support – Aid for impacted families,
Community aid – Resources for first responders, local nonprofits, and organizations aiding in community aid efforts, and
Healing and resilience – Support for mental health services, grief counseling, and community aid efforts.
If you would like to donate to ICT Together, go to ICT-together.org. If your donation exceeds $5,000, email meghan@wichitafoundation.org or call 316-264-4880.
What we know about the DC plane crash victims
The Wichita Foundation promises that 100% of contributions will go toward those affected.
Copyright 2025 Nexstar Media, Inc. All rights reserved. This material may not be published, broadcast, rewritten, or redistributed.
Orange background

Try Our AI Features

Explore what Daily8 AI can do for you:

Comments

No comments yet...

Related Articles

Hearings will dig into unanswered questions in deadly D.C. plane crash
Hearings will dig into unanswered questions in deadly D.C. plane crash

Washington Post

time43 minutes ago

  • Washington Post

Hearings will dig into unanswered questions in deadly D.C. plane crash

Army and Federal Aviation Administration officials are expected to face tough questions this week over their management of the crowded skies around Washington's Reagan National Airport, as safety investigators hold public hearings about January's deadly midair collision that killed 67 people. For three days starting Wednesday, the National Transportation Safety Board will grill witnesses and release thousands of pages of documents as it strives to answer crucial questions about the cause of the nation's first fatal commercial airline crash in more than 15 years. The Jan. 29 collision — between an American Airlines regional jet arriving from Wichita and an Army Black Hawk helicopter on a training mission — killed 64 passengers and crew on the airliner and all three crew members aboard the helicopter. The helicopter was flying on a dedicated helicopter route that follows the Potomac River and passes beneath a landing path for one of the runways at National. The NTSB has said it is examining why the helicopter was flying too high as it sped south over the river. Also unclear is whether its crew mistook another airliner in the night sky for the American Airlines flight. Even under normal circumstances, there was little margin for error between the helicopter route and the landing path; a Washington Post examination found the gap was as little as 15 feet. But on the night of the crash the helicopter was flying 78 feet higher than the 200-foot altitude limit on the helicopter route, investigators have found. The hearing is a key part of the NTSB's investigation but a final determination on the causes of the crash will probably not be reached until next year. The Army has disclosed little about its own review of the accident, frustrating family members of the victims, many of whom were figure skaters returning from a development camp in Wichita. NTSB Chair Jennifer Homendy has previously said she was angry that the FAA had not identified the risks in the busy shared corridor, despite having evidence of the dangers available in its own records. She has also said she is seeking information about a government working group set up in the years before the crash to manage the risks of helicopters in the area. 'We never want this to happen to anybody else,' Homendy said in an interview Monday. She said she and other board members have met multiple times with family members of the victims, who will be briefed ahead of the hearings on what to expect. She added she hopes to have the investigation wrapped up by the anniversary of the accident. Aviation safety expert John Cox, who spent decades flying in and out of the airspace around National Airport as a commercial pilot, said he anticipates investigators will be training their attention most closely on what happened aboard the Black Hawk. 'I think everything will focus on the helicopter crew because the jet was pretty much where it was supposed to be,' Cox said. The first session, on Wednesday, will examine the systems on board the helicopter, including its altimeter — the device that tells pilots how high they are flying — while a second panel includes an overview of the helicopter routes. On Thursday, the NTSB reviewers will examine air traffic control procedures and training at National. On the final day, Friday, the safety board will examine safety data and safety management by government agencies. Here's what to watch for as the hearings unfold: On older Black Hawks, like the one involved in the crash, there are two main ways to determine the helicopter's altitude. The first is through a barometric altimeter, which measures altitude based on air pressure changes. The second is through the radio altimeter, which measures altitude through the time it takes for signals from the Black Hawk's antennas to hit the ground and bounce back. The barometric altimeter has to be manually adjusted by the crew before and during each flight. Former Army Black Hawk pilot Brad Bowman vividly remembers twisting the knob to set the reading as a standard part of the procedure before takeoff. Bowman flew in the 12th Aviation Battalion — the same unit involved in the crash — in the early 2000s and is acutely aware of the small margin of error in the vicinity of National Airport. 'It really, really matters,' Bowman said. The Black Hawk's altitude reading can be 'off significantly if you don't have the right setting.' If the barometric altimeter wasn't set or was set incorrectly, it would affect the altitude the crew was seeing in the cockpit. Summaries of cockpit voice recordings previously released by the NTSB indicate that moments earlier during the helicopter's southbound flight along the Potomac River, the instructor pilot said that the Black Hawk was at 400 feet, while the pilot under evaluation during the training flight said the helicopter was at 300 feet. The two crew members did not flag or discuss the altitude discrepancy, the NTSB has said. Shortly after the crash, NTSB investigators reported that the Black Hawk's radio altimeter was reporting the helicopter at 278 feet at the moment of impact, but investigators have cautioned that they found conflicting data in the flight recorder. They have not released the barometric altitude reading the pilots may have seen. The public also has not been told if the crew had the most accurate readings available on the altitude and location of the commercial jets around them. Some older Army helicopters do not have an integrated ADS-B system, which stands for 'Automatic Dependent Surveillance-Broadcast.' There are two elements to ADS-B: 'out,' which would have broadcast the Black Hawk's position, and 'in,' which could have provided the crew with real-time information on the aircraft around them. The crew was not transmitting ADSB-out because it had spent part of that night flying sensitive routes. It had checked out an ADSB-in device to have on the flight, but it was still not clear if it was using it at the time of the accident, three Army officials told The Post. Flying into National at night can be magical, with the national monuments, White House, Capitol Hill and city development lit up on either side of the Potomac River. But it can also add up to a lot of light pollution. That's not an ideal setting for night vision goggles, which the NTSB believes the crew was wearing at the time of the crash. At the time of the crash, the Army's policy was that if one of the crew was in night vision goggles, all of them had to be. The Army said that policy has not changed. The goggles amplify the light and make it brighter. In the case where there's multiple ground- or air-based sources of light, it can create a situation in which it's hard to discern between different sources of light. But most importantly, night vision goggles limit a crew's field of view, much as wearing a swimming mask can reduce your field of view. 'And field of view in aviation is everything,' Bowman said. Mark Tomicich, a former FAA attorney who worked on several high-profile aviation accident investigations, said a reconstruction of what happened in the moments before the collision will offer important information about what went wrong. While many experts have focused on the Army helicopter and its three-member crew, he said he is interested in detail about what took place in the cockpit of the regional jet, after pilots were instructed by the tower to shift course and land on Runway 33 rather than Runway 1. The regional jet had a collision warning technology known as TCAS, an automated cockpit warning system that advises about conflicts with nearby aircraft. According to the preliminary report released by the NTSB in March, about 19 seconds before the collision, the cockpit crew for the operator of the American Airlines regional jet, PSA, received a TCAS alert that should have signaled the need for heightened awareness, Tomicich said. 'In some respects, with TCAS, the PSA crew had an electronic advantage over the helicopter crew and over the controller's radar,' Tomicich said. The controller managing the helicopter's journey past the airport first alerted the Army crew to the landing jet about two minutes before the crash. The helicopter crew, at that point more than six miles from the plane, said they had the jet in sight, and the controller approved their request to continue using 'visual separation.' That means it was the pilots' responsibility to avoid the plane. The controller received a conflict alert about 20 seconds before the crash, according to the NTSB — a sign that something was amiss. Within a few seconds, the controller provided instructions to the Army pilots to 'pass behind' the jet, and they again responded that they had it in sight. Visual separation is widely used near airports, experts said, and it allows for greater volumes of traffic to navigate busy airspace. But Scott Dunham, a former NTSB investigator, said the hearing could be an opportunity to scrutinize how it is applied. While the helicopter crew reported having the jet in sight, experts have said they might have confused two aircraft, and it's impossible for controllers to know for certain whether pilots are looking at the right aircraft. Controllers could have directed the helicopter to pause while allowing the incoming jet to land. Former Army pilots who have flown those routes said they have been directed to fly ellipses about a mile north of the airport when airspace is congested. The NTSB has indicated that the controller's instruction to 'pass behind' the airliner might not have been heard from the helicopter crew because they had briefly pressed the button on their own microphone, blocking the transmission. Information that the jet was 'circling' to Runway 33 was also not audible on the helicopter. Experts said what the helicopter pilots understood should become clearer with the release of the full transcript of their conversations as logged by the aircraft's cockpit voice recorder. In March, the NTSB urgently recommended that the FAA make changes to its helicopter routes, saying the corridors near National posed an 'intolerable risk.' The FAA swiftly closed the corridors to all but emergency and other essential flights. The Post reported in February that in the decade before the crash airline pilots had received more than 100 warnings about helicopters from their collision avoidance systems — incidents that were also logged by the FAA. Controllers at the National tower had raised questions about the helicopter route past the airport, including proposing shifting it over land to the east, The Post has also reported. That would have moved it further from the landing path, but no changes were made. At a Senate hearing in March, Homendy said she had been seeking information about a Washington-area helicopter working group but had been unable to determine who served on it or obtain minutes of its meetings. If investigators have now obtained those records, they could provide vital insight into how the FAA, the Army and other agencies that fly in the area collaborated on safety. Alex Horton and Brian Perlman contributed to this report.

'Leave All Carry-On Items Behind' During An Emergency Plane Evacuation Does Not Mean 'Grab Your Bags First', You Dinguses
'Leave All Carry-On Items Behind' During An Emergency Plane Evacuation Does Not Mean 'Grab Your Bags First', You Dinguses

Yahoo

time14 hours ago

  • Yahoo

'Leave All Carry-On Items Behind' During An Emergency Plane Evacuation Does Not Mean 'Grab Your Bags First', You Dinguses

It seems like every couple of days, a commercial flight makes the news over something that went wrong, and that's even before you account for all the small, private plane crashes. In one of the most recent examples, CNN reports an American Airlines flight leaving Denver International was evacuated prior to takeoff after experiencing a "possible landing gear incident." The good news is, everyone got off the plane with only one reported injury. The bad news is, a video of the evacuation showed many passengers ignored crewmember instructions and grabbed their bags before leaving the plane. That, my friends, is what we call "a bad idea," and it's not just because you're supposed to follow all crew orders. You're supposed to leave your bags on the plane during an emergency evacuation because it slows you down, and in turn, lengthens how long it takes to get everyone else off the plane. According to the Federal Aviation Administration, commercial aircraft need to be able to be fully evacuated in 90 seconds or less, but according to CNN, evacuating this American Airlines flight took 10 to 15 minutes. Yikes. Thankfully, the brake fire that broke out as a result of the landing gear issue wasn't big enough to take the entire plane with it, but that also isn't something you're going to know when the crew gives the order to evacuate the plane. And when they say to leave all carry-on items behind, they're serious. You get up, get off the plane and worry about your designer luggage, laptop and charger cables later. Pausing to grab your bags doesn't just make you selfish. It makes you a danger to everyone else on the plane. Read more: These Are The Worst Tire Recalls In Recent History Leave Everything Behind The good news is, as you can see in the video above, not everyone on board ignored crew instructions. Some people did what they were told and left their bags on board, but you can also see that wasn't the case for far too many of them. And even if you care more about your bags than other people getting off the plane safely, there's another lesson to be learned here, too. Going down the emergency slide and landing gracefully on your feet at the bottom isn't exactly guaranteed, but it looks like the passengers carrying their bags had a much harder time doing so than everyone else. So, even in a situation like this one, where passengers taking at least 10 minutes to evacuate the plane didn't prove deadly, you significantly increase your chances of injuring yourself on the tarmac when you lose your balance. You also run the risk of your luggage puncturing the slide on your way out, potentially injuring other passengers and making it far more difficult for the crew to manage the evacuation. As the video above points out, even if you travel with nice luggage, the Department of Transportation requires airlines to cover any damage to your bags while they're under the airlines' control. So even if the entire plane burned up and took your luggage with it, you'd still be entitled to compensation for what you lost. It's also just stuff, and stuff can be replaced. People, on the other hand, are much more difficult to replace, and prioritizing your personal convenience over other people's lives is bad, actually. If the crew announces an emergency evacuation, just leave your bags. It'll be fine, and no bag is worth risking someone else's life. If that isn't a good enough reason for you, at least leave your bags behind so you don't get mocked for your bad behavior online. Surely, you don't want that, right? Want more like this? Join the Jalopnik newsletter to get the latest auto news sent straight to your inbox... Read the original article on Jalopnik.

Passengers flee smoking jet on emergency slide after apparent landing gear problem at Denver airport
Passengers flee smoking jet on emergency slide after apparent landing gear problem at Denver airport

Chicago Tribune

timea day ago

  • Chicago Tribune

Passengers flee smoking jet on emergency slide after apparent landing gear problem at Denver airport

Passengers slid down an emergency slide of a smoking jet at Denver International Airport due to a possible problem with the plane's landing gear, authorities said. American Airlines Flight 3023 reported a 'possible landing gear incident' during its departure from Denver on Saturday afternoon, the Federal Aviation Administration said. The problem involved an aircraft tire, the Fort Worth, Texas-based airline said in a statement. The Boeing 737 MAX 8 carrying 173 passengers and six crew members was on its way to Miami International Airport, American said. Video showed people sliding down the inflatable chute near the front of the plane while clutching luggage and small children. Some passengers, including at least one adult carrying a young child, tripped at the end of the slide and fell onto the concrete runway. Passengers were then taken to the terminal by bus. Shay Armistead, a 17-year-old from Minturn, Colorado, described a chaotic scene. After hearing a loud 'boom,' the plane 'started to violently shake and we were drifting to the left side of the runway,' Armistead told The Associated Press in an interview. Armistead and her teammates on a ski racing team were on their way from Colorado to Chile when it happened. 'I started grabbing my friend's hands, I was like 'Oh my God,' and then they slammed on the brakes, and we all like went forward and they finally brought the plane to a stop,' she said. 'It was just terrifying.' One of the passengers was taken to a hospital with a minor injury, American Airlines said in its statement. Five people were evaluated for injuries at the scene but did not require hospitalization, airport officials said. 'About halfway to takeoff speed, we hear a big bang and a pop,' passenger Shaun Williams told KUSA-TV. 'The pilot immediately started abort procedures for taking off. You could feel him start to hit the brakes.' Firefighters extinguished a fire on the aircraft, the Denver Fire Department said. 'All customers and crew deplaned safely, and the aircraft was taken out of service to be inspected by our maintenance team,' American said. In a statement, the FAA said it's investigating. Armistead said she's thankful for everyone who helped her and the other passengers, and grateful that she's safe. 'You've just got to appreciate what you're given, and I'm so grateful that it wasn't worse,' Armistead said.

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