Here are your stories for today...
Be safe out there!
Tom
--
Flames shoot from DHL cargo plane during emergency landing at LAX, video shows
By Irene Cruz
LOS ANGELES (KABC) -- 
Tires on a DHL cargo plane caught on fire during an emergency landing at Los Angeles International Airport on Wednesday night, an intense moment caught on video.
The incident unfolded around 11 p.m. Wednesday as the plane arrived at LAX from Phoenix. Video shows the moment the plane touched down with flames shooting from underneath it.
Emergency crews rushed to the aircraft, forcing one of the runways to temporarily close. AIR7 got a view after the fire was put out and could see four rear tired with severe damage. 
Air traffic control audio captured the pilot reporting that the aircraft's brakes locked up.
Additional details about what caused the fire or what led up to the emergency landing were unclear.
No injuries were immediately reported.
https://abc7.com/post/tires-dhl-plane-appear-catch-fire-landing-lax/19742987/
American Airlines flight blows two tires just before departing from O'Hare
This is at least the fifth flight to blow a tire at O'Hare Airport this month.
By Izzy Stroobandt and NBC Chicago Staff
Passengers aboard an American Airlines flight were
forced to deplane right before takeoff after the aircraft they were on blew two tires while taxiing at O'Hare Airport on Wednesday afternoon, marking the fifth incident of such kind this month at the Chicago airport.
Around 1:30 p.m., American Airlines flight 3280 bound for Charlotte from Chicago blew two tires while taxiing for departure at O'Hare, according to the Federal Aviation Administration.
No injuries were reported and passengers exited the plane via its stairs and were bused to the terminal, authorities said.
Video posted to social media showed firefighters boarding the plane on the tarmac. At least one of the flat tires could also be seen in the video. 
The tire blew shortly after the plane pushed back from the gate, officials said.
American Airlines said passengers aboard the plane will "depart shortly ​on ​a ​replacement aircraft" in a statement sent to NBC Chicago.
​"We ​never ​want to ​disrupt ​our ​customers' ​travel plans and we apologize for the ​inconvenience ​this ​caused," American Airlines said in the statement.
Several incidents involving issues with landing gear and specifically blown tires have occurred this month at O'Hare Airport.
On August 13, a United Airlines flight blew a tire while
taking off. Then, on August 17, an American Airlines flight blew a tire while taxiing after landing just hours before a United Airline flight also blew a tire after landing. On August 21, an American Airlines flight again blew a tire after landing. While not related to a tire blowing, a Republic Airlines flight also reported issues with their breaking gear on August 25.
The FAA is continuing to investigate.
Private Plane crashes near South Lake Tahoe Airport runway
Petra Molina
SOUTH LAKE TAHHOE, Calif. – A private airplane crashed near the north end of the South Lake Tahoe Airport runway Wednesday morning. 
The incident occurred at approximately 8:50 a.m. South Lake Tahoe Police Department, South Lake Tahoe Fire Rescue and the El Dorado County Sheriff’s Office were dispatched to the airport, City of South Lake Tahoe Public Information Officer Sheree Juarez told the Daily Tahoe Tribune.
The pilot reportedly self-extracted from the aircraft and there were no reported injuries.
The aircraft was a single-engine Cessna and the incident occurred during landing, Juarez said.
The cause of the crash remains under investigation.
https://www.tahoedailytribune.com/news/private-plane-crashes-near-south-lake-tahoe-airport-runway/
Pampulha Airport runway closed after plane overturns.
Operations at the airfield were suspended during the afternoon of this Wednesday (26).
By g1 Minas — Belo Horizonte
Operations at Pampulha Airport, in Belo Horizonte , were suspended for a few hours on Wednesday afternoon (26). According to the airport administration, a plane with two occupants experienced problems during landing at 3:49 pm. No one was injured.
Images show the aircraft overturned on the runway,
which had to be closed for the removal of the twin-engine plane and an inspection by terminal teams ( see above ). The incident occurred one day after a Cirrus SR22 crashed and caught fire in Mateus Leme, in the Greater Belo Horizonte area .
This is a Hawker Beechcraft King Air C90GTi aircraft, registration PP-ADU. According to the Brazilian Aeronautical Registry (RAB) of the National Civil Aviation Agency (ANAC), the aircraft is in good standing for private flights, with a valid Airworthiness Verification Certificate (CVA) until August 26, 2027.
According to RAB, the aircraft belongs to a company controlled by Banco Safra, but is operated by Grupo Adubos Real.
In a statement, the Brazilian Air Force (FAB), through the Center for Investigation and Prevention of Aeronautical Accidents (Cenipa), reported that it has activated investigators to carry out the initial action regarding the incident involving the twin-engine aircraft with registration PP-ADU.
"At this stage, elements are gathered that will support the subsequent phases of the investigation, which aim to identify possible contributing factors and, where applicable, allow the issuance of safety recommendations aimed at preventing new occurrences," the agency added.
4 found dead in submerged plane after crash near Seldovia Airport
By Chris Aadland
Alaska State Troopers say four people died Wednesday in the crash of a small plane into a slough in the Kenai Peninsula community of Seldovia.
The Piper PA-24 inbound from Merrill Field Airport in
Anchorage crashed in the waters of Seldovia Slough just after 1:15 p.m., troopers said in an online statement.
The plane crashed near Seldovia’s airport and was submerged in 13 to 17 feet of water, according to Clint Johnson, Alaska region chief for the National Transportation Safety Board. Troopers said they received a report of the crash at 1:18 p.m.
People at the scene tried to reach the plane and rescue anyone inside but could not reach the aircraft, Johnson said.
Troopers had arrived at the crash site as of about 4:30 p.m., said Austin McDaniel, spokesman for the state Department of Public Safety. Alaska State Troopers and Wildlife Troopers from Anchor Point responded on a patrol vessel and the agency dispatched a helicopter from Anchorage.
At approximately 6:30 p.m., after the tide level dropped, troopers said they were able to extract the four bodies from inside the plane.
The State Medical Examiner Office will conduct an autopsy.
The NTSB is investigating the cause of the crash.
https://www.adn.com/alaska-news/aviation/2026/08/26/rescue-underway-after-plane-crashes-into-water-near-seldovia/
NTSB Final Report: PPHU Ekolot KR-030 Topaz
The Pilot Did Not Maintain Clearance To The Terrain While Maneuvering Near The Airport
Location: Platteville, Wisconsin Accident Number: CEN25LA149
Date & Time: April 8, 2025, 12:53 Local Registration: N568RD
Aircraft: PPHU Ekolot KR-030 Topaz Aircraft Damage: Substantial
Defining Event: Unknown or undetermined Injuries: 1 Serious
Flight Conducted Under: Part 91: General aviation - Personal
Analysis: Airplane position data revealed that, after takeoff, the pilot maneuvered within a 4-mile radius of the airport at varying altitudes up to about 2,000 ft mean sea level (msl). Shortly before the accident, the pilot executed a low pass or a touch-and-go and then entered a left turn, climbing the airplane to an altitude of about 1,100 ft msl while turning to a southerly course. The final data point was recorded about 30 seconds later and was located 0.15 miles west of the airport, coincident with the accident site. The ground impact marks relative to the accident site were consistent with a southeasterly course at the time of impact.
The position data indicated that the airplane course and groundspeed were about 137° and 78 kts at the end of the data. The recorded surface wind at the airport was from the west (250°) at 7 kts. Accordingly, the corresponding airplane airspeed was about 75 kts. The data did not point to an aerodynamic stall immediately preceding the impact.
A postrecovery examination of the airframe and engine did not reveal any anomalies consistent with an inflight failure or malfunction. Data recovered from the onboard engine control unit was consistent with a normally running engine responding to the pilot’s throttle control inputs. From takeoff until the end of the recorded data, each of the engine parameters remained within the specified limitations.
The pilot did not recall any aspects of the accident sequence. Based on the available information, the pilot did not maintain clearance to the terrain while maneuvering near the airport. The reason for not maintaining clearance from terrain could not be determined.
Probable Cause and Findings: The National Transportation Safety Board determines the probable cause(s) of this accident to be -- The pilot’s failure to maintain clearance from terrain for reasons which could not be determined.
FMI:Â www.ntsb.gov
Today in History
20 Years ago today:Â On 27 August 2006 Delta Connection flight 5191, a Canadair Regional Jet CRJ-100, operated by Comair crashed during takeoff from the wrong runway at Lexington-Blue Grass Airport, Kentucky, USA, killing 49 occupants; 1 survived the accident.
| Date: | Sunday 27 August 2006 |
| Time: | 06:07 |
| Type: | Canadair CL-600-2B19 Regional Jet CRJ-100ER |
| Owner/operator: | Delta Connection, opb Comair |
| Registration: | N431CA |
| MSN: | 7472 |
| Year of manufacture: | 2001 |
| Total airframe hrs: | 12048 hours |
| Cycles: | 14536 flights |
| Engine model: | General Electric CF34-3A1 |
| Fatalities: | Fatalities: 49 / Occupants: 50 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed, written off |
| Category: | Accident |
| Location: | Lexington-Blue Grass Airport, KY (LEX) -Â Â Â Â United States of America |
| Phase: | Take off |
| Nature: | Passenger - Scheduled |
| Departure airport: | Lexington-Blue Grass Airport, KY (LEX/KLEX) |
| Destination airport: | Atlanta Hartsfield-Jackson International Airport, GA (ATL/KATL) |
| Investigating agency:Â | NTSB |
| Confidence Rating: | Â Accident investigation report completed and information captured |
Narrative:
Delta Connection flight 5191, a Canadair Regional Jet
CRJ-100, operated by Comair crashed during takeoff from the wrong runway at Lexington-Blue Grass Airport, Kentucky,. USA, killing 49 occupants; 1 survived the accident.
Comair Flight 5191 was a regularly scheduled flight bound for Atlanta's Hartsfield-Jackson Atlanta International Airport (ATL), Atlanta, Georgia. Weather conditions at the time of the accident were 8 miles visibility, broken clouds at 5,000 feet, and no precipitation. Sunrise was at 7:03 AM, approximately one hour following the accident.
At 05:48 the CVR recorded automatic terminal information service (ATIS) information "alpha" which indicated that runway 22 was in use. About one minute later, the first officer told the air traffic controller that he had received the ATIS information. Two minutes later, the controller provided the crew of Flight 5191 departure information for their planned flight to Atlanta. At 5:52 a discussion among the flight crew was recorded on the CVR concerning which pilot would fly the airplane to Atlanta. It was decided that the first officer would be the flying pilot.
At 05:56, the captain stated, "Comair standard," which was determined to be part of the taxi briefing, and "Run the checklist at your leisure." At about 5:56, the first officer began the takeoff briefing, which is part of the before-starting-engines checklist. During the briefing he stated, "He said what runway...two four?" to which the captain replied, "It's two two." The first officer continued the takeoff briefing, which included three additional references to runway 22. After briefing that the runway end identifier lights were out, the first officer commented, "...Came in the other night it was like...lights are out all over the place." Investigators believed that what the first officer was referring to was on the previous day during a repositioning flight that landed on runway 22 at about 01:40 AM, the right runway edge lights after the intersection of runway 26 were out at the time.
Following the comment regarding the inoperative lighting, the first officer then stated, "Let's take it out and...take...(taxiway) Alpha. Two two's a short taxi." The captain called the takeoff briefing complete at about 05:57. At 05:58 the first officer called for the first two items on the before-starting-engines checklist, to which the captain commented that the before-starting-engine checklist had already been completed. The first officer questioned, "We did?" The first officer then briefed the takeoff decision speed (V1) as 137 kts and the rotation speed (VR) as 142 kts.
Flight data recorder (FDR) data for the accident flight started at about 05:58. FDR data showed that the pilot's heading bug on the multi function display (MFD) had been properly set to 227 degrees, which corresponded to the magnetic heading for runway 22.
At 05:59, the captain stated that the airplane was ready to
push back from the gate. FDR data showed that at about 6:00 they started the left and right engines. At 06:02 the first officer notified the controller that the airplane was ready to taxi. The controller then instructed the flight crew to taxi the airplane to runway 22. This instruction at that time authorized the airplane to cross runway 26 (the intersecting runway) without stopping. The first officer responded, "Taxi two two." FDR data showed that the captain began to taxi the airplane at about 06:02. About the same time, a Sky West Flight 6819 departed runway 22, which would have been parallel to their taxi route at that time.
At this point, the captain called for the taxi checklist. Beginning at about 06:03, the first officer stated, "Radar terrain displays" and "Taxi checks complete." At about 06:04 another commercial transport airplane, American Eagle Flight 882, departed runway 22.
From about 06:03 to 06:04, investigators determined that the flight crew engaged in conversation that was not pertinent to the operation of the flight. At about 06:04 the first officer began the before-takeoff checklist and indicated again that the flight would be departing from runway 22.
At about 06:04, the report indicated that the captain stopped the airplane at the hold-short line for runway 26. To get to the hold-short line for runway 22, (their assigned runway) they should have crossed the end of runway 26 and continued on the connecting taxiway. Afterward, the first officer made an announcement over the public address system to welcome the passengers and completed the before-takeoff checklist. At about 06:05, while the airplane was still at the hold-short line for runway 26, the first officer told the controller that, "Comair one twenty one" was ready to depart. Three seconds later the controller responded, "Comair one ninety one...fly runway heading. Cleared for takeoff." At 6:05, the captain began to taxi the airplane across the runway 26 hold short line. CVR recording showed that the captain called for the lineup checklist at the same time. About one second later, Comair Flight 5191 began turning onto runway 26. About 06:05, the first officer called the lineup checklist complete.
At about 6:06, the captain told the first officer, "All yours," and the first officer acknowledged, "My brakes, my controls." FDR data showed that the magnetic heading of the airplane at that time was about 266 degrees, which corresponded to the magnetic heading for runway 26. At that point, the CVR recorded the sound of engines increasing in power. The first officer then stated, "Set thrust please." to which the captain responded, "Thrust set." Shortly after this response from the captain, the first officer stated, "(that) is weird with no lights," and the captain responded, "Yeah," two seconds later.
Approximately eight seconds later, the captain called,
"One hundred knots," to which the first officer replied, "Checks." Approximately seven seconds later the captain called, "V-one, rotate," and then stated, "Whoa!" Investigators determined that the callout for V1 was six knots early, and the callout for VR was 11 knots early. It was also believed that the captain may have been reacting to seeing the end of the runway rapidly approaching.
The airplane impacted an earthen berm 265 feet beyond the end of runway 26, became temporarily airborne, then struck trees and burst into flames. Maximum airspeed recorded was 137 knots. The FDR ended at 06:06:36.
PROBABLE CAUSE: "The flight crew's failure to use available cues and aids to identify the airplane's location on the airport surface during taxi and their failure to cross check and verify that the airplane was on the correct runway before takeoff. Contributing to this accident were the flight crew's nonpertinent conversation during taxi, which resulted in loss of positional awareness and the Federal Aviation Administration's failure to require that all runway crossings be authorized only by specific air traffic control clearances."
