Here are the stories to start the new week...
Be safe out there!
Tom
--
Thought this is it: Laptop catches fire on US flight; 4-5 passengers burned
A laptop battery caught fire on American Airlines Flight 2398 as it approached Dallas, burning passengers' hands. The crew contained the device, but the incident adds to ongoing concern over lithium-ion battery risks onboard.
Written By: Ritaban Misra
An American Airlines passenger was treated for burns after a laptop battery caught fire aboard a flight from Atlanta to Dallas on Friday, with the pilot reporting that four to five passengers may have been injured.
American Airlines Flight 2398, an Airbus A321 carrying around 133 people, landed safely at Dallas-Fort Worth International Airport at about 6:55 pm local time, according to the Federal Aviation Administration (FAA), as reported by The Independent. 
Flight attendants contained the fire using a thermal containment bag, while emergency crews were waiting for the aircraft when it landed. A spokesperson for Dallas-Fort Worth International Airport said one patient was treated and released.
“American Airlines Flight 2398 landed safely at DFW after reports of smoke from a customer’s device during landing,” the airline told The Independent, praising the crew for quickly containing the device.
A passenger on the flight told ABC News that the smoke filled the cabin as flight attendants worked to extinguish the flames and assist passengers who had suffered burns.
Another passenger mentioned that she wasn't having 'very positive thoughts' during the fire. "I thought this is it. It was definitely very scary," she mentioned.
PILOT REPORTS PASSENGERS SUFFERS BURNS
Air traffic control audio obtained by CBS Texas captured the pilot reporting that a laptop had caught fire inside the aircraft.
The pilot said around four to five passengers had been burned by the laptop and indicated that the device had been contained in the middle section of the aircraft. He also said the passengers had suffered burns to their hands.
The extent of injuries to the other passengers was not immediately clear.
FAA RECORDS LITHIUM BATTERY INCIDENTS
Lithium-ion batteries are widely used in electronic devices including laptops, mobile phones, charging cases and portable power banks.
According to FAA data, 58 incidents involving lithium batteries that resulted in smoke, fire or other dangerous events have been recorded on passenger aircraft so far in 2026.
The FAA warns that lithium-ion batteries can overheat and undergo a process known as thermal runaway. According to the agency, this can occur without warning if a battery is damaged, overheated, exposed to water, overcharged or improperly packed. Manufacturing defects can also cause thermal runaway.
The incident aboard Flight 2398 comes amid continuing aviation safety concerns surrounding lithium-ion batteries, which can generate intense heat and smoke when they enter thermal runaway.
Airlines and flight crews use specialised procedures and containment equipment to manage such incidents when they occur onboard.
Small plane crash-lands in water off Boca Raton beach; lone pilot escapes without injury
A small-engine plane crash-landed in the water off Boca Raton Saturday, with the sole occupant escaping on her own before being taken to the hospital as a precaution.
By: Cassandra Garcia , Emma Romano
BOCA RATON, Fla. — A small-engine plane crash-landed in the water off Boca Raton Saturday, drawing stunned reactions from beachgoers and boaters who watched the scene unfold near South Beach Park at 250 South Ocean Blvd. 
Boca Raton Fire Rescue said only one woman was aboard the aircraft. She was able to exit the plane on her own. Lifeguards brought her to shore, where she was taken to the hospital as a precaution. No injuries were reported.
Brett Goorland, a tourist who had been snorkeling at nearby Red Reef Park, said he had a close-up view of the plane's final moments in the air.
"We looked down there was a school of snook, looked up, a plane came over us about 10 feet over us," Goorland said. "Bizarre site for sure."
Michael Arizzi and his wife were on a boat nearby when they noticed something was wrong. Arizzi said he works in aviation and has experience with aircraft maintenance.
"The plane got lower in front of Palmetto. I'm like wow that's really risky, before I noticed the plane go into a glide path," Arizzi said. "At first you go, oh it's not an emergency, it's not an emergency, and then all of a sudden the plane hits the water."
Arizzi credited the pilot for the safe outcome.
"That's kind of a flawless move for a pilot, is 'hey let me land in the water off the beach where there's lifeguards to help,' so that was an excellent move on the pilot and doing so in which it didn't put the public at risk," Arizzi said.
The plane remained in the water Saturday and is expected to stay until it is retrieved Sunday.
It is still unclear why the plane was forced to make an emergency landing on the water. Boca Raton Police said the FAA has taken over the investigation. The Coast Guard and Boca Raton Police are watching over the aircraft until it is removed.
https://www.wptv.com/news/region-c-palm-beach-county/lantana/plane-crashes-into-ocean-near-lantana-beach-no-injuries-reported
Small Aircraft Downed at Brenham Municipal Airport
Jason May jason@southtexasnews.com
BRENHAM — Emergency crews responded to a single-plane crash at the Brenham Municipal Airport after an aircraft crashed during an "operational incident."
According to official statements from the City of 
Brenham, two occupants were aboard the plane. Both individuals were transported by Washington County EMS with minor injuries, though local flight organization Brenham AeroTech noted in a statement that both occupants are safe.
Emergency responders arrived quickly at the scene, including personnel from the Texas Department of Public Safety (DPS), the Brenham Fire Department, Meyersville FD, Chappell Hill FD, Salem FD, city airport staff, and HAZMAT teams. Eye-witnesses reported unusual activity prior to the response, with one local resident noting on social media that she observed an aircraft around 8 a.m. flying low and appearing to experience issues.
Investigations into the cause of the crash are currently underway. DPS is leading the active ground investigation on site, while the Federal Aviation Administration (FAA) has been notified to conduct an inquiry into the circumstances surrounding the flight. Brenham AeroTech expressed gratitude for the prompt response of first responders and municipal staff, declining further comment while official investigations proceed.
https://kdhnews.com/news/texas/small-aircraft-downed-at-brenham-municipal-airport/article_8d64dfdb-d813-50b9-a764-430fb50ae7f6.html
Sheriff: Georgia airport closed following takeoff incident
Graham Cawthon
Two people escaped injury Friday afternoon when a small airplane skidded off a runway at a Georgia airport.
The accident happened around 2:30 p.m. at the Thomaston-Upson Airport on Delray Road, according to Sheriff Dan Kilgore. 
Takeoff attempt falls short
According to preliminary information, the 1977 Piper Lance PA-32R was traveling from Cherokee County, Georgia, to Sebastian, Florida. The plane had stopped in Upson County to refuel before continuing south.
The pilot told authorities he retracted the landing gear during takeoff but then realized the aircraft was not gaining enough lift to clear the end of the runway. He attempted to lower the landing gear again, but it did not deploy in time.
The plane landed on its underside, skidded along the runway and struck an antenna after running off the north end near Rocky Bottom Road. The aircraft’s propeller also was damaged in the accident.
FAA investigating
The Federal Aviation Administration was contacted, and investigators were responding to determine what caused the accident.
The Thomaston-Upson Airport will remain closed until further notice, Kilgore said.
https://www.wjcl.com/article/georgia-airport-runway-skid-faa-investigates/73497996
NTSB Prelim: Vans RV-4
One Video Showed The Airplane Departing Runway 17 And Then Initiating A Turn Back To The Airport
Location: Yuba City, CA Accident Number: WPR26FA262
Date & Time: July 16, 2026, 07:01 Local Registration: N98GB
Aircraft: Vans RV-4 Injuries: 1 Fatal
Flight Conducted Under: Part 91: General aviation - Personal
On July 16, 2026, at 0701 Pacific daylight time, an experimental amateur built Vans RV-4, N98GB, was substantially damaged when it was involved in an accident near Yuba City, California. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
A review of recorded video from the Sutter County Airport, Yuba City, California, and a neighboring business, captured the airplane at various portions of the accident flight. One video showed the airplane departing runway 17 and then initiating a turn back to the airport. The airplane overshot runway 35 and traveled out of the frame of the camera. As the airplane traveled into view of a neighboring business’s video, it appeared the airplane was on the ground traveling in a northerly direction before it rotated along its vertical axis to the left about 270° and came to rest upright in an open field.
The airplane’s first identified point of contact (FIPC) was the airport’s northern perimeter chain link fence. The debris field was about 230 ft in length, oriented on a 348° heading and consisted of portions of wooden propeller blades and the rudder. The airplane came to rest upright on a 056° heading and remained mostly intact. Flight control continuity was established from the cockpit to all the flight control surfaces.
The airplane was recovered to a secure location for further examination.
FMI: www.ntsb.gov
NTSB Final Report: Cirrus Design Corp SR22
As The Airplane Bounced, The Pilot Increased Engine Power To Go Around, Then Lost Control
Location: Lakeway, Texas Accident Number: CEN24LA367
Date & Time: September 25, 2024, 18:33 Local Registration: N565CP
Aircraft: Cirrus Design Corp SR22 Aircraft Damage: Substantial
Defining Event: Aerodynamic stall/spin Injuries: 1 Serious, 1 Minor
Flight Conducted Under: Part 91: General aviation - Personal
Analysis: During descent to the destination airport, the pilot confirmed that the closest weather station reported the wind from 030° at 10 knots, gusting to 16 knots, so he planned to land on runway 34. While on the base leg of the traffic pattern, he extended the flaps to 100%, reduced the engine power, and slowed to 85 knots indicated airspeed (KIAS). While on final approach and after clearing a set of powerlines that were perpendicular to the runway, he made a steep approach to the runway. As the airplane was above the displaced threshold, the airspeed decreased to about 63 KIAS, entered an aerodynamic stall, and landed hard on the runway. As the airplane bounced, the pilot increased engine power to go around, then lost control, veered off the left side of the runway and impacted a tree and terrain. The airplane sustained substantial damage to the fuselage, wings, and engine mount.
Postaccident examination of the runway revealed three distinct gouges where the landing gear impacted during the hard, bounced landing. The pilot reported that there were no preaccident mechanical malfunctions or failures that would have precluded normal operation.
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 adequate airspeed during landing, which resulted in an aerodynamic stall and loss of control during a go-around.
FMI: www.ntsb.gov
NTSB Prelim: Zenith Zodiak 601
(Nearby Pilot) Reported That Conditions Were Worse Than Forecast, And He Had To Divert To Avoid Instrument Meteorological Conditions
Location: Sioux City, IA Accident Number: CEN26FA267
Date & Time: July 24, 2026, 14:22 Local Registration: N27601
Aircraft: Zenith Zodiak 601 HDS Injuries: 1 Fatal
Flight Conducted Under: Part 91: General aviation - Personal
On July 24, 2026, about 1422 central daylight time, a Zenith Zodiac 601HDS experimental airplane, N27601, was destroyed when it was involved in an accident near Sioux City, Iowa. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
The multi-leg visual flight rules (VFR) cross country flight departed from the Wittman Regional Airport (KOSH), Oshkosh, Wisconsin, with a final destination in Colorado. At 1236 on the day of the accident, ADS-B data showed the airplane departed the Pocahontas Municipal Airport (KPOH), Pocahontas, Iowa, on a southwesterly flight track. Upon reaching the vicinity of Holstein, Iowa, the airplane then flew west parallelling U.S. Highway 20 in the direction of Sioux City, Iowa. About 3 miles short of the U.S. Highway 20/75 intersection, the airplane began to track to the northwest, eventually turned north, and began climbing.
After flying north, the airplane entered a right turn and descended until the last recorded data point which was located about a half mile southeast of the accident site. The airplane was found in about 6 to 8 feet of water in a man-made lake near the shoreline. The vegetation along the shoreline on the side of the accident site, as well as the bank opposite the accident site about 80 to100 feet away, was intact with no indication of having been struck by the accident airplane. The main wing spar remained intact along its length but from the main landing gear outward on both sides, the wing structure and wing skins showed aft crushing and had mostly separated from the spar. The fuselage was deformed 90° from the wing spar. The instrument panel, firewall, and engine separated from the front of the airplane and were located underneath and near the area the main wreckage came to rest. Upper engine cowling and windscreen fragments were scattered across the shoreline and a yard beyond the water.
Divers and a local towing company were able to remove the airplane from the water. The major components of the airplane were present. Flight control cable continuity was established for the ailerons, rudder, and elevators. A visual inspection of the engine did not reveal any signs of a catastrophic engine failure. The wreckage was moved to a secure location for further examination.
According to KPOH personnel, the pilot purchased 14.7 gallons of 100 low lead fuel before departing. At the accident site, fuel sheen was present on the water and oil was present in the water during the recovery of the engine.
The National Weather Service (NWS) Area Forecast Discussion issued by the Sioux Falls, South Dakota, Weather Forecast Office at 1209 on the day of the accident reported instrument flight rules (IFR) to marginal instrument flight rules (MVFR) conditions would slowly improve through midafternoon.
On the day of the accident around 1500, another pilot was flying west about 75 miles south of the accident pilot. He reported that conditions were worse than forecast, and he had to divert to avoid instrument meteorological conditions. He landed at an alternate airport and ended up driving home.
A review of FAA records showed the pilot held a private pilot certificate with a rating for airplane single engine land, but no instrument rating. The pilot, who was the airplane owner, built the airplane and he held a repairman experimental aircraft builder certificate for the airplane.
FMI: www.ntsb.gov
Today in History
18 Years ago today: On 24 August 2008 Iran Aseman Airlines flight IRC6895, a Boeing 737-200, crashed while returning to on approach to Bishkek-Manas International Airport, Kyrgyzstan, killing 65 occupants; 25 survived the accident.
| Date: | Sunday 24 August 2008 |
| Time: | 20:45 |
| Type: | Boeing 737-219 |
| Owner/operator: | Itek Air, opf Iran Aseman Airlines |
| Registration: | EX-009 |
| MSN: | 22088/676 |
| Year of manufacture: | 1980 |
| Total airframe hrs: | 60014 hours |
| Cycles: | 56196 flights |
| Engine model: | P&W JT8D-15 |
| Fatalities: | Fatalities: 65 / Occupants: 90 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed, written off |
| Category: | Accident |
| Location: | 7,8 km WNW of Bishkek-Manas International Airport (FRU) - Kyrgyzstan |
| Phase: | Approach |
| Nature: | Passenger - Scheduled |
| Departure airport: | Bishkek-Manas International Airport (FRU/UAFM) |
| Destination airport: | Tehran-Imam Khomeini International Airport (IKA/OIIE) |
| Investigating agency: | MAK |
| Confidence Rating: | Accident investigation report completed and information captured |
Narrative:
Iran Aseman Airlines flight IRC6895, a Boeing 737-200, crashed while returning to on approach to Bishkek-Manas International Airport, Kyrgyzstan, killing 65 occupants; 25 survived the accident.
Flight IRC6895 from Bishkek (FRU), Kyrgyzstan to Tehran (IKA), Iran was carried out by Itek Air. The Kyrgyz airline operated one of their Boeing 737-200 aircraft on the flight.
In the afternoon of August 24, from 16:30 to 20:00 local time, a thunderstorm with associated rain passed over Bishkek. Over that period the wind shifted from 220 degrees to 100 degrees at 20:30. Wind was blowing at about 6 kts, with wind variable at 23 knots. The temperature had dropped from 31 to 27 degrees C.
The weather then improved and at the time of departure visibility was more than 10 km with 6/8 clouds at an altitude of 5000 m (ca 16400 ft).
The Boeing 737 was cleared to taxy to runway 08 for departure. Take off was commenced at 20:30. The flight was cleared for a DW-1 departure, which entailed a left turn after takeoff to a heading of 240 degrees towards the RENAT beacon. From there it was to continue to the Chaldovar NDB, which should be crossed at or above FL158.
At 20:36:40, the airplane was climbing through an altitude of 3000 m (almost 10.000 feet). At that moment the cabin altitude alert horn probably sounded, because the crew reported problems with the cabin pressure.
The crew decided to return to Bishkek and requested a visual approach to runway 08. This was approved and the airplane made a right hand turn, for a straight-in approach to runway 08. At 20:41:40 the crew reported the runway in sight. About 20:42:30 the flight was 12 km from the runway, flying at 400 m above airfield elevation at an airspeed of 460 km/h (250 kts). At a distance of 5 km from landing, the airplane had decelerated to 340 km/h (185 kts), but it was not properly configured for landing. The flight crew then obtained permission to carry out a left-hand orbit in order to configure the plane for landing. A left hand turn was flown with a 30-degree bank.
In the process of the turn the aircraft descended further with the airspeed decreasing to 290 km/h (155 kts).
The airplane struck terrain some 7.5 km from the runway. At the time of impact the landing gear was down and flaps were selected down at 15 degrees.
The cause of the Itek Air B737-200 EX-009 accident during the air-turn back due to the cabin not pressurizing (probably caused by the jamming of the left forward door seal) was that the crew allowed the aircraft to descend at night to a lower than the minimum descent altitude for visual approach which resulted in the crash with damage to the aircraft followed by the fire and fatalities.
The combination of the following factors contributed to the accident:
- Deviations from the Boeing 737-200 SOP and PF/PM task sharing principles;
- Non-adherence to visual approach rules, as the crew did not keep visual contact with the runway and/or ground references and did not follow the prescribed procedures after they lost visual contact;
- Loss of altitude control during the missed approach (which was performed because the PIC incorrectly evaluated the aircraft position in comparison with the required descent flight path when he decided to perform visual straight-in approach);
- Non-adherence to the prescribed procedures after the TAWS warning was triggered.
