Two Planes Collide on Kalispell Runway, Sparking Massive Fireball

A Socata TBM 700 struck parked planes at Kalispell City Airport on August 11, 2025, at 2:08 p.m., creating a fireball. All four onboard survived; two sustained minor injuries. Firefighters contained the blaze quickly. FAA and NTSB are investigating; preliminary factual reporting is expected in 2–3 weeks.

VisaVerge.com
📋
Key takeaways
A Socata TBM 700 (2011) struck parked planes at Kalispell City Airport on August 11, 2025, at 2:08 p.m.
All four onboard exited unassisted; two treated for minor injuries and released; no fatalities reported.
FAA and NTSB opened investigations; preliminary report expected in about 2–3 weeks, final in 12–24 months.

(KALISPELL, MONTANA) Two planes collided at Kalispell City Airport (S27) on Monday afternoon, August 11, 2025, when a landing single‑engine aircraft struck parked planes and triggered a large fireball. All four people on the landing aircraft survived and only minor injuries were reported. The fire was contained within minutes. The Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) have opened an investigation and no cause has been assigned.

Officials said the incident happened at about 2:08 p.m. local time at the city‑owned general aviation field just south of downtown. The FAA identified the landing aircraft as a Socata TBM 700, a single‑engine turboprop built in 2011 and registered to Meter Sky LLC of Pullman, Washington. According to the NTSB, the flight originated in Pullman. The landing aircraft hit at least one unoccupied parked plane; videos shared by bystanders showed a towering fireball and thick smoke.

Two Planes Collide on Kalispell Runway, Sparking Massive Fireball
Two Planes Collide on Kalispell Runway, Sparking Massive Fireball

Four people were on board the TBM: the pilot and three passengers. All got out on their own. Two were treated at the airport for minor injuries and released. No one was inside the parked aircraft that burned. Kalispell Police and Fire confirmed a rapid multi‑agency response that included foam units to knock down flames on the planes and on grass beside the movement area.

Damage, response, and scene control

Kalispell Fire Chief Jay Hagen said both involved planes were total losses. The fire spread to multiple parked aircraft and into adjacent grass, but crews contained the flames within minutes. Evergreen, Smith Valley, and Whitefish fire units provided mutual aid.

⚠️ Important
Do not move or disturb damaged aircraft or debris until authorities release the scene; premature cleanup can compromise evidence, delay insurance payouts, and hinder the NTSB/FAA investigation.

By late afternoon, the scene was secure. Responders left by roughly 4:30–5:00 p.m., and aircraft on the ramp were moved back into place. No ongoing hazard was reported.

Early statements point to a loss of control during landing before the TBM struck parked aircraft. That description reflects the sequence of events, not a finding of cause. As of Tuesday, August 12, no fatalities had been reported, and the airport resumed normal operations after the cleanup. City officials asked tenants and pilots to expect routine notices and any short‑term checks of the affected areas.

“Multiple” planes caught fire, officials said; the exact number of damaged parked aircraft is not yet final.

What officials confirmed

  • Time and place: First 911 call at about 2:08 p.m. Monday at Kalispell City Airport (S27), a city‑owned general aviation field.
  • Aircraft: Socata TBM 700, 2011 model, owned by Meter Sky LLC (Pullman, WA).
  • People on board: 4 (pilot + 3 passengers). All exited unassisted.
  • Injuries: 2 minor injuries; both treated on scene and released. No fatalities.
  • Fire and damage: Impact ignited multiple parked airplanes and nearby grass, producing a large fireball. Both involved planes were total losses. Foam was used; fire contained within minutes.
  • Response and wrap‑up: Multi‑agency response cleared the scene by about 4:30–5:00 p.m. No ongoing hazard reported.
  • Investigation: FAA and NTSB have assumed the investigation; cause remains under review.

Flathead County Sheriff Brian Heino confirmed the emergency-call timeline and the combined response. The City of Kalispell said the incident site was quickly secured, and airport tenants could expect standard cleanup and coordination with investigators and insurers.

Investigation context and typical focus areas

A former FAA/NTSB investigator, Jeff Guzzetti, noted that collisions with parked aircraft happen a few times each year in general aviation. In cases like this, investigators typically focus on:

  • Approach stability
  • Landing rollout
  • Runway surface and conditions
  • Pilot workload and training/currency
  • Aircraft systems and maintenance history
  • Weather and meteorology

