We start the week with the following stories...
Of note, a couple of stories regarding personal device batteries that lit off while aircraft were in flight...
Be safe out there!
Tom
--
Power bank bursts into flames on Delhi-Chennai IndiGo flight, sparks panic
Passengers scramble to douse flames before crew extinguishes blaze; flight diverted
Stephen N R, Senior Associate Editor
Dubai: Dramatic scenes unfolded aboard an IndiGo flight from Delhi to Chennai after a power bank reportedly caught fire inside an overhead luggage compartment, forcing the aircraft to make an emergency diversion to Hyderabad. 
A video recorded by a passenger shows flames and an orange glow spreading through the overhead compartment as alarmed travellers scramble to contain the blaze.
Several passengers can be seen attempting to put out the fire by repeatedly dabbing at the burning area with their bags.
Cabin crew eventually extinguished the flames using onboard fire extinguishers, according to reports.
The aircraft was diverted to Hyderabad, where it landed safely. All passengers and crew members were reported safe.
The incident has once again raised concerns about the risks posed by lithium-ion batteries carried aboard commercial aircraft.
Video captures frightening moments
The passenger-recorded footage shows people standing in the aisle and reaching towards the overhead compartment as the fire burns above the seats.
The incident reportedly began when a malfunctioning power bank caught fire inside the luggage bin.
Although the flames were brought under control, the crew diverted the flight to Hyderabad as a precaution.
No injuries were reported.
Why power banks pose a fire risk
Power banks generally contain lithium-ion batteries, which can overheat if damaged, defective or subjected to an internal electrical fault.
In rare cases, this can trigger a process known as thermal runaway, in which a battery rapidly generates heat and may release smoke, flames or flammable gases.
Such fires are particularly concerning aboard aircraft because they can develop rapidly in confined spaces.
Aviation safety rules generally require passengers to carry power banks in cabin baggage rather than checked luggage, allowing crew members to respond quickly if a battery overheats.
Passengers are also advised to alert cabin crew immediately if a device becomes unusually hot, begins smoking or catches fire.
Similar incidents aboard aircraft
The IndiGo incident follows other cases in which portable batteries have caused fires during flights.
In March 2025, a Hong Kong Airlines flight travelling from Hangzhou to Hong Kong was diverted to Fuzhou after a power bank caught fire in an overhead luggage compartment.
Video footage showed flames emerging from the compartment as passengers and crew responded to the emergency. The aircraft landed safely.
In July 2025, a Virgin Australia flight also experienced an overhead locker fire involving a passenger's power bank. Cabin crew extinguished the blaze before the aircraft landed safely in Hobart.
The incidents highlight the importance of proper battery storage and prompt action by cabin crew when smoke or flames are detected.
While lithium-ion battery fires remain relatively uncommon compared with the number of devices carried on flights every day, aviation authorities continue to warn passengers about the potential risks of damaged or defective batteries.
https://gulfnews.com/world/asia/india/video-power-bank-bursts-into-flames-on-delhi-chennai-indigo-flight-sparks-panic-1.500706479
Power bank fire on Jeju Air flight from Cheongju to Jeju
KBS
An incident believed to have been caused by a portable battery ignition occurred on a Jeju Air aircraft just before takeoff from Cheongju Airport bound for Jeju. Fortunately, there were no casualties.According to passengers and Jeju Air officials, smoke was observed on Jeju Air Flight 7C227, which was scheduled to depart Cheongju for Jeju at 7:15 PM today (the 10th). 
A passenger told KBS in a phone call, "The interior of the plane suddenly filled with thick smoke," adding that "the flight was nearly full."
The aircraft was about to leave the tarmac after completing passenger boarding and closing the doors. It is
reported that as smoke began to rise from a portable battery owned by a passenger, people nearby immediately used clothing and other items to extinguish the fire, after which flight crew members took safety measures.
A Jeju Air official stated, "The passenger was holding a portable battery, and it appears the fire started from there," adding, "We are currently verifying the type of battery that ignited."
All 168 passengers on board have disembarked and are currently waiting at the airport's departure area.
Jeju Air stated that it is "currently verifying" whether alternative flights have been arranged.
Previously, on the 24th of last month, the first day of the Chuseok holiday, a fire believed to have been caused by a portable battery broke out on an Air Seoul passenger plane departing from Incheon Airport for Da Nang, Vietnam, before takeoff.
At that time as well, smoke was seen rising from a bag stored under a passenger's seat, which soon escalated into a fire, which flight attendants extinguished using bottled water and other items.
Single-engine airplane crashes in Flint, none injured
By Dave Herndon
FLINT, MI (FOX 2) - A single-engine aircraft crashed along the highway this afternoon when that engine failed. 
According to Flint Township Police, the aircraft had only the pilot onboard, and they were not injured in the crash. The small craft was descending towards Bishop Airport when a mechanical failure caused the engine to stop.
The pilot landed the plane along the shoulder of I-69, near I-75. No other vehicles were damaged.
Flint Township police investigators are working with the FAA and authorities at Bishop Airport to investigate the cause of the engine failure.
https://www.fox2detroit.com/news/single-engine-airplane-crashes-flint-none-injured
One Injured In Plane Crash
Kelly Hertz/P&D
Emergency crews were called to a single-engine plane crash late Friday afternoon west of Yankton. 
According to Yankton County Sheriff Preston Crissey, the pilot was attempting an emergency landing in a bean field south of S.D. Highway 50 near Highway 314.
There were two occupants in the plane, and there were no fatalities. One person was taken to the hospital with non-life-threatening injuries, according to Crissey, saying it’s the “best possible outcome” when his office gets called to a plane crash.
The site will be secured by the Sheriff’s office until the Federal Aviation Administration and the National Transportation Safety Board arrive to investigate.
The Yankton County Emergency Medical Services, Yankton County Emergency Management and the Yankton Fire Department all assisted the Sheriff’s office at the incident.
https://www.yankton.net/community/image_c79d8cc6-4f6d-4211-afdf-98bdfbdb6cbb.html
Two people dead after small plane crashes near Fergus, Ont.
By Jennifer K. Baker and Hannah Schmidt
Two people are dead after a small plane crashed into a field and caught fire near Fergus, Ont., on Friday morning.
Ontario Provincial Police (OPP) said the aircraft went
down near the intersection of Beatty Line and Wellington Road 17, between Fergus and Arthur, shortly after 10 a.m.
Both people aboard the plane were pronounced dead at the scene. Police said there were no other reported injuries.
The Transportation Safety Board of Canada (TSB) identified the aircraft as an amateur-built Skybolt biplane.
In an update Saturday, the TSB said the aircraft departed Fergus (Juergensen Field) Airport at about 10 a.m. for a local aerobatic training flight with two experienced pilots on board.
The aircraft crashed into a cornfield about two kilometres north of the airfield and came to rest upside down, the TSB said.
Emergency crews extinguished the fire, and multiple OPP units, including urban search and rescue, hazardous-materials specialists and tactical emergency medical services, responded to the scene.
Police said OPP resources had cleared the area shortly after noon Saturday.
The TSB said investigators will continue gathering and analysing information in the coming weeks.
The cause of the crash has not been released.
NTSB Releases Preliminary Report On NBC News Helicopter Accident
Helicopter Was Covering California Bus Accident At The Time
The National Transportation Safety Board released a preliminary report on Tuesday on the fatal NBC Los Angeles news helicopter accident in Chatsworth, Calif.
Three people died in the incident on Sept. 15, including aerial news reporter Eliana Moreno, pilot George Marciniw and 29-year-old Edy Guitierrez Mejia.
The NTSB said that the helicopter, an Airbus Helicopters (formerly Eurocopter) AS-350 B2 had departed the Whiteman Airport in Los Angeles and flew to Chatsworth to gather video footage of a recent fatal bus accident.
The preliminary report says that ADS-B data show that the helicopter was in the vicinity of the bus accident for about an hour and 24 minutes.
The NTSB reviewed a four-minute and twenty-one-second-long video recording that was taken by Moreno. Officials say the video captured ambient helicopter noise of the main rotor and engine. The NTSB explained that the noise was "consistent with normal operations."
During the last minute of flight, the helicopter was about 800 feet above ground, and it decelerated to about 6 knots ground speed.
During the last 29 seconds of the flight, Moreno's recording captured the helicopter noise as it changed frequency. Officials say it also captured intermittent and continuous horns, "consistent with the helicopter's main rotor high rpm, low rotor rpm and other aural advisories."
At about 6:55 p.m., data show that the helicopter began a rapid descent while turning right. NTSB officials say the last data point captured the helicopter at a high rate of descent, going about 38 knots groundspeed directly above the accident site.
The NTSB reviewed security footage from multiple nearby buildings that recorded the helicopter's final moments before it hit a metal storage container on the ground and burst into flames.
The preliminary report did not provide details on the cause. A final report is still pending.
FMI: www.ntsb.gov
NTSB Prelim: Robinson Helicopter Company R44 II
The Engine Lost Partial Power And The Helicopter Settled Into The Terrain Resulting In A Hard Landing
Location: Colquitt, GA Accident Number: ANC26LA103
Date & Time: September 11, 2026, 08:30 Local Registration: N4026E
Aircraft: Robinson Helicopter Company R44 II Injuries: 1 None
Flight Conducted Under: Part 137: Agricultural
On September 11, 2026 about 0830 eastern daylight time, a Robinson R44 helicopter, N4026E, was substantially damaged when it was involved in an accident near Colquitt, Georgia. The pilot was not injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 137 agricultural flight.
According to the pilot, he completed a preflight inspection and engine run-up of the helicopter and found no anomalies. He verified all gauges were in the green and hovered the helicopter over to a trailer and landed on the trailer. Ground personnel added five gallons of fuel and loaded 50 lbs of liquid to the helicopter while the helicopter remained running. The ground personnel unhooked all the hoses from the helicopter and gave the pilot a signal it was safe to depart from the trailer.
The pilot lifted the helicopter to a hover over the trailer and verified all gauges were still in the green. The pilot pushed forward on the cyclic to depart from the trailer, as the helicopter began to move forward, he felt a jolt and heard and felt the engine “skipping.” Subsequently the engine lost partial power and the helicopter settled into the terrain resulting in a hard landing. The helicopter sustained substantial damage to the tail boom, tail rotor gear box, and tail rotor blades.
A detailed wreckage examination is pending.
FMI: www.ntsb.gov
Postaccident Examination Revealed That The Left Inboard Leading-Edge PegaSTOL Slat Was Separated And Not Found Within The Vicinity Of The Main Wreckage
Location: Neosho, MO Accident Number: CEN26FA311
Date & Time: September 7, 2026, 13:37 Local Registration: N101XV
Aircraft: EXP STOL CH701 Injuries: 2 Fatal
Flight Conducted Under: Part 91: General aviation - Personal
On September 7, 2026, about 1337 central daylight time, an experimental STOL CH701 airplane, N101XV, sustained substantial damage when it was involved in an accident near Neosho, Missouri. The pilot and passenger sustained fatal injuries. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight.
According to a friend, the pilot had flown to the Neosho Hugh Robinson Airport (EOS), Neosho, Missouri, to assist him with some airplane maintenance. The maintenance consisted of temporarily removing and installing the accident airplane airspeed indicator into another airplane to allow for a ferry flight. After that ferry flight, the airspeed indicator was reinstalled and “tested” in the accident airplane. The pilot departed in the accident airplane with another friend about 1334.
A witness reported that the airplane departed EOS with no issues observed during the takeoff or initial climb. After he observed the initial climb, he got back into his vehicle and did not observe any further portion of the flight.
At 1335:39, a dash camera video recording, positioned about 0.80 nautical miles east of the airport, captured the airplane on the left crosswind for runway 19. The airplane tracked west to east before starting a left turn toward the northwest at about 1335:47. At 1335:50, the recording showed an unknown object departing and falling away from the airplane. The airplane continued the left turn and entered a nose down descent before disappearing behind a tree line.
The accident site was located in an open field about 0.48 nautical miles east of the departure end of runway 19. Impact ground scars and debris were consistent with the airplane impacting terrain in a nearly vertical nose down attitude.
Postaccident examination revealed that the left inboard leading-edge PegaSTOL slat was separated and not found within the vicinity of the main wreckage. The PegaSTOL wing slat system is manufactured by Dédalius Aviation Inc. A couple of days after the accident, the leading-edge slat was found by law enforcement about 0.14 nautical miles southwest of the accident site.
The airplane was retained for further examination.
FMI: www.ntsb.gov
Today in History
50 Years ago today: On 12 October 1976 Indian Airlines flight 171, a Caravelle, crashed near Bombay, India, following an uncontained engine failure and subsequent fire, killing all 95 occupants
| Date: | Tuesday 12 October 1976 |
| Time: | 01:35 |
| Type: | Sud Aviation SE-210 Caravelle VI-N |
| Owner/operator: | Indian Airlines |
| Registration: | VT-DWN |
| MSN: | 231 |
| Year of manufacture: | 1967 |
| Fatalities: | Fatalities: 95 / Occupants: 95 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed, written off |
| Category: | Accident |
| Location: | Bombay-Santacruz Airport (BOM) - India |
| Phase: | Approach |
| Nature: | Passenger - Scheduled |
| Departure airport: | Bombay-Santacruz Airport (BOM/VABB) |
| Destination airport: | Madras Airport (MAA/VOMM) |
| Confidence Rating: | Information is only available from news, social media or unofficial sources |
Narrative:
Indian Airlines flight 171, a Caravelle, crashed near Bombay, India, following an uncontained engine failure and subsequent fire, killing all 95 occupants
A no. 2 engine failure after takeoff from runway 27 forced the crew to return to Mumbai (Bombay). A fire erupted in the no. 2 engine area, reaching the hydraulic reservoir (located aft of the pressure bulkhead), draining it of all but accumulated pressure.
Pitch control was lost while on approach to runway 09; the aircraft crashed 45-deg. nose down into the ground from a height of 300 feet, 1000 feet short of the runway.
PROBABLE CAUSE: 10th Stage compressor disc failure; fuel lines were severed by debris, causing a fire in the no.2 engine area. The fire spread because the crew didn't shut off the fuel supply.
Today in History
50 Years ago today: On 12 October 1976 Indian Airlines flight 171, a Caravelle, crashed near Bombay, India, following an uncontained engine failure and subsequent fire, killing all 95 occupants
| Date: | Tuesday 12 October 1976 |
| Time: | 01:35 |
| Type: | Sud Aviation SE-210 Caravelle VI-N |
| Owner/operator: | Indian Airlines |
| Registration: | VT-DWN |
| MSN: | 231 |
| Year of manufacture: | 1967 |
| Fatalities: | Fatalities: 95 / Occupants: 95 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed, written off |
| Category: | Accident |
| Location: | Bombay-Santacruz Airport (BOM) - India |
| Phase: | Approach |
| Nature: | Passenger - Scheduled |
| Departure airport: | Bombay-Santacruz Airport (BOM/VABB) |
| Destination airport: | Madras Airport (MAA/VOMM) |
| Confidence Rating: | Information is only available from news, social media or unofficial sources |
Narrative:
Indian Airlines flight 171, a Caravelle, crashed near Bombay, India, following an uncontained engine failure and subsequent fire, killing all 95 occupants
A no. 2 engine failure after takeoff from runway 27 forced the crew to return to Mumbai (Bombay). A fire erupted in the no. 2 engine area, reaching the hydraulic reservoir (located aft of the pressure bulkhead), draining it of all but accumulated pressure.
Pitch control was lost while on approach to runway 09; the aircraft crashed 45-deg. nose down into the ground from a height of 300 feet, 1000 feet short of the runway.
PROBABLE CAUSE: 10th Stage compressor disc failure; fuel lines were severed by debris, causing a fire in the no.2 engine area. The fire spread because the crew didn't shut off the fuel supply.