Guzzetti emphasized that investigators gather a wide set of facts before making any judgment on cause. None of these areas have been cited here, and no conclusions have been made.

Investigation steps and timeline

The FAA and NTSB typically follow a set process after an airport crash or serious incident:

  1. Secure the site and document wreckage and marks on the runway or ramp.
  2. Collect crew and witness statements and retrieve aircraft records.
  3. FAA posts an initial notice within days.
  4. NTSB often releases a preliminary report in about 2–3 weeks, providing factual information (flight origin, registry, sequence of events, weather, initial damage assessment). It does not analyze cause.
  5. A full factual docket may include performance data, operations records, maintenance history, and meteorology. The NTSB can issue safety recommendations during the process.
  6. A final report with probable cause is generally issued within 12–24 months, depending on complexity.

For official updates, the NTSB’s aviation investigation page provides public access to preliminary and final reports: https://www.ntsb.gov/investigations/Pages/aviation.aspx

Effects on airport operations and tenants

  • Airport users in Kalispell can expect short‑term disruptions near the impacted ramp area while insurers and investigators document damage.
  • Owners of affected aircraft may be required to grant access before removal.
  • Pilots operating at S27 should monitor normal notices to air missions and any brief facility advisories.
  • As of Tuesday, no extended closure was reported.

Airports often review ramp layouts, parking lines, chocks, and spacing near runway ends after incidents like this. While Monday’s event will likely prompt an internal look at such items at Kalispell City Airport, no formal changes have been announced yet — any actions will depend on investigation findings.

Human and operational perspective

The human side of Monday’s fire is striking: a landing gone wrong at a community airport turned a quiet afternoon into a scene of heat, noise, and a wall of flame. Yet everyone on board the TBM walked away.

Nearby tenants will likely remember the smell of burned composite and fuel and the sight of scorched tie‑downs while repair crews and adjusters make their rounds. For the pilot and passengers, there will be long hours replaying seconds that moved very fast.

The Socata TBM 700, known for speed and long range, is a common choice for business and family travel in general aviation. It is a single‑pilot airplane operating in varied airport environments, including small fields like Kalispell City Airport. While powerful and advanced, general aviation runway excursions or loss of control on landing are not common but do occur; sometimes these incidents involve impacts with obstacles or parked aircraft if a touchdown or rollout drifts off course.

According to analysis by VisaVerge.com, early transparency from local agencies and quick confirmation of the basics—number of people on board, injury status, and the status of the fire—help calm public concern while federal investigators proceed. That sequence of solid communication and a clear handoff to the FAA and NTSB is what unfolded here.

Bottom line

As the NTSB gathers facts, the main points remain:

  • A landing Socata TBM 700 hit parked planes.
  • A fast‑moving fireball followed; the fire was contained within minutes.
  • All 4 people on board survived; 2 suffered minor injuries and were released.
  • The FAA and NTSB are investigating; no cause has been assigned yet.

The work now shifts from emergency response to careful documentation and, in time, lessons that may prevent the next close call.

VisaVerge.com
Learn Today
Socata TBM 700 → Single‑engine turboprop aircraft model commonly used for business and personal long‑range general aviation flights.
FAA → Federal Aviation Administration, U.S. agency overseeing civil aviation safety, certification, and regulatory compliance.
NTSB → National Transportation Safety Board, independent U.S. agency that investigates transportation accidents and issues safety recommendations.
NOTAM → Notice to Air Missions: a time‑critical notification about airport or airspace hazards, limitations, or changes to pilots.
Preliminary report → Initial factual NTSB document released about 2–3 weeks after an incident summarizing events without assigning probable cause.

This Article in a Nutshell

A landing Socata TBM 700 struck parked aircraft at Kalispell City Airport on August 11, 2025, producing a fireball. All four aboard survived; two sustained minor injuries. Fire crews contained flames within minutes. FAA and NTSB launched investigations; no cause assigned yet while investigators document wreckage and collect witness statements.

— VisaVerge.com
Share This Article
Shashank Singh
Breaking News Reporter
Follow:
As a Breaking News Reporter at VisaVerge.com, Shashank Singh is dedicated to delivering timely and accurate news on the latest developments in immigration and travel. His quick response to emerging stories and ability to present complex information in an understandable format makes him a valuable asset. Shashank's reporting keeps VisaVerge's readers at the forefront of the most current and impactful news in the field.
Subscribe
Notify of
guest

0 Comments
Inline Feedbacks
View all comments